SVN hosting: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
mNo edit summary
 
(15 intermediate revisions by 3 users not shown)
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 ==
'''''October 2007: It has been decided to open the SVN at OSGeo'''''
* Link to the [http://www.nabble.com/Motion%3A-migrate-to-SVN-trac-on-OSGeo-infrastructure-tf4633839.html PSC mailing list thread] discussing this.
See also bug [[Tracking]].
== See also ==
* [[Migration from CVS to SVN]] (technical issues)
* <strike>[http://trac.edgewall.org/attachment/ticket/5241/mediawiki2trac.ph Convert] MediaWiki pages to Trac</strike>
: 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 ==
== SVN repository with GForge at Intevation ==
Line 8: Line 28:
'''Pro:'''
'''Pro:'''
* continuity for GRASS
* continuity for GRASS
* GForge includes different SCMs, like CVS, SVN, Mercurial, ...
** GForge-SVN-Browser ([http://wald.intevation.org/scm/?group_id=27 example])
** As GForge-Wiki "phpwiki" is potentially available.
** more?


'''Contra:'''
'''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 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
* [[Tracking#Buggy_bugtracker.3F|more GForge bugs]]
* [[Tracking#Buggy_bugtracker.3F|more GForge bugs]]


== SVN repository with Trac at OSGeo ==
== SVN repository with Trac at OSGeo ==


OSGeo SVN/Trac Server: http://trac.osgeo.org/
OSGeo SVN/Trac Server: http://trac.osgeo.org/ . There are several SVN/Trac instances running, e.g. the [http://trac.osgeo.org/gdal/ GDAL SVN/Trac Server].


GDAL SVN/Trac Server: http://trac.osgeo.org/gdal/
Main servers are at [http://www.peer1.net/en/colocation.asp Peer1 colocation site], adminstered by the OSGeo System Administration Committee ([http://wiki.osgeo.org/index.php/SAC OSGeo-SAC]).
 
Main servers are at Peer1 colocation site: http://www.peer1.net/en/colocation.asp,  
adminstered by the OSGeo System Administration Committee.




'''Pro:'''
'''Pro:'''
* Integrated infrastructure with other OSGeo projects (GDAL, ...)
* Integrated infrastructure with other OSGeo projects (GDAL, ...)
* SVN and Trac nicely integrated, also Wiki integrated
* SVN and Trac nicely integrated, also Wiki integrated ([http://trac.osgeo.org/gdal/wiki Wiki example])
* Trac shows patches/diffs in SVN ([http://trac.osgeo.org/gdal/attachment/ticket/1570/altitudeMode_SVN_HEAD.patch example])
* Trac shows patches/diffs in SVN ([http://trac.osgeo.org/gdal/attachment/ticket/1570/altitudeMode_SVN_HEAD.patch example1], [http://trac.osgeo.org/gdal/changeset/12164 example2])
* login (signon) embedded in OSGeo LDAP: single signon for OSGeo infrastructure
* login (signon) embedded in OSGeo LDAP: single signon for OSGeo infrastructure
* Trac advantages
* Trac advantages
** [http://trac.osgeo.org/gdal/timeline Timeline] and [http://trac.osgeo.org/gdal/roadmap roadmap] provided for semi-automated release management (milestones)
** [http://trac.osgeo.org/gdal/timeline Timeline] and [http://trac.osgeo.org/gdal/roadmap roadmap] provided for semi-automated release management (milestones)
** Auto-generation of release notes ([http://trac.osgeo.org/gdal/wiki/Release/1.4.1 GDAL example]) which we currently do by hand for thousands of fixes
** Auto-generation of release notes ([http://trac.osgeo.org/gdal/wiki/Release/1.4.1 GDAL example]) which we currently do by hand for thousands of fixes
** Source code browser integrated
** [http://trac.osgeo.org/gdal/browser Source code browser] integrated | Alternative [http://josef.fsv.cvut.cz/cgi-bin/viewcvs.cgi/?root=grass7svn viewcvs interface for SVN]
** Wiki integrated
** [http://trac.osgeo.org/gdal/wiki Wiki] integrated
** Ticket notification in IRC channel
** Ticket notification in IRC channel and via [http://trac.osgeo.org/gdal/timeline RSS]
** tickets can moved around among OSGeo projects
** tickets can moved around among OSGeo projects
** easy ticket monitoring and retrieval
** easy ticket monitoring and [http://trac.osgeo.org/gdal/report retrieval]
** nice layout
** nice layout
* potential new translation portal of OSGeo would integrate, too
* potential new translation portal of OSGeo would integrate, too (we suggest [http://pootle.wordforge.org/ pootle])
* integration with [http://wiki.osgeo.org/index.php/BuildBot_Configuration BuildBot] (automated multi-platform test builds)


'''Contra:'''
'''Contra:'''
* some time already invested in Intevation's GForge
* some time already invested in Intevation's GForge
=== See also ===
* [[Migration from CVS to SVN]] (technical issues)
* [http://trac.edgewall.org/wiki/TracFaq#can-i-convert-mediawiki-pages-to-trac convert] MediaWiki pages to Trac


[[Category: Development]]
[[Category: Development]]

Latest revision as of 12: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
Retrieved from "https://grasswiki.osgeo.org/w/index.php?title=SVN_hosting&oldid=25516"