3 ms·
It’s open source, what’s keeping you from patching out that limitation?
by tinus_hn 5y ago
It’s open source, what’s keeping you from patching out that limitation?
- jmg_ 5y agoI've always been curious to see how project owners respond to someone re-implementing portions of paid features in an open source project. Assuming the patch is valid, do they decline it citing the paid feature or do something like making a straw man argument against it?
- akerl_ 5y agoI haven’t tried to pitch something to nginx, but as long as you did it as a clean implementation, “We’re declining to merge, since this is duplicative of code in our paid offering” is the general approach. And then you’re able to maintain your patch set alongside their upstream source.
- sneak 5y agoMy patches removing spyware and phone-home in open source have been universally rejected.
- gary_0 5y agoNothing. For instance, the Debian package nginx-extras includes implementations of some closed-source nginx features. But in my experience the patches are not particularly well-maintained (since they obviously won't be merged by nginx, there's already an official paid version, and the features are named differently from the closed-source ones so they're harder to find).