linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neil@brown.name>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ksummit-discuss@lists.linuxfoundation.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Olof Johansson <olof@lixom.net>, Chris Mason <clm@fb.com>,
	Mishi Choudhary <mishi@linux.com>
Subject: Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document
Date: Mon, 22 Oct 2018 08:20:11 +1100	[thread overview]
Message-ID: <87y3ar80ac.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20181020134908.GA32218@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 2996 bytes --]

On Sat, Oct 20 2018, Greg Kroah-Hartman wrote:

> Hi all,
>
> As everyone knows by now, we added a new Code of Conduct to the kernel
> tree a few weeks ago.

I wanted to stay detached from all this, but as remaining (publicly)
silent might be seen (publicly) as acquiescing, I hereby declare that:
   I reject, as illegitimate, this Code and the process by
   which it is being "developed".

It is clear from the surrounding discussions that this is well outside our
core competencies.  It will be flawed, it isn't what we need.

I call on any other community members who reject this process to say so,
not to remain silent.
#Iobject

We don't need a "Code of Conduct" nearly as much as we need "Leadership
in conduct".  Without the leadership, any code looks like a joke.

I call on Linus Torvalds to follow up on his confession (which I think
is momentous and worth celebrating - Hurray!!!) with repentance - a clear
demonstration of change of mind.
  Linus: I know your intentions are good and am confident that, now that
  you see the problem, you will be able to effect a solution.  If you
  are not so confident, please be aware that there are many in the
  community who can see clearly where you were blind, and are willing to
  help guide and coach.  Please reach out to someone you trust, and ask.

I call on the community to respond to this confession and repentance
from Linus with forgiveness and restoration.

I have no direct hurts to report and little to forgive, so my
forgiveness can only be worth little.  However, for what it is worth:
  I offer to Linus, and to any who are seeking to improve their
  behaviour, my forgiveness for any past hurts, whether direct or
  indirect.  I hold no grudge, and wish to continue working together as
  the need and opportunity arises.

  #Iforgive

I call on the community to effect whatever reparation is possible to
those who have been hurt. Sometimes an apology is all that is possible,
sometimes it is all that is needed.  If you are ever in a position to do
more, please consider doing so.

  On behalf of my community, I apologise to all those who have been hurt
  by us, for the lack of respect and care which should have been shown.
  Where I have hurt you, whether through action or inaction, I
  unreservedly apologise.

  #Iapologise  (or #Iapologize :-)

I call on you, Greg:
 - to abandon this divisive attempt to impose a "Code of Conduct"
 - to revert 8a104f8b5867c68
 - to return to your core competence of building a great team around
   a great kernel

 #Isupportreversion

I call on the community to consider what *does* need to be said, about
conduct, to people outside the community and who have recently joined.
What is the document that you would have liked to have read as you were
starting out?  It is all too long ago for me to remember clearly, and so
much has changed.

