git, future directions - ESOE Development

Message from discussion git, future directions
Received-SPF: pass (google.com: domain of s.mangelsd...@gmail.com designates 209.85.198.229 as permitted sender) client-ip=209.85.198.229;
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=TL9uhfKs8h9it8MckF+1Z+yv06g2dSrXH6SSJ+jgWCReRFF6ssm4mQEClY9qVp+ZbU
         6cs9YTA7npDcBxfvq6ItvoXjY+XdgIy+VGK+4sOy8QhPhD9tbyViJ93irZhoXbIjqt+m
         LkPdlYgTmb4gq3FfKJPIGP0JQryrRB5Z0I1tM=
MIME-Version: 1.0
In-Reply-To: <BE7C2473-6DC7-4EB3-B9B4-EAC63FEF8A87@gmail.com>
References: <EF21CAFB-258E-4DFB-8986-85981E155D03@intient.com>
	 <BE7C2473-6DC7-4EB3-B9B4-EAC63FEF8A87@gmail.com>
Date: Sun, 1 Mar 2009 17:24:09 +1000
Message-ID: <90ad28f40902282324s1fea9e1aj5ff753acafc15...@mail.gmail.com>
Subject: Re: [esoe-dev] Re: git, future directions
From: Shaun Mangelsdorf <s.mangelsd...@gmail.com>
To: esoe-dev@googlegroups.com
Content-Type: multipart/alternative; boundary=000e0cd295f48b1c690464099692

--000e0cd295f48b1c690464099692
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

>
> 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=85 yep just checked and they still aren't though they
> plan to.


Although I see your point, I think we can find suitable substitutes that
(while not as tightly integrated as the Atlassian suite) will give us what
we need and support git natively.

This might warrant some further investigation. If it turns out that git is
too widely unsupported, we may need to stay with subversion.

It makes sense to me to move this project to Codehaus or even Apache.
> 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.


We'd have to look into the copyright issues surrounding the ownership of th=
e
code. Apache for one requires that the code be owned by the foundation.

Not sure what Codehaus' barrier to entry is like, but on first inspection
they seem to have the Atlassian suite set up, so it's worth considering wha=
t
we want to do for SCM before we decide where to host the project long term.

I am not a hardcore git user so I may not have seen the light yet, but
> 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.


git+svn would be an option if we're stuck and can't find the necessary
tools, but I think a move to git would be good for the project as a whole.
Git's branching and merging features (among others) are second to none in m=
y
experience; and there are a great deal of features which will benefit a
project under distributed development, as ESOE is and will undoubtedly
continue to be.

Keen to hear more thoughts on this.

Shaun

--000e0cd295f48b1c690464099692
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"borde=
r-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-le=
ft: 1ex;"><div>
</div>No argument from me. The only thing I would be concerned about is<br>
making sure that the tooling supports it. The project needs continuous<br>
integration and a repository inspector, and ideally an issue tracker<br>
linked into both of these. I have used the Atlassian tool set to do<br>
this in the past which works well, but I don&#39;t think they are<br>
supporting git yet=85 yep just checked and they still aren&#39;t though the=
y<br>
plan to.</blockquote><div><br>Although I see your point, I think we can fin=
d suitable substitutes that (while not as tightly integrated as the Atlassi=
an suite) will give us what we need and support git natively.<br>
<br>This might warrant some further investigation. If it turns out that git=
 is too widely unsupported, we may need to stay with subversion.<br><br></d=
iv><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(20=
4, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

It makes sense to me to move this project to Codehaus or even Apache.<br>
Although Apache is quite strict on the projects they host so Codehaus<br>
might be a better choice. They have all the tools and admin interfaces<br>
to manage them, not to mention free bandwidth. It also adds a certain<br>
aspect of credibility to the project by having it hosted by a well<br>
known hoster of open source projects. Plus, it allows the developers<br>
to focus on developing rather than installing and configuring software.</bl=
ockquote><div><br>We&#39;d have to look into the copyright issues surroundi=
ng the ownership of the code. Apache for one requires that the code be owne=
d by the foundation.<br>
<br>Not sure what Codehaus&#39; barrier to entry is like, but on first insp=
ection they seem to have the Atlassian suite set up, so it&#39;s worth cons=
idering what we want to do for SCM before we decide where to host the proje=
ct long term.<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid=
 rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I am not a hardcore git user so I may not have seen the light yet, but<br>
I would rather stick with svn because of the support for it from<br>
FishEye and Bamboo for the time being. Individual developers can<br>
always use git+svn locally to get _some_ of the features.</blockquote><div>=
<br>git+svn would be an option if we&#39;re stuck and can&#39;t find the
necessary tools, but I think a move to git would be good for the
project as a whole. Git&#39;s branching and merging features (among others)=
 are second to none
in my experience; and there are a great deal of features which will
benefit a project under distributed development, as ESOE is and will undoub=
tedly
continue to be.<br><br>Keen to hear more thoughts on this.<br><br>Shaun<br>=
</div></div><br>

--000e0cd295f48b1c690464099692--