linux-fsdevel.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>
Cc: 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>, Jonathan Corbet <corbet@lwn.net>,
	Joshua Kinard <kumba@gentoo.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	linux-ide@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux MIPS Mailing List <linux-mips@linux-mips.org>,
	Linux mtd <linux-mtd@lists.infradead.org>,
	linux-parisc <linux-parisc@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	linux-scsi@vger.kernel.org, matthias.bgg@gmail.com,
	Network Development <netdev@vger.kernel.org>,
	nouveau <nouveau@lists.freedesktop.org>,
	Paolo Abeni <pabeni@redhat.com>,
	Paul Burton <paul.burton@mips.com>,
	Petr Mladek <pmladek@suse.com>, Rob Herring <robh@kernel.org>,
	sean.wang@mediatek.com,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	shannon.nelson@oracle.com, Stefano Brivio <sbrivio@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	"Tobin C. Harding" <me@tobin.cc>,
	makita.toshiaki@lab.ntt.co.jp,
	Willem de Bruijn <willemb@google.com>, Yonghong Song <yhs@fb.com>,
	yanjun.zhu@oracle.com
Subject: Re: [PATCH RFC 00/15] Zero ****s, hugload of hugs <3
Date: Fri, 30 Nov 2018 13:57:49 -0800	[thread overview]
Message-ID: <1543615069.3031.27.camel@HansenPartnership.com> (raw)
In-Reply-To: <20181130214405.GG23772@linux.intel.com>

On Fri, 2018-11-30 at 13:44 -0800, Jarkko Sakkinen wrote:
> 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.

OK, so something that would simply be considered in some quarters as
bad language isn't explicitly banned.  The thing which differentiates
simple bad language from "abusive, offensive or degrading language",
which is called out by the CoC, is the context and the target.

So when it's a simple expletive or the code of the author or even the
hardware is the target, I'd say it's an easy determination it's not a
CoC violation.  If someone else's code is the target or the inventor of
the hardware is targetted by name, I'd say it is.  Even non-native
English speakers should be able to determine target and context,
because that's the essence of meaning.

James

  parent reply	other threads:[~2018-12-01  9:08 UTC|newest]

Thread overview: 44+ 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 12/15] inotify: replace **** with a hug Jarkko Sakkinen
2018-12-01  6:40   ` Amir Goldstein
2018-12-05  9:49     ` Jan Kara
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 [this message]
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 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=1543615069.3031.27.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).