[mapguide-internals] CLA

Traian Stanev traian.stanev at autodesk.com
Mon Mar 9 19:28:25 EDT 2009

I've signed the agreement too, and I'm listed under FDO already. Don't tell me I have to sign another piece of paper -- it ain't happening! :-)

From: mapguide-internals-bounces at lists.osgeo.org [mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch [Jason.Birch at nanaimo.ca]
Sent: Monday, March 09, 2009 7:11 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] CLA

I don't disagree with my proposal...

So, for now Jackie is the only one who is allowed to check in code? ;)

(cheeky way of suggesting that the wiki be updated with the current list
of CLA signatories, including those covered under Corporate CLA).

BTW, I'm not sure if this came up here or somewhere else, but I remember
seeing something about CCLA folks also needing to have individual CLAs?
I could see this as being important because:
 - we don't have to worry about tracking who leaves what company; and
 - some people work for companies that don't have draconian employment
contracts where the company gets ownership of off-hours code and your
first born.


-----Original Message-----
From: Tom Fukushima
Sent: March-09-09 4:04 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] CLA

There wasn't any more discussion on this.  I would like to change how we
do things and back Jason's suggestion that everyone sign a CLA in order
to make any submission.

Does anyone disagree? If not I will make the change in 48 hours.

I will also add a link to this page so that we can quickly see who has
signed the CLA:


Here is Jason's original suggestion:
Hi all,

Our current "getting involved" document only talks about CLA
requirements for committers:


I think that we should strip "and has a signed Contributor License
Agreement on file with OSGeo" from the "Project Developer" role and add
something like:

"Regardless of developer status, code will only be committed if a signed
Contributor License Agreement has been placed on file by the developer.
This is required to ensure that our code base remains encumbrance-free."

mapguide-internals mailing list
mapguide-internals at lists.osgeo.org

More information about the mapguide-internals mailing list