Changes between Version 10 and Version 11 of BolsenaDraft2012
- Timestamp:
- 05/31/12 09:04:13 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TabularUnified BolsenaDraft2012
v10 v11 9 9 10 10 11 [[PageOutline(2-3,,inline)]] 12 13 14 15 == On going projects ? == 11 16 12 17 == Community == … … 17 22 * Many times, PSC members do not vote on proposals within the allotted time frame for that. How can we improve on that. 18 23 19 == GeoNetwork ==20 24 21 * On going projects ? 22 23 === Discussion on architecture updates === 25 == On going proposal == 26 * See [wiki:proposals] page 27 * [wiki:proposals/DCATandRDFServices Data Catalog Vocabulary and RDF services] 24 28 25 == Security == 29 == Discussion on architecture updates == 30 31 === Security === 26 32 * Status on http://trac.osgeo.org/geonetwork/wiki/proposals/ImprovedSecurityArchitecture 27 * CAS support (Jesse & Francois)33 * CAS support & LDAP improvements (Jesse & Francois) 28 34 29 == domain model==35 === domain model === 30 36 31 37 Considering GeoNetwork's functionality, you might expect there exist a class called Metadata, representing metadata. Sadly, this is not the case. The lack of a domain model makes doing changes to GeoNetwork very much more difficult and encourages source code pasta. Let's model our domain, and while at it, use [http://www.hibernate.org/ Hibernate] to have the domain classes hide the database. 32 38 33 == logging==39 === logging === 34 40 35 41 There is no point in maintaining a home-made logging facility when there are de facto standard libraries for this. Let's replace GN logging with [http://www.slf4j.org/ slf4j], and back it by the venerable [http://logging.apache.org/log4j/1.2/ log4j]. 36 42 37 == i18n==43 === i18n === 38 44 39 45 We have localisation in a very large number of xml files, in the database, and in yet different locations for Javascript. It would be most welcome to have 1 single place for all translations. At the very least, is there anything against merging all the xml files into a single file per language? … … 49 55 Discussion about advantages/disadvantages of repository migration to !GitHub. Tools like [http://subgit.com/index.html/ SubGit] seem can help for smooth migration, keeping in synch SVN-!GitHub repositories. 50 56 51 == = Wishlist ===57 == Wishlist == 52 58 53 == = R&D ===59 == R&D == 54 60 55 == = Presentations ===61 == Presentations == 56 62 57 63 confirmed:
