Changes between Version 25 and Version 26 of HowToContribute


Ignore:
Timestamp:
Aug 7, 2014, 7:53:47 PM (8 years ago)
Author:
annakrat
Comment:

fix links to RFC

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v25 v26  
    3030The typical process for new developers to gain full write access to the Main GRASS SVN repository is that for some mentorship period they send patches to the grass-dev mailing list (or the trac system) for existing old timer developers to review and commit. Full SVN access generally happens when the mentor has seen enough patches that they trust the person's code (committing it unchanged) and eventually get bored reviewing & rubber stamping all their patches. It is assumed during this period that a track record of trust will be established via participation on the grass-dev mailing list. At some point the mentor nominates the new developer on the PSC mailing list for full write access, and a vote happens.
    3131
    32  * In general, the [http://grass.osgeo.org/wiki/PSC GRASS Project Steering Committee] is responsible for granting SVN write access to contributors (as defined in [http://grass.osgeo.org/programming6/rfc1_psc.html RFC1]).
    33    * The new developer must '''read and abide by''' the document [http://grass.osgeo.org/programming6/rfc2_psc.html Legal aspects of code contributions] (RFC2).
     32 * In general, the [http://grass.osgeo.org/wiki/PSC GRASS Project Steering Committee] is responsible for granting SVN write access to contributors (as defined in [wiki:RFC/1_ProjectSteeringCommitteeGuidelines RFC1]).
     33   * The new developer must '''read and abide by''' the document [wiki:RFC/2_LegalAspectsOfCodeContributions Legal aspects of code contributions] (RFC2).
    3434   * An email must be sent to the [http://lists.osgeo.org/mailman/listinfo/grass-psc GRASS-PSC mailing list] by the new developer 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).
    3535
     
    4747 * [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:
    4848   * The requester needs to obtain an "osgeo_id" at http://www.osgeo.org/osgeo_userid - if s/he already have an "osgeo_id" but forgot it, it can be searched at http://www.osgeo.org/cgi-bin/ldap_web_search.py
    49    * The requester has to '''read and abide by''' the document [http://grass.osgeo.org/programming6/rfc2_psc.html Legal aspects of code contributions] (RFC2).
     49   * The requester has to '''read and abide by''' the document [wiki:RFC/2_LegalAspectsOfCodeContributions Legal aspects of code contributions] (RFC2).
    5050   * The request should be sent to a GRASS developer or the GRASS-PSC chair, stating that RFC2 was read and accepted (locate a mentor). The request then 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. For fast service you should provide your OSGeo ID in this email. (see below)
    5151   * After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below).