Niche Twitter opinion request!
Soliciting thoughts on “source-available” licenses. When are they most/least appropriate? Are there better/worse specific licenses for certain circumstances? Best writing on the subject?
Conversation
Context here is: I would like to encourage some avenues of mash-up and collaboration for , and eventually I’d like to actually-OSS everything. But I still feel insecure enough in my crowdsourced funding model that I want to leave some options open for the near future.
3
1
14
Quote Tweet
ECC released its implementation of Halo 2 under the TGPPL, a new type of open-source license.
electriccoin.co/blog/introduci
#Zcash $ZEC
Show this thread
1
1
This is very interesting—will do some reading; thank you!
1
2
Follow-up after much reflection; my current thinking is:
1. Dual-license under AGPL and Business Software License (no obligations for private use, devolves to Apache after 3 years)
2. Client libraries licensed Apache.
3. Use CLA to retain privilege to sell private licenses.
1
1
I like that this keeps the sources available to all (subject to onerous copyleft restrictions), makes sources permissively available "eventually", and retains some monetization flexibility. A balancing act…