<div dir="ltr"><h1 style="letter-spacing:-0.018em;font-size:19px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">RFC-5: PostGIS Committer Guidelines<a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines#RFC-5:PostGISCommitterGuidelines" title="Link to this section" style="color:rgb(215,215,215);text-decoration:none;border:none;font-size:0.8em;vertical-align:text-top" target="_blank"></a></h1>
<table style="border-spacing:0px;border-collapse:collapse;font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;border:2px solid rgb(204,204,204)">
<tbody><tr><td style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13px;border:1px solid rgb(204,204,204);padding:0.1em 0.25em">Version:</td><td style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13px;border:1px solid rgb(204,204,204);padding:0.1em 0.25em">
1.00000013</td></tr><tr><td style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13px;border:1px solid rgb(204,204,204);padding:0.1em 0.25em">Author:</td><td style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13px;border:1px solid rgb(204,204,204);padding:0.1em 0.25em">
Regina Obe <lr at pcorp dot us></td></tr><tr><td style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13px;border:1px solid rgb(204,204,204);padding:0.1em 0.25em">Last Edited:</td>
<td style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13px;border:1px solid rgb(204,204,204);padding:0.1em 0.25em">2012/05/04</td></tr><tr><td style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13px;border:1px solid rgb(204,204,204);padding:0.1em 0.25em">
Status:</td><td style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13px;border:1px solid rgb(204,204,204);padding:0.1em 0.25em">Approved</td></tr></tbody></table><h2 style="letter-spacing:-0.018em;font-size:16px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">
Changes to this file<a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines#Changestothisfile" title="Link to this section" style="color:rgb(215,215,215);text-decoration:none;border:none;font-size:0.8em;vertical-align:text-top" target="_blank"></a></h2>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">This RFC should be only changed by PostGIS PSC members. All PSC members must agree to the terms of the changes before the change is considered final except in the case of wording changes and formatting that do not alter the terms of the guidelines.</p>
<h2 style="letter-spacing:-0.018em;font-size:16px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">Purpose<a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines#Purpose" title="Link to this section" style="color:rgb(215,215,215);text-decoration:none;border:none;font-size:0.8em;vertical-align:text-top" target="_blank"></a></h2>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">To formalize source tree access, and specify some guidelines for source committers and patch submitters.</p>
<h2 style="letter-spacing:-0.018em;font-size:16px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">Election to Commit Access<a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines#ElectiontoCommitAccess" title="Link to this section" style="color:rgb(215,215,215);text-decoration:none;border:none;font-size:0.8em;vertical-align:text-top" target="_blank"></a></h2>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">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.</p>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">Removal of commit access should be handled by the same process.</p><p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">
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).</p>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">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.</p>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">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.</p>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">New committers are responsible for having read, and understood this document.</p><h2 style="letter-spacing:-0.018em;font-size:16px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">
Code and Documentation Conventions<a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines#CodeandDocumentationConventions" title="Link to this section" style="color:rgb(215,215,215);text-decoration:none;border:none;font-size:0.8em;vertical-align:text-top" target="_blank"></a></h2>
<ul><li><font color="#000000" style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13.333333015441895px">C code should follow our designated </font><a href="http://trac.osgeo.org/postgis/browser/trunk/STYLE" style="color:rgb(187,0,0);font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13.333333015441895px;text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank">Style Guidelines</a><font color="#000000" style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13.333333015441895px"> to the best of your abilities. -> </font><font style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13.333333015441895px" color="#0000ff">BE</font><font color="#000000" style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13.333333015441895px"> </font><span style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;color:rgb(0,0,255);font-size:13.333333015441895px">We can add </span><span style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;color:rgb(0,0,255);font-size:13.333333969116211px"><a href="http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html" target="_blank">http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html</a> for Java</span></li>
<li style="font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13.333333015441895px"><span>All source code in SVN should be in Unix text format as opposed to DOS text mode. </span><font color="#0000ff">(Ok I use nix based hosts @home @office)</font></li>
<li style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">Each new/changed function should be documented in the official docs following our <a href="https://trac.osgeo.org/postgis/wiki/DevWikiDocNewFeature" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank">Documentation Guidelines</a> <font color="#0000ff">OK</font></li>
</ul><h2 style="letter-spacing:-0.018em;font-size:16px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">SVN Administrator<a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines#SVNAdministrator" title="Link to this section" style="color:rgb(215,215,215);text-decoration:none;border:none;font-size:0.8em;vertical-align:text-top" target="_blank"></a></h2>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">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.</p>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">Initially Paul Ramsey will be the SVN Administrator.</p><h2 style="letter-spacing:-0.018em;font-size:16px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">
SVN Commit and Bug, Feature Tracking Practices<a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines#SVNCommitandBugFeatureTrackingPractices" title="Link to this section" style="color:rgb(215,215,215);text-decoration:none;border:none;font-size:0.8em;vertical-align:text-top" target="_blank"></a></h2>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">The following are considered good source commit and tracking practices for the PostGIS project.</p>
<ol style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif"><li>Use meaningful descriptions for commit log entries. <font color="#0000ff">OK</font></li><li>Add a bug reference like "<a href="https://trac.osgeo.org/postgis/ticket/1232" title="defect: Exception when calling isValid on multilinestring with only 1 point (closed: fixed)" style="color:rgb(187,0,0);text-decoration:line-through;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank">#1232</a>" at the beginning or end of SVN commit log entries when committing changes related to a ticket in Trac. The '#' character enables Trac to create a hyperlink from the changeset to the mentioned ticket. <font color="#0000ff">OK I hope there is an svn server script which is preventing me in case of human errors Ie it can check if Trac Issue is open and #1232 number format is correct.</font></li>
<li>When new enhancements are added or breaking changes are made and completed the related ticket should have in <strong>keywords</strong> section of ticket the word <strong>history</strong>. This will better ensure it is not forgotten when preparing the news release and official doc release notes.<span style="color:rgb(0,0,255)">OK</span></li>
<li>After committing changes related to a ticket in Trac, write the tree and revision in which it was fixed in the ticket description. Such as "Fixed in trunk <a title="No changeset 12345 in the repository" style="color:rgb(153,153,136)">r12345</a> and in branches/1.7 <a title="No changeset 12346 in the repository" style="color:rgb(153,153,136)">r12346</a>". The 'r' character enables Trac to create a hyperlink from the ticket to the changeset.<font color="#0000ff">OK but I dont understand how the changeset is collected from the revision number. Isnt the revision number a specifier of the atomic commit in SVN? SO specifiying the revision number as a comment in Trac may help us create hyperlink from only that latest commit changeset and not all the other previous commit changesets related to that issue? </font></li>
<li>Changes should not be committed in stable branches without a corresponding bug id. Any change worth pushing into the stable version is worth a bug entry. <font color="#0000ff">OK I think this was mentioned in 2</font></li>
<li>Never commit new features to a stable branch without permission of the PSC or release manager. Normally only fixes should go into stable branches. <font color="#0000ff">OK make sense</font></li>
<li>New features go in the main development trunk. <font color="#0000ff">OK</font></li><li>Only bug fixes should be committed to the code during pre-release code freeze, without permission from the PSC or release manager. <span style="color:rgb(0,0,255)">OK</span></li>
<li>Significant changes to the main development version should be discussed on the postgis-dev list before you make them, and larger changes will require an RFC approved by the PSC.<span style="color:rgb(0,0,255)">OK</span></li>
<li>Do not create new branches (except for spike branches) without the approval of the PSC. Release managers are assumed to have permission to create a branch. <font color="#0000ff">OK</font></li><li>spike branch (those in the spike/username area are to be used for experimentation or for major code refactoring that will destabilize the trunk. After such experimentation is deemed stable, this can then be merged into the trunk after approval from PSC members. <span style="color:rgb(0,0,255)">OK</span></li>
<li>When committing new features or significant changes to existing source code, the committer should take reasonable measures to insure that the source code continues to build and work on the most commonly supported platforms (currently Linux and Windows), either by testing on those platforms directly, running Buildbot tests, or by getting help from other developers working on those platforms. If new files or library dependencies are added, then the <a href="http://configure.in" target="_blank">configure.in</a>, Makefile.in and related documentations should be kept up to date. <font color="#0000ff">NA</font></li>
<li>In the event of broken build (build bot fail notification), the person who broke the build must fix the break before working on anything else <font color="#0000ff">OK</font></li></ol><h2 style="letter-spacing:-0.018em;font-size:16px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">
Committer Tracking<a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines#CommitterTracking" title="Link to this section" style="color:rgb(215,215,215);text-decoration:none;border:none;font-size:0.8em;vertical-align:text-top" target="_blank"></a></h2>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">A list of all project committers will be kept in the main postgis directory in a file called (CREDITS) listing for each SVN committer. This will be the responsibility of the PSC to ensure:</p>
<ul style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif"><li>Userid: the id that will appear in the SVN logs for this person.</li><li>Full name: the users actual name.</li>
<li>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.</li><li>A brief indication of areas of responsibility.</li><li>The name of key developers and their area of responsibility should also be prominently shown in latest release of manual in the doc/introduction.xml file. This will be the responsibility of the documentation lead to ensure.</li>
</ul><h2 style="letter-spacing:-0.018em;font-size:16px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">Relationship with other Projects<a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines#RelationshipwithotherProjects" title="Link to this section" style="color:rgb(215,215,215);text-decoration:none;border:none;font-size:0.8em;vertical-align:text-top" target="_blank"></a></h2>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">Some parts of the PostGIS code base are dependent on other upsteam projects or other projects rely heavily on functionality in PostGIS. Changes in those areas should go first into those upstream projects and then applied to PostGIS. In event of major changes to PostGIS, said projects should be regression tested (before a PostGIS release) to ensure the latest version still works with the latest RTM version of PostGIS.</p>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">Currently the list of those areas is :</p><ul style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">
<li>postgresql ( <a href="http://www.postgresql.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://www.postgresql.org</a>)</li>
<li>geos ( <a href="http://geos.osgeo.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://geos.osgeo.org</a>)</li>
<li>proj ( <a href="http://proj.osgeo.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://proj.osgeo.org</a>)</li>
<li>gdal ( <a href="http://gdal.osgeo.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://gdal.osgeo.org</a>)</li>
</ul><p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">GIS FOSS suites that need testing before PostGIS major release:</p><ul style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">
<li>mapserver (<a href="http://mapserver.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://mapserver.org</a>)</li>
<li>geoserver (<a href="http://geoserver.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://geoserver.org</a>)</li>
<li>openjump (<a href="http://openjump.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://openjump.org</a>)</li>
<li>qgis (<a href="http://qgis.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://qgis.org</a>)</li>
<li>gvSig (<a href="http://www.gvsig.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://www.gvsig.org</a>)</li>
<li>pgRouting (<a href="http://www.pgrouting.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://www.pgrouting.org/</a>)</li>
<li>osm2pgsql + other openstreetmap components (mapnik etc) (<a href="http://www.openstreetmap.org/" style="color:rgb(187,0,0);text-decoration:none;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(187,187,187)" target="_blank"><span style="background-image:url(https://trac.osgeo.org/postgis/chrome/common/extlink.gif);padding-left:12px;background-repeat:no-repeat no-repeat"> </span>http://www.openstreetmap.org/</a>)</li>
</ul><p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif"></p><h2 style="letter-spacing:-0.018em;font-size:16px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">
Legal<a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines#Legal" title="Link to this section" style="color:rgb(215,215,215);text-decoration:none;border:none;font-size:0.8em;vertical-align:text-top" target="_blank"></a></h2>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">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.</p>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">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).</p>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">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.</p>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">The code should be developed by the contributor, or the code should be from a source which can be rightfully contributed such as from the public domain, or from an open source project under a compatible license.</p>
<p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">All unusual situations need to be discussed and/or documented.</p><p style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">
Committers should adhere to the following guidelines, and may be personally legally liable for improperly contributing code to the source repository:</p><ul style="font-size:13.333333015441895px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif">
<li>Make sure the contributor (and possibly employer) is aware of the contribution terms.</li><li>Code coming from a source other than the contributor (such as adapted from another project) should be clearly marked as to the original source, copyright holders, license terms and so forth. This information can be in the file headers, but should also be added to the project licensing file if not exactly matching normal project licensing.</li>
<li>Existing copyright headers and license text should never be stripped from a file. If a copyright holder wishes to give up copyright they must do so in writing to the foundation before copyright messages are removed. If license terms are changed it has to be by agreement (written in email is ok) of the copyright holders.</li>
<li>Code with licenses requiring credit, or disclosure to users should be added to /postgis/trunk/LICENSE.TXT.</li><li>When substantial contributions are added to a file (such as substantial patches) the author/contributor should be added to the list of copyright holders for the file.</li>
<li>If there is uncertainty about whether a change is proper to contribute to the code base, please seek more information from the project steering committee, or the foundation legal counsel.</li><li>New contributors and company contributors should be added to the credits in doc/introduction.xml of the latest release of the PostGIS manual.</li>
<li>It is the responsibility of the document lead to insure when new enhancements are added or breaking changes are made, these are noted in the trunk/NEWS or relevant branch/NEWS as soon as conveniently possible. The note should include the trac # (unless a major feature with many tickets) and contributors to the feature/change.</li>
<li><font color="#0000ff">OK</font></li>
</ul></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 26 February 2014 13:50, Baris Ergun <span dir="ltr"><<a href="mailto:barisergun75@gmail.com" target="_blank">barisergun75@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><h1 style="letter-spacing:-0.018em;font-size:19px;font-family:Arial,Verdana,'Bitstream Vera Sans',Helvetica,sans-serif">
I<span style="font-weight:normal">will reply soon generraly it looks like I will comply all the rules. Just will read the doc carefully and also add some suggestions for Java Code Style reference etc.</span></h1>
</div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On 25 February 2014 23:04, Paul Ramsey <span dir="ltr"><<a href="mailto:pramsey@cleverelephant.ca" target="_blank">pramsey@cleverelephant.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
Aye, Baris, do you agree to conform to the committer guidelines (in particular note items 5,6,7 on stable branches and appropriate changes)</div><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
<br></div><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines" target="_blank">https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines</a></div>
<div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
And as an added note, to stick to committing in the Java area.</div><div><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
P.</div><div style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div> <div><div><br></div><span style="font-family:helvetica,arial;font-size:13px"></span>-- <br>Paul Ramsey<br>
<a href="http://cleverelephant.ca" target="_blank">http://cleverelephant.ca</a><div><a href="http://postgis.net" target="_blank">http://postgis.net</a></div></div> <br></div><div><div><p style="color:#a0a0a8">On February 25, 2014 at 1:02:16 PM, Sandro Santilli (<a href="mailto://strk@keybit.net" target="_blank">strk@keybit.net</a>) wrote:</p>
</div></div><blockquote type="cite"><span><div><div><div><div>On Tue, Feb 25, 2014 at 12:25:29PM -0800, Paul Ramsey wrote:<br>> Hi Devs,<br>> We have the potential for active maintenance of the Java chunk of the distribution, and I would like to give Baris Ergun commit privs to the java sub-tree. He’s already provided a couple of patches that look fine, and most importantly is thinking about the implications of his changes in the large before applying.<br>
> Please give me a vote on that (the alternative is continuing Java branch bitrot)<br><br>+1 for a java side maintainer<br><br>Please don't forget to test his resilience of burocratic pressure:<br><a href="https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines" target="_blank">https://trac.osgeo.org/postgis/wiki/DevWikiComitGuidelines</a><br>
<br>--strk;<br></div></div><div>_______________________________________________<br>postgis-devel mailing list<br><a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel</a></div></div></div></span></blockquote></div></blockquote></div><br>
<br clear="all">
<div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div dir="ltr">Barış<div><a href="http://www.linkedin.com/in/barisergun" target="_blank">www.linkedin.com/in/barisergun</a><br></div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Barış<div><a href="http://www.linkedin.com/in/barisergun" target="_blank">www.linkedin.com/in/barisergun</a><br></div></div>
</div>