I’m planning to open-source soon—ideally it’s eventually a protocol, not a centralized service! (Once we figure out what “it” is…)
I’m trying to balance benefit to the commons with retaining some privilege/flexibility. Tell me why this licensing plan is a bad idea?
Conversation
n.b. also that I’ll require contributors to sign a CLA just like Clojure’s, which requires shared copyright (not assignment) and pledges all derivative work will be released under FSF/OSI-approved license
clojure.org/dev/contributo
(I’ll also have some trademark guidelines to discourage exploitation.)
10
Ooo that's an interesting addition to the CLA. I've mostly just seen the Apache CLA being used (including here at FB) which is mostly the same big ticket items, with this particular piece not being present.
1