From 1e491c09c2ea2c6483f4bcfdaf70853e17f3d166 Mon Sep 17 00:00:00 2001 From: Ksenia Berezina Date: Thu, 17 Feb 2022 22:46:33 -0500 Subject: [PATCH] Fixes #3610 - Add explanation of our ML process to the contributing documentation --- tests/unit/test_webhook.py | 6 +- webcompat/issues.py | 5 +- .../templates/contributors/report-bug.html | 72 +++++++++++++++++-- 3 files changed, 74 insertions(+), 9 deletions(-) diff --git a/tests/unit/test_webhook.py b/tests/unit/test_webhook.py index 0fa6e2a17..082b42a6d 100644 --- a/tests/unit/test_webhook.py +++ b/tests/unit/test_webhook.py @@ -489,12 +489,16 @@ def test_prepare_rejected_issue_autoclosed(self): 'body': '

Thanks for the report. We have closed this issue\n' 'automatically as we suspect it is invalid. If we made ' 'a mistake, please\nfile a new issue and try to provide ' - 'more context.

', + 'more context.

You can find more\ninformation in the' + ' ' # noqa + '\ndocumentation about our machine learning' + ' process\nfor triaging reports.

', 'labels': ['bugbug-probability-high'], 'milestone': 8, 'state': 'closed', 'title': 'Issue closed.'} actual = helpers.prepare_rejected_issue("autoclosed") + print(actual) self.assertEqual(type(actual), dict) self.assertEqual(actual, expected) diff --git a/webcompat/issues.py b/webcompat/issues.py index a6ada0176..c434ec2ac 100644 --- a/webcompat/issues.py +++ b/webcompat/issues.py @@ -46,7 +46,10 @@ AUTOCLOSE_TITLE = 'Issue closed.' AUTOCLOSE_BODY = '''

Thanks for the report. We have closed this issue automatically as we suspect it is invalid. If we made a mistake, please -file a new issue and try to provide more context.

''' +file a new issue and try to provide more context.

You can find more +information in the +documentation about our machine learning process +for triaging reports.

''' TEMPLATE_CONFIG = { 'rejected': { diff --git a/webcompat/templates/contributors/report-bug.html b/webcompat/templates/contributors/report-bug.html index 85331af81..53606f04d 100644 --- a/webcompat/templates/contributors/report-bug.html +++ b/webcompat/templates/contributors/report-bug.html @@ -73,7 +73,7 @@

How To Report An Issue?

-
  • +
  • Last step! You can report the issue anonymously or with your Github username. (We use the GitHub issue reporting system behind-the-scenes for webcompat.com). When you are identified, we can better follow-up with you if there are additional information required to understand the issue. Anonymous issues which lack details will be closed when we can't reproduce the issue and do diagnosis.

    @@ -151,24 +151,82 @@

    In Browser

    Is It Really A Web Compatibility Issue?

    - In general there are four type of issues: + Issues that fall into the web compatibility category are related to layout, content, + features or site functionality and occur in one browser, but not in another, for various reasons.

    + +

    Therefore, we're looking for reports that represent differences in how browsers render web content with this principle in mind.

    + + For example: +
      +
    1. Missing elements on the page in Chrome, but not in Firefox.
      2. +
    2. Can't access a site due to Safari on iOS being unsupported.
      3. +
    3. Video or audio doesn't play.
      4. +
    4. The desktop version of the site is displayed on Firefox for Android, but Chrome receives the mobile layout.
      5. +
    5. Buttons or links don't respond to clicks or taps.
      6. +
    6. Can't log in or constantly being logged out in Firefox, but it works in Edge.
      7. +
    7. Animation on a website is slow in one browser but fast in another.
      8. +
    +

    + Note that network issues, tracking, ads and script blockers, are likely not compatibility issues. +

    +

    + Issues that are not related to web compatibility efforts and will be closed: +

    1. - Website issues, including layouts, features or content. Webcompat.com is the right place! Not all site issues are valid Web Compatibility issues. Network issues, ads and script blockers, flash requirements for every browser are likely not compatibility issues. + Issues that are reproducible in all browsers. Likely this is a website issue and author or owner of the website should be notified instead.
    2. - Deceptive websites (scams, malware). You can report them to the Report Phishing Page. + Issues with the user interface of the browser itself and not the content of a website. These suggestions should be reported directly to the browser vendor.
    3. - Issues with the user interface of the browser itself and not the content of a website. These suggestions should be reported directly to the browser vendor. + Add-ons or web extensions. Report these issues directly to the creator of the extension. +
      4. +
    4. + Deceptive websites (phishing, scam, malware). You can report such sites to the Report Phishing Page. +
      5. +
    5. + Illegal content on the website. The best would be to report to your local authorities as we're not in a position to act on these issues.
    6. - Add-ons or web extensions. Report these issue directly to the creator of the extension. + Incorrect or inaccurate content. The best course of action is to get in touch with the author/owner of the website and let them know.
    - + + + +
    +
    +
    +

    Machine Learning for detecting invalid reports

    + +

    + We have added a machine learning bot into our workflow to help with incoming reports triage. + The bot analyses content of the reports and classifies them as valid or invalid based on the historical data. + Invalid reports are closed automatically without human involvement.

    + +

    If your report was closed by the bot, there are three possible reasons: +

      +
    1. + It falls into a category that is outside the scope of this project. + Please take a closer look at the section describing web compatibility issues in detail. +
      2. +
    2. + The problem you're experiencing has already been reported, and we received a lot of duplicates. + In this case, you could search for the domain in question on our GitHub page + to look for similar reports and get updated information on their status. +
      3. +
    3. + It was closed by mistake. While these cases are rare, there is still a possibility that the bot classified your report as invalid mistakenly. + If you think it was closed by mistake, you could file another one using "Report via GitHub" option instead of + "Report anonymously". Reports from authenticated users don't get triaged by the bot. +
      4. +
    +

    + +