ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "jonsmirl@gmail.com" <jonsmirl@gmail.com>
To: trondmy@hammerspace.com
Cc: mishi@linux.com, gnomes@lxorguk.ukuu.org.uk,
	lkml <linux-kernel@vger.kernel.org>,
	ksummit-discuss@lists.linuxfoundation.org,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address
Date: Sat, 20 Oct 2018 15:14:20 -0400	[thread overview]
Message-ID: <CAKON4OxLLhUkPGGbSF_ZtBC18fzZo44t1gUSsbYA0d2vCPfosg@mail.gmail.com> (raw)
In-Reply-To: <dfabf8b10d3e825c9a7f6c110e042dc72e50217d.camel@hammerspace.com>

On Sat, Oct 20, 2018 at 2:47 PM Trond Myklebust <trondmy@hammerspace.com> wrote:
>
> On Sat, 2018-10-20 at 19:28 +0100, Alan Cox wrote:
> > > +to the circumstances. The Code of Conduct Committee is obligated
> > > to
> > > +maintain confidentiality with regard to the reporter of an
> > > incident.
> > > +Further details of specific enforcement policies may be posted
> > > +separately.
> >
> > Unfortunately by ignoring the other suggestions on this you've left
> > this
> > bit broken.
> >
> > The committee can't keep most stuff confidential so it's misleading
> > and
> > wrong to imply they can. Data protection law, reporting laws in some
> > countries and the like mean that anyone expecting an incident to
> > remain
> > confidential from the person it was reported against is living in
> > dreamland and are going to get a nasty shock.
> >
> > At the very least it should say '(except where required by law)'.
> >
> > There is a separate issue that serious things should always go to law
> > enforcement - you are setting up a policy akin to the one that got
> > the
> > catholic church and many others in trouble.
> >
> > You should also reserving the right to report serious incidents
> > directly
> > to law enforcement. Unless of course you want to be forced to sit on
> > multiple reports of physical abuse from different people about
> > someone - unable to tell them about each others report, unable to
> > prove
> > anything, and in twenty years time having to explain to the media why
> > nothing was done.
> >
>
> ...and then you get into questions about how this committee will
> respond to queries from said law enforcement, and indeed to which legal
> systems the committee will or will not report incidents.
>
> Why would we want to be going down the path of trying to handle reports
> about "serious incidents" in the first place? That seems way out of
> scope for a code of conduct arbitration scheme. Even attempting to
> counsel people as to whether or not they should report incidents can
> get you in trouble in many parts of the world.
>

Which is why the lawyers need to go over this document and I haven't
seen anything posted from them. In the same vein Mauro is concerned
that the way this is code is written it is a binding contract in
Brazil.


> --
> Trond Myklebust
> Linux NFS client maintainer, Hammerspace
> trond.myklebust@hammerspace.com
>
>


