On Jan 8, 6:23 ¨Âí¬ Ôòáî¼ôòáîóæ®®®Àçíáéì®ãïí÷òïôåº
> On Jan 7, 8:16 ¨Âí¬ ÔéáçÎïçõåéòá ¼ôêîïçõå®®®Àïïíáóôåò®ãïí÷òïôåº
>
> > Daniel Berger escreveu:
>
> > > On Jan 7, 2:10 pm, Trans <transf... / gmail.com> wrote:
>
> > > <snip>
>
> > >> To me GForge seems very dated. I think GitHub is much better example
> > >> of the future. It has most of the features developers need.
>
> > > I don't see a way to submit bugs.
> > > I don't see forums.
> > > I don't see mailing lists.
> > > I don't see a way to broadcast announcements.
> > > I don't see download stats.
> > > I don't see a way to monitor what new Ruby projects have been created.
> > > I don't see a way to logically group different, but related, libraries
> > > together.
> > > I don't see a way to attach external documents.
> > > I don't see a way to track all of the bugs and feature requests I've
> > > submitted on other projects.
> > > I don't see a place to paste code snippets.
>
> > > Github, an example of the future? The future isn't all it's cracked up
> > > to be apparently.
>
> Dan, I think you over value some of these features -- download stats
> on Rubyforge aren't very accurate

Except for a few projects that have either inadvertently or
intentionally pumped their own download stats, they're fairly
accurate. I track the download stats, so I can trend out the projects.

> announcements would be better handled by a dedicated mailing list

An RSS feed is even better. You can already do this for news on
individual projects. I've asked Tom about a site-wide RSS feed for
news announcements.

> and why attach external documents
> when we can just add them to our repos?

Because I don't necessarily want to download them. I may just want to
view them.

> Also, GitHub does have code
> snippets.

Ok, cool.

> Yes, some additional features would be nice. But I see no reason why
> they eventually can't be added -- I'm sure the GitHub folks have plans
> for the future too.

But if RF already has the features, why switch to github? And Redmine
has an even richer feature set.

> In any case, I don't think it's a good idea to think in terms of
> shutting the original Rubyforge down and starting Rubyforge2 up,
> rather I think it would be better to make a smooth transition. Let
> people move over at their leisure. The first adopters can be the ones
> who are okay with the more limited feature set.

In terms of rubyforge -> rubyforge2, I think a 3-5 year transition
would be fairly smooth. If you're referring to github, people will
transition, or not, at their leisure.

Regards,

Dan