[otisg]

> This is a very surprising move from AWS.

I wonder why you say that? It's kind of obvious that somebody was going to do it sooner or later to protect themselves, no? Perhaps fearing the license change?

> So you effectively get a fork.

Yup, I assume that will happen, too.

[pauldix]

Oh I assumed that someone would do it. I just didn't expect it to be AWS. Elastic is popular enough and the core open source license permissive enough that I expected some sort of fork eventually. The license of the original project is an important factor in this. For example, I wouldn't expect a fork of MongoDB because of the limitations of the AGPL license make it less appealing. With that case I'd expect what AWS already did, which was to create an API compatible system. Also notable is that they're not open sourcing that.

With Elastic, this looks like it's half marketing on AWS' part. They want to start repairing their image in the OSS world so they say they're doing this for the community.

[otisg]

Oh, interesting. I see this as a pure attack/defense move, not just marketing themselves in the OSS world. We'll see :)

[ssummers]

Well, they did also do this: https://aws.amazon.com/corretto/

So it does seem to be a pattern this year.

[otisg]

Yeah. I think the motivation there was the same. Judging by https://github.com/corretto/corretto-8/graphs/contributors and https://github.com/corretto/corretto-11/graphs/contributors there is some adoption... Not a lot yet.