845490 - module.metadata should have a way to make amo reviewers aware of safety level

Status: RESOLVED INCOMPLETE

(Add-on SDK Graveyard :: General, defect, P3)

Description

[Erik Vold [:erikvold] (please needinfo? me)]

some modules like window-utils, chrome, and observer-service are flagged by reviewers so that the add-ons that use them are not fast tracked and given a more careful review, this list has to be manually maintained though, and should really be marked in the sdk module metadata imo.

Comment 1

[Alexandre Poirot [:ochameau]]

Shouldn't we just distinguish addons using only high level api from all others?
Before the new layout, it was easy, now it is harder but might still be possible.

If that what we want, we may just explain them of to make the distinction, or tune cfx to put such flag in manifest.

Comment 2

[Erik Vold [:erikvold] (please needinfo? me)]

(In reply to Alexandre Poirot (:ochameau) from comment #1)
> Shouldn't we just distinguish addons using only high level api from all
> others?
> Before the new layout, it was easy, now it is harder but might still be
> possible.
> 
> If that what we want, we may just explain them of to make the distinction,
> or tune cfx to put such flag in manifest.

I think there are three levels of concern here, because not all low level modules provide super powers.

Comment 3

[Erik Vold [:erikvold] (please needinfo? me)]

Don't have time for this one at the moment.

Comment 4

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1399562