\begin{article}
\title{Mapbender}
\maketitle

\begin{itemize}
\item  Contact name: \textbf{Christoph Baudson}
\item Website: \url{http://mapbender.org}
\end{itemize}

\section{Key Accomplishments}
More transparent decision making on road map. Road maps are now created regularly for each quarter, with at most three items, developers vote up-front for items on mailing list and discuss via IRC.

Interweaving Mapbender client side with jQuery. This results in more stability, less and concise code, better performance and user experience (for example slippy WMS map).

Relying on jQuery UI for creating widgets like datatables or or dialogs. Results in less code, easier development of new functionality, better user experience, better customization with jQuery UI CSS framework theme roller.
\begin{itemize}
\item  Creation of a core JavaScript API.
\item  Created a foundation for technical documentation.
\item  Two successful GSoC projects, one student is now a regular committer, a GSoC student from 2008 returned.
\item  A lot of great code sprints, like weekends with 10-15 devs!
\item  Regular IRC meetings, we meet Mondays and I believe we never missed a date last year! About 5 attendees average.
\item  Adoption of Mapbender has broadened. Focus is on large infrastructures and distributed SDI management. Some Examples: 
\begin{itemize}
\item  \url{http://www.prtr.bund.de}
\item  \url{http://www.geoportal.rlp.de}
\item  State of Baden-Württemberg decided to use Mapbender and GeoNetwork (Launch in October 2010)
\item  Berlin-Brandenburg SDI decided to use Mapbender as geoportal software
\item  Several city administrations started using Mapbender, for more details see \url{http://www.mapbender.org/Gallery}
\end{itemize}
\end{itemize}

\section{Areas for Improvement}
We didn't succeed in showing Mapbender's qualities to OSGeo or a wider audience in general.  We need to be more confident in marketing, especially outside of Germany. Maybe FOSS4G in Barcelona will be an opportunity.
\begin{itemize}
\item  Unit testing didn't take off as we hoped it would. 
\item  Documentation is not as complete as we wanted it to be. 
\item  The installation and update process has been improved, but is still not as easy as we wanted it to be.
\item  More consistent work flow of administration interfaces.
\item  Due to large refactoring last year backwards compatibility suffered a little and updates were tricky. Be patient with us, we learned a lot and this year will be much smoother.
\item  Redesign splash screen and portal front end.
\item  Modularize authentication code, potentially use GeoPrisma "Checkers". 
\item  Implement deployment of JavaScript code for inclusion into other web sites (Widgets/\nohyphens{Apps}/Mashups).
\end{itemize}

\section{Outlook for 2010}
\begin{itemize}
\item  Rely more on other (OSGeo) software, reduce Mapbender core:
\begin{itemize}
\item  We want to get closer to OpenLayers, we looked at Mapstraction and maybe this will be a good way to align our API to the OpenLayers API.
\item  Maybe use server side code from GeoPrisma or MapFish.
\item  Create interface to GeoNetwork.
\item  Integration of an SVG lib like RaphaelJS.
\end{itemize}
\item  Implement permanent portal as OSGeo service metadata library/repository/bucket backend.
\item  Reduce technical debt.
\begin{itemize}
\item  Rock solid documentation and stable API.
\item  Unit testing .
\end{itemize}
\item  Enthusiasm in representing Mapbender at some international fairs.
\end{itemize}

\section{Opportunities to Help}
\begin{itemize}
\item  Volunteers to maintain documentation, user manuals and tutorials.
\item  More community feedback, we are curious about what OSGeo folks think about Mapbender.
\item  We could need some input on client side (JS) unit testing.
\item  People with UI design experience and advanced CSS knowledge.
\item  As long as we do not have enough unit tests, we need volunteers to do manual testing.
\item  We could use a financial boost to address technical debt.
\end{itemize}

\end{article}