\documentclass{article}
\usepackage{ulem}
\pagestyle{headings}
\begin{document}
\tableofcontents

\part{ Split Git Repo into individual components.}
\section{ Bugs}
N/A

\section{ People}
All developers.

\section{ Description}
\subsection{ Steps for the split}
\renewcommand{\labelenumi}{\arabic{enumi}}
\begin{enumerate}
\item{\textbf{X} Make dev.horde.org read-only}
\item{\textbf{X} Notify mailing lists}
\item{\textbf{X} Split git repo with framework/bin/horde-git-split-all}
\item{\textbf{X} Set up email updates for new repo}
\item{\textbf{X} Add files to new repo}
\begin{itemize}
\item{.travis.ini, .travis.yml}
\begin{itemize}
\item{.gitignore}
\end{itemize}
\end{itemize}
\item{\textbf{X} Create FRAMEWORK\_5\_2 branch in libraries}
\item{\textbf{X} Update website}
\end{enumerate}
Later:

\renewcommand{\labelenumi}{\arabic{enumi}}
\begin{enumerate}
\item{Use more standard directory layout}
\begin{itemize}
\item{\textbf{X} phpunit.xml and other dev tool configurations in base directory.}
\begin{itemize}
\item{\textbf{X} README -> README.rst and COPYING -> LICENSE, and move to base directory.}
\item{PSR-4 layout}
\end{itemize}
\end{itemize}
\item{Fix API doc generation}
\item{Generate documentation for each repo}
\item{Add package-specific entries to bugs.horde.org}
\item{Go through all PRs and refer to new repos}
\item{Archive horde repo}
\end{enumerate}
\subsection{ Todos}
Global:

\renewcommand{\labelenumi}{\arabic{enumi}}
\begin{enumerate}
\item{\textbf{X} Prepare website with new instructions}
\item{\textbf{X} Create script to automatically build list of apps/libs (for use by install script)}
\begin{itemize}
\item{\textbf{X} Get all repos via https://api.github.com/orgs/horde/repos\footnote{https://api.github.com/orgs/horde/repos}}
\item{\textbf{X} Check for horde.yml files at https://raw.githubusercontent.com/horde/[REPO]/master/horde.yml\footnote{https://raw.githubusercontent.com/horde/[REPO]/master/horde.yml}}
\end{itemize}
\item{\textbf{O} Create single installation script}
\begin{itemize}
\item{\textbf{X} This script can create/clone the git repos as needed.}
\item{\textbf{X} All repos will be stored in a base folder}
\item{\textbf{X} Option to create a separate, web-accessible directory.}
\item{\textbf{O} Includes stuff in framework/bin (See Doc/Dev/Scripts\footnote{http://example.com/index.php?page=Doc/Dev/Scripts})}
\begin{itemize}
\item{\textbf{O} horde-generate-module -> move to skeleton/bin/skeleton-generate-module}
\item{\textbf{X} horde-rev-cmp (obsolete)}
\item{\textbf{O} horde-run-cmd}
\item{\textbf{X} install\_dev}
\item{\textbf{O} install\_framework (obsolete?)}
\item{\textbf{O} pear\_batch\_install}
\item{\textbf{O} test\_framework}
\end{itemize}
\item{\textbf{O} Includes stuff in horde-support/maintenance-tools (See Doc/Dev/Scripts\footnote{http://example.com/index.php?page=Doc/Dev/Scripts})}
\begin{itemize}
\item{\textbf{X} horde-build-snaps (obsolete)}
\item{\textbf{O} horde-build-website-docs.sh}
\item{\textbf{O} horde-ckeditor}
\item{\textbf{O} horde-installer-phar-create}
\item{\textbf{X} horde-js-compress (obsolete)}
\item{\textbf{X} horde-patch-config.sh (obsolete)}
\item{\textbf{O} horde-update-ISO3166-countries}
\end{itemize}
\item{\textbf{O} Includes the groupware install code (in fact, the Horde\_Core\_Bundle code is probably a good place to start in terms of creating the install script).}
\item{\textbf{O} Use Horde\_Pear libs to query for list of packages to install}
\item{\textbf{O} This script can be packaged via PHAR}
\begin{itemize}
\item{\textbf{O} Allow config file}
\end{itemize}
\end{itemize}
\item{\textbf{O} Create autoloader driver for use with script-facilitated development install}
\item{\textbf{O} Create Vagrant image to allow for testing/development}
\end{enumerate}
\section{ Open Questions (Votes)}
\begin{itemize}
\item{Prefix split repositories with "horde-"?}
\begin{itemize}
\item{Jan: no}
\begin{itemize}
\item{Mike: no}
\end{itemize}
\end{itemize}
\item{What to do with the "horde" base repository. Delete current "horde" repository and replace it with the current "horde" application, or find a new repository name for the current "horde" application and keep or empty the current "horde" repository.}
\begin{itemize}
\item{Jan: leaning to the former}
\begin{itemize}
\item{Mike: leaning to the later (Wouldn't deleting the contents of the current repository mess anyone who has it checked out?)}
\begin{itemize}
\item{Outcome: use "base" as a name.}
\end{itemize}
\end{itemize}
\end{itemize}
\end{itemize}

\noindent\rule{\textwidth}{1pt}
Back to the Project List\footnote{http://example.com/index.php?page=Project}

\end{document}
