8 ms·
It’s “detrimental” to companies who perhaps shouldn’t have chosen a license that allows AWS to do exactly what they did. Those companies can’t simultaneously cl
by sokoloff 5y ago
It’s “detrimental” to companies who perhaps shouldn’t have chosen a license that allows AWS to do exactly what they did. Those companies can’t simultaneously claim to be competent and to have made that choice without knowing what they were doing.
IMO, they chased the benefits of being open source and then changed course when the costs to them exceeded the benefits (which is fine for code going forward), but trademark concerns aside, I can’t see AWS as the bad actor here.
- ignoramous 5y agoIf anything AWS has increased its co-operation with F/OSS businesses of late and this clear shift in strategy was apparent in product / partnership announcements leading up to 2021 re:Invent. AWS, I believe, realise the F/OSS ecosystem mustn't be taken undue advantage of. I mean, AWS stands a good chance of getting caught in a vehement backlash (let alone sporadic bad PR) from the developer community, who ironically form the basis of an entire industry AWS sells into and operates in. With Microsoft + GitHub intensifying their investments in F/OSS, AWS had to play ball. It is smart, not petty on anyone's part. Judging from the tone of the article, I am glad Elastic is content in their current business relationship with AWS. Hopefully, the companies also find an agreement to have AWS' OpenSearch fork merged back in, as well. disclaimer: ex-AWS, but zero insider information.
- pabs3 5y agoIf the rumours here on HN are true they need to start working on giving back some of their internal patches too. I think they also need to start providing funding to FLOSS projects too, and doing something like Google Project Zero.
- skrtskrt 5y agoThis comment is in every thread about this, but there has to be a solution that satisfies FOSS purists as well as casual users without allowing a massive, evil megacorp to just stomp on every company built around open-source solutions.
- Salgat 5y agoHow 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.
- skrtskrt 5y agoAgain, 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 MariaDB have tried to address this with licensing - MariaDB seems to have done this much less clumsily than Mongo, but both still had FOSS advocates shrieking --- EDIT to include response to below comments so everyone doesn't keep repeating the same things: > 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. You have to take the good with the bad > 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. If everyone stomps their feet and says "there's no solution, otherwise it's not OSS!" then the end result is only going to be a lot less open-source software. I'm not asking if someone who wrote code and chose an existing OSS license that allows any possible usage has any real recourse once they want to make money off of it - obviously not. I am asking, can we find a way to ensure software creators are compensated while still having the generally-recognized benefits of FOSS? > Don't you think there's a moral issue expecting free contributions to something which only you are allowed to monetize? Nowhere in OSS licenses does it include the expectations of free contributions > And how can you satisfy users to the greatest extent while also preventing them from using the provider that is best able to meet their needs? Again, can we just find a way for the creators to be compensated? I'd love for the OSS to be available as a hosted solution to be available on every cloud provider, including if the original creators choose to provide a cloud hosting. I'd also love for the original creators to be able to get some sliver of the money AWS/Google/Azure are making off of it. --- To me it seems like if you were to start a business around your open-source code right now, you would be smart to do one of these two things: 1. a MariaDB/CockroachDB BSL approach, where the newest versions are BSL, with a restriction that you can't provide a product where you just host our software without paying us, then all code automatically is fully open-source (GPL or whatever) after x amount of time, or x major version releases. - this comes with the danger of all the bad PR and gnashing of teeth that comes with non-pure-OSS licenses, or people just not adopting it because they dislike or don't understand the license 2. Open-Core with non-OSS-licensed Enterprise versions, and lean really hard into developing hosting and enterprise integrations to make sure you can make some money off the nonfree portions - this seems even more dangerous, that you have to be distracted on such things that are not the core product in order to defend against ending up like Docker, with everyone using it and no one paying you a dime.
- Dylan16807 5y ago> It’s “detrimental” to companies who perhaps shouldn’t have chosen a license that allows AWS to do exactly what they did. Yes, it is. Why the scare quotes? Lots of things are legally allowed that would be very detrimental to me. Or you. > Those companies can’t simultaneously claim to be competent and to have made that choice without knowing what they were doing. I'm glad you can tell the future. > IMO, they chased the benefits of being open source and then changed course when the costs to them exceeded the benefits (which is fine for code going forward), but trademark concerns aside, I can’t see AWS as the bad actor here. You can at least see how the system has big problems, even if you don't want to blame Amazon for them, right?
- sokoloff 5y agoI can see several cases where open sourcing your core product will be very helpful to your company at one phase and harmful in another. Whether that’s a big problem in the system is a topic that people will differ on.
- Dylan16807 5y agoI get it, you see this as complaining about how things shifted when this is a tradeoff they embraced from the start. But there are situations where it's not that things changed, with companies that would love to be open source but it would hurt them at all phases. If you have to be super proprietary to make any money off software, that's bad for everyone. When a piece of code is responsible for enormous amounts of money and none of that goes to the author, that's a bad way to get more code and a bad way to support valuable authors.
- sokoloff 5y agoDoes the presence of AGPL address most (almost all?) of your concern? It seems like that would offer individual users freedom to use and modify the source while precluding Amazon from monetizing it effectively. Those same properties of AGPL mean it’s generally viewed as not as effective at attracting a community of early users, but in a case where the alternative is proprietary-only and the company “wants” to be open-source, AGPL seems a better option for them.