search

akvo / akvo-flow

A data collection and monitoring tool that works anywhere.
http://akvo.org/products/akvoflow/
GNU Affero General Public License v3.0
65 stars 31 forks source link

Implement Contributors agreement #526

Closed mtwestra closed 4 years ago

mtwestra commented 10 years ago

We want it to be easy for people to contribute to the Akvo FLOW codebase, and on the other hand ensure that everyone can use FLOW without worrying about a copyright claim or having some important piece of functionality disappear.

At the moment, we a paper contributor agreement, which needs to be print off, signed and submitted to Akvo. However, this might be quite a heavy procedure.

Other projects use the idea of a Developers Certificate of Origin (DCO), which states that the contributor is entitled to contribute this code to Akvo, and that the contributor is willing to have it used in distributions and derivative works.

Basically, it would require all commit messages to have a signed-off-by line off the following shape:

Replacing John Smith’s details with your name, email address and GitHub username.

Usually, the procedure is descibed in a CONTRIBUTING.md file in the root of the repo, as shown here: https://github.com/dotcloud/docker/blob/master/CONTRIBUTING.md#sign-your-work

Often, some exceptions to the contributor agreement are used, for example:

Some example implementations: Example 1: Enyo "IMPORTANT: All pull requests must now include the following line in the pull request comments (using your full name and email address), which indicates your contribution complies to the Enyo Developer's Certificate of Origin v1.1: http://enyojs.com/community/dco/"

http://enyojs.com/community/contribute/

Example 2: Docker http://blog.docker.io/2014/01/docker-code-contributions-require-developer-certificate-of-origin/

Example 3: Linux http://elinux.org/Developer_Certificate_Of_Origin

bjelkeman commented 10 years ago

Ok, let me review this next week.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.