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 522D8B88 for ; Thu, 20 Apr 2017 11:25:50 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [65.50.211.133]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A7CE3106 for ; Thu, 20 Apr 2017 11:25:49 +0000 (UTC) Date: Thu, 20 Apr 2017 08:25:35 -0300 From: Mauro Carvalho Chehab To: Jonathan Corbet Message-ID: <20170420082535.18dc0607@vento.lan> In-Reply-To: <20170419163636.6747a232@lwn.net> References: <20170418181506.30de0470@vento.lan> <20170419163636.6747a232@lwn.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ksummit , Greg Kroah-Hartman , Ingo Molnar , Dave Airlie , Doug Ledford , David Miller Subject: Re: [Ksummit-discuss] "Maintainer summit" invitation discussion List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Em Wed, 19 Apr 2017 16:36:36 -0600 Jonathan Corbet escreveu: > On Tue, 18 Apr 2017 18:15:06 -0300 > Mauro Carvalho Chehab wrote: > > > There is one particular issue that occurs to me, although I'm not sure > > if it would fit on the new "maintainer summit" format: it is related > > to how to group documentation. Also, this is actually Jon's call, but > > I suspect that he may want to hear comments from the others. > > I could imagine talking about a few documentation issues, including > interactions with the rest of the kernel. Who has responsibility for > taking docs patches is often not clear, leading to multiple maintainers > picking them up or conflicts between trees. I suspect that conflicts are hard to avoid, as often patch series need to touch both code and Documentation/. I guess keeping the MAINTAINERS updated to reflect who is responsible for each file under Documentation is one important step to minimize conflicts. Btw, that's one of the reasons why I believe that one book per subsystem would work better than spreading the subsystem documentation among several different books: once such book is added at the main Documentation/index.rst and Documentation/conf.py, the subsystem maintainer can take care of all documentation patches for such book without risking to cause conflicts with other trees. Thanks, Mauro