[Hecl-devel] Infrastructure
Brought to you by:
davidw
From: David W. <dav...@gm...> - 2009-08-18 09:10:15
|
Hi, I have been thinking a bit about infrastructure for Hecl since my last post regarding svn and git. I am thinking that it's nearly time to do a bit of housecleaning. Some possibilities: * Google Code * github * Other? These relate to the following services: * version control: svn and git are the two candidates here. git can import the entire svn history, which I don't want to lose. I'm not sure if google code can do this... a quick search shows that it's *possible*, but potentially a pain in the neck. git is a bit harder to use from windows. Actually, we could also consider Mercurial, as that's available on Google Code, but I have already invested some time in git, and it seems 'good enough'. * bug tracking: both github and google code have this. google code's looks simpler and cleaner, and everyone has a gmail account, whereas not everyone has a github account. * mailing list. Google Groups is definitely the way to go here. It's a nice, clean interface that is much easier to admin and sign up for than the SF mailing list. You can choose to interact with it like a web forum, or as a mailing list. It would be possible to export the current user list and reimport it in a Google Group. Other stuff? I hate SF's file release system, and love the idea of having 'nightly builds' available from Github. A 'marketing' consideration is that github is new and popular, whereas SF has an old/tired/ugly image, and while that's not worth the disruption by itself, it is a consideration. Thoughts? Questions? -- David N. Welton http://www.welton.it/davidw/ http://www.dedasys.com/ Sent from Padua, Veneto, Italy |