[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181130222605.GA26261@linux.intel.com>
Date: Fri, 30 Nov 2018 14:26:05 -0800
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Jonathan Corbet <corbet@....net>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
Davidlohr Bueso <dave@...olabs.net>,
Kees Cook <keescook@...omium.org>,
LKML <linux-kernel@...r.kernel.org>,
Amir Goldstein <amir73il@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Daniel Axtens <dja@...ens.net>,
"David S. Miller" <davem@...emloft.net>,
Dominik Brodowski <linux@...inikbrodowski.net>,
Maling list - DRI developers
<dri-devel@...ts.freedesktop.org>,
Eric Dumazet <edumazet@...gle.com>, federico.vaga@...a.pv.it,
Geert Uytterhoeven <geert+renesas@...der.be>,
Helge Deller <deller@....de>, Joshua Kinard <kumba@...too.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
linux-ide@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
Linux Media Mailing List <linux-media@...r.kernel.org>,
Linux MIPS Mailing List <linux-mips@...ux-mips.org>,
Linux mtd <linux-mtd@...ts.infradead.org>,
linux-parisc <linux-parisc@...r.kernel.org>,
Linux PM list <linux-pm@...r.kernel.org>,
linux-scsi@...r.kernel.org, matthias.bgg@...il.com,
Network Development <netdev@...r.kernel.org>,
nouveau <nouveau@...ts.freedesktop.org>,
Paolo Abeni <pabeni@...hat.com>,
Paul Burton <paul.burton@...s.com>,
Petr Mladek <pmladek@...e.com>, Rob Herring <robh@...nel.org>,
sean.wang@...iatek.com,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
shannon.nelson@...cle.com, Stefano Brivio <sbrivio@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
"Tobin C. Harding" <me@...in.cc>, makita.toshiaki@....ntt.co.jp,
Willem de Bruijn <willemb@...gle.com>,
Yonghong Song <yhs@...com>, yanjun.zhu@...cle.com
Subject: Re: [PATCH RFC 00/15] Zero ****s, hugload of hugs <3
On Fri, Nov 30, 2018 at 03:14:59PM -0700, Jonathan Corbet wrote:
> On Fri, 30 Nov 2018 14:12:19 -0800
> Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com> wrote:
>
> > As a maintainer myself (and based on somewhat disturbed feedback from
> > other maintainers) I can only make the conclusion that nobody knows what
> > the responsibility part here means.
> >
> > I would interpret, if I read it like at lawyer at least, that even for
> > existing code you would need to do the changes postmorterm.
> >
> > Is this wrong interpretation? Should I conclude that I made a mistake
> > by reading the CoC and trying to understand what it *actually* says?
> > After this discussion, I can say that I understand it less than before.
>
> Have you read Documentation/process/code-of-conduct-interpretation.rst?
> As has been pointed out, it contains a clear answer to how things should
> be interpreted here.
Ugh, was not aware that there two documents.
Yeah, definitely sheds light. Why the documents could not be merged to
single common sense code of conduct?
/Jarkko
Powered by blists - more mailing lists