X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=resources.dbk;h=74fa28ab59f7eba2db78da69e06a1ed466037cf6;hp=15e818bb41e112a7c5f9c7c5a0a46b7f88ed94e1;hb=f06e9dbc5a07fe74a5f7f3ac054d2efc6019b965;hpb=acf9d704554019d9c436bf634136df8595ce1dc9 diff --git a/resources.dbk b/resources.dbk index 15e818b..74fa28a 100644 --- a/resources.dbk +++ b/resources.dbk @@ -92,7 +92,7 @@ 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; +can see them using your shell account on &master-host; and looking in the &file-debian-private-archive; directory. @@ -132,46 +132,45 @@ community (OFTC) network. The irc.debian.org DNS entry is an alias to irc.oftc.net. -The main channel for Debian in general is #debian. This +The main channel for Debian in general is #debian. This is a large, general-purpose channel where users can find recent news in the -topic and served by bots. #debian is for English -speakers; there are also #debian.de, -#debian-fr, #debian-br and other +topic and served by bots. #debian is for English +speakers; there are also #debian.de, +#debian-fr, #debian-br and other similarly named channels for speakers of other languages. -The main channel for Debian development is #debian-devel. +The main channel for Debian development is #debian-devel. It is a very active channel since usually over 150 people are always logged in. It's a channel for people who work on Debian, it's not a support channel -(there's #debian for that). It is however open to anyone +(there's #debian for that). It is however open to anyone who wants to lurk (and learn). Its topic is commonly full of interesting information for developers. -Since #debian-devel is an open channel, you should not +Since #debian-devel is an open channel, you should not speak there of issues that are discussed in &email-debian-private;. There's another channel for this -purpose, it's called #debian-private and it's protected by +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 +just zgrep for #debian-private in all the files. There are other additional channels dedicated to specific subjects. -#debian-bugs is used for coordinating bug squashing -parties. #debian-boot is used to coordinate the work on -the debian-installer. #debian-doc is occasionally used to +#debian-bugs is used for coordinating bug squashing +parties. #debian-boot is used to coordinate the work on +the debian-installer. #debian-doc is occasionally used to talk about documentation, like the document you are reading. Other channels are dedicated to an architecture or a set of packages: -#debian-bsd, #debian-kde, -#debian-jr, #debian-edu, -#debian-sf (SourceForge package), -#debian-oo (OpenOffice package) ... +#debian-kde, #debian-dpkg, +#debian-jr, #debian-edu, +#debian-oo (OpenOffice package) ... Some non-English developers' channels exist as well, for example -#debian-devel-fr for French speaking people interested in +#debian-devel-fr for French speaking people interested in Debian's development. @@ -210,7 +209,7 @@ functions in the Debian project. Most of the machines are used for porting 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 +Some 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. @@ -238,9 +237,11 @@ etc. If you have a problem with the operation of a Debian server, and you think that -the system operators need to be notified of this problem, the Debian system -administrator team is reachable at -debian-admin@&lists-host;. +the system operators need to be notified of this problem, you can check +the list of open issues in the DSA queue of our request tracker at (you can login with user "guest" and password "readonly"). +To report a new problem, simply send a mail to &email-rt-dsa; and make +sure to put the string "Debian RT" somewhere in the subject. If you have a problem with a certain service, not related to the system @@ -274,8 +275,8 @@ reduce unnecessary duplication of effort or wasted processing time. The ftp-master server The &ftp-master-host; server holds the canonical copy of -the Debian archive (excluding the non-US packages). Generally, package uploads -go to this server; see . +the Debian archive. Generally, package uploads go to this server; see +. It is restricted; a mirror is available on merkel. @@ -288,15 +289,6 @@ the procedures in . -
-The non-US server - -The non-US server &non-us-host; was discontinued with -the release of sarge. The pseudo-package nonus.debian.org still exists for now. - -
-
The www-master server @@ -339,28 +331,23 @@ Send mail to &email-debian-devel; if you have any questions.
-
-The CVS server - - -Our CVS server is located on cvs.debian.org. - +
+The VCS servers -If you need to use a publicly accessible CVS server, for instance, to help -coordinate work on a package between many different developers, you can request -a CVS area on the server. +If you need to use a Version Control System for any of your Debian work, +you can use one the existing repositories hosted on Alioth or you can +request a new project and ask for the VCS repository of your choice. +Alioth supports CVS (alioth.debian.org), Subversion +(svn.debian.org), Arch (tla/baz, both on arch.debian.org), Bazaar +(bzr.debian.org), Darcs (darcs.debian.org), Mercurial (hg.debian.org) and Git +(git.debian.org). Checkout if you plan +to maintain packages in a VCS repository. See for +information on the services provided by Alioth. -Generally, cvs.debian.org offers a combination of local CVS -access, anonymous client-server read-only access, and full client-server access -through ssh. Also, the CVS area can be accessed read-only -via the Web at . - - -To request a CVS area, send a request via email to -&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. +Historically, Debian first used cvs.debian.org to host +CVS repositories. But that service is deprecated in favor of Alioth. +Only a few projects are still using it.
@@ -457,14 +444,14 @@ As you can see, the top-level directory contains two directories, dists/ and pool/. The latter is a “pool” in which the packages actually are, and which is handled by the archive maintenance database and the accompanying programs. The former -contains the distributions, stable, -testing and unstable. The +contains the distributions, stable, +testing and unstable. The Packages and Sources files in the distribution subdirectories can reference files in the pool/ directory. The directory tree below each of the distributions is arranged in an identical manner. What we describe below for -stable is equally applicable to the -unstable and testing distributions. +stable is equally applicable to the +unstable and testing distributions. dists/stable contains three directories, namely @@ -485,9 +472,9 @@ installing the Debian distribution on a specific architecture
Sections -The main section of the Debian archive is what makes up +The main section of the Debian archive is what makes up the official &debian-formal; distribution. -The main section is official because it fully complies +The main section is official because it fully complies with all our guidelines. The other two sections do not, to different degrees; as such, they are not officially part of &debian-formal;. @@ -501,13 +488,13 @@ Manual. The DFSG is our definition of “free software.” Check out the Debian Policy Manual for details. -Packages in the contrib section have to comply with the +Packages in the contrib section have to comply with the DFSG, but may fail other requirements. For instance, they may depend on non-free packages. Packages which do not conform to the DFSG are placed in the -non-free section. These packages are not considered as +non-free section. These packages are not considered as part of the Debian distribution, though we support their use, and we provide infrastructure (such as our bug-tracking system and mailing lists) for non-free software packages. @@ -521,21 +508,21 @@ above discussion is just an introduction. The separation of the three sections at the top-level of the archive is important for all people who want to distribute Debian, either via FTP servers on the Internet or on CD-ROMs: by distributing only the -main and contrib sections, one can -avoid any legal risks. Some packages in the non-free +main and contrib sections, one can +avoid any legal risks. Some packages in the non-free section do not allow commercial distribution, for example. On the other hand, a CD-ROM vendor could easily check the individual package -licenses of the packages in non-free and include as many +licenses of the packages in non-free and include as many on the CD-ROMs as it's allowed to. (Since this varies greatly from vendor to vendor, this job can't be done by the Debian developers.) Note that the term section is also used to refer to categories which simplify the organization and browsing of available packages, e.g. -admin, net, -utils etc. Once upon a time, these sections (subsections, +admin, net, +utils etc. Once upon a time, these sections (subsections, rather) existed in the form of subdirectories within the Debian archive. Nowadays, these exist only in the Section header fields of packages. @@ -554,24 +541,24 @@ Atari, Amiga and Macintoshes), MIPS, and PowerPC. The Linux 2.2 kernel supports even more architectures, including ARM and UltraSPARC. Since Linux supports these platforms, Debian decided that it should, too. Therefore, Debian has ports underway; in fact, we also have ports underway to non-Linux -kernels. Aside from i386 (our name for Intel x86), there -is m68k, alpha, -powerpc, sparc, -hurd-i386, arm, -ia64, hppa, -s390, mips, -mipsel and sh as of this writing. - - -&debian-formal; 1.3 is only available as i386. Debian -2.0 shipped for i386 and m68k -architectures. Debian 2.1 ships for the i386, -m68k, alpha, and -sparc architectures. Debian 2.2 added support for the -powerpc and arm architectures. -Debian 3.0 added support of five new architectures: ia64, -hppa, s390, mips -and mipsel. +kernels. Aside from i386 (our name for Intel x86), there +is m68k, alpha, +powerpc, sparc, +hurd-i386, arm, +ia64, hppa, +s390, mips, +mipsel and sh as of this writing. + + +&debian-formal; 1.3 is only available as i386. Debian +2.0 shipped for i386 and m68k +architectures. Debian 2.1 ships for the i386, +m68k, alpha, and +sparc architectures. Debian 2.2 added support for the +powerpc and arm architectures. +Debian 3.0 added support of five new architectures: ia64, +hppa, s390, mips +and mipsel. Information for developers and users about the specific ports are available at @@ -582,8 +569,8 @@ the Debian Ports web pages.
Packages -There are two types of Debian packages, namely source and -binary packages. +There are two types of Debian packages, namely source and +binary packages. Source packages consist of either two or three files: a @@ -595,9 +582,9 @@ or both an .orig.tar.gz and a If a package is developed specially for Debian and is not distributed outside of Debian, there is just one .tar.gz file which contains the sources of the program. If a package is distributed elsewhere too, the -.orig.tar.gz file stores the so-called upstream -source code, that is the source code that's distributed by the -upstream maintainer (often the author of the software). +.orig.tar.gz file stores the so-called upstream +source code, that is the source code that's distributed by the +upstream maintainer (often the author of the software). In this case, the .diff.gz contains the changes made by the Debian maintainer. @@ -612,7 +599,7 @@ about the package (maintainer, version, etc.). Distributions The directory system described in the previous chapter is itself contained -within distribution directories. Each distribution is +within distribution directories. Each distribution is actually contained in the pool directory in the top-level of the Debian archive itself. @@ -634,16 +621,16 @@ compatibility).
Stable, testing, and unstable -There are always distributions called stable (residing in -dists/stable), testing (residing in -dists/testing), and unstable +There are always distributions called stable (residing in +dists/stable), testing (residing in +dists/testing), and unstable (residing in dists/unstable). This reflects the development process of the Debian project. -Active development is done in the unstable distribution -(that's why this distribution is sometimes called the development -distribution). Every Debian developer can update his or her +Active development is done in the unstable distribution +(that's why this distribution is sometimes called the development +distribution). Every Debian developer can update his or her packages in this distribution at any time. Thus, the contents of this distribution change from day to day. Since no special effort is made to make sure everything in this distribution is working properly, it is sometimes @@ -651,57 +638,58 @@ literally unstable. The testing distribution is generated -automatically by taking packages from unstable if they satisfy certain -criteria. Those criteria should ensure a good quality for packages within -testing. The update to testing is launched each day after the new packages +automatically by taking packages from unstable if they +satisfy certain criteria. Those criteria should ensure a good quality for +packages within testing. The update to testing + is launched twice each day, right after the new packages have been installed. See . After a period of development, once the release manager deems fit, the -testing distribution is frozen, meaning that the policies -which control how packages move from unstable to -testing are tightened. Packages which are too buggy are -removed. No changes are allowed into testing except for +testing distribution is frozen, meaning that the policies +which control how packages move from unstable to +testing are tightened. Packages which are too buggy are +removed. No changes are allowed into testing except for bug fixes. After some time has elapsed, depending on progress, the -testing distribution is frozen even further. Details of +testing distribution is frozen even further. Details of the handling of the testing distribution are published by the Release Team on debian-devel-announce. After the open issues are solved to the satisfaction of the Release Team, the distribution is released. Releasing means that -testing is renamed to stable, and a -new copy is created for the new testing, and the previous -stable is renamed to oldstable and +testing is renamed to stable, and a +new copy is created for the new testing, and the previous +stable is renamed to oldstable and stays there until it is finally archived. On archiving, the contents are moved to &archive-host;). This development cycle is based on the assumption that the -unstable distribution becomes stable -after passing a period of being in testing. Even once a +unstable distribution becomes stable +after passing a period of being in testing. Even once a distribution is considered stable, a few bugs inevitably remain — that's why the stable distribution is updated every now and then. However, these updates are tested very carefully and have to be introduced into the archive individually to reduce the risk of introducing new bugs. You can find proposed -additions to stable in the +additions to stable in the proposed-updates directory. Those packages in proposed-updates that pass muster are periodically moved as a batch into the stable distribution and the revision level of the stable distribution is incremented (e.g., ‘3.0’ becomes ‘3.0r1’, ‘2.2r4’ becomes ‘2.2r5’, and so forth). Please refer to -uploads to the stable +uploads to the stable distribution for details. -Note that development under unstable continues during the -freeze period, since the unstable distribution remains in -place in parallel with testing. +Note that development under unstable continues during the +freeze period, since the unstable distribution remains in +place in parallel with testing.
More information about the testing distribution -Packages are usually installed into the `testing' distribution after they have -undergone some degree of testing in unstable. +Packages are usually installed into the testing distribution +after they have undergone some degree of testing in unstable. For more details, please see the information about @@ -712,20 +700,21 @@ the testing distribution.
Experimental -The experimental distribution is a special distribution. -It is not a full distribution in the same sense as `stable' and `unstable' are. +The experimental distribution is a special distribution. +It is not a full distribution in the same sense as stable, +testing and unstable are. Instead, it is meant to be a temporary staging area for highly experimental software where there's a good chance that the software could break your system, -or software that's just too unstable even for the unstable +or software that's just too unstable even for the unstable distribution (but there is a reason to package it nevertheless). Users who -download and install packages from experimental are +download and install packages from experimental are expected to have been duly warned. In short, all bets are off for the -experimental distribution. +experimental distribution. These are the sources.list 5 lines for -experimental: +experimental: deb http://ftp.xy.debian.org/debian/ experimental main @@ -733,42 +722,43 @@ deb-src http://ftp.xy.debian.org/debian/ experimental If there is a chance that the software could do grave damage to a system, it is -likely to be better to put it into experimental. For +likely to be better to put it into experimental. For instance, an experimental compressed file system should probably go into -experimental. +experimental. Whenever there is a new upstream version of a package that introduces new features but breaks a lot of old ones, it should either not be uploaded, or be -uploaded to experimental. A new, beta, version of some +uploaded to experimental. A new, beta, version of some software which uses a completely different configuration can go into -experimental, at the maintainer's discretion. If you are +experimental, at the maintainer's discretion. If you are working on an incompatible or complex upgrade situation, you can also use -experimental as a staging area, so that testers can get +experimental as a staging area, so that testers can get early access. -Some experimental software can still go into unstable, +Some experimental software can still go into unstable, with a few warnings in the description, but that isn't recommended because -packages from unstable are expected to propagate to -testing and thus to stable. You -should not be afraid to use experimental since it does not +packages from unstable are expected to propagate to +testing and thus to stable. You +should not be afraid to use experimental since it does not cause any pain to the ftpmasters, the experimental packages are automatically -removed once you upload the package in unstable with a +removed once you upload the package in unstable with a higher version number. New software which isn't likely to damage your system can go directly into -unstable. +unstable. -An alternative to experimental is to use your personal web +An alternative to experimental is to use your personal web space on people.debian.org. -When uploading to unstable a package which had bugs fixed in experimental, -please consider using the option -v to -dpkg-buildpackage to finally get them closed. +When uploading to unstable a package which had bugs fixed +in experimental, please consider using the option +-v to dpkg-buildpackage to finally get +them closed.
@@ -777,30 +767,36 @@ please consider using the option -v to
Release code names -Every released Debian distribution has a code name: Debian -1.1 is called `buzz'; Debian 1.2, `rex'; Debian 1.3, `bo'; Debian 2.0, `hamm'; -Debian 2.1, `slink'; Debian 2.2, `potato'; Debian 3.0, `woody'; Debian 3.1, -sarge; Debian 4.0, etch. There is also a ``pseudo-distribution'', called -`sid', which is the current `unstable' distribution; since packages are moved -from `unstable' to `testing' as they approach stability, `sid' itself is never -released. As well as the usual contents of a Debian distribution, `sid' -contains packages for architectures which are not yet officially supported or -released by Debian. These architectures are planned to be integrated into the -mainstream distribution at some future date. +Every released Debian distribution has a code name: Debian +1.1 is called buzz; Debian 1.2, rex; +Debian 1.3, bo; Debian 2.0, hamm; +Debian 2.1, slink; Debian 2.2, potato; +Debian 3.0, woody; Debian 3.1, sarge; +Debian 4.0, etch and Debian 5.0 will be called +lenny. There is also a ``pseudo-distribution'', called +sid, which is the current unstable +distribution; since packages are moved from unstable to +testing as they approach stability, sid +itself is never released. As well as the usual contents of a Debian +distribution, sid contains packages for architectures which +are not yet officially supported or released by Debian. These architectures +are planned to be integrated into the mainstream distribution at some future +date. Since Debian has an open development model (i.e., everyone can participate and -follow the development) even the `unstable' and `testing' distributions are -distributed to the Internet through the Debian FTP and HTTP server network. -Thus, if we had called the directory which contains the release candidate -version `testing', then we would have to rename it to `stable' when the version +follow the development) even the unstable and +testing distributions are distributed to the Internet through the +Debian FTP and HTTP server network. Thus, if we had called the directory which +contains the release candidate version testing, then we +would have to rename it to stable when the version is released, which would cause all FTP mirrors to re-retrieve the whole distribution (which is quite large). On the other hand, if we called the distribution directories -Debian-x.y from the beginning, people would think that -Debian release x.y is available. (This happened in the +Debian-x.y from the beginning, people would think that +Debian release x.y is available. (This happened in the past, where a CD-ROM vendor built a Debian 1.0 CD-ROM based on a pre-1.0 development version. That's the reason why the first official Debian release was 1.1, and not 1.0.) @@ -811,9 +807,9 @@ by their code names and not their release status (e.g., `slink'). These names stay the same during the development period and after the release; symbolic links, which can be changed easily, indicate the currently released stable distribution. That's why the real distribution directories use the -code names, while symbolic links for -stable, testing, and -unstable point to the appropriate release directories. +code names, while symbolic links for +stable, testing, and +unstable point to the appropriate release directories.
@@ -888,11 +884,11 @@ script is called to ask all the primary mirrors to update themselves. 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 +to stable, the announcement is sent to &email-debian-changes;. If a package is released with -Distribution: set to `unstable' or `experimental', the -announcement will be posted to &email-debian-devel-changes; -instead. +Distribution: set to unstable or +experimental, the announcement will be posted to +&email-debian-devel-changes; instead. Though ftp-master is restricted, a copy of the installation is available to all @@ -975,28 +971,30 @@ a given package at the URL
-
-The <command>madison</command> utility +
+The <command>dak ls</command> utility -madison is a command-line utility that is available on -&ftp-master-host;, and on the mirror on -&ftp-master-mirror;. It uses a single argument corresponding -to a package name. In result it displays which version of the package is -available for each architecture and distribution combination. An example will -explain it better. +dak ls is part of the dak suite of tools, listing +available package versions for all known distributions and architectures. +The dak tool is available on &ftp-master-host; +, and on the mirror on &ftp-master-mirror;. +It uses a single argument corresponding to a package name. An example will +explain it better: -$ madison libdbd-mysql-perl -libdbd-mysql-perl | 1.2202-4 | stable | source, alpha, arm, i386, m68k, powerpc, sparc -libdbd-mysql-perl | 1.2216-2 | testing | source, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc -libdbd-mysql-perl | 1.2216-2.0.1 | testing | alpha -libdbd-mysql-perl | 1.2219-1 | unstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc +$ dak ls evince +evince | 0.1.5-2sarge1 | oldstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc +evince | 0.4.0-5 | etch-m68k | source, m68k +evince | 0.4.0-5 | stable | source, alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc +evince | 2.20.2-1 | testing | source +evince | 2.20.2-1+b1 | testing | alpha, amd64, arm, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc +evince | 2.22.2-1 | unstable | source, alpha, amd64, arm, armel, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc -In this example, you can see that the version in unstable -differs from the version in testing and that there has -been a binary-only NMU of the package for the alpha architecture. Each version -of the package has been recompiled on most of the architectures. +In this example, you can see that the version in unstable +differs from the version in testing and that there has +been a binary-only NMU of the package for all architectures. Each version +of the package has been recompiled on all architectures.
@@ -1065,11 +1063,20 @@ In order to prevent spam, all messages sent to these addresses must contain the +contact + + +Mails sent to the maintainer through the *@packages.debian.org email +aliases. + + + + summary Regular summary emails about the package's status. Currently, only progression -in testing is sent. +in testing is sent. @@ -1093,8 +1100,10 @@ how your package gets recompiled for all architectures. cvs -CVS commit notifications, if the package has a CVS repository and the -maintainer has set up forwarding commit notifications to the PTS. +VCS commit notifications, if the package has a VCS repository and the +maintainer has set up forwarding of commit notifications to the PTS. The +"cvs" name is historic, in most cases commit notifications will come +from some other VCS like subversion or git. @@ -1193,7 +1202,13 @@ package -cvs: notification of CVS commits +contact: mails sent to the maintainer through the +*@packages.debian.org aliases + + + + +cvs: notification of VCS commits @@ -1306,24 +1321,30 @@ Here is an example of added headers for a source upload notification on the X-Loop: dpkg@&pts-host; X-PTS-Package: dpkg X-PTS-Keyword: upload-source -X-Unsubscribe: echo 'unsubscribe dpkg' | mail pts@qa.debian.org +List-Unsubscribe: <mailto:pts@qa.debian.org?body=unsubscribe+dpkg>
-
-Forwarding CVS commits in the PTS +
+Forwarding VCS commits in the PTS -If you use a publicly accessible CVS repository for maintaining your Debian +If you use a publicly accessible VCS repository for maintaining your Debian package, you may want to forward the commit notification to the PTS so that the subscribers (and possible co-maintainers) can closely follow the package's evolution. -Once you set up the CVS repository to generate commit notifications, you just +Once you set up the VCS repository to generate commit notifications, you just have to make sure it sends a copy of those mails to sourcepackage_cvs@&pts-host;. -Only the people who accept the cvs keyword will receive -these notifications. +Only the people who accept the cvs keyword will receive +these notifications. Note that the mail need to be sent from a +debian.org machine, otherwise you'll have to add +the X-PTS-Approved: 1 header. + + +For Subversion repositories, the usage of svnmailer is recommended. +See for an example on how to do it.
@@ -1441,10 +1462,10 @@ information section: From: Raphael Hertzog <hertzog@debian.org> To: pts-static-news@qa.debian.org -Subject: Browse debian-cd CVS repository with cvsweb +Subject: Browse debian-cd SVN repository Package: debian-cd -Url: &url-cvsweb;debian-cd/ +Url: http://svn.debian.org/viewsvn/debian-cd/trunk/ The second one is an announcement sent to a mailing list which is also sent to @@ -1452,7 +1473,7 @@ the PTS so that it is published on the PTS web page of the package. Note the use of the BCC field to avoid answers sent to the PTS by mistake. -: Raphael Hertzog <hertzog@debian.org> +From: Raphael Hertzog <hertzog@debian.org> To: debian-gtk-gnome@&lists-host; Bcc: pts-news@qa.debian.org Subject: Galeon 2.0 backported for woody @@ -1493,19 +1514,20 @@ responsibility.
-Debian *Forge: Alioth +Debian's GForge installation: Alioth -Alioth is a fairly new Debian service, based on a slightly modified version of -the GForge software (which evolved from SourceForge). This software offers -developers access to easy-to-use tools such as bug trackers, patch manager, -project/task managers, file hosting services, mailing lists, CVS repositories -etc. All these tools are managed via a web interface. +Alioth is a Debian service based on a slightly modified version of the +GForge software (which evolved from SourceForge). This software offers +developers access to easy-to-use tools such as bug trackers, patch +manager, project/task managers, file hosting services, mailing lists, CVS +repositories etc. All these tools are managed via a web interface. It is intended to provide facilities to free software projects backed or led by Debian, facilitate contributions from external developers to projects started by Debian, and help projects whose goals are the promotion of Debian or its -derivatives. +derivatives. It's heavily used by many Debian teams and provides +hosting for all sorts of VCS repositories. All Debian developers automatically have an account on Alioth. They can @@ -1513,9 +1535,14 @@ activate it by using the recover password facility. External developers can request guest accounts on Alioth. -For more information please visit . +For more information please visit the following links: + + + + + +