<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
- <!ENTITY % commondata SYSTEM "common.ent" > %commondata;
+ <!ENTITY % commondata SYSTEM "common.ent" > %commondata;
]>
<chapter id="resources">
<title>Resources for Debian Developers</title>
<para>
Much of the conversation between Debian developers (and users) is managed
through a wide array of mailing lists we host at <literal><ulink
-url="http://&lists-host;/">&lists-host;</ulink></literal>. To find out
-more on how to subscribe or unsubscribe, how to post and how not to post, where
-to find old posts and how to search them, how to contact the list maintainers
-and see various other information about the mailing lists, please read <ulink
-url="&url-debian-lists;"></ulink>. This section will only
-cover aspects of mailing lists that are of particular interest to developers.
+url="http://&lists-host;/">&lists-host;</ulink></literal>.
+To find out more on how to subscribe or unsubscribe, how to post and how not to
+post, where to find old posts and how to search them, how to contact the list
+maintainers and see various other information about the mailing lists, please
+read <ulink url="&url-debian-lists;"></ulink>. This section
+will only cover aspects of mailing lists that are of particular interest to
+developers.
</para>
<section id="mailing-lists-rules">
<title>Basic rules for use</title>
<itemizedlist>
<listitem>
<para>
-<email>debian-devel-announce@&lists-host;</email>, used to announce
-important things to developers. All developers are expected to be subscribed
-to this list.
+&email-debian-devel-announce;, used to announce important
+things to developers. All developers are expected to be subscribed to this
+list.
</para>
</listitem>
<listitem>
<para>
-<email>debian-devel@&lists-host;</email>, used to discuss various
-development related technical issues.
+&email-debian-devel;, used to discuss various development
+related technical issues.
</para>
</listitem>
<listitem>
<para>
-<email>debian-policy@&lists-host;</email>, where the Debian Policy is
-discussed and voted on.
+&email-debian-policy;, where the Debian Policy is discussed
+and voted on.
</para>
</listitem>
<listitem>
<para>
-<email>debian-project@&lists-host;</email>, used to discuss various
-non-technical issues related to the project.
+&email-debian-project;, used to discuss various non-technical
+issues related to the project.
</para>
</listitem>
</itemizedlist>
<section id="mailing-lists-special">
<title>Special lists</title>
<para>
-<email>debian-private@&lists-host;</email> is a special mailing list for
-private discussions amongst Debian developers. It is meant to be used for
-posts which for whatever reason should not be published publicly. As such, it
-is a low volume list, and users are urged not to use
-<email>debian-private@&lists-host;</email> unless it is really necessary.
+&email-debian-private; is a special mailing list for private
+discussions amongst Debian developers. It is meant to be used for posts which
+for whatever reason should not be published publicly. As such, it is a low
+volume list, and users are urged not to use
+&email-debian-private; unless it is really necessary.
Moreover, do <emphasis>not</emphasis> forward email from that list to anyone.
Archives of this list are not available on the web for obvious reasons, but you
can see them using your shell account on <literal>&lists-host;</literal>
directory.
</para>
<para>
-<email>debian-email@&lists-host;</email> is a special mailing list used as
-a grab-bag for Debian related correspondence such as contacting upstream
-authors about licenses, bugs, etc. or discussing the project with others where
-it might be useful to have the discussion archived somewhere.
+&email-debian-email; is a special mailing list used as a
+grab-bag for Debian related correspondence such as contacting upstream authors
+about licenses, bugs, etc. or discussing the project with others where it
+might be useful to have the discussion archived somewhere.
</para>
</section>
<title>IRC channels</title>
<para>
Several IRC channels are dedicated to Debian's development. They are mainly
-hosted on the <ulink url="http://www.oftc.net/oftc/">Open and free technology
+hosted on the <ulink url="&url-oftc;">Open and free technology
community (OFTC)</ulink> network. The <literal>irc.debian.org</literal> DNS
entry is an alias to <literal>irc.oftc.net</literal>.
</para>
<para>
Since <emphasis>#debian-devel</emphasis> is an open channel, you should not
speak there of issues that are discussed in
-<email>debian-private@&lists-host;</email>. There's another channel for
-this purpose, it's called <emphasis>#debian-private</emphasis> and it's
-protected by a key. This key is available in the archives of debian-private in
-<filename>master.debian.org:&file-debian-private-archive;</filename>, just
-<command>zgrep</command> for <emphasis>#debian-private</emphasis> in all the
-files.
+&email-debian-private;. There's another channel for this
+purpose, it's called <emphasis>#debian-private</emphasis> and it's protected by
+a key. This key is available in the archives of debian-private in
+<filename>master.debian.org:&file-debian-private-archive;</filename>,
+just <command>zgrep</command> for <emphasis>#debian-private</emphasis> in all
+the files.
</para>
<para>
There are other additional channels dedicated to specific subjects.
</para>
<para>
Channels dedicated to Debian also exist on other IRC networks, notably on the
-<ulink url="http://www.freenode.net/">freenode</ulink> IRC network, which was
-pointed at by the <literal>irc.debian.org</literal> alias until 4th June 2006.
+<ulink url="&url-openprojects;">freenode</ulink> IRC network,
+which was pointed at by the <literal>irc.debian.org</literal> alias until 4th
+June 2006.
</para>
<para>
To get a cloak on freenode, you send Jörg Jaspert <joerg@debian.org> a
<para>
Most of the machines are available for individual developers to use, as long as
the developers follow the rules set forth in the <ulink
-url="&url-devel-docs;dmup">Debian Machine Usage Policies</ulink>.
+url="&url-dmup;">Debian Machine Usage Policies</ulink>.
</para>
<para>
Generally speaking, you can use these machines for Debian-related purposes as
<section id="servers-bugs">
<title>The bugs server</title>
<para>
-<literal>&bugs-host;</literal> is the canonical location for the Bug
-Tracking System (BTS).
+<literal>&bugs-host;</literal> is the canonical location for
+the Bug Tracking System (BTS).
</para>
<para>
It is restricted; a mirror is available on <literal>merkel</literal>.
<para>
If you plan on doing some statistical analysis or processing of Debian bugs,
this would be the place to do it. Please describe your plans on
-<email>debian-devel@&lists-host;</email> before implementing anything,
-however, to reduce unnecessary duplication of effort or wasted processing time.
+&email-debian-devel; before implementing anything, however, to
+reduce unnecessary duplication of effort or wasted processing time.
</para>
</section>
<para>
Problems with the Debian FTP archive generally need to be reported as bugs
against the <systemitem role="package">&ftp-debian-org;</systemitem>
-pseudo-package or an email to <email>ftpmaster@debian.org</email>, but also see
+pseudo-package or an email to &email-ftpmaster;, but also see
the procedures in <xref linkend="archive-manip"/> .
</para>
</section>
<para>
If you find a problem with the Debian web server, you should generally submit a
bug against the pseudo-package, <systemitem
-role="package">&www-debian-org;</systemitem>. Remember to check whether or not
+role="package">www.debian.org</systemitem>. Remember to check whether or not
someone else has already reported the problem to the <ulink
url="http://&bugs-host;/&www-debian-org;">Bug Tracking System</ulink>.
</para>
one of the other servers located outside the United States.
</para>
<para>
-Send mail to <email>debian-devel@&lists-host;</email> if you have any
-questions.
+Send mail to &email-debian-devel; if you have any questions.
</para>
</section>
</para>
<para>
To request a CVS area, send a request via email to
-<email>debian-admin@debian.org</email>. Include the name of the requested CVS
+&email-debian-admin;. Include the name of the requested CVS
area, the Debian account that should own the CVS root area, and why you need
it.
</para>
<section id="devel-db">
<title>The Developers Database</title>
<para>
-The Developers Database, at <ulink url="&url-debian-db;"></ulink>, is an
-LDAP directory for managing Debian developer attributes. You can use this
-resource to search the list of Debian developers. Part of this information is
-also available through the finger service on Debian servers, try
-<command>finger yourlogin@db.debian.org</command> to see what it reports.
+The Developers Database, at <ulink
+url="&url-debian-db;"></ulink>, is an LDAP directory for
+managing Debian developer attributes. You can use this resource to search the
+list of Debian developers. Part of this information is also available through
+the finger service on Debian servers, try <command>finger
+yourlogin@db.debian.org</command> to see what it reports.
</para>
<para>
Developers can <ulink url="&url-debian-db-login;">log into the
<para>
personal information such as your address, country, the latitude and longitude
of the place where you live for use in <ulink
-url="&url-devel-docs;developers.loc">the world map of Debian
+url="&url-worldmap;">the world map of Debian
developers</ulink>, phone and fax numbers, IRC nickname and web page
</para>
</listitem>
<title>The Debian archive</title>
<para>
The &debian-formal; distribution consists of a lot of packages
-(<filename>.deb</filename>'s, currently around &number-of-pkgs;) and a few additional files
-(such as documentation and installation disk images).
+(<filename>.deb</filename>'s, currently around
+&number-of-pkgs;) and a few additional files (such as
+documentation and installation disk images).
</para>
<para>
Here is an example directory tree of a complete Debian archive:
<para>
All the information on Debian mirrors, including a list of the available public
FTP/HTTP servers, can be found at <ulink
-url="url-debian-mirroring"></ulink>. This useful page also includes
-information and tools which can be helpful if you are interested in setting up
-your own mirror, either for internal or public access.
+url="&url-debian-mirrors;"></ulink>. This useful page also
+includes information and tools which can be helpful if you are interested in
+setting up your own mirror, either for internal or public access.
</para>
<para>
Note that mirrors are generally run by third-parties who are interested in
Once the package is accepted, the system sends a confirmation mail to the
maintainer and closes all the bugs marked as fixed by the upload, and the
auto-builders may start recompiling it. The package is now publicly accessible
-at <ulink url="http://incoming.debian.org/"></ulink> until it is really
+at <ulink url="&url-incoming;"></ulink> until it is really
installed in the Debian archive. This happens only once a day (and is also
called the `dinstall run' for historical reasons); the package is then removed
from incoming and installed in the pool along with all the other packages.
<filename>.changes</filename> file that you uploaded to the appropriate mailing
lists. If a package is released with the <literal>Distribution:</literal> set
to `stable', the announcement is sent to
-<email>debian-changes@&lists-host;</email>. If a package is released with
+&email-debian-changes;. If a package is released with
<literal>Distribution:</literal> set to `unstable' or `experimental', the
-announcement will be posted to
-<email>debian-devel-changes@&lists-host;</email> instead.
+announcement will be posted to &email-debian-devel-changes;
+instead.
</para>
<para>
Though ftp-master is restricted, a copy of the installation is available to all
<listitem>
<para>
<literal>bts-control</literal>: reply to mails sent to
-<email>control@&bugs-host;</email>
+&email-bts-control;
</para>
</listitem>
<listitem>
<title>Developer's packages overview</title>
<para>
A QA (quality assurance) web portal is available at <ulink
-url="&url-debian-qa;developer.php"></ulink> which displays a table
-listing all the packages of a single developer (including those where the party
-is listed as a co-maintainer). The table gives a good summary about the
-developer's packages: number of bugs by severity, list of available versions in
-each distribution, testing status and much more including links to any other
-useful information.
+url="&url-ddpo;"></ulink> which displays a table listing all
+the packages of a single developer (including those where the party is listed
+as a co-maintainer). The table gives a good summary about the developer's
+packages: number of bugs by severity, list of available versions in each
+distribution, testing status and much more including links to any other useful
+information.
</para>
<para>
It is a good idea to look up your own data regularly so that you don't forget
</para>
<para>
For more information please visit <ulink
-url="http://alioth.debian.org/"></ulink>.
+url="&url-alioth;"></ulink>.
</para>
</section>