Security/Tracking protection/Bug triage: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Switch from DevAdvocacy to Tech Evangelism: Desktop since DevAdvocacy is reserved for devrel folks)
mNo edit summary
Line 20: Line 20:
#* '''tp-product''': --
#* '''tp-product''': --
#* '''tp-entitylist''': P2
#* '''tp-entitylist''': P2
#* '''Tech Evangelism''' product: --
#* '''Tech Evangelism''': --

Revision as of 22:27, 14 September 2017

How

  1. Look through all Firefox::Tracking Protection bugs and webcompat.com issues linked from the breakage metabug looking for things we can fix:
    • Platform bugs should be moved into Toolkit::Safe Browsing
    • Server-side bugs should be moved into Cloud Services::Server: Shavar
  2. Close any unreproducible bugs with WORKSFORME.
  3. 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
    • trackingprotection otherwise
  4. Check that breakage bugs include the offending blocked resource in the comments.
  5. Tag bugs with the list that causes the breakage in the whiteboard field.
    • tp-base for the standard list
    • tp-content for the strict list
  6. Mark bugs that have the same root cause (e.g. Facebook videos are blocked on site X) as DUPLICATE of one another.
  7. 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.
  8. Tag feature requests and bugs that require a product decision with the tp-product whiteboard tag.
  9. 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).
  10. Set a priority on the bug:
    • tp-product: --
    • tp-entitylist: P2
    • Tech Evangelism: --