launchpad developmentNote: This is user facing and should go through the LEP process.
Nominate Spam
As a Launchpad user
I want to be able to easily and effectively nominate spam for removal
so that I and other users see less spam and more valuable content
The user doesn't care how the spam is subsequently removed--manually or automatically--but does care that it happens soon.
Launchpad developers have expected that acting on spam nomination would be done manually. The CHR developer is an obvious mechanism. Adding this to the CHR responsibilities is unsatisfying because CHR has generally been problematic.
Rationale
I don't believe in the importance of this feature. I think other things are more important. If let CHR people hide things I think that will make the priority of this further feature go way down.
Stakeholders
Who really cares about this feature? When did you last talk to them?
Constraints
What MUST the new behaviour provide?
What MUST it not do?
Subfeatures
Other LaunchpadEnhancementProposals that form a part of this one.
Workflows
What are the workflows for this feature? Provide mockups for each workflow.
You do not have to get the mockups and workflows right at this point. In fact, it is better to have several alternatives, delaying deciding on the final set of workflows until the last responsible moment.
Success
How will we know when we are done?
How will we measure how well we have done?
Thoughts?
Put everything else here. Better out than in.
