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

Tue Oct 9 15:22:21 PDT 2012

All,

This subject has been receiving quite a bit of discussion on other lists at OSGeo.  It also seems to be the biggest to-do item on our end to move past incubation.

Is there any preference from anyone about which version (listed below) of a method for tracing code contributes and Licensing agreements?

Bobb

From: incubator-bounces at lists.osgeo.org [mailto:incubator-bounces at lists.osgeo.org] On Behalf Of Cameron Shorter
Sent: Tuesday, October 09, 2012 4:49 PM
To: Frank Warmerdam
Cc: incubator at lists.osgeo.org
Subject: Re: [Incubator] Committer Responsibility Guidelines Examples?

Jody,
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.
This means that before a new developer is provided to access to commit to the code base, they need to sign a code contribution agreement, or state publicly that they agree to the project license and software development guidelines.

The link to the geotools project you reference below does this by requiring new developers to sign a code contribution agreement before committing.

A lighter version is provided for the OSGeo-Live project:
http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion
Commit access
To get commit access, you need to create yourself an osgeo user id<http://www.osgeo.org/osgeo_userid>, then join our email list<http://lists.osgeo.org/mailman/listinfo/live-demo> 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:
*         Creative Commons Attribution-ShareAlike 3.0 Unported License for Quickstarts
*         Creative Commons Attribution 3.0 Unported License for Project Overviews
*         Version 2.1+ of the LGPL for install scripts
*         One of the OSI approved Open Source licenses for installed applications
A project admin will then add you to the osgeo<https://www.osgeo.org/cgi-bin/auth/ldap_group.py?group=osgeo> user group.

Other projects, such as Frank's reference below provide something similar.

On 9/10/2012 9:59 AM, Frank Warmerdam wrote:
Jody,

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:

  http://trac.osgeo.org/gdal/wiki/rfc3_commiters

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.

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.

Best regards,
Frank

On Mon, Oct 8, 2012 at 3:41 PM, Jody Garnett <jody.garnett at gmail.com<mailto:jody.garnett at gmail.com>> wrote:
Morning Cameron:

Over on the GeoMoose PSC list we have been going over your following feedback:
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.

Do you have any specific examples in mind? I was able to hunt down a couple of examples from projects I work on:
Here are some examples from projects I work on:

GeoTools: "Thou shalt not break the buildDon't break the build"
- http://docs.geotools.org/latest/developer/roles/index.html

GeoServer: "over time some rules and conventions have emerged"
- http://docs.geoserver.org/stable/en/developer/policies/comitting.html

The GeoMOOSE Coding Standards to cover the same kind of material: "DRY, UI separation etc.."
- http://www.geomoose.org/developer/standards.html

--
Jody Garnett

_______________________________________________
Incubator mailing list
Incubator at lists.osgeo.org<mailto:Incubator at lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/incubator

--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com<mailto:warmerdam at pobox.com>
light and sound - activate the windows | http://pobox.com/~warmerdam<http://pobox.com/%7Ewarmerdam>
and watch the world go round - Rush    | Geospatial Software Developer

--

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

http://www.lisasoft.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20121009/f4eabf26/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20121009/f4eabf26/attachment.txt>