From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AA22F10AA for ; Thu, 20 Sep 2018 20:11:37 +0000 (UTC) Received: from mail-lj1-f195.google.com (mail-lj1-f195.google.com [209.85.208.195]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 02552F8 for ; Thu, 20 Sep 2018 20:11:35 +0000 (UTC) Received: by mail-lj1-f195.google.com with SMTP id j19-v6so9565658ljc.7 for ; Thu, 20 Sep 2018 13:11:35 -0700 (PDT) MIME-Version: 1.0 References: <2153698.dD80FJtCWu@avalon> <12303202.TmDbdoTgoG@avalon> In-Reply-To: <12303202.TmDbdoTgoG@avalon> From: Dmitry Torokhov Date: Thu, 20 Sep 2018 13:11:21 -0700 Message-ID: To: Laurent Pinchart Content-Type: text/plain; charset="UTF-8" Cc: Mauro Carvalho Chehab , James Bottomley , 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) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Sep 20, 2018 at 12:55 PM Laurent Pinchart 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