Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addressing CLAs #11

Open
shanecoughlan opened this issue Sep 5, 2023 · 1 comment
Open

Addressing CLAs #11

shanecoughlan opened this issue Sep 5, 2023 · 1 comment

Comments

@shanecoughlan
Copy link
Contributor

From Item 4 here:
#2

Should we include a requirement that a process exists to check and get necessary signatures for CLA's? If so it should also be documented and communicated to the program participants.

@Jimmy-ahlberg
Copy link

The background here being that some Organizations have chosen to delegate/not delegate with a Power of Attorney (PoA) or similar the signing of CLA's and similar documents. Thus a project, unless they have a copy of said PoA, does not really know if a CLA was properly signed or not.

To reduce risk for organizations contributing to a project, the project itself, and downstream users, having clarity on if the CLA is correctly signed or not is beneficial.
For this purpose would be beneficial if a contact point within the organization existed, or if an organization has communicated that it uses this specification the project and downstream recipients can trust that any CLA has been properly signed. Thus reducing IP risks and frictions to contributors, projects, and downstream users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants