Created: 2006-05-27
Contributors: RaphaelHertzog
RaphaelHertzog: if you edit this page to add comments, please sign your comment. Place your comment as sub-list-items if you respond to a point. You can add new signed top-level entries if needed. I'll try to make it evolve according to comments (and still keep it coherent), don't rework it completely on your own. Feel free to join #debian-newmaint on irc.debian.org to discuss with me and other interested people.
Contents
Summary
This specification aims to design a new process for accepting new members in the Debian project.
Rationale
The NM process is working well to select technically good people who are packagers and who are heavily involved in Debian. But it's clearly suboptimal for all other kinds of contributors that deserve to be part of our project. The DM concept has introduced a new way to contribute. It looks like many DD felt it was wrong to create DM completely disconnected from NM.
Thus this is an attempt to supersede the NM process by a more generic "membership" process which includes the process to become a DD and much more.
We don't want to micro-manage every implementation details but we want to give clear guidelines and setup the basic building blocks required for this improved process.
-- I disagree with the statement that "The NM process is clearly suboptimal". This either needs to be backed up (and I don't see any ground for such a strong statement), or the introduction needs to be rewritten to make clear why we need NM v2, or something to supplement NM. -- ChristophBerg 2007-08-18
-- I rewrote the paragraph to make it clearer. The suboptimal was considering other kind of contributors, I'm happy with the NM process for selecting DD as it is. But I disliked the DD or nothing approach we had up to now. -- RaphaelHertzog 2007-08-19
Use Cases
- Bob likes Debian and wants to be somewhat involved. He has the time and the skills to maintain some simple packages but not much more.
- Alice is the upstream author of package X and wants to maintain it within Debian, because she uses Debian and she's sad to see her package neglected within Debian. She doesn't want to be DD.
- John creates nice artwork and contributes them regularly to Debian. He would like a bit more recognition for his work.
- Frédéric contributes to the French translation team. He would like more recognition for his work.
- Yves-Alexis is NM waiting for the DAM to create his account. He's been involved for a long time and would like to be full DD.
Design
- This project is presented as a "redesign from scratch" project but the NM process is not so bad for creating DD so we'll try to only "fix it". It sucks the most at the DAM/keyring maint level and that's precisely a part that need redesigning anyway (for handling the new kinds of contributors).
- We're only used to handle packaging contributions and I doubt we'll be able to come up with precise checks that allow non-packaging contributors to become project members. This will require "human evaluation". Somewhat like the evaluation done by the community council on the Ubuntu project (but done in a less superficial manner I hope).
- We need to come up with guidelines that should apply to all "project members" and then with specifics for each category of contributors.
Categorization of contributors
Let's define what's common to all contributors (and what want to be common) and what's specific to each category.
Common guidelines
- Every (technically) good contribution should be accepted.
- Anyone who wants to be member should abide by our foundation documents and our internal rules.
- New contributors can't be project members before at least one year of regular contribution.
- Contributors who want to be members will have to request it. Being contributor doesn't imply automatic membership.
- General membership implies: @debian.org email, right to vote.
What about access to internal mailing lists, i.e. debian-private? Just for DDs? -- FranzPletz
- More rights can be granted depending on the work that the contributor is doing.
- All contributors and members are required to subscribe to debian-devel-announce.
Definition of developers (DD)
- They are the core of Debian, they have control over the evolution of the distribution.
- They have the right to upload all packages (NMU).
- Most power positions (ftpmasters, policy editors, DSA, Security, DPL, ...) are handled by members of this group.
- We have very high standards (technical and social) for those people. The current NM process reflects that.
- Any contributor can try to become DD after 6 months of regular contributions. He might fail and still continue contributing.
How? What makes a contributor qualified to become a DD? (will also think about that) -- FranzPletz
Definition of maintainers (DM)
- They care only about a handful of packages.
- They care about the quality of their packages and want them to be well integrated in Debian.
- They are the work-force that let Debian have a so large set of packages and still have a very good consistency and quality.
- They have to be granted upload rights for the packages that they maintain.
Definition of artists
- They work to improve the visual appeal of our distribution. It might concern packages (themes, etc.) but it might concern our website too.
Definition of translators
- They help localize our distribution.
Definition of documentation writers
- They help writing good documentation.
- They can be granted upload rights on documentation packages (following the same procedure than DM).
Processes
Let's try to define what processes are needed.
Becoming member (common to all categories)
- The candidate needs to be already a contributor.
- The "Membership Committee" decides based on its history of contributions and its social behaviour.
Becoming developer
Becoming maintainer
- To become DM, one has to maintain a package, have it sponsored by DD and have the sponsors recommend him to the "Membership Committee". They'll be granted the right to upload that package without review from a DD.
Becoming artist
Becoming translator
Becoming documentation writer
Implementation
- Nothing yet.
Outstanding Issues
Too many to be listed. Feel free to start.