Debian New Maintainer Process: History and Aims
Hanna Wallach, Dafydd Harries, Moray Allan
This paper/talk is aimed especially at Debian New Maintainer Process applicants and those considering applying, but it is relevant to all those interested in how Debian admits new developers. Since the process
is in a better state than it has been for some time, we suggest standing back from it to see how it has developed over the years, and to think about what its overall aims should be.
We intend to structure the DebConf session into three parts:
1. History of NM
2. How NM works today, including "What an AM really wants to see"
1. History of NM
The Debian New Maintainer process forms a key part of Debian's social and organisational structure. Debian has a very large body of volunteer developers, and for some years has been running the NM process as a formal procedure to induct new developers into the organisation. The process is unique to Debian, and widely considered to be a significant contributory factor in Debian's reputation for technical excellence and consistency across the whole distribution.
At the same time, many people outside the project see the NM process as a negative barrier to joining Debian. Some who get as far as applying to the process get bogged down when they receive their first communications from their Application Manager. We suggest that both these problems are often due to false perceptions of the process, for example in misunderstanding the quality of response that application managers expect from their applicants.
We describe how the NM process evolved over the years, describing why the various tests are now used. Most potential applicants only know about the current form of the NM process, without knowing why it has developed to this state: having this history available to them will let applicants understand why they are being asked to do the things they are during the NM process.
The history of the NM process also clarifies discussion about the aims of the current NM process for those inside Debian, by reminding us why the various requirements were originally introduced.
2. How NM works today
2.1. Applicant's view
We briefly summarise the current NM process from an applicant's point of
2.2. People involved
We describe the NM process from the point of view of those running it, by showing the relationships between those performing the various organisational tasks.
Statistics for recent applications / acceptances / rejections.
2.4. What an Application Manager really wants to see
What is an Application Manager really looking for in applicants? Many applicants seem unclear, but this is not intended to be secret information.
Some tentative conclusions can be drawn about the NM process in view of its history.
Overall, the process is working well, with the number of applicants waiting for people other than themselves currently going down.
There is always a tendency towards making the process more complex and adding further requirements on applicants. It's good if this means that we get better trained developers out of the process, but it's bad if it discourages people from applying or from seeing the process through.
Hanna Wallach recently began maintaining several Debian packages, and is currently in the NM process.
Dafydd Harries completed the NM process in December, and is currently waiting for account creation.
Moray Allan went through the NM process in 2003, and has been an Application Manager since April 2004.