3 ms·
I very much sympathize with the goals here (I'm deeply concerned about open source sustainability), but this doesn't strike me as a good solution. Not a single
by freedomben 7y ago
I very much sympathize with the goals here (I'm deeply concerned about open source sustainability), but this doesn't strike me as a good solution. Not a single company I have worked for would allow a dependency like this in their repo (and I wouldn't blame them). Not only is it legally gray, but somebody has to maintain that subscription. We do buy licenses but only for big/important stuff. Something like this could work for a project of sufficient magnitude, but I don't think it will for smaller stuff.
- sdrzn 7y agoI 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).
- latchkey 7y agoHave you ever dealt with the purchasing department at a large corporation? Hint: They really don't care about saving engineering hours.