We moved the code repository of Clipperz’s open source projects from Google Code to SourceForge, because Google doesn’t like AGPL and is kindly requesting all developers that opted for this license to leave.
It is also not okay to host an AGPL covered program on code.google.com […] So sadly, the answer is to remove your project and host somewhere else like SF or Savannah.
Chris DiBona, the Open Source Programs Manager at Google on Google Groups
Ok, message received! But why is Google against AGPL? Just to stop the proliferation of open source licenses? Noble cause, but are we sure that this strong position is not related to AGPL closing the “ASP loophole”? Russel Beattie has little doubts:
Makes perfect sense, really. Google has made bazillions of dollars using free software in their backend without having to release any of their modifications back into the world. Something like the AGPL which requires server-side modifications to also be released is a direct threat to their way of doing business. Refusing to add AGPL to the list of open source licenses on Google Code to help promote is unsurprising, and in fact expected.
However, I’m sure that AGPL will be adopted by tons of projects going forward. I see no chances for Google to stop or delay this trend. If they don’t want us, they don’t deserve us.
Google Code is a great hosting service and we really enjoyed it while it lasted. I will miss its clean and ad-free interface. Adieu!
All Clipperz’s open source projects are now hosted on SourceFourge. The Community Edition of our password manager is available for downloads here, while the Javascript Crypto Library can be found here.
(another brilliant gapingvoid cartoon)
Delicious
Digg
Reddit
Facebook
Yahoo
Netscape
StumbleUpon
how sad… but nvm, we will
how sad… but nvm, we will have svn in sf ;)
Actually, google releases almost all of it back
Saying things and quoting things like this just proves that you don’t bother to look around or even check sources. Google releases almost all their free software modifications back, they just don’t issue press releases about it like other companies.
Re: Actually, google releases almost all of it back
Releasing some, or even most, of the “marginal” projects as open source is not a problem.
Being legally forced to release ALL the code based on open source projects of the core stuff used internally would have a very different impact on their business.
Double Standards
It simply reflects Google’s double standard attitude. Shame google shame!
Asshole
Chris DiBona seems to be a real asshole too, being rude at an employee for just asking an innocent question.
Agree
I’m amazed that Chris DiBona gets away with comments like this:
“No need for the lecture, I submitted the gpl to osi myself and I understand the politics. It’s easy to get worked up with this stuff, but this is also incredibly unproductive for GPL/AGPL proejcts to take this approach to other open source licenses as tehre is a -lot- of code under apache and bsd that can and has enrich gpl/agpl projects.”
and:
“You need me to disambiguate for you? I think you need to go find my employment documents and find out where it says I work for you.
Chris”
Sounds evil to me.
Milking the GNU: Google to users
Nice post on the same argument (via Fabrizio Capobianco)
Post new comment