More about elastic: elastic.co/blog/why-license-change-AWS
Here is Amazon's response: aws.amazon.com/blogs/opensource/stepping-up-for-a-truly-open-source-elasticsearch. Note that Amazon is actually accusing Elastic of not being open source.
Here's the Wikipedia take: en.wikipedia.org/wiki/Elasticsearch.
We'll talk more in the next couple weeks about the rise of the "anti-Amazon", or "anti-cloud" licenses. Suffice it to say that AWS has changed things.
Also suffice it to say that open-sourcing your main product is a tricky decision. I am not making a recommendation one way or the other.
From blog.feenk.com/developers-spend-most-of-their-time-figuri-7aj1ocjhe765vvlln8qqbuhto. They have a nice diagram. What most open-source contributors really do is "maintenance", and maintenance is hard. The Feenk blog suggests it represents two-thirds of the work.
Wednesday: Linux, GPL and family
Overall structure of git