sdrzn

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.

You're absolutely right this should not be a clause in our ToS. I've just removed it and notified all repository owners of the change.

There was a misunderstanding of what 'Content' entailed on my part–it was meant to encompass anything without a license already attached in order to grant us rights to distribute unlicensed software. Our ToS should have been more specific, I apologize.

Very interesting thought–I'd love to see how this dynamic actually plays out. I personally would welcome more contributors v.s. doing their work myself.

I think if a project maintainer were to act maliciously in terms of earnings share, developers would call them out and less people would contribute as a result.

> rather have an own GitRoyalty account

This is definitely on the roadmap and eventually we'll expand outside of GitHub and allow repos from other hosts like GitLab.

> ... changing all of the GitRoyalty package links, installing the packages...

You should always commit your GitRoyalty license keys and share it with your teammates. This way you never have to deal with your package.json/lock files directly, just `npm install` and you're good to go! (This takes care of updating for you as well)

> I'm pretty impressed with the beautifully done website.

Thank you! I just used bootstrap and made the docs myself.

Great idea and you can do this with GitRoyalty! You can hide any files you want behind the subscription–it doesn't have to be the manifest or build script. So in your case you can hide a docs.md file.

I think companies will hop on board if it means saving engineering hours. OSS has monetary value to these businesses, enough to make a small subscription to support the tremendous development efforts behind it. In most projects, OSS makes up the majority of the codebase, so it is "big/important" IMO.

As for the legal aspect, permissive licensing like MIT/Apache 2.0 allows developers and consumers to distribute and use code pretty freely, which is what makes OSS so great and why GitRoyalty doesn't impose any other licensing.

One of the driving factors behind making GitRoyalty was the corporate mentality I've experienced where management will pay for whatever is necessary, but think twice before sponsoring anything (especially transitive projects).

GitRoyalty just hosts a git remote repository that you pay to get access to. NPM and almost all other package managers support installing from git URLs, and too many people rely on this functionality for it to ever be removed.

The purple dollar value on the Discover page shows the Individual price of the repository, not the total profits.