Difference between revisions of "SVN hosting"

From GRASS-Wiki
Jump to: navigation, search
m
 
Line 1: Line 1:
 +
'''Historical document, please keep it.'''
 +
 
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.
 
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.
 
  
 
== News ==
 
== News ==

Latest revision as of 04:51, 7 February 2019

Historical document, please keep it.

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.

News

October 2007: It has been decided to open the SVN at OSGeo

See also bug Tracking.

See also

MediaWiki is available at OSGeo, so this shouldn't be needed. (and I prefer MediaWiki ;-) --HB)
Note: there is now also the Mediawiki converter plugin installed at osgeo.org (but I tend to agree with HB) -- MN
What does that plugin do? TracWiki->Mediawiki?
yes -- MN
If so Mw->Tw->Mw would be lossy & better to copy Mw->Mw? (??) --HB
Sure, if we keep MW, we'll simply dump it and import -- MN

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)
    • As GForge-Wiki "phpwiki" is potentially available.
    • 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
  • 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