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 A2996FF9 for ; Thu, 20 Sep 2018 19:14:36 +0000 (UTC) Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0107.outbound.protection.outlook.com [104.47.40.107]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 53984798 for ; Thu, 20 Sep 2018 19:14:34 +0000 (UTC) From: To: , Date: Thu, 20 Sep 2018 19:14:31 +0000 Message-ID: References: <20180920072351.49c41618@coco.lan> <2153698.dD80FJtCWu@avalon> In-Reply-To: <2153698.dD80FJtCWu@avalon> Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: mchehab+samsung@kernel.org, James.Bottomley@hansenpartnership.com 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: , > -----Original Message----- > From: Laurent Pinchart=20 > 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. >=20 > 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. >=20 > 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 directi= ons. > 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 o= ut 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. -- Tim