[haiku-web] Re: The state of Trac (was: Re: Website Maintainer)

Niels Reedijk wrote:

Hi Charlie

2007/11/12, Charlie Clark <charlie@xxxxxxxxxxxxxx>:

Am 12.11.2007 um 15:07 schrieb Niels Reedijk:


We made a switch once from Bugzilla to Trac. What is the added value
of switching again? I'm curious about what exactly doesn't work for
whom, and why should we care. Trac seems clean and effective, and
moreover it works for me, so why should we switch?

Trac isn't clean: it has a really awful data model. I spent quite a
lot of time customising it for yellowTAB adding some of this stuff.
We don't need the wiki part and we currently don't use the svn
integration and integration with other systems isn't very easy.


You're right. I seem to remember that trac was chosen because it 'fit'
with the choice for subversion. Up to now, we haven't been using it
very much though...

(BTW, I have been using the Wiki part, but I agree that it isn't
indispensible).


Because of the borked data model we currently implement product
hierarchies using a javascript hack which I personally find
unpalatable. However, if you're happy to pick up the maintenance then
please go ahead. I have just been thinking out loud in case I really
am the bug tracker maintenance.


Well, I'm certainly not happy to pick up the major maintenance ;-) .
Seriously, I offer help in the area of regular maintenance: keeping
trac up to date, porting our patches, checking whether the backup
mechanism works.


As far as the migration goes: I'm no fan of moving to new systems
just because they're new and cool but I personally feel that a sound
data model is important (Trac's is bad but Bugzilla's is much worse).


Well, there are two options:

1. Continue to use trac.
a. If we can use the svn module, and if this provides added value, it
might make for a descent argument to keep using track for the tickets
(for now). Whenever we grow out of the ticket system, it might be a
good idea to start shopping around.

2. Switch to another issue tracker.

I'm offering help on both options, though limited to regular
maintenance. In the end, it's your call.
Is it really one individual's call? This is a tool used by a lot of people. Should this not be the call of the majority of the users of Trac, or at least of those who use it more heavily (iow, the core devs)? 

Cheers,

Koki
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List

Other related posts: