Security/Tracking protection/Bug triage: Difference between revisions
Jump to navigation
Jump to search
(Use the URL field and mention the Disconnect categories) |
(→Reproducing bugs: Use of the "user story" field) |
||
| Line 30: | Line 30: | ||
# Close any unreproducible bugs with <tt>WORKSFORME</tt>. | # Close any unreproducible bugs with <tt>WORKSFORME</tt>. | ||
# Find the | # Find the blocked resource(s) responsible for the breakage (using [https://addons.mozilla.org/firefox/addon/umatrix/ uMatrix]) and add it to the '''user story''' field. | ||
# Tag bugs with the category that causes the breakage in the whiteboard field (use [https://github.com/mozilla-services/shavar-list-creation/blob/master/disconnect_mapping.py this mapping] for Twitter, Google and Facebook resources in the ''Disconnect'' category): | # Tag bugs with the category that causes the breakage in the '''whiteboard''' field (use [https://github.com/mozilla-services/shavar-list-creation/blob/master/disconnect_mapping.py this mapping] for Twitter, Google and Facebook resources in the ''Disconnect'' category): | ||
#* '''tp-ads''' for the Advertising category | #* '''tp-ads''' for the Advertising category | ||
#* '''tp-analytics''' for the Analytics category | #* '''tp-analytics''' for the Analytics category | ||
#* '''tp-social''' for the Social category | #* '''tp-social''' for the Social category | ||
#* '''tp-content''' for the Content category (only part of the strict list) | #* '''tp-content''' for the Content category (only part of the strict list) | ||
Revision as of 23:24, 21 June 2018
As bugs come into the Firefox::Tracking Protection component, the bug triage owner should follow these steps:
- Move misplaced bugs into the right component:
- Platform bugs should be moved into Toolkit::Safe Browsing
- Server-side bugs should be moved into Cloud Services::Server: Shavar
- Ensure the URL of the broken page is in the URL field
- Breakage bugs should block one of these meta bugs:
- tppaywall if TP is triggering a paywall / adblocker detection script (e.g. FuckAdBlock)
- tpvideo if TP is blocking the playing of videos
- tplogin if TP is breaking the login/registration flow of a site (including SSO providers)
- tpimages if TP is blocking necessary/useful images (excluding display ads)
- trackingprotection otherwise
- Close paywall-related bugs as WONTFIX.
- Mark bugs that have the same root cause (e.g. Facebook videos are blocked on site X) as DUPLICATE of one another.
- Add the tp-entitylist whiteboard tag if the breakage could be mitigated by expanding the entity whitelist to linked domains owned by the same organization.
- Add the tp-needsrepro whiteboard tag if the problematic resource is not mentioned in the bug.
- For feature requests and bugs that require a product decision:
- Tag with the tp-product whiteboard tag.
- NEEDINFO :pdol with a suggested decision (typically P3 or WONTFIX).
- Move to Tech Evangelism: Desktop any bug that needs to be resolved by the site owners (e.g. to avoid relying on trackers for their site's functionality to work).
- Set a priority on the bug:
- tp-needsrepro: P3
- tp-product: --
- tp-entitylist: P2
- Tech Evangelism: --
Reproducing bugs
Someone looking at the tp-needsrepro bugs should:
- Close any unreproducible bugs with WORKSFORME.
- Find the blocked resource(s) responsible for the breakage (using uMatrix) and add it to the user story field.
- Tag bugs with the category that causes the breakage in the whiteboard field (use this mapping for Twitter, Google and Facebook resources in the Disconnect category):
- tp-ads for the Advertising category
- tp-analytics for the Analytics category
- tp-social for the Social category
- tp-content for the Content category (only part of the strict list)