[med-svn] r5589 - trunk/community/papers/11_med-floss_luxemburg
Nelson A. de Oliveira
naoliv at alioth.debian.org
Fri Dec 10 10:21:59 UTC 2010
Author: naoliv
Date: 2010-12-10 10:21:58 +0000 (Fri, 10 Dec 2010)
New Revision: 5589
Modified:
trunk/community/papers/11_med-floss_luxemburg/paper-text.tex
Log:
More small fixes
Modified: trunk/community/papers/11_med-floss_luxemburg/paper-text.tex
===================================================================
--- trunk/community/papers/11_med-floss_luxemburg/paper-text.tex 2010-12-10 08:29:51 UTC (rev 5588)
+++ trunk/community/papers/11_med-floss_luxemburg/paper-text.tex 2010-12-10 10:21:58 UTC (rev 5589)
@@ -12,7 +12,7 @@
foundation for bringing those products together. To assure complete
coverage and harmonic integration, the \DebianMed project was
initiated to provide a software management infrastructure to improve
- communication among Debian package maintainers, e.g. to identify
+ communication among Debian package maintainers, \emph{e.g.} to identify
missing glue packages to translate data formats or to point out
conflicts in the naming of binaries.
@@ -25,7 +25,7 @@
of the developers back into the distribution and made medical
software a constituent member of the Debian distribution.
- The ideas behind the Debian Med generalised into the concept of
+ The ideas behind the \DebianMed generalised into the concept of
Debian Pure Blends. Blends, such as Debian Edu, Debian Science,
DebiChem (chemistry), Debian GIS, DeMuDi \emph{etc.}, were created
to provide a targeted appearance of the Debian distribution for
@@ -54,7 +54,7 @@
increasing specialisation of software.
% MH: don't think that is necessary
%and a field of application that has its
-%focus on something else, i.e. the human, than the exchange of information.
+%focus on something else, \emph{i.e.} the human, than the exchange of information.
%a field of aptask is one of the
%hardest in the field of health care: there is a much smaller number of
@@ -89,8 +89,8 @@
%
% MH: Agreed -- this needs some glue to get to the next paragraph
Web search engines pick up the software tools and their descriptions
-on the Debian Med task pages. Beyond mere lists or announcement
-sites, e.g. Freshmeat.net, any Debian user can almost instantly
+on the \DebianMed task pages. Beyond mere lists or announcement
+sites, \emph{e.g.} Freshmeat.net, any Debian user can almost instantly
start evaluating the software on the local computer.
@@ -223,7 +223,7 @@
system, but may only by offered in supplemental repositories.
Another important rule is that any granted permission must not be specific to
-Debian, but shall be universally applicable to anyone, i.e. another software
+Debian, but shall be universally applicable to anyone, \emph{i.e.} another software
vendor or an individual users. This requirement is another indication for an
intrinsic impetus to help Free software at large.
@@ -237,10 +237,10 @@
The technical constraints on the packaging are formulated in the Debian
Policy document. While every package needs to comply with that policy,
every single maintainer of a Debian package has complete freedom
-to decide what software to package. Those who package, i.e. those
+to decide what software to package. Those who package, \emph{i.e.} those
who do, give the distribution it shape.
This is referred to as {\em
-Do-o-cracy} in Debian and refers to the fact that: The one who does something
+do-ocracy} in Debian and refers to the fact that: the one who does something
decides what is done and how it is done.
% Is this needed?
@@ -258,18 +258,18 @@
availability of software that contributes to everyday's routine
and beyond.
-This {\em Do-o-cracy} principle enables individuals or small groups to
+This {\em do-ocracy} principle enables individuals or small groups to
actively influence the support of certain work fields.
Here, community-driven Linux distributions have an edge over
commercial Linux distributions. The number of users that may use
-a package, i.e. that pay back for an initial packaging effort,
+a package, \emph{i.e.} that pay back for an initial packaging effort,
is not the decisive factor in favor or against the maintenance of a
package. One only needs a sufficiently large community of active
package maintainers to have confidence that the current
infrastructure will be maintained, that new packages will
be brought into the distribution and that one will possibly be
allowed to improve current workflows with personal contributions.
-Debian Med is actively benefiting from this aspect and is supporting a
+\DebianMed is actively benefiting from this aspect and is supporting a
lot of applications which are very specific to medical care and are
not integrated in any other large distribution.
@@ -362,7 +362,7 @@
a Debian GNU/Linux system. However, these are not yet covering
scientific applications. The Blend toolkit
will support \command{tasksel} to enable selection of \emph{niche}
- software collections, \emph{e.g.} Debian Med, right after a fresh installation of a
+ software collections, \emph{e.g.} \DebianMed, right after a fresh installation of a
general Debian system.
% yoh: don't we want ideally "during a fresh installation of a Debian system"?
% at: we would *want* this but unfortunately we would need our own
@@ -440,7 +440,7 @@
\end{itemize*}
Due to the complexity of the task these projects had to make compromises
-regarding the quality of their products and where freuqently being
+regarding the quality of their products and where frequently being
\begin{itemize*}
\item sloppy about policy of the underlying Debian system
\item sloppy about the licenses of the included programs
@@ -466,7 +466,7 @@
Especially the latter aspect made such an approach to distribute software
unacceptable for sensible medical data.
-To prevent these problems Debian Med took a different approach. The initial team was
+To prevent these problems \DebianMed took a different approach. The initial team was
also quite small, but has grown in the eight years of existence to more
than 20 active maintainers. The primary idea is to maintain medical
applications {\em inside} Debian. This automatically solves all
@@ -477,14 +477,14 @@
and an QA team running intense tests regarding software quality (see
above).
-Similar effort as Debian Med exists in Fedora as
+Similar effort as \DebianMed exists in Fedora as
\printurl{http://fedoraproject.org/wiki/SIGs/FedoraMedical}{FedoraMedical
SIG (Special Interest Group)} and in openSUSE as
\printurl{http://en.opensuse.org/Portal:Medical}{openSUSE Medical}.
Both projects share the same idea to put medical applications inside a
larger distribution instead of trying to do the work of the
distributor themselves. The
-difference to Debian Med (besides of the different distribution) is
+difference to \DebianMed (besides of the different distribution) is
that both teams are much smaller and thus the number of packaged
applications is in both cases less than 5\% of the applications
available for Debian. Moreover Debian does not distinguish between
@@ -498,7 +498,7 @@
biological software}. The remarkable fact here is not the
underlying operating system (you can easily have Debian with a FreeBSD
kernel with Debian 6.0) but rather the fact that the same strategy to
-support a specific field as in Debian Med was followed: Use a large
+support a specific field as in \DebianMed was followed: Use a large
and technically well supported system and put the specific software
for special use cases {\em into} this instead of deriving the whole
system.
@@ -562,7 +562,7 @@
% duplication
The underlying principle that those things will be done if there is
-somebody who just does the work is called {\em Do-O-Cracy} -- which
+somebody who just does the work is called {\em do-ocracy} -- which
just means the doer decides what gets done.
That is the reason why Debian is often the platform of choice for
@@ -660,7 +660,7 @@
%to stay strictly inside Debian -- so even if manpower is a problem
\DebianMed is not a derived distribution and is a part of the
-Debian project. \DebianMed relies on the core Debian infrastructure (e.g. build farm
+Debian project. \DebianMed relies on the core Debian infrastructure (\emph{e.g.} build farm
across variety architectures, online repositories and mirrors, bug
tracking system) and only complements it with an additional thin
layer yet again functioning within Debian infrastructure. That guarantees that overall development system remains robust
@@ -672,9 +672,9 @@
frequently software products maintained by \DebianMed are of generic
utility, \emph{e.g.} Java or Python libraries, and thus of interest to the
Debian audience outside of the target scope of \DebianMed -- Medicine,
-as a result benefitting Debian as a whole. Due to significant
+as a result benefiting Debian as a whole. Due to significant
overlap, boundaries between different Blends are not clearly defined and
-the separation of \DebianMed from e.g. Debian Science is often
+the separation of \DebianMed from \emph{e.g.} Debian Science is often
artifactual.
\begin{figure}[!htp]
@@ -684,7 +684,7 @@
\label{figure:authorstats}
\end{figure}
-The success of the Debian Blends approach finds evidence in e.g. a
+The success of the Debian Blends approach finds evidence in \emph{e.g.} a
continuous growth of the number of packages inside Debian which are of
interest for health care. Taking the number of dependencies of some
metapackages into account (see figure \ref{figure:dmstats}), only a
@@ -753,7 +753,7 @@
\subsubsection{Role inside Debian}
The Debian Pure Blends framework was mainly inspired by the \DebianMed
-needs. The implementation e.g. by the Debian Edu project -- another
+needs. The implementation \emph{e.g.} by the Debian Edu project -- another
Blend -- is far more advanced. There are several reasons for this
fact. The main reasons is an enormous availability of software for education
and the fact that a Norwegian company paid developers to work full
@@ -769,7 +769,7 @@
The tasks pages are providing an overview about all the work fields
like biology, medical imaging, practice management etc. which are
covered by \DebianMed. The list of all the packages is regenerated
-on a daily basis and includes some meta information to e.g. point to
+on a daily basis and includes some meta information to \emph{e.g.} point to
relevant scientific publications and the description of the
packages in this task. So the output of the project can be easily \marginpar{just have a regular reference to the URL}
viewed at \printurl{http://debian-med.alioth.debian.org/tasks/}{the
@@ -784,7 +784,7 @@
results and inform about versions packaged for Debian as well as a
notification about new releases. Moreover, the visitor of
these pages gets an easy option to provide a screenshot or a missing
-or translations as well as fixing a wrong translation, i.e. everyone
+or translations as well as fixing a wrong translation, \emph{i.e.} everyone
is visibly invited to contribute.
There are also quality assurance tools developed for instance there is
@@ -806,7 +806,7 @@
The contributors to \DebianMed aim at providing the best possible
platform for medical work. The Freedom for users to apply those
-technologies for local needs, i.e. new scientific problems or
+technologies for local needs, \emph{i.e.} new scientific problems or
particular regulations in health care, are intrinsically connected
with that prime ambition. The Debian Free Software Guidelines
match those nicely and are applicable across platforms.
@@ -893,14 +893,14 @@
Some scientific funding agencies put considerable pressure on
research grant applicants to explain how to possibly bring their
-developments to practical applications, i.e. to distribute
+developments to practical applications, \emph{i.e.} to distribute
the software. Debian and its derivative distributions are a
very suitable medium for this purpose.
\DebianMed hopes to help the communication between developers
-for the sharing of data management, i.e. the input for their
+for the sharing of data management, \emph{i.e.} the input for their
tools that should be consistent for all tools contributing
-to a scientific workflow. While some ideas like e.g. getData \marginpar{wiki.debian.org/getData},
+to a scientific workflow. While some ideas like \emph{e.g.} getData \marginpar{wiki.debian.org/getData},
have been developed, this still needs to be amended to suite
the community better.
@@ -934,7 +934,7 @@
%For Debian GNU/Linux to become the race-horse for Free Software in
%health care.
-All that said about Debian, at the end of the day it is the Freeness
+All that said about Debian, at the end of the day it is the freeness
of the software that is important. openSUSE and Fedora, with
slight variations, have adopted much of the principles that Debian
spearheaded. We still need to advance mechanisms like the packaging
More information about the debian-med-commit
mailing list