|
|
ESOE Development |
On 26/02/2009, at 6:22 PM, Bradley Beddoes wrote: It makes sense to me to move this project to Codehaus or even Apache. I am not a hardcore git user so I may not have seen the light yet, but
> I'd like to get others input on moving ESOE code bases to GIT backed No argument from me. The only thing I would be concerned about is
making sure that the tooling supports it. The project needs continuous
integration and a repository inspector, and ideally an issue tracker
linked into both of these. I have used the Atlassian tool set to do
this in the past which works well, but I don't think they are
supporting git yet… yep just checked and they still aren't though they
plan to.
Although Apache is quite strict on the projects they host so Codehaus
might be a better choice. They have all the tools and admin interfaces
to manage them, not to mention free bandwidth. It also adds a certain
aspect of credibility to the project by having it hosted by a well
known hoster of open source projects. Plus, it allows the developers
to focus on developing rather than installing and configuring software.
I would rather stick with svn because of the support for it from
FishEye and Bamboo for the time being. Individual developers can
always use git+svn locally to get _some_ of the features.