#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2013-12-30 17:37+0100\n"
"PO-Revision-Date: 2012-11-22 21:11+0100\n"
"Last-Translator: Mateusz Kacprzak <mateusz.kacprzak@yandex.ru>\n"
"Language-Team: \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 1.5.4\n"

#. Tag: keyword
#, no-c-format
msgid "Objective"
msgstr ""

#. Tag: keyword
#, no-c-format
msgid "Means"
msgstr ""

#. Tag: keyword
#, no-c-format
msgid "Operation"
msgstr ""

#. Tag: keyword
#, no-c-format
msgid "Volunteer"
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Debian Project"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Before diving right into the technology, let us have a look at what the Debian Project is, its objectives, its means, and its operations."
msgstr ""

#. Tag: title
#, no-c-format
msgid "What Is Debian?"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>association</primary>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>CULTURE</emphasis> Origin of the Debian name"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Look no further: Debian is not an acronym. This name is, in reality, a contraction of two first names: that of Ian Murdock, and his girlfriend at the time, Debra. Debra + Ian = Debian."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian is a GNU/Linux and GNU/kFreeBSD distribution. We will discuss what a distribution is in further detail in <xref linkend=\"sect.role-of-distributions\" />, but for now, we will simply state that it is a complete operating system, including software and systems for installation and management, all based on the Linux or FreeBSD kernel and free software (especially those from the GNU project)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "When he created Debian, in 1993, under the leadership of the FSF, Ian Murdock had clear objectives, which he expressed in the <emphasis>Debian Manifesto</emphasis>. The free operating system that he sought would have to have two principal features. First, quality: Debian would be developed with the greatest care, to be worthy of the Linux kernel. It would also be a non-commercial distribution, sufficiently credible to compete with major commercial distributions. This double ambition would, in his eyes, only be achieved by opening the Debian development process just like that of Linux and the GNU project. Thus, peer review would continuously improve the product."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>CULTURE</emphasis> GNU, the project of the FSF"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>GNU</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>GNU</primary><secondary>is Not Unix</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The GNU project is a range of free software developed, or sponsored, by the Free Software Foundation (FSF), originated by its iconic leader, Dr. Richard M. Stallman. GNU is a recursive acronym, standing for “GNU is Not Unix”."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>CULTURE</emphasis> Richard Stallman"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Stallman, Richard</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>RMS</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<acronym>FSF</acronym>'s founder and author of the GPL license, Richard M. Stallman (often referred to by his initials, RMS) is a charismatic leader of the Free Software movement. Due to his uncompromising positions, he's not unanimously admired, but his non-technical contributions to Free Software (in particular at the legal and philosophical level) are respected by everybody."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A Multi-Platform Operating System"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>meta-distribution</primary>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>COMMUNITY</emphasis> Ian Murdock's journey"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Ian Murdock</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Murdock, Ian</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Progeny</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Ian Murdock, founder of the Debian project, was its first leader, from 1993 to 1996. After passing the baton to Bruce Perens, Ian took a less public role. He returned to working behind the scenes of the free software community, creating the Progeny company, with the intention of marketing a distribution derived from Debian. This venture was, sadly, a commercial failure, and development was abandoned. The company, after several years of scraping by, simply as a service provider, eventually filed for bankruptcy in April of 2007. Of the various projects initiated by Progeny, only <emphasis>discover</emphasis> still remains. It is an automatic hardware detection tool."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian, remaining true to its initial principles, has had so much success that, today, it has reached a tremendous size. The 13 architectures offered cover 11 hardware architectures and 2 kernels (Linux and FreeBSD). Furthermore, with more than 17,300 source packages, the available software can meet almost any need that one could have, whether at home or in the enterprise."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The sheer size of the distribution can be inconvenient: it is really unreasonable to distribute 70 CD-ROMs to install a complete version on a standard PC… This is why Debian is increasingly considered as a “meta-distribution”, from which one extracts more specific distributions intended for a particular public: Debian-Desktop for traditional office use, Debian-Edu for education and pedagogical use in an academic environment, Debian-Med for medical applications, Debian-Junior for young children, etc. A more complete list of the subprojects can be found in the section dedicated to that purpose, see <xref linkend=\"sect.sub-projects\" />."
msgstr ""

#. Tag: para
#, no-c-format
msgid "These partial views of Debian are organized in a well-defined framework, thus guaranteeing hassle-free compatibility between the various “sub-distributions”. All of them follow the general planning for release of new versions. And since they build on the same foundations, they can be easily extended, completed, and personalized with applications available in the Debian repositories."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>subproject</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "All the Debian tools operate in this direction: <command>debian-cd</command> has for a long time now allowed the creation of a set of CD-ROMs containing only a pre-selected set of packages; <command>debian-installer</command> is also a modular installer, easily adapted to special needs. <command>APT</command> will install packages from various origins, while guaranteeing the overall consistency of the system."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>TOOL</emphasis> Creating a Debian CD-ROM"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>debian-cd</command></primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<command>debian-cd</command> creates ISO images of installation media (CD, DVD, Blu-Ray, etc.) ready for use. Any matter regarding this software is discussed (in English) on the <email>debian-cd@lists.debian.org</email> mailing list."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>BACK TO BASICS</emphasis> To each computer, its architecture"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The term “architecture” indicates a type of computer (the most known include Mac or PC). Each architecture is differentiated primarily according to its processor, usually incompatible with other processors. These differences in hardware involve varying means of operation, thus requiring that software be compiled specifically for each architecture."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>architecture</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>processor</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Most software available in Debian is written in portable programming languages: the same source code can be compiled for various architectures. In effect, an executable binary, always compiled for a specific architecture, will not usually function on the other architectures."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Recall that each program is created by writing source code; this source code is a text file composed of instructions in a given programming language. Before you can use the software, it is necessary to compile the source code, which means transforming the code into a binary (a series of machine instructions executable by the processor). Each programming language has a specific compiler to execute this operation (for example, <command>gcc</command> for the C programming language)."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>source</primary><secondary>code</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>binary code</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>compilation</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>compiler</primary>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>TOOL</emphasis> Installer"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>debian-installer</command></primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<command>debian-installer</command> is the name of the Debian installation program. Its modular design allows it to be used in a broad range of installation scenarios. The development work is coordinated on the <email>debian-boot@lists.debian.org</email> mailing list under the direction of Joey Hess and Cyril Brulebois."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Quality of Free Software"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian follows all of the principles of Free Software, and its new versions are not released until they are ready. Developers are not forced by some set schedule to rush to meet an arbitrary deadline. People frequently complain of the long time between Debian's stable releases, but this caution also ensures Debian's legendary reliability: long months of testing are indeed necessary for the full distribution to receive the “stable” label."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian will not compromise on quality: all known critical bugs are resolved in any new version, even if this requires the initially forecast release date to be pushed back."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Legal Framework: A Non-Profit Organization"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Legally speaking, Debian is a project managed by an American not-for-profit, volunteer association. The project has around a thousand <emphasis>Debian developers</emphasis>, but brings together a far greater number of contributors (translators, bug reporters, artists, casual developers, etc.)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "To carry its mission to fruition, Debian has a large infrastructure, with many servers connected across the Internet, offered by many sponsors."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>COMMUNITY</emphasis> Behind Debian, the SPI association, and local branches"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>SPI</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Debian France</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Software in the Public Interest</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian doesn't own any server in its own name, since it is only a project within the <emphasis>Software in the Public Interest</emphasis> association, and SPI manages the hardware and financial aspects (donations, purchase of hardware, etc.). While initially created specifically for the Debian project, this association now hosts other free software projects, especially the PostgreSQL database, Freedesktop.org (project for standardization of various parts of modern graphical desktop environments, such as GNOME and KDE), and the Libre Office office suite. <ulink type=\"block\" url=\"http://www.spi-inc.org/\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "In addition to SPI, various local associations collaborate closely with Debian in order to generate funds for Debian, without centralizing everything in the U.S.A: they are known as “Trusted Organizations” in the Debian jargon. This setup avoids prohibitive international transfer costs, and fits well with the decentralized nature of the project."
msgstr ""

