[haiku-web] Re: Trac (reevaluated)

> 
> As far as Trac... Honestly, the devs all seem to love Bugzilla. They 
> use 
> it, they love it, they aren't really inclined to change, as far as I 
> can 
> see. Waldemar and I don't think that it is very usable for non-devs. 
> I 
> don't personally see the need to press the issue, atm, because there 
> are 
> more than enough bugs to work on (that is to say, the devs are maxed 
> out 
> and a better bug tracker with gazillions more bugs wouldn't make 
> Haiku 
> any better right now).
>
Sure, Bugzilla does its job of dealing with *bugs*. Trac, on the other 
hand, gives you a timeline, a roadmap/milestone feature (i.e., auto-
status) and a flexible framework for extensions. Tried hacking 
Bugzilla?
 
>
> I am interested in seeing what Trac can do, but, honestly, there is *
> NO* 
> guarantee that it will be used. I haven't been a huge fan of the 
> other 
> Trac implementations that I have seen, but I know that it can easily 
> be 
> a implementation/configuration issue.
>
By Trac implementation, do you mean instance?

> 
> As far as being open, part of the problem is that we are too 
> distributed. We have some stuff about this in (this) list, some in 
> private emails (from before this list existed), some in wiki, etc. 
> That 
> is another goal that I have for the new website - to tie all of the 
> communication methods together so that there are no separate 
> forums/wikis/email lists - that everything is tied together so that 
> there is one and only one data stream for each area of Haiku. When a 
> wiki page changes, folks who have signed up for email will get a link 
> or 
> a page in their email; it will be available via the website and a 
> forum 
> entry will be posted. One data stream, whether you like push or pull.
>
Maybe there's a lesson to be learned from the PyPy guys (even though 
they have a sligtly different development model), but they essentially 
keep documents, IRC meeting logs and whatnot in their repository.  I 
think it'd be nice to have the mailing lists running on (e.g.) 
lists.haiku-os.org, so all resources were really collected in one 
place.
 
-- Mikael
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Any sufficiently complicated C or Fortran program
 contains an ad hoc informally-specified bug-ridden
 slow implementation of half of Common Lisp."      -- Philip Greenspun
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List

Other related posts: