4 ms·
Well to be fair they explicitly said it wasn't a fork, and that any work they do on it will be pushed upstream. The cynical view, I guess, is that the commits t
by markbnj 8y ago
Well to be fair they explicitly said it wasn't a fork, and that any work they do on it will be pushed upstream. The cynical view, I guess, is that the commits they push will be providing free features that compete with Elastic's paywalled features.
- benatkin 8y agoI can't find anywhere where they said it isn't a fork. I searched the article for the word fork to make sure I didn't miss anything. They said it wasn't an internally forked version meaning it isn't a private fork, and they said that their intention wasn't to create a fork. I'm not completely sure if anything that's core to ElasticSearch is forked. The repos on GitHub are modules not including one that's called "elasticsearch" or "core" or "main" or something like that, but some seem pretty essential. As for myself, I like to call an alternative distro a fork, and I disagree that their intention isn't to create a fork, based on my idea of a fork. They're free to have their opinion on what constitutes a fork, but I don't think they're an authority on it so I'm gonna stick to my current view of what a fork is...
- markbnj 8y agoThe statement was made on the AWS blog, which was linked from an earlier post of this item I think. Anyway: https://aws.amazon.com/blogs/aws/new-open-distro-for-elasticsearch/ https://aws.amazon.com/blogs/aws/new-open-distro-for-elastic... > This is not a fork; we will continue to send our contributions and patches upstream to advance these projects.