#. Tag: para
#, no-c-format
msgid "While the list of trusted organizations is rather short, there are many more Debian-related associations whose goal is to promote Debian: <emphasis>Debian France</emphasis>, <emphasis>Debian-UK</emphasis>, <emphasis>Debian-ES</emphasis>, <emphasis>debian.ch</emphasis>, and others around the world. Do not hesitate to join your local association and support the project! <ulink type=\"block\" url=\"http://wiki.debian.org/Teams/Auditor/Organizations\" /> <ulink type=\"block\" url=\"http://france.debian.net/\" /> <ulink type=\"block\" url=\"http://wiki.earth.li/DebianUKSociety\" /> <ulink type=\"block\" url=\"http://www.debian-es.org/\" /> <ulink type=\"block\" url=\"http://debian.ch/\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Foundation Documents"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Foundation Documents</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "A few years after its initial launch, Debian formalized the principles that it should follow as a free software project. This deliberately activist decision allows orderly and peaceful growth by ensuring that all members progress in the same direction. To become a Debian developer, any candidate must confirm and prove their support and adherence to the principles established in the project's Foundation Documents."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The development process is constantly debated, but these Foundation Documents are widely and consensually supported, thus rarely change. The Debian constitution also offers other guarantees for their stability: a three-quarters qualified majority is required to approve any amendment."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Commitment towards Users"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>social contract</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>contract, social</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The project also has a “social contract”. What place does such a text have in a project only intended for the development of an operating system? That is quite simple: Debian works for its users, and thus, by extension, for society. This contract summarizes the commitments that the project undertakes. Let us study them in greater detail:"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian will remain 100% free."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This is Rule No. 1. Debian is and will remain composed entirely and exclusively of free software. Additionally, all software development within the Debian project, itself, will be free."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>PERSPECTIVE</emphasis> Beyond software"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The first version of the Debian Social Contract said “Debian Will Remain 100% Free <emphasis>Software</emphasis>”. The disappearance of this word (with the ratification of Version 1.1 of the contract in April of 2004) indicates the will to achieve freedom, not only in software, but also in the documentation and any other element that Debian wishes to provide within its operating system."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This change, which was only intended as editorial, has, in reality, had numerous consequences, especially with the removal of some problematic documentation. Furthermore, the increasing use of firmware in drivers poses problems: many are non-free, yet they are necessary for proper operation of the corresponding hardware."
msgstr ""

#. Tag: para
#, no-c-format
msgid "We will give back to the free software community."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Any improvement contributed by the Debian project to a work integrated in the distribution is sent back to the author of the work (called “upstream”). In general, Debian will cooperate with the community rather than work in isolation."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>COMMUNITY</emphasis> Upstream author, or Debian developer?"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>upstream author</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>author, upstream</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>upstream</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The term “upstream author” means the author(s)/developer(s) of a work, those who write and develop it. On the other hand, a “Debian developer” uses an existing work to make it into a Debian package (the term “Debian maintainer” is better suited)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "In practice, the distinction is often not as clear-cut. The Debian maintainer may write a patch, which benefits all users of the work. In general, Debian encourages those in charge of a package in Debian to get involved in “upstream” development as well (they become, then, contributors, without being confined to the role of simple users of a program)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "We will not hide problems."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian is not perfect, and, we will find new problems to fix every day. We will keep our entire bug report database open for public view at all times. Reports that people file on-line will promptly become visible to others."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Our priorities are our users and free software."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This commitment is more difficult to define. Debian imposes, thus, a bias when a decision must be made, and will discard an easy solution for the developers that will jeopardize the user experience, opting for a more elegant solution, even if it is more difficult to implement. This means to take into account, as a priority, the interests of the users and free software."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Works that do not meet our free software standards."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian accepts and understands that users may want to use some non-free programs. That's why the project allows usage of parts of its infrastructure to distribute Debian packages of non-free software that can safely be redistributed."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>COMMUNITY</emphasis> For or against the non-free section?"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>non-free</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>section</primary><secondary>non-free</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The commitment to maintain a structure to accommodate non-free software (i.e. the “non-free” section, see the sidebar <xref linkend=\"sidebar.sections\" />) is frequently a subject of debate within the Debian community."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Detractors argue that it turns people away from free software equivalents, and contradicts the principle of serving only the free software cause. Supporters flatly state that most of the non-free packages are “nearly free”, and held back by only one or two annoying restrictions (the most common being the prohibition against commercial usage of the software). By distributing these works in the non-free branch, we indirectly explain to the author that their creation would be better known and more widely used if they could be included in the main section. They are, thus, politely invited to alter their license to serve this purpose."
msgstr ""

#. Tag: para
#, no-c-format
msgid "After a first, unfruitful attempt in 2004, the complete removal of the non-free section should not return to the agenda for several years, especially since it contains many useful documents that were moved simply because they did not meet the new requirements for the main section. This is especially the case for certain software documentation files issued by the GNU project (in particular, Emacs and Make)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The continued existence of the non-free section is a source of occasional friction with the Free Software Foundation, and is the main reason it refuses to officially recommend Debian as an operating system."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Debian Free Software Guidelines"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>free software principles</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>DFSG</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Debian Free Software Guidelines</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>free</primary><secondary>software</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "This reference document defines which software is “free enough” to be included in Debian. If a program's license is in accordance with these principles, it can be included in the main section; on the contrary, and provided that free distribution is permitted, it may be found in the non-free section. The non-free section is not officially part of Debian; it is an added service provided to users."
msgstr ""

#. Tag: para
#, no-c-format
msgid "More than a selection criteria for Debian, this text has become an authority on the subject of free software, and has served as the basis for the “Open Source Definition”. Historically, it is therefore one of the first formal definitions of the concept of “free software”."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The GNU General Public License, the BSD License, and the Artistic License are examples of traditional free licenses that follow the 9 points mentioned in this text. Below you will find the text as it is published on the Debian website. <ulink type=\"block\" url=\"http://www.debian.org/social_contract#guidelines\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Free redistribution."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The license of a Debian component may not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license may not require a royalty or other fee for such sale."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>BACK TO BASICS</emphasis> Free licenses"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>license</primary><secondary>BSD</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>BSD license</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>license</primary><secondary>GPL</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>GPL</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>GNU</primary><secondary>General Public License</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>General Public License</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>license</primary><secondary>artistic</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>artistic license</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The GNU GPL, the BSD license, and the Artistic License all comply with the Debian Free Software Guidelines, even though they are very different."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The GNU GPL, used and promoted by the FSF (Free Software Foundation), is the most common. Its main feature is that it also applies to any derived work that is redistributed: a program incorporating or using GPL code can only be distributed according to its terms. It prohibits, thus, any reuse in a proprietary application. This poses serious problems for the reuse of GPL code in free software incompatible with this license. As such, it is sometimes impossible to link a program published under another free software license with a library distributed under the GPL. On the other hand, this license is very solid in American law: FSF lawyers have participated in the drafting thereof, and have often forced violators to reach an amicable agreement with the FSF without going to court. <ulink type=\"block\" url=\"http://www.gnu.org/copyleft/gpl.html\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The BSD license is the least restrictive: everything is permitted, including use of modified BSD code in a proprietary application. Microsoft even uses it, basing the TCP/IP layer of Windows NT on that of the BSD kernel. <ulink type=\"block\" url=\"http://www.opensource.org/licenses/bsd-license.php\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Finally, the Artistic License reaches a compromise between these two others: integration of code in a proprietary application is permitted, but any modification must be published. <ulink type=\"block\" url=\"http://www.opensource.org/licenses/artistic-license-2.0.php\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The complete text of these licenses is available in <filename>/usr/share/common-licenses/</filename> on any Debian system."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Source code."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The program must include source code, and must allow distribution in source code as well as compiled form."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Derived works."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Integrity of the author's source code."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The license may restrict source-code from being distributed in modified form <emphasis>only</emphasis> if the license allows the distribution of “patch files” with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software (<emphasis>This is a compromise. The Debian group encourages all authors not to restrict any files, source or binary, from being modified</emphasis>)."
msgstr ""

#. Tag: title
#, no-c-format
msgid "No discrimination against persons or groups."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The license must not discriminate against any person or group of persons."
msgstr ""

#. Tag: title
#, no-c-format
msgid "No discrimination against fields of endeavor."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Distribution of license."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties."
msgstr ""

#. Tag: title
#, no-c-format
msgid "License must not be specific to Debian."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The rights attached to the program must not depend on the program being part of a Debian system. If the program is extracted from Debian and used or distributed without Debian but otherwise within the terms of the program's license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the Debian system."
msgstr ""

