3 ms·
The problem with non-permissive licensing is that a lot of employment contracts strictly forbid them. That and commercially licensed OSS projects have no way to
by sdrzn 7y ago
The problem with non-permissive licensing is that a lot of employment contracts strictly forbid them. That and commercially licensed OSS projects have no way to distribute funds to arbitrary contributors in a legally straightforward way.
And I personally have not had any success with donations, whereas 2 days after setting up my project with GitRoyalty me and my contributors are making $10/month.
- nine_k 7y agoThis is indeed an interesting problem! It looks like a way to sell a commercial license in effect, without selling it in any legal terms. I wonder how funds acquired via GitRoyalty get distributed, from the legal standpoint, and what makes such distribution different from distributing a share from a sale of a commercial license.
- zaphirplane 7y agoWhat is the difference between your open source repository and this one. I am assuming that the model is having 2 repos one open source and the other with gitroyalty with something extra (edit I see it uses sub modules)