1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
|
#use wml::debian::template title="Checklist for Application Managers"
#use wml::debian::translation-check translation="5011f532637dc7820b79b151eecfda4ab65aa22f" maintainer="galaxico"
<p>
<b>Note:</b> The <a href="https://wiki.debian.org/FrontDesk/AMTutorial">AM
Tutorial</a> wiki page is more up to date than this page.
</p>
<p>This checklist only covers the most important areas of the NM checks.
Depending on the <a href="./newmaint#Applicant">Applicant's</a>
background and plans in the project, an <a href="./newmaint#AppMan">\
Application Manager</a> may choose to ignore some of the things
listed here or to add others.</p>
<p>Also see the <a href="nm-amhowto">Mini-HOWTO for Application
Managers</a>.</p>
<h3><a name="identification">Identification Check</a></h3>
<p>The <a href="./newmaint#Applicant">Applicant</a> has to have
an OpenPGP public key signed by at least one <a href="./newmaint#Member">\
Debian member</a>. If possible, at least one other signature
from a well-connected OpenPGP key is also required. Always
use <tt>gpg --check-sigs</tt>, not <tt>gpg --list-sigs</tt> to verify
an Applicant's identity.</p>
<p>The OpenPGP key that will go to the Debian Keyring needs to be
a version 4 key. To check this, get the fingerprint of the key
and check if it's either 32 or 40 hexadecimal digits long. Version 3
keys have only 32 digits, version 4 have 40 digits. This key
doesn't have to be the same as the one that is used to verify the
Applicant's identity.</p>
<p>Applicants <em>must</em> have an encryption key. Check this by
running <tt>gpg --list-keys <var><KeyID></var></tt>.
If the output doesn't contain a line with either
<tt><var><Number></var>E/<var><KeyID></var></tt> or
<tt><var><Number></var>g/<var><KeyID></var></tt>, the
Applicant needs to add an encryption subkey.</p>
<p>If the <a href="./newmaint#Applicant">Applicant</a> can't
provide a signed key, a government-issued photo ID can be used for
identification. Please contact the <a href="./newmaint#FrontDesk">\
Front Desk</a> in such cases.</p>
<p>Additional verification options can be used if there is some
doubt about the identity of the Applicant:</p>
<ul>
<li>If the Applicant is a student, someone at their university can
confirm their identify. This person should also be listed on the
webpages of the university staff.</li>
<li>If the Applicant works in a bigger company, their employer should
be able to confirm their identity.</li>
<li>There are websites that can do reverse lookups for telephone
numbers, though this normally doesn't work for mobile phones.
The number the Applicant provides should either resolve to their
own name or the person answering the phone should be able to
confirm the Applicant's identity.</li>
</ul>
<h3><a name="pandp">Philosophy and Procedures</a></h3>
<p>There are no fixed rules for this part, but some areas should
always be covered (and it is recommended to discuss the
others):</p>
<ul>
<li>Applicants have to agree to uphold the <a
href="$(DOC)/debian-policy/">Debian Policy</a> and the <a
href="$(DEVEL)/dmup">Debian Machine Usage Policy (DMUP)</a>.</li>
<li>Applicants need to agree to the <a href="$(HOME)/social_contract">\
Social Contract</a> and must be able to explain how Debian
relates to the Free Software Community.</li>
<li>Applicants must have a good understanding of the <a
href="$(HOME)/social_contract#guidelines">Debian Free Software
Guidelines</a>. They need to be able to decide if a license is free
or not and should have a strong opinion about Free Software.</li>
<li>Applicants have to understand how the Debian Bug Tracking
System works, what information Debian keeps in there (pseudo-packages,
wnpp, ...) and how they can manipulate it.</li>
<li>Applicants should know about Debian QA processes (orphaning,
removing, NMUing and QA uploads).</li>
<li>Applicants should understand the Debian release process.</li>
<li>Applicants should know Debian's l10n and i18n efforts and what
they can do to help them.</li>
</ul>
<h3><a name="tands">Tasks and Skills</a></h3>
<p>What needs to be covered by the T&S checks depends on the
area the Applicant wishes to work in:</p>
<ul>
<li>Applicants aiming to work as packager <em>must</em> have at least
one package in the archive. The package should have enough users
to provide a basis for documentation of the Applicant's packaging
skills and their way of dealing with users, bug submitters and bugs.
<br />
Further questions should also cover some basic aspects of Debian
packaging (conffiles, menus, init scripts, sub-policies, porting,
complex dependencies).</li>
<li>Applicants planning to write documentation must have already
provided examples of their work. They should also have a clear vision
on what kind of documents they want to work on in the future.</li>
</ul>
<h3><a name="finalreport">Final Application Report to the Debian
Account Manager</a></h3>
<p>After all checks are finished and the AM is satisfied with the
Applicant's performance, a report should be submitted to the Debian
Account Manager and the New Member Front Desk. It should
document what was done to satisfy the different parts of the New
Member checks and also contain all information collected
about the Applicant.</p>
<p>The email should be directed at <da-manager@debian.org> and
<nm@debian.org> and contain the following
things:</p>
<ul>
<li>A short overview about the application, containing some basic
information about the Applicant.</li>
<li>The account name the Applicant requested. It should be at least
3 characters long.</li>
<li>The email address to which all mail directed at
<var><account></var>@debian.org should be forwarded.</li>
<li>The fingerprint of the Applicant's OpenPGP public key that should be incorporated
into the Debian Keyring.</li>
<li>An gzipped mbox with logs of all discussion between the Application Manager
and the Applicant about the application.</li>
</ul>
<p>This completes the Application Manager's responsibilities in the
application process. The New Member Front Desk and the Account
Manager will check and judge the application report.</p>
<hr />
<a href="newmaint">Back to the New Members Corner</a>
|
