What is the proper way to report false-positive spam classification on crbug.com?

[Ryo Hashimoto]

Hi,

Does anyone know how can I report/fix false-positive spam classification on Chromium's bug tracker (i.e. crbug.com)?

Specifically, I stopped receiving updates about crbug.com/660189 after the issue was incorrectly classified as spam.

I (and 4 other people) have tried to file a bug with the "report incorrect spam classification" link, but there is no response for the filed bug on Monorail issue tracker after waiting for a month.

Is there any other way to report the false-positive case which is more likely to get proper attention, or is it possible to manually edit some whitelist to unspam the wrongly-labelled Chromium issue?

Thanks,

- Ryo

[Paweł Hajdan, Jr.]

+infra-dev,jrobbins

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CABtzobKDynmqYrHSmYwxk4j-7-bXYWZAC_W%2Biu7%3D7E1sC80prQ%40mail.gmail.com.

[Julie Parent]

+sean, the issue owner for follow up.

I've also marked it as non-spam so you'll start getting updates again.

You received this message because you are subscribed to the Google Groups "infra-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to infra-dev+unsubscribe@chromium.org.
To post to this group, send email to infr...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/infra-dev/CAATLsPYuGteca5iFqZUwgTgwsxSEqC%3DMOuZM3v1%2BaP98%2BsrH2A%40mail.gmail.com.

[Jason Robbins]

Sorry about that.  I think that this was a process failure on my part.  I haven't kept up with all the false-positive reports because, for a while, a lot of them were actually false reports from spammers.   

Also, I had the mistaken idea that when people report a false-positive, I should go review all recently spam classifications in that project rather than look at one issue specifically.   In this case, I did look but couldn't find the wrongly classified issue, and then I failed to follow up after you clarified.  I already changed the template for those reports, but I'll change the way those false-positive review issues are created to capture more specific info automatically.

Thanks,

jason!

[Ryo Hashimoto]

On Sat, Jul 22, 2017 at 3:18 AM, Jason Robbins <jrob...@chromium.org> wrote:

Sorry about that.  I think that this was a process failure on my part.  I haven't kept up with all the false-positive reports because, for a while, a lot of them were actually false reports from spammers.   

Also, I had the mistaken idea that when people report a false-positive, I should go review all recently spam classifications in that project rather than look at one issue specifically.   In this case, I did look but couldn't find the wrongly classified issue, and then I failed to follow up after you clarified.  I already changed the template for those reports, but I'll change the way those false-positive review issues are created to capture more specific info automatically.

Sounds like a great improvement!

Thanks,

jason!

On Fri, Jul 21, 2017 at 10:28 AM, Julie Parent <jpa...@chromium.org> wrote:

+sean, the issue owner for follow up.

I've also marked it as non-spam so you'll start getting updates again.

Cool, thanks!