[haiku-web] Re: [haiku-admin] Re: Website

>
> > problem is whether to auto-subscribe every contributor/author or to
> > require manual subscription. It's probably too annoying for normal
> > users, so it's better to have the possibility to mail authors 
> > manually
> > for more information.
> 
> Over my dead body, as they say. A bug tracker should foremost target 
> the needs of the developers, anything else *must* come after those.
> Creating the need to talk to the reporter without the bug tracker is 
> undermining the quality of the bug tracker in a big way.
>
I don't understand what you mean by talking to the developer without 
the bug tracker? In Trac it's easy to just add a comment to an existing 
ticket.
 

> Turns out I misread that. Yes, having a default developer per 
> component 
> is the way to go, definitely.
> 
> > And what does that have to do with components? Users *should* 
> > select 
> > the 
> > component that is affected by the bug. That is all we need from a 
> > user:
> > (For users, Type is always Defect and can't be changed)
> 
> Why is that? There can be bugs, feature requests, oddities, ... - or 
> do 
> you just intend to have different masks for this?
> 
There are more than defects, indeed. We should just make sure they 
don't overlap.

> > > The more people are using Haiku, the more bug reports will come 
> > > in 
> > > - 
> > > and most of these bug reports will be unusable, anyway - IMO 
> > > that's 
> > > not 
> > > even mean, just realistic :)
> > Here, I agree with you. We can at least try to add a little note:
> > * how to reproduce
> > * experienced behavior
> > * expected behavior
> > next to the details field, so users at least know what information 
> > we 
> > need (it's still up to them to read that note and actually write a 
> > good 
> > bug report, but maybe it helps).
> 
> Also: "Please mention the exact revision you tested" :)
> 
http://projects.edgewall.com/trac/wiki/TracTicketsCustomFields


> 
> It's not that I'm against switching to Trac, I just don't see the 
> point 
> in wasting any time and effort in doing so. I might still be against 
> it 
> when I have to use it, though, of course :)
> 
As it stands now, the Haiku web resources are spread throughout the 
place, and it's rather disjoint at that. Making the bug tracker, blog 
and content available directly from the front page is certainly a good 
goal. Furthermore, changing the current website to use a real CMS 
instead of what we have now wouldn't hurt either -- Phipps said this 
was Kurtis'(sp?) first larger web app.  Communication (blog, integrated 
roadmap view on the front page, moderated article queue, ...) is what 
the web should be about!


-- 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: