On 2018-03-31, Sergey Bronnikov <serg...@bronevichok.ru> wrote: > Setup another bugtracker which you like, connect it to bugs@ and send a > link to this thread.
Please don't. My suggestion of looking at bugs@ as a seed is for a *person* to read new reports, collect information into one place, figure out if it really is a bug, write up tickets. Sounds like hard work? Yes, it is. A bug tracker needs curation/triage, that is not something that can be automated. If you look at a successful bug tracker, you will not be able to see most of this work without grovelling through dead tickets because the already-fixed issues and veiled support requests will no longer be visible.