| 2006-05-18 14:23:12 |
Omnifarious |
bug |
|
|
added bug |
| 2006-08-09 14:59:14 |
Brad Bollenbach |
launchpad: status |
Unconfirmed |
Needs Info |
|
| 2006-08-09 14:59:14 |
Brad Bollenbach |
launchpad: statusexplanation |
|
|
|
| 2006-08-10 00:42:16 |
Matthew Paul Thomas |
launchpad: status |
Needs Info |
Confirmed |
|
| 2006-08-10 00:43:00 |
Matthew Paul Thomas |
title |
Launchad needs a way of easily flagging spam |
Launchpad needs a way of easily flagging spam |
|
| 2007-05-28 02:45:52 |
Matthew Paul Thomas |
description |
I've seen at least one spam project on Launchpad. It took about 3 weeks to be removed. One isn't that many of course. But it would be nice to have a more expedited process for just spam since spammers make more money the longer their links are there.
|
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (e.g. bug 32990), spam bug reports (e.g. bug 69942), and incoherent and disruptive bug comments (ongoing in Bazaar).
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or remove it, and (if necessary) remove its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the revenue and/or offense caused. |
|
| 2007-10-19 06:00:30 |
Matthew Paul Thomas |
description |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (e.g. bug 32990), spam bug reports (e.g. bug 69942), and incoherent and disruptive bug comments (ongoing in Bazaar).
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or remove it, and (if necessary) remove its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the revenue and/or offense caused. |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (e.g. bug 32990), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (e.g. in Bazaar), and offensive translations (e.g. bug 153962). Future examples might include defamation or copyright violations.
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or remove it, and (if necessary) deactivate its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the revenue and/or offense caused.
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, and a built-in option to warn the creator of a borderline item. |
|
| 2008-01-08 20:13:41 |
Matthew Paul Thomas |
description |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (e.g. bug 32990), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (e.g. in Bazaar), and offensive translations (e.g. bug 153962). Future examples might include defamation or copyright violations.
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or remove it, and (if necessary) deactivate its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the revenue and/or offense caused.
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, and a built-in option to warn the creator of a borderline item. |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (e.g. in Bazaar), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or remove it, and (if necessary) deactivate its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the revenue and/or offense caused.
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't use Launchpad may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, and a built-in option to warn the creator of a borderline item. |
|
| 2008-03-20 18:32:18 |
Joey Stanford |
launchpad: importance |
Medium |
High |
|
| 2008-03-25 02:28:50 |
Matthew Paul Thomas |
description |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (e.g. in Bazaar), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or remove it, and (if necessary) deactivate its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the revenue and/or offense caused.
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't use Launchpad may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, and a built-in option to warn the creator of a borderline item. |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (e.g. in Bazaar), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or hide/remove it, and (if necessary) deactivate its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the ill-gotten revenue and/or offense caused.
(Don't mark a bug as a duplicate of this one if it is about implementing spam handling for a particular type of thing. Spam handling will not be implemented for everything all at once. This bug is about implementing the general mechanism.)
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't have a Launchpad account may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, a built-in option to warn the creator of a borderline item, and automatic spam detection. |
|
| 2008-04-22 09:23:51 |
Matthew Paul Thomas |
description |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (e.g. in Bazaar), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or hide/remove it, and (if necessary) deactivate its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the ill-gotten revenue and/or offense caused.
(Don't mark a bug as a duplicate of this one if it is about implementing spam handling for a particular type of thing. Spam handling will not be implemented for everything all at once. This bug is about implementing the general mechanism.)
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't have a Launchpad account may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, a built-in option to warn the creator of a borderline item, and automatic spam detection. |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or hide/remove it, and (if necessary) deactivate its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the ill-gotten revenue and/or offense caused.
(Don't mark a bug as a duplicate of this one if it is about implementing spam handling for a particular type of thing. Spam handling will not be implemented for everything all at once. This bug is about implementing the general mechanism.)
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't have a Launchpad account may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, a built-in option to warn the creator of a borderline item, and automatic spam detection. |
|
| 2008-04-23 08:13:35 |
Matthew Paul Thomas |
description |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or hide/remove it, and (if necessary) deactivate its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the ill-gotten revenue and/or offense caused.
(Don't mark a bug as a duplicate of this one if it is about implementing spam handling for a particular type of thing. Spam handling will not be implemented for everything all at once. This bug is about implementing the general mechanism.)
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't have a Launchpad account may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, a built-in option to warn the creator of a borderline item, and automatic spam detection. |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
(DON'T mark a bug as a duplicate of this one if it is about implementing spam handling for a particular type of thing. Spam handling will not be implemented for everything all at once. This bug is about implementing the general mechanism.)
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or hide/remove it, and (if necessary) deactivate its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the ill-gotten revenue and/or offense caused.
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't have a Launchpad account may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, a built-in option to warn the creator of a borderline item, and automatic spam detection. |
|
| 2008-07-06 18:39:24 |
Matthew Paul Thomas |
description |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
(DON'T mark a bug as a duplicate of this one if it is about implementing spam handling for a particular type of thing. Spam handling will not be implemented for everything all at once. This bug is about implementing the general mechanism.)
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or hide/remove it, and (if necessary) deactivate its creator. Admins should be able to do so quickly, without needing direct DB access, to minimize the ill-gotten revenue and/or offense caused.
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't have a Launchpad account may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, a built-in option to warn the creator of a borderline item, and automatic spam detection. |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
(DON'T mark a bug as a duplicate of this one if it is about implementing spam handling for a particular type of thing. Spam handling will not be implemented for everything all at once. This bug is about implementing the general mechanism.)
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or hide/remove it, and (if necessary) deactivate its creator (bug 122170). Admins should be able to do so quickly, without needing direct DB access, to minimize the offense caused or ill-gotten revenue gained.
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't have a Launchpad account may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, a built-in option to warn the creator of a borderline item, and automatic spam detection. |
|
| 2008-12-18 15:07:23 |
Herb McNew |
bug |
|
|
added subscriber Canonical LOSAs |
| 2009-03-31 04:22:43 |
Mary Gardiner |
removed subscriber Mary Gardiner |
|
|
|
| 2009-07-31 07:01:36 |
Paweł Madej |
removed subscriber Paweł Madej |
|
|
|
| 2009-08-14 12:04:16 |
Matthew Revell |
tags |
|
gatekeeper |
|
| 2009-08-20 15:17:53 |
Gary Poster |
launchpad-foundations: milestone |
|
3.1.10 |
|
| 2009-11-11 05:34:04 |
Curtis Hovey |
launchpad-foundations: milestone |
3.1.10 |
3.1.11 |
|
| 2009-12-15 17:05:00 |
Gary Poster |
launchpad-foundations: milestone |
3.1.11 |
|
|
| 2010-04-07 16:08:49 |
Matthew Paul Thomas |
description |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
(DON'T mark a bug as a duplicate of this one if it is about implementing spam handling for a particular type of thing. Spam handling will not be implemented for everything all at once. This bug is about implementing the general mechanism.)
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or hide/remove it, and (if necessary) deactivate its creator (bug 122170). Admins should be able to do so quickly, without needing direct DB access, to minimize the offense caused or ill-gotten revenue gained.
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't have a Launchpad account may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, a built-in option to warn the creator of a borderline item, and automatic spam detection. |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
(DON'T mark a bug as a duplicate of this one if it is about implementing spam handling for a particular type of thing. Spam handling will not be implemented for everything all at once. This bug is about implementing the general mechanism.)
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or hide/remove it, review other actions by the same person (bug 520413), and (if necessary) deactivate its creator (bug 122170). Admins should be able to do so quickly, without needing direct DB access, to minimize the offense caused or ill-gotten revenue gained.
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't have a Launchpad account may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, a built-in option to warn the creator of a borderline item, and automatic spam detection.
|
|
| 2010-05-28 14:22:40 |
Tom Haddon |
tags |
gatekeeper |
canonical-losa-lp gatekeeper |
|
| 2010-09-19 19:43:04 |
Mathieu Marquer |
bug |
|
|
added subscriber Mathieu Marquer |
| 2010-11-03 13:04:26 |
Jani Uusitalo |
bug |
|
|
added subscriber Jani Uusitalo |
| 2010-11-08 19:05:10 |
neuromancer |
bug |
|
|
added subscriber neuromancer |
| 2010-11-11 15:47:16 |
Curtis Hovey |
summary |
Launchpad needs a way of easily flagging spam |
Launchpad needs a way of easily flagging spam and abuse |
|
| 2010-11-18 16:01:36 |
Robert Collins |
tags |
canonical-losa-lp gatekeeper |
canonical-losa-lp feature-flags gatekeeper |
|
| 2010-11-18 16:01:52 |
Robert Collins |
tags |
canonical-losa-lp feature-flags gatekeeper |
canonical-losa-lp feature gatekeeper |
|
| 2011-01-25 05:18:41 |
Gabe Gorelick |
bug |
|
|
added subscriber Gabe Gorelick |
| 2011-02-05 13:50:16 |
papukaija |
bug |
|
|
added subscriber papukaija |
| 2011-03-02 05:12:33 |
José Lou Chang |
bug |
|
|
added subscriber José Lou Chang |
| 2011-03-30 16:44:36 |
j.c.sackett |
branch linked |
|
lp:~jcsackett/launchpad/set-question-message-visibility |
|
| 2011-04-03 03:48:36 |
Launchpad QA Bot |
launchpad: milestone |
|
11.04 |
|
| 2011-04-03 03:48:36 |
Launchpad QA Bot |
launchpad: assignee |
|
j.c.sackett (jcsackett) |
|
| 2011-04-03 03:48:40 |
Launchpad QA Bot |
tags |
canonical-losa-lp feature gatekeeper lp-foundations |
canonical-losa-lp feature gatekeeper lp-foundations qa-needstesting |
|
| 2011-04-03 03:48:42 |
Launchpad QA Bot |
launchpad: status |
Triaged |
Fix Committed |
|
| 2011-04-04 22:54:38 |
j.c.sackett |
launchpad: status |
Fix Committed |
Triaged |
|
| 2011-04-04 22:54:42 |
j.c.sackett |
tags |
canonical-losa-lp feature gatekeeper lp-foundations qa-needstesting |
canonical-losa-lp feature gatekeeper lp-foundations qa-ok |
|
| 2011-04-05 19:33:43 |
j.c.sackett |
launchpad: assignee |
j.c.sackett (jcsackett) |
|
|
| 2011-04-07 08:01:07 |
Launchpad QA Bot |
tags |
canonical-losa-lp feature gatekeeper lp-foundations qa-ok |
canonical-losa-lp feature gatekeeper lp-foundations qa-needstesting |
|
| 2011-04-07 08:01:09 |
Launchpad QA Bot |
launchpad: status |
Triaged |
Fix Committed |
|
| 2011-04-07 08:01:09 |
Launchpad QA Bot |
launchpad: assignee |
|
j.c.sackett (jcsackett) |
|
| 2011-04-07 14:13:58 |
j.c.sackett |
launchpad: status |
Fix Committed |
Triaged |
|
| 2011-04-07 14:14:03 |
j.c.sackett |
launchpad: assignee |
j.c.sackett (jcsackett) |
|
|
| 2011-04-07 14:14:50 |
j.c.sackett |
bug |
|
|
added subscriber j.c.sackett |
| 2011-04-07 19:41:33 |
Robert Collins |
tags |
canonical-losa-lp feature gatekeeper lp-foundations qa-needstesting |
canonical-losa-lp feature gatekeeper lp-foundations qa-untestable |
|
| 2011-04-07 20:30:22 |
j.c.sackett |
branch unlinked |
lp:~jcsackett/launchpad/set-question-message-visibility |
|
|
| 2011-04-07 21:10:17 |
Michael R. Crusoe |
removed subscriber Michael R. Crusoe |
|
|
|
| 2011-04-11 21:38:27 |
Curtis Hovey |
launchpad: milestone |
11.04 |
|
|
| 2011-05-16 01:02:39 |
William Grant |
tags |
canonical-losa-lp feature gatekeeper lp-foundations qa-untestable |
canonical-losa-lp feature gatekeeper lp-foundations |
|
| 2011-05-24 17:19:21 |
Kenyon Ralph |
bug |
|
|
added subscriber Kenyon Ralph |
| 2011-05-30 08:05:41 |
William Grant |
removed subscriber Canonical Launchpad Engineering |
|
|
|
| 2011-06-01 20:17:43 |
j.c.sackett |
removed subscriber j.c.sackett |
|
|
|
| 2011-06-06 09:05:23 |
Robert Collins |
summary |
Launchpad needs a way of easily flagging spam and abuse |
No way for unprivileged users to report (probable) spam within Launchpad |
|
| 2011-06-06 09:11:03 |
Robert Collins |
summary |
No way for unprivileged users to report (probable) spam within Launchpad |
No way for unprivileged users to report (probable) spam or abusive content within Launchpad |
|
| 2011-06-06 09:14:22 |
Robert Collins |
description |
Launchpad should have an expedited process for dealing with inappropriate contributions. In the past these have included spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
(DON'T mark a bug as a duplicate of this one if it is about implementing spam handling for a particular type of thing. Spam handling will not be implemented for everything all at once. This bug is about implementing the general mechanism.)
For every kind of thing an unprivileged user can create in Launchpad, anyone should have the ability to flag it as inappropriate so that admins can review it, confirm it or hide/remove it, review other actions by the same person (bug 520413), and (if necessary) deactivate its creator (bug 122170). Admins should be able to do so quickly, without needing direct DB access, to minimize the offense caused or ill-gotten revenue gained.
We will know this bug is fixed when:
* Launchpad moderators can visit a queue of things that have been reported as inappropriate (ordered most-frequently-reported first), click on each thing to examine it, and choose whether to allow it, remove it, or remove it and deactivate its creator.
* For at least two different types of item (e.g. projects and bug comments), anyone can click a "Report as inappropriate" or similar link, taking them to a form for explaining why it is inappropriate. (Should we provide this even for people who are not logged in? Someone who doesn't have a Launchpad account may encounter a copyright/trademark infringement on Launchpad via a Web search.) When submitted, the item appears in the queue for admins.
Future work might include aggregating items by creator or by reporter, a built-in option to warn the creator of a borderline item, and automatic spam detection.
|
Symptoms
========
Spam of various sorts can be handled by Launchpad administrators and the community help rotation role that Launchpad developers participate in. However end users have to report these spam objects over IRC or email. This makes it awkward for new users or users unaware of the process to actually address the spam, and can even lead to more spam where folk reply to the conversation in a bug / list etc saying that the previous message is spam : if the previous message is quoted this can perpetuate the spammers link / message.
Proposed solution
=================
Allow unprivileged users to flag that they consider a given object to be spam / abusive content.
Provide folk responsible for handling spam/abusive content a work queue where they can review flagged objects and decide:
- definitely not spam (takes it out of the queue forever)
- spam (hide or even delete the object)
- link to other objects updated or created by the same account (bug 520413)
- suspend the account if appropriate (bug 122170) |
|
| 2011-06-07 08:58:52 |
Jonathan Lange |
description |
Symptoms
========
Spam of various sorts can be handled by Launchpad administrators and the community help rotation role that Launchpad developers participate in. However end users have to report these spam objects over IRC or email. This makes it awkward for new users or users unaware of the process to actually address the spam, and can even lead to more spam where folk reply to the conversation in a bug / list etc saying that the previous message is spam : if the previous message is quoted this can perpetuate the spammers link / message.
Proposed solution
=================
Allow unprivileged users to flag that they consider a given object to be spam / abusive content.
Provide folk responsible for handling spam/abusive content a work queue where they can review flagged objects and decide:
- definitely not spam (takes it out of the queue forever)
- spam (hide or even delete the object)
- link to other objects updated or created by the same account (bug 520413)
- suspend the account if appropriate (bug 122170) |
Symptoms
========
Spam of various sorts can be handled by Launchpad administrators and the community help rotation role that Launchpad developers participate in. However end users have to report these spam objects over IRC or email. This makes it awkward for new users or users unaware of the process to actually address the spam, and can even lead to more spam where folk reply to the conversation in a bug / list etc saying that the previous message is spam: if the previous message is quoted this can perpetuate the spammers link / message.
In the past these have included: spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), spam bug attachments, offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
Proposed solution
=================
Allow unprivileged users to flag that they consider a given object to be spam / abusive content.
Provide folk responsible for handling spam/abusive content a work queue where they can review flagged objects and decide:
- definitely not spam (takes it out of the queue forever)
- spam (hide or even delete the object)
- link to other objects updated or created by the same account (bug 520413)
- suspend the account if appropriate (bug 122170) |
|
| 2011-07-06 15:58:13 |
Michael Imamura |
bug |
|
|
added subscriber Michael Imamura |
| 2011-09-25 14:30:28 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2011-10-22 14:15:58 |
Curtis Hovey |
launchpad: importance |
High |
Low |
|
| 2011-10-22 14:16:26 |
Curtis Hovey |
tags |
canonical-losa-lp feature gatekeeper lp-foundations |
canonical-losa-lp comments feature gatekeeper lp-foundations spam |
|
| 2011-11-23 11:00:09 |
era |
bug |
|
|
added subscriber era |
| 2012-02-25 11:07:05 |
Burkart Lingner |
bug |
|
|
added subscriber Burkart Lingner |
| 2012-05-16 14:59:15 |
Florian Rathgeber |
bug |
|
|
added subscriber Florian Rathgeber |
| 2012-12-03 19:58:16 |
Michael Imamura |
removed subscriber Michael Imamura |
|
|
|
| 2013-05-23 08:30:57 |
Hendrik Schrieber |
bug |
|
|
added subscriber Hendrik Knackstedt |
| 2014-01-17 10:46:33 |
Ken Sharp |
bug |
|
|
added subscriber Ken Sharp |
| 2014-10-26 02:32:24 |
dobey |
removed subscriber Rodney Dawes |
|
|
|
| 2015-11-07 11:40:02 |
JohnWashington |
bug |
|
|
added subscriber JohnWashington |
| 2015-12-20 18:35:19 |
Dara Adib |
removed subscriber Dara Adib |
|
|
|
| 2017-08-06 18:15:19 |
Eduard Hasenleithner |
bug |
|
|
added subscriber Eduard Hasenleithner |
| 2018-10-04 09:55:56 |
Colin Watson |
description |
Symptoms
========
Spam of various sorts can be handled by Launchpad administrators and the community help rotation role that Launchpad developers participate in. However end users have to report these spam objects over IRC or email. This makes it awkward for new users or users unaware of the process to actually address the spam, and can even lead to more spam where folk reply to the conversation in a bug / list etc saying that the previous message is spam: if the previous message is quoted this can perpetuate the spammers link / message.
In the past these have included: spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), spam bug attachments, offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
Proposed solution
=================
Allow unprivileged users to flag that they consider a given object to be spam / abusive content.
Provide folk responsible for handling spam/abusive content a work queue where they can review flagged objects and decide:
- definitely not spam (takes it out of the queue forever)
- spam (hide or even delete the object)
- link to other objects updated or created by the same account (bug 520413)
- suspend the account if appropriate (bug 122170) |
Symptoms
========
Spam of various sorts can be handled by Launchpad administrators and the community help rotation role that Launchpad developers participate in. However end users have to report these spam objects over IRC or email. This makes it awkward for new users or users unaware of the process to actually address the spam, and can even lead to more spam where folk reply to the conversation in a bug / list etc saying that the previous message is spam: if the previous message is quoted this can perpetuate the spammers link / message.
In the past these have included: spam projects (bug 151504, e.g. bug 32990), dummy branches (bug 177980), spam bug reports (e.g. bug 69942), incoherent/disruptive bug comments (bug 220535), spam bug attachments, offensive translations (e.g. bug 153962), and off-topic answers to questions (bug 85358). Future examples might include malware PPA packages, defamatory text, or copyright or trademark violations.
Current status
==============
Spam should be reported by opening a ticket on https://answers.launchpad.net/launchpad.
Proposed solution
=================
Allow unprivileged users to flag that they consider a given object to be spam / abusive content.
Provide folk responsible for handling spam/abusive content a work queue where they can review flagged objects and decide:
- definitely not spam (takes it out of the queue forever)
- spam (hide or even delete the object)
- link to other objects updated or created by the same account (bug 520413)
- suspend the account if appropriate (bug 122170) |
|
