linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tirado <mtirado418@gmail.com>
To: James.Bottomley@hansenpartnership.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses
Date: Sat, 20 Oct 2018 18:11:16 +0000	[thread overview]
Message-ID: <CAMkWEXPSSXG_f1v-BYEXwkwoniJ8wndo49z01BSh-QaLcD3ChQ@mail.gmail.com> (raw)
In-Reply-To: <1539701896.2805.7.camel@HansenPartnership.com>

James, and our other friends,


On Tue, Oct 16, 2018 at 2:59 PM James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>
> The current code of conduct has an ambiguity

More than one ambiguity. This whole file needs to go.

>* Trolling,

Who decides what is trolling, and what is a technique for raising
awareness or sparking discussion on an issue?

>  * Other conduct which could reasonably be considered inappropriate in a
>    professional setting


Why should this last bit remain?  Any literate person with access to a
dictionary should know how ambiguous the word professional is.  As an
amateur contributor to the FOSS ecosystem I am more than a bit
offended by the decision to use such divisive, politically charged,
and financially discriminatory language in a project of such massive
technical importance.  This entire file should be expunged from the
repository and replaced by well defined minimalistic guidelines for
maintaining order on the mailing lists, rather than a set of ambiguous
codes that force maintainers to take politically motivated actions
against contributors for undefined reasons.

Using words like professional is a distressing red flag because it
doesn't add any clarification on the issue (what was the issue
again?), it only raises more questions.  I can't think of any reason
that word would be needed unless you're trying to push out unpaid
contributors.  Why should someones employment status be held against
them when contributing ideas or code to a technical project that has
benefited greatly from amateur contributions?

I fear for the kernels future now that irrational politics are
beginning to creep.

  parent reply	other threads:[~2018-10-20 22:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 14:57 [PATCH v3 0/3] code of conduct fixes James Bottomley
2018-10-16 14:58 ` [PATCH v3 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley
2018-10-17  2:10   ` [Ksummit-discuss] " Frank Rowand
2018-10-17  2:41     ` James Bottomley
2018-10-17 18:49       ` Frank Rowand
2018-10-17 19:07         ` Randy Dunlap
2018-10-17 19:08         ` James Bottomley
2018-10-17 19:53           ` Frank Rowand
2018-10-18 14:56             ` James Bottomley
2018-10-18 19:22               ` Frank Rowand
2018-10-18 19:49                 ` Tim.Bird
2018-10-18 19:57                   ` James Bottomley
2018-10-18 23:07                     ` Frank Rowand
2018-10-17 19:26         ` Alexandre Belloni
2018-10-20 18:11   ` Michael Tirado [this message]
2018-10-16 14:59 ` [PATCH v3 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley
2018-10-16 15:00 ` [PATCH v3 3/3] code-of-conduct: Add back the TAB as the central reporting point James Bottomley
2018-10-17 15:32   ` [Ksummit-discuss] " Shuah Khan

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=CAMkWEXPSSXG_f1v-BYEXwkwoniJ8wndo49z01BSh-QaLcD3ChQ@mail.gmail.com \
    --to=mtirado418@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).