[Cdd-commits] r931 - cdd/trunk/docs/papers/200808_cdd
CDD Subversion Commit
noreply at alioth.debian.org
Sun Jul 6 16:10:54 UTC 2008
Author: tille
Date: Sun Jul 6 16:10:53 2008
New Revision: 931
Modified:
cdd/trunk/docs/papers/200808_cdd/cdd-paper.tex
Log:
Some more text - not ready yet.
Modified: cdd/trunk/docs/papers/200808_cdd/cdd-paper.tex
==============================================================================
--- cdd/trunk/docs/papers/200808_cdd/cdd-paper.tex (original)
+++ cdd/trunk/docs/papers/200808_cdd/cdd-paper.tex Sun Jul 6 16:10:53 2008
@@ -195,7 +195,7 @@
to categorise packages that are useful for certain tasks. This is
done in so called tasks files which are processed using the
\package{cdd-dev} package to build meta packages. The other
-application of these tasks files is building internationalized web
+application of these tasks files is building internationalised web
pages which display the packages that are relevant for a certain CDD
task with the descriptions of the packages. The translation for the
descriptions are drawn from the
@@ -203,18 +203,18 @@
the more complete the DDTP translation of packages that are relevant
for a CDD are the better is the translation of the web pages featuring
the CDD tasks. Thus by adding another use case of DDTP translations
-the effort might become additional partipiciants and the quality of
+the effort might become additional participants and the quality of
translations - especially those of specific packages which need some
expert knowledge for proper translation - might increase.
-The internationalized web pages which are generated automatically out
+The internationalised web pages which are generated automatically out
of the information inside the tasks files is a key documentation
feature which is a really helpful tool for developers of the CDD as
well as very informative for users because they immediately get an
-overview about all ready to install software that might be helpfull
+overview about all ready to install software that might be helpful
for their day to day work. Thus we try to promote these pages as the
main entry point for information for our users what we have done,
-which work is in progress and what's on our todo list. This
+which work is in progress and what's on our TODO list. This
information might give them a good motivation to join the project.
The first step might be to provide better translations for the package
descriptions which is certainly a task which is better done by experts
@@ -232,10 +232,10 @@
base of a software and thus the potential developer base.
The process to establish a certain piece of Free Software described
-above seems to be quite straightforeward but without a linking
-instance like a CDD inbetween upstream developer and users the
+above seems to be quite straightforward but without a linking
+instance like a CDD in between upstream developer and users the
propagation of specialised Free Software is often everything else than
-straightforeward. If the idea of Free Software reaches a specialist
+straightforward. If the idea of Free Software reaches a specialist
who is working on a specific solution he is happy to release the code
on his private web page -- and that it is just there. It is not very
common to use well known source code repositories like
@@ -249,94 +249,57 @@
Some volunteers have realised this situation and provide extensive
link lists either on static HTML pages or Wikis to enable others to
-join the catalogisation effort. The problem here is that these link
+join the catalogue effort. The problem here is that these link
lists are often incomplete and what matters even more are not directly
connected to immediately installable and executable binaries.
-There are some similar efforts like CDD in other distributions
-(Gentoo biology, BSD Biology) because also other distributors realised
-the problem described above. The difference between such kind of
-installable software collections and a CDD is that a CDD
-
-
-\section{Supporting very special applications}
-
-There are several reasons for and against adding special applications
-to the \Debian pool. One drawback is penalty is that \Debian becomes
-larger and larger regarding the number of packages and the question
-raises: How many packages are good for Debian? Currently there is no
-reasonable answer to this question and the rule for adding packages is
-currently: As long as one person is interested enough in a software to
-maintain the package it will be included.
-
-From the upstream maintainers point of view it is a very interesting
-method to bring special applications under quality control. It often
-happens that Debian maintainers add reasonable patches and Debian
-users might file interesting bug reports that lead to further
-enhancements of the software.
-
-As mentioned above \Debian can serve as a vehicle for upstream
-software because \Debian users just stumble upon some programs they
-did not know before when they are installing \Debian. So integrating
-software into \Debian just increases the user base of the software.
-
-This turns in to the question: How many packages are good for our
-users? If our users on one hand learn about interesting applications
-and on the other hand are enabled to install these applications
-flawlessly ready to run this is exactly what we want.
-
-Related to the packaging of special applications is the question about
-packaging special data. Some applications need large data sets to
-work reasonably and it is not really an option to bundle all these
-into normal packages because this would drive mirror maintainers crazy
-in terms of bandwidth and disk space. There would be other solutions
-to discuss like providing a separate data archive which seems not to
-be happen according to \printurl{bugs.debian.org/38902}{\#38902
- wont-fix} or alternatively find some common tool that downloads data
-according to certain rules.
-
-So the basic goal of Custom Debian Distributions is to enable the user
-to focus on the packages that are really needed for his day to day
-work leading him friendly through the jungle of \Debian{}'s
-$\mathsf{>}$ 15000 packages. A user that is working in a certain
-field is only interested in a defined \emph{subset} of packages and
-the CDD that is concerned about this field tries to prepare the
-computer optimally to install this subject with adapted configuration
-and easily accessible applications. So CDDs are taking care of
-groups specialised users turning \Debian into a useful tool adapted
-to their requirements for day to day work and making it to the
-distribution of choice for their use cases. It should enable and easy
-installation and automatically configuration whenever possible to make
-the needed work to fit the intended purpose as small as possible
-
-While \Debian as a distribution stays a general collection of Free
-Software ready to install it supports specialists as well which is
-kind of unique in the distribution market. By attracting specialists
-\Debian might become more attractive for a larger user base especially
-those users that are basically left alone by other distributions.
-So the basic idea of Custom Debian Distributions is
-\begin{center}
- Do not make a separate distribution but make\\
- \Debian fit for special purpose instead.
-\end{center}
-
-% Naturally a
-%\Debian developer looks at the operating system as the thing users
-%really want. And yes there are users that just want an operating
-%system and no it is not a bad thing to focus on the system itself.
-%But believe it or not there are people out there who do not really
-%care about operating systems. These people use their computer as kind
-%of device like their mobile phone or there washing machine. They
-%absolutely do not care about the operating system that is running the
-%programs that are needed to dial the correct number and do a phone call
-%or to get clean clothes.
+There are some similar efforts like CDD in other distributions for
+instance there is a comparable effort to package biological Free
+Software done by
+\printurl{http://kambing.ui.edu/gentoo-portage/sci-biology/}{Gentoo}
+or \printurl{http://www.freebsdsoftware.org/biology/}{FreeBSD} because
+also other distributors realised the problem described above. The
+difference between such kind of installable software collections and
+a CDD is that a Custom Debian Distribution tries to do more than
+just packaging specific software. It is rather about forming a team
+of maintainers who try to build a consistent system around several
+tasks in a specific field, care for easily installation using
+meta-packages, making sure that everything works together smoothly and
+working actively as missing link between upstream developers and users.
+
+
+\section{CDD is more than packaging specific software}
+
+The main work of a distributor is providing precompiled binaries of
+Free Software, caring for smooth installation and upgrades as well as
+security fixes for the distributet packages. In the case of Debian
+which maintains the largest pool of ready to install binary software
+packages this is quite a large amount of work. The huge amount of
+software includes larger subset of software for very specific use and
+this is the playground of CDD packaging teams who closely work
+together to bundle their competence on packages with a specific user
+base.
+
+It turns out that there is a good chance of cooperation between CDDs
+on a technical level because several jobs to do are at least similar.
+This idea is the basis of the whole CDD effort: Making sure that the
+wheel that drives a certain CDD is only invented once and adopted for
+all others. The
+Attracting derivers
+
+\section{Techniques}
+
+\subsection{Building metapackages}
+
+\subsection{Web pages based on common scripts}
+
\section{Summary}
Custom Debian Distributions might solve future structural problems of
-Debian while fitting better user interests. If done the right ay it
-makes Debian stronge and is sometimes refered to as: ``\emph{The last,
+Debian while fitting better user interests. If done the right way it
+makes Debian stronger and is sometimes refered to as: ``\emph{The last,
final step towards Total World Domination.}''
From a \Debian developers point of view we are really {\em
More information about the Cdd-commits
mailing list