#. Tag: title
#, no-c-format
msgid "License must not contaminate other software."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be free software."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>BACK TO BASICS</emphasis> Copyleft"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>copyleft</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>copyrights</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Copyleft is a principle that consists in using copyrights to guarantee the freedom of a work and its derivatives, rather than restrict the rights of uses, as is the case with proprietary software. It is, also, a play of words on the term “copyright”. Richard Stallman discovered the idea when a friend of his, fond of puns, wrote on an envelope addressed to him: “copyleft: all rights reversed”. Copyleft imposes preservation of all initial liberties upon distribution of an original or modified version of a work (usually a program). It is, thus, not possible to distribute a program as proprietary software if it is derived from code from a copyleft released program."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The most well-known family of copyleft licenses is, of course, the GNU GPL and its derivatives, the GNU LGPL or GNU Lesser General Public License, and the GNU FDL or GNU Free Documentation License. Sadly, the copyleft licenses are generally incompatible with each other. Consequently, it is best to use only one of them."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>COMMUNITY</emphasis> Bruce Perens, a controversial leader"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Bruce Perens</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Perens, Bruce</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Open Source</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Bruce Perens was the second leader of the Debian project, just after Ian Murdock. He was very controversial in his dynamic and authoritarian methods. He nevertheless remains an important contributor to Debian, to whom Debian is especially indebted for the editing of the famous “Debian Free Software Guidelines” (DFSG), an original idea of Ean Schuessler. Subsequently, Bruce would derive from it the famous “Open Source Definition”, removing all references to Debian from it. <ulink type=\"block\" url=\"http://www.opensource.org/\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "His departure from the project was quite emotional, but Bruce has remained strongly attached to Debian, since he continues to promote this distribution in political and economic spheres. He still sporadically appears on the e-mail lists to give his advice and present his latest initiatives in favor of Debian."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>codename</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>name</primary><secondary>codename</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Rex</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Buzz</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Bo</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Hamm</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Slink</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Potato</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Woody</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Sarge</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Etch</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Lenny</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Squeeze</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Wheezy</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Jessie</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Sid</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Toy Story</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Pixar</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Last anecdotal point, it was Bruce who was responsible for inspiring the different “codenames” for Debian versions (1.1 — <emphasis role=\"distribution\">Rex</emphasis>, 1.2 — <emphasis role=\"distribution\">Buzz</emphasis>, 1.3 — <emphasis role=\"distribution\">Bo</emphasis>, 2.0 — <emphasis role=\"distribution\">Hamm</emphasis>, 2.1 — <emphasis role=\"distribution\">Slink</emphasis>, 2.2 — <emphasis role=\"distribution\">Potato</emphasis>, 3.0 — <emphasis role=\"distribution\">Woody</emphasis>, 3.1 — <emphasis role=\"distribution\">Sarge</emphasis>, 4.0 — <emphasis role=\"distribution\">Etch</emphasis>, 5.0 — <emphasis role=\"distribution\">Lenny</emphasis>, 6.0 — <emphasis role=\"distribution\">Squeeze</emphasis>, 7 — <emphasis role=\"distribution\">Wheezy</emphasis>, <emphasis role=\"distribution\">Testing</emphasis> — <emphasis role=\"distribution\">Jessie</emphasis>, <emphasis role=\"distribution\">Unstable</emphasis> — <emphasis role=\"distribution\">Sid</emphasis>). They are taken from the names of characters in the Toy Story movie. This animated film entirely composed of computer graphics was produced by Pixar Studios, with whom Bruce was employed at the time that he led the Debian project. The name “Sid” holds particular status, since it will eternally be associated with the <emphasis role=\"distribution\">Unstable</emphasis> branch. In the film, this character was the neighbor child, who was always breaking toys — so beware of getting too close to <emphasis role=\"distribution\">Unstable</emphasis>. Otherwise, <emphasis role=\"distribution\">Sid</emphasis> is also an acronym for “Still In Development”."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Inner Workings of the Debian Project"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>operations, internal</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>organization, internal</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The abundant end results produced by the Debian project derive simultaneously from the work on the infrastructure performed by experienced Debian developers, from the individual or collective work of developers on Debian packages, and from user feedback."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Debian Developers"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>developers</primary><secondary>Debian developers</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian developers have various responsibilities, and as official project members, they have great influence on the direction the project takes. A Debian developer is generally responsible for at least one package, but according to their available time and desire, they are free to become involved in numerous teams, acquiring, thus, more responsibilities within the project. <ulink type=\"block\" url=\"http://www.debian.org/devel/people\" /> <ulink type=\"block\" url=\"http://www.debian.org/intro/organization\" /> <ulink type=\"block\" url=\"http://wiki.debian.org/Teams\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>TOOL</emphasis> Developer's database"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>developers</primary><secondary>developer's database</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>database</primary><secondary>developer's database</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian has a database including all developers registered with the project, and their relevant information (address, telephone, geographical coordinates such as longitude and latitude, etc.). Some of the information (first and last name, country, username within the project, IRC username, GnuPG key, etc.) is public and available on the Web. <ulink type=\"block\" url=\"http://db.debian.org/\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The geographical coordinates allow the creation of a map locating all of the developers around the globe. Debian is truly an international project: its developers can be found on all continents, although the majority are in “Western countries”."
msgstr ""

#. Tag: title
#, no-c-format
msgid "World-wide distribution of Debian developers"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>world-wide distribution</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Package maintenance is a relatively regimented activity, very documented or even regulated. It must, in effect, comply with all the standards established by the <emphasis>Debian Policy</emphasis>. Fortunately, there are many tools that facilitate the maintainer's work. The developer can, thus, focus on the specifics of their package and on more complex tasks, such as squashing bugs. <ulink type=\"block\" url=\"http://www.debian.org/doc/debian-policy/\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>BACK TO BASICS</emphasis> Package maintenance, the developer's work"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>maintenance</primary><secondary>package maintenance</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>package</primary><secondary>maintenance</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Maintaining a package entails, first, “packaging” a program. Specifically, this means to define the means of installation so that, once installed, this program will operate and comply with the rules the Debian project sets for itself. The result of this operation is saved in a <filename>.deb</filename> file. Effective installation of the program will then require nothing more than extraction of this compressed archive and execution of some pre-installation or post-installation scripts contained therein."
msgstr ""

