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.
