Re:Kafka on Kubernetes: What could go wrong?
by sofixa on Saturday July 23, 2022 @03:46PM
(#32206929)
> It's just another startup source-available license parading "I want to be open source on GitHub.. but gosh please don't use my code without paying me!!"
Isn't it "please don't create a competing service to us"? Considering how many tech startups struggled with that very same problem, it's a completely understandable concern. Some, like Sentry, have a time limited license - BSL for 2 years and then it switches to Apache/MIT. Sounds like a pretty good compromise.
> Companies should stop instructing Heather to create these licenses IMO, and just split their code into open source and enterprise-only parts. It's easier, more honest, and ends this whole debate. It's the GitLab/Sourcegraph model too.
It's not easier for them, because the codebase is split, they have to consider which features go where, potentially piss off people by moving features to the enterprise only parts (e.g. InfluxData). And that doesn't stop an Amazon selling your open core version with some custom additions.
Isn't it "please don't create a competing service to us"? Considering how many tech startups struggled with that very same problem, it's a completely understandable concern. Some, like Sentry, have a time limited license - BSL for 2 years and then it switches to Apache/MIT. Sounds like a pretty good compromise.
> Companies should stop instructing Heather to create these licenses IMO, and just split their code into open source and enterprise-only parts. It's easier, more honest, and ends this whole debate. It's the GitLab/Sourcegraph model too.
It's not easier for them, because the codebase is split, they have to consider which features go where, potentially piss off people by moving features to the enterprise only parts (e.g. InfluxData). And that doesn't stop an Amazon selling your open core version with some custom additions.