[Ksummit-discuss] [TOPIC] Guidance for subsystem maintainers

[Jiri Kosina]

On Tue, 13 May 2014, josh at joshtriplett.org wrote:

> 2) We could improve the experience for patch submitters without
> necessarily pushing changes to maintainer workflows.  I wonder if we
> could do a better job of providing automated tools that make life easier
> for maintainers and patch submitters?  For instance, what about having
> easy-to-enable git hooks on git.kernel.org similar to those Andrew and
> Greg use, notifying the patch submitter when a maintainer merges their
> patch?  Maintainers could opt into those hooks specifically for
> whichever repository has their "will go upstream eventually" branches,
> and supply a short description of where patches typically flow from
> their tree so submitters know what to expect.
> 
> Would that be useful?  Would maintainers want it?  What properties would
> it need to have?  Could kernel.org support that?  And would anyone be
> interested in helping to write it?  (I'm willing to help, given answers
> to those questions to make sure it'll actually get *used*.)

Good idea! I'd actually be very happy user of facility if it's provided by 
kernel.org.

Specifying a regexp on a branch name for which the automated e-mails 
should be sent out would suit my needs completely.

Thanks,

-- 
Jiri Kosina
SUSE Labs