ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Tim.Bird@sony.com, ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC FOR KS] CoC and Linus position (perhaps undocumented/closed/limited/invite session)
Date: Thu, 20 Sep 2018 13:11:21 -0700	[thread overview]
Message-ID: <CAKdAkRR9ON=GkCKRTa51WBEAuH6cuWsJPsfMyLx5X22Wc=_w+w@mail.gmail.com> (raw)
In-Reply-To: <12303202.TmDbdoTgoG@avalon>

On Thu, Sep 20, 2018 at 12:55 PM Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
>
> Hi Tim,
>
> On Thursday, 20 September 2018 22:14:31 EEST Tim.Bird@sony.com wrote:
> > From: Laurent Pinchart
> > > On Thursday, 20 September 2018 16:49:40 EEST Tim.Bird@sony.com wrote:
> > ...
> >
> > >> The TAB is working out the details of enforcement policy, and a FAQ to go
> > >> along with the CoC, that we plan to present at the Maintainers Summit.
> > >
> > > May I suggest a (public) forum where everybody could post their concerns ?
> > > One big concern is that the new code of conduct was dumped on the
> > > community without much warning, dumping a FAQ the same way without
> > > consulting the user base could produce a similar feeling.
> > >
> > > Discussing the FAQ in public would be best but I understand that would be
> > > difficult as it would very well quickly go in all kinds of random
> > > directions. A way to report our concerns and feel heard would in my
> > > opinion be a good middle ground.
> >
> > I think having something to discuss before the Maintainers Summit
> > would be a good idea.  My hope is that a FAQ would give the perspective
> > of the TAB members on what appear to be the "hot issues" with this change,
> > without leading to endless wrangling or bike-shedding.
> >
> > I have found people's input on this list to be extremely valuable to find
> > out concerns and possible remedies, but this is not the only forum.  (It's
> > just more tractable than following LKML, for me, at least.)  But I'd be
> > open to other venues.
>
> There has been some useful feedback, but I've found the silence on the mailing
> list pretty deafening compared to the importance of the announcement. It
> screams of private conversations, and I feel some reluctance to speak
> publicly, possibly due to the uncertainty of what will happen now. After the
> Bastille fell, it was wise not to speak out before knowing what the new power
> to be would consider appropriate. Having an official forum to report
> questions, doubts, fears and other feelings (I would say concrete proposals
> too, but that could turn into a bit of a bikeshedding chaos) to help making
> sure the FAQ will address the questions of the community - and not the
> questions that the TAB believes are the important ones, even if the TAB tries
> to do its best - would in my opinion be useful. It could be the ksummit-
> discuss mailing list, I just feel that some sort of green light is needed. I
> might be too optimistic though.
>
> To lead by example, I'll ask a question of mines. Since Linus' announcement
> that took many people by surprise (obviously not everybody as the code of
> conduct patch was signed by several TAB members, but by no means by a vast
> majority of the community), all sort of discussions took place in private, and
> rumours have started spreading regarding the events that led to this
> situation. I believe I'm not the only one who would like to be informed about
> the history of this unusual development. While I understand that not all
> information can (or should) always be disclosed, this isn't a case of
> voyeurism, some sort of official story would in my opinion help giving
> cohesion to the Linux kernel community.

I also would like to know how this code of conduct was adopted. The
previous "code of conflict" was at least somewhat circulated among
maintainers, this came out of the blue, at least for me.

Thanks.

-- 
Dmitry

  reply	other threads:[~2018-09-20 20:11 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
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 [this message]
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='CAKdAkRR9ON=GkCKRTa51WBEAuH6cuWsJPsfMyLx5X22Wc=_w+w@mail.gmail.com' \
    --to=dmitry.torokhov@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=Tim.Bird@sony.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=mchehab+samsung@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