> > Kai Wetlesen wrote: > > > What would a potential curator of a bug tracker need > > > to do besides spin up a server, install, and maintain > > > the chosen (or written) software? > > > > not underestimate the effort involved. > > > > so this has come up before, and the answer remains the same. anyone can > > setup > > a bug tracker, and feed bugs into it. close the ones that get fixed, > > categorize the rest, etc.. do that for a few months and see how it goes. > > > > i'm not really interested in looking at an empty bug database. nor one > > that's > > filled with crap. so yeah, there's a bootstrapping problem. > > > > 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. > > > > like a lot of projects that seem really easy, you'd think somebody would > > just > > do it if it were that simple. but the idea that nobody wants to chance > > investing time in a deadend project suggests they kind of know the time > > investment isn't just a saturday afternoon. > > > > Theo de Raadt wrote: > Indeed, this thread is full of volunteers, isn't it? > > Why haven't one of you already started doing it? > > (not including Ted, Ingo, or Antoine, or myself)
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. ~Kai
signature.asc
Description: Message signed with OpenPGP
