Moving to Google Code, even though sometimes Google is terrible

Kenai is being closed, so I'm moving all my projects to Google Code for the Mercurial source repositories and Google Groups for the mailing lists. To provide a complete information that can be helpful for others, I fortunately have my own instance of Jira - one of the biggest losses when leaving Kenai - with the exception of BetterBeansBinding, that I don't want to bind to Tidalwave; and I'll probably use the SonaType free hosting for Maven repositories. I have still to figure out where to publish media (screenshots and screencasts) and the javadocs. Google Code is popular and creating a project is easy - I'm periodically forced to stop for one day because of a protection against misuse - I actually understand that it's not a common thing that the same person creates a dozen projects at the same time. There's a worse annoyance with Google Groups - I'm getting the message "You may not create any more groups at this time. Please try again later." since two days and I've still to create a good bunch of them - but eventually I'll be over. What I find Google is a real disaster is support - I mean, when you need to do something outside of the automated flow. For instance, I've discovered that Google is very kind to SourceForge: it doesn't allow you to create a project which already exists with the same name at SourceForge (*), unless you get the explicit approval ...

Date: February, 03 2010
Url: http://www.java.net/blog/fabriziogiudici/archive/2010/02/03/moving-google-code-even-though-sometimes-google-terrible

Others News