Re: [Ksummit-discuss] [CORE TOPIC] [nomination] Move Fast and Oops Things

[Dan Carpenter <dan.carpenter@oracle.com>]

On Fri, May 16, 2014 at 10:09:51AM -0700, Andy Grover wrote:
> * If the maintainer is unresponsive, what recourse does a submitter
> have? (Is this written down somewhere?) Is taking recourse actually
> culturally acceptable? How would the gone-around maintainer treat
> future submissions?

You ping the maintainer after a month of no response.  If there is still
no response after month two then you try to send it through Andrew.

If the maintainer responds but requests changes then you have to do what
he says.  If the maintainer responds but just NAKs your patch, then
you're pretty much screwed.  If you really care, then you have to carry
those patches out of tree.

> 
> * At what point does it make sense to field a sub- or co-maintainer?

I don't maintain a git tree but the mechanical bit don't seem that hard
to me.  It's reviewing the code which is tricky.  All patches should be
going to a list (LKML doesn't count) so anyone can help review patches.

But how to get people to review each other's patches?

regards,
dan carpenter