[Ksummit-2012-discuss] [ATTEND] Discussion: role of the maintainer?

Mark Brown broonie at opensource.wolfsonmicro.com
Sun Jun 17 17:54:06 UTC 2012

On Sat, Jun 16, 2012 at 07:31:19PM +0000, Myklebust, Trond wrote:

> My question is whether or not there might be some value in splitting out
> some of these roles, so that we can assign them to different people, and
> thus help to address the scalability issues that Thomas raised? For
> instance, would it be useful to have a separate 'software maintainer'
> role for dealing with post-merge issues, such as ensuring that bugs and
> regressions get fixed by someone?

I mostly agree with Guenter's comments on this, I think that overall
it's much better to give people permission to do more (which naturally
takes off a bit of the load) and let things flow than to try anything

> If so, how do we ensure that people get credit for the roles that they
> assume? Should we perhaps add additional entries to the MAINTAINERS file
> for some of these responsibilities?

I do sometimes find myself wishing there were more postive things I
could do to say "X is doing an awesome job, you should pay attention to
them/do things like they do/whatever", doing that and saying things
directly to people is good but it's not as discoverable for new
contributors as it might be.  I'm all out of useful ideas for how to do
that, though.

More information about the Ksummit-2012-discuss mailing list