Changes between Version 2 and Version 3 of TinyOWSModGeocacheIntegration
- Timestamp:
- Aug 5, 2011, 7:20:04 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TinyOWSModGeocacheIntegration
v2 v3 1 = TinyOWS and mod_geocache integration in the MapServer project =1 = TinyOWS and Mod-Geocache integration in the MapServer project = 2 2 3 This page discusses the administrative details of the integration of the TinyOWS and mod _geocache projects into the MapServer project, if RFC 70 and 71 are accepted.3 This page discusses the administrative details of the integration of the TinyOWS and mod-Geocache projects into the MapServer project, if RFC 70 and 71 are accepted. 4 4 5 5 == Governance == … … 7 7 * It is planned that the MapServer PSC would become the ultimate authority for the merged projects 8 8 * Olivier Courtin to be added to the MapServer PSC as owner of the TinyOWS module 9 * Thomas Bonfort is already on the PSC and will act as owner of the mod _geocache module9 * Thomas Bonfort is already on the PSC and will act as owner of the mod-Geocache module 10 10 * It is understood that even though the ultimate decision authority is the PSC and the merged projects will have to follow the PSC rules (RFCs, etc.), the recommendations of a module owner are most of the time followed and the PSC does not get in the way of a module owner trying to make enhancements to the software, unless other devs envisions possible issues, in which case the group works together to define a better solution. (in other words, Oliver and Thomas will remain the technical leads of their respective modules and the PSC will do its best to support them in their work) 11 11 … … 27 27 == Release planning / scheduling == 28 28 29 * Tricky: we want to allow TinyOWS and mod_geocache to have an independent and faster release cycle than MapServer core which is more mature. But users would also benefit from a combined/unified release of the full suite every once in a while... so we need to be able to allow a mix of both.29 * Tricky: we want to allow TinyOWS and Mod-Geocache to have an independent and faster release cycle than MapServer core which is more mature. But one of the drivers for this merge is that users would also benefit from a combined/unified release of the full suite every once in a while... so we need to be able to allow a mix of both. 30 30 31 31 * Release numbering? 32 * MapServer 6.x, TinyOWS 1.x, mod_geocache 0.4 ... confusing if we want to appear as a unified project... and then which version number do we give to the complete suite when we release as a whole?33 * Adopt a common release numbering scheme? e.g. Ubuntu-style based on year.month? Would allow intermediate releases by component, while having consistent release numbers between all components ... e.g. MapServer suite with all components initially released as 11.08 (august 2011), next major release of MapServer core planned for early 2012, but in the meantime sub-projects can be released as 11.10, 11.11, etc... and next full suite release (including MapServer core) could be around February as v12.2? 32 * MapServer 6.x, TinyOWS 1.x, Mod-Geocache 0.4 ... confusing if we want to appear as a unified project... and then which version number do we give to the complete suite when we release as a whole? 33 * Adopt a common release numbering scheme? e.g. Ubuntu-style based on year.month? Would allow intermediate releases by component, while having consistent release numbers between all components ... e.g. MapServer suite with all components initially released as 11.08 (august 2011), next major release of MapServer core planned for early 2012, but in the meantime sub-projects can be released as 11.10, 11.11, etc... and next full suite release (including MapServer core) could be around February as v12.2? This also allows for bugfix releases as 11.8.1, 11.8.2, etc. 34 34 * Other options? 35 35 … … 42 42 43 43 == Mailing lists == 44 45 * Okay to use the existing mapserver lists? 46 * RFC 70 says: tinyows-dev and tinyows-users should be stopped and news discussions should occurs to relevant mapserver ones. 47 * RFC 71 has nothing explicit but mentions the switch to mapserver-dev (which would imply mapserver-users as well) 44 48 45 49 == SVN == … … 86 90 == Website and documentation == 87 91 92 * How do we organize docs and the website in the context of combined projects? 93 * How do we deal with releases (and docs updates) that are not synchronized? 94 95 * RFC 70 says: tinyows.org domain could be redirected to the coming MapServer TinyOWS documentation pages. 96 * RFC 71 says: The mod-geocache documentation is rather sparse, and consists essentially of a commented configuration file. There will have to be an effort to add documentation to the main mapserver doc site, and to migrate the few wiki pages from the google-code hosting.
