Changes between Version 24 and Version 25 of HowToContribute


Ignore:
Timestamp:
Oct 28, 2011, 8:33:20 AM (11 years ago)
Author:
neteler
Comment:

explain "osgeo_id"

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v24 v25  
    4040
    4141 * We invite and encourage users who write GRASS add-on code to host it in our grass-addons SVN. We do so because:
    42    * 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 contributer to full developer requires a minimum of training.
     42   * 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.
    4343   * 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.
    4444   * 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.
     
    4646   * Infrastructure: Ability to take advantage of the svn history and trac system integration, including bug tracker. (these are really quite good things)
    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:
     48   * 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
    4849   * The requester has to '''read and abide by''' the document [http://grass.osgeo.org/programming6/rfc2_psc.html Legal aspects of code contributions] (RFC2).
    4950   * 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)