SVN hosting
The goal is to move to SVN infrastructure for GRASS 7. The hosting of SVN needs to be discussed. A new repository has to be created in any case, despite its physical location.
SVN repository with GForge at Intevation
GRASS GForge Server: http://wald.intevation.org/tracker/?group_id=21
Pro:
- continuity for GRASS
Contra:
- GForge is not really accepted by GRASS developers, low usage (much lower than with old RT). Important developers are not even registered at all
- GForge is not integrated with CVS, apparently also not with SVN
- Wiki is yet on another server
- more GForge bugs
SVN repository with Trac at OSGeo
OSGeo SVN/Trac Server: http://trac.osgeo.org/ . There are several SVN/Trac instances running, e.g. the GDAL SVN/Trac Server.
Main servers are at Peer1 colocation site, adminstered by the OSGeo System Administration Committee (OSGeo-SAC).
Pro:
- Integrated infrastructure with other OSGeo projects (GDAL, ...)
- SVN and Trac nicely integrated, also Wiki integrated (Wiki example)
- Trac shows patches/diffs in SVN (example1, example2)
- login (signon) embedded in OSGeo LDAP: single signon for OSGeo infrastructure
- Trac advantages
- Timeline and roadmap provided for semi-automated release management (milestones)
- Auto-generation of release notes (GDAL example) which we currently do by hand for thousands of fixes
- Source code browser integrated | Alternative viewcvs interface for SVN
- Wiki integrated
- Ticket notification in IRC channel and via RSS
- tickets can moved around among OSGeo projects
- easy ticket monitoring and retrieval
- nice layout
- potential new translation portal of OSGeo would integrate, too (we suggest pootle)
- integration with BuildBot (automated multi-platform test builds)
Contra:
- some time already invested in Intevation's GForge
See also
- Migration from CVS to SVN (technical issues)
- convert MediaWiki pages to Trac