8 ms·
Google's Internal AGPL Policy
- gentleman11 7y agoI wish it was easier to monetize free software. I am making an Indy game right now and it is hard enough to make money already with 7k+ games coming out per year (plus, my third party assets don’t have a license that allows redistribution in such a way)
- jldugger 7y ago> I wish it was easier to monetize free software. Well, you might ponder over this line from the policy: > In some cases, we may have alternative licenses available for AGPL licensed code.
- dleslie 7y agoYou can go the classic route that id, raven et al followed: open source the executable but keep the data closed.
- ryukafalz 7y agoGoogle’s allergic to copyleft licenses, so that’s about what I’d expect. But smaller software companies, consider this a sign: want to be FOSS but don’t want the tech giants to swallow your business? Go AGPL, they’ll avoid it like the plague.
- niftich 7y agoInstead, once your product grows popular enough, they'll just offer a managed, hosted service with a compatible API.
- yjftsjthsd-h 7y agoYeah, but they'd do that regardless, so AGPL is the least-sucky option.
- imtringued 7y agoAs long as they contribute their changes back that is perfectly okay.
- ryukafalz 7y agoWell, while the current status of Oracle v. Google (APIs being copyrightable) is a disaster for the software industry, if you can't beat 'em... AGPL APIs, anyone?
- tony 7y ago> want to be FOSS but don’t want the tech giants to swallow your business? I get the aesthetic and sentiment, but in practice this doesn't convey the reality. Having a business link or incorporate your open source software project isn't necessarily bad. At the very least, it's a social proof. There could be sponsorships, patches sent back. There plenty examples of permissively licensed software out there that directly contradict this: FreeBSD for Nintendo Switch and PS4, FreeNAS Django, TypeScript, Jupyter. VSCode. Electron. Python. Ruby. CoreCLR. Windows Terminal. Anyone of these projects, someone could fork it, rename it, repackage it as value added. It doesn't happen since the transaction incentivizes merging contributions upstream - maintaining forked code has passive costs. Pushing it back passes the burden (and also the benefit) of the changes back to the project. > Go AGPL, they’ll avoid it like the plague. I feel when we're thinking about gatekeeping who and uses our software and why, we're not really doing open source anymore. In that case, writing commercial software license from scratch, or based off a permissively licensed project, and not releasing the source is an option.
- djaque 7y agoI license all of my software AGPL and the reason I do it isn't gatekeeping or some theoretical argument about what software is. It's because I have put a large amount of effort into this product and decided to release it for the benefit of the community. I would feel taken advantage of if a company came in and hoarded that software while making a profit off of it and never giving back. The free market is great and all, but it's also OK to just ask that people give you a fair deal when they use your code.
- beefhash 7y ago> and decided to release it for the benefit of the community I don't understand. You're saying “for the benefit of the community”, but then only speak about companies as negative examples. (1) Are companies inherently incapable of being members of the community to you? (2) Are people whose software is more liberally licensed (and may wish to incorporate parts of yours) not part of the community to you?
- 7y ago
- fabianhjr 7y agoI think AGPL is neither clear enough nor restrictive enough. Fortunatly some amazing people have been working on a stronger copyleft license (https://licensezero.com/licenses/parity https://licensezero.com/licenses/parity) and a soft-copyleft non-commercial license (https://licensezero.com/licenses/prosperity https://licensezero.com/licenses/prosperity)
- saagarjha 7y ago> Fortunatly some amazing people have been working on a stronger copyleft license (https://licensezero.com/licenses/parity https://licensezero.com/licenses/parity) How so?
- fabianhjr 7y ago> Contribute software you develop, operate, or analyze with this software, including changes or additions to this software.
- EGreg 7y agoThat’s the advice I got from Stallman’s (or FSF) lawyer. The same guy who inspired Diaspora guys. Forgot his name. In between ranting at me for about an hour he did give me that useful piece of info. The only thing I asked him. Quite a character, that guy.
- kazinator 7y agoIn this case, Google is just being allergic to a non-free license. It's no different from not being allowed to check into Google's monorepo something with an IBM copyright on it, without any wording about free redistribution and use.
- lidHanteyk 7y agoAGPL licensing denotes Free Software. It is too free for Google.
- kazinator 7y agoAGPL carries conditions on the use of the software, not only redistribution. It cannot be called free by any stretch of the imagination; though obviously some people in the GNU project and the FSF feel they have that stretch.
- rstuart4133 7y agoI use the AGPL myself, and over the decades become obvious both it and the GPL have a flaw: they don't define when their most contentious aspect (them being "viral"), is triggered, so most of the time it's a hope and a prayer. I have no doubt Stallman thought the term "derived work" was pretty clear at the time, but the amount of wriggle room it provides in the hands of the wrong people this could be devastating to business. (Think: Oracle trying to stretch the definition of copyright to cover API's.) The occasional rare project does go out of its way to define the demarcation line. For example, the kernel's authors have made it very clear the demarcation line is the user space API, so anything that relies on it is not considered a derived work. I have no doubt that is one of the reasons you find the linux kernel everywhere. But even some top tier GNU projects have similarly clear lines: not only are programs complied with the GCC not considered derived works, programs that statically link the libraries needed by the GCC compiled code are not considered derived either. And so unsurprisingly, using the GCC is not considered dangerous, despite it being GPL. Personally, I'd like to see an [A]GPLv4, that formally defines what is a "derivative work" is or at least provide a list of choices users could include. It could, for example, exclude programs that use output of another when that output is intended to be readable by humans, and it could exclude header files and similar things that define API's. Doing that would remove a lot of the uncertainty about when the GPL is "viral" and when it isn't. As it stands, Google's blanket ban seems like a reasonable response.
- lidHanteyk 7y agoGoogle also recoils from WTFPL, which may make it a more palatable license for folks who don't agree with the AGPL's various quirks and features. Not that AGPL is bad, but WTFPL is quite bare-bones.
- brendyn 7y agoPresumably because using it is terribly reckless. It doesn't even contain a standard disclaimer preventing the user from suing the distributor or copyright holder.
- loeg 7y agoYou want the WTFNMFPL instead: https://tldrlegal.com/license/do-what-the-fuck-you-want-to-but-it's-not-my-fault-public-license-v1-(wtfnmfpl-1.0) https://tldrlegal.com/license/do-what-the-fuck-you-want-to-b...
- tingletech 7y agoI can't find either on this list https://opensource.org/licenses/alphabetical https://opensource.org/licenses/alphabetical
- catalogia 7y agoHas any programmer ever actually been sued after using the WTFPL license? If not, if the threat is theoretical, then I don't think it meets the bar for "terribly reckless."
- verdverm 7y agoThe main reason I don't release with AGPL (and similarly red flagged licenses) is so that corporations can adopt the project.
- bigiain 7y agoThat's a perfectly valid choice. Other people's choice to avoid corporations from adopting the project without giving anything in return is also a perfectly valid choice. (You have a higher chance of having your project become globally used, other people value that less than pull requests and/or money. And that's fine.)
- kazinator 7y agoThe AGPL burdens you with requirements related to simply running the program, even if you're not a money-making corporation. Say you want to put up some wiki or something, for some volunteer organization of yours. If you run some AGPL thing and customize it in any way, you're burdened with having to serve everyone the code. Come on, are you saying that if some corporation uses your program that took ten man-years of effort, and re-distributes the code due to making some trivial one-line change, then they have given something adequate in return? If you don't like corporations using stuff for free, then just put a proper shareware license on it: "free for non-commercial use". The motivation for the AGPL isn't about giving back to the community; it's just a wrongheaded attempt to attack the problems caused by SaaS. Namely, that users are tied to using programs whose installation is on remote equipment they don't control, and whose behaviors are a blackbox.
- bigiain 7y ago> you're burdened with having to serve everyone the code. Yes, if that’s the option the author of the code chose. You are free to choose some other code, or write your own. You have zero entitlement to use somebody else’s code under conditions that suit you, over the wishes of the author. It makes no difference whether the author(s) chose AGPL for reasons you like it not, or if they did it out of philosophical purity or spite. They get to choose. You get to choose whether to use their code or not under the rights and conditions they grant you. Google have clearly worked this out and codified it in their policies. If you think that’s putting some overly heavy burden on you, that doesn’t change anything. Choose some other code or write some yourself. Nobody owes you the right to use their code. Sorry.
- probdist 7y agoThis is how RStudio and certain other great open source tools get bigcos to pay for licenses. They are allergic to AGPL and therefore will happily pay for alternative licenses for tools their employees demand.
- rodgerd 7y agoGoogle: Unless we can get your free labour, we don't want your stuff.
- lflux 7y agoSame thing inside Amazon. GPLv2 on a case-by-base basis, AGPL/GPLv3: don't even ask. BSD/MIT: Go hog wild
- bigiain 7y ago... and if it's got enough mindshare to be worth having, but is AGPL or some other "too restrictive license", just reimplement (probably an old version of) it's APIs from scratch, and use misleading marketing weasel-words to lock in your existing users of other services who aren't paying enough attention. <smirk>
- classics2 7y agoMany viral licenses are just demands for payment by other means. It’s not really surprising to see companies recognizing it and refusing to pay the asking price.
- saagarjha 7y agoYes, the payment is that you must contribute your changes back to the project.
- m463 7y agoDual-licensed code may be distributed with different restrictions to a paying customer.
- gary-kim 7y agoThat's only possible if one entity has the rights to the entire codebase. Personally, almost all my software is released under the AGPL and there is no CLA so it cannot be dual-licensed, which is how I want it.
- yokohummer7 7y ago> Do not attempt to check AGPL-licensed code into google3 What is this "google3" thing? Is this the name of their monorepo?
- saagarjha 7y agoYes.
- thayne 7y ago> any product or service that depends on AGPL-licensed code, or includes anything copied or derived from AGPL-licensed code, may be subject to the virality of the AGPL license I'm not a lawyer, but my understanding of the AGPL was that its virality only applied to changes to the software, or software that was directly linked to it. So if a product A used an AGPL licensed service over the network, that would not require that A also be licensed as AGPL.