medialize/ally.js

CLA snafu

Open

#48 opened on Oct 19, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,519 stars) (97 forks)batch import
help wantedquestion

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

Tech stack
javascript
Domain
developer experience
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
This issue discusses whether ally.js should start collecting Contributor License Agreements (CLAs). It is a policy decision, not a code change. No specific files are involved. The maintainer should decide on the approach and potentially set up a CLA signing process. There are no linked PRs or code modifications.