So Google detests the AGPL license: https://opensource.google.com/docs/using/agpl-policy/ going as far as to demand this:
"Do not install AGPL-licensed programs on your workstation, Google-issued laptop, or Google-issued phone without explicit authorization from the Open Source Programs Office."
So to degooglify the internet everyone should choose AGPL for open source projects :)
My understanding is that it is just a GPLv3 apart from counting "interactions over network" the same as disturbing binaries when it comes to requiring distribution of sources.
So it could be mildly inconvenient to have to publish your local patches to your AGPL irc/mail/foo client, but no real showstopper.
Personally I am mostly involved with server stuff anyway, and there AGPL is a very good default choice.
@ralph with GPL (for example) you can take some code, modify it and run it on a server without making the changes available. AGPL doesn't allow this. since Google is running loads of modified open source server software without making the changes available, AGPL is often against their business interests. another issue is is probably that Googlers who are ignorant of what AGPL software requires could get Google into lots of trouble.
@steckerhalter actually, that's likely to have the opposite effect as desired: those of us in the company who continually push for open source engangement have our argument made harder when base libraries are AGPL. So far, that's been rare. But, when it comes up, it's painful enough that we tend to reimplement whatever the component is. That's bad for everyone.
No one can argue that Google--so far--hasn't contributed to open source project is big ways.
@jasondclinton maybe. btw, "degoolify" is used as a term (AFAIK) to denote the effort to transition to the #openweb and move away from corporations in general, not just Google. To hinder these corporations from being able to use open source software could have positive effects. They would increasingly work in their silos and their influence on open source software would dwindle. Meanwhile the open source projects could flourish apart from business interests of big corporations.
@jasondclinton @steckerhalter the problem is that google ALSO has restrictions on using GPL-based in any way that would require them to comply with the licenses. the only difference between GPL and AGPL is that google primarily distributes code over the network so their policies are written with that in mind.
techpol Show more
@steckerhalter there are others too it hates
keep in mind if EVERYBODY does it all at once they're going to start trying to find legal arguments to weaken it somehow, and they have an army of flesh eating lawyers
so start with things you DEFINITELY don't want them near -- your ML stuff, NLP stuff, most important projects of yours first
pick your defenses, let it happen as the tide would come in -- if it's a tsunami they'll decide it's worth attacking properly, I fear
I don't think they're going to this coming week, but that's going to be a question of access
if they find they've got less and less access to open software, they will
but maybe by then enough important open software will be out that getting their way in court will be harder and harder
a girl can dream