2 ms·
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 las
by sangnoir 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. 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.