Thanks,
NeilBrown
#Iobject #Iforgive #Iapologise #Isupportreversion

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

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

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20 13:49 [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document Greg Kroah-Hartman
2018-10-20 13:49 ` [PATCH 1/7] Code of conduct: Fix wording around maintainers enforcing the code of conduct Greg Kroah-Hartman
2018-10-20 13:50 ` [PATCH 2/7] Code of Conduct Interpretation: Add document explaining how the Code of Conduct is to be interpreted Greg Kroah-Hartman
2018-10-20 13:50 ` [PATCH 3/7] Code of Conduct Interpretation: Properly reference the TAB correctly Greg Kroah-Hartman
2018-10-20 13:50 ` [PATCH 4/7] Code of Conduct: Provide links between the two documents Greg Kroah-Hartman
2018-10-20 13:50 ` [PATCH 5/7] Code of Conduct Interpretation: Put in the proper URL for the committee Greg Kroah-Hartman
2018-10-20 19:01   ` Geert Uytterhoeven
2018-10-21  7:18     ` [Ksummit-discuss] " Greg KH
2018-10-20 13:51 ` [PATCH 6/7] Code of Conduct: Change the contact email address Greg Kroah-Hartman
2018-10-20 18:28   ` Alan Cox
2018-10-20 18:45     ` [Ksummit-discuss] " Trond Myklebust
2018-10-20 19:14       ` jonsmirl
2018-10-21  8:27         ` Theodore Y. Ts'o
2018-10-21  9:23           ` Greg KH
2018-10-20 19:24     ` Tim.Bird
2018-10-20 20:07       ` Trond Myklebust
2018-10-21  0:13       ` Alan Cox
2018-10-21  6:19         ` Thomas Gleixner
2018-10-20 20:13     ` James Bottomley
2018-10-20 13:51 ` [PATCH 7/7] MAINTAINERS: Add an entry for the code of conduct Greg Kroah-Hartman
2018-10-21 21:20 ` NeilBrown [this message]
2018-10-21 22:26   ` [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document Josh Triplett
2018-10-21 23:37     ` Theodore Y. Ts'o
2018-10-23  1:44       ` NeilBrown
2018-10-22 20:26     ` NeilBrown
2018-10-22 22:46       ` Theodore Y. Ts'o
2018-10-23  1:31         ` NeilBrown
2018-10-23  6:26         ` Dan Carpenter
2018-10-23  6:40           ` Al Viro
2018-10-23  6:46             ` Dan Carpenter
2018-10-23  3:31       ` Al Viro
2018-10-23  4:25         ` NeilBrown
2018-10-23  4:52           ` Al Viro
2018-10-23  5:28             ` NeilBrown
2018-10-23  6:00               ` Al Viro
2018-10-23 20:45                 ` NeilBrown
2018-10-23  8:11           ` Theodore Y. Ts'o
2018-10-23 14:22             ` Rainer Fiebig
2018-10-23 15:43               ` Theodore Y. Ts'o
2018-10-23 17:51                 ` Rainer Fiebig
2018-10-23 21:14             ` NeilBrown
2018-10-24 12:16       ` Josh Triplett
2018-10-25 21:14         ` NeilBrown
2018-10-27  1:10           ` Josh Triplett
2018-10-28 21:48             ` NeilBrown
2018-11-01 16:45             ` Paul E. McKenney
2018-11-01 21:11               ` Josh Triplett
2018-11-02 13:13                 ` Paul E. McKenney
2018-11-01 21:50               ` NeilBrown
2018-11-02 13:33                 ` Paul E. McKenney
2018-11-03  8:36                   ` NeilBrown
2018-11-03 17:37                     ` Paul E. McKenney
2018-11-03 21:06                       ` NeilBrown
2018-11-03 22:23                         ` Paul E. McKenney
2018-11-02 13:52                 ` James Bottomley
2018-11-03  9:19                   ` Eric S. Raymond
2018-11-04 10:35         ` Geert Uytterhoeven
2018-10-21 22:33   ` Joe Perches
2018-10-21 22:37     ` Randy Dunlap
2018-10-22  9:09   ` Rainer Fiebig
2018-10-22 11:02   ` [Ksummit-discuss] " James Bottomley
2018-10-24  8:49   ` Laura Abbott
2018-10-25  7:56     ` The linux devs can rescind their license grant visionsofalice
2018-10-25  8:19       ` Greg Kroah-Hartman
2018-10-25 19:39         ` Eric S. Raymond
2018-10-25 20:47           ` Theodore Y. Ts'o
2018-10-25 21:41             ` Eric S. Raymond
2018-10-25 22:12               ` NeilBrown
2018-10-25 22:38                 ` Eric S. Raymond
2018-10-25 22:52                   ` NeilBrown
2018-11-04 10:47                 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-10-25 23:06               ` Al Viro
2018-10-26  2:28                 ` Eric S. Raymond
2018-10-26  5:49                   ` Al Viro
2018-10-27  6:52                 ` visionsofalice
2018-10-27  7:32                   ` Al Viro
2018-10-27 16:18                     ` [Ksummit-discuss] " Tim.Bird
2018-10-27 22:09                       ` Jiri Kosina
     [not found]                         ` <CAK2MWOtNUTjWy5pTcGco5DNurqNCc=9CfDJ-Ko-K+6HDC55ikg@mail.gmail.com>
2018-10-27 23:07                           ` Eric S. Raymond
2018-10-27 23:40                           ` Al Viro
2018-10-28 21:13                         ` NeilBrown
2018-10-25 23:32             ` Iván Chavero
2018-10-26 13:15           ` Eben Moglen
2018-10-26 15:50             ` Eric S. Raymond
2018-10-26 15:53               ` Eben Moglen
2018-10-26 17:32             ` visionsofalice
2018-10-26 18:31               ` Eben Moglen
2018-10-27  7:12                 ` visionsofalice
2018-12-18 18:53                 ` The linux devs can rescind their license grant. - Analysis published? visionsofalice
2018-10-26 10:34         ` The linux devs can rescind their license grant visionsofalice
2018-10-29 22:31         ` Bradley M. Kuhn
2018-12-18 19:17           ` visionsofalice
2018-10-27  5:04       ` The linux devs can rescind their license grant. - Additional restrictive terms visionsofalice
2018-12-18 20:55       ` The CoC regime is a License violation " visionsofalice
2018-12-19  1:17       ` visionsofalice
2018-12-23 16:05       ` visionsofalice
2018-10-25 22:02     ` Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-25  8:06   ` Pavel Machek
2018-10-25 11:20   ` Rainer Fiebig
2018-10-25 22:18     ` NeilBrown
2018-10-26  8:33       ` Rainer Fiebig
2018-10-26 22:40         ` NeilBrown
2018-10-27 11:49           ` Rainer Fiebig
2018-10-21 23:36 ` Eric S. Raymond

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=87y3ar80ac.fsf@notabene.neil.brown.name \
    --to=neil@brown.name \
    --cc=clm@fb.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mishi@linux.com \
    --cc=olof@lixom.net \
    --cc=tglx@linutronix.de \
    /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).