#. Tag: para
#, no-c-format
msgid "After this initial phase, the maintenance cycle truly begins: preparing updates to follow the latest version of the Debian Policy, fixing bugs reported by users, and including new “upstream” versions of the program which naturally continues to develop simultaneously. For instance, at the time of the initial packaging, the program was at version 1.2.3. After some months of development, the original authors release a new stable version, numbered 1.4.0. At this point, the Debian maintainer should update the package, so that users can benefit from its latest stable version."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Debian Policy</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>policy</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The Policy, an essential element of the Debian Project, establishes the norms ensuring both the quality of the packages and perfect interoperability of the distribution. Thanks to this Policy, Debian remains consistent despite its gigantic size. This Policy is not fixed in stone, but continuously evolves thanks to proposals formulated on the <email>debian-policy@lists.debian.org</email> mailing list. Amendments that are agreed upon by all interested parties are accepted and applied to the text by a small group of maintainers who have no editorial responsibility (they only include the modifications agreed upon by the Debian developers that are members of the above-mentioned list). You can read current amendment proposals on the bug tracking system: <ulink type=\"block\" url=\"http://bugs.debian.org/debian-policy\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>COMMUNITY</emphasis> Policy editorial process"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Anyone can propose an amendment to the Debian Policy just by submitting a bug report with a severity level of “wishlist” against the <emphasis role=\"pkg\">debian-policy</emphasis> package. The process that then starts is documented in <filename>/usr/share/doc/debian-policy/Process.html</filename>: if it is acknowledged that the problem revealed must be resolved by creating a new rule in the Debian Policy, a discussion begins on the <email>debian-policy@lists.debian.org</email> mailing list until consensus is reached and a proposal issued. Someone then drafts a desired amendment and submits it for approval (in the form of a patch to review). As soon as two other developers approve the fact that the proposed amendment reflects the consensus reached in the previous discussion (they “second” it), the proposal can be included in the official document by one of the <emphasis role=\"pkg\">debian-policy</emphasis> package maintainers. If the process fails at one of these steps, the maintainers close the bug, classifying the proposal as rejected."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>DEBIAN POLICY</emphasis> The documentation"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>documentation</primary><secondary>location</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>location of the documentation</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><filename>/usr/share/doc/</filename></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><filename>README.Debian</filename></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><filename>NEWS.Debian.gz</filename></primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Documentation for each package is stored in <filename>/usr/share/doc/<replaceable>package</replaceable>/</filename>. This directory often contains a <filename>README.Debian</filename> file describing the Debian specific adjustments made by the package maintainer. It is, thus, wise to read this file prior to any configuration, in order to benefit from their experience. We also find a <filename>changelog.Debian.gz</filename> file describing the changes made from one version to the next by the Debian maintainer. This is not to be confused with the <filename>changelog.gz</filename> file (or equivalent), which describes the changes made by the upstream developers. The <filename>copyright</filename> file includes information about the authors and the license covering the software. Finally, we may also find a file named <filename>NEWS.Debian.gz</filename>, which allows the Debian developer to communicate important information regarding updates; if <emphasis>apt-listchanges</emphasis> is installed, then these messages are automatically displayed. All other files are specific to the software in question. We especially like to point out the <filename>examples</filename> sub-directory, which frequently contains examples of configuration files."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The Policy covers very well the technical aspects of packaging. The size of the project also raises organizational problems; these are dealt with by the Debian Constitution, which establishes a structure and means for decision making. In other words, a formal governance system."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>constitution</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Debian Project Leader</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>DPL</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>leader</primary><secondary>role</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>leader</primary><secondary>election</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "This constitution defines a certain number of roles and positions, plus responsibilities and authorities for each. It is particularly worth noting that Debian developers always have ultimate decision making authority by a vote of general resolution, wherein a qualified majority of three quarters (75%) of votes is required for significant alterations to be made (such as those with an impact on the Foundation Documents). However, developers annually elect a “leader” to represent them in meetings, and ensure internal coordination between varying teams. This election is always a period of intense discussions. This leader's role is not formally defined by any document: candidates for this post usually propose their own definition of the position. In practice, the leader's roles include serving as a representative to the media, coordinating between “internal” teams, and providing overall guidance to the project, within which the developers can relate: the views of the DPL are implicitly approved by the majority of project members."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Specifically, the leader has real authority; his vote resolves tie votes; he can make any decision which is not already under the authority of someone else and can delegate part of his responsibilities."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Jackson, Ian</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Akkerman, Wichert</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Collins, Ben</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Garbee, Bdale</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Michlmayr, Martin</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Robinson, Branden</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Towns, Anthony</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Hocevar, Sam</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>McIntyre, Steve</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Zacchiroli, Stefano</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Nussbaum, Lucas</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Since its inception, the project has been successively led by Ian Murdock, Bruce Perens, Ian Jackson, Wichert Akkerman, Ben Collins, Bdale Garbee, Martin Michlmayr, Branden Robinson, Anthony Towns, Sam Hocevar, Steve McIntyre, Stefano Zacchiroli and Lucas Nussbaum."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>technical committee</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The constitution also defines a “technical committee”. This committee's essential role is to decide on technical matters when the developers involved have not reached an agreement between themselves. Otherwise, this committee plays an advisory role for any developer who fails to make a decision for which they are responsible. It is important to note that they only get involved when invited to do so by one of the parties in question."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>the project secretary</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Finally, the constitution defines the position of “project secretary”, who is in charge of the organization of votes related to the various elections and general resolutions."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The “general resolution” procedure is fully detailed in the constitution, from the initial discussion period to the final counting of votes. For further details see: <ulink type=\"block\" url=\"http://www.debian.org/devel/constitution.en.html\" />"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>general resolution</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>vote</primary>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>CULTURE</emphasis> Flamewar, the discussion that catches fire"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>flamewar</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>heated debate</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "A “flamewar” is an exceedingly impassioned debate, which frequently ends up with people attacking each other once all reasonable argumentation has been exhausted on both sides. Certain themes are more frequently subject to polemics than others (the choice of text editor, “do you prefer <command>vi</command> or <command>emacs</command>?”, is an old favorite). The matters often provoke very rapid e-mail exchanges due to the sheer number of people with an opinion on the matter (everyone) and the very personal nature of such questions."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Nothing particularly useful generally comes from such discussions; the general recommendation is to stay out of such debates, and maybe rapidly skim through their content, since reading them in full would be too time-consuming."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Even if this constitution establishes a semblance of democracy, the daily reality is quite different: Debian naturally follows the free software rules of the do-ocracy: the one who does things gets to decide how to do them. A lot of time can be wasted debating the respective merits of various ways to approach a problem; the chosen solution will be the first one that is both functional and satisfying… which will come out of the time that a competent person did put into it."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This is the only way to earn one's stripes: do something useful and show that one has worked well. Many Debian “administrative” teams operate by appointment, preferring volunteers who have already effectively contributed and proved their competence. This method is practical, because the most of the work these teams do is public, therefore, accessible to any interested developer. This is why Debian is often described as a “meritocracy”."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>CULTURE</emphasis> Meritocracy, the reign of knowledge"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>meritocracy</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Meritocracy is a form of government in which authority is exercised by those with the greatest merit. For Debian, merit is a measure of competence, which is, itself, assessed by observation of past actions by one or more others within the project (Stefano Zacchiroli, the previous project leader, speaks of “do-ocracy”, meaning “power to those who get things done”). Their simple existence proves a certain level of competence; their achievements generally being free software, with available source code, which can easily be reviewed by peers to assess their quality."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This effective operational method guarantees the quality of contributors in the “key” Debian teams. This method is by no means perfect and occasionally there are those who do not accept this way of operating. The selection of developers accepted in the teams may appear a bit arbitrary, or even unfair. Furthermore, not everybody has the same definition of the service expected from these teams. For some, it is unacceptable to have to wait eight days for inclusion of a new Debian package, while others will wait patiently for three weeks without a problem. As such, there are regular complaints from the disgruntled about the “quality of service” from some teams."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>COMMUNITY</emphasis> Integration of new maintainers"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>maintainer</primary><secondary>new maintainer</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The team in charge of admitting new developers is the most regularly criticized. One must acknowledge that, throughout the years, the Debian project has become more and more demanding of the developers that it will accept. Some people may see some injustice in that, but we must confess that what were only little challenges at the beginning have become much greater in a community of over 1,000 people, when it comes to ensuring the quality and integrity of everything that Debian produces for its users."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>DAM</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Debian Account Managers</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Furthermore, the acceptance procedure is concluded by review of the candidacy by a small team, the Debian Account Managers. These managers are, thus, particularly exposed to criticism, since they have final say in the inclusion or rejection of a volunteer within the Debian developers community. In practice, sometimes they must delay the acceptance of a person until they have learned more about the operations of the project. One can, of course, contribute to Debian before being accepted as an official developer, by being sponsored by current developers."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Active Role of Users"
msgstr ""

#. Tag: para
#, no-c-format
msgid "One might wonder if it is relevant to mention the users among those who work within the Debian project, but the answer is a definite yes: they play a critical role in the project. Far from being “passive”, some users run development versions of Debian and regularly file bug reports to indicate problems. Others go even further and submit ideas for improvements, by filing a bug report with a severity level of “wishlist”, or even submit corrections to the source code, called “patches” (see sidebar <xref linkend=\"sidebar.patch\" />)."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>TOOL</emphasis> Bug tracking system"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>system</primary><secondary>Bug Tracking System</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>BTS</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Bug Tracking System</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><literal>bugs.debian.org</literal></primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The Debian Bug Tracking System (Debian BTS) is used by large parts of the project. The public part (the web interface) allows users to view all bugs reported, with the option to display a sorted list of bugs selected according to various criteria, such as: affected package, severity, status, address of the reporter, address of the maintainer in charge of it, tag, etc. It is also possible to browse the complete historical listing of all discussions regarding each of the bugs."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Below the surface, the Debian BTS communicates via e-mail: all information that it stores come from messages sent by the various persons involved. Any e-mail sent to <email>12345@bugs.debian.org</email> will, thus, be assigned to the history for bug no. 12345. Authorized persons may “close” a bug by writing a message describing the reasons for the decision to close to <email>12345-done@bugs.debian.org</email> (a bug is closed when the indicated problem is resolved or no longer relevant). A new bug is reported by sending an e-mail to <email>submit@bugs.debian.org</email> according to a specific format which identifies the package in question. The address <email>control@bugs.debian.org</email> allows editing of all the “meta-information” related to a bug."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian BTS has other functional features, as well, such as the use of tags for labeling bugs. For more information, see <ulink type=\"block\" url=\"http://www.debian.org/Bugs/\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>VOCABULARY</emphasis> Severity of a bug"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>severity</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>bug</primary><secondary>severity</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The severity of a bug formally assigns a degree of gravity to the reported problem. Effectively, not all bugs have the same importance; for instance, a typo in a manual page is not comparable to a security vulnerability in server software."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian uses an extended scale to describe the severity of a bug. Each level is defined precisely in order to facilitate the selection thereof. <ulink type=\"block\" url=\"http://www.debian.org/Bugs/Developer#severities\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Additionally, numerous satisfied users of the service offered by Debian like to make a contribution of their own to the project. As not everyone has appropriate levels of expertise in programming, they may choose to assist with the translation and review of documentation. There are language-specific mailing lists to coordinate this work. <ulink type=\"block\" url=\"https://lists.debian.org/i18n.html\" /> <ulink type=\"block\" url=\"http://www.debian.org/international/\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>BACK TO BASICS</emphasis> What are i18n and l10n?"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>internationalization</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>localization</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>i18n</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>l10n</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "“i18n” and “l10n” are the abbreviations for the words “internationalization” and “localization”, respectively, preserving the initial and last letter of each word, and the number of letters in the middle."
msgstr ""

