* Lucas Nussbaum <lucas@debian.org>, 2012-01-19, 19:27:
I'm generally not a big fan to overuse the BTS for stuff it wasn't really designed for. This tends to result in complex processes that are difficult to follow for newcomers. For example, the wnpp bugs are often misformed, or people don't follow the right process.
The big difference is that nobody reads the wnpp bug traffic. But debian-mentors (or whatever the pseudo-package will be eventually called) bug traffic will land on this mailing list. Malformed bug titles will be promptly corrected, people don't following the process will be educated. :)
* Integration into UDD bug search[2] [2] <http://udd.debian.org/bugs.cgi>It might be better to write a separate cgi for that, to add more specific logic. For example, you could easily split the list with: - new packages - new uploads for existing packages - packages already uploaded (RFS that should be closed) - RFS that couldn't be parsed
Or we could write a bot that would usertag the bugs appropriately. Then you could use normal BTS view rather than UDD.
-- Jakub Wilk