Changes between Version 8 and Version 9 of rfc3_commiters
- Timestamp:
- Mar 22, 2018, 2:25:36 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
rfc3_commiters
v8 v9 1 = RFC 3: GDAL Commit er Guildlines =1 = RFC 3: GDAL Committer Guildlines = 2 2 3 3 Author: Frank Warmerdam[[BR]] … … 34 34 can stay informed on policies, technical developments and release preparation. 35 35 36 New commit ers are responsible for having read, and understood this document.36 New committers are responsible for having read, and understood this document. 37 37 38 38 == Committer Tracking == 39 39 40 A list of all project committers will be kept in the main gdal directory (called COMMIT ERS) listing for each SVN committer:40 A list of all project committers will be kept in the main gdal directory (called COMMITTERS) listing for each SVN committer: 41 41 42 42 * Userid: the id that will appear in the SVN logs for this person. … … 49 49 One member of the Project Steering Committee will be designed the SVN 50 50 Administrator. That person will be responsible for giving SVN commit access 51 to folks, updating the COMMIT ERS file, and other SVN related management. That51 to folks, updating the COMMITTERS file, and other SVN related management. That 52 52 person will need login access on the SVN server of course. 53 53 … … 94 94 == Legal == 95 95 96 Commit ers are the front line gatekeepers to keep the code base clear of96 Committers are the front line gatekeepers to keep the code base clear of 97 97 improperly contributed code. It is important to the GDAL/OGR users, 98 98 developers and the OSGeo foundation to avoid contributing any code to … … 102 102 included in the repository understand that the code will be released under 103 103 the MIT/X license, and that the person providing the code has the right 104 to contribute the code. For the commit er themselves understanding about105 the license is hopefully clear. For other contributors, the commit er106 should verify the understanding unless the commit er is very comfortable that104 to contribute the code. For the committer themselves understanding about 105 the license is hopefully clear. For other contributors, the committer 106 should verify the understanding unless the committer is very comfortable that 107 107 the contributor understands the license (for instance frequent contributors). 108 108 … … 119 119 All unusual situations need to be discussed and/or documented. 120 120 121 Commit ers should adhere to the following guidelines, and may be personally121 Committers should adhere to the following guidelines, and may be personally 122 122 legally liable for improperly contributing code to the source repository: 123 123 … … 131 131 == Bootstraping == 132 132 133 The following existing commit ers will be considered authorized GDAL/OGR134 committers as long as they each review the commit er guidelines, and133 The following existing committers will be considered authorized GDAL/OGR 134 committers as long as they each review the committer guidelines, and 135 135 agree to adhere to them. The SVN administrator will be responsible for 136 136 checking with each person.