#. Tag: para
#, no-c-format
msgid "To “internationalize” a program consists of modifying it so that it can be translated (localized). This involves partially rewriting a program initially written to work in one language in order to be able to open it to all languages."
msgstr ""

#. Tag: para
#, no-c-format
msgid "To “localize” a program consists of translating the original messages (frequently in English) to another language. For this, it must have already been internationalized."
msgstr ""

#. Tag: para
#, no-c-format
msgid "In summary, internationalization prepares the software for translation, which is then executed by localization."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>BACK TO BASICS</emphasis> Patch, the way to send a fix"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>patch</command></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>patch</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>diff</command></primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "A patch is a file describing changes to be made to one or more reference files. Specifically, it will contain a list of lines to be removed or added to the code, as well as (sometimes) lines taken from the reference text, replacing the modifications in context (they allow identification of the placement of the changes if the line numbers have been changed)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The tool used for applying the modifications given in such a file is simply called <command>patch</command>. The tool that creates it is called <command>diff</command>, and is used as follows:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "<computeroutput>$ </computeroutput><userinput>diff -u file.old file.new &gt;file.patch</userinput>\n"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The <filename>file.patch</filename> file contains the instructions for changing the content of <filename>file.old</filename> into <filename>file.new</filename>. We can send it to someone, who can then use it to recreate <filename>file.new</filename> from the two others, like this:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "<computeroutput>$ </computeroutput><userinput>patch -p0 file.old &lt;file.patch</userinput>\n"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The file, <filename>file.old</filename>, is now identical to <filename>file.new</filename>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>TOOL</emphasis> Report a bug with <command>reportbug</command>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>reportbug</command></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>bug</primary><secondary>report a bug</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>report a bug</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The <command>reportbug</command> tool facilitates sending bug reports on a Debian package. It helps making sure the bug in question hasn't already been filed, thus preventing redundancy in the system. It reminds the user of the definitions of the severity levels, for the report to be as accurate as possible (the developer can always fine-tune these parameters later, if needed). It helps writing a complete bug report without the user needing to know the precise syntax, by writing it and allowing the user to edit it. This report will then be sent via an e-mail server (local, by default, but <command>reportbug</command> can also use a remote server)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This tool first targets the development versions, which is where the bugs will be fixed. Effectively, changes are not welcome in a stable version of Debian, with very few exceptions for security updates or other important updates (if, for example, a package is not working at all). A correction of a minor bug in a Debian package must, thus, wait for the next stable version."
msgstr ""

#. Tag: para
#, no-c-format
msgid "All of these contribution mechanisms are made more efficient by users' behavior. Far from being a collection of isolated persons, users are a true community within which numerous exchanges take place. We especially note the impressive activity on the user discussion mailing list, <email>debian-user@lists.debian.org</email> (<xref linkend=\"solving-problems\" /> discusses this in greater detail)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Not only do users help themselves (and others) on technical issues that directly affect them, but they also discuss the best ways to contribute to the Debian project and help it move forward — discussions that frequently result in suggestions for improvements."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Since Debian does not expend funds on any self-promoting marketing campaigns, its users play an essential role in its diffusion, ensuring its notoriety via word-of-mouth."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This method functions quite well, since Debian fans are found at all levels of the free software community: from install parties (workshops where seasoned users assist newcomers to install the system) organized by local LUGs or “Linux User Groups”, to association booths at large tech conventions dealing with Linux, etc."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Volunteers make posters, brochures, stickers, and other useful promotional materials for the project, which they make available to everyone, and which Debian provides freely on its website: <ulink type=\"block\" url=\"http://www.debian.org/events/material\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Teams and Sub-Projects"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian has been organized, right from the start, around the concept of source packages, each with its maintainer or group of maintainers. Many work teams have emerged over time, ensuring administration of the infrastructure, management of tasks not specific to any package in particular (quality assurance, Debian Policy, installer, etc.), with the latest series of teams growing up around sub-projects."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Existing Debian Sub-Projects"
msgstr ""

#. Tag: para
#, no-c-format
msgid "To each their own Debian! A sub-project is a group of volunteers interested in adapting Debian to specific needs. Beyond the selection of a sub-group of programs intended for a particular domain (education, medicine, multimedia creation, etc.), sub-projects are also involved in improving existing packages, packaging missing software, adapting the installer, creating specific documentation, and more."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>VOCABULARY</emphasis> Sub-project and derivative distribution"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>derivative distribution</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The development process for a derivative distribution consists in starting with a particular version of Debian and making a number of modifications to it. The infrastructure used for this work is completely external to the Debian project. There isn't necessarily a policy for contributing improvements. This difference explains how a derivative distribution may “diverge” from its origins, and why they have to regularly resynchronize with their source in order to benefit from improvements made upstream."
msgstr ""

#. Tag: para
#, no-c-format
msgid "On the other hand, a sub-project can not diverge, since all the work on it consists of directly improving Debian in order to adapt it to a specific goal."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The most known distribution derived from Debian is, without a doubt, Ubuntu, but there are many. See <xref linkend=\"derivative-distributions\" /> to learn about their particularities and their positioning in relationship to Debian."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Here is a small selection of current sub-projects:"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian-Junior, by Ben Armstrong, offering an appealing and easy to use Debian system for children;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian-Edu, by Petter Reinholdtsen, focused on the creation of a specialized distribution for the academic world;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian Med, by Andreas Tille, dedicated to the medical field;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian-Multimedia, from the creators of Agnula, which deals with multimedia creation;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian-Desktop, by Colin Walters, focuses on the desktop;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian-Ham, created by Bruce Perens, targets ham radio enthusiasts;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian-NP (Non-Profit) is for not-for-profit organizations;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian-Lex, finally, is intended for work within the legal field."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This list will most likely continue to grow with time and improved perception of the advantages of Debian sub-projects. Fully supported by the existing Debian infrastructure, they can, in effect, focus on work with real added value, without worrying about remaining synchronized with Debian, since they are developed within the project."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>PERSPECTIVE</emphasis> Debian in academia"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Debian-Edu</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>SkoleLinux</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian-Edu was, initially, a French project, created by Stéphane Casset and Raphaël Hertzog as part of their jobs at Logidée, on behalf of a pedagogical documentation departmental center. Raphaël then integrated it in Debian as a sub-project. Due to time constraints, it has not progressed further, as is often the case with free software projects lacking contributors."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Likewise, a team of Norwegians worked on a similar distribution, also based on the <command>debian-installer</command>. SkoleLinux's progress being significant, Raphaël suggested that it become part of the Debian family and to take over the Debian-Edu sub-project."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>PERSPECTIVE</emphasis> Debian for multimedia"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>64Studio</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>DeMuDi</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis>debian-multimedia</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Agnula</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Agnula was a European project, managed under the direction of an Italian team. It entailed, for the “DeMuDi” part, the development of a version of Debian dedicated to multimedia applications. Certain members of the project, especially Marco Trevisani, wanted to perpetuate it by integrating it within the Debian Project. The Debian-Multimedia sub-project was born. <ulink type=\"block\" url=\"http://wiki.debian.org/DebianMultimedia\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The project, however, had difficulty in forging an identity and taking off. Free Ekanayaka did the work within Debian, but offered the results under the form of a derivative distribution, which is now known as 64Studio. This distribution is affiliated with a new company that offers technical support. <ulink type=\"block\" url=\"http://www.64studio.com/\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Administrative Teams"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Most administrative teams are relatively closed and recruit only by cooptation. The best means to become a part of one is to intelligently assist the current members, demonstrating that you have understood their objectives and methods of operation."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The ftpmasters are in charge of the official archive of Debian packages. They maintain the program that receives packages sent by developers and automatically stores them, after some checks, on the reference server (<literal>ftp-master.debian.org</literal>)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "They must also verify the licenses of all new packages, in order to ensure that Debian may distribute them, prior to including them in the corpus of existing packages. When a developer wishes to remove a package, they address this team through the bug tracking system and the <emphasis>ftp.debian.org</emphasis> “pseudo-package”."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>ftpmaster</primary>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>VOCABULARY</emphasis> The pseudo-package, a monitoring tool"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>pseudo-package</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The bug tracking system, initially designed to associate bug reports with a Debian package, has proved very practical to manage other matters: lists of problems to be resolved or tasks to manage without any link to a particular Debian package. The “pseudo-packages” allow, thus, certain teams to use the bug tracking system without associating a real package with their team. Everyone can, thus, report issues that needs to be dealt with. For instance, the BTS has a <emphasis>ftp.debian.org</emphasis> entry that is used to report and track problems on the official package archive or simply to request removal of a package. Likewise, the <emphasis>www.debian.org</emphasis> pseudo-package refers to errors on the Debian website, and <emphasis>lists.debian.org</emphasis> gathers all the problems concerning the mailing lists."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>TOOL</emphasis> FusionForge, the Swiss Army Knife of collaborative development"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><literal>alioth</literal></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>FusionForge</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "FusionForge is a program that enables creation of sites similar to <literal>www.sourceforge.net</literal>, <literal>alioth.debian.org</literal>, or even <literal>savannah.gnu.org</literal>. It hosts projects and provides a range of services that facilitate collaborative development. Each project will have a dedicated virtual space there, including a web site, several “ticketing” systems to track — most commonly — bugs and patches, a survey tool, file storage, forums, version control system repositories, mailing lists and various other related services."
msgstr ""

