Changes between Version 40 and Version 41 of HowToContribute


Ignore:
Timestamp:
May 19, 2019, 7:09:37 AM (3 years ago)
Author:
martinl
Comment:

svn->git

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v40 v41  
    2828To enhance code quality and security, a procedure has been established to control and grant GRASS-SVN write access. In general, write access must be requested and is not automatically assigned. Any code submission must be compliant with the GRASS submission rules.
    2929
    30 ==== Write access to the Main GRASS-SVN repository ====
     30==== Write access to the GRASS core repository ====
    3131
    32 The typical process for new developers to gain full write access to the Main GRASS SVN repository is that for some mentorship period they send patches to the grass-dev mailing list (or the trac system) for existing old timer developers to review and commit. Full SVN access generally happens when the mentor has seen enough patches that they trust the person's code (committing it unchanged) and eventually get bored reviewing & rubber stamping all their patches. It is assumed during this period that a track record of trust will be established via participation on the grass-dev mailing list. At some point the mentor nominates the new developer on the PSC mailing list for full write access, and a vote happens.
     32The typical process for new developers to gain full write access to the [https://github.com/OSGeo/grass core GRASS repository] is that for some mentorship period they send patches to the grass-dev mailing list (or the trac system) for existing old timer developers to review and commit. Full Git access generally happens when the mentor has seen enough pull requests that they trust the person's code (committing it unchanged) and eventually get bored reviewing & rubber stamping all their pull requests. It is assumed during this period that a track record of trust will be established via participation on the grass-dev mailing list. At some point the mentor nominates the new developer on the PSC mailing list for full write access, and a vote happens.
    3333
    34  * In general, the [http://grass.osgeo.org/wiki/PSC GRASS Project Steering Committee] is responsible for granting SVN write access to contributors (as defined in [wiki:RFC/1_ProjectSteeringCommitteeGuidelines RFC1]).
     34 * In general, the [http://grass.osgeo.org/wiki/PSC GRASS Project Steering Committee] is responsible for granting Git write access to contributors (as defined in [wiki:RFC/1_ProjectSteeringCommitteeGuidelines RFC1]).
    3535   * The new developer must '''read and abide by''' the document [wiki:RFC/2_LegalAspectsOfCodeContributions Legal aspects of code contributions] (RFC2).
    36    * An email must be sent to the [http://lists.osgeo.org/mailman/listinfo/grass-psc GRASS-PSC mailing list] by the new developer stating that RFC2 was read and accepted. This requires [http://lists.osgeo.org/mailman/listinfo/grass-psc subscription] to the PSC mailing list. After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below).
     36   * An email must be sent to the [http://lists.osgeo.org/mailman/listinfo/grass-psc GRASS-PSC mailing list] by the new developer stating that RFC2 was read and accepted. This requires [http://lists.osgeo.org/mailman/listinfo/grass-psc subscription] to the PSC mailing list. After a period of evaluation, Git write access may be granted and is set up in the !GitHub authentication system (see below).
    3737
    3838