4 ms·
I had to check that today is not April 1st. If you badly want my money, sell me your product honestly, under a commercial license, and don't call it OSS. There
by nine_k 7y ago
I had to check that today is not April 1st.
If you badly want my money, sell me your product honestly, under a commercial license, and don't call it OSS. There are other "source available" licenses.
If you want a donation from me, show your tipping jar / patreon / whatever else link.
If you want your software be OSS, well, don't conceal the source.
I suppose that a project of any significance that would use such a "paywall" will be plainly forked, with a build / manifest / whatever file maintained manually.
- sdrzn 7y agoThe 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)
- bb88 7y ago> If you want your software be OSS, well, don't conceal the source. That's what struck me as odd too. #2 of the OSI "Open Source Definition" seems useful. The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a product is not distributed with source code, there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost, preferably downloading via the Internet without charge. The source code must be the preferred form in which a programmer would modify the program. Deliberately obfuscated source code is not allowed. Intermediate forms such as the output of a preprocessor or translator are not allowed. So charging for a reasonable reproduction fee is fine, but a subscription would seem to violate the spirit of this, since the subscription isn't being paid to github for their cost of reproduction. AFAICT, the fee is paid to the developers, not to anyone that does any actual reproduction.
- kiba 7y agoCharging money for OSS is perfectly kosher under FOSS definition.
- rmc 7y agoFLOSS doesn't require that you give your software away for free. It's totally fine to require payment. (Now, the traditional 'sell copies of software' doesn't work so well for FLOSS, since every customer of yours can start selling it themselves, or give it away to anyone, which is why this approach is rare. But it's still FLOSS)