3 ms·
that's kind of a "for now" issue. eventually these will become common enough that things will shake out, but it will take years.
by foobiekr 7y ago
that's kind of a "for now" issue. eventually these will become common enough that things will shake out, but it will take years.
- tolmasky 7y agoHasn’t happened for GPL3, and I would bet it won’t happen for these either. More importantly, the one-click solutions offered by amazon, GCP, etc. will always be the GPL2/MIT/etc licensed products, while the others will require you to either install and manage on your own, or sign up separately outside your main cloud provider. This will be an additional point of friction (potentially more so than the licensing woes).
- amenod 7y agoI wouldn't be so sure of that. For AWS it is risky to not support popular platforms, because it gives their customers a reason to move elsewhere. AWS is not the only cloud provider around (and certainly not the cheapest). There is a reason they developed an alternative to MongoDB instead of just saying "sorry, we don't support MongoDB because of license". They couldn't buy a license from them because that would set a bad example (they are not really fond of these alternative licenses) and they probably didn't want to maintain MongoDB codebase (before relicensing), so this was the only solution left.
- dragonwriter 7y agoNo, it's fairly inherent; the OSD is very well aligned with the considerations that would support whitelisting licenses that adhere to it.