linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	David Miller <davem@davemloft.net>
Cc: dave@stgolabs.net, keescook@chromium.org,
	linux-kernel@vger.kernel.org, amir73il@gmail.com,
	akpm@linux-foundation.org, andriy.shevchenko@linux.intel.com,
	dja@axtens.net, linux@dominikbrodowski.net,
	dri-devel@lists.freedesktop.org, edumazet@google.com,
	federico.vaga@vaga.pv.it, geert+renesas@glider.be, deller@gmx.de,
	corbet@lwn.net, kumba@gentoo.org, linux-doc@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-m68k@lists.linux-m68k.org, linux-media@vger.kernel.org,
	linux-mips@linux-mips.org, linux-mtd@lists.infradead.org,
	linux-parisc@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-scsi@vger.kernel.org, matthias.bgg@gmail.com,
	netdev@vger.kernel.org, nouveau@lists.freedesktop.org,
	pabeni@redhat.com, paul.burton@mips.com, pmladek@suse.com,
	robh@kernel.org, sean.wang@mediatek.com,
	sergey.senozhatsky@gmail.com, shannon.nelson@oracle.com,
	sbrivio@redhat.com, rostedt@goodmis.org, me@tobin.cc,
	makita.toshiaki@lab.ntt.co.jp, willemb@google.com, yhs@fb.com,
	yanjun.zhu@oracle.com
Subject: Re: [PATCH RFC 00/15] Zero ****s, hugload of hugs <3
Date: Fri, 30 Nov 2018 14:04:09 -0800	[thread overview]
Message-ID: <1543615449.3031.32.camel@HansenPartnership.com> (raw)
In-Reply-To: <20181130215429.GA24415@linux.intel.com>

On Fri, 2018-11-30 at 13:54 -0800, Jarkko Sakkinen wrote:
> On Fri, Nov 30, 2018 at 01:48:08PM -0800, David Miller wrote:
> > From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > Date: Fri, 30 Nov 2018 13:44:05 -0800
> > 
> > > On Fri, Nov 30, 2018 at 01:01:02PM -0800, James Bottomley wrote:
> > > > No because use of what some people consider to be bad language
> > > > isn't
> > > > necessarily abusive, offensive or degrading.  Our most heavily
> > > > censored
> > > > medium is TV and "fuck" is now considered acceptable in certain
> > > > contexts on most channels in the UK and EU.
> > > 
> > > This makes following the CoC extremely hard to a non-native
> > > speaker as
> > > it is not too explicit on what is OK and what is not. I did
> > > through the
> > > whole thing with an eye glass and this what I deduced from it.
> > 
> > It would be helpful if you could explain what part of the language
> > is unclear wrt. explaining how CoC does not apply to existing code.
> > 
> > That part seems very explicit to me.
> 
> Well, now that I re-read it, it was this part to be exact:
> 
> "Maintainers have the right and responsibility to remove, edit, or
> reject comments, commits, code, wiki edits, issues, and other
> contributions that are not aligned to this Code of Conduct, or to ban
> temporarily or permanently any contributor for other behaviors that
> they deem inappropriate, threatening, offensive, or harmful."
> 
> How this should be interpreted?

Firstly, this is *only* about contributions going forward.  The
interpretation document says we don't have to look back into the
repository and we definitely can't remove something from git that's
already been committed.

As a Maintainer, if you feel bad language is inappropriate for your
subsystem then you say so and reject with that reason patches that come
in containing it (suggesting alternative rewordings).  However, your
determination about what is or isn't acceptable in your subsystem isn't
binding on other maintainers, who may have different standards ... this
is identical to what we do with coding, like your insistence on one
line per variable or other subsystem's insistence on reverse christmas
tree for includes ...

James


> I have not really followed the previous CoC discussions as I try to
> always use polite language so I'm sorry if this duplicate.
> 
> /Jarkko
> 


  reply	other threads:[~2018-11-30 22:04 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181130192737.15053-1-jarkko.sakkinen@linux.intel.com>
2018-11-30 19:27 ` [PATCH RFC 05/15] parisc: replace **** with a hug Jarkko Sakkinen
2018-11-30 22:48   ` Dennis Clarke
2018-11-30 23:03     ` Jarkko Sakkinen
2018-11-30 23:05   ` Diego Viola
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]         ` <2007856.n5V9iKLVsV@eth7>
2018-11-30 20:42           ` David Miller
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 [this message]
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
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 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=1543615449.3031.32.camel@HansenPartnership.com \
    --to=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=jarkko.sakkinen@linux.intel.com \
    --cc=keescook@chromium.org \
    --cc=kumba@gentoo.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=makita.toshiaki@lab.ntt.co.jp \
    --cc=matthias.bgg@gmail.com \
    --cc=me@tobin.cc \
    --cc=netdev@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=pabeni@redhat.com \
    --cc=paul.burton@mips.com \
    --cc=pmladek@suse.com \
    --cc=robh@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sbrivio@redhat.com \
    --cc=sean.wang@mediatek.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=shannon.nelson@oracle.com \
    --cc=willemb@google.com \
    --cc=yanjun.zhu@oracle.com \
    --cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).