I started this thread… please let me take a shot at summarizing
- Rewriting GForge in Ruby for RubyForge is a waste of time and a
religious persuit because it splits the development of an existing,
supported product in two and that’s not good for a bunch of well
- There are things that are less than optimal about GForge, it’d be
nice if these things could be added:
- Publishing gems is not as streamlined as it could be
- It’d be nice to have source browsing
- Certain other features from Trac would be nice
- (my personal comments) It’s clunky to run surveys and there’s
no built-in chat and there’s no iCal integration (e.g., when did
we release stuff, what’s upcoming to do on my calendar, etc.)
- Put your code where your mouth is (I plan to, but I wanted to
understand from others what the upsides and downsides were)
- Did I miss something?
Please send me a list of things people want to add to RubyForge. I’ll
- Aggregate the input items so there’s a list of what people want
- Look at the GForge schema to see how hard it would be to put a
app (or a series of Rails apps) on the ‘side’ of GForge so that if we
for example, Ruport based reporting or Trac-style issue tracking, how
the actual process of integrating that with a GForge single sign-on
and also what the additional burden would be on Tom and Richard.
- On Friday, I’ll publish the “top 10 list” and the “how hard it
be to add these features beside GForge” lists.
So, you all, please send me your wish list publicly or privately.