-
Notifications
You must be signed in to change notification settings - Fork 4
Contributor Licence Agreement
SciTools uses CLA Assistant to manage our CLA signatories.
The check should run within seconds. If this doesn't happen then it's best to trigger a re-run.
Just open this URL, modified appropriately: https://cla-assistant.io/check/SciTools/iris-grib?pullRequest=295
A Gist belonging to SciTools-assistant. Updates to this text will 'reset' existing signatories - further contributions will require agreeing to the new version.
Note that this text includes reference to signatures being managed by CLA Assistant, and how they store data. If this changes, the CLA text will need to be changed also. Watching the CLA Assistant repo for new releases is a good way to be notified of such changes. The text has been written/updated in collaboration with the UK Met Office legal staff.
SciTools-assistant login details are held my the AVD Team at the UK Met Office.
Log in to: CLA assistant (cla-assistant.io), granting any requested permissions. Your GitHub account will need to already have sufficient permissions to the repo/organization you are setting up.
No GUI-specific instructions are written here as they are bound to change over time. Note that some settings are only available when editing a setup, rather than when initially adding.
We apply the CLA at the organization level - further permissions will be requested to make this work; grant those when requested. With this setting, all repos under the organization get monitored in the same way, including new ones added later.
We use the Share option so that a signature within SciTools also applies to SciTools-incubator etcetera.
We do not implement any minimum changes settings - all contributions require a signature.
We exempt bots (e.g. Dependabot) from needing to sign. The *[bot] pattern is effective at catching all instances.
Publicly listed members of the MetOffice GitHub organization are exempt from signing - agreement is implicit in their employment. Publicizing or hiding organization membership - GitHub Docs
Once set up, be sure to click the option to recheck all currently open pull requests in the organization.
The above setup via cla-assistant.io should automatically add a new CI check for CLA signatories.
Ensure that any contributing guidelines (e.g. CONTRIBUTING.md etcetera) reference this CLA, and not an older out-dated arrangement.
Apply a branch protection rule to prevent merging if the CLA CI has not passed. Note that this can only be added if the CLA CI has run in the last week, so you might need to raise a dud PR for quieter repositories.