ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Dave Airlie <airlied@gmail.com>
Cc: ksummit <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 09:43:32 -0400	[thread overview]
Message-ID: <20180918094332.2c0d066a@gandalf.local.home> (raw)
In-Reply-To: <CAPM=9tz6_byufs2xdOmU73VPVU2ojb=Ox0YzQxFpOs7jztjbFg@mail.gmail.com>

On Tue, 18 Sep 2018 15:55:23 +1000
Dave Airlie <airlied@gmail.com> wrote:

> I think there might be place for a report from the people who did sign
> off the CoC about the thoughts/process involved in updating it (and/or
> urgency) to the rest of the Maintainer group.
> 
> Now I understand that having a public talk about such a thing will
> likely descend into farce, there may be scope for something of a
> Chatham House Rule style meeting, or just a non-recorded, non-public
> session like we've done for sensitive subjects are previous kernel
> summits.

I believe this topic merits a discussion at Maintainer's Summit. It can
probably be much more productive face to face with several maintainers
in one room than what would result in a mailing list (both public and
private) discussion.

I'm willing to lead this if nobody else wants to do it.

  (I don't know why I do this to myself)


> 
> It might just be a readout from a similar meeting at Edinburgh summit
> (maybe someone else can propose that), or maybe some sort of Q&A
> session. Maybe Linus could record a piece to camera for the
> maintainers that can't make Edinburgh, but would still like to
> understand where everything currently sits. Said piece would of course
> be burned afterwards.

I would like to get an honest opinion from everyone involved, and
remove any of the ambiguities that people still have.

> 
> After the past 2-3 days I get the feeling there are maintainers unsure
> about how this affects them and I think assuaging those fears might be
> a good thing.

Agreed.

> 
> I'm also equally happy nailing the lid back on the can of worms and
> never discussing it again.

No no, the can is now open and you have released the worms ;-)

-- Steve

  reply	other threads:[~2018-09-18 13:43 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 [this message]
2018-09-18 14:34   ` Daniel Vetter
2018-09-18 14:58     ` Geert Uytterhoeven
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=20180918094332.2c0d066a@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=airlied@gmail.com \
    --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