#. Tag: para
#, no-c-format
msgid "<literal>alioth.debian.org</literal> is Debian's FusionForge server, administered by Tollef Fog Heen, Stephen Gran, and Roland Mas. Any project involving one or more Debian developers can be hosted there. <ulink type=\"block\" url=\"http://alioth.debian.org/\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Although rather complex internally, due to the broad range of services that it provides, FusionForge is otherwise relatively easy to install, thanks to the exceptional work of Roland Mas and Christian Bayle on the <emphasis role=\"pkg\">fusionforge</emphasis> Debian package."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The <emphasis>Debian System Administrators</emphasis> (DSA) team (<email>debian-admin@lists.debian.org</email>), as one might expect, is responsible for system administration of the many servers used by the project. They ensure optimal functioning of all base services (DNS, Web, e-mail, shell, etc.), install software requested by Debian developers, and take all precautions in regards to security. <ulink type=\"block\" url=\"http://dsa.debian.org\" />"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis>debian-admin</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>DSA (Debian System Administrators)</primary>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>TOOL</emphasis> Package tracking system"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>package tracking system</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>system</primary><secondary>package tracking system</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>PTS</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>DDPO</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Debian Developer's Packages Overview</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "This is one of Raphaël's creations. The basic idea is, for a given package, to centralize as much information as possible on a single page. Thus, one can quickly check the status of a program, identify tasks to be completed, and offer one's assistance. This is why this page gathers all bug statistics, available versions in each distribution, progress of a package in the <emphasis role=\"distribution\">Testing</emphasis> distribution, the status of translations of descriptions and debconf templates, the possible availability of a new upstream version, notices of noncompliance with the latest version of the Debian Policy, information on the maintainer, and any other information that said maintainer wishes to include. <ulink type=\"block\" url=\"http://packages.qa.debian.org/\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "An e-mail subscription service completes this web interface. It automatically sends the following selected information to the list: bugs and related discussions, availability of a new version on the Debian servers, new translations available for proofreading, etc."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Advanced users can, thus, follow all of this information closely and even contribute to the project, once they've got a good enough understanding of how it works."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Another web interface, known as <emphasis>Debian Developer's Packages Overview</emphasis> (DDPO), provides each developer a synopsis of the status of all Debian packages placed under their charge. <ulink type=\"block\" url=\"http://qa.debian.org/developer.php\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "These two websites are tools used by Debian QA (Quality Assurance), the group responsible for quality assurance within Debian."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>assurance</primary><secondary>quality assurance</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>quality</primary><secondary>assurance</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The <emphasis>listmasters</emphasis> administer the e-mail server that manages the mailing lists. They create new lists, handle bounces (delivery failure notices), and maintain spam filters (unsolicited bulk e-mail)."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>listmaster</primary>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>CULTURE</emphasis> Traffic on the mailing lists: some figures"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>lists</primary><secondary>mailing lists</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>mailing lists</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The mailing lists are, without a doubt, the best testimony to activity on a project, since they keep track of everything that happens. Some statistics (from 2012) regarding our mailing lists speak for themselves: Debian hosts more than 260 lists, totaling 190,000 individual subscriptions. The 22,000 messages sent each month generate 600,000 e-mails daily."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Each specific service has its own administration team, generally composed of volunteers who have installed it (and also frequently programmed the corresponding tools themselves). This is the case of the bug tracking system (BTS), the package tracking system (PTS), <literal>alioth.debian.org</literal> (FusionForge server, see sidebar), the services available on <literal>qa.debian.org</literal>, <literal>lintian.debian.org</literal>, <literal>buildd.debian.org</literal>, <literal>cdimage.debian.org</literal>, etc."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Development Teams, Transversal Teams"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Unlike administrative teams, the development teams are rather widely open, even to outside contributors. Even if Debian does not have a vocation to create software, the project needs some specific programs to meet its goals. Of course, developed under a free software license, these tools make use of methods proven elsewhere in the free software world."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>CULTURE</emphasis> CVS"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Concurrent Versions System</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>CVS</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>configuration management</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "CVS (Concurrent Versions System) is a tool for collaborative work on multiple files, while maintaining a history of modifications. The files in question are generally text files, such as a program's source code. If several people work together on the same file, <command>cvs</command> can only merge the alterations made if they were made to different portions of the file. Otherwise, these “conflicts” must be resolved by hand. This system manages modifications, line by line, by storing diff patches from one version to another."
msgstr ""

#. Tag: para
#, no-c-format
msgid "CVS uses a central archive (called a CVS repository) to store files and the history of their modifications (each revision is recorded in the form of a <emphasis>diff</emphasis> patch file, intended to be used on the prior version). Everyone checks out a particular version (working copy) to work on. The tool allows one to view the modifications made to the working copy (<command>cvs diff</command>), to record them in the central repository by creating a new entry in the versions history (<command>cvs commit</command>), to update the working copy to include modifications made in parallel by other uses (<command>cvs update</command>), and to record a particular configuration in the history in order to be able to easily extract it later on (<command>cvs tag</command>)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "<command>CVS</command> experts will know how to handle multiple concurrent versions of a project in development without them interfering with each other. These versions are called <emphasis>branches</emphasis>. This metaphor of a tree is fairly accurate, since a program is initially developed on a common trunk. When a milestone has been reached (such as version 1.0), development continues on two branches: the development branch prepares the next major release, and the maintenance branch manages updates and fixes for version 1.0."
msgstr ""

#. Tag: para
#, no-c-format
msgid "<command>cvs</command>, however, does have some limitations. It is unable to manage symbolic links, changes in file or directory names, the deletion of directories, etc. It has contributed to the appearance of more modern free alternatives which have filled in most of these gaps. These include, especially, <command>subversion</command> (<command>svn</command>), <command>git</command>, <command>bazaar</command> (<command>bzr</command>), and <command>mercurial</command> (<command>hg</command>). <ulink type=\"block\" url=\"http://subversion.apache.org/\" /> <ulink type=\"block\" url=\"http://git-scm.com/\" /> <ulink type=\"block\" url=\"http://bazaar.canonical.com/\" /> <ulink type=\"block\" url=\"http://mercurial.selenic.com/\" />"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>subversion</command></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>svn</command></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>git</command></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>bzr</command></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>hg</command></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>mercurial</command></primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian has developed little software of its own, but certain programs have assumed a starring role, and their fame has spread beyond the scope of the project. Good examples are <command>dpkg</command>, the Debian package management program (it is, in fact, an abbreviation of Debian PacKaGe, and generally pronounced as “dee-package”), and <command>apt</command>, a tool to automatically install any Debian package, and its dependencies, guaranteeing the consistency of the system after an upgrade (its name is an acronym for Advanced Package Tool). Their teams are, however, much smaller, since a rather high level of programming skill is required to gain an overall understanding of the operations of these types of programs."
msgstr ""

