1315094 - Outreach to add-ons that directly call CPOWs

Status: RESOLVED WORKSFORME

(Firefox :: Extension Compatibility, defect)

Description

[:shell escalante]

Bug 1214824 landed a patch to stop allowing unsafe CPOW calls when MPC=True was set as of Fx50.

We already did outreach to 6 add-on developers that had used unsafe CPOWs.   This told them of the change and that they were put on a white list (bug 1283681) that would let them keep using CPOWs for a while - so they had time to fix.

The first telemetry had a filter for "hide data points that don't have enough submissions".  This missed flagging 58 lower volume add-ons, who are also calling CPOWs directly.  They have been added to the whitelist for 50 - but need outreach about fixing.

The 58 add-on IDs are here https://docs.google.com/spreadsheets/d/1-trz-tboMYhlI8M3cfnMysrYee7tLsz0QHwlqfqH6UM/edit#gid=24618415.  

Is there any way to contact many at once based on add-on ID?

Here is the original email template with full descriptions - that still validly describes the issue https://docs.google.com/document/d/1ZFy2B6C-C8B0jfEgd0eAazTv0xXg2A6-HRdiVN2I5Uo/edit

Comment 1

[Jorge Villalobos [:jorgev] (he/him)]

I suggested using the AMO admin tool to contact those developers. Andrew, should an issue be filed on Github for this?

Comment 2

[Andrew Williamson [:eviljeff]]

(In reply to Jorge Villalobos [:jorgev] from comment #1)
> I suggested using the AMO admin tool to contact those developers. Andrew,
> should an issue be filed on Github for this?

If there's a way to identify those Add-ons based on information we hold on AMO, yes.  If we're having to add detection or hard-code the Add-on IDs it's probably easier to use another tool.

Comment 3

[:shell escalante]

i'll file an issue in github issue.  We have them identified.  In Fx50 they are whitelisted - so they won't break with the patch (which blocks MPC=true from calling CPOWs directly).

I'll look through the last few ID's for who we need to pull out of the list to contact directly, not contact, or need a different email (invalid IDs (may have gotten wrong), partners, people marked MPC=false don't need contact, and folks not marked MPC=true need a different contact)

Comment 4

[Julien Cristau [:jcristau]]

Mass wontfix for bugs affecting firefox 52.

Comment 5

[Mark Banner (:standard8)]

Since we're no longer accepting non-WebExtensions add-ons, I believe this is now WFM.