--
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2018-10-20 19:14 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20 13:49 [Ksummit-discuss] [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document Greg Kroah-Hartman
2018-10-20 13:49 ` [Ksummit-discuss] [PATCH 1/7] Code of conduct: Fix wording around maintainers enforcing the code of conduct Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 2/7] Code of Conduct Interpretation: Add document explaining how the Code of Conduct is to be interpreted Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 3/7] Code of Conduct Interpretation: Properly reference the TAB correctly Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 4/7] Code of Conduct: Provide links between the two documents Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 5/7] Code of Conduct Interpretation: Put in the proper URL for the committee Greg Kroah-Hartman
2018-10-20 19:01   ` Geert Uytterhoeven
2018-10-21  7:18     ` Greg KH
2018-10-20 13:51 ` [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address Greg Kroah-Hartman
2018-10-20 18:28   ` Alan Cox
2018-10-20 18:45     ` Trond Myklebust
2018-10-20 19:14       ` jonsmirl [this message]
2018-10-21  8:27         ` Theodore Y. Ts'o
2018-10-21  9:23           ` Greg KH
2018-10-20 19:24     ` Tim.Bird
2018-10-20 20:07       ` Trond Myklebust
2018-10-21  0:13       ` Alan Cox
2018-10-21  6:19         ` Thomas Gleixner
2018-10-20 20:13     ` James Bottomley
2018-10-20 13:51 ` [Ksummit-discuss] [PATCH 7/7] MAINTAINERS: Add an entry for the code of conduct Greg Kroah-Hartman
2018-10-21 21:20 ` [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-21 22:26   ` Josh Triplett
2018-10-21 23:37     ` Theodore Y. Ts'o
2018-10-23  1:44       ` NeilBrown
2018-10-22 20:26     ` NeilBrown
2018-10-22 22:46       ` Theodore Y. Ts'o
2018-10-23  1:31         ` NeilBrown
2018-10-23  6:26         ` Dan Carpenter
2018-10-23  6:40           ` Al Viro
2018-10-23  6:46             ` Dan Carpenter
2018-10-23  3:31       ` Al Viro
2018-10-23  4:25         ` NeilBrown
2018-10-23  4:52           ` Al Viro
2018-10-23  5:28             ` NeilBrown
2018-10-23  6:00               ` Al Viro
2018-10-23 20:45                 ` NeilBrown
2018-10-23  8:11           ` Theodore Y. Ts'o
2018-10-23 14:22             ` Rainer Fiebig
2018-10-23 15:43               ` Theodore Y. Ts'o
2018-10-23 21:14             ` NeilBrown
2018-10-24 12:16       ` Josh Triplett
2018-10-25 21:14         ` NeilBrown
2018-10-27  1:10           ` Josh Triplett
2018-10-28 21:48             ` NeilBrown
2018-11-01 16:45             ` Paul E. McKenney
2018-11-01 21:11               ` Josh Triplett
2018-11-02 13:13                 ` Paul E. McKenney
2018-11-01 21:50               ` NeilBrown
2018-11-02 13:33                 ` Paul E. McKenney
2018-11-03  8:36                   ` NeilBrown
2018-11-03 17:37                     ` Paul E. McKenney
2018-11-03 21:06                       ` NeilBrown
2018-11-03 22:23                         ` Paul E. McKenney
2018-11-02 13:52                 ` James Bottomley
2018-11-04 10:35         ` Geert Uytterhoeven
2018-10-21 22:33   ` Joe Perches
2018-10-21 22:37     ` Randy Dunlap
2018-10-22  9:09   ` Rainer Fiebig
2018-10-22 11:02   ` James Bottomley
2018-10-24  8:49   ` Laura Abbott
     [not found]     ` <185b786a2bd6e8d527dca161dc42e4f1@redchan.it>
2018-10-25  8:19       ` [Ksummit-discuss] The linux devs can rescind their license grant Greg Kroah-Hartman
     [not found]         ` <20181025193901.GD26403@thyrsus.com>
2018-10-25 20:47           ` Theodore Y. Ts'o
     [not found]             ` <20181025214123.GA2448@thyrsus.com>
2018-10-25 22:12               ` NeilBrown
     [not found]                 ` <20181025223813.GA5137@thyrsus.com>
2018-10-25 22:52                   ` NeilBrown
2018-11-04 10:47                 ` Geert Uytterhoeven
2018-10-25 23:06               ` Al Viro
     [not found]                 ` <20181026022836.GA12924@thyrsus.com>
2018-10-26  5:49                   ` Al Viro
     [not found]                 ` <75eb4a46c8a2c1d4a927760fd1f2009d@redchan.it>
2018-10-27  7:32                   ` Al Viro
2018-10-27 16:18                     ` Tim.Bird
2018-10-27 22:09                       ` Jiri Kosina
     [not found]                         ` <CAK2MWOtNUTjWy5pTcGco5DNurqNCc=9CfDJ-Ko-K+6HDC55ikg@mail.gmail.com>
2018-10-27 23:40                           ` Al Viro
2018-10-28 21:13                         ` NeilBrown
2018-10-29 22:31         ` Bradley M. Kuhn
2018-10-25 22:02     ` [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-25  8:06   ` Pavel Machek
     [not found]   ` <2341648.lzjnUGKk1z@siriux>
2018-10-25 22:18     ` NeilBrown
     [not found]       ` <ffeb597c-9ca2-cf21-ba52-2146ab20c83a@mailbox.org>
2018-10-26 22:40         ` NeilBrown

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=CAKON4OxLLhUkPGGbSF_ZtBC18fzZo44t1gUSsbYA0d2vCPfosg@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mishi@linux.com \
    --cc=trondmy@hammerspace.com \
    /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