#. Tag: para
#, no-c-format
msgid "The most important team is probably that for the Debian installation program, <command>debian-installer</command>, which has accomplished a work of momentous proportions since its conception in 2001. Numerous contributors were needed, since it is difficult to write a single program able to install Debian on a dozen different architectures. Each one has its own mechanism for booting and its own bootloader. All of this work is coordinated on the <email>debian-boot@lists.debian.org</email> mailing list, under the direction of Joey Hess and Cyril Brulebois. <ulink type=\"block\" url=\"http://www.debian.org/devel/debian-installer/\" /> <ulink type=\"block\" url=\"http://kitenet.net/~joey/blog/entry/d-i_retrospective/\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The (very small) <command>debian-cd</command> program team has an even more modest objective. Many “small” contributors are responsible for their architecture, since the main developer can not know all the subtleties, nor the exact way to start the installer from the CD-ROM."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Many teams must collaborate with others in the activity of packaging: <email>debian-qa@lists.debian.org</email> tries, for example, to ensure quality at all levels of the Debian project. The <email>debian-policy@lists.debian.org</email> list develops Debian Policy according to proposals from all over the place. The teams in charge of each architecture (<email>debian-<replaceable>architecture</replaceable>@lists.debian.org</email>) compile all packages, adapting them to their particular architecture, if needed."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Other teams manage the most important packages in order to ensure maintenance without placing too heavy a load on a single pair of shoulders; this is the case with the C library and <email>debian-glibc@lists.debian.org</email>, the C compiler on the <email>debian-gcc@lists.debian.org</email> list, or Xorg on the <email>debian-x@lists.debian.org</email> (this group is also known as the X Strike Force, and coordinated by Cyril Brulebois)."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Follow Debian News"
msgstr ""

#. Tag: para
#, no-c-format
msgid "As already mentioned, the Debian project evolves in a very distributed, very organic way. As a consequence, it may be difficult at times to stay in touch with what happens within the project without being overwhelmed with a never-ending flood of notifications."
msgstr ""

#. Tag: para
#, no-c-format
msgid "If you only want the most important news about Debian, you probably should subscribe to the <email>debian-announce@lists.debian.org</email> list. This is a very low-traffic list (around a dozen messages a year), and only gives the most important announcements, such as the availability of a new stable release, the election of a new Project Leader, or the yearly Debian Conference."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Debian Project News</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "More general (and regular) news about Debian are sent to the <email>debian-news@lists.debian.org</email> list. The traffic on this list is quite reasonable too (usually around a handful of messages a month), and it includes the semi-regular “Debian Project News”, which is a compilation of various small bits of information about what happens in the project. Since all Debian developers can contribute these news when they think they have something noteworthy to make public, the DPN gives a valuable insight while staying rather focused on the project as a whole."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>COMMUNITY</emphasis> The publicity and press teams"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Debian's official communication channels are managed by volunteers of the Debian publicity team and of the press team. Members of the latter are delegates of the Debian Project Leader and handle official press releases. The publicity team is much less formal and welcomes contributions from everybody, be it to write articles for “Debian Project News” or to animate the <emphasis>@debian</emphasis> Identi.ca microblogging account. <ulink type=\"block\" url=\"http://wiki.debian.org/Teams/Press\" /> <ulink type=\"block\" url=\"http://wiki.debian.org/Teams/Publicity\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid "For more information about the evolution of Debian and what is happening at some point in time in various teams, there's also the <email>debian-devel-announce@lists.debian.org</email> list. As its name implies, the announcements it carries will probably be more interesting to developers, but it also allows interested parties to keep an eye on what happens in more concrete terms than just when a stable version is released. While <email>debian-announce</email> gives news about the user-visible results, <email>debian-devel-announce</email> gives news about how these results are produced. As a side note, “d-d-a” (as it is sometimes referred to) is the only list that Debian developers must be subscribed to."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Planet Debian</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "A more informal source of information can also be found on Planet Debian, which aggregates articles posted by Debian contributors on their respective blogs. While the contents do not deal exclusively with Debian development, they provide a view into what is happening in the community and what its members are up to. <ulink type=\"block\" url=\"http://planet.debian.org/\" />"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>microblog</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Identi.ca</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Twitter</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Facebook</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Google+</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>social networks</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>network</primary><secondary>social networks</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The project is also well represented on social networks. While Debian only has an official presence on platforms built with free software (like the Identi.ca microblogging platform, powered by <emphasis>pump.io</emphasis>), there are many Debian contributors who are animating Twitter accounts, Facebook pages, Google+ pages, and more. <ulink type=\"block\" url=\"https://identi.ca/debian\" /> <ulink type=\"block\" url=\"https://twitter.com/debian\" /> <ulink type=\"block\" url=\"https://www.facebook.com/debian\" /> <ulink type=\"block\" url=\"https://plus.google.com/111711190057359692089\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Role of Distributions"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Linux distribution</primary><secondary>role</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "A GNU/Linux distribution has two main objectives: install a free operating system on a computer (either with or without an existing system or systems), and provide a range of software covering all of the users' needs."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Installer: <command>debian-installer</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The <command>debian-installer</command>, designed to be extremely modular in order to be as generic as possible, targets the first objective. It covers a broad range of installation situations and in general, greatly facilitates the creation of a derivative installer corresponding to a particular case."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This modularity, which also makes it very complex, may be daunting for the developers discovering this tool; but whether used in graphical or text mode, the user's experience is still similar. Great efforts have been made to reduce the number of questions asked at installation time, in particular thanks to the inclusion of automatic hardware detection software."
msgstr ""

#. Tag: para
#, no-c-format
msgid "It is interesting to note that distributions derived from Debian differ greatly on this aspect, and provide a more limited installer (often confined to the i386 or amd64 architectures), but more user-friendly for the uninitiated. On the other hand, they usually refrain from straying too far from package contents in order to benefit as much as possible from the vast range of software offered without causing compatibility problems."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Software Library"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Quantitatively, Debian is undeniably the leader in this respect, with over 17,300 source packages. Qualitatively, Debian’s policy and long testing period prior to releasing a new stable version justify its reputation for stability and consistency. As far as availability, everything is available on-line through many mirrors worldwide, with updates pushed out every six hours."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Many retailers sell CD-ROMs on the Internet at a very low price (often at cost), the “images” for which are freely available for download. There is only one drawback: the low frequency of releases of new stable versions (their development sometimes takes more than two years), which delays the inclusion of new software."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Most new free software programs quickly find their way into the development version which allows them to be installed. If this requires too many updates due to their dependencies, the program can also be recompiled for the stable version of Debian (see <xref linkend=\"debian-packaging\" /> for more information on this topic)."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Lifecycle of a Release"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>lifecycle</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Unstable</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Testing</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Stable</emphasis></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><emphasis role=\"distribution\">Experimental</emphasis></primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The project will simultaneously have three or four different versions of each program, named <emphasis role=\"distribution\">Experimental</emphasis>, <emphasis role=\"distribution\">Unstable</emphasis>, <emphasis role=\"distribution\">Testing</emphasis>, and <emphasis role=\"distribution\">Stable</emphasis>. Each one corresponds to a different phase in development. For a good understanding, let us take a look at a program's journey, from its initial packaging to inclusion in a stable version of Debian."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>VOCABULARY</emphasis> Release"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>release</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The term “release”, in the Debian project, indicates a particular version of a distribution (e.g., “unstable release” means “the unstable version”). It also indicates the public announcement of the launch of any new version (stable)."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The <emphasis role=\"distribution\">Experimental</emphasis> Status"
msgstr ""

#. Tag: para
#, no-c-format
msgid "First let us take a look at the particular case of the <emphasis role=\"distribution\">Experimental</emphasis> distribution: this is a group of Debian packages corresponding to the software currently in development, and not necessarily completed, explaining its name. Not everything passes through this step; some developers add packages here in order to get feedback from more experienced (or braver) users."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Otherwise, this distribution frequently houses important modifications to base packages, whose integration into <emphasis role=\"distribution\">Unstable</emphasis> with serious bugs would have critical repercussions. It is, thus, a completely isolated distribution, its packages never migrate to another version (except by direct, express intervention of the maintainer or the ftpmasters). It is also not self-contained: only a subset of the existing packages are present in <emphasis role=\"distribution\">Experimental</emphasis>, and it generally does not include the base system. This distribution is therefore mostly useful in combination with another, self-contained, distribution such as <emphasis role=\"distribution\">Unstable</emphasis>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The <emphasis role=\"distribution\">Unstable</emphasis> Status"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Let us turn back to the case of a typical package. The maintainer creates an initial package, which they compile for the <emphasis role=\"distribution\">Unstable</emphasis> version and place on the <literal>ftp-master.debian.org</literal> server. This first event involves inspection and validation from the ftpmasters. The software is then available in the <emphasis role=\"distribution\">Unstable</emphasis> distribution, which is the “cutting edge” distribution chosen by users who are more concerned with having up to date packages than worried about serious bugs. They discover the program and then test it."
msgstr ""

