X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=resources.dbk;h=8a008914954e61c11e429dd6d3331af5a16efc19;hp=373bc5583ed8ac8636cad18983a08c1a78b47a3a;hb=c628744c6110f628796a70b48112f249ec322641;hpb=c81927355fe51c8a09827d098d0caad05a052d67 diff --git a/resources.dbk b/resources.dbk index 373bc55..8a00891 100644 --- a/resources.dbk +++ b/resources.dbk @@ -1,7 +1,7 @@ %commondata; + %commondata; ]> Resources for Debian Developers @@ -15,12 +15,13 @@ all the other resources that are available to help you in your maintainer work. Much of the conversation between Debian developers (and users) is managed through a wide array of mailing lists we host at &lists-host;. 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 . This section will only -cover aspects of mailing lists that are of particular interest to developers. +url="http://&lists-host;/">&lists-host;. +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 . This section +will only cover aspects of mailing lists that are of particular interest to +developers.
Basic rules for use @@ -50,27 +51,27 @@ The core Debian mailing lists that developers should use are: -debian-devel-announce@&lists-host;, 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. -debian-devel@&lists-host;, used to discuss various -development related technical issues. +&email-debian-devel;, used to discuss various development +related technical issues. -debian-policy@&lists-host;, where the Debian Policy is -discussed and voted on. +&email-debian-policy;, where the Debian Policy is discussed +and voted on. -debian-project@&lists-host;, 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. @@ -83,11 +84,11 @@ There are other mailing lists available for a variety of special topics; see
Special lists -debian-private@&lists-host; 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 -debian-private@&lists-host; 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 not 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 &lists-host; @@ -95,10 +96,10 @@ and looking in the &file-debian-private-archive; directory. -debian-email@&lists-host; 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.
@@ -125,7 +126,7 @@ url="&url-debian-lists-new;">the HOWTO. IRC channels Several IRC channels are dedicated to Debian's development. They are mainly -hosted on the Open and free technology +hosted on the Open and free technology community (OFTC) network. The irc.debian.org DNS entry is an alias to irc.oftc.net. @@ -148,12 +149,12 @@ information for developers. Since #debian-devel is an open channel, you should not speak there of issues that are discussed in -debian-private@&lists-host;. There's another channel for -this purpose, it's called #debian-private and it's -protected by a key. This key is available in the archives of debian-private in -master.debian.org:&file-debian-private-archive;, just -zgrep for #debian-private in all the -files. +&email-debian-private;. There's another channel for this +purpose, it's called #debian-private and it's protected by +a key. This key is available in the archives of debian-private in +master.debian.org:&file-debian-private-archive;, +just zgrep for #debian-private in all +the files. There are other additional channels dedicated to specific subjects. @@ -174,8 +175,9 @@ Debian's development. Channels dedicated to Debian also exist on other IRC networks, notably on the -freenode IRC network, which was -pointed at by the irc.debian.org alias until 4th June 2006. +freenode IRC network, +which was pointed at by the irc.debian.org alias until 4th +June 2006. To get a cloak on freenode, you send Jörg Jaspert <joerg@debian.org> a @@ -209,7 +211,7 @@ activities, and they all have a permanent connection to the Internet. Most of the machines are available for individual developers to use, as long as the developers follow the rules set forth in the Debian Machine Usage Policies. +url="&url-dmup;">Debian Machine Usage Policies. Generally speaking, you can use these machines for Debian-related purposes as @@ -253,8 +255,8 @@ mirrored to another server.
The bugs server -&bugs-host; is the canonical location for the Bug -Tracking System (BTS). +&bugs-host; is the canonical location for +the Bug Tracking System (BTS). It is restricted; a mirror is available on merkel. @@ -262,8 +264,8 @@ It is restricted; a mirror is available on merkel. 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 -debian-devel@&lists-host; 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.
@@ -280,7 +282,7 @@ It is restricted; a mirror is available on merkel. Problems with the Debian FTP archive generally need to be reported as bugs against the &ftp-debian-org; -pseudo-package or an email to ftpmaster@debian.org, but also see +pseudo-package or an email to &email-ftpmaster;, but also see the procedures in .
@@ -303,7 +305,7 @@ official web pages, the face of Debian for most newbies. If you find a problem with the Debian web server, you should generally submit a bug against the pseudo-package, &www-debian-org;. Remember to check whether or not +role="package">www.debian.org. Remember to check whether or not someone else has already reported the problem to the Bug Tracking System. @@ -332,8 +334,7 @@ materials subject to the U.S. export restrictions, in which case you can use one of the other servers located outside the United States. -Send mail to debian-devel@&lists-host; if you have any -questions. +Send mail to &email-debian-devel; if you have any questions. @@ -356,7 +357,7 @@ via the Web at . To request a CVS area, send a request via email to -debian-admin@debian.org. 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. @@ -384,11 +385,12 @@ out which chroots are available via
The Developers Database -The Developers Database, at , 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 -finger yourlogin@db.debian.org to see what it reports. +The Developers Database, at , 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 finger +yourlogin@db.debian.org to see what it reports. Developers can log into the @@ -414,7 +416,7 @@ whether you are on vacation personal information such as your address, country, the latitude and longitude of the place where you live for use in the world map of Debian +url="&url-worldmap;">the world map of Debian developers, phone and fax numbers, IRC nickname and web page @@ -441,8 +443,9 @@ url="&url-debian-db-mail-gw;">. The Debian archive The &debian-formal; distribution consists of a lot of packages -(.deb's, currently around &number-of-pkgs;) and a few additional files -(such as documentation and installation disk images). +(.deb's, currently around +&number-of-pkgs;) and a few additional files (such as +documentation and installation disk images). Here is an example directory tree of a complete Debian archive: @@ -831,9 +834,9 @@ push mirroring). All the information on Debian mirrors, including a list of the available public FTP/HTTP servers, can be found at . 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;">. 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. Note that mirrors are generally run by third-parties who are interested in @@ -872,7 +875,7 @@ package is refused and is moved to the reject directory. 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 until it is really +at 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. @@ -885,10 +888,10 @@ The archive maintenance software will also send the OpenPGP/GnuPG signed .changes file that you uploaded to the appropriate mailing lists. If a package is released with the Distribution: set to `stable', the announcement is sent to -debian-changes@&lists-host;. If a package is released with +&email-debian-changes;. If a package is released with Distribution: set to `unstable' or `experimental', the -announcement will be posted to -debian-devel-changes@&lists-host; instead. +announcement will be posted to &email-debian-devel-changes; +instead. Though ftp-master is restricted, a copy of the installation is available to all @@ -1178,7 +1181,7 @@ summary: bts-control: reply to mails sent to -control@&bugs-host; +&email-bts-control; @@ -1474,12 +1477,12 @@ contained in the previous one. Developer's packages overview A QA (quality assurance) web portal is available at 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;"> 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. It is a good idea to look up your own data regularly so that you don't forget @@ -1510,7 +1513,7 @@ request guest accounts on Alioth. For more information please visit . +url="&url-alioth;">.