3 ms·
Not sure hiding/removing the project build or manifest is the best approach. Documentation seems like it’d be a better target. Use the software free full OSS bu
by elcritch 7y ago
Not sure hiding/removing the project build or manifest is the best approach. Documentation seems like it’d be a better target. Use the software free full OSS but non-simple or extensive documentation for a subscription fee. It seems a number of OSS devs make money by writing books, and it could incentivize good documentation as well. There’s been many times I’d not want to pay for a license but would’ve begged for in depth documentation.
- sdrzn 7y agoGreat 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.
- Gys 7y agoAccessing the documentation is more like a one time thing. I could always copy it somewhere else for later reference.
- antpls 7y agoLike any file that you would hide with GitRoyalty, you could always share the full repo once you have access to it (probably illegally) I believe documentation would become outdated sooner than build scripts with new releases, and would require effort to maintain (more than build scripts), which would better justify to pay. Anyway, the idea of GitRoyalty seems not to make technically impossible to share the payed content, but rather to propose a way for honest people to remunerate honest developers and library maintainers.
- cgijoe 7y agoI love this idea.