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 D900DA71 for ; Fri, 6 Oct 2017 16:33:01 +0000 (UTC) Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A020D48C for ; Fri, 6 Oct 2017 16:33:01 +0000 (UTC) Date: Fri, 6 Oct 2017 10:32:59 -0600 From: Jonathan Corbet To: Josh Poimboeuf Message-ID: <20171006103259.78ab2508@lwn.net> In-Reply-To: <20171006162621.aeauqeih7uner5wp@treble> References: <20171005192002.hxbjjdjhrfa4oa37@thunk.org> <1507303665.3104.13.camel@HansenPartnership.com> <20171006162621.aeauqeih7uner5wp@treble> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Cc: James Bottomley , ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] Maintainer's Summit Agenda Planning List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 6 Oct 2017 11:26:21 -0500 Josh Poimboeuf wrote: > I think it would be a good idea to have a Maintainer's Guide which tries > to document a lot of this knowledge. It would help new maintainers > learn the ropes, and would also help drive consensus for maintainer's > best practices. It could document the typical processes of a > maintainer, and policy guidelines like some of the above topics. Strangely enough, this is a conversation that has been popping up in other contexts too. We may see an initial attempt before too long. The tricky part, of course, is finding a way to document the consensus on best practices without trying to "drive" it too hard. My own thought is that a good starting place might be a "how to avoid getting your pull request flamed" document, since there is some semblance of a consensus there and it's a place where people often make mistakes. jon