Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitRoyalty – First OSS Paywall

gitroyalty.com

Post reply on HN
Print view View original

51–52 of 52 posts

Re: GitRoyalty – First OSS Paywall

#51

Post by joepie91_ »

sdrzn wrote: post #2

Thanks Feross! GitRoyalty is an experiment that allows OSS project maintainers to hide a package’s manifest file (or build script) behind a monthly subscription. This way users will have to subscribe in order to install the package using dependency managers like NPM. The idea is that with low prices and the power of numbers, both popular and transitive OSS dependencies can sustain development instead of relying on a…

> * While this isn’t FOSS, it keeps the best parts of open source in place (open GitHub collaboration, permissive licensing) while incentivizing users to pay contributors

No, those aren't "the best parts of open source". The best part of open-source is building a collective public commons, which this model does not allow for.

Re: GitRoyalty – First OSS Paywall

#52

Post by sdrzn »

joepie91_ wrote: post #51
sdrzn wrote: post #2

Thanks Feross! GitRoyalty is an experiment that allows OSS project maintainers to hide a package’s manifest file (or build script) behind a monthly subscription. This way users will have to subscribe in order to install the package using dependency managers like NPM. The idea is that with low prices and the power of numbers, both popular and transitive OSS dependencies can sustain development instead of relying on a…

> * While this isn’t FOSS, it keeps the best parts of open source in place (open GitHub collaboration, permissive licensing) while incentivizing users to pay contributors No, those aren't "the best parts of open source". The best part of open-source is building a collective public commons, which this model does not allow for.

GitRoyalty works for transitive dependencies as well (dependencies of dependencies) by ensuring users are subscribed to all transitive dependencies before installing the direct dependency. So in this way this model not only still allows building a collective public project, but also compensates each developer that's involved in it.
Post reply on HN