From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Axtens <dja@axtens.net>,
"David S. Miller" <davem@davemloft.net>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Eric Dumazet <edumazet@google.com>,
federico.vaga@vaga.pv.it,
Geert Uytterhoeven <geert+renesas@glider.be>,
Helge Deller <deller@gmx.de>, Joshua Kinard <kumba@gentoo.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kern>
Subject: Re: [PATCH RFC 00/15] Zero ****s, hugload of hugs <3
Date: Fri, 30 Nov 2018 14:26:05 -0800 [thread overview]
Message-ID: <20181130222605.GA26261@linux.intel.com> (raw)
In-Reply-To: <20181130151459.3ca2f5c8@lwn.net>
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@linux.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
next prev parent reply other threads:[~2018-11-30 22:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 19:27 [PATCH RFC 00/15] Zero ****s, hugload of hugs <3 Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 07/15] ide: replace **** with a hug Jarkko Sakkinen
2018-11-30 19:40 ` [PATCH RFC 00/15] Zero ****s, hugload of hugs <3 Kees Cook
2018-11-30 19:56 ` Davidlohr Bueso
2018-11-30 20:12 ` Jens Axboe
2018-11-30 20:34 ` Michael Schmitz
2018-11-30 20:35 ` David Miller
[not found] ` <20181130.123507.1940310466680455876.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2018-11-30 20:39 ` Abuse
2018-11-30 20:42 ` David Miller
[not found] ` <20181130.124228.979846577878820546.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2018-11-30 20:45 ` Abuse
2018-11-30 20:43 ` Steven Rostedt
2018-12-01 4:08 ` Jarkko Sakkinen
2018-11-30 21:42 ` Jarkko Sakkinen
2018-11-30 21:47 ` David Miller
2018-11-30 21:53 ` Jens Axboe
2018-11-30 20:34 ` David Miller
2018-11-30 20:55 ` Jarkko Sakkinen
2018-11-30 21:01 ` James Bottomley
2018-11-30 21:44 ` Jarkko Sakkinen
2018-11-30 21:48 ` David Miller
2018-11-30 21:54 ` Jarkko Sakkinen
2018-11-30 22:04 ` James Bottomley
2018-11-30 21:57 ` James Bottomley
2018-11-30 22:12 ` Jarkko Sakkinen
2018-11-30 22:14 ` Jonathan Corbet
2018-11-30 22:26 ` Jarkko Sakkinen [this message]
2018-11-30 22:29 ` Jarkko Sakkinen
2018-11-30 22:30 ` James Bottomley
2018-11-30 22:40 ` Jarkko Sakkinen
2018-11-30 23:28 ` Jarkko Sakkinen
2018-12-01 8:20 ` Geert Uytterhoeven
2018-12-07 13:39 ` Eric Curtin
2018-11-30 22:26 ` James Bottomley
2018-11-30 21:02 ` Steven Rostedt
2018-11-30 21:04 ` Jonathan Corbet
2018-11-30 20:09 ` John Paul Adrian Glaubitz
2018-11-30 21:32 ` Jarkko Sakkinen
2018-11-30 20:31 ` Matthias Brugger
2018-11-30 21:34 ` Jarkko Sakkinen
2018-11-30 20:42 ` Chris Mason
2018-11-30 21:36 ` Jarkko Sakkinen
2018-11-30 21:07 ` Jarkko Sakkinen
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=20181130222605.GA26261@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.net \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=dja@axtens.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=edumazet@google.com \
--cc=federico.vaga@vaga.pv.it \
--cc=geert+renesas@glider.be \
--cc=keescook@chromium.org \
--cc=kumba@gentoo.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kern \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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).