[Fiware-ge-owners] Project Harmony - adopting and enforcing a CLA.

Jason Fox jason.fox at fiware.org
Thu Oct 22 11:03:20 CEST 2020


After the recent agreement within the TSC to adopt a common CLA <https://en.wikipedia.org/wiki/Contributor_License_Agreement> for FIWARE Components, it is necessary that individual contributors sign the CLA before contributing. This process can be easily automated by adding a GitHub Action to the PR process. Attached below is a Git Patch file which will add the necessary changes. Copy the cla.patch file to the root of each of your GitHub repositories and run the following commands:


git checkout -b feature/cla 
git am cla.patch


The Git  patch is generic so <GIT_HUB_PATH> and <PROJECT NAME>  will need to be replaced after the change. The cla.yml file may also need to be updated (things like allowlist)

The feature branch may then be pushed to the remote repo as a PR.


This PR adds a mechanism to enforce the harmonized FIWARE CLA for individuals <https://fiware.github.io/contribution-requirements/individual-cla.pdf>
Added a Pull Request Template
Added a code of conduct
Added contributions referring to the harmonized CLA for FIWARE Enablers.
Added a GitHub Action to enforce the CLA <https://github.com/cla-assistant/github-action>. See https://github.com/cla-assistant/github-action <https://github.com/cla-assistant/github-action>
To enable the GitHub Action, you'll need to follow the instructions here:  https://github.com/cla-assistant/github-action#environmental-variables- <https://github.com/cla-assistant/github-action#environmental-variables->

Specifically you'll need to:

1. create a personal access token <https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/creating-a-personal-access-token> https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/creating-a-personal-access-token <https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/creating-a-personal-access-token>
2. grant the token repo scope 

3. Alter the settings of this repository and to add a secret <https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets> called PERSONAL_ACCESS_TOKEN.

https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets <https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets>

 <https://user-images.githubusercontent.com/3439249/96732580-c7af5980-13b8-11eb-8220-da8e82e6b7d0.png>
To see the CLA enforcement in action look at the PR here <https://github.com/jason-fox/github-api-testing/pull/1>: https://github.com/jason-fox/github-api-testing/pull/1 <https://github.com/jason-fox/github-api-testing/pull/1>





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ge-owners/attachments/20201022/1417c102/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cla.patch
Type: application/octet-stream
Size: 12807 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-ge-owners/attachments/20201022/1417c102/attachment-0001.obj>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ge-owners/attachments/20201022/1417c102/attachment-0003.html>


More information about the Fiware-ge-owners mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy