[Blends-commit] [SCM] blends-dev branch, master, updated. 29c85db4e2875f4407976fac2d24894aa01690dc
Andreas Tille
tille at debian.org
Sun Nov 24 17:34:08 UTC 2013
The following commit has been merged in the master branch:
commit 29c85db4e2875f4407976fac2d24894aa01690dc
Author: Andreas Tille <tille at debian.org>
Date: Sun Nov 24 18:33:30 2013 +0100
Fix links to commit statistics graphs and add more links of team metrics
diff --git a/doc/en/02_about.sgml b/doc/en/02_about.sgml
deleted file mode 100644
index 829ec0e..0000000
--- a/doc/en/02_about.sgml
+++ /dev/null
@@ -1,329 +0,0 @@
-<chapt id="about">
- <heading>What are Debian Pure Blends?</heading>
-
- <sect id="debian">
- <heading>What is Debian?</heading>
-
-<p>
- The core of an operating system is a piece of software that interacts
- with the hardware of the computer, and provides basic functionality
- for several applications. On Linux based systems, the so-called
- kernel provides this functionality, and the term Linux just means
- this core without those applications that provide the functionality
- for users. Other examples are the Hurd, or the flavours of the BSD
- kernel.
-</p>
-<p>
- Many applications around UNIX-like kernels are provided by the <url
- id="http://www.gnu.org/" name="GNU"> system. That is why Linux based
- operating systems are described as GNU/Linux systems. The GNU tools
- around the Linux kernel build a complete operating system.
-</p>
-<p>
- Users do not need only an operating system. They also need certain
- applications like web servers, or office suites. A
- <em>distribution</em> is a collection of software packages around the
- GNU/Linux operating system that satisfies the needs of the target
- user group. There are general distributions, which try to support
- all users, and there are several specialised distributions, which
- each target a special group of users.
-</p>
-<p>
- <em>Distributors</em> are those companies that are building these
- collections of software around the GNU/Linux operating system.
- Because it is Free Software, the user who buys a distribution pays
- for the service that the distributor is providing. These services
- might be:
- <list>
- <item>Preparing a useful collection of software around GNU/Linux.</item>
- <item>Caring for smooth installation that the target user is able to
- manage.</item>
- <item>Providing software updates and security fixes.</item>
- <item>Writing documentation and translations to enable the user to use
- the distribution with maximum effect.</item>
- <item>Selling Boxes with ready to install CDs and printed
- documentation.</item>
- <item>Offering training and qualification.</item>
- </list>
-</p>
-<p>
- Most distributors ship their distribution in binary packages. Two
- package formats are widely used:
- <taglist>
- <tag>RPM (RedHat Package Manager)</tag>
- <item>which is supported by RedHat, SuSE, Mandriva and others.
- <tag>DEB (Debian Package)</tag>
- <item>used by Debian and derived distributions.
- </item>
- </taglist>
- All GNU/Linux distributions have a certain amount of common ground,
- and the <url id="http://www.linuxbase.org/" name="Linux Standard
- Base"> (LSB) is attempting to develop and promote a set of standards
- that will increase compatibility among Linux distributions, and enable
- software applications to run on any compliant system.
-</p>
-<p>
- The very essence of any distribution, (whether delivered as RPMs, DEBs,
- Source tarballs or ports) is the choice of <em>policy statements</em>
- made (or not made, as the case may be) by the creators of the distribution.
-</p>
-<p>
- <em>Policy statements</em> in this sense are things like
- "configuration files live in
- <file>/etc/$package/$package.conf</file>, logfiles go to
- <file>/var/log/$package/$package.log</file> and the documentation
- files can be found in <file>/usr/share/doc/$package</file>."
-</p>
-<p>
- The policy statements are followed by the tool-chains and
- libraries used to build the software, and the lists of dependencies, which
- dictate the prerequisites and order in which the software has to be
- built and installed. (It's easier to ride a bicycle if you put the wheels
- on first. ;-) )
-</p>
-<p>
- It is this <em>adherence to policy</em> that causes a distribution
- to remain consistent within its own bounds. At the same time, this is
- the reason why packages can not always be safely installed across
- distribution boundaries. A SuSE <file>package.rpm</file> might not
- play well with a RedHat <file>package.rpm</file>, although the
- packages work perfectly well within their own distributions. A
- similar compatability problem could also apply to packages from the
- same distributor, but from a different version or generation of the
- distribution.
-</p>
-<p>
-<comment>AT: The context is somehow missing here.</comment>
- As you will see later in more detail, Debian Pure Blends are
- just a modified ruleset for producing a modified (specialised)
- version of Debian GNU/Linux.
-</p>
-<p>
- A package management system is a very strong tool to manage software
- packages on your computer. A large amount of the work of a
- distributor is building these software packages.
-</p>
-<p>
- Distributors you might know are
- <url name="Mandriva" id="http://www.mandriva.com/">,
- <url name="RedHat" id="http://www.redhat.com/">,
- <url name="SuSE" id="http://www.suse.com/">
- (now owned by <url name="Novell" id="http://www.novell.com/linux/">)
- and others.
-</p>
-<p>
- <url id="http://www.debian.org" name="Debian"> is just one of them.
-</p>
-
-<p>
-Well, at least this is what people who do not know Debian well might
-think about it. But, in fact, Debian is a different kind of
-distribution ...
-</p>
-</sect>
-
-<sect id="whatdebian">
- <heading>What is Debian? (next try)</heading>
-
-<p>
-The Debian Project is an association of individuals who have made
-common cause to create a free operating system. This operating system
-that we have created is called <strong>Debian GNU/Linux</strong>,
-or simply Debian for short.
-</p>
-<p>
-Moreover, work is in progress to provide Debian of kernels other than
-Linux, primarily for the Hurd. Other possible kernels are the
-flavours of BSD, and there are even people who think about ports to MS
-Windows.
-</p>
-<p>
-All members of the Debian project are connected in a <url name ="web of
-trust" id="http://people.debian.org/~tille/talks/img/earthkeyring.png">,
-which is woven by signing GPG keys. One requirement to become a
-member of the Debian project is to have a GPG key signed by a Debian
-developer. Every time one Debian developer meets another developer
-for the first time, they sign each other's keys. In this way, the web
-of trust is woven.
-</p>
-</sect>
-
-<sect id="difference">
- <heading>Differences from other distributions</heading>
-
-<p>
-<list>
- <item>Debian is not a company, but an organisation.</item>
- <item>It does not sell anything.</item>
- <item>Debian members are volunteers.</item>
- <item>Maintainers are working on the common goal:
- to build the best operating system they can achieve.</item>
- <item>Debian maintains the largest collection of ready-to-install Free
- Software on the Internet.</item>
- <item>There are two ways to obtain Debian GNU/Linux:
- <enumlist>
- <item>Buy it from some <em>other</em> distributor on
- CD. Perhaps the correct term would be
- <em>re</em>distributor. Because Debian is free, anybody can
- build his own distribution based on it, sell CDs, and even
- add new features, such as printed documentation, more software,
- support for different installers and more.
- </item>
- <item>Download Debian from the web for free.</item>
- </enumlist>
- The latter is the common way, and there are really great tools
- to do it this way. Certainly it is always possible to copy Debian
- from a friend.
- </item>
-</list>
-</p>
- </sect>
-
-<sect id="Blends">
- <heading>Debian Pure Blends</heading>
-
-<p>
-Debian contains nearly 22.000 binary packages, and this number is
-constantly increasing. There is no single user who needs all these
-packages (even if conflicting packages are not considered).
-</p>
-<p>The normal user is interested in a subset of these packages. But
-how does the user find out which packages are really interesting?
-</p>
-<p>
-One solution is provided by the <package>tasksel</package> package.
-It provides a reasonable selection of quite general tasks that can be
-accomplished using a set of packages installed on a Debian GNU/Linux
-system. But this is not really fine grained, and does not address all
-of the needs of user groups with special interests.
-</p>
-<p>
-<em>Debian Pure Blends</em> - in short Blends if used clearly in the
-Debian internal context which makes "Pure" and "Debian" obvious -
-which were formerly known as Custom Debian Distributions (this name
-was confusing because it left to much room for speculation that this
-might be something else than Debian) try to provide a solution for
-<em>special groups of target users with different skills and
-interests</em>. Not only do they provide handy collections of specific
-program packages, but they also ease installation and configuration
-for the intended purpose.
-</p>
-<p>
-Debian Pure Blends are <strong>not forks</strong> from Debian. As the
-new name says clearly they are pure Debian and just provide a specific
-flavour. So if you obtain the complete Debian GNU/Linux distribution,
-you have all available Debian Pure Blends included.
-</p>
-<p>
-The concept of what is called <em>Blend</em> in Debian is also known
-in other distributions. For instance in Fedora there are
-<url id="http://fedoraproject.org/wiki/SIGs" name="Special Interest Groups (SIGs)">
-even if some SIGs in Fedora are what in Debian is known as interntal
-project because it is focussed on technical implementetions and not
-on user oriented applications.
-</p>
-</sect>
-
-<sect>
- <heading>Difference between a Blend and a remastered system</heading>
-
-<p>
-Not necessarily all currently existing Blends are actually providing
-installation media (live media or installer). The reason for this is
-that such installation media are not always necessary / wanted. You
-can just install plain Debian and install some metapackages on top of it.
-However, the metapackage approach makes the creation of installation
-media quite simple by using
-<url id="http://live.debian.net/" name="Debian Live">.
-Here are some reasons for this approach compared to a remastering
-strategy.
-</p>
-
-<sect1>
-<heading>Technical</heading>
-<p>
-The process for creation of a blend involves starting with a Debian or
-derivative repository and creating an image directly from that (live,
-install or otherwise) that contains a selection of material from that
-repository delivered in such a way that it is usable by a particular
-target user for a particular purpose with a minimum of effort.
-</p>
-<p>
-By contrast, the process of remastering generally involves first
-downloading an image produced by the parent distro (live, install or
-otherwise,) then tearing it apart and reassembling it with your
-customizations applied.
-</p>
-</sect1>
-
-<sect1>
-<heading>Philosophical</heading>
-<p>
-The blends philosophy is to work as closely with the parent distro as
-possible. If possible, the project should be done entirely within the
-distro as a subproject, containing only material supplied by the parent
-distro. We call this a "Pure Blend".
-</p>
-<p>
-The remastering philosophy (if it can be called that) seems to be
-"whatever works" and involves little or no interaction with the parent
-distro. It's a lazy approach used by people who have newly discovered
-that they can hack images to make them into custom images to make
-something uniquely theirs. Probably fine for quick-and-dirty results,
-but hard to support in the long run.
-</p>
-<p>
-The users of a blend are served better than the users of a
-remaster because of the following advantages:
-</p>
-
-<sect2>
-<heading>Technical advantage</heading>
-<p>
-A new version of a well-crafted blend ought to be able to be produced at
-any time directly from the repository simply by building it; the user
-has some assurance that the resulting system remains 'untainted' by
-hacking it up with scripts that 'damage' the original system by removing
-files from packages, changing files in packages, etc. something that
-hurts maintainability / support for such a system.
-</p>
-</sect2>
-
-<sect2>
-<heading>Community advantage</heading>
-<p>
-A blend project aims to leverage support resources from the existing
-community to serve some sub-community within it. They accomplish this by
-not violating Debian packaging policy, producing something that is
-either pure Debian (a "pure blend") or Debian + additional packages,
-rather than some frankendistro artlessly stitched together from someone
-else's distro with scripts that change things everywhere with no regard
-to policy. Thus, normal support channels can be used with a pure blend
-since what you end up with is not a derivative at all, but just Debian,
-set up and ready to go for whatever you wanted to use it for.
-</p>
-</sect2>
-
-</sect1>
-
-</sect>
-
-</chapt>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
-sgml-exposed-tags:nil
-sgml-local-catalogs:nil
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/en/04_existing_blends.sgml b/doc/en/04_existing_blends.sgml
deleted file mode 100644
index f4971e2..0000000
--- a/doc/en/04_existing_blends.sgml
+++ /dev/null
@@ -1,543 +0,0 @@
-<chapt id="existing">
- <heading>Existing Debian Pure Blends</heading>
-
- <sect id="debian-jr">
- <heading>Debian Junior: Debian for children from 1 to 99</heading>
-
-<p>
-<taglist>
- <tag>Start</tag>
- <item>beginning of 2000</item>
- <tag>URL</tag>
- <item><url name="Debian Jr." id="http://www.debian.org/devel/debian-jr"></item>
- <tag>Tasks</tag>
- <item><url name="Tasks of Debian Jr." id="http://blends.alioth.debian.org/junior/tasks"></item>
- <tag>Mailing list</tag>
- <item><url name=" debian-jr at lists.debian.org" id="http://lists.debian.org/debian-jr/"></item>
- <tag>Initiator</tag>
- <item>Ben Armstrong <email>synrg at debian.org</email></item>
- <tag>Activity</tag>
- <item><url name="Activists on Debian Jr. mailing list" id="http://blends.debian.net/liststats/authorstat_debian-jr.png"></item>
- <tag>Release</tag>
- <item>Debian 3.0 (Woody)</item>
- <tag>Goals</tag>
- <item>
- <list>
- <item>To make Debian an OS that children of all ages will <em>want</em>
- to use, preferring it over the alternatives.</item>
- <item>To care for those applications in Debian suitable for children,
- and ensure their quality, to the best of our abilities.
- <item>To make Debian a playground for children's enjoyment and
- exploration.</item>
- </list>
- </item>
-
-</taglist>
-The main target is young children. By the time children are teenaged, they
-should be comfortable with using Debian without any special modifications.
-</p>
-<p>
-Debian Jr. was the first Blend. In fact, at the time this project was
-created, the idea behind of Debian Pure Blends was born, although
-then, we used the term "Debian Internal Project". Over time, this
-name was changed to "Custom Debian Distributions" first because it was
-too broad, as it was equally descriptive of a number of quite
-different projects, such as IPv6 and QA. The next change of names
-became necessary when it was realised that the term "Custom Debian
-Distribution" was considered as "something else than Debian" by any
-newcomer. This was so misleading that it effectively blocked a wide
-propagation of the principle.
-</p>
-<p>
-Debian Jr. not only provides games, but is also concerned about their
-quality from a child's perspective. Thus, games that are regarded as
-not well suited to young children are omitted. Moreover, choices are
-made about which packages are best suited for children to use for
-various other activities and tasks that interest them. This includes,
-for example, simple text processing, web browsing and drawing.
-</p>
-</sect>
-
-
- <sect id="debian-med">
- <heading>Debian Med: Debian in Health Care</heading>
-
-<p>
-<taglist>
- <tag>Start</tag>
- <item><url name="beginning of 2002" id="http://lists.debian.org/debian-devel/2002/01/msg01730.html"></item>
- <tag>URL</tag>
- <item><url name="Debian Med" id="http://www.debian.org/devel/debian-med"></item>
- <tag>Tasks</tag>
- <item><url name="Tasks of Debian Med" id="http://debian-med.alioth.debian.org/tasks"></item>
- <tag>Mailing list</tag>
- <item><url name=" debian-med at lists.debian.org" id="http://lists.debian.org/debian-med/"></item>
- <tag>Initiator</tag>
- <item>Andreas Tille <email>tille at debian.org</email></item>
- <tag>Activity</tag>
- <item>
- <p><url name="Activists on Debian Med mailing list" id="http://blends.debian.net/liststats/authorstat_debian-med.png"></p>
- <p><url name="Activists on Debian Med developer list" id="http://blends.debian.net/liststats/authorstat_debian-med-packaging.png"></p>
- <!-- authorstats not available
- <p><url name="Activists on Debian Med commit list" id="http://blends.debian.net/liststats/authorstat_debian-med-commit.png"></p>
- //-->
- </item>
- <tag>Release</tag>
- <item>Sarge</item>
- <tag>Goals</tag>
- <item>
- <list>
- <item>To build an integrated software environment for all medical tasks.</item>
- <item>To care especially for the quality of program packages in the field of medicine
- that are already integrated within Debian.</item>
- <item>To build and include in Debian packages of medical software that are missing
- in Debian.</item>
- <item>To care for a general infrastructure for medical users.</item>
- <item>To make efforts to increase the quality of third party Free Software
- in the field of medicine.</item>
- </list>
- </item>
-</taglist>
-
-</sect>
-
- <sect id="debian-edu">
- <heading>Debian Edu: Debian for Education</heading>
-
-<p>
-<taglist>
- <tag>Start</tag>
- <item>Summer of 2002, since 2003 merged with SkoleLinux, which is now
- synonymous with Debian Edu</item>
- <tag>URL</tag>
- <item><url name="Debian Edu Wiki"
- id="http://wiki.debian.org/DebianEdu"></item>
- <tag>Tasks</tag>
- <item><url name="Tasks of Debian Edu" id="http://blends.alioth.debian.org/edu/tasks"></item>
- <tag>Mailing list</tag>
- <item><url name=" debian-edu at lists.debian.org" id="http://lists.debian.org/debian-edu/"></item>
- <tag>Activity</tag>
- <item><url name="Activists on Debian Edu mailing list" id="http://blends.debian.net/liststats/authorstat_debian-edu.png"></item>
- <tag>Responsible</tag>
- <item>Petter Reinholdtsen <email>pere at hungry.com</email></item>
- <tag>Release</tag>
- <item>Sarge</item>
- <tag>Goals</tag>
- <item>
- <list>
- <item>To make Debian the best distribution available for educational
- use.</item>
- <item>Provide a ready to run classroom installation with free
- educational software. An automatically installed server
- provides net-boot services for disk-less thin clients and
- all necessary applications for educational use.</item>
- <item>To federate many initiatives around education, which are
- partly based on forks of Debian.</item>
- <item>To continue the internationalisation efforts of SkoleLinux.
- </item>
- <item>To focus on easy installation in schools.</item>
- <item>To cooperate with other education-related projects (like
- <url id="http://schoolforge.net/" name="Schoolforge">,
- <url id="http://www.ofset.org/" name="Ofset">,
- <url id="http://edu.kde.org/" name="KdeEdu">).</item>
- </list>
- </item>
-</taglist>
-
-This project started with the intention to bring back into Debian a fork from
-Debian that was started by some people in France. Because they had some
-time constraints, the people who initially started this effort
-handed over responsibility to the Norwegian <url name="Skolelinux"
-id="http://www.skolelinux.org">, which is currently more or less
-identical to Debian Edu.
-</p>
-<p>
-The Debian Edu project gathered special interest in Spain because
-there are derived Debian distributions from this country that are
-intended to be used in schools. For instance there are:
- <taglist>
- <tag><url id="http://www.linex.org/" name="LinEX"></tag>
- <item><p>A Debian derivative distribution used in all schools in
- Extremadura.</p>
- <p>Currently they are joining Debian Edu and by doing so
- becoming fully integrated into Debian. This is a really
- important move because it brings a lot of good software and
- experience back into Debian.
- </p>
- </item>
- </taglist>
-</p>
-</sect>
-
- <sect id="demudi">
- <heading>Debian Multimedia</heading>
-
-<p>
-<taglist>
- <tag>Start</tag>
- <item>
- <p>In 2004 there was and effort by DeMuDi to become a Blend but
- this effort seems to have stalled. DeMuDi was part of the
- <url name="Agnula" id="http://www.agnula.org/"> project
- (founded by European Community) and the work somehow was
- taken over by the 64 studio project.
- </p>
- <p>At DebConf 10 in the
- <url name="Debian Multimdia BOF" id="http://penta.debconf.org/dc10_schedule/events/670.en.html">
- a decision was made to use the Blends stuff for rendering
- web sentinel pages. It was furtherly mentioned that the
- people driving DeMuDi joined the Debian Multimedia packaging
- team so there is now an unique effort to tackle multimedia
- relevant packages.
- </p>
- </item>
- <tag>URL</tag>
- <item><url name="Debian Multimedia" id="http://wiki.debian.org/DebianMultimedia">
- </item>
- <tag>Tasks</tag>
- <item><url name="Tasks of Debian Multimedia" id="http://blends.alioth.debian.org/multimedia/tasks"></item>
- <tag>Activity</tag>
- <item>
- <p><url name="Activists on Debian Multimedia maintainers mailing list" id="http://blends.debian.net/liststats/authorstat_pkg-multimedia-maintainers.png"></p>
- <!-- authorstat not availble
- <p><url name="Activists on Debian Multimedia commits mailing list" id="http://blends.debian.net/liststats/authorstat_pkg-multimedia-commits.png"></p>
- //-->
- <p><url name="Activists on Debian Multimedia user mailing list" id="http://blends.debian.net/liststats/authorstat_debian-multimedia.png"></p>
- </item>
- <tag>Responsible</tag>
- <item>Reinhard Tartler<email>siretart at tauware.de</email></item>
- <tag>Goals</tag>
- <item>
- <list>
- <item>Oriented toward audio and video</item>
- <item>To make GNU/Linux a platform of choice for the musician
- and the multimedia artist.</item>
- <item>Join multimedia forces inside Debian</item>
- </list>
- </item>
-</taglist>
-</p>
-</sect>
-
-<sect id="debian-gis">
- <heading>Debian GIS: Geographical Information Systems</heading>
-<p>
-<taglist>
- <tag>Start</tag>
- <item><url name="October 2004" id="http://lists.debian.org/debian-devel-announce/2004/10/msg00007.html"</item>
- <tag>URL</tag>
- <item><url name="DebianGIS Wiki"
- id="http://wiki.debian.org/DebianGis"></item>
- <tag>Tasks</tag>
- <item><url name="Tasks of Debian GIS" id="http://blends.alioth.debian.org/gis/tasks"></item>
- <tag>Mailing list</tag>
- <item><url name="user and developer list" id="http://wiki.debian.org/DebianGis/MailingLists"></item>
- <tag>Activity</tag>
- <item><url name="Activists on Debian GIS mailing list" id="http://blends.debian.net/liststats/authorstat_debian-gis.png"></item>
- <tag>Initiator</tag>
- <item>Francesco P. Lovergine <email>frankie at debian.org</email></item>
- <tag>Goals</tag>
- <item>
- <list>
- <item>Geographical Information Systems</item>
- <item><url name="OpenStreetMap" id="http://www.openstreetmap.org"> and GPS devices</item>
- </list>
- </item>
-</taglist>
-</p>
-</sect>
-
-<sect id="debichem">
- <heading>DebiChem: Debian for Chemistry</heading>
-
-<p>
-<taglist>
- <tag>Start</tag>
- <item>October 2004</item>
- <tag>URL</tag>
- <item><url name="Debichem Alioth page"
- id="http://alioth.debian.org/projects/debichem/"></item>
- <tag>Tasks</tag>
- <item><url name="Tasks of DebiChem" id="http://blends.alioth.debian.org/debichem/tasks"></item>
- <tag>Mailing list</tag>
- <item><url name="debichem-users at lists.alioth.debian.org" id="http://lists.alioth.debian.org/mailman/listinfo/debichem-users"></item>
- <tag>Activity</tag>
- <item>
- <p><url name="Activists on DebiChem mailing list" id="http://blends.debian.net/liststats/authorstat_debichem-devel.png"></p>
- <!-- authorstat not available
- <p><url name="Activists on DebiChem commits list" id="http://blends.debian.net/liststats/authorstat_debichem-commits.png"></p>
- //-->
- </item>
- <tag>Initiator</tag>
- <item>Michael Banck <email>mbanck at debian.org</email></item>
- <tag>Goals</tag>
- <item>
- <list>
- <item>Chemical applications in Debian</item>
- </list>
- </item>
-</taglist>
-</p>
-
-</sect>
-
-<sect id="debian-science">
- <heading>Debian Science: Debian for science</heading>
-
-<p>
-<taglist>
- <tag>Start</tag>
- <item><url name="July 2005" id="http://lists.debian.org/debian-devel/2005/07/msg01555.html"></item>
- <tag>URL</tag>
- <item><url name="Debian Science Wiki"
- id="http://wiki.debian.org/DebianScience"></item>
- <tag>Tasks</tag>
- <item><url name="Tasks of Debian Science" id="http://blends.alioth.debian.org/science/tasks"></item>
- <tag>Mailing list</tag>
- <item><url name="debian-science at lists.debian.org" id="http://lists.debian.org/debian-science/"></item>
- <tag>Activity</tag>
- <item>
- <p><url name="Activists on Debian Science mailing list" id="http://blends.debian.net/liststats/authorstat_debian-science.png"></p>
- <p><url name="Activists on Debian Science maintainers list" id="http://blends.debian.net/liststats/authorstat_debian-science-maintainers.png"></p>
- <!-- authorstat not available
- <p><url name="Activists on Debian Science commits list" id="http://blends.debian.net/liststats/authorstat_debian-science-commits.png"></p>
- //-->
- </item>
- <tag>Responsible</tag>
- <item>Sylvestre Ledru <email>sylvestre at debian.org</email></item>
-</taglist>
-</p>
-
-<p>
- While there are Debian Pure Blends that care for certain sciences
- (Debian Med deals in a main part with Biology, DebiChem for
- Chemistry and Debian GIS for geography) not all sciences are covered
- by a specific Blend. The main reason is that at the moment not
- enough people support such an effort for every science. The
- temporary solution was to build a general Debian Science Blend that
- makes use of the work of other Blends in case it exists.
-</p>
-</sect>
-
- <sect id="accessibility">
- <heading>Debian Accessibility Project</heading>
-
-<p>
-Debian for blind and visually impaired people
-
-<taglist>
- <tag>Start</tag>
- <item>February 2003</item>
- <tag>Mailing list</tag>
- <item><url name=" debian-accessibility at lists.debian.org" id="http://lists.debian.org/debian-accessibility/"></item>
- <tag>URL</tag>
- <item><url name="Debian Accessibility" id="http://www.debian.org/devel/debian-accessibility/"></item>
- <tag>Tasks</tag>
- <item><url name="Tasks of Debian Accessibility" id="http://blends.alioth.debian.org/accessibility/tasks"></item>
- <tag>Activity</tag>
- <item><url name="Activists on Debian Accessibility mailing list" id="http://blends.debian.net/liststats/authorstat_debian-accessibility.png"></item>
- <tag>Initiator</tag>
- <item>Mario Lang <email>mlang at debian.org</email></item>
- <tag>Goals</tag>
- <item>
- <list>
- <item>To make Debian accessible to people with disabilities.</item>
- <item>To take special care for: Screen readers; Screen magnification programs;
- Software speech synthesisers; Speech recognition software; Scanner drivers
- and OCR software; Specialised software like edbrowse (web-browse in the
- spirit of line-editors)
- </item>
- <item>To make text-mode interfaces available.</item>
- <item>To provide screen reader functionality during installation.</item>
- </list>
- </item>
-</taglist>
-
-</p>
-</sect>
-
-
-<sect id="stalled-blends">
- <heading>Blends that were announced but development is stalled</heading>
-
- <sect1 id="debian-desktop">
- <heading>Debian Desktop: Debian GNU/Linux for everybody</heading>
-
-<p>
-Motto: "Software that Just Works".
-
-<taglist>
- <tag>Start</tag>
- <item>October 2002</item>
- <tag>URL</tag>
- <item><url name="Debian Desktop" id="http://www.debian.org/devel/debian-desktop"></item>
- <tag>Mailing list</tag>
- <item><url name=" debian-desktop at lists.debian.org" id="http://lists.debian.org/debian-desktop/"></item>
- <tag>Activity</tag>
- <item><url name="Activists on Debian Desktop mailing list" id="http://blends.debian.net/liststats/authorstat_debian-desktop.png"></item>
- <tag>Initiator</tag>
- <item>Colin Walters <email>walters at debian.org</email></item>
- <tag>Goals</tag>
- <item>
- <list>
- <item>To try to build the best possible operating system for home
- and corporate workstation use.</item>
- <item>To ensure desktops like GNOME and KDE coexist well in Debian and
- work optimally.</item>
- <item>To balance ease of use for beginners with flexibility
- for experts.</item>
- <item>To make the system easy to install and configure (e.g. via
- hardware-detection).</item>
- </list>
- </item>
-</taglist>
-
-This Blend has many common issues with other Blends. The latest move
-of Debian Desktop was to care about more up to date software that can
-be used as common base for all Debian Pure Blends. The
-common interest is described in detail in <ref
-id="new_ways_of_distribution">. Unfortunately since about 2004 the
-project is really silent and it might be considered dead now.
-</p>
-</sect1>
-
- <sect1 id="debian-lex">
- <heading>Debian Lex: Debian GNU/Linux for Lawyers</heading>
-
-<p>
-<taglist>
- <tag>Start</tag>
- <item>April 2003</item>
- <tag>URL</tag>
- <item><url name="Debian Lex" id="http://www.debian.org/devel/debian-lex"></item>
- <tag>Tasks</tag>
- <item><url name="Tasks of Debian Lex" id="http://blends.alioth.debian.org/lex/tasks"></item>
- <tag>Mailing list</tag>
- <item><url name=" debian-lex at lists.debian.org" id="http://lists.debian.org/debian-lex/"></item>
- <tag>Activity</tag>
- <item><url name="Activists on Debian Lex mailing list" id="http://blends.debian.net/liststats/authorstat_debian-lex.png"></item>
- <tag>Initiator</tag>
- <item>Jeremy Malcolm <email>Jeremy at Malcolm.id.au</email></item>
- <tag>Goals</tag>
- <item>
- <list>
- <item>To build a complete system for all tasks in legal
- practice.</item>
- <item>To add value by providing customised templates for lawyers to
- existing packages like OpenOffice.org and SQL-Ledger, and
- sample database schemas for PostgreSQL.
- </item>
- </list>
- </item>
-</taglist>
-The word <em>lex</em> is the Latin word for law.
-</p>
-</sect1>
-
-
- <sect1 id="debian-enterprise">
- <heading>Debian Enterprise</heading>
-
-<p>
-Debian GNU/Linux for Enterprise Computing
-
-<taglist>
- <tag>Start</tag>
- <item>End of 2003</item>
- <tag>URL</tag>
- <item>Debian Enterprise</item>
- <tag>Initiator</tag>
- <item>Zenaan Harkness <email>zen at iptaustralia.net</email></item>
- <tag>Activity</tag>
- <item><url name="Activists on Debian Enterprise mailing list" id="http://blends.debian.net/liststats/authorstat_debian-enterprise.png"></item>
- <tag>Goals</tag>
- <item>
- <list>
- <!-- [BA] The following are stated on the web site as what Debian Enterprise
- does, and not as goals. But the goals section on the web site is hard
- to reduce to specific goals point-by-point. I believe this needs fixing,
- and perhaps could be improved by talking it over with Zenaan. -->
- <item>To apply the UserLinux Manifesto.</item>
- <item>To establish the benchmark in world class Enterprise
- operating systems engineered within an industry driven
- shared-cost development model.</item>
- <item>To vigorously defend its distinctive trademarks and
- branding.</item>
- <item>To develop extensive and professional quality
- documentation.</item>
- <item>To provide engineer certification through partner
- organisations.</item>
- <item>To certify the Debian Enterprise GNU/Linux operating system
- to specific industry standards.</item>
- <item>To pre-configure server tasks</item>
- <!-- [BA] I don't know what this point means, nor can I find it on the
- web site, so perhaps it should simply be removed.
- <item>To provide install-time options regarding the intended
- purpose.</item>
- [AT] Removed by comment
- The idea behind it was that it might be interesting to
- provide some configuration options for certain servers
- which might have connections to others. For instance Zope
- can be run behind Apache using some rewriting rules but
- this is poorly documented and a working example or
- something else could help here. It was discussed via
- E-Mail that Debian Enterprise could provide such
- "inter-package-connection" configurations as examples.
- This was badly worded above and not officially stated at
- their web site, but should not be lost out of focus and
- should remain here at least as comment. Perhaps you might
- find a better wording.
- -->
- </list>
- </item>
-</taglist>
-</p>
-
-</sect1>
-
- <sect1 id="other">
- <heading>Other possible Debian Pure Blends</heading>
-<p>
- There are fields that could be served nicely by not yet existing
- Blends:
- <taglist>
- <tag>Debian eGov</tag>
- <item>Could address government issues, administration, offices of authorities,
- accounting.</item>
- <tag>Office</tag>
- <item>Could cover all office issues.</item>
- <tag>Accounting</tag>
- <item>Could integrate accounting systems into Debian.</item>
- <tag>Biology</tag>
- <item>Could perhaps take over some stuff from Debian Med.</item>
- <tag>Physics</tag>
- <item>Might look after simulation software.</item>
- <tag>Mathematics</tag>
- <item>There is even already a live CD - see Quantian in <ref id="liveCD"></item>
- <tag>???</tag>
- <item>There are a lot more potential Blends.</item>
- </taglist>
-</p>
-</sect1>
-
-</sect>
-
-</chapt>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
-sgml-exposed-tags:nil
-sgml-local-catalogs:nil
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/en/04_existing_blends.xml b/doc/en/04_existing_blends.xml
index 41c9b8a..3eb4697 100644
--- a/doc/en/04_existing_blends.xml
+++ b/doc/en/04_existing_blends.xml
@@ -128,9 +128,9 @@ for example, simple text processing, web browsing and drawing.
<listitem>
<para><ulink url="http://blends.debian.net/liststats/authorstat_debian-med.png">Activists on Debian Med mailing list</ulink></para>
<para><ulink url="http://blends.debian.net/liststats/authorstat_debian-med-packaging.png">Activists on Debian Med developer list</ulink></para>
- <!-- authorstats not available
- <para><ulink url="http://blends.debian.net/liststats/authorstat_debian-med-commit.png">Activists on Debian Med commit list</ulink></para>
- //-->
+ <para><ulink url="http://blends.debian.net/liststats/commitstat_debian-med.png">Commiters to Debian Med VCS</ulink></para>
+ <para><ulink url="http://blends.debian.net/liststats/uploaders_debian-med.png">Uploaders of Debian Med team</ulink></para>
+ <para><ulink url="http://blends.debian.net/liststats/bugs_debian-med.png">Team members closing the most bugs in Debian Med packages</ulink></para>
</listitem>
</varlistentry>
@@ -307,10 +307,10 @@ intended to be used in schools. For instance there are:
<term>Activity</term>
<listitem>
<para><ulink url="http://blends.debian.net/liststats/authorstat_pkg-multimedia-maintainers.png">Activists on Debian Multimedia maintainers mailing list</ulink></para>
- <!-- authorstat not availble
- <para><ulink url="http://blends.debian.net/liststats/authorstat_pkg-multimedia-commits.png">Activists on Debian Multimedia commits mailing list</ulink></para>
- //-->
<para><ulink url="http://blends.debian.net/liststats/authorstat_debian-multimedia.png">Activists on Debian Multimedia user mailing list</ulink></para>
+ <para><ulink url="http://blends.debian.net/liststats/commitstat_pkg-multimedia.png">Commiters to Debian Multimedia VCS</ulink></para>
+ <para><ulink url="http://blends.debian.net/liststats/uploaders_pkg-multimedia.png">Uploaders of Debian Multimedia team</ulink></para>
+ <para><ulink url="http://blends.debian.net/liststats/bugs_pkg-multimedia.png">Team members closing the most bugs in Debian Multimedia packages</ulink></para>
</listitem>
</varlistentry>
@@ -434,9 +434,9 @@ intended to be used in schools. For instance there are:
<term>Activity</term>
<listitem>
<para><ulink url="http://blends.debian.net/liststats/authorstat_debichem-devel.png">Activists on DebiChem mailing list</ulink></para>
- <!-- authorstat not available
- <para><ulink url="http://blends.debian.net/liststats/authorstat_debichem-commits.png">Activists on DebiChem commits list</ulink></para>
- //-->
+ <para><ulink url="http://blends.debian.net/liststats/commitstat_debichem.png">Commiters to DebiChem VCS</ulink></para>
+ <para><ulink url="http://blends.debian.net/liststats/uploaders_debichem.png">Uploaders of DebiChem team</ulink></para>
+ <para><ulink url="http://blends.debian.net/liststats/bugs_debichem.png">Team members closing the most bugs in DebiChem packages</ulink></para>
</listitem>
</varlistentry>
@@ -492,9 +492,9 @@ intended to be used in schools. For instance there are:
<listitem>
<para><ulink url="http://blends.debian.net/liststats/authorstat_debian-science.png">Activists on Debian Science mailing list</ulink></para>
<para><ulink url="http://blends.debian.net/liststats/authorstat_debian-science-maintainers.png">Activists on Debian Science maintainers list</ulink></para>
- <!-- authorstat not available
- <para><ulink url="http://blends.debian.net/liststats/authorstat_debian-science-commits.png">Activists on Debian Science commits list</ulink></para>
- //-->
+ <para><ulink url="http://blends.debian.net/liststats/commitstat_debian-science.png">Commiters to Debian Science VCS</ulink></para>
+ <para><ulink url="http://blends.debian.net/liststats/uploaders_debian-science.png">Uploaders of Debian Science team</ulink></para>
+ <para><ulink url="http://blends.debian.net/liststats/bugs_debian-science.png">Team members closing the most bugs in Debian Science packages</ulink></para>
</listitem>
</varlistentry>
diff --git a/doc/en/A_devel.sgml b/doc/en/A_devel.sgml
deleted file mode 100644
index da63841..0000000
--- a/doc/en/A_devel.sgml
+++ /dev/null
@@ -1,707 +0,0 @@
- <appendix id="DevelDescription">
- <heading>Description of development tools</heading>
- <sect id="blends-dev">
- <heading>Package <package>blends-dev</package></heading>
-
-<p>
-If metapackages are builded using the tools inside the
-<package>blends-dev</package> package it can be ensured that the
-resulting metapackages will work nicely with the same version of
-<package>blends-common</package> package. The goal is to keep
-necessary changes for the source of the metapackages of a Debian Pure
-Blend as low as possible when the version of the
-<package>blends</package> source package changes. Thus it is
-strongly recommended to use the tools described below.
-</p>
-<p>
-The usage of the tools in the <package>blends-dev</package> package might
-introduce a versioned dependency in the
-<package><var><blend></var>-config</package> package from which
-all other metapackages of the <var>Blend</var> in question will
-depend. This <package><var><blend></var>-config</package> package
-instantiates the <var>Blend</var> in the common registry for all Blends in
-<file>/etc/blends</file>.
-</p>
-
-<p>
-The version <package>0.7.0</package> of <package>blends-dev</package> uses
-<url id="https://wiki.debian.org/UltimateDebianDatabase" name="UDD">
-to generate Blends' metapackages. Currently all Blends' info is stored into UDD.
-Information such as VCs, description, homepage etc for a Blend can be found into the
-<url id="http://udd.debian.org/schema/udd.html#public.table.blends-metadata" name="blends_metadata">
-UDD table. All the info about Blends' tasks and their package dependencies are also stored
-into the <url id="http://udd.debian.org/schema/udd.html#public.table.blends-tasks" name="blends_tasks"> and
-<url id="http://udd.debian.org/schema/udd.html#public.table.blends-dependencies-alternatives" name="blends_dependencies_alternatives">
-tables. Having the latter in combination with other UDD tables
-(such as a table with info about all Debian available packages)
-provides the ability to check whether a package exists for an architecture or not thus
-<package>blends-dev</package> can generate architecture dependent metapackages.
-</p>
-
-<p>
-The best idea to use the tools provided by the
-<package>blends-dev</package> is to put a <file>Makefile</file> into the
-build directory containing one single line
-
-<example>
- include /usr/share/blends-dev/Makefile
-</example>
-
-(see <file>/usr/share/doc/blends-dev/examples/Makefile</file>).
-Users using <package>blends-dev 0.7.0</package> on existing Blends
-which have more than one releases might encouter some <file>Makefile</file>
-errors for more info see <ref id="statusdump"> and <ref id="changelogentry">.
-
-Using this <file>Makefile</file> all tools that were contained in
-<package>blends-dev</package> package versions before 0.4. These tools
-are moved to <file>/usr/share/blends-dev/</file> because there is no need
-to call them directly. Here is a list of the <file>make</file> targets.
-</p>
-
-<sect1 id="blends-tasks.desc">
- <heading>Blend<tt>-tasks.desk</tt></heading>
-
-<p>
-This target generates a <package>task-description.template</package> file.
-The template can be converted to a proper description file that is used in
-<prgn>tasksel</prgn> to enable selecting the tasks belonging to the Blend.
-The initial template contains all the needed package dependencies
-for a Blend. But because some packages might not be available for a(or multiple)
-architectures the template uses the following syntax when specifying packages:
-<example> package1 [!arch1 arch2]</example>
-
-That says do not include the package1 in the
-taskdescription file when arch1 or arch2 is used.
-When a Blends' <package>orig.tar.gz</package> is generated,
-the initial template gets converted
-from the <package>blends-dev rules</package> file to a proper taskdescription file.
-The convertion is filtering out the packages which are not available for the
-host's (where the <package>orig.tar.gz</package> is generated) architecture.
-This make sure that the taskdescription file will not include package which are
-not available for the target architecture.
-Finally the file will be moved to the
-<var>blend</var><package>-tasks</package>. All information
-about Blends package dependencies is obtained from the UDD.
-</p>
-
-</sect1>
-<sect1 id="debian_control">
- <heading><tt>debian/control</tt></heading>
-
-<p>
-The <file>debian/control</file> file of a Blend metapackage source
-archive is auto generated out of dependencies that are specified in so
-called <file>tasks</file> files. The rationale behind this is to
-enhance flexibility about changes inside the Debian package pool where
-new packages might appear and others might be renamed.
-The <file>tasks</file> just define which dependencies the Blend
-maintainer group wants to be fulfilled and the
-script <prgn>blend-gen-control</prgn> using UDD verifies whether these
-dependencies exist in a specified package pool. A
-package pool can be considered as the packages available for a
-combination of distribution, component and release values. By default when
-creating metapackages debian,main,testing values are used to "create" a package pool from UDD.
-Once a Blends' dependencies are verified the <file>debian/control</file> file is generated
-according to the available packages. This does not only work for the Debian package pool
-containing the distributions stable, testing and unstable. You can
-even build your metapackages against a different package pool of a
-Debian based distribution. This is for instance used to create the
-SkoleLinux metapackages.
-</p>
-
-<p>
-As mentioned in the previous section, using UDD in Blends' tools provides the ability to generate
-architecture dependent metapackages. Thus the generated
-<package>debian/control</package> specifies for every task source target as architecture value:
-<example>Architecture: any</example>
-
-Specifying <package>any</package> indicates that the source package isn't dependent
-on any particular architecture and should compile fine on any one. To fulfil this
-in case of missing packages <package>control</package> file uses the following syntax:
-
-<example>Depends: package1 [!arch1 !arch2]</example>
-
-If a package is not available for a specific arch, exclude it from it. So the above example says:
-depend on package1 but not when architecture arch1 or arch2 is used. More info about
-<package>debian/control</package> syntax can be found in
-<url id="http://www.debian.org/doc/debian-policy/" name="Debian Policy Manual" >
-</p>
-
-<p>
-The syntax of the <file>tasks</file> files which serve as the central
-database for the information in the <file>debian/control</file> file
-is defined by RFC822. Some of the tags were mentioned formerly in
-<ref id="packageslist"> to explain how the <file>tasks</file> files
-can be used to create the web sentinel pages. Now the tags that
-influence the creation of the <file>debian/control</file> file are given.
-</p>
-<p>
- <taglist>
- <tag>Depends</tag>
- <item>Will be turned to "Recommends" in the
- resulting <file>debian/control</file> file. The
- rationale behind this is to enable installing the
- metapackage even if a package belonging to this task is
- missing for whatever reason. It also allows finally to
- remove the metapackage. This makes even more
- sense since <prgn>apt-get</prgn> considers "Recommends"
- as default installation targets.
- </item>
- <tag>Recommends</tag>
- <item>The packages that are listed as "Recommends" in the
- tasks file should be installed on the machine where the
- metapackage is installed and which are needed to work
- on a specific task.
- </item>
- <tag>Suggests</tag>
- <!-- [BA] Why would we suggest non-free? Doesn't policy allow a non-free
- package to specify "Enhances" to avoid this problem?
- [AT] I have to admit that "Enhances" is new to me. When
- reading policy I think this field is out of control of
- the metapackage developer because it has to be included
- by the package maintainer. I'm not really convinced that
- this is a good solution - but I would follow the suggestions
- of others in this issue.
- -->
- <item><p>Use "Suggests" for packages of lesser importance that
- might be possibly useful, or non-free packages.</p>
- <p>
- If a package is not available in the package pool of the
- target distribution when creating
- the <file>debian/control</file> file inside the meta
- package source archive any "Depends" or "Recommends" are
- turned into "Suggests" to enable a flawless installation
- of the metapackage. Generally packages are concerned as missing if
- they do not exist into Debian main component(default is testing release).
- Packages that are specified with
- "Suggests" will not be taken over to
- the <prgn>tasksel</prgn> control file
- (Blend<file>-tasks.desk</file>,
- see <ref id="blends-tasks.desc">) but only to the list of
- suggested packages of the according metapackage.
- </item>
- <tag>Ignore</tag>
- <item>The "Ignore" key can be used as kind of "Soft-Suggests"
- to put a package on the radar of the Blend. Packages that
- are tagged with Ignore will not be taken over into the
- list of dependencies inside
- the <file>debian/control</file> file of the resulting
- metapackage neither to the Blend<file>-tasks.desk</file>
- control file for <prgn>tasksel</prgn> but will be taken
- over onto the installation medium of a Blend in case there
- is some space left. This key becomes especially
- important for specifying not yet packaged software that
- might be packaged in the future (prospective packages).
- This is explained in detail in the paragraph about the
- web sentinel (see <ref id="packageslist">).
- </item>
- <tag>Avoids</tag>
- <item>The "Avoids" key specifies existing packages that will
- be listed in the the <file>debian/control</file> file as
- "Recommends" or "Suggests" but, should not go to a
- installation medium (CD, DVD, etc.) that might be
- produced by the Blend. A reason to avoid a package might
- be that it belongs to the non-free section.
- </item>
- </taglist>
-</p>
-</sect1>
-
-<sect1 id="statusdump">
- <heading><tt>statusdump</tt></heading>
-
-<p>
-This target generates a json file containing the latest package dependencies
-for the selected Blend. It parses the files from the <tt>tasks</tt> directory
-and generates a <var>blend</var><tt>_version.json</tt> into a <tt>dependency_data</tt>
-directory. As <tt>version</tt> it gets the latest version specified in the Blend's
-<tt>debian/changelog</tt> file. In case the <tt>dependency_data</tt> directory
-does not exist into a Blend's root directory it automatically creates it.
-</p>
-
-<p>
-A user can also generate a json dependencies file manually
-using the <tt>tasks_diff</tt> script. The script can be called
-from a Blend's root directory:
-
-<example>
- /usr/share/blends-dev/task_diff --status-dump --tasks . --output blend_version.json
-</example>
-If the user does not specify the output argument the script by default
-will generate the json file under the <tt>tasks.json</tt> name in the
-current directory.
-</p>
-
-<p>
-Note: in case a user needs to generate a json file for a previous release
-(rather than the latest) to get the <tt>changelogentry</tt>
-(see <ref id="changelogentry">) target to work, must keep the following thing in mind:
-
-The user must provide to <tt>task_diff</tt> script the <em>root</em> directory of a previous Blend release
-(through the --task(-t) argument). He should also save the output into the <tt>dependency_data</tt>
-directory into the latest Blend release providing manually
-the name <var>blend</var><tt>_version.json</tt> (through the --output(-o) argument:
-
-<example>
-/usr/share/blends-dev/task_diff --status-dump -t blend/tags/previous/ -o latest_blend/dependency_data/blend_version.json
-</example>
-
-For example if the name of the Blend is <tt>myblend</tt> and the release is <tt>0.2.0</tt>
-then the json file must have the name <tt>myblend_0.2.0.json</tt>
-</p>
-
-</sect1>
-
-<sect1 id="changelogentry">
- <heading>changelogentry</heading>
-
-<p>
-This target compares the latest and the previous Blend release and dumps the tasks'
-package differences. It reports the added/removed packages
-per task (or added/removed task files)
-between releases. This "report" is automatically
-added into the <tt>debian/changelog</tt>
-in the latest relase section under the file's manual changes.
-In case a previous difference report
-exists, it overrides it. In case a Blend does not have more than release
-(initial release) then this target is ignored.
-</p>
-
-<p>
-In order the comparison to be properly performed the
-<var>blend</var><tt>_version.json</tt> files for the two latest releases
-must exist under the <tt>dependency_data</tt> directory. In case any of the
-previous files is missing then the target will fail with an error
-(specifying the missing version_file). The json file for the latest
-release is automatically generated from the <tt>statusdump</tt> target
-so it this will not cause the problem.
-</p>
-
-<p>
-This changelog entry is a new feature so the problem of this target failing
-(because of a missing json file) will appear for existing Blends which have
-more than one releases and do not have a <var>blend</var><tt>_version.json</tt>
-for the previous release under their <tt>dependency_data</tt> directory.
-Usually Blend's releases are tagged into the VCs, so the previous problem
-can be solved by generating the dependency json file for the previous
-release (using a previous VCs tag). This can be done by calling manually
-the <tt>task_diff</tt> script (see <ref id="statusdump">)
-</p>
-
-</sect1>
-
-<sect1>
- <heading>Apt <file>sources.list</file> files in <file>/etc/blends/</file></heading>
-<p>
-These files are used by <manref name="blend-gen-control" section="1"> to
-build valid <file>debian/control</file> files that contain only
-available packages in their dependencies. This enables building meta
-packages for <tt>stable</tt>, <tt>testing</tt>, <tt>unstable</tt> or
-even a completely different distribution that has valid
-<file>sources.list</file> entries. The file
-<file>/etc/blends/control.list</file> is used as default for <manref
-name="blend-gen-control" section="1"> and usually is a symbolic link
-(see <manref name="ln" section="1">) to
-<file>sources.list.</file><var>distribution</var>. It might be
-changed using the <tt>-s </tt><var>dist</var> option of <manref
-name="blend-gen-control" section="1">.
-</p>
-<p>
-<strong>TODO:</strong> <em>Either parse the available
-<file>/etc/apt/sources.list</file> or use a sane <prgn>debconf</prgn>
-question to use the "nearest" mirror.</em>
-</p>
-</sect1>
-
-<sect1>
- <heading>Templates in <file>/usr/share/blends/templates</file></heading>
-<p>
-The directory <file>/usr/share/blends/templates</file> contains templates
-that can be used to build a <var><blend></var><package>-config</package>,
-which uses the tools that are contained in the
-<package>blends-common</package> package, and are useful to manage
-<var><blend></var> user groups (see <ref id="userroles">).
-</p>
-</sect1>
-</sect>
-
-<sect id="blends-common">
- <heading>Package <package>blends-common</package></heading>
-
-<p>
-This package creates a common registry for all Blends in
-<file>/etc/blends</file>. Each Blend should put the files that are used
-into a subdirectory named like the Blend of <file>/etc/blends</file>. The
-<package>blends-common</package> package installs a common configuration
-file <file>/etc/blends/blends.conf</file>, which can be used to influence the
-behaviour of the tools described below.
-</p>
-
-<sect1>
- <heading><!-- document type does not allow element "MANREF" here--><tt>blend-role(8)</tt></heading>
-<p>
-<taglist>
- <tag>NAME</tag>
- <item>
- <prgn>blend-role</prgn> - add/remove roles in registered Debian Pure Blend
-
- </item>
- <tag>SYNOPSIS</tag>
- <item>
- <prgn>blend-role</prgn> <var>add|del</var> <var>Blend</var> [<var>Role</var>]
- </item>
- <tag>DESCRIPTION</tag>
- <item>Add/remove (register/unregister) <var>Role</var> for the
- specified <var>Blend</var>. If <var>Role</var> is not specified, it's
- assumed to be named like <var>Blend</var>.
- </item>
-
-
- <tag>OPTIONS</tag>
- <item>
- <taglist>
- <tag><var>Blend</var></tag>
- <item>A registered Blend in /etc/blends, for example
- one of <tt>med</tt>, <tt>junior</tt>,
- <tt>edu</tt> or <tt>science</tt>
- </item>
- </taglist>
- </item>
- <tag>AUTHOR</tag>
- <item>Andreas Tille <email>tille at debian.org</email>,
- Cosimo Alfarano <email>kalfa at debian.org</email>.</item>
-</taglist>
-</p>
-</sect1>
-
-<sect1 id="blend-update-menus">
- <heading><!-- document type does not allow element "MANREF"
- here--><tt>blend-update-menus(8)</tt></heading>
-<p>
-<taglist>
- <tag>NAME</tag>
- <item>
- <prgn>blend-update-menus</prgn> - add menu of metapackage to all Blend users
- </item>
- <tag>SYNOPSIS</tag>
- <item>
- <prgn>blend-update-menus</prgn> [<var>--blend Blend</var> | <var>--user
- user</var>]
- </item>
- <tag>DESCRIPTION</tag>
- <item>
- <p>
- blend-update-menus behaves differently depending on who run the
- command:
- </p>
-
- <p>
- If it is called by a user, it adds, and keeps updated, menu
- entries for the user who runs it.
- </p>
-
- <p>
- If it is called by root, it adds and keeps updated user's menu
- entries (see menu package for users' menus) for all users who
- belong to the group of the specified Blend, or only for a specified
- user, depending on which parameter is passed to the script.
- </p>
- </item>
-
- <tag>OPTIONS</tag>
- <item>
- <taglist>
- <tag><var>Blend</var></tag>
- <item>one of the installed Blends, listed in /etc/blends/, for example
- (if installed: <tt>med</tt>, <tt>junior</tt>,
- <tt>edu</tt> or <tt>science</tt>.
- </item>
- <tag><var>user</var></tag>
- <item>system user</item>
- </taglist>
- </item>
- <tag>AUTHOR</tag>
- <item>Andreas Tille <email>tille at debian.org</email>,
- Cosimo Alfarano <email>kalfa at debian.org</email>.</item>
-</taglist>
-</p>
-</sect1>
-
-<sect1>
- <heading><!-- document type does not allow element "MANREF" here--><tt>blend-user(8)</tt></heading>
-<p>
-<taglist>
- <tag>NAME</tag>
- <item>
- <prgn>blend-user</prgn> - add/remove user to Role of a registered Blend
-
- </item>
- <tag>SYNOPSIS</tag>
- <item>
- <prgn>blend-user</prgn> <var>add|del</var> <var>Blend</var> <var>user</var> [<var>Role</var>]
- </item>
- <tag>DESCRIPTION</tag>
- <item>Add/remove user to a <var>Role</var> of the specified <var>Blend</var>.
-
- If <var>Role</var> is not specified, it's assumed to be named like
- <var>Blend</var>
- </item>
-
-
- <tag>OPTIONS</tag>
- <item>
- <taglist>
- <tag><var>Blend</var></tag>
- <item>A registered Blend in /etc/blends, for example
- one of <tt>med</tt>, <tt>junior</tt>,
- <tt>edu</tt> or <tt>science</tt>.
- </item>
- <tag><var>user</var></tag>
- <item>user to add</item>
- <tag><var>Role</var></tag>
- <item>the role in the <var>Blend</var> that <var>user</var> will
- assume</item>
- </taglist>
- </item>
- <tag>AUTHOR</tag>
- <item>Andreas Tille <email>tille at debian.org</email>,
- Cosimo Alfarano <email>kalfa at debian.org</email>.</item>
-</taglist>
-</p>
-</sect1>
-
-<sect1>
- <heading><tt>blends.conf(5)</tt></heading>
-<p>
-<taglist>
- <tag>NAME</tag>
- <item>
- <file>blends.conf</file> - configuration for Debian Pure Blends registry
- </item>
- <tag>DESCRIPTION</tag>
- <item>This file is sourced from shell scripts inside the Debian
- Pure Blends package <package>blends-common</package> and thus
- it has to follow shell syntax. The variables that are set
- inside this configuration file can be overriden by special
- Blend configration files
- <file>/etc/blends/<var><>Blend></var>/<var><>Blend></var>.conf</file>
- for each single Blend.
- <tag>SYNTAX</tag>
- <item>The following variables can be set:
- <taglist>
- <tag><tt>DBBACKEND</tt></tag>
- <item>Set the backend for the user role management system.
- Currently the only implemented role management system is
- <tt>unixgroups</tt> but others might be implemented
- later. Unsetting this variable leads to use no roles at all.
- </item>
- <tag><tt>UPDATEUSERMENU</tt></tag>
- <item>If this is set to <tt>yes</tt>, the user menus of meta
- packages can be created automatically at install time of
- the package if the postinst script of the package allows
- this. It is suggested to use this option in the specific
- configuration files of a special Debian Pure Blend that
- override the settings of the general configuration file.
- </item>
- <tag><tt>SHAREDIR</tt></tag>
- <item>Set the base directory for the user role management
- system. While this is more or less a feature for
- debugging this might be also used otherwise.
- </item>
- <tag><tt>DRYRUN</tt></tag>
- <item>This variable can be set for debugging. Normally it
- should be left unset (<em>NOT</em> set to <tt>false</tt>
- or anything else!). If set to <tt>true</tt> a dry run of
- the tools is performed or <tt>echo DRYRUN:</tt> would
- print debugging information.
- </item>
- <tag><tt>DEBUG</tt></tag>
- <item>If set to <tt>1</tt> debugging mode is switched on.
- </taglist>
- </item>
- <tag>SEE ALSO</tag>
- <item>
- <file>blend-role (8)</file>, <file>blend-update-menus (8)</file>,
- <file>blend-user (8)</file>
- </item>
- <tag>AUTHOR</tag>
- <item>Andreas Tille <email>tille at debian.org</email>,
- Cosimo Alfarano <email>kalfa at debian.org</email>.</item>
-</taglist>
-</p>
-</sect1>
-
-</sect>
-
-
-<sect id="svn">
- <heading>Working with the source repository (<file>svn</file> in process of moving to <file>git</file>)</heading>
-<p>
- Sometimes it might be interesting for developers to check out the
- latest code of the Blend tools or a special Blend code for the meta
- packages. In <ref id="communication"> the directory layout of the
- <file>svn</file>-directory was described. How to derive the
- Debian packages from this layout?
-<taglist>
- <tag>Checkout</tag>
- <item>
- For the Blend tools and this documentation
-<example>
- git clone git+ssh://<var>username</var>@git.debian.org/git/blends/blends.git
-</example>
- or for the Debian Pure Blend <var>BLEND-name</var>
-<example>
- svn checkout svn+ssh://<var>username</var>@svn.debian.org/svn/blends/projects/<var>BLEND-name</var>/trunk
-</example>
- Note: This will be moved to Git (at least) soon after Wheezy release.
- </item>
- <tag>Build source package</tag>
- <item>
- Change into the created directory and type
-<example>
- make -f debian/rules get-orig-source
-</example>
- This creates a <file>tar.gz</file> source archive of the packages
- you want to build. For your personal comfort you can create a
- file <file>Makefile</file> in your package source directory containing
-<example>
- #!/usr/bin/make -f
- include /usr/share/blends-dev/Makefile
-</example>
- Which enables you to simply say
-<example>
- make dist
-</example>
- to create the source tarball.
- </item>
- <tag>Build Debian packages</tag>
- <item>
- Unpack the created source tarball and proceed like you build
- Debian packages normally.
- </item>
-</taglist>
-</p>
-<p>
-The current Debian Med packages provide a working example how to use
-the tools described below.
-</p>
-</sect>
-
- <sect id="webpagecreation">
- <heading>How to create tasks and bugs pages of web sentinel</heading>
-
-<p>
-In <ref id="sentinel"> the creation of so called tasks
-pages <ref id="packageslist"> and bugs pages <ref id="bugs"> was
-described. These pages are automatically build by a cron job on Alioth
-from the current state of the tasks files in the SVN repository.
-If you have commited changes to the tasks pages and want to see the
-effect immediately the steps to do are as follows:
-</p>
-<p>
-<enumlist>
- <item>Login to <tt>alioth.debian.org</tt></item>
- <item><tt>cd /var/lib/gforge/chroot/home/groups/blends/webtools/</tt></item>
- <item><tt>./tasks.py <blend-name></tt></item>
-</enumlist>
-</p>
-<p>
-To know what a valid <tt><blend-name></tt> might be have a look
-into
-<tt>/var/lib/gforge/chroot/home/groups/blends/webtools/webconf</tt>.
-Each Blend has an according config file there. Leave out
-the <tt>.conf</tt> extension and you have a
-valid <tt><blend-name></tt>.
-</p>
-<p>
-In case you are planing some more experimental changes there is
-another host which was kindly sponsored by Frédéric Hébert for Debian
-Med called <tt>blends.debian.net</tt> which is running a copy of
-UDD and also hosts the latest development snapshot of the Blends web
-tools. Just ask Andreas Tille <email>tille at debian.org</email> in case
-you like a login on this host.
-</p>
-<p>
-The code which builds web and tasks pages is available in Git at
-<tt>git://git.debian.org/git/blends/website.git</tt>. It is
-using the <url id="http://genshi.edgewall.org/" name="Genshi
-templating system"> which enables influencing the layout of the pages
-by editing the templates in the
-<file>templates</file> directory.
-You can also influence some parameters of the web pages in the
-configuration files in the <file>webconf</file> directory.
-Last but not least you can provide translations for the web pages in
-the <file>po</file> directory.
-</p>
-<p>
-Once something on the web pages was changed you can activate the
-changes as follows:
-</p>
-<p>
-<enumlist>
- <item>Login to <tt>alioth.debian.org</tt> or <tt>blends.debian.net</tt></item>
- <item><tt>cd /var/lib/gforge/chroot/home/groups/blends/webtools/</tt></item>
- <item><tt>git pull</tt></item>
-</enumlist>
-</p>
-<p>
-Please note that the <tt>css</tt> and <tt>js</tt> files which are
-influencing the layout of the automatically created pages are in
-the same area as the static web pages (see below <ref id="staticwebpages">).
-</p>
-</sect>
-
- <sect id="staticwebpages">
- <heading>Editing static web pages of Blends on Alioth</heading>
-<p>
-A very simple entry page is created for each Blend which is linked
-from the
-<url id="http://blends.alioth.debian.org/" name="list of all Blends">.
-Most probably the maintainers of a Blend want to enhance this page a
-bit. It is actually intended that this simple template will be
-enhanced as it is done for instance for the
-<url id="http://debian-med.alioth.debian.org" name="Debian Med
-project"> which has a quite complex PHP driven web with a lot of other
-features than just linking to the tasks and bugs pages. Maintainers
-of a Blend should care for this index page which currently is just
-featuring links to the automatically updated pages as well as an image
-which shows the activity of the
-<url id="http://people.debian.org/~tille/talks/200808_lightning/liststats.pdf"
-name="relevant mailing list">. Maintaining these static pages is
-not a "service" which is done for you. The maintainers of a Blend
-should care for this!
-</p>
-<p>
-The static pages are maintained in Git at
-<tt>git://git.debian.org/git/blends/website.git</tt> in the
-<file>websites</file> directory.
-Once you have changed the content of the pages you can activate
-the changes by doing:
-</p>
-<p>
-<enumlist>
- <item>Login to <tt>alioth.debian.org</tt> or <tt>blends.debian.net</tt></item>
- <item><tt>cd /var/lib/gforge/chroot/home/groups/blends/webtools/</tt></item>
- <item><tt>git pull</tt></item>
-</enumlist>
-</p>
-</sect>
- </appendix>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-namecase-general:t
-sgml-general-insert-case:lower
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:2
-sgml-indent-data:t
-sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
-sgml-exposed-tags:nil
-sgml-local-catalogs:nil
-sgml-local-ecat-files:nil
-End:
--->
--
Git repository for blends code
More information about the Blends-commit
mailing list