<para>
Firstly, subscribe to &email-debian-devel; if you haven't
already. Send the word <literal>subscribe</literal> in the
-<emphasis>Subject</emphasis> of an email to
+<literal>Subject</literal> of an email to
&email-debian-devel-req;. In case of problems, contact the
list administrator at &email-listmaster;. More information on
-available mailing lists can be found in <xref linkend="mailing-lists"/> .
+available mailing lists can be found in <xref linkend="mailing-lists"/>.
&email-debian-devel-announce; is another list which is
mandatory for anyone who wishes to follow Debian's development.
</para>
Another good list to subscribe to is &email-debian-mentors;.
See <xref linkend="mentors"/> for details. The IRC channel
<literal>#debian</literal> can also be helpful; see <xref
-linkend="irc-channels"/> .
+linkend="irc-channels"/>.
</para>
<para>
When you know how you want to contribute to &debian-formal;,
</para>
<para>
If you wish to be a mentor and/or sponsor, more information is available in
-<xref linkend="newmaint"/> .
+<xref linkend="newmaint"/>.
</para>
</section>
linkend="key-maint"/> for more information on maintaining your public key.
</para>
<para>
-Debian uses the <command>GNU Privacy Guard</command> (package <systemitem
+Debian uses the <literal>GNU Privacy Guard</literal> (package <systemitem
role="package">gnupg</systemitem> version 1 or better) as its baseline
standard. You can use some other implementation of OpenPGP as well. Note that
OpenPGP is an open standard based on <ulink
<para>
You need a version 4 key for use in Debian Development. Your key length must
be at least 1024 bits; there is no reason to use a smaller key, and doing so
-would be much less secure.
<footnote><para> Version 4 keys are keys conforming
+would be much less secure.<footnote><para> Version 4 keys are keys conforming
to the OpenPGP standard as defined in RFC 2440. Version 4 is the key type that
has always been created when using GnuPG. PGP versions since 5.x also could
-create v4 keys, the other choice having beein pgp 2.6.x compatible v3 keys
+create v4 keys, the other choice having been pgp 2.6.x compatible v3 keys
(also called legacy RSA by PGP). </para> <para> Version 4 (primary) keys can
either use the RSA or the DSA algorithms, so this has nothing to do with
GnuPG's question about which kind of key do you want: (1) DSA and Elgamal, (2)
requirements just pick the default. </para> <para> The easiest way to tell
whether an existing key is a v4 key or a v3 (or v2) key is to look at the
fingerprint: Fingerprints of version 4 keys are the SHA-1 hash of some key
-matieral, so they are 40 hex digits, usually grouped in blocks of 4.
+material, so they are 40 hex digits, usually grouped in blocks of 4.
Fingerprints of older key format versions used MD5 and are generally shown in
blocks of 2 hex digits. For example if your fingerprint looks like
<literal>5B00 C96D 5D54 AEE1 206B AF84 DE7A AF6E 94C0 9C7F</literal>
</para>
<para>
To apply as a new maintainer, you need an existing Debian Developer to support
-your application (an <emphasis>advocate</emphasis>). After you have
+your application (an <literal>advocate</literal>). After you have
contributed to Debian for a while, and you want to apply to become a registered
developer, an existing developer with whom you have worked over the past months
has to express their belief that you can contribute to Debian successfully.
~ianmdlvl / developers-reference.git / blobdiff