Difference between revisions of "SVN hosting"

From GRASS-Wiki
Jump to: navigation, search
(SVN repository with GForge at Intevation)
(GForge-SVN-Browser URL)
Line 9: Line 9:
 
* continuity for GRASS
 
* continuity for GRASS
 
* GForge includes different SCMs, like CVS, SVN, Mercurial, ...
 
* GForge includes different SCMs, like CVS, SVN, Mercurial, ...
 +
** GForge-SVN-Browser ([http://wald.intevation.org/scm/?group_id=27 example])
 +
** more?
  
 
'''Contra:'''
 
'''Contra:'''

Revision as of 00:20, 29 September 2007

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
  • GForge includes different SCMs, like CVS, SVN, Mercurial, ...
    • GForge-SVN-Browser (example)
    • more?

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
  • 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
  • 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