Forum: Rails Engines Engines on the move....

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
05d703f649ef1d07e78d7b479fb4c4ac?d=identicon&s=25 James Adam (Guest)
on 2006-02-28 16:23
(Received via mailing list)
Hi all,

In the next few days or so, the engines SVN repository is going to be
moving from the (excellent) opensvn hosts to their own server,
http://dev.rails-engines.org/svn/. The repository is mirrored there at
the moment, but eventually this will become the primary location for
development, and where 'script/plugin' will download from. There's no
need to switch your copies quite yet, however, I'll post again when
the 'official' switch happens.

What I would like to know is if anyone has any preferences over the
bug tracking software we use. I have both Trac and Collaboa running at
the moment, and I'm leaning towards Collaboa, purely in terms of
hackability given it's written in Ruby. However, if anyone can make a
strong case for either, I'd definitely like to know.

- James

--
* J *
  ~
98b3b41b2fa030c78579d8e693acf447?d=identicon&s=25 Mauro Cicio (maurocicio)
on 2006-02-28 16:30
(Received via mailing list)
I vote for Collaboa for hackability reasons.

Mauro
Cb610750ee94ca103aef4b2dc7b1b768?d=identicon&s=25 Nick Stuart (Guest)
on 2006-02-28 16:51
(Received via mailing list)
No preference really here James. I will say I haven't been a big fan
of trac for the little bit that I've used it. It just doesn't seem to
'work' in the whole scheme of things. But, I've never used Collaboa
either so I'm not sure if its really any better (in my view).

-Nick
05d703f649ef1d07e78d7b479fb4c4ac?d=identicon&s=25 James Adam (Guest)
on 2006-02-28 16:54
(Received via mailing list)
If you can be a bit more specific about it not 'working', we might be
able to see about the suitability of Collaboa - which, incidentally,
models itself on Trac quite heavily in terms of the fundamental
entities and so on.

Maybe you can suggest something else?

- james

On 2/28/06, Nick Stuart <nicholas.stuart@gmail.com> wrote:
>
--
* J *
  ~
Cb610750ee94ca103aef4b2dc7b1b768?d=identicon&s=25 Nick Stuart (Guest)
on 2006-02-28 17:22
(Received via mailing list)
I don't if I'm a good canidate to give a detailed description on its
issues as I haven't used it enough. I'm most familiar with bugzilla
(go figure) and JIRA for other projects I've used.  With JIRA being
the one I actually prefered over bugzilla. Maybe once I get using
either of these systems I'll come around (maybe).

If anything I would say collaboa if its based of trac for the reason
being that its done in ruby. Trac is done in python correct?

-Nick
00e3a96684ab390a350b0271e98741d3?d=identicon&s=25 Nshbrown Nshbrown (nshb)
on 2006-03-01 01:58
(Received via mailing list)
+1 for Collaboa. The interface just look so much nicer :)

-Nb

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Nathaniel S. H. Brown                           http://nshb.net
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
D046cca1a33655b6285065ec89711389?d=identicon&s=25 Lance Ball (Guest)
on 2006-03-01 18:10
(Received via mailing list)
I also prefer Collaboa as it is just much simpler, cleaner and easier to
use.

The two big things that trac has going for it are the wiki and reports.
But
with with the existing wiki at rails-engines.org that's less of an
issue.
And the filters on the "Tickets" page does a nice job of dealing with
data
in the way that trac reports do.

Simplicity, to me, is always preferable if you get everything you really
need.

Lance
This topic is locked and can not be replied to.