bbgm - the discussion - Latest Comments in Google Code as a science repository

Re: Google Code as a science repository

pansapiens — Thu, 22 May 2008 20:01:42 -0000

It's amazing how the little differences in the interfaces between say, Google Code and Sourceforge seem to make participation easier. They essentially have similar features, and yet one always feels a whole lot more usable than the other. There are a lot of dead (or still-born) projects on Sourceforge, and I'm sure part of the reason is the messy setup for comments/bug tracking/documentation etc. It just doesn't seem as slick and easy to get an overview of what is going on in a Sourceforge project compared with one in Google Code (or Trac). I think we will see more tech-savvy (and hopefully the not-so-savvy) scientists realizing how nicely some projects can be managed this way and jumping on board in the future.

Ever since Neil wrote about setting up Trac + SVN to manage bioinformatics projects, I've been managing a few internal projects this way and it works great. Some of these will probably move to Google Code when I've cleaned them up for pubic consumption, but I really should get into the habit of just starting these out 'in the cloud' to begin with.

Re: Google Code as a science repository

mndoci — Thu, 22 May 2008 14:06:21 -0000

Matt

Thanks for posting the link. Can't wait for Disqus/FF to integrate those back into the blog. It's inevitable and Danial Ha mentioned they were working on that

Re: Google Code as a science repository

mza — Thu, 22 May 2008 13:43:51 -0000

Some good comments over on FF: http://friendfeed.com/e/c61...

Re: Google Code as a science repository

pedrobeltrao — Thu, 22 May 2008 13:29:42 -0000

That reminds me that I still did not make time to push on that open project ... hopefully when I get one project done in the new lab I will have an easier time convincing the boss that this is OK.