| 12 | |
| 13 | Removal of SVN commit access should be handled by the same process. |
| 14 | |
| 15 | The new committer should have demonstrated commitment to GeoNetwork and knowledge of the GeoNetwork source code and processes to the committee's satisfaction, usually by reporting bugs, submitting patches, and/or actively participating in the GeoNetwork mailing list(s). |
| 16 | |
| 17 | The new committer should also be prepared to support any new feature or changes that he/she commits to the GeoNetwork 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. |
| 18 | |
| 19 | All committers should also be a member of the geonetwork-devel mailing list so they can stay informed on policies, technical developments and release preparation. |
| 20 | |
| 21 | New commiters are responsible for having read, and understood this document. |