Rubyforge => Redmine

I

Intransition

Hi all -

Me and some other folks are looking into switching RubyForge over to use =
Redmine. =A0If you'd like to help, the migration script is underway here:

Err... woozahhh

I thought you guys were "moving on". I am very surprised to see you
are actually converting Rubyforge from PHP to Ruby. Is this in
production?

So it the Redmine just a issues? Or more than that?

I posted about it before, but I fell Rubyforge would do well to become
a "dashboard" app withsplugins for managing various services related
to their projects whether internal or external.
 
L

Luis Lavena

Hi all -

Me and some other folks are looking into switching RubyForge over to use Redmine.  If you'd like to help, the migration script is underway here:

http://github.com/rubycentral/rubyforge

Or if you think this is a terrible idea, please speak now...

I just wonder what is going to happen with file hosting.

I'm fine with a modernized structure, but want to know what to expect
to be able to better plan RubyInstaller and other projects tracking
needs.
 
T

Tom Copeland

use Redmine. If you'd like to help, the migration script is underway =
here:
=20
Err... woozahhh
=20
I thought you guys were "moving on". I am very surprised to see you
are actually converting Rubyforge from PHP to Ruby. Is this in
production?

It is not... we must first code up a migration script and port various =
cronjobs and what have you.
=20
So it the Redmine just a issues? Or more than that?

It does lots, and the bits it doesn't do we'll write.
=20
I posted about it before, but I fell Rubyforge would do well to become
a "dashboard" app withsplugins for managing various services related
to their projects whether internal or external.

Yup, we probably need something like "the code is over here on github" =
as an SCM option.

Yours,

Tom
 
T

Tom Copeland

use Redmine. If you'd like to help, the migration script is underway =
here:
=20
I just wonder what is going to happen with file hosting.
=20
I'm fine with a modernized structure, but want to know what to expect
to be able to better plan RubyInstaller and other projects tracking
needs.

We'll still do file hosting... but gems will definitely stay with =
gemcutter (i.e., rubygems.org).

Yours,

Tom
 
T

Tom Copeland

=20
No:
=20
http://www.redmine.org/
=20
But the question is not that, is what would happen with file being
hosted there, the package model do not fit the old RubyForge one.

True, yup, Redmine has a files tab but I think it's pretty much a linear =
list.=20

How much of the RubyForge Package/Release/File structure do you think we =
need?

Thanks,

Tom
 
C

Caleb Clausen

True, yup, Redmine has a files tab but I think it's pretty much a linear
list.

How much of the RubyForge Package/Release/File structure do you think we
need?

Personally, I don't see much point to having rubyforge model releases.
A separate directory for each package is clearly needed, but I just
want a place to dump my tarballs. Having to 'create a release' each
time I do that is (a little bit of) extra work. The 'release' of a
file is implicitly stored in the file's name anyway.

While we're on the subject, it would be extremely nice if the urls to
files were friendlier. Something like
http://rubyforge.org/<packagename>/<filename> is what I would like to
see, rather than the current scheme which involves numbers in the url
as I recall. (OTOH, files currently on rubyforge might need to keep
their current urls as well, otherwise you risk breaking external
links...)
 
L

Luis Lavena

True, yup, Redmine has a files tab but I think it's pretty much a linear list.

Linear works for me. I'm worried that file releases for RubyInstaller,
tar files for projects like SQLite3-Ruby and others are lost.

Just that.
How much of the RubyForge Package/Release/File structure do you think we need?

RubyForge release cycle is overkill, that one of the reasons I think
gemcutter make gem releases blossom, it lowered the release barrier.

Thanks to you man.
 
T

Tom Copeland

=20
Personally, I don't see much point to having rubyforge model releases.
A separate directory for each package is clearly needed, but I just
want a place to dump my tarballs. Having to 'create a release' each
time I do that is (a little bit of) extra work. The 'release' of a
file is implicitly stored in the file's name anyway.

Hm, interesting, yeah, seems like the date and filename =
(foobar-1.2.3.tar.gz) gets you most of the way there.
=20
While we're on the subject, it would be extremely nice if the urls to
files were friendlier. Something like
http://rubyforge.org/<packagename>/<filename> is what I would like to
see, rather than the current scheme which involves numbers in the url
as I recall. (OTOH, files currently on rubyforge might need to keep
their current urls as well, otherwise you risk breaking external
links...)

Cool, yup, I think Redmine generates reasonable URLs for files. =20

For external links, maybe we can generate a huge rewritemap... hm, or =
have a custom route that looks things up by "old_frs_file_id"... well, =
lots of possibilties, but yup, it would be good to keep those external =
links working.

Yours,

Tom
 
T

Tom Copeland

=20
Linear works for me. I'm worried that file releases for RubyInstaller,
tar files for projects like SQLite3-Ruby and others are lost.
=20
Just that.

Cool. No worries, yup, we'll keep all that data (and the files) in some =
form.
RubyForge release cycle is overkill, that one of the reasons I think
gemcutter make gem releases blossom, it lowered the release barrier.

Excellent, so sounds like a lighter release mechanism is a good thing... =
glad to hear it....

Yours,

Tom
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,744
Messages
2,569,484
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top