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

Handling of legacy StrongLoop CLAs #32

Open
achrinza opened this issue May 6, 2022 · 0 comments
Open

Handling of legacy StrongLoop CLAs #32

achrinza opened this issue May 6, 2022 · 0 comments
Assignees
Labels
P2 Priority 2

Comments

@achrinza
Copy link
Member

achrinza commented May 6, 2022

Previously, contributions to the packages parts of the LoopBack Project were governed by the StrongLoop CLA. This CLA was signed on a per-Git Repository basis, but AFAIK, is identical across Git Repositories. The CLAs were signed on https://cla.strongloop.com/ (now offline).

Eventually the project shifted towards using Developer Certificate of Origin 1.1 (DCO) for new contributions. However the DCO does not apply to existing contributions.

With the shift away from CLA, do we still need to maintain a copy of the signed CLAs for future reference?

I remember that it was part of a different Linux Foundation Project checklist to transfer the signed CLAs, but I don't currently have a link to it at the moment.

As for the OpenJSF, it isn't listed in their on-boarding checklist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Priority 2
Projects
Status: Current/Backlog
Development

No branches or pull requests

2 participants