r63882 - in /website/docs/miniDebConf-paris2010: Makefile miniDebConf-paris2010.pdf miniDebConf-paris2010.tex pet.png

xoswald at users.alioth.debian.org xoswald at users.alioth.debian.org
Sun Oct 17 16:27:45 UTC 2010


Author: xoswald
Date: Sun Oct 17 16:26:55 2010
New Revision: 63882

URL: http://svn.debian.org/wsvn/?sc=1&rev=63882
Log:
Update Paris MiniDebconf slides

Added:
    website/docs/miniDebConf-paris2010/pet.png   (with props)
Modified:
    website/docs/miniDebConf-paris2010/Makefile
    website/docs/miniDebConf-paris2010/miniDebConf-paris2010.pdf
    website/docs/miniDebConf-paris2010/miniDebConf-paris2010.tex

Modified: website/docs/miniDebConf-paris2010/Makefile
URL: http://svn.debian.org/wsvn/website/docs/miniDebConf-paris2010/Makefile?rev=63882&op=diff
==============================================================================
--- website/docs/miniDebConf-paris2010/Makefile (original)
+++ website/docs/miniDebConf-paris2010/Makefile Sun Oct 17 16:26:55 2010
@@ -4,11 +4,9 @@
 all: show
 
 clean:
-	rm -f $(BASENAME).{aux,log,nav,out,pdf,snm,toc,vrb}
+	rm -f $(BASENAME).{aux,log,nav,out,snm,toc,vrb}
 
 build: clean
-	# Run it twice, as otherwise the .nav file won't be there, and no
-	# index will be made
 	pdflatex $(BASENAME).tex
 	pdflatex $(BASENAME).tex
 

Modified: website/docs/miniDebConf-paris2010/miniDebConf-paris2010.pdf
URL: http://svn.debian.org/wsvn/website/docs/miniDebConf-paris2010/miniDebConf-paris2010.pdf?rev=63882&op=diff
==============================================================================
Binary files - no diff available.

