Twitter | Search | |
Joseph Ruscio Mar 11
Open Distro for Elasticsearch is absolutely a fork. At some point in the future AWS will acknowledge this and claim that it was forced into becoming a fork by refusal of upstream to cooperate.
Reply Retweet Like
Mark Imbriaco Mar 11
Replying to @josephruscio @adamhjk
And it will be true.
Reply Retweet Like
Joseph Ruscio Mar 11
Replying to @markimbriaco @adamhjk
Sure but it’s the OSS equivalent of entrapment.
Reply Retweet Like
Mark Imbriaco Mar 11
Replying to @josephruscio @adamhjk
What if I told you it was already true before they did it.
Reply Retweet Like
Joseph Ruscio Mar 11
Replying to @markimbriaco @adamhjk
I think that’s my whole point? They know this is a fork and it’s disingenuous to claim otherwise.
Reply Retweet Like
Adam Jacob Mar 11
I think and both believe it to be a distro, and that their intent is to upstream everything that can be, or it is in a module. That means until they carry patches, its not a fork, but a true distribution.
Reply Retweet Like
adrian cockcroft Mar 11
Amazon Linux is a Distro of Linux with packages added. Corretto is a distro of OpenJDK, that can’t use that name because of the way the name is licensed. Open Distro for ElasticSearch is a distro that can use the name because we have that right. We know how to run a distro.
Reply Retweet Like
Adam Jacob Mar 11
I don’t question wether you know how to run a distro. I question why anyone would let you. I know I wouldn’t for any business I was in control of. I do think doing it anyway (because you can) is also a mistake - distro or no, its needlessly aggressive.
Reply Retweet Like
adrian cockcroft Mar 11
The point here is that Elastic wants all the benefits of being open source, and wants to retain complete control as well, so is shifting its business and customers to a proprietary model and was hoping customers didn’t notice.
Reply Retweet Like
msw Mar 11
Replying to @adrianco @adamhjk and 2 others
Just from a pragmatic perspective (I really don't like getting into a "you're not doing {open source,your business model right} right" argument), the OSS ES was missing a fair bit of necessary functionality. There is now a good deal more open source available...
Reply Retweet Like
Adam Jacob
Yes! I must repeat myself: what you’ve done isn’t bad, and it isn’t wrong. That you could do it and benefit from their primary brand directly is a massive mistake in their trademark policy, in my opinion. Because you are competing with them. Doesn’t matter why.
Reply Retweet Like More
Adam Jacob Mar 11
Replying to @_msw_ @adrianco and 2 others
I think it’s a big deal because it’s largely the only defensible thing anyone has once you oss - if you open Source all the kit, and any service provider can run it for their customers without paying you for anything, and they can use the brand while they are at it: what’s left?
Reply Retweet Like