#. Tag: para
#, no-c-format
msgid "If they encounter bugs, they report them to the package's maintainer. The maintainer then regularly prepares corrected versions, which they upload to the server."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Every newly updated package is updated on all Debian mirrors around the world within six hours. The users then test the corrections and search for other problems resulting from the modifications. Several updates may then occur rapidly. During these times, autobuilder robots come into action. Most frequently, the maintainer has only one traditional PC and has compiled his package on the amd64 (or i386) architecture; the autobuilders take over and automatically compile versions for all the other architectures. Some compilations may fail; the maintainer will then receive a bug report indicating the problem, which is then to be corrected in the next versions. When the bug is discovered by a specialist for the architecture in question, the bug report may come with a patch ready to use."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>autobuilder</primary>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Compilation of a package by the autobuilders"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>QUICK LOOK</emphasis> <command>buildd</command>, the Debian package recompiler"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>buildd</command></primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>build daemon</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<emphasis>buildd</emphasis> is the abbreviation of “build daemon”. This program automatically recompiles new versions of Debian packages on the architectures on which it is hosted (cross-compiling not always being sufficient) ."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Thus, to produce binaries for the <literal>sparc</literal> architecture, the project has <literal>sparc</literal> machines available (specifically, Sun brand). The <emphasis>buildd</emphasis> program runs on them continuously and creates binary packages for <literal>sparc</literal> from source packages sent by Debian developers."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This software is used on all the computers serving as autobuilders for Debian. By extension, the term <emphasis>buildd</emphasis> frequently is used to refer to these machines, which are generally reserved solely for this purpose."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Migration to <emphasis role=\"distribution\">Testing</emphasis>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "A bit later, the package will have matured; compiled on all the architectures, it will not have undergone recent modifications. It is then a candidate for inclusion in the <emphasis role=\"distribution\">Testing</emphasis> distribution — a group of <emphasis role=\"distribution\">Unstable</emphasis> packages chosen according to some quantifiable criteria. Every day a program automatically selects the packages to include in <emphasis role=\"distribution\">Testing</emphasis>, according to elements guaranteeing a certain level of quality:"
msgstr ""

#. Tag: para
#, no-c-format
msgid "lack of critical bugs, or, at least fewer than the version currently included in <emphasis role=\"distribution\">Testing</emphasis>;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "at least 10 days spent in <emphasis role=\"distribution\">Unstable</emphasis>, which is sufficient time to find and report any serious problems;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "successful compilation on all officially supported architectures;"
msgstr ""

#. Tag: para
#, no-c-format
msgid "dependencies that can be satisfied in <emphasis role=\"distribution\">Testing</emphasis>, or that can at least be moved there together with the package in question."
msgstr ""

#. Tag: para
#, no-c-format
msgid "This system is clearly not infallible; critical bugs are regularly found in packages included in <emphasis role=\"distribution\">Testing</emphasis>. Still, it is generally effective, and <emphasis role=\"distribution\">Testing</emphasis> poses far fewer problems than <emphasis role=\"distribution\">Unstable</emphasis>, being for many, a good compromise between stability and novelty."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>NOTE</emphasis> Limitations of <emphasis role=\"distribution\">Testing</emphasis>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "While very interesting in principle, <emphasis role=\"distribution\">Testing</emphasis> does have some practical problems: the tangle of cross-dependencies between packages is such that a package can rarely move there completely on its own. With packages all depending upon each other, it is sometimes necessary to migrate a large number of packages simultaneously, which is impossible when some are uploading updates regularly. On the other hand, the script identifying the families of related packages works hard to create them (this would be an NP-complete problem, for which, fortunately, we know some good heuristics). This is why we can manually interact with and guide this script by suggesting groups of packages, or imposing the inclusion of certain packages in a group, even if this temporarily breaks some dependencies. This functionality is accessible to the Release Managers and their assistants."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Recall that an NP-complete problem is of an exponential algorithmic complexity according to the size of the data, here being the length of the code (the number of figures) and the elements involved. The only way to resolve it is frequently to examine all possible configurations, which could require enormous means. A heuristic is an approximate, but satisfying, solution."
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>COMMUNITY</emphasis> The Release Manager"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Release Manager</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Stable Release Manager</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Release Manager is an important title, associated with heavy responsibilities. The bearer of this title must, in effect, manage the release of a new, stable version of Debian, and define the process for development of <emphasis role=\"distribution\">Testing</emphasis> until it meets the quality criteria for <emphasis role=\"distribution\">Stable</emphasis>. They also define a tentative schedule (not always followed)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "We also have Stable Release Managers, often abbreviated SRM, who manage and select updates for the current stable version of Debian. They systematically include security patches and examine all other proposals for inclusion, on a case by case basis, sent by Debian developers eager to update their package in the stable version."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The Promotion from <emphasis role=\"distribution\">Testing</emphasis> to <emphasis role=\"distribution\">Stable</emphasis>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Let us suppose that our package is now included in <emphasis role=\"distribution\">Testing</emphasis>. As long as it has room for improvement, its maintainer must continue to improve it and restart the process from <emphasis role=\"distribution\">Unstable</emphasis> (but its later inclusion in <emphasis role=\"distribution\">Testing</emphasis> is generally faster: unless it changed significantly, all of its dependencies are already available). When it reaches perfection, the maintainer has completed their work. The next step is the inclusion in the <emphasis role=\"distribution\">Stable</emphasis> distribution, which is, in reality, a simple copy of <emphasis role=\"distribution\">Testing</emphasis> at a moment chosen by the Release Manager. Ideally this decision is made when the installer is ready, and when no program in <emphasis role=\"distribution\">Testing</emphasis> has any known critical bugs."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Since this moment never truly arrives, in practice, Debian must compromise: remove packages whose maintainer has failed to correct bugs on time, or agree to release a distribution with some bugs in the thousands of programs. The Release Manager will have previously announced a freeze period, during which each update to <emphasis role=\"distribution\">Testing</emphasis> must be approved. The goal here is to prevent any new version (and its new bugs), and to only approve updates fixing bugs."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A package's path through the various Debian versions"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>VOCABULARY</emphasis> Freeze: the home straight"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>freeze</primary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "During the freeze period, development of the <emphasis role=\"distribution\">Testing</emphasis> distribution is blocked; no more automatic updates are allowed. Only the Release Managers are then authorized to change packages, according to their own criteria. The purpose is to prevent the appearance of new bugs by introducing new versions; only thoroughly examined updates are authorized when they correct significant bugs."
msgstr ""

#. Tag: para
#, no-c-format
msgid "After the release of a new stable version, the Stable Release Manager manages all further development (called “revisions”, ex: 5.0.1, 5.0.2, 5.0.3 for version 5.0). These updates systematically include all security patches. They will also include the most important corrections (the maintainer of a package must prove the gravity of the problem that they wish to correct in order to have their updates included)."
msgstr ""

#. Tag: para
#, no-c-format
msgid "At the end of the journey, our hypothetical package is now included in the stable distribution. This journey, not without its difficulties, explains the significant delays separating the Debian Stable releases. This contributes, over all, to its reputation for quality. Furthermore, the majority of users are satisfied using one of the three distributions simultaneously available. The system administrators, concerned above all about the stability of their servers, don't need the latest and greatest version of GNOME; they can choose Debian <emphasis role=\"distribution\">Stable</emphasis>, and they will be satisfied. End users, more interested in the latest versions of GNOME or KDE than in rock-solid stability, will find Debian <emphasis role=\"distribution\">Testing</emphasis> to be a good compromise between a lack of serious problems and relatively up to date software. Finally, developers and more experienced users may blaze the trail, testing all the latest developments in Debian <emphasis role=\"distribution\">Unstable</emphasis> right out of the gate, at the risk of suffering the headaches and bugs inherent in any new version of a program. To each their own Debian!"
msgstr ""

#. Tag: title
#, no-c-format
msgid "<emphasis>CULTURE</emphasis> GNOME and KDE, graphical desktop environments"
msgstr ""

#. Tag: para
#, no-c-format
msgid "GNOME (GNU Network Object Model Environment) and KDE (K Desktop Environment) are the two most popular graphical desktop environments in the free software world. A desktop environment is a set of programs grouped together to allow easy management of the most common operations through a graphical interface. They generally include a file manager, office suite, web browser, e-mail program, multimedia accessories, etc. The most visible difference resides in the choice of the graphical library used: GNOME has chosen GTK+ (free software licensed under the LGPL), and KDE has selected Qt (a company-backed project, available nowadays both under the GPL and a commercial license). <ulink type=\"block\" url=\"http://www.gnome.org/\" /> <ulink type=\"block\" url=\"http://www.kde.org/\" />"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Chronological path of a program packaged by Debian"
msgstr ""