[med-svn] r5565 - trunk/community/papers/11_med-floss_luxemburg

[Andreas Tille]

Author: tille
Date: 2010-12-09 15:43:59 +0000 (Thu, 09 Dec 2010)
New Revision: 5565

Modified:
   trunk/community/papers/11_med-floss_luxemburg/paper-text.tex
Log:
Some orthographic fixes


Modified: trunk/community/papers/11_med-floss_luxemburg/paper-text.tex
===================================================================
--- trunk/community/papers/11_med-floss_luxemburg/paper-text.tex	2010-12-09 15:18:54 UTC (rev 5564)
+++ trunk/community/papers/11_med-floss_luxemburg/paper-text.tex	2010-12-09 15:43:59 UTC (rev 5565)
@@ -5,17 +5,16 @@
   free medical software into the focus of users. Those may be IT
   service providers for smaller clinics, the doctors themselves,
   researchers in pre-clinical environments or just skilled enthusiasts
-  with an ambition to apply their talents the biomedical domain.
-  % yoh: I do not see much of sense in paragraph brake here
-  At that time, the communities in computational biology, medical
-  imaging and medical informatics already had a number of
-  high-quality Free Software solutions. Debian as a Linux distribution
-  provided a solid 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 missing glue packages to translate data formats or to
-  point out conflicts in the naming of binaries.
+  with an ambition to apply their talents the biomedical domain.  At
+  that time, the communities in computational biology, medical imaging
+  and medical informatics already had a number of high-quality Free
+  Software solutions. Debian as a Linux distribution provided a solid
+  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
+  missing glue packages to translate data formats or to point out
+  conflicts in the naming of binaries.
 
   Over the past decade, the integrative
   \DebianMed project has shown positive effects beyond benefitting
@@ -26,19 +25,19 @@
   of the developers back into the distribution and made medical
   software a constituent member of the Debian distribution.
 
-  The ideas behind the Debian Med generalized 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 different domains of applications.  Blends task
-  pages complemented canonical Debian package listing with additional
-  information (e.g. scientific references) and also covered software
-  products which are relevant for a given domain, but not yet
-  integrated into Debian.  Combination of Blends teams and Debian
-  sponsorship approaches allowed to significantly eased the way to
-  contribute to Debian, thus making it possible to eliminate necessity
-  for the derived distributions and provide customized versions of
-  Debian, suchas \DebianMed, within Debian infrastructure.
+  The ideas behind the Debian Med 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
+  different domains of applications.  Blends task pages complemented
+  canonical Debian package listing with additional information
+  (e.g. scientific references) and also covered software products
+  which are relevant for a given domain, but not yet integrated into
+  Debian.  Combination of Blends teams and Debian sponsorship
+  approaches allowed to significantly eased the way to contribute to
+  Debian, thus making it possible to eliminate necessity for the
+  derived distributions and provide customised versions of Debian,
+  such as \DebianMed, within Debian infrastructure.
   % the others are inactive enough to not mention them here
 \end{abstract}
 
@@ -65,7 +64,7 @@
 the community as much as possible to develop itself and to develop
 the contacts to their users. Debian as a Linux distribution already
 supports the distribution of the software, rendering it instantly
-available. Modularization aspect of Debian does not only reduces the packaging work by allowing to
+available. Modularisation aspect of Debian does not only reduces the packaging work by allowing to
 depend on other packages, it allows for easier maintenance of the
 complete system since updates and fixes in the core libraries most
 of the time do
@@ -93,8 +92,8 @@
 \subsection{Status of Free Software in health care}
 
 More common programs like a web server, or a mail user agent are installed
-manigfold and have a very large user base. This increases the chance to  \marginpar{what \emph{manigfold} was supposed to be?}
-attract gifted programmers who could have an almost intiutive spontaneous
+manifold and have a very large user base. This increases the chance to  \marginpar{what \emph{manifold} was supposed to be?}
+attract gifted programmers who could have an almost intuitive spontaneous
 understanding on the structure of the control flow of the program
 (by understanding the problem domain extremely well) and could map
 this to the source code (since they would have solve the problem
@@ -102,7 +101,7 @@
 implement any change they need for themselves
 without too much of a personal investment and contribute it back to
 the project.  For the
-lager challenges there may be many different driving forces coming
+larger challenges there may be many different driving forces coming
 together. \marginpar{explain?}
 
 The fact that a piece of software is needed for one's own work is often
@@ -265,12 +264,12 @@
     upgraded to the future stable release.  This makes sure that new
     Debian releases can be rolled out smoothly in release critical
     applications.
-  \item[Package Installation and De-installation] The tool piuparts
-    tests that .deb packages (as used by Debian) handle  installation,
-    upgrading, and removal correctly. It does this by creating a
-    minimal Debian installation in a chroot, and installing,
-    upgrading, and removing packages in that environment, and
-    comparing the state of the directory tree before and after.
+  \item[Package Installation and De-installation] The tool
+    \package{piuparts} tests that .deb packages (as used by Debian)
+    handle installation, upgrading, and removal correctly. It does
+    this by creating a minimal Debian installation in a chroot, and
+    installing, upgrading, and removing packages in that environment,
+    and comparing the state of the directory tree before and after.
 \end{description}
 
 \subsubsection{Build daemons}