[Incubator] Code contribution examples?

Cameron Shorter cameron.shorter at gmail.com
Tue Feb 12 00:51:06 PST 2013

I assume that you are referring to processes that projects need to have 
in place to ensure that contributed code meets the license guidelines?

For the OSGeo-Live project we use the following process:

Commit access
To get [OSGeo-Live] commit access, you need to create yourself an osgeo 
user id, then join our email list and ask to be given access to 
subversion. In this email, you will also need to confirm that you will 
comply with our license guidelines. Write something like:
"Hi all, I'd like to contribute XXX to OSGeo-Live. Could I please get 
access to subversion. My osgeo-user id is: YYYY.
I confirm that my contributions to OSGeo-Live will be compatible with 
the OSGeo-Live license guidelines at the time of contribution."

The current OSGeo-Live license guidelines are:
A project admin will then add you to the osgeo user group.

The first thing you should do to test your svn install is to add your 
name the code contributors or translators list(s):

On 11/02/2013 9:54 AM, Jody Garnett wrote:
> I am continuing to struggle with examples of how to handle code 
> contribution (in the context of GeoMoose I would like to be able to 
> quickly point to a range of examples, and see if we can find one to 
> meet the communities needs).
> Can I ask the list for good (or bad) examples and why you like them?
> For my part I will try and gather these up into the FAQ, since this 
> discussion happens with each project that comes along.
> -- 
> Jody Garnett
> _______________________________________________
> Incubator mailing list
> Incubator at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/incubator

Cameron Shorter
Geospatial Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20130212/0e9030e8/attachment.html>

More information about the Incubator mailing list