On 23-Apr-09, at 5:33 PM, Daniel Kulp wrote:
Personally, I'm +0 on the idea moving to git. I really don't care
one way
or the other if its svn or git.
However, I'm -1 to anything that involves pulling the code outside
of the ASF
unless it would get the "blessing" from infrastructure and/or the
board. If
you want to invest some time/resources in helping them figure out
what to do,
donate a machine to host the repos, whatever, I'm fine with that.
Knock
yourself out. But until that is done and the repos can be safely
hosted here
(or the board OK's endorsing stuff at GitHub), then I'm -1.
Honestly, I REALLY don't like the fact that much of the maven stuff
is already
not in ASF (confluence and jira). I am honestly amazed that the
board hasn't
pushed that issue.
It wasn't supported at the time, I pushed the envelope and as a result
JIRA and Confluence are available at Apache. No one would buck the
status quo and not being able to use good tools because no one wanted
to help or provide the infrastructure wasn't a good enough reason to
me. And no, I didn't want to argue ad nauseam the merits of using JIRA
and Confluence. Apparently, according to many of the infrastructure
folks Confluence and JIRA have not been successful because no one
maintains them.
I'm tired of fighting for the case that we have professionally managed
infrastructure by the likes of Contegix who professionally support
JIRA and Confluence. Plus they would do it for free for Apache.
If Apache Infra wanted to do all the work migrating and testing the
movement of our content from Codehaus to Apache they can be my guest.
If you want to do it feel free.
The board hasn't pushed the issue because someone would actually have
to do the work. Confluence is relatively easy, and JIRA with the next
version should be easier. But historically, migrating a single JIRA
project out of one instance and placing it into another is pretty much
impossible with an Atlassian employee to do it. But we have Jeff here
so maybe he would do it.
If you want to move it off a 24/7 monitored infrastructure, you go for
it. I'm not going to argue with anyone anymore. I think Contegix is
fabulous and they will always be my first choice for a hosted
infrastructure. If you feel so strongly call a vote, migrate the
content, test it and it will be here. Concern resolved.
Dan
On Thu April 23 2009 1:00:36 pm 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
--
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
What matters is not ideas, but the people who have them. Good people
can fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
