I actually got my RMagick4J project already moved over to Google (and
renamed it along the way). It was awkward to share the SVN repo (as in,
made history tracking and so on a bit more awkward). And I was having
svn weirdness with Subversive, too. The bug tracker and wiki also seem
nice at Google.
I was figuring I'd just use RubyForge for releasing gems.
But maybe Codehaus would clear up my concerns, too. If it seems
reasonable, maybe I could move over there. I just don't see a strong
need to keep the diverse group of projects together.
- Tom
Ryan Bell wrote:
+1. Moving it all to Codehaus makes my life easier :)
Having all the issues in one place will be also be good.
On 4/23/07, *Chris Nelson* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
+1 on moving to Codehaus. In addition to the above reasons, Xircles
is a Rails app :)
My guess is the bug tracker at rubyforge is so heinous few if any
people bothered to use it. You could probably just move to JIRA and
not worry about migrating old issues. And I would say move
everything
at once if possible. Having gone thru moving Trails from Java.net
<http://Java.net> to
Codehaus, if you move piecemeal it's just a lot messier, IMHO.
On 4/23/07, Thomas E Enebo < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> Sounds good to me...Easier to use one system for me. I also
like Jira
> a hell of a lot more.
> We already have infrastructure to add developers who have access to
> branches (which I guess can be used for jruby-extra projects as
well).
> That is how voegle is added.
>
> -Tom
>
> On 4/23/07, Charles Oliver Nutter < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> > Given that:
> >
> > - rubyforge is a little unreliable
> > - rubyforge svn doesn't support http access to svn
> > - gforge bug tracker is garbage
> >
> > I would propose that we move jruby-extras development stuff to
Codehaus.
> > The source would live in the JRuby contrib repository, so it
would still
> > be separate. All of you who are committers now would be
committers
> > there, as well as having access to JRuby JIRA to update bugs.
We would
> > add submodules under JRuby for the various JRuby-extras projects.
> >
> > Any concerns about this idea? Better ideas? Do we just want to
start
> > using JIRA for all jruby-extras bugs? Incrementally try moving
pieces
> > over there?
> >
> > - Charlie
> > _______________________________________________
> > Jruby-extras-devel mailing list
> > [email protected]
<mailto:[email protected]>
> > http://rubyforge.org/mailman/listinfo/jruby-extras-devel
<http://rubyforge.org/mailman/listinfo/jruby-extras-devel>
> >
>
>
> --
> Blog: http://www.bloglines.com/blog/ThomasEEnebo
> Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ,
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> _______________________________________________
> Jruby-extras-devel mailing list
> [email protected]
<mailto:[email protected]>
> http://rubyforge.org/mailman/listinfo/jruby-extras-devel
>
_______________________________________________
Jruby-extras-devel mailing list
[email protected]
<mailto:[email protected]>
http://rubyforge.org/mailman/listinfo/jruby-extras-devel
--
Ryan L. Bell
http://kofno.wordpress.com
http://kofno.blogspot.com
------------------------------------------------------------------------
_______________________________________________
Jruby-extras-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/jruby-extras-devel
_______________________________________________
Jruby-extras-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/jruby-extras-devel
