Skip to content
GitLab
Commit cfdc14eb authored by Nicolas Dandrimont's avatar Nicolas Dandrimont 🤔
Browse files

Complete slides

parent adade298
Hide whitespace changes
Inline Side-by-side
2012-11-25_MiniDebconfParis/debexpo.tex
View file @ cfdc14eb
...@@ -51,6 +51,7 @@ ...@@ -51,6 +51,7 @@
\end{frame} \end{frame}
\subsection{What is this talk about}
\begin{frame} \begin{frame}
\frametitle{What this talk is not about} \frametitle{What this talk is not about}
...@@ -62,7 +63,6 @@ ...@@ -62,7 +63,6 @@
\end{frame} \end{frame}
\subsection{What is this talk about}
\begin{frame} \begin{frame}
\frametitle{mentors.debian.net} \frametitle{mentors.debian.net}
...@@ -123,10 +123,11 @@ ...@@ -123,10 +123,11 @@
\frametitle{Why mentors.debian.net?} \frametitle{Why mentors.debian.net?}
\begin{itemize} \begin{itemize}
\item[<1->] A central place for sponsored maintainers to upload and \item A central place for sponsored maintainers to \emph{upload} and
share their packages for review \emph{share} their packages for \emph{review}
\item[<2->] A companion to the debian-mentors mailing-list \pause
\item[<2->] A place for developers of Debian derivatives too \item A companion to the debian-mentors mailing-list
\item A place for developers of Debian derivatives too
(Ubuntu's ``Debian-first'' policy comes to mind) (Ubuntu's ``Debian-first'' policy comes to mind)
\end{itemize} \end{itemize}
...@@ -136,7 +137,10 @@ ...@@ -136,7 +137,10 @@
\begin{frame} \begin{frame}
\frametitle{A brief history of mentors.debian.net} \frametitle{A brief history of mentors.debian.net}
\begin{itemize}
\item Initiated by Christoph Haas and others long ago
\item Replaced by more recent software (debexpo) in 2011
\end{itemize}
\end{frame} \end{frame}
\begin{frame} \begin{frame}
...@@ -153,8 +157,8 @@ ...@@ -153,8 +157,8 @@
\item Goal: mentors.debian.net replacement \item Goal: mentors.debian.net replacement
\end{itemize} \end{itemize}
\item Asheesh and Arno Töll make debexpo replace the old \item Asheesh and Arno Töll make debexpo replace the old
mentors.d.n site (2011/07/something) mentors.d.n site (2011/08/11)
\item UI improvements (debexpo v2, 2012/02/something) \item UI improvements (debexpo v2, 2012/02/26)
\item GSoC 2012 (debexpo v3, 2012/11/25 ?) \item GSoC 2012 (debexpo v3, 2012/11/25 ?)
\end{itemize} \end{itemize}
...@@ -196,20 +200,20 @@ ...@@ -196,20 +200,20 @@
\begin{frame} \begin{frame}
\frametitle{Automatic package---sponsor matching} \frametitle{Automatic package---sponsor matching}
\begin{itemize}[<1->] \begin{itemize}
\item For a maintainer : finding a sponsor = lengthy process \item For a maintainer : finding a sponsor = lengthy process
\item For a sponsor : flow of packages to be sponsored = overwhelming \item For a sponsor : flow of packages to be sponsored = overwhelming
\end{itemize} \end{itemize}
\uncover[<2->]{ \pause
The goal of the project is two-fold
\begin{itemize} The goal of the project is two-fold
\begin{itemize}
\item giving sponsored maintainers a ``list'' of potential sponsors to prod \item giving sponsored maintainers a ``list'' of potential sponsors to prod
\item giving potential sponsors a list of packages to look out for \item giving potential sponsors a list of packages to look out for
\end{itemize} \end{itemize}
All this automatically All this automatically
}
\end{frame} \end{frame}
...@@ -241,6 +245,7 @@ ...@@ -241,6 +245,7 @@
\item Matching stub \item Matching stub
\end{itemize} \end{itemize}
\pause
TODO: TODO:
\begin{itemize} \begin{itemize}
\item proper matching \item proper matching
...@@ -252,54 +257,104 @@ ...@@ -252,54 +257,104 @@
\begin{frame} \begin{frame}
\frametitle{Improved package review interface} \frametitle{Improved package review interface}
The issue: Several ``competing'' platforms for package reviews
\begin{itemize}
\item mentors.debian.net ``comments''
\item debian-mentors mailing-list
\item sponsorship-requests bugs
\item team mailing-lists
\end{itemize}
\pause
The goal:
\begin{itemize}
\item getting all the information in one place: mentors.d.n
\item while still allowing the use of the other platforms
\item catering for our friends from derivative distributions
\end{itemize}
\end{frame} \end{frame}
\begin{frame} \begin{frame}
\frametitle{A tricky task} \frametitle{A tricky task}
\begin{itemize}
\item source browser : need to extend our package storage pool to
get the flat source
\item review interface : need to rework completely the (broken,
useless) comment engine
\item need to connect to the mailing-list and the BTS properly for
three-way integration
\end{itemize}
\end{frame} \end{frame}
\begin{frame} \begin{frame}
\frametitle{What's been done?} \frametitle{Outcomes}
\begin{itemize}
\item a git-based package storage backend
\item a source-code browser with in-line review capabilities
\item the basis for a ``karma'' system
\item a connector for mailing-lists, not yet deployed
\end{itemize}
\end{frame} \end{frame}
\section{The road ahead} \section{The road ahead}
\subsection{Further integration with the BTS-based workflow} \subsection{Further integration with the BTS-based workflow}
\begin{frame} \begin{frame}
\frametitle{The problem} \frametitle{The new sponsorship-requests workflow}
\end{frame} Tracking sponsorship-requests as bugs is an improvement over just
having the history in the debian-mentors archive. \\~\\
\begin{frame} \pause
\frametitle{Solutions}
\end{frame} But mentors.debian.net lacks integration with it. \\~\\
A nice interface: \url{http://mentors.pault.ag/} (and yes, the queue
is loooong). Having such a view in mentors.d.n would be (very) good.
\end{frame}
\subsection{Catering to packaging teams} \subsection{Catering to packaging teams}
\begin{frame} \begin{frame}
\frametitle{The problem} \frametitle{Package maintainance is shifting towards teams}
\end{frame} There are more and more packaging teams, each with their own
workflow (tracking packages via their SCM on alioth, via their
mailing-list, via a PET, ...) \\~\\
\pause
mentors.debian.net needs to take that into account and give teams
tools to help with their workflow. \\~\\
Goal: reducing the number of entry points for newcomers,
streamlining the sponsorship process.
\begin{frame}
\frametitle{Solutions}
\end{frame} \end{frame}
\subsection{mentors.debian.*org*?} \subsection{mentors.debian.*org*?}
\begin{frame} \begin{frame}
\frametitle{The problem} \frametitle{A critical piece of infrastructure, not official yet}
\end{frame} Half of Debian's packages are maintained by sponsored maintainers. A
lot of the newcomers come through mentors.debian.net, but that
service is run off of ``personal'' resources in an unofficial
fashion. \\~\\
\begin{frame} The (main) issue: people are allowed to upload random crap and mentors.d.n
\frametitle{Solution} distributes it (no NEW queue). \\~\\
\pause
Solution (thanks to zack and SPI lawyers): disclaim responsibility on
user-contributed content by having the users (GPG-)sign an agreement
before uploads are allowed.
\end{frame} \end{frame}
...@@ -308,15 +363,28 @@ ...@@ -308,15 +363,28 @@
\begin{frame} \begin{frame}
\frametitle{A small team with big ideas} \frametitle{A small team with big ideas}
Even with the GSoC, we are a small team of very busy people (Arno is
working on his Masters Thesis, I just changed jobs, ...), and there
are lots to do. \\~\\
As usual, help is welcome!
\end{frame} \end{frame}
\begin{frame} \begin{frame}
\frametitle{How to help} \frametitle{How to help?}
We don't really have/use a mailing-list, so your best bet is coming
to see us on IRC: $\sharp$debexpo on irc.debian.org. \\~\\
You can take a look at our wiki pages :
http://wiki.debian.org/Debexpo/Development
\end{frame} \end{frame}
\begin{frame} \begin{frame}
\LARGE{Thanks for listening!}
\end{frame} \end{frame}
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment