search

etf-validator / governance

ETF Steering Group and the Technical Committee documents
1 stars 2 forks source link

CLA draft #3

Closed jonherrmann closed 5 years ago

jonherrmann commented 6 years ago

I missed to explain the mechanism behind the CLA checks: On each PR a CI will take the GitHub username of the developer and check if it can download the signed file. The PR will be marked with "tests failed" if the file does not exist. We can also try to implement this with organisations, but this would be harder to achieve.

http://gov.etf-validator.net/cla/: So the idea is that one of us will receive all the signed CLAs, stores them and is responsible for the management of the signatures and the GitHub user accounts? yes

3 (d): What will be at https://gov.etf-validator.net/TOR/CONTRIBUTING.html This will be one part of it: https://github.com/etf-validator/docs/blob/master/TOR/Technical_Committee.adoc#qc-of-developments . I opened an issue for it #5.

cportele commented 6 years ago

resolves #21