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

Horde\_RefactorBugsPeopleDescriptionResources

\part{Horde\_Refactor}
A Library and Tool Set for refactoring code

\section{Bugs}
List any tickets on http://bugs.horde.org/\footnote{http://bugs.horde.org/} that cover this issue or are relevant to it.

\section{People}
\section{Description}
Horde\_Refactor is a commandline tool to enforce quality in code and documentation\newline
Refactoring is governed by Rules which implement detection and change of content violating the rule.

Currently, two formal rules are implemented:\newline
- php4 constructor handling: Ensure a php5 constructor exists if a php4 constructor is found and, if needed, swap positions to ensure compat.\newline
- FileLevelDocBlock\footnote{http://example.com/index.php?page=FileLevelDocBlock}: Ensure that a file level doc block with at least certain information is present in all class files.

Some Horde\_Refactor Rules may or may not need a configuration file.\newline
Configuration Options for a Horde\\Refactor\\Rule\\Base descendent Foo are defined in a Horde\\Refactor\\Config\\Base descendent class of the same name (if any).

This file can sport default values. To override these, provide a config file

TODO: Example

\section{Resources}
Include links to protocol descriptions, specifications, RFCs, external applications, presentations on http://horde.org/papers/\footnote{http://horde.org/papers/} or elsewhere that are relevant, articles, API docs from http://dev.horde.org/\footnote{http://dev.horde.org/} - anything that might be useful to someone working on this.


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

\end{document}
