[Cdd-commits] r1020 - cdd/trunk/docs/talks/200808_debconf8
CDD Subversion Commit
noreply at alioth.debian.org
Thu Aug 7 13:57:16 UTC 2008
Author: tille
Date: Thu Aug 7 13:57:15 2008
New Revision: 1020
Added:
cdd/trunk/docs/talks/200808_debconf8/
cdd/trunk/docs/talks/200808_debconf8/bugs_overview.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/cdd-paper.tex
cdd/trunk/docs/talks/200808_debconf8/cdd.tex
cdd/trunk/docs/talks/200808_debconf8/ddtp_detail_amide-1.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/ddtp_detail_amide-2.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/ddtp_detail_amide.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/ddtp_stats.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/index_members.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/index_svn.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/index_todo.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/qa_features.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/qa_new_upstream.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/task_med-bio.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/task_med-epi_unoff.png (contents, props changed)
cdd/trunk/docs/talks/200808_debconf8/task_med-imaging_prospective.png (contents, props changed)
Log:
Inject current status of talk because people.d.o is down
Added: cdd/trunk/docs/talks/200808_debconf8/bugs_overview.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/cdd-paper.tex
==============================================================================
--- (empty file)
+++ cdd/trunk/docs/talks/200808_debconf8/cdd-paper.tex Thu Aug 7 13:57:15 2008
@@ -0,0 +1,367 @@
+% cdd-paper.tex
+% Authors: Andreas Tille
+% Revisions: August 2008
+
+\documentclass{article}
+\usepackage{times}
+\newif\ifpdf
+\ifx\pdfoutput\undefined
+ \pdffalse % we do not use PDFLaTeX
+ \PassOptionsToPackage{dvips}{graphics}
+\else
+ \pdfoutput=1 % we use PDFLaTeX
+ \pdftrue
+ \PassOptionsToPackage{pdftex}{graphics}
+\fi
+\usepackage{graphics,color}
+\usepackage[latin1]{inputenc}
+\ifpdf
+ \PassOptionsToPackage{pdftex,colorlinks=true,urlcolor=blue,linkcolor=blue}{hyperref}
+ \pdfcompresslevel=9
+\else
+ \usepackage{url}
+\fi
+\usepackage{html}
+\usepackage[T1]{fontenc}
+%\usepackage[english]{babel} %%% conflicts with \cite !!!
+\usepackage{xspace}
+
+\newcommand{\Path}[1]{\path{#1}\xspace}
+\newcommand{\onlynameurl}[1]{\Path{#1}}
+\newcommand{\package}[1]{\Path{#1}}
+\newcommand{\command}[1]{\Path{#1}}
+\newcommand{\file}[1]{\Path{#1}}
+
+\newcommand{\Debian}{\texttt{Debian}\xspace}
+\newcommand{\DebianGL}{\Debian \texttt{GNU/Linux}\xspace}
+\newcommand{\CDD}{\texttt{Custom Debian Distribution}}
+
+\newcommand{\printemail}[1]{%
+ \ifpdf
+ \href{mailto:#1}{$<$#1$>$}%
+ \else
+ \onlynameurl{$<$#1$>$}%
+ \fi
+ \xspace
+}
+\newcommand{\printurl}[2]{%
+ \htmladdnormallink{#2}{http://#1}%
+ \xspace
+}
+
+\newcommand{\myinsertgraphic}[1]{%
+ \ifpdf
+ % \resizebox{#2}{#3}{%
+ %\resizebox{80mm}{53mm}{%
+ \includegraphics{#1}%
+ %}%
+ \else
+ \includegraphics{#1}%
+ %%\epsfig{file=#1.eps}%, height=#2, width=#3}
+ \fi
+}
+
+\def\halfsloppy{%
+ \tolerance 1250%
+ \emergencystretch 0.75em}
+
+% from http://user.it.uu.se/~matkin/programming/TeX/hacks.tex
+% \smiley
+% \frowny
+% Here we have a smile face (and a frowny face) to use together with
+% text in horisontal mode
+\begingroup
+ \def\facewith#1{$\bigcirc\mskip-13.3mu{}^{..}
+ \mskip-11mu\scriptscriptstyle#1\ $}
+ \xdef\frowny{\facewith\frown}
+ \xdef\smiley{\facewith\smile}
+\endgroup
+
+\date{DebConf 8, Mar del Plata, August 2008}
+
+\begin{document}
+\title{Custom \Debian Distributions\ - \\
+\large Making Debian the distribution of choice for specific work fields}
+
+\author{Andreas Tille}
+
+\maketitle
+
+\begin{abstract}
+The idea of Custom Debian Distributions was born at DebConf 3 in Oslo
+and has turned now into a solid tool set that can be used to organise
+packages targeting at a specific work field inside Debian in a quite
+efficient way. After five years it is time for a report about status
+and success as well as continuing to spread the idea amongst people to
+enable them to spend a minimum effort for the adoption of the tools to
+get a maximum effect in maintaining a CDD.
+
+One goal of Custom Debian Distributions is to form a group of Debian
+developers who care for a specific set of packages that are used in
+the day to day work of a certain user group. The fact that Debian has
+grown to the largest pool of ready to install packages on the net has
+led to the side effect that it is hard to maintain for beginners. A
+Custom Debian Distribution adds some substructure to the currently
+flat pool of 15000+X packages without a user oriented structure.
+These substructures are intended to put a focus on special user
+interest. These substructures are not based on technical matters like
+Debian installer team, porting teams or teams that are focussing to
+implement programming language policies.
+
+There are some similarities to Debian-i18n which also has the pure
+goal to serve the needs of certain end user groups with the difference
+that the users are grouped not according to their field of work but
+according to their language. In fact it makes even sense to create
+CDDs for languages that require certain technical means to optimally
+support the language regarding direction of writing, special fonts
+etc. It is known that some countries in Asia builded Debian % TODO: WHICH COUNTRY, NAME OF DIST
+derivatives for this purpose but in principle it is not necessary to
+derive - the better solution is to make Debian more flexible by
+starting a CDD effort inside Debian.
+
+The talks will give some examples from the success of CDDs like
+Debian Edu and Debian Med. One very important outcome of the CDD
+effort is the ongoing reunification of Linex - the Debian derived
+distribution that is used in all schools in Extremadura - with
+Debian Edu. This step means that Debian gets a very large
+implementation in all schools of Extremadura while on the other hand
+the effort of development for the people who invented Linex will be
+reduced. Debian featuring Debian Edu now has a very good chance to
+become a really good international school distribution because it has
+roots in five countries (Norway, Spain, France, Germany and Japan) and
+might become attractive for many more.
+
+The success stories of CDDs would not have been possible outside
+Debian and thus leaving the path to build Zillions of Debian
+derivatives that reach a very small user base and working together
+inside Debian is the main idea of the talk. To make this idea more
+attractive in the second part of the talk a description of tools that
+were developed in the CDD effort will be presented. Especially the
+newly developed web tools that give a good overview about the
+packages that are useful for a certain field of work and the QA tools
+that enable the CDD team members to easily get an overview about
+packages that need some action. So if people are not yet convinced
+that a CDD for their purpose makes sense we will catch them by the
+tools they might get for free if they follow the proposed strategy.
+\end{abstract}
+
+
+
+\section{Symbiosis between experts and developers}
+
+
+As it was explained in last years CDD talk 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 of 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.
+
+The tricky part in developing a CDD is now to tie a solid network of
+Debian developers, upstream developers (``developing experts'') and
+users (experts in a defined field). It has turned out that gathering
+upstream developers into a CDD team is quite often not very hard.
+There are several upstream developers who try to become Debian
+Maintainer status - a concept which turned out to be quite
+successfully. The rationale behind this is if it comes to field
+specific software it is often written by experts in this field to
+solve the tasks of their daily work. Observations have shown that
+this software while showing great features regarding the task which
+should be solved there are often weak parts in the build system or in
+the general handling of using libraries or wide spread tools. This is
+exactly the point where Debian developers have good experiences and
+are able to provide technical help.
+
+So it happens quite often that upstream developers of field specific
+applications are quite happy if Debian developers want to build Debian
+packages of the software because they anticipate enhancements of their
+build system and a security audit. Last but not least they expect a
+wide distribution of their work to reach a large user base easily.
+
+
+\section{Attracting people by providing interesting technical base}
+
+The acceptance of new methods is drastically higher if the techniques
+provided are convincing enough and provide interesting features for
+the target audience. Considering this we tried to develop simple ways
+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 metapackages. The other
+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
+\printurl{ddtp.debian.net}{Debian Description Translation Project} and
+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 participants and the quality of
+translations - especially those of specific packages which need some
+expert knowledge for proper translation - might increase.
+
+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 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
+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
+using the package themselves instead by Joey Randomtranslator who
+tries his best in a word by word translation but if he does not know
+the real usage of the package it is hard to provide a really useful
+translation.
+
+Once we were able to rise users interest they might be interested to
+do the next step to install and try the packages in question. This is
+the point where the upstream developer of the software becomes a new
+user which might report bugs or give hints for enhancements and might
+become a coworker finally. This way Debian, or more specifically the
+CDD that supports the specific field, has helped to increase the user
+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 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
+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
+\printurl{savannah.gnu.org}{Savannah} or
+\printurl{sourceforge.com}{SourceForge} or even implementing a version
+control system to promote group development. In contrary if an other
+specialist is seeking for a solution for the same problem he has to
+invent extended Google queries to find the project in question -- if
+he has the idea to seeking and before he is starting simply from
+scratch.
+
+Some volunteers have realised this situation and provide extensive
+link lists either on static HTML pages or Wikis to enable others to
+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 for
+instance there is a comparable effort to package biological Free
+Software done by
+\printurl{kambing.ui.edu/gentoo-portage/sci-biology/}{Gentoo}
+or \printurl{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
+metapackages, 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 distributed 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. There is a similar situation in the internationalisation
+teams: There is a well defined group of users (speakers of a certain
+language) who need special support (translations at various places)
+and it make sense if language teams just work together and use common
+tools like DDTP server and others.
+
+While this translation work is one part of the internationalisation
+team it can not stop here. It is also about proving that Debian is
+flexible enough to incorporate this kind of changes instead of forcing
+users to make language based forks of Debian. Unfortunately there are
+many people out there who feature a wrong concept of using Free
+Software. They read the license as they are allowed to modify the
+software as modifying their local copy and tweak it until it fits
+their needs. They treat this constant forking as the normal way to
+customise their distribution. The internationalisation team has done
+a good job in propagating the idea that it is better to include
+translations into Debian than adding translations over and over for
+every new release of Debian.
+
+In principle the maintainers of a CDD have the same job: Attracting
+derivers who have not yet understood the power of internal
+customisation inside a CDD to reach their goal -- optimal support of
+their users -- more efficiently. The most convincing example how a
+CDD managed to merge a derivative back to Debian is that the
+educational branch of \printurl{www.linex.org}{LinEx} is
+working on unification with Debian Edu since end of year 2007.
+
+\section{Techniques}
+
+The techniques used are based on sorting certain packages of the
+Debian pool into certain remits or in the terminology we have chosen
+in CDDs ``tasks''. So the tasks files are listing dependencies from
+Debian packages and different tools are using these as common source
+of information.
+
+\subsection{Building metapackages and tasksel descriptions}
+
+The \package{cdd-dev} can be used to build a set of metapackages and
+tasksel descriptions. Because the technique is described in very
+detail in the \printurl{cdd.alioth.debian.org/cdd}{article about CDD}
+there is no need to repeat the content here. I would rather ask you
+to follow the link and especially read section {\em 6.1 Metapackages}.
+
+The build process using \package{cdd-dev} also included the creation
+of a \package{CDD-tasks} package which contains information for
+tasksel to enable the tasks of a CDD via tasksel.
+
+
+\subsection{Web pages based on common scripts}
+
+A quite new feature are the web pages that are builded based on the
+very same information that is used to build the metapackages. This
+enables users to get a very quick overview because they see all
+packages included in the task together with the description. Because
+the target audience does not necessarily is comfortable with English
+language the descriptions are even translated in case there is such a
+translation provided by the \printurl{ddtp.debian.net}{Debian
+ Description Translation Project}. Such pages are available for
+the following projects:
+
+\begin{itemize}
+ \item \printurl{cdd.alioth.debian.org/edu/tasks}{Debian Edu}
+ \item \printurl{cdd.alioth.debian.org/gis/tasks}{Debian GIS}
+ \item \printurl{cdd.alioth.debian.org/junior/tasks}{Debian Junior}
+ \item \printurl{debian-med.alioth.debian.org/tasks}{Debian Med}
+ \item \printurl{cdd.alioth.debian.org/science/tasks}{Debian Science}
+\end{itemize}
+
+In addition to the packages existing inside Debian there is an easy
+way to specify prospective packages that should be included into
+Debian in the future. These packages are listed on the web pages
+as well. To read more about this feature just have a look into the
+\printurl{cdd.alioth.debian.org/cdd}{article about CDD} especially
+section {\em 8.1 Existing and prospective packages}.
+
+There is no need to copy the information of the just existing article
+about CDD which is continuously updated and thus this document ends
+here with the strong recommendation to read the technical details
+there.
+
+\end{document}
Added: cdd/trunk/docs/talks/200808_debconf8/cdd.tex
==============================================================================
--- (empty file)
+++ cdd/trunk/docs/talks/200808_debconf8/cdd.tex Thu Aug 7 13:57:15 2008
@@ -0,0 +1,280 @@
+%% Files that are needed for LaTeX processing (style + inputs) are available
+%% relative to the download place in the directory ../inputs, the images in
+%% ../img
+%%
+% \documentclass[compress,trans]{beamer}
+\documentclass[compress]{beamer}
+
+\mode<presentation>
+{
+ \usetheme{Wernigerode}
+}
+
+\usepackage{debian-at,debian-freebeer}
+
+\title{Custom \Debian Distributions}
+
+\subtitle{Making Debian the distribution of choice for specific work fields}
+
+\author{\AndreasTille}
+
+%\institute{\Debian}
+\institute{\link{http://www.debconf.org/debconf8/}{Debian Conference 8}}
+
+\date{Mar del Plata, August 12, 2008}
+
+% New definition of varcolor
+\definecolor{VarColor}{rgb}{0,0,1} %
+
+% from http://user.it.uu.se/~matkin/programming/TeX/hacks.tex
+% \smiley
+% \frowny
+% Here we have a smile face (and a frowny face) to use together with
+% text in horisontal mode
+\begingroup
+ \def\facewith#1{$\bigcirc\mskip-13.3mu{}^{..}
+ \mskip-11mu\scriptscriptstyle#1\ $}
+ \xdef\frowny{\facewith\frown}
+ \xdef\smiley{\facewith\smile}
+\endgroup
+
+
+\begin{document}
+
+\begin{frame}[plain]
+ \titlepage
+\end{frame}
+
+
+\begin{frame}
+ \frametitle{Overview}
+ %\renewcommand{\baselinestretch}{2.5}%
+ \baselineskip=25pt%
+ \tableofcontents%[pausesections]
+\end{frame}
+
+%\mode<trans>
+\mode<presentation>
+{
+ \beamerdefaultoverlayspecification{<+->}
+ \setbeamercovered{dynamic}
+}
+
+\section{Symbiosis between experts and developers}
+
+\subsection{Shortintro CDD}
+\begin{frame}
+ \frametitle{Reminder: Basic goal of CDDs}
+ \begin{itemize}
+ \item Debian $\mathsf{>}$ 15000 packages
+ \item Users interested in \emph{subset}
+ \item Groups of specialised users
+ \item Easy installation and configuration
+ \item While \Debian stays general support specialists as well
+ \item \textbf{No derivative} from Debian
+ \item[] \goal{Basic idea: Do not make a separate distribution but
+ make Debian fit for special purpose instead}
+ \end{itemize}
+\end{frame}
+
+\begin{frame}
+ \frametitle{Looking from outside}
+
+ \begin{itemize}
+ \item Doctor and friend of mine:\newline
+ ``Debian developers == {\em `secret society'} '' \smiley
+ \item We know we are everything but secret
+ \item At least one feature of secrecy: concealment
+ \begin{itemize}
+ \item Concealment inside advertising noise of proprietary
+ products
+ \item Concealment by disunity
+ \end{itemize}
+ \item[\MyBigRightArrow] \result{Breaking the secret by advertising complete solutions}
+ \end{itemize}
+\end{frame}
+
+\subsection{Missing link upstream developer -- user}
+\begin{frame}
+ \frametitle{Upstream - Debian Developer - User}
+
+ \begin{itemize}
+ \item Tie a solid network of Debian developers, upstream
+ developers (``developing experts'') and users
+ \item Rationale: Experts in this field need help in build system
+ / packaging
+ \item Upstream anticipates enhancements of build system and
+ security audit
+ \item Finally support upstream developers to become Debian maintainers
+ \end{itemize}
+\end{frame}
+
+
+\begin{frame}
+ \frametitle{Attracting people by providing interesting techniques}
+ \begin{itemize}
+ \item Acceptance of new methods higher if the techniques provided
+ are convincing enough
+ \item Simple ways to categorise packages (``tasks files'')
+ \item Internationalised web pages displaying relevant packages
+ \item Key documentation feature
+ \item If
+ \end{itemize}
+\end{frame}
+
+
+\section{Used techniques}
+
+\subsection{Using \package{cdd-dev}}
+
+\begin{frame}
+ \frametitle{Tasks files}
+\begin{block}{Similar to \file{debian/control}}
+ \fix{Task:} \var{taskname} \newline
+ \fix{Description:} \var{Shortdescription} \newline
+ \hspace*{2mm}\var{Longdescription} \newline
+
+ \fix{Depends:} \var{some dependant packages} \newline
+ \fix{Recommends:} \var{some recommended packages} \newline
+ \fix{Suggests:} \var{some suggested packages} \newline
+\end{block}
+\end{frame}
+
+\begin{frame}
+ \frametitle{\package{cdd-dev}}
+ \begin{itemize}
+ \item Verify availability of \fix{Depends} / \fix{Recommends}
+ \item Turn \fix{Depends} into \fix{Recommends}
+ \item Packages unavailable in \dist{main} will be turned into
+ \fix{Suggests}
+ \item Create proper \file{debian/control} file to build valid
+ metapackages
+ \item Create \file{tasksel} control file \file{<CDD>-tasks.desc}
+ \end{itemize}
+\end{frame}
+
+\subsection{Web tools}
+
+\begin{frame}
+ \frametitle{Further usage of tasks files}
+ \begin{itemize}
+ \item Debian Edu uses information to build installation media
+ \item Debian Med has developed several web tools
+ \begin{itemize}
+ \item Bugs overview
+ \item Description translation (DDTP) status
+ \item QA features
+ \item Tasks overview
+ \end{itemize}
+ \item Tasks overview is factorised for all CDDs
+ \end{itemize}
+\end{frame}
+
+\begin{frame}
+ \frametitle{Bugs overview}
+ \vspace{-5mm}
+ \begin{center}
+ \resizebox{120mm}{!}{\includegraphics{bugs_overview}}
+ \end{center}
+
+\end{frame}
+
+\begin{frame}
+ \frametitle{Support Debian Description Translation project}
+ \vspace{-1mm}
+ \begin{center}
+ \resizebox{60mm}{!}{\includegraphics{ddtp_stats}}
+ \end{center}
+\end{frame}
+
+\begin{frame}
+ \frametitle{Users deserve translated descriptions}
+ \begin{center}
+ \resizebox{100mm}{!}{\includegraphics{ddtp_detail_amide-1}}
+ \end{center}
+\end{frame}
+
+\begin{frame}
+ \frametitle{Give experts a chance to provide proper translations}
+ \begin{center}
+ \resizebox{100mm}{!}{\includegraphics{ddtp_detail_amide-2}}
+ \end{center}
+\end{frame}
+
+\begin{frame}
+ \vspace{-5mm}
+ \frametitle{Watching upstream}
+ \begin{center}
+ \resizebox{120mm}{!}{\includegraphics{qa_new_upstream}}
+ \end{center}
+\end{frame}
+
+\begin{frame}
+ \vspace{-2mm}
+ \frametitle{Putting QA info into CDD frame}
+ \begin{center}
+ \resizebox{110mm}{!}{\includegraphics{qa_features}}
+ \end{center}
+\end{frame}
+
+\subsection{Prospective packages and todo list}
+
+\begin{frame}
+ \frametitle{Additional fields}
+\begin{block}{Prospective packages}
+ \fix{Depends:} \var{not yet existing package name} \newline
+ \fix{Homepage:} \var{Homepage of project} \newline
+ \fix{Responsible:} \var{Future maintainer (optional)} \newline
+ \fix{License:} \var{License of software to package} \newline
+ \fix{WNPP:} \var{Bug number (optional)} \newline
+ \fix{Pkg-URL:} \var{URL to unofficial package} \newline
+ \fix{Pkg-Description:} \var{Description of prospective package} \newline
+\end{block}
+\end{frame}
+
+\begin{frame}
+ \vspace{-2mm}
+ \frametitle{Tasks pages}
+ \begin{center}
+ \resizebox{122mm}{!}{\includegraphics{task_med-bio}}
+ \end{center}
+\end{frame}
+
+\begin{frame}
+ \vspace{-2mm}
+ \frametitle{Inofficial packages}
+ \begin{center}
+ \resizebox{122mm}{!}{\includegraphics{task_med-epi_unoff}}
+ \end{center}
+\end{frame}
+
+\begin{frame}
+% \vspace{-1mm}
+ \frametitle{Todo: prospective packages}
+ \begin{center}
+ \resizebox{100mm}{!}{\includegraphics{task_med-imaging_prospective}}
+ \end{center}
+\end{frame}
+
+
+\section{Future}
+
+
+\begin{frame}
+ \frametitle{Try to establish technique}
+ \begin{itemize}
+ \item Further enhancements
+ \item Make projects like DebiChem and Debian-Accessibility using
+ the framework
+ \item Try to bring back external projects to Debian by providing
+ attractive tools
+ \end{itemize}
+\end{frame}
+
+\input med-end-en.tex
+
+\end{document}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%5
+\endinput
+
Added: cdd/trunk/docs/talks/200808_debconf8/ddtp_detail_amide-1.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/ddtp_detail_amide-2.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/ddtp_detail_amide.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/ddtp_stats.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/index_members.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/index_svn.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/index_todo.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/qa_features.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/qa_new_upstream.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/task_med-bio.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/task_med-epi_unoff.png
==============================================================================
Binary file. No diff available.
Added: cdd/trunk/docs/talks/200808_debconf8/task_med-imaging_prospective.png
==============================================================================
Binary file. No diff available.
More information about the Cdd-commits
mailing list