Changes between Version 15 and Version 16 of HowToContribute


Ignore:
Timestamp:
May 30, 2008, 4:33:32 AM (14 years ago)
Author:
hamish
Comment:

svn addons

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v15 v16  
    2424   * In general, the [http://grass.gdf-hannover.de/wiki/PSC GRASS Project Steering Committee] is responsible for granting SVN write access to contributors (as defined in [http://download.osgeo.org/grass/grass6_progman/rfc/rfc1_psc.html RFC1]).
    2525      * The requester has to '''read and abide by''' the document [http://download.osgeo.org/grass/grass6_progman/rfc/rfc2_psc.html Legal aspects of code contributions] (RFC2).
    26       * The request has to be send to the GRASS-PSC [http://lists.osgeo.org/mailman/listinfo/grass-psc mailing list], stating that RFC2 was read and accepted. This requires [http://lists.osgeo.org/mailman/listinfo/grass-psc subscription] to the PSC mailing list. After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below).
     26      * The request has to be sent to the GRASS-PSC [http://lists.osgeo.org/mailman/listinfo/grass-psc mailing list], stating that RFC2 was read and accepted. This requires [http://lists.osgeo.org/mailman/listinfo/grass-psc subscription] to the PSC mailing list. After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below).
     27
     28
    2729 * Write access to the '''GRASS-Addons-SVN repository:'''
     30   * We invite and encourage users who write GRASS add-on code to host it in our grass-addons SVN. We do so because:
     31      * After some years private websites often go away and the code is lost
     32      * From the start all code there is licensed under the GPL (or compatible), so all can use the content there without worry, and mature modules may be moved into the main GRASS code as needed.
     33      * The code will be widely backed up and if the main source code ever moves, all the addons will move with it in parallel
     34      * Ability to take advantage of the svn history and trac system integration (this is really quite a good thing)
    2835   * [http://trac.osgeo.org/grass/browser/grass/trunk/AUTHORS GRASS developers] with write access can grant SVN write access to contributors (you may contact an active developer, see grass-dev mailing list archive). The selected developer is a sort of "sponsor/mentor" for the requester. Procedure:
    2936      * The requester has to '''read and abide by''' the document [http://download.osgeo.org/grass/grass6_progman/rfc/rfc2_psc.html Legal aspects of code contributions] (RFC2).
    30       * The request has to be send to a GRASS developer or the GRASS-PSC chair, stating that RFC2 was read and accepted. After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below).
    31       * New commands stored in the GRASS-Addons-SVN repository should be also added as link to the [http://grass.osgeo.org/wiki/GRASS_AddOns Wiki list of tools].
     37      * The request has to be send to a GRASS developer or the GRASS-PSC chair, stating that RFC2 was read and accepted (locate a mentor). The request has to be sent to the GRASS-PSC [http://lists.osgeo.org/mailman/listinfo/grass-psc mailing list], stating that RFC2 was read and accepted. As only subscribers are allowed to post to OSGeo mailing lists, this requires [http://lists.osgeo.org/mailman/listinfo/grass-psc subscription] to the PSC mailing list for that time.
     38      * After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below).
     39      * New commands stored in the GRASS-Addons-SVN repository should be also added as link to the [http://grass.osgeo.org/wiki/GRASS_AddOns Wiki list of tools] and placed in the appropriate directory hierarchy.
    3240
    3341=== Setting up the new SVN write access ===