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

\part{ Horde 4 Configuration}
Several proposals for ways that configurations will change in Horde 4.

\section{ Replace .dist files with .local.php files.}
In order to reduce the amount of up-front configuration needed, I propose that we either:

\renewcommand{\labelenumi}{\arabic{enumi}}
\begin{enumerate}
\item{Have standard defaults for all configurations, and have configuration files be optional for specifying local changes.}
\item{Have the standard config files (currently the *.dist files) as the .php versions, and have .local.php files which are included if present for local modifications.}
\end{enumerate}
\section{ Config objects.}
Configuration data needs to be encapsulated instead of being thrown around in the global scope. Having a general Horde\_Config class, with the defaults in that class, would allow for easy implementation of option \#1 above.

\section{ Config vs. preferences}
In many cases config options should be controllable as policies, either on a per-user or some other larger but not site-wide basis. This should also integrate with vhosting support (i.e., a config policy per vhost). See Project/HordePolicy\footnote{http://example.com/index.php?page=Project/HordePolicy} and perhaps Project/HordeSpaces\footnote{http://example.com/index.php?page=Project/HordeSpaces} as well.

\section{ Configuration GUI}
All options, whether this is MIME helpers, preferences, configuration settings, etc., should be settable from the configuration GUI.

\end{document}
