search

pgRouting / pgrouting

Repository contains pgRouting library. Development branch is "develop", stable branch is "master"
https://pgrouting.org
GNU General Public License v2.0
1.15k stars 364 forks source link

Contribution agreements #124

Open dkastl opened 11 years ago

dkastl commented 11 years ago

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

dkastl commented 11 years ago

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

dkastl commented 9 years ago

More resources:

dkastl commented 8 years ago

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

dkastl commented 8 years ago

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

dkastl commented 8 years ago

https://cla.github.com/

dkastl commented 8 years ago

@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.

dkastl commented 7 years ago

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.

cvvergara commented 7 years ago

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

cvvergara commented 7 years ago

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

dkastl commented 6 years ago

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/

dkastl commented 4 years ago

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.