Changes between Version 4 and Version 5 of DevWikiComitGuidelines


Ignore:
Timestamp:
Feb 23, 2011, 11:20:13 PM (10 years ago)
Author:
robe
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevWikiComitGuidelines

    v4 v5  
    77
    88== Purpose ==
    9 To formalize SVN commit access, and specify some guidelines for SVN committers and patch submitters.
     9To formalize source commit source tree access, and specify some guidelines for source committers and patch submitters.
     10
     11== Election to Commit Access ==
     12Permission for commit source tree access shall be provided to new developers only if accepted by the PostGIS Project Steering Committee. A proposal should be written to the PSC for new committers and voted on normally. It is not necessary to write an RFC document for these votes, a proposal to postgis-dev is sufficient.
     13
     14Removal of commit access should be handled by the same process.
     15
     16The new committer should have demonstrated commitment to PostGIS and knowledge of the PostGIS source code and processes to the committee's satisfaction, usually by reporting bugs, submitting patches, and/or actively participating in the PostGIS mailing list(s).
     17
     18The new committer should also be prepared to support any new feature or changes that he/she commits to the PostGIS source tree in future releases, or to find someone to which to delegate responsibility for them if he/she stops being available to support the portions of code that he/she is responsible for.
     19
     20All committers should also be a member of the postgis-dev mailing list so they can stay informed on policies, technical developments and release preparation.
     21
     22New commiters are responsible for having read, and understood this document.