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

Thu Oct 11 09:25:27 PDT 2012

On Tue, Oct 9, 2012 at 7:57 PM, Jim Klassen <klassen.js at gmail.com> wrote:
> My understanding of common practice is similar to what the OSGeo Live
> project does.
>
> 1) There is a document that enumerates the licenses and that committers have
> responsibility to make sure the code they commit is theirs to commit and
> that it is committed following the licensing structure.
>
> 2) Committers acknowledge that they will abide by said document.

I like this method (some document that committers acknowledge) as well.

Eli

>
> This seems to be what happens with GDAL and is what I remember happening
> with MapServer.  I would suggest (as usual) that we basically duplicate the
> process from MapServer rather than reinvent a wheel.  I'm open to other
> options, but the OpenLayers paper on file method seems to add more questions
> than answers (who administers it, where, how does this get transferred,
> checked, publicly acknowledged...)
>
> On Oct 9, 2012, at 5:22 PM, Basques, Bob (CI-StPaul) wrote:
>
> 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, 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:
> ·         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 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> 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
> http://lists.osgeo.org/mailman/listinfo/incubator
>
>
>
>
>
> --
> ---------------------------------------+--------------------------------------
> I set the clouds in motion - turn up   | Frank Warmerdam,
> warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> 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
>
> _______________________________________________
> Incubator mailing list
> Incubator at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/incubator
> _______________________________________________
> geomoose-psc mailing list
> geomoose-psc at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
>
>
>
> _______________________________________________
> geomoose-psc mailing list
> geomoose-psc at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
>