eg: keep the motu-list as it is, and have an motu-bug list, that could be subscribed to if desired, and/or assign people the responsability of gatekeeping that list, eg: removing duplicates, cleaning up the quality, and then posting a summary Bug report to the motu list so that only quality gets onto the main list removing the user based spam eg: "I want package verison X+1".
Assigning a sub section of the MOTU group to house keep this and feed to the core list may be a way to go ?
I suspect as mentioned above that the noise ratio would increase, and lot of it would be lacking in a quality bug report (judging by a lot of the quality of generic bug reports on launchpad)
Would it not be possible to expand on a solution,
eg: keep the motu-list as it is, and have an motu-bug list, that could be subscribed to if desired, and/or assign people the responsability of gatekeeping that list, eg: removing duplicates, cleaning up the quality, and then posting a summary Bug report to the motu list so that only quality gets onto the main list removing the user based spam eg: "I want package verison X+1".
Assigning a sub section of the MOTU group to house keep this and feed to the core list may be a way to go ?
I suspect as mentioned above that the noise ratio would increase, and lot of it would be lacking in a quality bug report (judging by a lot of the quality of generic bug reports on launchpad)