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 0BE38D4D for ; Tue, 11 Sep 2018 08:41:40 +0000 (UTC) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F3D5D8D for ; Tue, 11 Sep 2018 08:41:38 +0000 (UTC) From: Jani Nikula To: Jiri Kosina , James Bottomley In-Reply-To: References: <1536592110.4035.5.camel@HansenPartnership.com> Date: Tue, 11 Sep 2018 11:41:39 +0300 Message-ID: <87a7oo2zp8.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Cc: ksummit Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 10 Sep 2018, Jiri Kosina wrote: > On Mon, 10 Sep 2018, James Bottomley wrote: > >> 1. How do reviews happen? Non email projects tend to have only one >> review mechanism (gerrit, github, gitlab, etc.) and stick to it. Do >> we want to pick a technology or allow multiple? I don't think this >> is kernel wide, it could be a sybsystem choice. > > Yeah, but OTOH even now I've heard a lot of feedback about the irregular > contributors / newcomers being confused by different subsystems having > different processess and requirements; and those are basically just rather > "minor" things currently (bugzilla usage, patchwork usage, subscriber-only > mailinglists, etc), but it's still enough to confuse the hell out of > people. MAINTAINERS is supposed to be the central database about all this. IMO maintainers should be more active in getting their data updated. We have folks who don't document their preferences or expectations, at all, and then go on to rant at random contributors about how their corner of the kernel community is supposed to operate. For example, that they never look at bugzilla etc. If the current entries don't cover everything, one can use W: to add a link to more details, or we can add new entries. And that's just the obvious prerequisite to actively telling contributors to look at MAINTAINERS. BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center