[geomoose-psc] FW: [Incubator] Committer Responsibility Guidelines Examples?

[Basques, Bob (CI-StPaul)]

All,

This seemed appropriate to forward here . . .to keep  in mind while formulating a GeoMoose version . . .

Bobb



From: incubator-bounces at lists.osgeo.org [mailto:incubator-bounces at lists.osgeo.org] On Behalf Of Jody Garnett
Sent: Saturday, October 13, 2012 10:19 PM
To: Cameron Shorter
Cc: incubator at lists.osgeo.org
Subject: Re: [Incubator] Committer Responsibility Guidelines Examples?

On Wednesday, 10 October 2012 at 7:48 AM, Cameron Shorter wrote:
The key element I'm looking for is a documented process, which is part of the project's supporting web pages, describing how the project will ensure future contributions to the code base will follow license guidelines.
Agreed
The link to the geotools project you reference below does this by requiring new developers to sign a code contribution agreement before committing.
Alas that is only step 1…an important step I admit.

The second step (for GeoTools) is to capture when new code is subjected to a review prior to being included in the library.
- http://docs.geotools.org/latest/developer/procedures/supported.html
(This covers several things, including IP check, and importantly a documentation requirement)

Jody Garnett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20121015/b0b10421/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20121015/b0b10421/attachment.txt>