Changes between Version 44 and Version 45 of HowToContribute


Ignore:
Timestamp:
Apr 12, 2020, 2:45:41 PM (4 years ago)
Author:
neteler
Comment:

SVN -> git

Legend:

Unmodified
Added
Removed
Modified

  • HowToContribute

    v44 v45  
    1818The Trac ticket system is the best way to submit your code contributions if you don't have write access to SVN, and (even for those with write access) the preferred way to submit more radical changes for general review. See for example trac ticket #33.
    1919 * Submit your code and documentation patches [http://trac.osgeo.org/grass/newticket here].
    20  * [http://grass.osgeo.org/wiki/Patches How to create a patch] - they should be generated versus the latest development SVN (trunk).
     20 * [http://grass.osgeo.org/wiki/Patches How to create a patch] - they should be generated versus the latest development ("master" in !GitHub).
    2121
    2222'''Code quality:''' Check your code according to GRASS GIS [wiki:Submitting Submitting rules and guide list].
    … …  
    5858   * 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
    60 === Setting up the new SVN write access after acceptance ===
     60=== Setting up your write access after acceptance ===
    6161
    62 Once SVN access is granted, the requester's "osgeo_id" will be enabled.
    63 The GRASS-PSC chair (currently Markus Neteler) and other developers will add this "osgeo_id" to the list of enabled accounts in the OSGeo LDAP authentication system ([https://www.osgeo.org/cgi-bin/auth/ldap_group.py?group=grass here] for GRASS-SVN and [https://www.osgeo.org/cgi-bin/auth/ldap_group.py?group=grass_addons here] for GRASS-Addons-SVN; requires authentication).
     62Once the git repo access is granted, the requester's !GitHub ID will be enabled by either the GRASS-PSC chair (currently Markus Neteler) and other core developers.
     63Then clone the source code from !GitHub.
    6464
    6565'''Important:''' Contributions have to follow the [wiki:Submitting] code rules.
    … …  
    6969 * If you contribute own code: See [wiki:Submitting Submitting - GRASS GIS Addons]
    7070 * If you want to modify existing code: [wiki:DownloadSource Get the source code] and Happy hacking :)
    71  * If you want to suggest changes or a source code patch, please submit the change as "diff" and not the full modified file. See [wiki:HowToSVN#LocalDiffs HowToSVN Creating local diffs]
    72  * Consider to subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-commit grass-commit] mailing list which distributes GRASS-SVN commit differences for real-time code review.
     71 * If you want to suggest changes or a source code patch, please submit the change as "diff" and not the full modified file. See [wiki:HowToSVN#LocalDiffs HowToGit Creating local diffs]
     72 * Consider to subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-commit grass-commit] mailing list which distributes GRASS-git commit differences for real-time code review.
     73
    7374=== Coding standards and code style ===
    7475
    75 Check your code against the rules defined in the document [wiki:Submitting]. This ensures a smooth integration into the standard GRASS code base and avoids portability problems.
     76Check your code against the rules defined in the document [wiki:Submitting]. This ensures a smooth integration into the standard GRASS GIS code base and avoids portability problems.
    7677
    7778=== And after submission of an Addon? ===