From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC FOR KS] CoC and Linus position (perhaps undocumented/closed/limited/invite session)
Date: Tue, 18 Sep 2018 16:58:02 +0200 [thread overview]
Message-ID: <CAMuHMdXnNVt8bvywgZQmMaAt8=Qy=6z7PQa4xsM-2h_Ymo3fwQ@mail.gmail.com> (raw)
In-Reply-To: <CAKMK7uGDd6771vc8WNyNPPgHoCA_7Bmj19DGLXBn8sU88mpDoA@mail.gmail.com>
On Tue, Sep 18, 2018 at 4:34 PM Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> On Tue, Sep 18, 2018 at 3:43 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Tue, 18 Sep 2018 15:55:23 +1000
> > Dave Airlie <airlied@gmail.com> wrote:
> What suprised me is how quickly this all happened. Back when we've
> done the same CoC for freedesktop.org and all the graphics stuff
> hosted there, there's been years of hallway track preceeding formally
> enacting the CoC. Social expectations on the mailing list already
> reflected the consensus that we expect constructive and respectful
> collaboration, with informal peer driven enforcement when a maintainer
> went a bit over the line. We also had pretty much everyone ack the
> documentation patch before it landed. In other words, nothing changed
> for dri-devel when we've done this ~2 years ago, except the already
> lived expectations have been encoded.
>
> As much as I welcome this as a first step on a fairly long path, it
> does feel rushed since it seems to have happened in just ~10 days.
> From chatting with people, I think this left a lot wondering about
> what's really going on, with interesting conspiracy theories running
> rampant. Personally I have serious worries that to rapid change will
> overwhelm the community's ability to process it, with ugly unintended
> consequences.
Indeed, it feels a bit... rushed.
Commit ddbd2b7ad99a418c ("Code of Conflict") was acked by 66 developers.
Bringing up the analogy with other source tree changes, I would expect a
patch ripping out a substantial piece of code to be CCed to the people that
acked its original introduction. Obviously that's not what happened here.
Disclaimer: the above doesn't say anything about the merits of the new CoC.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-09-18 14:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 5:55 Dave Airlie
2018-09-18 13:43 ` Steven Rostedt
2018-09-18 14:34 ` Daniel Vetter
2018-09-18 14:58 ` Geert Uytterhoeven [this message]
2018-09-20 9:12 ` Rafael J. Wysocki
2018-09-20 9:53 ` Daniel Vetter
2018-09-20 10:05 ` Daniel Vetter
2018-09-20 15:57 ` Mark Brown
2018-09-18 14:02 ` James Bottomley
2018-09-18 14:41 ` Daniel Vetter
2018-09-18 19:29 ` Mauro Carvalho Chehab
2018-09-18 19:36 ` Josh Triplett
2018-09-18 19:52 ` Mauro Carvalho Chehab
2018-09-18 20:52 ` Takashi Iwai
2018-09-18 21:15 ` Josh Triplett
2018-09-18 23:06 ` Steven Rostedt
2018-09-18 23:38 ` Laurent Pinchart
2018-09-18 19:58 ` Arnaldo Carvalho de Melo
2018-09-19 11:28 ` James Bottomley
2018-09-19 11:37 ` Mauro Carvalho Chehab
2018-09-19 12:03 ` Mauro Carvalho Chehab
2018-09-19 14:16 ` James Bottomley
2018-09-19 16:06 ` Mauro Carvalho Chehab
2018-09-19 19:55 ` Mauro Carvalho Chehab
2018-09-19 20:10 ` Luck, Tony
2018-09-19 23:28 ` Mauro Carvalho Chehab
2018-09-19 23:45 ` Tim.Bird
2018-09-19 20:23 ` Dave Airlie
2018-09-20 0:01 ` Mauro Carvalho Chehab
2018-09-20 0:22 ` Tim.Bird
2018-09-20 6:33 ` Jani Nikula
2018-09-20 7:01 ` Josh Triplett
2018-09-20 7:11 ` Daniel Vetter
2018-09-20 7:04 ` David Woodhouse
2018-09-24 13:53 ` Mel Gorman
2018-09-25 5:45 ` Leon Romanovsky
2018-09-20 10:19 ` Laurent Pinchart
2018-09-20 10:23 ` Mauro Carvalho Chehab
2018-09-20 12:31 ` Jani Nikula
2018-09-20 13:04 ` Mauro Carvalho Chehab
2018-09-20 13:49 ` Tim.Bird
2018-09-20 13:55 ` Laurent Pinchart
2018-09-20 19:14 ` Tim.Bird
2018-09-20 19:55 ` Laurent Pinchart
2018-09-20 20:11 ` Dmitry Torokhov
2018-09-20 20:14 ` Jonathan Corbet
2018-09-20 20:52 ` Mauro Carvalho Chehab
2018-09-20 2:44 ` Joe Perches
2018-09-20 11:11 ` Laurent Pinchart
2018-09-20 13:35 ` Joe Perches
2018-09-20 3:38 ` Stephen Hemminger
2018-09-20 12:28 ` Eric W. Biederman
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='CAMuHMdXnNVt8bvywgZQmMaAt8=Qy=6z7PQa4xsM-2h_Ymo3fwQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=daniel.vetter@ffwll.ch \
--cc=ksummit-discuss@lists.linuxfoundation.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