Re: Issues

>> Ideally, we want *one* tool for everything.  Tikiwiki seems the best
>> thing so far, and I would rather see the community throw its weight
>> behind one tool than a number of them.  I even know the bugzilla
>> configuration process and internal code base and would rather sacrifice
>> that in the short term for the long term ease of use.
>> 
>> In that regard, it seems that we could cut back significantly on
>> independent services using tikiwiki, so it still seems like the best
>> total solution for our needs.  Thoughts?
>
>I have a bit of reservation on using tikiwiki for bug tracking as well in
>the long term.  I have yet to see a system that has adequate bug tracking
>for a large project AND is usable for other things.
>
>For now I think it would be fine stand alone, but if/when bugs start rolling
>in I think it may be unavoidable to go with a full blown Mozilla setup.  I
>guess time will tell, but I'm sure we will outgrow the capabilities in
>tikiwiki once things are rolling.
>
>There is a great bugzilla for large projects talk at OLS, so maybe we'll
>have to schedule that one into things ;)

I'll toss in another option Request Tracker [http://www.bestpractical.com/rt/]
is used by corporate sites to track bugs or issues and I get the impression that
it's very flexible and could maybe be integrated into tikiwiki.  It can be
authenticated off of Apache who can authenticate off of LDAP like tikiwiki.  I
expect our devs could easily make it a seamless integration.

flickerfly