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
| ||
|
Date: Wed, 14 Nov 2018 20:53:13 -0800 From: Dan Williams <dan.j.williams@...el.com> To: linux-kernel@...r.kernel.org Cc: Mauro Carvalho Chehab <mchehab@...nel.org>, Dave Jiang <dave.jiang@...el.com>, Daniel Vetter <daniel.vetter@...ll.ch>, Linus Torvalds <torvalds@...ux-foundation.org>, Dmitry Vyukov <dvyukov@...gle.com>, Vishal Verma <vishal.l.verma@...el.com>, Jonathan Corbet <corbet@....net>, Thomas Gleixner <tglx@...utronix.de>, Ross Zwisler <zwisler@...nel.org>, Joe Perches <joe@...ches.com>, "Tobin C. Harding" <me@...in.cc>, "Martin K. Petersen" <martin.petersen@...cle.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Steve French <stfrench@...rosoft.com>, Olof Johansson <olof@...om.net>, corbet@....net, linux-nvdimm@...ts.01.org, ksummit-discuss@...ts.linuxfoundation.org Subject: [RFC PATCH 0/3] Maintainer Handbook: Subsystem Profile At a recently concluded session at the Linux Plumbers Conference I proposed a "Subsystem Profile" as a document that a maintainer can provide to set contributor expectations and provide fodder for a discussion between maintainers about the merits of different maintainer policies. For those that did not attend, the goal of the Subsystem Profile, and the Maintainer Handbook more generally, is to provide a desk reference for maintainers both new and experienced. The session introduction was: The first rule of kernel maintenance is that there are no hard and fast rules. That state of affairs is both a blessing and a curse. It has served the community well to be adaptable to the different people and different problem spaces that inhabit the kernel community. However, that variability also leads to inconsistent experiences for contributors, little to no guidance for new contributors, and unnecessary stress on current maintainers. There are quite a few of people who have been around long enough to make enough mistakes that they have gained some hard earned proficiency. However if the kernel community expects to keep growing it needs to be able both scale the maintainers it has and ramp new ones without necessarily let them make a decades worth of mistakes to learn the ropes. To be clear, the proposed document does not impose or suggest new rules. Instead it provides an outlet to document the unwritten rules and policies in effect for each subsystem, and that each subsystem might decide differently for whatever reason. --- Dan Williams (3): MAINTAINERS: Reclaim the P: tag for Subsystem Profile MAINTAINERS, Handbook: Subsystem Profile libnvdimm, MAINTAINERS: Subsystem Profile Documentation/maintainer/index.rst | 1 Documentation/maintainer/subsystem-profile.rst | 145 ++++++++++++++++++++++++ Documentation/nvdimm/subsystem-profile.rst | 86 ++++++++++++++ MAINTAINERS | 26 +++- 4 files changed, 249 insertions(+), 9 deletions(-) create mode 100644 Documentation/maintainer/subsystem-profile.rst create mode 100644 Documentation/nvdimm/subsystem-profile.rst
Powered by blists - more mailing lists