ckan / ckan/cla

Process for non-CLA'd code

Open
#7 3 comments 0 reactions 0 assignees View on GitHub
not about the wording
Dominant language
No language data
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Although the main chunk of code is going to be done by OKF and others who'll sign the CLA easily, what about the rest?
- are we going to seek out old contributions and get them to sign or replace it?
- are we going to be strict about all new contributions?

Rufus implied that tiny or old contributions we would not seek CLA-signing for - is that ok legally? Is it simply a small risk that CKAN Association is ok to take on, which is less hassle than tracking down a hundred or so people with their one-liners emailed at some point (or whatever it is).

@wardi asked about this

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.