How about we write the thing up clearly in the developers guide, and we add a
description into JIRA when they report the bug (we already have our own custom
descriptions). We may be able to link to the correct page of the developers
guide.
I am wondering if we can instead have a
On Tuesday, 28 May 2013 at 4:18 PM, Jody Garnett wrote:
How about we write the thing up clearly in the developers guide, and we add a
description into JIRA when they report the bug (we already have our own
custom descriptions). We may be able to link to the correct page of the
developers
An other OSGeo project, OSGeo Live, requested an email from the mailing
list from the potential committer before he/she gets commit access (see
Section Commit Access right here:
http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion) to subversion. I know
its a bit different with github's pull
On 28/05/13 14:18, Jody Garnett wrote:
I am wondering if we can instead have a contributor-agreement-lite,
I think this
page was meant to have checkboxes and an accept button:
http://www.eclipse.org/legal/CLA.php
(It says at the top that it is a reference copy, to actually fill it in
you
We could make everyone agree, and make it really easy, like a web form.
I could not find an form version of the Eclipse CLA.
On 28/05/13 14:18, Jody Garnett wrote:
How about we write the thing up clearly in the developers guide, and we
add a description into JIRA when they report the bug (we
Well the form idea is only one idea. Asking for a statement in Jira or GitHub
is fine as well. Ask them enough times and they may want to sign code
contribution agreement.
--
Jody Garnett
On 28/05/2013, at 6:19 PM, Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
wrote:
We could make
With the recent adoption of the new GeoTools contributor agreement, the
PMC considered the status of patches submitted by community members who
have not signed the agreement. For example, we sometimes receive patches
attached to Jira issues or emailed to the mailing lists. As mentioned in
