Changes between Version 42 and Version 43 of HowToContribute


Ignore:
Timestamp:
May 25, 2019, 6:05:29 AM (5 years ago)
Author:
martinl
Comment:

svn->git

Legend:

Unmodified
Added
Removed
Modified

  • HowToContribute

    v42 v43  
    3737
    3838
    39 ==== Write access to the GRASS-Addons-SVN repository ====
     39==== Write access to the GRASS Addons repository ====
    4040
    4141''Rationale:''
    4242
    43 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:
     43Write access to the [https://github.com/OSGeo/grass-addons Addons 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 repository, write access to the Addons repository is typically initiated by the new contributor. Overall:
    4444
    45  * We invite and encourage users who write GRASS add-on code to host it in our grass-addons SVN. We do so because:
     45 * We invite and encourage users who write GRASS add-on code to host it in our grass-addons repository. We do so because:
    4646   * Community building: It gets people involved and educated - contributing to the main GRASS code uses the exact same website, software, and commands. Thus the trip from contributor to full developer requires a minimum of training.
    4747   * Archival: After some years it is common that people move on, then private websites fade away and the code is lost. The code will be widely backed up and if the main source code ever moves, all the addons will move with it in parallel.
    4848   * Guaranteed license: 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 promoted into the main GRASS code as needed.
    4949   * Caretaking: In years to come others may easily contribute bug fixes and upgrades if a flaw is found or the GRASS API changes.
    50    * Infrastructure: Ability to take advantage of the svn history and trac system integration, including bug tracker. (these are really quite good things)
    51  * [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.
     50   * Infrastructure: Ability to take advantage of the git history including bug tracker. (these are really quite good things)
     51 * [https://github.com/OSGeo/grass/blob/master/AUTHORS GRASS developers] with write access can grant repository 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.
    5252
    5353''Procedure:''
    54    * 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
     54   * The requester needs to obtain !GitHub account at https://github.com/join
    5555   * The requester has to '''read and abide by''' the document [wiki:RFC/2_LegalAspectsOfCodeContributions Legal aspects of code contributions] (RFC2).
    56    * 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).
    57    * After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below).
    58    * New commands stored in the GRASS-Addons-SVN repository should be also added as link to the [https://grasswiki.osgeo.org/wiki/AddOns Wiki list of tools] and placed in the appropriate directory hierarchy.
     56   * 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 !GitHub username in this email (see below).
     57   * After a period of evaluation, Git write access may be granted and is set up in the !GitHub authentication system (see below).
     58   * New commands stored in the GRASS Addons repository should be also added as link to the [https://grasswiki.osgeo.org/wiki/AddOns Wiki list of tools] and placed in the appropriate directory hierarchy.
    5959
    6060=== Setting up the new SVN write access after acceptance ===