[haiku-web] Re: Trac (was: Website)

On 2006-03-21 at 13:43:48 [+0100], Waldemar Kornewald <wkornew@xxxxxxx> wrote:
> Yesterday, I privately talked to Michael. We made it clearer what the
> reasons for a switch to Trac would be.
> 
> My issues:
> * lack of visible progress on *our* website
> * meaningless and too complex status indicators on Status page
> * too complicated bug and task trackers
> 
> Progress indicators:
> * number of committed lines-of-code per month
>      only meaningful for developers
> * number of active developers per month
>      users might expect higher numbers
> * blog and news summary
>      might be good
> * progress bars for every team/component
>      wonderful, but must be updated regularly
> * latest screenshot
>      hmm...
> * latest closed tasks and bugs
>      I love it
> 
> Do we need a timeline/changelog of tasks and bugs? I like this very much
> because it is a good progress indicator. How could we do this with Bugzilla?

Don't know and count me out: I don't do perl and Bugzilla's DB model is still 
a mess. I think as much as has been done to tidy up Bugzilla without changing 
the code. Another problem I have with Bugzilla is that username = e-mail 
address. Not very clever in my opinion.
 
> Is something like Trac's Roadmap needed? Indeed, the roadmap could be
> replaced by a simple website page that also links to RFCs and goes into
> detail, if needed. Trac's Roadmap may be too limiting.
> 
> It is very difficult to make good status estimates. Can we provide an
> approximate 0-10 points status rating for every team/big-task? How can
> we get you to update the status page? Simply by asking for the status
> once per month and releasing a news item? Or would you be willing to
> login to our CMS and update a simple text field (e.g.: "Media: 60%")?
> 
> How do we want to manage tasks if we keep Bugzilla? Michael suggested
> that we don't need a special task tracker because everyone already
> maintains a private TODO/task list and simple text pages on our website
> would work, too. My take: I already used this scheme on our wiki and it
> works for my PPP TODO list. Personally, I feel more comfortable with
> editing text on our website instead of being limited by a task manager's
> interface.

Christopher Lenz, one of the main Trac developers, wrote a software metrics 
project ("Bitten", I believe) as part of Google's summer of code. So there is 
the possibility of integrating this. Simply reaching milestones, closing 
bugs, etc. will never give a true picture of progress because they are 
incredibly variable. So editorial content will always be a must. This is why 
we currently have the blogs which are dissociated from the Bugzilla and the 
source.

> How much work is required to simplify Bugzilla? In addition to the
> changes suggested for Trac (see our wiki) we also should remove the OS
> and URL fields. Moreover, the interface needs a big cleanup to look
> nicer, but that is not very important... Maybe we don't need support for
> components-as-tree because Bugzilla already has Product->Component, but
> unfortunately, changing the product does not immediately change the list
> of components.

See above, can't contribute to this solution. OTOH I have already done most 
of the changes to Trac necessary for the proposed features.

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

Other related posts: