[Ksummit-discuss] Maintainer's Summit Agenda Planning

Josh Poimboeuf jpoimboe at redhat.com
Fri Oct 6 16:51:36 UTC 2017

On Fri, Oct 06, 2017 at 10:32:59AM -0600, Jonathan Corbet wrote:
> On Fri, 6 Oct 2017 11:26:21 -0500
> Josh Poimboeuf <jpoimboe at redhat.com> 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.

Ah, nice.

> The tricky part, of course, is finding a way to document the consensus on
> best practices without trying to "drive" it too hard.

We somehow manage to get consensus on millions of lines of code, you'd
think we could figure out how to agree on a small process document ;-)

But seriously, I think even parts which are disagreed upon, or which are
up to the maintainer's judgement, can be documented as such.

I wonder if a maintainers mailing list would help for such discussions,
if we don't already have one.

> 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.



More information about the Ksummit-discuss mailing list