All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Pavel Machek <pavel@ucw.cz>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [PATCH 0/2] code of conduct fixes
Date: Wed, 10 Oct 2018 09:25:36 -0700	[thread overview]
Message-ID: <5e5c745b-5b59-6655-99b1-c40874fdbdf2@infradead.org> (raw)
In-Reply-To: <20181010161256.GB19941@amd>

On 10/10/18 9:12 AM, Pavel Machek wrote:
> Hi!
> 
>>> Personally I'm not happy at all with how the new code of conduct was
>>> rushed in, least because I still don't understand why it happened,
>>> but also for all the other reasons we've discussed here in the past
>>> few weeks.
> 
> These are exactly my thoughts.

Exactly.  We have a process and the 4.19-rc4 CoC patch did not follow it.

>>> But I also understand that there's lots of people (me included) who
>>> don't want to ship a release with the code of conduct in it's current
>>> in-between state. I think adding a disclaimer at the top, along the
>>> lines of
>>>
>>> "Please note that this code of conduct and it's enforcement are still
>>> under discussion."
>>
>> I don't disagree with the position, but eliminating our old code of
>> conduct in favour of another we cast doubt on with this disclaimer
>> effectively leaves us with nothing at all, which seems to be a worse
>> situation.  In that case, I think reverting the CoC commit
>> (8a104f8b5867c682) and then restarting the replacement process is
>> better than adding a disclaimer to the new one.
> 
> Reverting it then having proper discussion sounds suitable to me.
> 
> (And it would be nice to have something on the mailing lists, too, as
> I probably won't make it to kernel summit this year.)

Ditto.

-- 
~Randy

      reply	other threads:[~2018-10-10 16:25 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06 21:35 [Ksummit-discuss] [PATCH 0/2] code of conduct fixes James Bottomley
2018-10-06 21:35 ` James Bottomley
2018-10-06 21:36 ` [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley
2018-10-06 21:36   ` James Bottomley
2018-10-07  8:25   ` [Ksummit-discuss] " Geert Uytterhoeven
2018-10-07  8:25     ` Geert Uytterhoeven
2018-10-07 15:25     ` Shuah Khan
2018-10-07 15:25       ` Shuah Khan
2018-10-07  9:04   ` Daniel Vetter
2018-10-07  9:04     ` Daniel Vetter
2018-10-07  9:54     ` Hannes Reinecke
2018-10-07 15:29     ` James Bottomley
2018-10-08 19:49       ` Mauro Carvalho Chehab
2018-10-08 19:49         ` Mauro Carvalho Chehab
2018-10-07 17:53   ` Guenter Roeck
2018-10-07 22:25   ` Dave Airlie
2018-10-07 22:25     ` Dave Airlie
2018-10-07 22:56     ` Al Viro
2018-10-07 23:02       ` Al Viro
2018-10-07 23:37       ` Dave Airlie
2018-10-08 10:14         ` Mark Brown
2018-10-08 10:14           ` Mark Brown
2018-10-08 19:32         ` Mauro Carvalho Chehab
2018-10-08 19:32           ` Mauro Carvalho Chehab
2018-10-08 17:05       ` Luck, Tony
2018-10-08 17:05         ` Luck, Tony
2018-10-08 14:08     ` James Bottomley
2018-10-10 16:36     ` Pavel Machek
2018-10-10 16:36       ` Pavel Machek
2018-10-08 15:20   ` Josh Triplett
2018-10-08 15:20     ` Josh Triplett
2018-10-08 15:30     ` James Bottomley
2018-10-08 19:23       ` Mauro Carvalho Chehab
2018-10-08 19:23         ` Mauro Carvalho Chehab
2018-10-08 19:57         ` Josh Triplett
2018-10-09 10:55           ` Mark Brown
2018-10-09 18:29     ` Rainer Fiebig
2018-10-09 18:56       ` Josh Triplett
2018-10-09 19:38         ` Laurent Pinchart
2018-10-09 19:38           ` Laurent Pinchart
2018-10-09 19:44           ` James Bottomley
2018-10-10  7:22             ` Rainer Fiebig
2018-10-10  5:52           ` Rainer Fiebig
2018-10-10  7:08         ` Rainer Fiebig
2018-10-08 19:24   ` Mauro Carvalho Chehab
2018-10-08 19:24     ` Mauro Carvalho Chehab
2018-10-10 20:48   ` Frank Rowand
2018-10-06 21:37 ` [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley
2018-10-06 21:37   ` James Bottomley
2018-10-06 21:43   ` [Ksummit-discuss] " Tim.Bird
2018-10-06 21:43     ` Tim.Bird
2018-10-07  3:33     ` James Bottomley
2018-10-08 13:51       ` Tim.Bird
2018-10-08 13:51         ` Tim.Bird
2018-10-08 14:09         ` James Bottomley
2018-10-08 17:58           ` Tim.Bird
2018-10-08 17:58             ` Tim.Bird
2018-10-08 18:11             ` James Bottomley
2018-10-08 18:54               ` Tim.Bird
2018-10-08 18:54                 ` Tim.Bird
2018-10-08 15:03         ` jonsmirl
2018-10-08 15:03           ` jonsmirl
2018-10-08 15:37       ` Alan Cox
2018-10-08 15:37         ` Alan Cox
2018-10-11  7:42         ` Dan Carpenter
2018-10-07 15:32   ` Shuah Khan
2018-10-07 15:32     ` Shuah Khan
2018-10-07 17:56   ` Guenter Roeck
2018-10-07 19:51   ` Geert Uytterhoeven
2018-10-07 19:51     ` Geert Uytterhoeven
2018-10-08 18:15   ` Chris Mason
2018-10-08 18:15     ` Chris Mason
2018-10-08 19:04     ` [Ksummit-discuss] " Josh Triplett
2018-10-08 20:23   ` Mauro Carvalho Chehab
2018-10-08 20:23     ` Mauro Carvalho Chehab
2018-10-10 15:53     ` Alan Cox
2018-10-10 15:53       ` Alan Cox
2018-10-10 17:19       ` Mauro Carvalho Chehab
2018-10-10 17:19         ` Mauro Carvalho Chehab
2018-10-10 20:09         ` Alan Cox
2018-10-10 20:09           ` Alan Cox
2018-10-10 20:30           ` Mauro Carvalho Chehab
2018-10-10 20:30             ` Mauro Carvalho Chehab
2018-10-10 20:32           ` Dave Airlie
2018-10-07 17:11 ` [Ksummit-discuss] [PATCH 0/2] code of conduct fixes Daniel Vetter
2018-10-07 17:11   ` Daniel Vetter
2018-10-07 17:40   ` James Bottomley
2018-10-07 17:50     ` jonsmirl
2018-10-07 17:50       ` jonsmirl
2018-10-07 17:52     ` Daniel Vetter
2018-10-10 16:12     ` Pavel Machek
2018-10-10 16:12       ` Pavel Machek
2018-10-10 16:25       ` Randy Dunlap [this message]

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=5e5c745b-5b59-6655-99b1-c40874fdbdf2@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.