What do we want to add to RubyForge (was: RubyForge in Ruby?

Ruby
#1

Folks,

I started this thread… please let me take a shot at summarizing
people’s
points:

  • Rewriting GForge in Ruby for RubyForge is a waste of time and a
    religious persuit because it splits the development of an existing,
    well
    supported product in two and that’s not good for a bunch of well
    stated
    reasons.
  • 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?

So…

Please send me a list of things people want to add to RubyForge. I’ll
do
the following:

  • 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
    Rails
    app (or a series of Rails apps) on the ‘side’ of GForge so that if we
    add,
    for example, Ruport based reporting or Trac-style issue tracking, how
    hard
    the actual process of integrating that with a GForge single sign-on
    would be
    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
    would
    be to add these features beside GForge” lists.

So, you all, please send me your wish list publicly or privately.

Thanks,

David

#2

Darcs support.

#3

David P. wrote:

we add,
for example, Ruport based reporting or Trac-style issue tracking,
how hard
the actual process of integrating that with a GForge single sign-on
would be
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 would
    be to add these features beside GForge” lists.

So, you all, please send me your wish list publicly or privately.
I guess I’ll take a look at RubyForge, list all the things I’m not
likely to use with any of my 1-5 person projects, and give you my top
ten list of things that I’d like to see removed. Although, when all is
said and – undone – the end result is likely to resemble, for some
strange reason, BaseCamp.

–
M. Edward (Ed) Borasky

http://linuxcapacityplanning.com

#4

On 6/24/06, David P. [email protected] wrote:

Folks,

Please send me a list of things people want to add to RubyForge.

  • Ugly interface of RubyForge. The “tabs” browsing at the top has to go,
    especially how clicking “Home” will take you out of the current project
    you
    are browsing completely and put you on the home page for the site, not
    the
    home page for the project.
  • Search on RubyForge is terrible. Searching ‘software/group’ is very
    limited. It’d be nice if that searched a wider variety of information
    than
    just the title and description of projects
  • Automatic RDOC of source code checked in, possibly even used as the
    "default’ project page. A much better default than “Coming soon!”
  • What is the Trove software map? I’ve never seen anything categorize
    itself. Is it useful?
  • Search drop down changes its options when you browse into a project,
    versus when you are on the home page for ruby forge. Confusing.
  • If you have to log in while entering a new issue, forum post, etc. the
    site should remember where you were and what you had typed prior to
    login.
  • As others have said, a clearer means for releasing ruby gems.

Thanks for taking the time to gather this info, and good luck with the
project!

Justin

#5

On Sun, 2006-06-25 at 09:37 +0900, [email protected] wrote:

Darcs support.

git also.

-mental

#6

On 6/28/06, MenTaLguY [email protected] wrote:

On Sun, 2006-06-25 at 09:37 +0900, [email protected] wrote:

Darcs support.

git also.

-mental

+1

Michal

#7

“Michal S.” [email protected] writes:

On 6/28/06, MenTaLguY [email protected] wrote:

On Sun, 2006-06-25 at 09:37 +0900, removed_email_ad[email protected] wrote:

Darcs support.

git also.

-mental

+1

Providing the git server probably won’t be easy in on a server with
lots of users, but if rsync was possible, darcs and git (and
mercurial, and bzr) could be done easily, at least for pulling.
(Usually, you want the pushable core repository locally anyway.)