Difference between revisions of "Mapbender Report 2009"

From OSGeo
Jump to navigation Jump to search
 
(4 intermediate revisions by 2 users not shown)
Line 12: Line 12:
 
* a lot of great code sprints, like weekends with 10-15 devs!
 
* a lot of great code sprints, like weekends with 10-15 devs!
 
* regular IRC meetings, we meet Mondays and I believe we never missed a date last year! About 5 attendees average
 
* regular IRC meetings, we meet Mondays and I believe we never missed a date last year! About 5 attendees average
 +
* Adoption of Mapbender has broadened. Focus is on large infrastructures and distributed SDI management. Some Examples:
 +
** http://www.prtr.bund.de
 +
** http://www.geoportal.rlp.de
 +
** State of Baden-Württemberg decided to use Mapbender and GeoNetwork (Launch in October 2010)
 +
** Berlin-Brandenburg SDI decided to use Mapbender as geoportal software
 +
** Several city administrations started using Mapbender, for more details see http://www.mapbender.org/Gallery
  
 
=== Areas for Improvement ===
 
=== Areas for Improvement ===
Line 17: Line 23:
 
* unit testing didn't take off as we hoped it would.  
 
* unit testing didn't take off as we hoped it would.  
 
* documentation is not as complete as we wanted it to be.  
 
* documentation is not as complete as we wanted it to be.  
−
* we could use a financial boost to address technical debt.
 
 
* the installation and update process has been improved, but is still not as easy as we wanted it to be.
 
* the installation and update process has been improved, but is still not as easy as we wanted it to be.
−
* more consistent workflow of administration interfaces
+
* more consistent work flow of administration interfaces
 
* 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.
 
* 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.
 +
* Redesign splash screen and portal front end
 +
* Modularize authentication code, potentially use GeoPrisma "Checkers".
 +
* Implement deployment of JavaScript code for inclusion into other web sites (Widgets/Apps/Mashups)
  
 
=== Opportunities to Help ===
 
=== Opportunities to Help ===
Line 28: Line 36:
 
* people with UI design experience and advanced CSS knowledge
 
* people with UI design experience and advanced CSS knowledge
 
* as long as we do not have enough unit tests, we need volunteers to do manual testing
 
* as long as we do not have enough unit tests, we need volunteers to do manual testing
 +
* we could use a financial boost to address technical debt.
  
 
=== Outlook for 2010 ===
 
=== Outlook for 2010 ===
−
* Rely more on other software, reduce Mapbender core
+
* Rely more on other (OSGeo) software, reduce Mapbender core
 
** 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
 
** 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
 
** maybe use server side code from GeoPrisma or MapFish
 
** maybe use server side code from GeoPrisma or MapFish
 
** create interface to Geonetwork
 
** create interface to Geonetwork
 
** integration of an SVG lib like RaphaelJS
 
** integration of an SVG lib like RaphaelJS
 +
* Implement permanent portal as OSGeo service metadata library/repository/bucket back end 
 
* Reduce technical debt
 
* Reduce technical debt
 
** rock solid documentation and stable API
 
** rock solid documentation and stable API
 
** unit testing  
 
** unit testing  
 +
* Enthusiasm in representing Mapbender at some international fairs
  
 
__notoc__
 
__notoc__
 
[[Category: Reports 2009]]
 
[[Category: Reports 2009]]

Latest revision as of 10:00, 29 January 2010

Mapbender

  • Contact name: Christoph Baudson

Key Accomplishments

  • More transparent decision making on road map. Road maps are now created regularly for each quarter, with at most three items, devs 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
  • creation of a core JavaScript API
  • created a foundation for technical documentation
  • two successful GSoC projects, one student is now a regular committer, a GSoC student from 2008 returned
  • a lot of great code sprints, like weekends with 10-15 devs!
  • regular IRC meetings, we meet Mondays and I believe we never missed a date last year! About 5 attendees average
  • Adoption of Mapbender has broadened. Focus is on large infrastructures and distributed SDI management. Some Examples:

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.
  • unit testing didn't take off as we hoped it would.
  • documentation is not as complete as we wanted it to be.
  • the installation and update process has been improved, but is still not as easy as we wanted it to be.
  • more consistent work flow of administration interfaces
  • 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.
  • Redesign splash screen and portal front end
  • Modularize authentication code, potentially use GeoPrisma "Checkers".
  • Implement deployment of JavaScript code for inclusion into other web sites (Widgets/Apps/Mashups)

Opportunities to Help

  • volunteers to maintain documentation, user manuals, tutorials.
  • more community feedback, we are curious about what OSGeo folks think about Mapbender
  • we could need some input on client side (JS) unit testing.
  • people with UI design experience and advanced CSS knowledge
  • as long as we do not have enough unit tests, we need volunteers to do manual testing
  • we could use a financial boost to address technical debt.

Outlook for 2010

  • Rely more on other (OSGeo) software, reduce Mapbender core
    • 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
    • maybe use server side code from GeoPrisma or MapFish
    • create interface to Geonetwork
    • integration of an SVG lib like RaphaelJS
  • Implement permanent portal as OSGeo service metadata library/repository/bucket back end
  • Reduce technical debt
    • rock solid documentation and stable API
    • unit testing
  • Enthusiasm in representing Mapbender at some international fairs
Retrieved from "http://wiki.osgeo.org/w/index.php?title=Mapbender_Report_2009&oldid=44760"