Bolsena 2011 - draft agenda

1. Community
   1. Committee
   2. Community tools
   3. Community mini codesprint
2. Documentation
3. GeoNetwork
   1. Discussion on architecture updates
   2. New features & fixes
   3. R&D

For the 4th time, the ​Bolsena OSGeo Hacking Event is going to be held. This page lists some ideas that can be discussed within the GeoNetwork faction.

Please add any idea you have here !

Community

Committee

• Update AB ?
• Propose PSC update ?
• See & update:
  • ​http://trac.osgeo.org/geonetwork/wiki/PSC
  • List of motions in the proposal page

Community tools

• Community tools (sourceforge.net, ML, ...) should be accessible/manageable by at least 2 persons from the community (check that)

Community mini codesprint

• 2011 was the first time we've had a mini-codesprint, which is an event taking place some months before the traditional Bolsena meeting. In spite of the rather sparse attendance by GeoNetwork developers, some ​great results were achieved, such as good improvements to the Lucene analysis, impressive performance gains in search results display, and general refactoring of dusty code, amongst other things. Thanks to François Prunayre for conceiving and hosting this event. Let's do it every year, and if you weren't there in 2011, make sure you're there in 2012.

Documentation

• Update ​GeoNetwork logo ? There is some discussion that GeoNetwork does not really have a logo; a strong, graphical image that could act as a powerful symbol for GeoNetwork. The current graphics as on the default banner can hardly be considered a 'logo'; no need at all to have the project's name in the logo.
• Name change : isn't it better to call GeoNetwork "GeoNetwork", rather than "GeoNetwork open source" ? The "open source" suffix adds nothing meaningful and is rather non-standard for a name, as it's not capitalized. If size does matter, it's not in projects' names !
• Publish French documentation on the website

GeoNetwork

• On going projects ?

Discussion on architecture updates

Components

• GAAP
• Search
  • Search module: SOLR
  • CSW Search module ?
• GeoNetwork legacy = admin & editor ?
• What's metro ?
  • What type of communication between components ? ​JMS
  • ESB, Routine engine (​Camel)

Agreement on new or existing dependencies

• Security layer require :
  • Axis (or Metro, ​CXF ?) ​comparison
  • JAXB or JIBX (see section on XML binding ​here)
  • Spring security
• Javascript : heikki thinks that jQuery is in many ways superior to Ext.js, particularly in its programming model and the plethora of readily-available plugins for jQuery. Yet we need Ext because of GeoExt. Can we not isolate use of Ext to the mapviewer for as long as there is no jQuery equivalent to GeoExt, and use jQuery everywhere else ?

New features & fixes

• Security layer & GAAP
• JS Widgets :
  • file upload : where we have file upload functions, it would be nice if we provide a drag & drop function instead of the old, old, filechooser -- something like Gmail has it. Of course with perfect degrading for users of certain browsers. A very good one is ​jQuery File Upload
• ...

R&D

• Ontologies & thesaurus
  • Custom Lucene Analyzer
  • Thesaurus browser widget: like ​ArborJS ?
• CSW 3.0