Modified: website/docs/miniDebConf-paris2010/miniDebConf-paris2010.tex
URL: http://svn.debian.org/wsvn/website/docs/miniDebConf-paris2010/miniDebConf-paris2010.tex?rev=63882&op=diff
==============================================================================
--- website/docs/miniDebConf-paris2010/miniDebConf-paris2010.tex (original)
+++ website/docs/miniDebConf-paris2010/miniDebConf-paris2010.tex Sun Oct 17 16:26:55 2010
@@ -19,7 +19,7 @@
 
 \title[Debian MiniConf Paris 2010]{\Large{Introducing Perl team}}
 \subtitle{Debian's Perl team structure and organization}
-\author{Xavier Oswald - xoswald at debian.org}
+\author{Xavier Oswald \and Gregor Herrmann \and Dominique Dumont}
 \date{30th October 2010}
 
 %\pgfdeclareimage[height=1cm]{debian-logo}{debian-swirl}
@@ -38,201 +38,300 @@
 
 \frame
 {
-  \frametitle{Contents}
-  \tableofcontents[]   
+	\frametitle{Contents}
+	\tableofcontents[]   
 }
 
 
 \section{Introduction}
-\frame
-{
-  \frametitle{What is the Debian Perl team?}
-
-  \begin{itemize}
-    \item Maintain almost 1700 Perl packages within Debian
-    \item Both official Debian Developers and sponsees
-    \item Around 70-80 committers,\footnote{\url{http://www.ohloh.net/p/pkg-perl}} but most activity from a small core team
-    \item Also indirectly contributes most of the Perl packages in
-      Debian's derivatives (e.g. Ubuntu).
-  \end{itemize}
-}
-
-
-\frame
-{
-  \frametitle{Using Perl on Debian}
-
-  How do you install Perl modules?
-
-  \begin{itemize}
-    \item {\tt apt-get install libfoo-perl}
-    \item Backports for older releases
-    \item CPAN for unpackaged modules
-  \end{itemize}
-
-  CPAN (the tool) is configured to play nicely with Debian packages,
-  but does not install packages when satisfying dependencies.
-}
-
-\section{Perl team organization}
-
-% TODO
+
+\frame
+{
+	\frametitle{About us}
+
+	We are all perl team members
+
+	\begin{itemize}
+		\item \textbf{Xavier Oswald} - xoswald at debian.org\\
+		\begin{itemize}
+			\item Front-Desk member, Applicant Manager, responsible of collab-maint
+			\item Maintain about 50 debian packages and member of 10 teams
+		\end{itemize}
+	
+	\item \textbf{Gregor Herrmann} - gregoa at debian.org\\
+		\begin{itemize}
+			\item TODO 
+			\item TODO
+		\end{itemize}
+
+	\item \textbf{Dominique Dumont} - dominique.dumont at hp.com\\ 
+		\begin{itemize}
+			\item TODO
+			\item TODO
+		\end{itemize}
+	\end{itemize}
+}
+
+
+\frame
+{
+	\frametitle{What is the Debian Perl team?}
+
+	\begin{itemize}
+		\item Maintain almost 1700 Perl packages within Debian
+		\item Both official Debian Developers and sponsees
+		\item Around 70-80 committers,\footnote{\url{http://www.ohloh.net/p/pkg-perl}} but most activity from a small core team
+		\item Also indirectly contributes most of the Perl packages in
+		Debian's derivatives (e.g. Ubuntu).
+	\end{itemize}
+}
+
+
+\frame
+{
+	\frametitle{Using Perl on Debian}
+
+	How do you install Perl modules?
+
+	\begin{itemize}
+		\item {\tt apt-get install libfoo-perl}
+		\item Backports for older releases
+		\item CPAN for unpackaged modules
+	\end{itemize}
+
+	CPAN (the tool) is configured to play nicely with Debian packages,
+		 but does not install packages when satisfying dependencies.
+}
+
+\section{Team organization}
+
+\frame
+{
+	\frametitle{Tools}
+
+	\url{http://pkg-perl.alioth.debian.org}
+	
+	\begin{itemize}
+		\item Infrastructure, \url{http://alioth.debian.org}
+		\item Svn and/or Git
+		\item \url{http://bugs.debian.org}
+		\item IRC (\#debian-perl on OFTC)
+		\item Two mailing lists (discussion, automated messages)
+	\end{itemize}
+
+	What makes the difference ?
+}
+
+\frame
+{
+	\frametitle{Package Entropy Tracker - PET}
+
+	\url{http://pet.alioth.debian.org/}
+
+	\begin{itemize}
+		\item Follow RC bugs
+		\item New upstream
+		\item Ready for upload
+		\item New and Incoming
+		\item \ldots
+	\end{itemize}
+
+	Useful when maintaining a huge amount of packages.
+}
+
+\frame
+{
+	\frametitle{Package Entropy Tracker - PET}
+	
+	\begin{figure}
+		\includegraphics[scale=0.23]{pet}
+	\end{figure}
+}
+
+\frame
+{
+	\frametitle{Managing changelog}
+
+	Headers that are used in changelog files and used by PET
+	
+	\begin{itemize}
+		\item UNRELEASED
+		\item IGNORE-VERSION
+		\item WAITS-FOR
+	\end{itemize}
+
+	\url{http://pkg-perl.alioth.debian.org/changelog.html}
+}
+
+\frame
+{
+	\frametitle{Subversion usage guidelines}
+
+	\begin{itemize}
+		\item Repository anatomy
+		\item Initial upload
+		\item Building a package
+		\item Tagging and Releasing
+		\item Upstream upgrade
+	\end{itemize}
+
+	\url{http://pkg-perl.alioth.debian.org/subversion.html}
+}
+
+\frame
+{
+	\frametitle{Tips and tricks}
+
+	We have a small guide of tips used by perl team members to make life easier
+	when packaging perl modules.
+
+	\begin{itemize}
+		\item Functions
+		\item Aliases
+		\item Scripts
+	\end{itemize}
+
+	Contributions are welcomed.
+
+	\url{http://pkg-perl.alioth.debian.org/tips.html}
+}
+
 
 \section{Packaging perl modules}
 \frame
 {
-  \frametitle{When a module isn't packaged}
-
-  If the Perl module you need is not available, you have several options:
-
-  \begin{enumerate}
-    \item Install it with CPAN, and handle future upgrades yourself.
-    \item File an RFP (Request for package) bug in Debian.\footnote{\url{http://pkg-perl.alioth.debian.org/howto/RFP.html}}
-    \item Build yourself a private Debian package with dh-make-perl, and handle future upgrades yourself.
-    \item Get involved and contribute it back to Debian!
-  \end{enumerate}
-
-  Getting involved is easier than you think.
-}
-
-\frame
-{
-  \frametitle{Creating a package - dh-make-perl}
-
-  dh-make-perl can jump-start creating a new Perl package.
-
-  \begin{itemize}
-    \item {\tt apt-get install dh-make-perl} and read the man page.
-    \item Run {\tt dh-make-perl --cpan Module::Name}.
-    \item Add {\tt --pkg-perl} if you are packaging for the team.
-    \item Then run {\tt debuild} and hack until it builds.
-  \end{itemize}
-
-  If you don't want to contribute it to Debian, you could stop here.
-}
-
-\frame
-{
-  \frametitle{Creating a package - svn-buildpackage}
-
-  Once you have an initial package, you can upload to SVN.  pkg-perl
-  uses a fairly complex SVN layout.\footnote{\url{http://pkg-perl.alioth.debian.org/subversion.html}}
-
-  \begin{itemize}
-    \item Use {\tt svn-inject} to inject new packages
-    \item {\tt svn-buildpackage} for building
-    \item {\tt svn-upgrade} for upstream upgrades
-  \end{itemize}
-
-  Set the suite to `UNRELEASED' in debian/changelog for now.
-
-  Commits are logged to IRC.
-}
-
-\frame
-{
-  \frametitle{Creating a package - cowbuilder}
-
-  One of the more tricky parts of packaging is getting the build
-  dependencies correct.  cowbuilder is a tool for building packages in
-  a clean chroot:
-
-  \begin{itemize}
-    \item {\tt sudo apt-get install cowbuilder}
-    \item {\tt sudo cowbuilder --create}
-    \item {\tt sudo cowbuilder --build libfoo-perl\_1.0-1.dsc}
-    \item Can also integrate it into svn-buildpackage.
-  \end{itemize}
-
-  Check the test suite gets run!
-}
-
-\frame
-{
-  \frametitle{Creating a package - lintian}
-
-  We want Debian packages to be of high quality.  lintian is a tool
-  that can check for common problems.
-
-  \begin{itemize}
-    \item {\tt sudo apt-get install lintian}
-    \item {\tt lintian -iI --pedantic --color=auto libfoo-perl\_1.0-1\_amd64.changes}
-    \item Can also integrate it with debuild/cowbuilder
-  \end{itemize}
-}
-
-\frame
-{
-  \frametitle{Creating a package - getting feedback}
-
-  Once you think your package is ready for review, mark it as such:
-
-  \begin{itemize}
-    \item {\tt dch -r}
-    \item (or `s/UNRELEASED/unstable/' in debian/changelog)
-    \item {\tt svn commit -m `dch -r; ready for review'}
-  \end{itemize}
-
-  The package status will be changed automatically in PET.
-}
-
-\frame
-{
-  \frametitle{Creating a package - what next?}
-
-  \begin{itemize}
-    \item You are likely to get feedback via IRC or email.
-    \item Sometimes TODO lists are left for you in debian/changelog by the
-      reviewer, with the suite set back to UNRELEASED.
-    \item Once the reviewer is happy, they will upload the package and
-      tag the release in SVN.
-  \end{itemize}
+	\frametitle{When a module isn't packaged}
+
+	If the Perl module you need is not available, you have several options:
+
+	\begin{enumerate}
+		\item Install it with CPAN, and handle future upgrades yourself.
+		\item File an RFP (Request for package) bug in Debian.\footnote{\url{http://pkg-perl.alioth.debian.org/howto/RFP.html}}
+		\item Build yourself a private Debian package with dh-make-perl, and handle future upgrades yourself.
+		\item Get involved and contribute it back to Debian!
+	\end{enumerate}
+
+	Getting involved is easier than you think.
+}
+
+\frame
+{
+	\frametitle{Creating a package - dh-make-perl}
+
+	dh-make-perl can jump-start creating a new Perl package.
+
+	\begin{itemize}
+		\item {\tt apt-get install dh-make-perl} and read the man page.
+		\item Run {\tt dh-make-perl --cpan Module::Name}.
+		\item Add {\tt --pkg-perl} if you are packaging for the team.
+		\item Then run {\tt debuild} and hack until it builds.
+	\end{itemize}
+
+	If you don't want to contribute it to Debian, you could stop here.
+}
+
+\frame
+{
+	\frametitle{Creating a package - svn-buildpackage}
+
+	Once you have an initial package, you can upload to SVN.  pkg-perl
+		uses a fairly complex SVN layout.\footnote{\url{http://pkg-perl.alioth.debian.org/subversion.html}}
+
+	\begin{itemize}
+		\item Use {\tt svn-inject} to inject new packages
+		\item {\tt svn-buildpackage} for building
+		\item {\tt svn-upgrade} for upstream upgrades
+	\end{itemize}
+
+	Set the suite to `UNRELEASED' in debian/changelog for now.
+
+		Commits are logged to IRC.
+}
+
+\frame
+{
+	\frametitle{Creating a package - cowbuilder}
+
+	One of the more tricky parts of packaging is getting the build
+		dependencies correct.  cowbuilder is a tool for building packages in
+		a clean chroot:
+
+	\begin{itemize}
+		\item {\tt sudo apt-get install cowbuilder}
+		\item {\tt sudo cowbuilder --create}
+		\item {\tt sudo cowbuilder --build libfoo-perl\_1.0-1.dsc}
+		\item Can also integrate it into svn-buildpackage.
+	\end{itemize}
+
+	Check the test suite gets run!
+}
+
+\frame
+{
+	\frametitle{Creating a package - lintian}
+
+	We want Debian packages to be of high quality.  lintian is a tool
+		that can check for common problems.
+
+	\begin{itemize}
+		\item {\tt sudo apt-get install lintian}
+		\item {\tt lintian -iI --pedantic --color=auto libfoo-perl\_1.0-1\_amd64.changes}
+		\item Can also integrate it with debuild/cowbuilder
+	\end{itemize}
+}
+
+\frame
+{
+	\frametitle{Creating a package - getting feedback}
+
+	Once you think your package is ready for review, mark it as such:
+
+	\begin{itemize}
+		\item {\tt dch -r}
+		\item (or `s/UNRELEASED/unstable/' in debian/changelog)
+		\item {\tt svn commit -m `dch -r; ready for review'}
+	\end{itemize}
+
+	The package status will be changed automatically in PET.
+}
+
+\frame
+{
+	\frametitle{Creating a package - what next?}
+
+	\begin{itemize}
+		\item You are likely to get feedback via IRC or email.
+		\item Sometimes lists of things to do are left for you in debian/changelog by the
+		reviewer, with the suite set back to UNRELEASED.
+		\item Once the reviewer is happy, they will upload the package and
+		tag the release in SVN.
+	\end{itemize}
 }
 
 \section{Getting involved}
-\frame
-{
-  \frametitle{Getting involved - tools}
-
-  The Perl team uses tools to speed up packaging.
-
-  \begin{itemize}
-    \item alioth.debian.org for team management
-    \item SVN for most packages, but a few are stored in git
-    \item \url{http://bugs.debian.org/}
-    \item Package Entropy Tracker (PET)
-    \item IRC (\#debian-perl on OFTC)
-    \item Two mailing lists - one for discussion, one to receive
-      automated messages
-  \end{itemize}
-
-  \url{http://pkg-perl.alioth.debian.org/} links to all of these.
-}
-
-\frame
-{
-  \frametitle{Getting involved - joining the team}
-  \begin{itemize}
-    \item Create an alioth account
-    \item Apply to join the pkg-perl group on alioth
-    \item Introduce yourself on the debian-perl mailing list
-    \item Optionally use IRC for realtime communication
-  \end{itemize}
-
-  \url{http://wiki.debian.org/Teams/DebianPerlGroup/Welcome}
+
+\frame
+{
+	\frametitle{Getting involved - joining the team}
+	\begin{itemize}
+		\item Create an alioth account
+		\item Apply to join the pkg-perl group on alioth
+		\item Introduce yourself on the debian-perl mailing list
+		\item Optionally use IRC for realtime communication
+	\end{itemize}
+
+	\url{http://wiki.debian.org/Teams/DebianPerlGroup/Welcome}
 }
 
 \section{Conclusion}
 
-%TODO
-
-\frame
-{
-  \frametitle{Questions?}
-
-  \begin{center}
-    Thanks for your attention
-  \end{center}
+\frame
+{
+	\frametitle{Questions?}
+
+	\begin{center}
+		Thanks for your attention\footnote{\url{http://pkg-perl.alioth.debian.org/docs/miniDebConf-paris2010/}}
+	\end{center}
 }
 
 \end{document}

Added: website/docs/miniDebConf-paris2010/pet.png
URL: http://svn.debian.org/wsvn/website/docs/miniDebConf-paris2010/pet.png?rev=63882&op=file
==============================================================================
Binary file - no diff available.

Propchange: website/docs/miniDebConf-paris2010/pet.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream




More information about the Pkg-perl-cvs-commits mailing list