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

On 2006-03-20 at 12:18:14 [+0100], Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> 
wrote:
> As I said, I think this can actually be an advantage, but we'd have to
> live with it for a longer time until we can make any statements.
>
> While that sounds all nice, it's not what we desperately need; it would
> just be nice to have.

In general I would agree with Axel on pretty much every point. Change is 
work and the active developers are obviously happy with what they've got. I 
think they've done an excellent job skinning Bugzilla
 
> And? It's a definite requirement for developers, anyway, I don't see
> any reason why we should hide that feature from anyone. What we could
> do is a "subscribe" feature that acts differently depending on the
> user's preferences. Then those who don't want e-Mail notification don't
> get it, for whatever reason.

In my opinion the solution is specify this when creating the components.

You might for example specify that all bug requests for a particular 
component go to the developer, the responsible group or both. If a 
developer is interested in a bug then he just needs to join that groups 
mailing list for bugs. In this way the technology supports the organic 
organisation.
 
> > 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.
 
> Turns out I misread that. Yes, having a default developer per component
> is the way to go, definitely.

Looks like we're agreed on this.

> Why is that? There can be bugs, feature requests, oddities, ... - or do
> you just intend to have different masks for this?

Nod.
 
> Also: "Please mention the exact revision you tested" :)

Please take the yellowTAB bug tracker as the baseline for this project. I 
like the irony of me doing work for free twice on this! ;-)
 
> That's silly. It's a bug tracker, nothing more. It's a tool for god's
> sake. Bugzilla gets the job done without any usability complaints for
> the developers - why should we not be happy with it? It provides
> everything we need.

Difficult not to agree with this.
 
> I agree that it looks a bit repelling to those who haven't used it
> before, though, but I don't consider this a big problem, as it's so
> damn easy to ignore those extra fields and options.

It should be clear that as little developer resources get committed to this 
as possible. I'll do the work on Trac and Waldemar can start on the CMS 
when he's fixed the Haiku network stack! ;-)
 
> 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 :)

Oh, stop moaning and get back in your cellar!

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

Other related posts: