linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
Cc: xDynamite <dreamingforward@gmail.com>,
	"jonsmirl@gmail.com" <jonsmirl@gmail.com>,
	Theodore Tso <tytso@mit.edu>,
	fche@redhat.com, riel@surriel.com, ec429@cantab.net,
	Olof Johansson <olof@lixom.net>, Jonathan Corbet <corbet@lwn.net>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Code of Conduct: Let's revamp it.
Date: Fri, 28 Sep 2018 16:56:53 +0100	[thread overview]
Message-ID: <20180928165653.17bbdb13@alans-desktop> (raw)
In-Reply-To: <9be16b08-7aa9-d42e-24c0-f054af39b78a@petrovitsch.priv.at>

> Well, then I have to repeat myself: Signed-off source code (in form of
> patches) in a well-known programming language for a (nowadays)
> well-known GPLv2 licensed project mailed on "everyone can subscribe"
> mailinglists, (thus) to be found in several $SEARCH_ENGINE-indexed
> mailinglist archives, if accepted to be found in lots of publicly
> accessible git repos can be not intended to be published?
> 
> I wonder what else must happen.

There is a bigger problem in the ambiguity.

It's easy to deal with signed off by lines because I had the sense to
make sure that the DCO covered us for EU data protection and thus it's
explicit.

It's relatively easy to deal with the case of 'I contributed some code'.

It's really not at all obvious what happens with 'I got some code from
another project that contains it's authors name'.

The wording IMHO just needs tightening up - and that's a useful
discussion that ought to he bad. I tihnk everyone understands the *inent*
of such wording - don't go around doxing people, or posting their home
address on facebook and calling for people to attend with pitchforks.

There's a second related area that needs sorting out in wording which is
the implication of any kind of privacy in a complaint - which is really
bad in two ways

As it is set up now the tab is not a lawyer so the tab could not claim
any kind of legal privilege. That means in the event of a complaint the
tab would be powerless not to release almost all the info in the
complaint if hit by a data protectin request in many jurisdictions. Sure
they'd have to (and be required to) remove some of the information that
might identify the complainant.

Secondly one thing that we've learned repeatedly (and notably from the
church scandals) is that there are some complaints that should upon
receipt be handed directly to law enforcement, but there is no carve out
for this.

The other issue is that whoever handles any complaint system needs a
budget and lawyers because they will potentially have to field judicial
reviews and other challenges. That means the TAB needs to have
exemplary record keeping and process because anyone who stands up in a
legal challenge and says 'Umm.. we read it and talked about it and kind
of decided X but I don't remember why and there are no minutes and there
is on process document' is going to get fried. Someone needs to have that
process in place well in advance.

Alan

  parent reply	other threads:[~2018-09-28 15:57 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  6:00 Code of Conduct: Let's revamp it Edward Cree
2018-09-19 14:18 ` Jonathan Corbet
2018-09-19 23:35   ` Edward Cree
2018-09-20  1:16     ` Olof Johansson
2018-09-20  2:14       ` Edward Cree
2018-09-21  1:48         ` Rik van Riel
2018-09-21  2:16           ` unixing
2018-09-21 13:07           ` Frank Ch. Eigler
2018-09-21 16:34             ` \0xDynamite
2018-09-21 23:15               ` Theodore Y. Ts'o
2018-09-21 23:20                 ` Joey Pabalinas
2018-09-21 23:31                 ` jonsmirl
2018-09-21 23:59                   ` Bernd Petrovitsch
2018-09-24 18:59                     ` \0xDynamite
2018-09-24 19:45                       ` Bernd Petrovitsch
2018-09-25  2:24                         ` gratuitouslicensesarerevocable
2018-09-25 17:14                         ` \0xDynamite
2018-09-26  0:41                           ` Bernd Petrovitsch
2018-09-26 19:34                             ` \0xDynamite
2018-09-26 20:55                               ` Joey Pabalinas
2018-09-28 18:34                                 ` \0xDynamite
2018-09-28 15:56                             ` Alan Cox [this message]
2018-09-28 19:38                               ` jonsmirl
2018-09-29 12:44                               ` Eric S. Raymond
2018-09-29 12:46                               ` Eric S. Raymond
2018-09-22  0:05                   ` Joey Pabalinas
2018-09-22  0:24                     ` jonsmirl
2018-09-24 17:43                       ` Max Filippov
2018-09-24 18:07                         ` jonsmirl
2018-09-23 18:44                 ` \0xDynamite
2018-09-25 23:48                 ` Michael Woods
2018-09-24 17:25             ` unconditionedwitness
2018-09-25 11:28         ` Pavel Machek
2018-09-25 12:36           ` Christoph Conrads
2018-09-25 13:13             ` Eric S. Raymond
2018-09-25 13:41               ` Christoph Conrads
2018-09-25 17:38                 ` \0xDynamite
2018-09-25 13:28             ` Pavel Machek
2018-09-26 10:24               ` Martin Steigerwald
2018-09-25 15:14             ` Theodore Y. Ts'o
2018-09-25 22:30               ` Eric S. Raymond
2018-09-26 11:17               ` Christoph Conrads
2018-09-20  3:07       ` Theodore Y. Ts'o
2018-09-20  4:18       ` Willy Tarreau
2018-09-20  9:27         ` unconditionedwitness
2018-09-20 22:57           ` Edward Cree
2018-09-23 14:50             ` Christoph Conrads
2018-09-23 18:41             ` \0xDynamite
2018-09-24 17:21             ` unconditionedwitness
     [not found]               ` <c61eb2d545150d46428f4bc25843cd58@redchan.it>
     [not found]                 ` <201809241941.44460.dr.klepp@gmx.at>
     [not found]                   ` <20180924204809.GK23968@linuxmafia.com>
2018-09-25  2:09                     ` [DNG] Fwd: " gratuitouslicensesarerevocable
2018-09-20  9:29         ` unconditionedwitness
  -- strict thread matches above, loose matches on Subject: below --
2018-09-20 21:18 Christoph Conrads
2018-09-21  8:09 ` Martin Steigerwald
2018-09-21 11:36   ` Christoph Conrads
2018-09-17 11:48 Lukas Wunner
2018-09-17 12:24 ` Greg Kroah-Hartman
2018-09-18 19:16   ` Pavel Machek
2018-09-19 10:30     ` Mauro Carvalho Chehab
2018-09-18 20:16   ` Lukas Wunner
     [not found]     ` <61b4a3f9-ccd1-061c-1c1b-ec993b056c66@bosch-fellbach.de>
2018-09-20 10:57       ` Lukas Wunner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180928165653.17bbdb13@alans-desktop \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=bernd@petrovitsch.priv.at \
    --cc=corbet@lwn.net \
    --cc=dreamingforward@gmail.com \
    --cc=ec429@cantab.net \
    --cc=fche@redhat.com \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=riel@surriel.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).