3 ms·
> The underlying issue here in this one is that people (apparently so far!) want to use AWS/GCP/etc more than they want to use mongo, redis, cockroach, or any p
by OJFord 7y ago
> The underlying issue here in this one is that people (apparently so far!) want to use AWS/GCP/etc more than they want to use mongo, redis, cockroach, or any particular technology.
> No license change will fix that.
Well, perhaps not a licence change, but if it's good enough that it's The One the provider wants, but it can't offer it under the terms of the licence, then paying for it under a separate licence could be a win for both parties.
- sangnoir 7y agoDepending on the licensing cost and the effort required to integrate the project with their infrastructure, it might be cheaper for the provider to fork the last version before the relicense and support it going forward. Maintaining API/wire-protocol compatibility isn't that hard for large tech companies these licenses are trying to battle. I don't think these open source companies are not aware of the risk of forking, but they are between a rock (AWS/GCP) and a hard place (VC returns demands).
- Xylakant 7y ago> Depending on the licensing cost and the effort required to integrate the project with their infrastructure, it might be cheaper for the provider to fork the last version before the relicense and support it going forward e.g. AWS creating OpenDistro for Elasticsearch and adding core elastic stack functionality for free (Auth/TLS/Alerting) by integrating and adapting existing OS components.