<div>
Yes - the concern of code contribution agreement (or explicitly not having one) was raised. That was straight forward and being worked on.</div><div>-- </div><div><div>Jody Garnett</div></div>
<p style="color: #A0A0A8;">On Tuesday, 9 October 2012 at 8:59 AM, Frank Warmerdam wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>Jody,<div><br></div><div>I think I raised the concern, and I was looking for something like the "Legal" section of the GDAL commiter guidelines stressing the responsibilities of commiters to ensure the code they commit is appropriately contributed:</div>
<div><br> <a href="http://trac.osgeo.org/gdal/wiki/rfc3_commiters">http://trac.osgeo.org/gdal/wiki/rfc3_commiters</a></div><div><br></div><div>On GDAL (and some similar projects) we expect new commiters to publically acknowledge that they have read the guidelines and will endevour to adhere to them on the project mailing list so there is a lightweight record. </div>
<div><br></div><div>The goal is to ensure that commiters understand their responsibilities, and to demonstrate that the project had made reasonable efforts to keep the code base clean. </div><div><br></div><div>Best regards,</div>
<div>Frank</div><div><br></div><div><br></div><div><div>On Mon, Oct 8, 2012 at 3:41 PM, Jody Garnett <span dir="ltr"><<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a>></span> wrote:<br><blockquote type="cite"><div>
<div>
Morning Cameron:</div><div><br></div><div>Over on the GeoMoose PSC list we have been going over your following feedback:</div><div><blockquote type="cite"><div>I'd also like to see "Commiter Responsibilities Guidelines" embedded into a "Software Developers Guide" or similar. I'm afraid the link to meeting minutes doesn't constitute guidelines.</div></blockquote><div><br></div><div>Do you have any specific examples in mind? I was able to hunt down a couple of examples from projects I work on:</div></div><div><div><div>Here are some examples from projects I work on:</div><div><br>
</div><div>GeoTools: "Thou shalt not break the buildDon't break the build" </div><div>- <a href="http://docs.geotools.org/latest/developer/roles/index.html" target="_blank">http://docs.geotools.org/latest/developer/roles/index.html</a></div>
<div><br></div><div>GeoServer: "over time some rules and conventions have emerged"</div><div>- <a href="http://docs.geoserver.org/stable/en/developer/policies/comitting.html" target="_blank">http://docs.geoserver.org/stable/en/developer/policies/comitting.html</a></div>
<div><br></div><div>The GeoMOOSE Coding Standards to cover the same kind of material: "DRY, UI separation etc.." </div><div>- <a href="http://www.geomoose.org/developer/standards.html" target="_blank">http://www.geomoose.org/developer/standards.html</a></div>
</div><span><font color="#888888"><div><br></div><div>-- </div><div>Jody Garnett<br></div><div><br></div></font></span></div>
<br>_______________________________________________<br>
Incubator mailing list<br>
<a href="mailto:Incubator@lists.osgeo.org">Incubator@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/incubator" target="_blank">http://lists.osgeo.org/mailman/listinfo/incubator</a><br>
<br></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>---------------------------------------+--------------------------------------<br>I set the clouds in motion - turn up | Frank Warmerdam, <a href="mailto:warmerdam@pobox.com" target="_blank">warmerdam@pobox.com</a><br>
light and sound - activate the windows | <a href="http://pobox.com/~warmerdam" target="_blank">http://pobox.com/~warmerdam</a><br>and watch the world go round - Rush | Geospatial Software Developer<br><br>
</div>
</div></div></span>
</blockquote>
<div>
<br>
</div>