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

Guenter Roeck linux at roeck-us.net
Sun Jun 17 01:13:21 UTC 2012

On Sat, Jun 16, 2012 at 07:31:19PM +0000, Myklebust, Trond wrote:
> Hi,
> This is a spin off from the discussion topic that was started by Thomas
> Gleixner. I'd like to turn this into a full discussion on the role of
> the Linux Maintainer.
> Currently, the Linux maintainer appears to be responsible for filling
> all of the traditional roles of software architect, software developer,
> patch reviewer, patch committer, and software maintainer.
> 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?
> 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?
Having more than one maintainer works well for the hwmon subsystem. It is a good
way to "train" new maintainers.

I don't like the idea of formalizing maintainer's responsibilities, and I don't
see the need to do it. It should be up to the maintainers to decide and work out
which role to take; there are multiple ways to split the work, roles may change
over time, and the maintainers are the best to decide what their role should be.

And when it comes to architects, my personal opinion is that every architect
should also implement code, to not forget what it actually takes to do it.


More information about the Ksummit-2012-discuss mailing list