Kai Wetlesen wrote:
> > > you don't have to announce your bug database the first day you set it up. 
> > > in
> > > fact, it's better not to. but in a few months time, when somebody 
> > > inevitably
> > > asks misc how do i contribute, where's the todo list, you'll have this 
> > > handy
> > > list of unresolved bugs to point them at.

> There are many decisions that would need to be made that will piss somebody
> off. Decisions like what software/platform to use, where to host the thing, 
> and
> how much the tool should integrate into existing bug reporting mechanisms
> (right now just fancy emailing).
> 
> To answer your tactful question Theo, I personally haven’t done anything 
> because
> I do not have your blessing nor of someone who can say “yes just effing do 
> it". But,
> if you would be willing to give me free reign it will be done.

Imagine if you'd followed my suggestion and spent the last six months curating
a bug database. Then today you could have sent us a link to it and everybody
would see how useful it is. Now we have to wait another six months.

Reply via email to