Earlier quoted context omitted.
How is AWS stomping all over it? Being able to fork for your own needs is a good thing. You don't make something open source and accept the world's free contributions without acknowledging that.
Again, you’re leading with the definition-of-FOSS argument. Step back from FOSS for a second. I think most people would agree that there’s somewhat of a moral issue with just taking someone else’s open source software and just hosting it and making billions, with nothing for the creators, because you are a megacorp who is good at hosting. Now, is there a way to solve that and have the benefits of FOSS? Both Mongo and…
Elastic and Amazon reach agreement on trademark infringement lawsuit
41–50 of 188 posts
Re: Elastic and Amazon reach agreement on trademark infringement lawsuit
#42Earlier quoted context omitted.
There is. AGPL + dual licensing.
How would dual licensing go down, ideally in these cases? I figured if that worked, Elastic, Redis, MariaDB, Mongo, Timescale, and Cockroach Labs would have gone that route
Re: Elastic and Amazon reach agreement on trademark infringement lawsuit
#43Earlier quoted context omitted.
How is AWS stomping all over it? Being able to fork for your own needs is a good thing. You don't make something open source and accept the world's free contributions without acknowledging that.
Again, you’re leading with the definition-of-FOSS argument. Step back from FOSS for a second. I think most people would agree that there’s somewhat of a moral issue with just taking someone else’s open source software and just hosting it and making billions, with nothing for the creators, because you are a megacorp who is good at hosting. Now, is there a way to solve that and have the benefits of FOSS? Both Mongo and…
This feels like an oxymoron: if it's open source licensed there is explicitly no 'owner.'
Re: Elastic and Amazon reach agreement on trademark infringement lawsuit
#44Earlier quoted context omitted.
AGPL seems to guarantee mostly that you can obtain changes people are applying downstream in order to host your software, and apply them back up. It does not prevent someone from making billions off of doing nothing but hosting your software because they are better than you at hosting.
Nor should it, that's what OSS is about. Why should they not do what they want with your software? As long as it stays open it's OSS
Is there a way to get the benefits of OSS AND for the creators to get more then zero dollars when someone makes a shitload of money off of just putting their software on an enterprise cloud?
Re: Elastic and Amazon reach agreement on trademark infringement lawsuit
#45Earlier quoted context omitted.
Again, you’re leading with the definition-of-FOSS argument. Step back from FOSS for a second. I think most people would agree that there’s somewhat of a moral issue with just taking someone else’s open source software and just hosting it and making billions, with nothing for the creators, because you are a megacorp who is good at hosting. Now, is there a way to solve that and have the benefits of FOSS? Both Mongo and…
> someone else’s open source software This feels like an oxymoron: if it's open source licensed there is explicitly no 'owner.'
Re: Elastic and Amazon reach agreement on trademark infringement lawsuit
#46Earlier quoted context omitted.
Again, you’re leading with the definition-of-FOSS argument. Step back from FOSS for a second. I think most people would agree that there’s somewhat of a moral issue with just taking someone else’s open source software and just hosting it and making billions, with nothing for the creators, because you are a megacorp who is good at hosting. Now, is there a way to solve that and have the benefits of FOSS? Both Mongo and…
> Now, is there a way to solve that and have the benefits of FOSS? The answer is simple - no. Either your product is fully free and you accept that people can fork it, even Amazon, or you choose a restrictive license. You can't make "free" (as in libre) compatible with "but". I can totally see that you think this is unfair, but they did allow it and they were perfectly happy when being FOSS brought them market share.…
Re: Elastic and Amazon reach agreement on trademark infringement lawsuit
#47Earlier quoted context omitted.
How is AWS stomping all over it? Being able to fork for your own needs is a good thing. You don't make something open source and accept the world's free contributions without acknowledging that.
Again, you’re leading with the definition-of-FOSS argument. Step back from FOSS for a second. I think most people would agree that there’s somewhat of a moral issue with just taking someone else’s open source software and just hosting it and making billions, with nothing for the creators, because you are a megacorp who is good at hosting. Now, is there a way to solve that and have the benefits of FOSS? Both Mongo and…
EDIT: regarding your inline response,
> Nowhere in OSS licenses does it include the expectations of free contributions
The expectation is not encoded in the license, it is the reason for choosing the license. Why would anyone want to afford you the benefits of FOSS so that you can personally monetize it and nobody else?
Re: Elastic and Amazon reach agreement on trademark infringement lawsuit
#48Earlier quoted context omitted.
How is AWS stomping all over it? Being able to fork for your own needs is a good thing. You don't make something open source and accept the world's free contributions without acknowledging that.
Again, you’re leading with the definition-of-FOSS argument. Step back from FOSS for a second. I think most people would agree that there’s somewhat of a moral issue with just taking someone else’s open source software and just hosting it and making billions, with nothing for the creators, because you are a megacorp who is good at hosting. Now, is there a way to solve that and have the benefits of FOSS? Both Mongo and…
If you have a moral qualm with bigcorps using your work for free, you don’t license in such a way that they can. Make your own license, or slap AGPL3 on it - either way, no bigcorp touches it.
But you cannot be mad when you say “I release this code under these terms” and AWS takes you up on your offer.
Re: Elastic and Amazon reach agreement on trademark infringement lawsuit
#49Earlier quoted context omitted.
Nor should it, that's what OSS is about. Why should they not do what they want with your software? As long as it stays open it's OSS
Ok, but I am asking is there any solution? Is there a way to get the benefits of OSS AND for the creators to get more then zero dollars when someone makes a shitload of money off of just putting their software on an enterprise cloud?
> Is there a way to get the benefits of OSS AND for the creators to get more then zero dollars when someone makes a shitload of money off of just putting their software on an enterprise cloud?
You're basically asking if something can be simultaneously open and not open.
The benefits come precisely because someone can come along and create a successful business using your software without owing you anything. That is the reason for the benefits.
Re: Elastic and Amazon reach agreement on trademark infringement lawsuit
#50Earlier quoted context omitted.
How is AWS stomping all over it? Being able to fork for your own needs is a good thing. You don't make something open source and accept the world's free contributions without acknowledging that.
Again, you’re leading with the definition-of-FOSS argument. Step back from FOSS for a second. I think most people would agree that there’s somewhat of a moral issue with just taking someone else’s open source software and just hosting it and making billions, with nothing for the creators, because you are a megacorp who is good at hosting. Now, is there a way to solve that and have the benefits of FOSS? Both Mongo and…