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

[Yaroslav Halchenko]

Author: yoh
Date: 2010-12-09 14:35:48 +0000 (Thu, 09 Dec 2010)
New Revision: 5562

Modified:
   trunk/community/papers/11_med-floss_luxemburg/paper-text.tex
Log:
worked on abstract a bit -- might need to be shortened

Modified: trunk/community/papers/11_med-floss_luxemburg/paper-text.tex
===================================================================
--- trunk/community/papers/11_med-floss_luxemburg/paper-text.tex	2010-12-09 14:24:44 UTC (rev 5561)
+++ trunk/community/papers/11_med-floss_luxemburg/paper-text.tex	2010-12-09 14:35:48 UTC (rev 5562)
@@ -6,27 +6,39 @@
   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.
-
-  At the time, the communities in computational biology, medical
+  % 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
-  helped in bringing those packages together. And the \DebianMed project 
-  provides a software management infrastructure to help the
-  communication between those who provide those packages, e.g. to
+  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, it has shown that the integrative
-  \DebianMed project has positive effects beyond the regular Debian users.
-  Many ties between those providing the packages and those who develop
-  the software have been established. Larger development teams upload
-  their Debian packages directly. This communicates the experience
-  of the developers back into the distribution.
+  Over the past decade, the integrative
+  \DebianMed project has shown positive effects beyond benefitting
+  regular Debian users alone.
+  Many ties have been established between original software developers
+  and Debian package maintainers.  Large development teams started to upload
+  their Debian packages directly. That communicated the experience
+  of the developers back into the distribution and made medical
+  software a constituent member of the Debian distribution.
 
-  The ideas behind the Debian Med evolved into the concept of
-  Debian Pure Blends. Today, there are Blends forming Debian Edu,
-  Debian Science, DebiChem (chemistry), Debian GIS, DeMuDi and
-  (multimedia) and others.
+  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 others are inactive enough to not mention them here
 \end{abstract}