pgrouting Contribution agreements

Think about if and how to manage contributor agreements: past present future: http://lists.osgeo.org/pipermail/incubator/2013-June/002181.html

Does a small pull request require a contribution agreement?
Ask Jody (OSGeo incubation) for some template

Jun 16 '13 10:06 dkastl

This looks like an interesting way without too much adminstrative overhead: http://nodejs.org/cla.html

Aug 04 '13 02:08 dkastl

More resources:

http://www.harmonyagreements.org/
https://www.clahub.com/

Jul 21 '15 09:07 dkastl

http://www.eclipse.org/legal/CLA.php http://www.eclipse.org/legal/CoO.php

Dec 01 '15 08:12 dkastl

https://github.com/cla-assistant/cla-assistant

Dec 01 '15 09:12 dkastl

https://cla.github.com/

Dec 01 '15 11:12 dkastl

@cvvergara I'm not sure exactly how to handle this at the moment in the easiest way. The topic came up also on OSGeo mailing list. I want a solution, that doesn't require administration overhead. Not sure about the currently best approach.

Jul 19 '16 03:07 dkastl

If we are planning OSGeo incubation or something similar we probably need contributors "sign" a CLA in some way. I keep this open for now.

Dec 09 '16 00:12 dkastl

This is what I figured out: http://irclogs.geoapt.com/osgeolive/%23osgeolive.2016-12-09.log

Dec 09 '16 00:12 cvvergara

Contribution agreement has be approved here https://lists.osgeo.org/pipermail/incubator/2017-April/003242.html

May 18 '17 11:05 cvvergara

There seems to be a new tool, that will automatically ask a new contributor to "sign" a CLA with the first pull request. Maybe worth to check?

https://cla-assistant.io/

Jan 30 '18 14:01 dkastl

I think we should go with DCO: https://github.com/consento-org/mobile/issues/83 It's the better way to handle eventual copyright issues. CLA can be bad for community contributions.

Feb 18 '20 03:02 dkastl