Changes between Version 53 and Version 54 of Bolsena2010


Ignore:
Timestamp:
May 18, 2010, 9:32:20 AM (14 years ago)
Author:
mcoudert
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Bolsena2010

    v53 v54  
    2626 || 4 || || Javadoc|| Automatically add the Javadoc pages to this wiki, updated from a Hudson build process? For all of the branches? ||  ||
    2727 || 5 || || Coding rules || Some people really like working with ''patches''; other people prefer using short-lived SVN branches for a similar purpose. Can we all agree on doing it one way or the other? ||  ||
    28  || 6 || || ||  ||  ||
    29  || 7 || || ||  ||  ||
     28 || 6 || ||Community || This wiki is a bit of a mess, in my opinion. I think it would be good if we could put maybe 3 people in charge to firstly, clean it up and better structure it; and secondly, to try to keep it that way. ||  ||
     29 || 7 || DONE? || Database || Let's create SQL files that can fill an empty GeoNetwork database with only the minimum needed to run the program? The admin user, settings, regions, things like that. Not everyone is really eager to use GAST for anything. || Done by Jose? ||
     30 || 8 || || Release Strategy|| Can we release GeoNetwork 3.0 (with the CSW/ebRIM interface)? Maybe we can have simultaneous "current releases" in both the GN2.x and GN3.x lineages, as do for example Lucene and Tomcat? ||  ||
     31 || 9 || || Database  || Does anyone like the function of the installer that it overwrites your JDBC credentials with randomly generated values? I certainly don't, as my DB lives very much longer than the many GeoNetwork installations I always do, so I have to edit {{{config.xml}}} everytime. How's about removing that? ||  ||
     32 || 10 || ||Community || Would it be an idea to appoint Language Managers for each of the supported translations? They would form the International Internationalization Committee (IIC, or CII in French) and they're summoned to maintain the i18n files for their language, before each new release. This might even be arranged in an [http://www.osgeo.org/ OSGEO]-wide manner. ||  ||
     33 || 11 || ||Code Refactoring || The class {{{DataManager.java}}} and its sister {{{XMLSerializer.java}}} are in particularly bad shape, in my opinion. There are literally dozens of public methods that all do more or less the same thing. Of course it's not clearly documented why they are all there or when to use which. Would it be too drastic to propose that we keep 1 single public method for each of the functions ''createMetadata'', ''updateMetadata'', ''validateMetadata'', etc. ? ||  ||
     34 || 12 || || RIA, Framework || Any relevant software going on that might be useful for GeoNetwork? Think of [http://mapproxy.org/ MapProxy], [http://chiba.sourceforge.net Chiba] and [http://geojquery.org/wiki/doku.php GeoJQuery]. Other ones? ||  ||
     35 || 13 || || || || ||
    3036
    3137 * While at it can we change the code so that you can save settings from the GUI even if not all expected settings are present in your database?
    3238
    3339
    34  * This wiki is a bit of a mess, in my opinion. I think it would be good if we could put maybe 3 people in charge to firstly, clean it up and better structure it; and secondly, to try to keep it that way.
    35 
    36  * Let's create SQL files that can fill an empty GeoNetwork database with only the minimum needed to run the program? The admin user, settings, regions, things like that. Not everyone is really eager to use GAST for anything.
    37 
    38  * Can we release GeoNetwork 3.0 (with the CSW/ebRIM interface)? Maybe we can have simultaneous "current releases" in both the GN2.x and GN3.x lineages, as do for example Lucene and Tomcat?
    39 
    40  * Does anyone like the function of the installer that it overwrites your JDBC credentials with randomly generated values? I certainly don't, as my DB lives very much longer than the many GeoNetwork installations I always do, so I have to edit {{{config.xml}}} everytime. How's about removing that?
    41 
    42  * Would it be an idea to appoint Language Managers for each of the supported translations? They would form the International Internationalization Committee (IIC, or CII in French) and they're summoned to maintain the i18n files for their language, before each new release. This might even be arranged in an [http://www.osgeo.org/ OSGEO]-wide manner.
    43 
    44  * The class {{{DataManager.java}}} and its sister {{{XMLSerializer.java}}} are in particularly bad shape, in my opinion. There are literally dozens of public methods that all do more or less the same thing. Of course it's not clearly documented why they are all there or when to use which. Would it be too drastic to propose that we keep 1 single public method for each of the functions ''createMetadata'', ''updateMetadata'', ''validateMetadata'', etc. ?
    45 
    46  * Any relevant software going on that might be useful for GeoNetwork? Think of [http://mapproxy.org/ MapProxy], [http://chiba.sourceforge.net Chiba] and [http://geojquery.org/wiki/doku.php GeoJQuery]. Other ones?
     40 *
    4741
    4842 * In the [http://nationaalgeoregister.nl NGR] project, a modification to the code around the editor called ''Inflation and Vacuum'' is implemented, that makes it much easier to create valid metadata from scratch. In essence it takes the function of {{{update-fixed-info.xsl}}} (which also tries to do some automatic adjustments to help things along) a whole seven miles further. What do the developers think of this? (I'll provide documentation sometime soon).