Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking Protection Issues and Webcompat infrastructure #255

Open
5 tasks
karlcow opened this issue Mar 10, 2022 · 0 comments
Open
5 tasks

Tracking Protection Issues and Webcompat infrastructure #255

karlcow opened this issue Mar 10, 2022 · 0 comments
Assignees

Comments

@karlcow
Copy link

karlcow commented Mar 10, 2022

This issue here is to record understanding and state of discussions on what is happening around tracking protection issues and how the webcompat team can provide the knowledge for the privacy team to organize themselves.

Some possible topics that needs to be addressed.

Discussions Leads on webcompat side

@ksy36 and @wisniewskit are the two leads for this discussion on the webcompat side.

Background

The Privacy team has a repo which collects ETP related issues. (private only)
https://github.com/mozilla/tracking-protection-issues-private/issues/

As of March 10, 2022

Repo Total issues Start date issues/day
Privacy issues ~146,000 July 2018 146
Webcompat issues ~100,000 January 2016 99

Current Triage on webcompat side for ETP issues

Webcompat team sometimes receives ETP issues on webcompat.com. Each time this is happening they are being tested and transferred to bugzilla. If a triage process was created by the Privacy team we could imagine moving the bug which are in webcompat/web-bugs to mozilla/tracking-protection-issues-private

Triage on Privacy side for webcompat issues

To the best of the webcompat team knowledge, the issues landing on mozilla/tracking-protection-issues-private are not being triaged nor shared with the webcompat team. We can perfectly imagine a system, when someone reported wrongly webcompat issues on ETP infrastructure to have them moved to https://github.com/webcompat/web-bugs/issues .

Some CAN and CAN NOT

  • webcompat team can NOT absorb the volume of issues that tracking protection is receiving. The Privacy team would have to set up their own triage team and their own ML bot.
  • webcompat team can provide expertise and formation on how to do the triage
  • webcompat team can provide expertise on how to tweak an ML bot for the mozilla/tracking-protection-issues-private repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants