Changes between Version 16 and Version 17 of HowToContribute


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

more svn addons

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v16 v17  
    2929 * Write access to the '''GRASS-Addons-SVN repository:'''
    3030   * 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)
     31      * 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.
     32      * 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.
     33      * 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.
     34      * Caretaking: In years to come others may easily contribute bug fixes and upgrades if a flaw is found or the GRASS API changes.
     35      * Infrastructure: Ability to take advantage of the svn history and trac system integration, including bug tracker. (these are really quite good things)
     36
    3537   * [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:
    3638      * 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).