Saturday, January 23, 2010

Saying Goodbye to Google Code


Just when I thought I had found a single provider for 90% of my net needs I could be happy with, I came across the following thread:

Particularly this...

"Basically the answer is when I, Fitz, Greg or the team think it is
popular enough. I know you guys think we don't like it for nefarious
reasons, but what you're missing is we dislike -all- new licenses that
are unpopular. They lead to bifurcation of the open source development
world and that is a high price to pay.

I personally think the AGPL is deeply flawed, and I've commented on
that on my own blog and on others, but that really -doesn't- matter.
If the AGPL gets to be popular, like lgpl or bsd popular, than we'll
certainly offer it as an option on, "

The other posters go on to show that AGPL is used on a great many sites and ask how many it takes to pass the "popular" test ... and "Chris" just stops answering.

Now GoogleCode is supposed to be a community site, but here is a google-person stating that a license has to meet *his* particular standards or they won't allow community members to use it

Now I don't know who Chris is, For all I know, he could be a Google founder, but I don't really care. The point of community is not to arm-twist everyone else into doing what you individually want. The idea that google finds such an attitude acceptable has to make me seriously rethink just how google-dependant I really want to become.

As for my AGPL project, I guess I'm headed back to SourceForge who use the yardstick that, if its recognized by OSI, its an okay license. Frankly, I've never been thrilled with OSI either, but its a better yardstick then Google's.

No comments: