From: Uma Geller <umageller@...>
Date: 2006-12-22T04:45:59+09:00
Subject: Re: Ruby's Trac Alternative

> So I'm trying to use Trac for our FUN3D development,
> as an experiment for a potential NASA-wide installation,
> but Trac is not the easiest thing to get setup.  Lately,
> I've even had to hack some of the Python internals to
> get syntax highlighting working via enscript.

For the Python-clueless in me, it wasn't easy to set-up Trac.
But after the initial pain things went rather smoothly.

I agree the ideal situation would be one were we could hack and add
qualities to the tool  (I'm always finding names for things, Rutrac,
Tracby ?) but it seems so far, the quality of Trac has largely
outweighed the pain of being subject to Python.

Is it the main reason for a port would be to eliminate the pain of
hacking in Python, or is it something else we would be able to do with
Ruby that is (near) impossible with Python ?

A lady will always prefer gems to snakes, of course, but I'm trying to
find out whether there are powerful reasons to port Trac so that the
Ruby community would be willing to throw its weight behind.
Otherwise, solo efforts may not be the best idea for this kind effort
with little or no noticeable reward.
(in the end you will just have something that looks and smells like
Trac, only with Ruby inside)

best,
                        UG
---
Uma Geller
http://umageller.wordpress.com