Changes between Version 20 and Version 21 of DevWikiComitGuidelines
- Timestamp:
- Feb 24, 2011, 12:39:19 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevWikiComitGuidelines
v20 v21 20 20 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. 21 21 22 New commit ers are responsible for having read, and understood this document.22 New committers are responsible for having read, and understood this document. 23 23 24 24 == Committer Tracking == … … 33 33 == SVN Administrator == 34 34 35 One member of the Project Steering Committee will be designated the SVN Administrator. That person will be responsible for giving SVN commit access to folks, updating the C OMMITERSfile, and other SVN related management. That person will need login access on the SVN server of course.35 One member of the Project Steering Committee will be designated the SVN Administrator. That person will be responsible for giving SVN commit access to folks, updating the CREDITS and authors.svn file, and other SVN related management. That person will need login access on the SVN server of course. 36 36 37 37 Initially Paul Ramsey will be the SVN Administrator. … … 77 77 == Legal == 78 78 79 Commit ers are the front line gatekeepers to keep the code base clear of improperly contributed code. It is important to the PostGIS users, developers and the OSGeo foundation to avoid contributing any code to the project without it being clearly licensed under the project license.79 Committers are the front line gatekeepers to keep the code base clear of improperly contributed code. It is important to the PostGIS users, developers and the OSGeo foundation to avoid contributing any code to the project without it being clearly licensed under the project license. 80 80 81 Generally speaking the key issues are that those providing code to be included in the repository understand that the code will be released under the original GPL license, and that the person providing the code has the right to contribute the code. For the commit er themselves understanding about the license is hopefully clear. For other contributors, the commiter should verify the understanding unless the commiter is very comfortable that the contributor understands the license (for instance frequent contributors).81 Generally speaking the key issues are that those providing code to be included in the repository understand that the code will be released under the original GPL license, and that the person providing the code has the right to contribute the code. For the committer themselves understanding about the license is hopefully clear. For other contributors, the committer should verify the understanding unless the committer is very comfortable that the contributor understands the license (for instance frequent contributors). 82 82 83 83 If the contribution was developed on behalf of an employer (on work time, as part of a work project, etc) then it is important that an appropriate representative of the employer understand that the code will be contributed under the GPL license. The arrangement should be cleared with an authorized supervisor/manager, etc. … … 87 87 All unusual situations need to be discussed and/or documented. 88 88 89 Commit ers should adhere to the following guidelines, and may be personally legally liable for improperly contributing code to the source repository:89 Committers should adhere to the following guidelines, and may be personally legally liable for improperly contributing code to the source repository: 90 90 91 91 * Make sure the contributor (and possibly employer) is aware of the contribution terms. … … 98 98 == Bootstraping == 99 99 100 The following existing commit ers will be considered authorized PostGIS committers as long as they each review the commiter guidelines, and agree to adhere to them. The SVN administrator will be responsible for checking with each person.100 The following existing committers will be considered authorized PostGIS committers as long as they each review the committer guidelines, and agree to adhere to them. The SVN administrator will be responsible for checking with each person. 101 101 102 102 * Paul Ramsey
