CLA snafu
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.6k
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
ally.js is being published under MIT license for the time being. Should the project ever achieve its goals (i.e. move into a FOSS foundation), it is likely that the license has to be changed a bit.
I wonder if it's wise to begin collecting signatures for a CLA (Contributor License Agreement) right away, rather than having to hunt them down later.
I also wonder if it is sufficient to make authors agree to the CLA (e.g. jQuery CLA) via a comment in the PR.
Contributor guide
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.
Research direction
The issue body is the only entry point provided and frames an unresolved question about adopting a Contributor License Agreement. Start by reviewing the proposed jQuery CLA process and the project's future licensing plans, then define the agreement and contribution workflow that would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100