linux-kernel - [ATTEND] Discussion: role of the maintainer?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 16 Jun 2012 19:31:19 +0000
From:	"Myklebust, Trond" <Trond.Myklebust@...app.com>
To:	"ksummit-2012-discuss@...ts.linux-foundation.org" 
	<ksummit-2012-discuss@...ts.linux-foundation.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: [ATTEND] Discussion: role of the maintainer?

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?

Cheers
  Trond

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@...app.com
www.netapp.com