|Version 6 (modified by robe, 2 years ago)|
RFC ? : PostGIS Committer Guidelines
Author: Regina Obe
To formalize source commit source tree access, and specify some guidelines for source committers and patch submitters.
Election to Commit Access
Permission 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.
Removal of commit access should be handled by the same process.
The 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).
The 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.
All committers should also be a member of the postgis-dev mailing list so they can stay informed on policies, technical developments and release preparation.
New commiters are responsible for having read, and understood this document.
A list of all project committers will be kept in the main postgis directory in a file called (authors.svn) listing for each SVN committer:
- Userid: the id that will appear in the SVN logs for this person.
- Full name: the users actual name.
- Email address: A current email address at which the committer can be reached. It may be altered in normal ways to make it harder to auto-harvest.
- A brief indication of areas of responsibility. (brief description of responsibility is kept in Credits)