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


Am 12.11.2007 um 16:13 schrieb Niels Reedijk:


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...
It wasn't possible because the repository and Trac are running on different servers. There is some tool to do the sync but the svn integration wasn't considered to be that important. 


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


Content should be in one place only - on the main site.


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.
From what Waldemar said it shouldn't be much work to bring the version of Trac up to date as the customisation is mainly a Javascript hack and now that Genshi has replaced Clearsilver I feel much happier with the templates. 


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.
I really dislike the limitations of the data model in Trac. It makes adding value to the project extremely difficult and some of it is just sick: what's wrong with writing SQL? I say this despite the respect I have for the project and devs as a whole: there is no doubt that Trac has shaken up the bug tracker environment. I started looking around at Python-based alternatives and Roundup looked interesting. I won't have time before BeGeistert 018 (12. + 13. January in Düsseldorf, Haiku Asylum from the 8th) to go into this in any detail but I would hope that would provide a good opportunity to look at the issue in detail with developers and anyone prepared to help out: check your diary. 


Niels

P.S. There is a ticket about tying subversion and trac together in
http://dev.haiku-os.org/ticket/966. There is discussion about svnsync
which requires subversion 1.4 to be installed on berlios. However,
berlios also seems to offer rsync. Would that work?
No idea but as noted above this doesn't seem to be important at the moment. 

Charlie
--
Charlie Clark
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-938-5360
GSM: +49-178-782-6226



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

Other related posts: