loopbackio / loopbackio/loopback-governance
Handling of legacy StrongLoop CLAs
@dhmlau is already working on this.
Since May 11, 2022.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.