Changes between Version 36 and Version 37 of HowToContribute

Timestamp:

Jan 27, 2016, 6:51:17 AM (8 years ago)

Author:

neteler

Comment:

clarified

HowToContribute

@@ -39 +39 @@
 ==== Write access to the GRASS-Addons-SVN repository ====
 
+''Rationale:''
+
 Write access to the [http://svn.osgeo.org/grass/grass-addons/ Addons SVN repository] is much less rigorous than to the core source code repository. It is in effect an '''incubation area''', both for new code and new developers. Write access does not require the full vote of the GRASS-PSC, just the support of one mentor and adherence to our [wiki:RFC/2_LegalAspectsOfCodeContributions RFC2 document], which guarantees that the code is license-compatible with the rest of GRASS. As opposed to write access to the Main SVN repository, write access to the Addons repository is typically initiated by the new contributor. Overall:
 
@@ -47 +49 @@
    * Caretaking: In years to come others may easily contribute bug fixes and upgrades if a flaw is found or the GRASS API changes.
    * Infrastructure: Ability to take advantage of the svn history and trac system integration, including bug tracker. (these are really quite good things)
- * [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:
+ * [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:''
    * 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
    * The requester has to '''read and abide by''' the document [wiki:RFC/2_LegalAspectsOfCodeContributions Legal aspects of code contributions] (RFC2).
-   * 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)
+   * The request needs to be sent to the GRASS-PSC mailing list, stating that RFC2 was read and accepted (ideally also suggest a mentor among the developers). As only subscribers are allowed to post to OSGeo mailing lists, this requires [http://lists.osgeo.org/mailman/listinfo/grass-psc subscription] to the mailing list for that time. For fast service you should provide your OSGeo ID in this email (see below).
    * After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below).
    * 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.