Note: This is user facing and  should go through the [[LaunchpadEnhancementProposalProcess|LEP]] process.

= Nominate Spam =

'''As a ''' Launchpad user<<BR>>
'''I want ''' to be able to easily and effectively nominate spam for removal<<BR>>
'''so that ''' I and other users see less spam and more valuable content<<BR>>

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 [[Foundations/Proposals/HideSpam|let CHR people hide things]] I think that will make the priority of this further feature go way down.

== Stakeholders ==

 * Some Launchpad users apparently care about this feature, given bug Bug:45419.

== Constraints ==

 * The feature must result in most valid nominations being effective: leading to spam going away.
 * The feature should result in the majority of the nominations being valid.
 * This feature should be easy to find visually, but not distracting or even immediately evident.
 * The feature should be one click to nominate.
 * Only authenticated users may identify elements as spam.
 * Provide the ability to gradually roll out this functionality to different types of Launchpad objects.
 * Corollary: Provide an easy path for adding this functionality to future objects.
 * If fulfilling the nomination is manual, it should be fast for the CHR person.

== Unnecessary Desires ==
These are called out as things that are *not* constraints for this proposal, even though they might be desirable.

 * The feature will not generate karma for nominating items that subsequently are hidden as spam.

== Subfeatures ==

''Other LaunchpadEnhancementProposal``s 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? ==

Curtis: I wanted to add a two flags, is_spam and is_visible to IMessage. logged in users would see button (This is spam) when their mouse was hovering over any IMessage decendent like IBugComment. Choosing the button work change the message to indicate someone has flag the message as spam, the button changes to (This is not spam).  There is a queue where ~registry can see all messages flagged as spam. They can unselect the is_visible to hide the message. ~registry members can view any message (bugs/1234/+comment/4) and see an link to edit the message. The member can redact personal information so that the crucial information remains visible.