7 ms·
The problem isn't really here. The problem is that everyone wants a permissive abusable license when AGPL would be just fine. If everyone here complaining just
by karmakaze 7y ago
The problem isn't really here. The problem is that everyone wants a permissive abusable license when AGPL would be just fine. If everyone here complaining just used AGPL then we wouldn't have this Amazon situation.
People want to have their cake and eat it too. They started with an MIT license because it gets more uptake then whine when the license terms are being followed.
But then it wouldn't be widely used. The solution to that is for everyone to use AGPL then the open-source playing field is level again.
- hendzen 7y agoMongodb already used AGPL prior to switching to the SSPL...
- eeZah7Ux 7y agoThe problem is that only MongoDB did it, not the majority of the FLOSS ecosystem.
- kemitchell 7y agoThat’s not what Mongo said. They called out specific issues with AGPLv3’s terms. http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2018-October/003603.html http://lists.opensource.org/pipermail/license-review_lists.o...
- TAForObvReasons 7y agoAGPL is vulnerable to certain workarounds in the same way that GPL was. The CC class of non-commercial licenses might be more applicable, but that may harm adoption. EDIT: honestly not sure why this is so heavily downvoted (-7 as of the edit), the whole point of SSPL and other licenses is to address the "workarounds" that Amazon and others have discovered in AGPL
- boramalper 7y agoI’m not sure if CC is meant for software either (except for CC0 perhaps). For instance, does non-commercial mean (1) you cannot use [the output of] the program for any commercial purposes, or does it mean (2) you cannot sell the program itself (and its derivatives). The difference is subtle but AGPL permits (1) whilst practically forbidding (2) by enforcing copyleft; hence it fits the OSS criteria whereas CC NC wouldn’t if both (1) and (2) are true.
- detaro 7y agoCreative Commons themselves say that CC licenses (outside CC0) are not designed and not recommended for software.
- AnaniasAnanas 7y agoWould you mind elaborating on that? I am interested in a super-copyleft license for my next project and thought that AGPL was the "best" option out there. In what ways can it be bypassed?
- Reelin 7y agoCheck mongoDB's SSPL FAQ (https://www.mongodb.com/licensing/server-side-public-license/faq#when-to-use https://www.mongodb.com/licensing/server-side-public-license...). As far as I'm concerned, SSPL is superior to AGPL in that it catches all the bits that make your software actually work, forcing you to include them as part of the offering. I honestly don't understand the apparent objection to referring to a license with such a clause as open source - all it does is close a (major imo) loophole.
- detaro 7y ago> “Service Source Code” means the Corresponding Source for the Program or the modified version, and the Corresponding Source for all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available.” So I can't run a service for it on VPS at a hosting provider, because I can not share the source to the backup system, hypervisor and load-balancer they use? Are firmware-blobs in my kernel-drivers ok? That seems extremely open and far-reaching, to the point that one could argue that it clearly is intended to forbid offerings as a service, even if it pretends not to. EDIT: after looking up details about the "comical debate" (quote article), that indeed appears to have been one of the arguments. Not surprising the article badmouths the OSI, but doesn't actually engage with or even dare mention their arguments.
- Reelin 7y agoUpon rereading the bit you quoted, I agree that could be an issue. I had initially misinterpreted "all such that a user could run an instance of the service using the Service Source Code you make available" to mean it was limited to any essential supporting bits you had implemented that might have otherwise been made proprietary (much to the detriment of a user trying to actually use the source code you provided). It does seem to be overreaching, but I also maintain that the AGPL has a major loophole as things currently stand. Edit: From the sibling comment, it seems that SSPLv2 tries to address this.
- yarrel 7y agoPlease don't use the (awesome) CC licenses for software - https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software https://creativecommons.org/faq/#can-i-apply-a-creative-comm...
- SpicyLemonZest 7y agoRight, but leadership is needed to coordinate that change. The OSI needs to stand up and say "hey, the widespread use of permissive licenses is a threat to the open source community; please try to avoid them, and here's some ways you can accomplish your goals without a permissive license." Most open source projects aren't monetized, and most monetized projects won't be picked up by Amazon, so without a coordinated push permissive licenses are just the simplest way to go.
- Hello71 7y agothe FSF have been saying that for longer than the OSI has existed. people mocked them for saying that they were idealistic and unreasonable.
- edoceo 7y agoAnd some donate to both. FSF is a big reason we chose GPLv3 - when at first I was thinking MIT.
- SpicyLemonZest 7y agoThe FSF takes the more extreme stance that general adoption just doesn't matter. If big companies ban libraries using their recommended viral licenses, that's not a problem they're looking to solve; it just means the people writing free software will have an advantage.
- tango12 7y agoThis is true. We had to change our license from AGPL to Apache to make sure enterprise adoption was frictionless because there’s often a blanket ban on AGPL. https://news.ycombinator.com/item?id=20064281 https://news.ycombinator.com/item?id=20064281
- karmakaze 7y agoHmm, wonder if there's something we can take away from this. Let's say the latest major release is AGPL (or newer dominant copyleft) and the previous major release is more enterprise friendly licensed with those offering paid support handling the security and maintenance of them. This means that the community can continue to develop and use the latest and greatest. Not perfect but it might work in some cases.
- galaxyLogic 7y agoSounds like an interesting idea. How about taking it even further and say what you say above but then also provide the latest and greatest release also as a commercial version. Then companies who want the latest will pay for it and OS community gets the latest with AGPL, while companies who prefer MIT license get a version that works but is not the latest or greatest. That would be much like paying for support, getting the latest and greatest earlier than those who don't pay for it.
- karmakaze 7y agoI wondered about combining it with dual licensing, but I don't even know how people do that today. Say if a whole community contributed to an AGPL project and it has a dual commercial license, who controls and profits from it?
- galaxyLogic 7y agoMaybe all (registered) contributors would have to sign agreement that they give rights to publish also with commercial license to the corporation or non-profit that is in charge of the distribution. Would they be willing to do so? Well maybe they should get a cut of the profits. That gets complicated managing all the payments, but I can see a single company using this model for their own benefit. Build momentum with the (two) OS licenses and get some income from the commercial license. What could make this an attractive simple-to-manage model is that there would still be just one product, with different time-based releases of it, provided with a different license. No need to fix bugs in the older releases, they are fixed in later versions. And everybody gets the fixes eventually but those who pay (or agree to AGPL) get them sooner.
- jandrewrogers 7y agoMost companies use open source because the permissiveness gives them optionality that they value highly, and will even invest resources in supporting, but don't expect to exercise in most cases. If you eliminate that optionality (e.g. AGPL) then it erodes the value proposition of open source for companies and thus their interest in supporting it. This is the reason many companies will not touch AGPL, it eliminates most of the value they expected to get from the transaction. And without company support, open source development would languish. This is the challenge, and it doesn't have an easy answer. Without optionality, open source offers little to corporate users.
- karmakaze 7y ago> eliminates most of the value Is this really true or just perceived? How often is that optionality actually exercised? And I don't believe that most of the value is in it. The benefits to using good software that continues to be maintained by those using or supporting it is immediate.
- bartread 7y agoDual-licensing is an option too: you can either have AGPL or pay for some other license that allows commercial use without the need to open source everything else.