I'm fine with moving to Git. When you say it will start with Maven 3.x, what
does that include? Will all the trunks switch over or just components/trunk to
start with?
Jason van Zyl wrote:
Hi,
Maven was the first project at Apache to use JIRA and though there was a
great deal of concern/noise about using JIRA it ultimately proved to be
a decent system and now lots of projects are using JIRA.
I'm not particularly interested in mandating everything in Maven to use
GIT but I would like to pilot the use of GIT as the canonical repository
for Maven 3.x and wanted to see what others thought.
I believe that GIT is going to be the dominant SCM in the very near
future because the distributed nature is so much more inline with the
way OSS should work. Anyone can get a complete copy of our work and it
is much easier to absorb those changes. There are many examples now on
the net demonstrating projects that have switched to GIT and their
communities have flourished as a result.
We are also seeing the rise of Java implementations of GIT and to me
this means there are going to be an order of magnitude more developers
able to work on the core system. JGIT, which is being developed
primarily by Shawn Pearce @ Google, is awesome. I actually have been
participating in helping with the build for JGIT and I've been working
with Peter Royal to create a MINA SSHD wrapper around JGIT using
JSecurity for authentication and it's so easy. Peter cranked out a
working prototype in 3 hours. This simply is not possible with C-based
systems like Subversion which is essentially a closed box or generally
uninteresting to Java developers. JGIT along with Gerrit (an awesome
code review tool Shawn Pearce is working on) is being used by the Google
Android team and it's working well (I'm meeting with Shawn Pearce today
to chat) so I think we have evidence this works.
I'd be happy if everyone here wanted to use GIT but I do believe that I
have a better chance of getting people involved with Maven 3.x if I can
get the canonical repository in GIT.
In the Maven project we set precedent with JIRA and now I would like to
do that with GIT.
If Apache Infrastructure doesn't want to support this then I feel we can
do the same thing we did with JIRA until they catch up. I think having a
canonical repository at Github is safe, well backed up and maintained
and I don't think we would have to worry about anything there. They have
full-time staff and a slew of engineers so I would even argue that a
repository at Github would be just as safe and well maintained as a
Subversion repository here.
Any thoughts?
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
