mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Chris Mason <clm@fb.com>, Dan Williams <dan.j.williams@intel.com>,
	Jonathan Corbet <corbet@lwn.net>, Olof Johansson <olof@lxom.net>,
	Steven Rostedt <rostedt@goodmis.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Code of Conduct: Let's revamp it.
Date: Tue, 18 Sep 2018 22:16:31 +0200	[thread overview]
Message-ID: <20180918201631.as5zjjkldtkduwll@wunner.de> (raw)
In-Reply-To: <20180917122430.GA3320@kroah.com>

On Mon, Sep 17, 2018 at 02:24:30PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Sep 17, 2018 at 01:48:52PM +0200, Lukas Wunner wrote:
> > On Sun, Sep 16, 2018 at 12:22:43PM -0700, Linus Torvalds wrote:
> > > +Scope
> > > +=====
> > > +
> > > +This Code of Conduct applies both within project spaces and in public
> > > +spaces when an individual is representing the project or its community.
> > > +Examples of representing a project or community include using an
> > > +official project e-mail address, posting via an official social media
> > > +account, or acting as an appointed representative at an online or
> > > +offline event. Representation of a project may be further defined and
> > > +clarified by project maintainers.
> > 
> > Seriously though, I read this to know what I need to be aware of but oddly
> > the language of this paragraph says it doesn't apply to me:  I'm not using
> > an official project e-mail address nor an official social media account,
> > nor has anyone appointed me as representative.  I can live with that, I'm
> > just wondering what the benefit of a document is that only seems to apply
> > to a tiny fraction of the community.
> 
> I do not think you are reading the document correctly.  As an example,
> it should cover any emails sent to this list.  That is not a "tiny
> fraction" by my last count :)

You may want to make that more explicit in the document.

The document appears to be geared towards smaller projects with
official project e-mail addresses handed out to a group and it
specifies dos and don'ts for members of that group when they have
their project hat on.

However in the kernel community there's a large continuum with
Linus and those who send him pulls on one end of the spectrum,
and random folks writing on the mailing lists or bugzillas at
the other end.  The further we get to the latter end, the more
menthal gymnastics are necessary (at least for me) to consider
the document applicable to them, given the restrictions laid
out in the "Scope" paragraph.

Just my 2 cents anyway.

Thanks,

Lukas

  parent reply	other threads:[~2018-09-18 20:16 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [not found]     ` <61b4a3f9-ccd1-061c-1c1b-ec993b056c66@bosch-fellbach.de>
2018-09-20 10:57       ` Lukas Wunner
2018-09-19  6:00 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
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
2018-09-20  9:29         ` unconditionedwitness
2018-09-20 21:18 Christoph Conrads
2018-09-21  8:09 ` Martin Steigerwald
2018-09-21 11:36   ` Christoph Conrads

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=20180918201631.as5zjjkldtkduwll@wunner.de \
    --to=lukas@wunner.de \
    --cc=clm@fb.com \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lxom.net \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®