https://wiki.mozilla.org/api.php?action=feedcontributions&user=Jorge.villalobos&feedformat=atomMozillaWiki - User contributions [en]2024-03-28T15:16:07ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=User:Jorge.villalobos&diff=1216185User:Jorge.villalobos2019-08-08T20:20:30Z<p>Jorge.villalobos: Update</p>
<hr />
<div>{{Remobox<br />
|name=Jorge<br />
|surname=Villalobos<br />
|image=<br />
|city=San José<br />
|country=Costa Rica<br />
|region=LATAM<br />
|mentor=User:Henx<br />
|bugzillamail=jorge@mozilla.com<br />
|pmail=jorge@mozilla.com<br />
|twitter=jorgevillalobos<br />
|ircnick=jorgev<br />
|ircchannels=#amo #addons #teamaddons<br />
|background=Add-ons Product Manager<br />
}}<br />
<br />
<br />
<br />
{{VerifiedUser|type=editor}}</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Thunderbird_and_SeaMonkey_Add-ons_FAQ&diff=1197262Add-ons/Thunderbird and SeaMonkey Add-ons FAQ2018-07-13T19:31:35Z<p>Jorge.villalobos: Added links</p>
<hr />
<div>'''Where can I find add-ons to install?'''<br />
<br />
Add-ons for Firefox and Firefox for Android can be found at https://addons.mozilla.org (also known as AMO).<br />
<br />
Add-ons for Thunderbird and SeaMonkey can be found at https://addons.thunderbird.net.<br />
<br />
'''Why is there a separate site for Thunderbird and SeaMonkey add-ons?'''<br />
<br />
The Firefox add-on development platform was migrated in 2017 to a new technology called [https://developer.mozilla.org/en-US/Add-ons/WebExtensions WebExtensions]. This makes it easy to create powerful cross-browser add-ons using web technologies. Throughout 2018, all legacy add-ons and legacy features on AMO are being phased out.<br />
<br />
Given that Thunderbird and SeaMonkey still use legacy add-on technology, it was decided it would be easier for the add-on websites to split, so AMO can do away with legacy features and continue its development.<br />
<br />
'''Who runs the Thunderbird and SeaMonkey add-ons site?'''<br />
<br />
The site is managed by the Thunderbird Council and runs on Mozilla infrastructure. It runs on a forked version of the AMO code, and the Mozilla Add-ons Team are working with the Thunderbird Council to make the transition as smooth as possible.<br />
<br />
'''How does this affect add-on users on Thunderbird and SeaMonkey?'''<br />
<br />
This shouldn’t affect users. All AMO URLs pointing to Thunderbird or SeaMonkey add-ons should redirect to the new site. Add-on update requests should also be redirected. New versions of Thunderbird and SeaMonkey should point directly to the new site, so the redirects are eventually unnecessary.<br />
<br />
'''I’m a developer. Where can I find my add-ons?'''<br />
<br />
If your add-ons are compatible with Firefox or Firefox for Android, they can be found on AMO. If they are compatible with Thunderbird or SeaMonkey, they can be found on https://addons.thunderbird.net. You should be able to log in using the same credentials as on AMO.<br />
<br />
Since add-ons can support both Firefox and Thunderbird, or Firefox and SeaMonkey (or all of them), an add-on can be on both sites. The websites are independent, so changes done on one doesn’t reflect on the other.<br />
<br />
'''How can I opt out of this process?'''<br />
<br />
If you don’t want your add-ons on either site, you can go to your listing management page and either disable or delete your add-on. Note that if your add-on is on both sites, you might need to do this twice.<br />
<br />
'''Where can I ask more questions about this?'''<br />
<br />
You can post a message on [https://discourse.mozilla.org/t/new-site-for-thunderbird-add-ons/30027 our community forum] or email amo-admins AT mozilla DOT org for additional information.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Thunderbird_and_SeaMonkey_Add-ons_FAQ&diff=1197261Add-ons/Thunderbird and SeaMonkey Add-ons FAQ2018-07-13T19:29:53Z<p>Jorge.villalobos: Removed dupe title</p>
<hr />
<div>'''Where can I find add-ons to install?'''<br />
<br />
Add-ons for Firefox and Firefox for Android can be found at https://addons.mozilla.org (also known as AMO).<br />
<br />
Add-ons for Thunderbird and SeaMonkey can be found at https://addons.thunderbird.net.<br />
<br />
'''Why is there a separate site for Thunderbird and SeaMonkey add-ons?'''<br />
<br />
The Firefox add-on development platform was migrated in 2017 to a new technology called WebExtensions. This makes it easy to create powerful cross-browser add-ons using web technologies. Throughout 2018, all legacy add-ons and legacy features on AMO are being phased out.<br />
<br />
Given that Thunderbird and SeaMonkey still use legacy add-on technology, it was decided it would be easier for the add-on websites to split, so AMO can do away with legacy features and continue its development.<br />
<br />
'''Who runs the Thunderbird and SeaMonkey add-ons site?'''<br />
<br />
The site is managed by the Thunderbird Council and runs on Mozilla infrastructure. It runs on a forked version of the AMO code, and the Mozilla Add-ons Team are working with the Thunderbird Council to make the transition as smooth as possible.<br />
<br />
'''How does this affect add-on users on Thunderbird and SeaMonkey?'''<br />
<br />
This shouldn’t affect users. All AMO URLs pointing to Thunderbird or SeaMonkey add-ons should redirect to the new site. Add-on update requests should also be redirected. New versions of Thunderbird and SeaMonkey should point directly to the new site, so the redirects are eventually unnecessary.<br />
<br />
'''I’m a developer. Where can I find my add-ons?'''<br />
<br />
If your add-ons are compatible with Firefox or Firefox for Android, they can be found on AMO. If they are compatible with Thunderbird or SeaMonkey, they can be found on https://addons.thunderbird.net. You should be able to log in using the same credentials as on AMO.<br />
<br />
Since add-ons can support both Firefox and Thunderbird, or Firefox and SeaMonkey (or all of them), an add-on can be on both sites. The websites are independent, so changes done on one doesn’t reflect on the other.<br />
<br />
'''How can I opt out of this process?'''<br />
<br />
If you don’t want your add-ons on either site, you can go to your listing management page and either disable or delete your add-on. Note that if your add-on is on both sites, you might need to do this twice.<br />
<br />
'''Where can I ask more questions about this?'''<br />
<br />
You can post a message on our community forum or email amo-admins AT mozilla DOT org for additional information.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Thunderbird_and_SeaMonkey_Add-ons_FAQ&diff=1197259Add-ons/Thunderbird and SeaMonkey Add-ons FAQ2018-07-13T19:29:24Z<p>Jorge.villalobos: Jorge.villalobos moved page Add-ons/Thunderbird-SeaMonkey-FAQ to Add-ons/Thunderbird and SeaMonkey Add-ons FAQ: Better title</p>
<hr />
<div><h1>Thunderbird and SeaMonkey Add-ons Site FAQ</h1><br />
<br />
'''Where can I find add-ons to install?'''<br />
<br />
Add-ons for Firefox and Firefox for Android can be found at https://addons.mozilla.org (also known as AMO).<br />
<br />
Add-ons for Thunderbird and SeaMonkey can be found at https://addons.thunderbird.net.<br />
<br />
'''Why is there a separate site for Thunderbird and SeaMonkey add-ons?'''<br />
<br />
The Firefox add-on development platform was migrated in 2017 to a new technology called WebExtensions. This makes it easy to create powerful cross-browser add-ons using web technologies. Throughout 2018, all legacy add-ons and legacy features on AMO are being phased out.<br />
<br />
Given that Thunderbird and SeaMonkey still use legacy add-on technology, it was decided it would be easier for the add-on websites to split, so AMO can do away with legacy features and continue its development.<br />
<br />
'''Who runs the Thunderbird and SeaMonkey add-ons site?'''<br />
<br />
The site is managed by the Thunderbird Council and runs on Mozilla infrastructure. It runs on a forked version of the AMO code, and the Mozilla Add-ons Team are working with the Thunderbird Council to make the transition as smooth as possible.<br />
<br />
'''How does this affect add-on users on Thunderbird and SeaMonkey?'''<br />
<br />
This shouldn’t affect users. All AMO URLs pointing to Thunderbird or SeaMonkey add-ons should redirect to the new site. Add-on update requests should also be redirected. New versions of Thunderbird and SeaMonkey should point directly to the new site, so the redirects are eventually unnecessary.<br />
<br />
'''I’m a developer. Where can I find my add-ons?'''<br />
<br />
If your add-ons are compatible with Firefox or Firefox for Android, they can be found on AMO. If they are compatible with Thunderbird or SeaMonkey, they can be found on https://addons.thunderbird.net. You should be able to log in using the same credentials as on AMO.<br />
<br />
Since add-ons can support both Firefox and Thunderbird, or Firefox and SeaMonkey (or all of them), an add-on can be on both sites. The websites are independent, so changes done on one doesn’t reflect on the other.<br />
<br />
'''How can I opt out of this process?'''<br />
<br />
If you don’t want your add-ons on either site, you can go to your listing management page and either disable or delete your add-on. Note that if your add-on is on both sites, you might need to do this twice.<br />
<br />
'''Where can I ask more questions about this?'''<br />
<br />
You can post a message on our community forum or email amo-admins AT mozilla DOT org for additional information.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Thunderbird-SeaMonkey-FAQ&diff=1197260Add-ons/Thunderbird-SeaMonkey-FAQ2018-07-13T19:29:24Z<p>Jorge.villalobos: Jorge.villalobos moved page Add-ons/Thunderbird-SeaMonkey-FAQ to Add-ons/Thunderbird and SeaMonkey Add-ons FAQ: Better title</p>
<hr />
<div>#REDIRECT [[Add-ons/Thunderbird and SeaMonkey Add-ons FAQ]]</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Thunderbird_and_SeaMonkey_Add-ons_FAQ&diff=1197258Add-ons/Thunderbird and SeaMonkey Add-ons FAQ2018-07-13T19:28:18Z<p>Jorge.villalobos: First version</p>
<hr />
<div><h1>Thunderbird and SeaMonkey Add-ons Site FAQ</h1><br />
<br />
'''Where can I find add-ons to install?'''<br />
<br />
Add-ons for Firefox and Firefox for Android can be found at https://addons.mozilla.org (also known as AMO).<br />
<br />
Add-ons for Thunderbird and SeaMonkey can be found at https://addons.thunderbird.net.<br />
<br />
'''Why is there a separate site for Thunderbird and SeaMonkey add-ons?'''<br />
<br />
The Firefox add-on development platform was migrated in 2017 to a new technology called WebExtensions. This makes it easy to create powerful cross-browser add-ons using web technologies. Throughout 2018, all legacy add-ons and legacy features on AMO are being phased out.<br />
<br />
Given that Thunderbird and SeaMonkey still use legacy add-on technology, it was decided it would be easier for the add-on websites to split, so AMO can do away with legacy features and continue its development.<br />
<br />
'''Who runs the Thunderbird and SeaMonkey add-ons site?'''<br />
<br />
The site is managed by the Thunderbird Council and runs on Mozilla infrastructure. It runs on a forked version of the AMO code, and the Mozilla Add-ons Team are working with the Thunderbird Council to make the transition as smooth as possible.<br />
<br />
'''How does this affect add-on users on Thunderbird and SeaMonkey?'''<br />
<br />
This shouldn’t affect users. All AMO URLs pointing to Thunderbird or SeaMonkey add-ons should redirect to the new site. Add-on update requests should also be redirected. New versions of Thunderbird and SeaMonkey should point directly to the new site, so the redirects are eventually unnecessary.<br />
<br />
'''I’m a developer. Where can I find my add-ons?'''<br />
<br />
If your add-ons are compatible with Firefox or Firefox for Android, they can be found on AMO. If they are compatible with Thunderbird or SeaMonkey, they can be found on https://addons.thunderbird.net. You should be able to log in using the same credentials as on AMO.<br />
<br />
Since add-ons can support both Firefox and Thunderbird, or Firefox and SeaMonkey (or all of them), an add-on can be on both sites. The websites are independent, so changes done on one doesn’t reflect on the other.<br />
<br />
'''How can I opt out of this process?'''<br />
<br />
If you don’t want your add-ons on either site, you can go to your listing management page and either disable or delete your add-on. Note that if your add-on is on both sites, you might need to do this twice.<br />
<br />
'''Where can I ask more questions about this?'''<br />
<br />
You can post a message on our community forum or email amo-admins AT mozilla DOT org for additional information.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=WebExtensions/Triage&diff=1195844WebExtensions/Triage2018-06-20T20:43:16Z<p>Jorge.villalobos: Updated WE queries due to Product change.</p>
<hr />
<div>= Purpose of Meeting =<br />
Recurring triage sessions to accomplish these community goals:<br />
* Transparency: Decide whether APIs tagged "design-decision-needed" are "design-decision-approved" or "wontfix" to ensure transparency for the direction of WebExtensions. <br />
* Participation: Give guidance on and assign advisors to APIs marked "design-decision-approved" to make it easier for contributors to get involved.<br />
* Experiments: Discuss and provide feedback for [http://webextensions-experiments.readthedocs.io/en/latest/index.html WebExtensions Experiments].<br />
<br />
=Next Meeting=<br />
[https://docs.google.com/document/d/1Y_oYPldTT_kQOOouyJbC-8y3ASIizScLKFRhQfsDQWI/edit#heading=h.v63i1wz9d1pc May 29, 2018]<br />
<br />
=Details & How to Join=<br />
* Every other Tuesday at [http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 10:30am Pacific] (17:30 UTC) <br />
* Need help converting to your local time? [https://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 Click here].<br />
* Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU<br />
*IRC: [https://wiki.mozilla.org/IRC irc.mozilla.org], #Addons channel<br />
*To join from a telephone, dial one of the following numbers depending on your nearest location: <br />
**US Toll Free +1 800 707 2533, pin 2000, conf 8960 <br />
**US/CA/Mountain View +1 650 903 0800, extension 2000, 8960<br />
**US/CA/San Francisco: +1 415 762 5700, extension 2000, 8960<br />
**US/OR/Portland: +1 971 544 8000, extension 2000, 8960 <br />
**CA/BC/Vancouver: +1 778 785 1540, extension 2000, 8960 <br />
**CA/ON/Toronto: +1 416 848 3114, extension 2000, 8960 <br />
**UK/London: +44 (0)207 855 3000, extension 2000, 8960<br />
**FR/Paris: +33 (0) 184 883 737, Press 1 for English or 2 for French, extension 2000, 8960 <br />
**DE/Berlin: +49 30 983 333 000, extension 2000, 8960<br />
**NZ/Auckland: +64 9 555 1100, extension 2000, 8960<br />
<br />
==About This Triage==<br />
* We normally spend 5 minutes per bug<br />
* The more information in the bug, the better<br />
* The goal of the triage is to give a general thumbs up or thumbs down on a proposal; we won't be going deep into implementation details<br />
* If you're interested in submitting a proposal for a new API, please read the [[WebExtensions/Vision|WebExtensions Vision]].<br />
<br />
==Triage Guidelines==<br />
Bugs marked "design-decision-needed" should be:<br />
*Tagged with "design-decision-approved" or "wontfix" (including reason)<br />
<br />
Bugs marked "design-decision-approved" should have:<br />
*Clear description of the API and suggested implementation if possible<br />
*Priority & impact<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code#Develop_Web_Extensions_APIs onboarding process]<br />
*Advisor<br />
<br />
==Bug Queries==<br />
====="design-decision-needed"=====<br />
These are determined from the Monday WebExtensions triage. They are APIs we [https://mzl.la/2M717uc need more discussion] on.<br />
<br />
====="design-decision-approved"=====<br />
These are APIs we would [https://mzl.la/2JS8B7C like to have]. They should meet the triage criteria listed above.<br />
<br />
==WebExtensions Experiments==<br />
* Submit your [http://webextensions-experiments.readthedocs.io/en/latest/index.html WebExtensions Experiment] by opening an issue on the [https://github.com/web-ext-experiments/about/issues web-ext-experiments github repo].<br />
* Be sure to include the following in your issue: <br />
** Link to where your experiment is located<br />
** A quick overview of what it does<br />
** Any Bugzilla bugs that it might address<br />
** If you’d like to move your repository over to this organisation and we can create a repository for you<br />
* A comment will be added to the issue when your WebExtensions Experiment has been added to a meeting agenda.<br />
<br />
= Archive =<br />
=====2018=====<br />
[https://docs.google.com/document/d/1Y_oYPldTT_kQOOouyJbC-8y3ASIizScLKFRhQfsDQWI/edit#heading=h.hhpni8ijl0wx May 15, 2018] <br /><br />
[https://docs.google.com/document/d/1TRkZ2u3GQXwlHpfP4-P_SXcwIwvlQz5Sm-C8I89Ya_o/edit# May 8, 2018] <br /><br />
[https://docs.google.com/document/d/1A7lwSkunTIdPE8FGqYV93oO-2l8xo3GFqTbY1l1QC1w/edit# April 17, 2018] <br /><br />
[https://docs.google.com/document/d/1cFcqNOLwp77aosh5QUeNKgW8FQONAzOBlqjbcbxdIXw/edit# April 10, 2018] <br ><br />
[https://docs.google.com/document/d/1H1ZEWf7dmyyu7NZZL90TkbyaUTjbdIK3TUEtO_vff34/edit# April 3, 2018] <br /><br />
[https://docs.google.com/document/d/1k7AgEyVdZzeF2AIrQl9pP2QRpLENa1OfHvTKhYvKaSo/edit# March 27, 2018] <br /> <br />
[https://docs.google.com/document/d/1b4r8z964_Est_mbSYUx9jtRt-HTtXgu-EAzM_3yr7ww/edit March 13, 2018]<br /><br />
[https://docs.google.com/document/d/1n-Cbk3d6j394mObWPMhQsfIyHIL08RhC_IEV2QBV1x8/edit#heading=h.ntu5tnxkwd88 March 6, 2018] <br /><br />
[https://docs.google.com/document/d/1Jd50z5FMuS6tA6BMiCkpemAMeE5CtR_NboA-EdYI7jE/edit# February 27, 2018] <br /><br />
[https://docs.google.com/document/d/1-edU5RRFo2TupsOW400AcTOj8yyQnXd0F7uSsqkEzck/edit#heading=h.hhpni8ijl0wx February 20, 2018] <br /><br />
[https://docs.google.com/document/d/1731b2kkN1wndNzVvo--5gwUcagbOSKGNYv4769r68NM/edit# February 6, 2018] <br /><br />
[https://docs.google.com/document/d/1x80jYXicAotNjlitY5RZDcSRpRM3lmaSHp_q4co4OEg/edit# January 30, 2018] <br /><br />
[https://docs.google.com/document/d/1Mc0h5OVd30WBjCORssdifZRXYQrk6WcTqX1cw6ADO9k/edit# January 23, 2018] <br /><br />
[https://docs.google.com/document/d/13AiUqFgtLsuJ17QjzUOQ7nBN1U_ZEO0yzMaHLLl0JKk/edit# January 16, 2018] <br /> <br />
[https://docs.google.com/document/d/15JYw3L1490dKbr6yTLz1uirH8rfhcSiLJCubSWDlnfs/edit#heading=h.edrw957gm8hg January 9, 2018] <br /><br />
<br />
=====2017=====<br />
[https://docs.google.com/document/d/1KwfTum8Ow5w4afPAOvShpu_d_MNtahhOIqL3-Em9lLc/edit#| December 19, 2017] <br /><br />
[https://docs.google.com/document/d/1vH4wqJJZt1jk-cpx5NOq67b1UNekeQog6bz2HFOHe5E/edit# December 5, 2017] <br /><br />
[https://docs.google.com/document/d/1MduEIKmXDdj3p94PJDrPPPYvbSfEdrrMF-UhMnHPqEQ/edit# November 28, 2017] <br /><br />
[https://docs.google.com/document/d/1g3RMfKZ3671NcusMqkoOiKwfPekRe-VI7Rzqxo6F_Ao/edit# November 14, 2017] <br /><br />
[https://docs.google.com/document/d/1qqE6fkqr-RNWaFvMpv0Z8O5FLDgQ3AT5eGdbTt7lRGg/edit# October 31, 2017]<br /><br />
[https://docs.google.com/document/d/1oUFGD57_NGbtV5y8k_yIS3GN8pFO3M_K1SWQhzlq6Ho/edit# October 17, 2017]<br /><br />
[https://docs.google.com/document/d/1X5RmNq2tGC5Aw3npIKqxB2vhnVhg9uOoXh2TggduTPU/edit#heading=h.hhpni8ijl0wx October 3, 2017]<br /><br />
[https://docs.google.com/document/d/1pw5y-GHwDLPV9bYK4HWCiZtslqFtAeL3G9bC4ZDbdjs/edit# September 26, 2017]<br /><br />
[https://docs.google.com/document/d/13gmYyN0qCjzV7YAsqGpbeeHr3al0yiWP7ayqKJPLS2w/edit#heading=h.hhpni8ijl0wx September 5, 2017]<br /><br />
[https://docs.google.com/document/d/11SdY-aRhvPU3SvH8jpj0covj3Teq9_GJl8wMeEeSVwo/edit# August 22, 2017]<br /><br />
[https://docs.google.com/document/d/1I-i1FQ38nwFHNl4hnzTctdsYHXOjJpeAgm1Bm3VoUUA/edit# August 8, 2017]<br /><br />
[https://docs.google.com/document/d/1l5zlSASqZAzzJGZhHtLWY1yaUwCKZiHXXGP1k_2W-TU/edit# August 1, 2017] - WebExtensions Only <br /><br />
[https://docs.google.com/document/d/1BBIZhiHG1zlQiu6744jiAYyWJLa-B0iRu9vzWypkvF4/edit# July 25, 2017] <br /><br />
[https://docs.google.com/document/d/1gWszBunGAyOJ_V8_HMECXJuZ4Gd_HTM_M7xjDSwSxeo/edit#heading=h.t2yykqfh2jii July 18, 2017] - WebExtensions only <br /><br />
[https://docs.google.com/document/d/1MEMC7EyZ2VVInbWod7FD2SFGp36osoxQkhUm5f0aNSs/edit# July 11, 2017] <br /><br />
[https://docs.google.com/document/d/1s2j85VfYKTDftppFU-K7pgRs6sEuMTHVXqf3RL5iYvs/edit# June 20, 2017] - WebExtensions only<br /><br />
[https://docs.google.com/document/d/1A_M0YD86Plcs6eHyM2KXkDXY074BHZ3fZvaWXCljQLI/edit# June 13, 2017] <br /><br />
[https://docs.google.com/document/d/1pTNjK5i_8gHt3EeiUiu5KCUVeRcfwn7ybCPDBSx6CLM/edit June 6, 2017 - WebExtensions only] <br /><br />
[https://docs.google.com/document/d/1hKKRpGFIaAaI3G_HfPX2Nk8pCchyhUIKJB9y5sIrVV4/edit# May 30, 2017] <br /><br />
[https://docs.google.com/document/d/1-j08Zo4sbwAuRZndNNtdIRlDM8TblddDA-PAeRgYMWU/edit#heading=h.du5ihvu5p6ro May 23, 2017] - WebExtensions only <br /><br />
[https://docs.google.com/document/d/1vrhHNOelBty4hXcjQ8VbFk-azHRFFDVyGka7H0VpEa8/edit# May 16, 2017] <br /><br />
[https://docs.google.com/document/d/1q7UD3DxsT5z0lO3EbOyF9Iln32Wg_e9LYMdHZ80BEb4/edit#heading=h.du5ihvu5p6ro May 9, 2017] - WebExtensions APIs only<br/><br />
[https://docs.google.com/document/d/1vf8AaW8tKKbMn4KhsqEYhrYqVTUGaERHQmzanEp2Cls/edit# May 2, 2017]<br /><br />
[https://docs.google.com/document/d/1WScwIH2D5tiL7vT4_lC44oFigR53xatWsUEwyjWvs7k/edit# April 25] - WebExtensions APIs only<br /><br />
[https://docs.google.com/document/d/1zKqhDqXoH9vi88q4DGtOHm1hsCF8ZwLNvCrrCE5htbc/edit# April 18, 2017]<br /><br />
[https://docs.google.com/document/d/1V4NP4tWnjHigS2lAosCLfkU2FTcrQnoQzzXZmmB1uzk/edit April 4, 2017]<br /><br />
[https://docs.google.com/document/d/1xM6iKOSGo9cDWw3ZA27PT-AVlx1Mvd79sxC6pYNhBqU/edit#heading=h.t2yykqfh2jii March 21, 2017]<br /><br />
[https://docs.google.com/document/d/1zzfedbTKAHUmm4UctxSOIJV3iKayXQ8TuXPodXW8wC0/edit#heading=h.sbitm9gruxfs March 7, 2017]<br /><br />
[https://docs.google.com/document/d/1H4sjnRFc87NZXZsM6XIgwWaoV2bdRFepiG28G7WzgPs/edit?usp=sharing Feb 21, 2017]<br /><br />
[https://docs.google.com/document/d/1X5OUNgpUcMLkHrOPbg-OLWSA2hzoRykRZd2gyTJ9vgU/edit# Feb 7, 2017]<br /><br />
[https://docs.google.com/document/d/1add-6FL8mzksvzbyB83HUmEkVmKERd-nt740AYr-4PE/edit# Jan 24, 2017]<br /><br />
[https://docs.google.com/document/d/18K97o1juaHSeYEkes1iMz8AayjuVkUuIK844ErGaa-c/edit?usp=sharing Jan 10, 2017]<br />
<br />
=====2016=====<br />
[https://docs.google.com/document/d/1S1QrBK1hrulE7dlLiQzjMupHUUSwDYRYAOXiqtMHe-k/edit?usp=sharing Dec 13, 2016]<br /><br />
[https://docs.google.com/document/d/1IMBFXHNpg_A-15VdJM1Hh8DUUXF1xNFy87W1w8ZEOBk/edit#heading=h.du5ihvu5p6ro Nov 29, 2016]<br /><br />
[https://docs.google.com/document/d/1cMvAtlIZpykpxZ0bG2J2lh7Mx1WcVfLrHSDJZHFvexc/edit Nov 15, 2016]<br /><br />
[https://docs.google.com/document/d/1i5CT821JFutWL-f3AZ3VhlYIIzulnMttjNp1JsYba8M/edit# Nov 1, 2016]<br /><br />
[https://docs.google.com/document/d/1elytPf_HqAqqFC6EM0-hrJp7kWJA-LfKILXV1tzNLTU/edit Oct 18, 2016]<br /></div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Contribute/Triage&diff=1195843Add-ons/Contribute/Triage2018-06-20T20:39:45Z<p>Jorge.villalobos: Formatting</p>
<hr />
<div>= Purpose of Meeting =<br />
Recurring triage sessions to accomplish these community goals:<br />
<br />
* Ensure add-on bugs marked "Good First Bug" are fresh and updated for new contributors. If you are a new contributor who wants to write code for add-on related projects, please [https://wiki.mozilla.org/Add-ons/Contribute/Code start here].<br />
<br />
=Next Meeting=<br />
Check the Developer Communication calendar for the next Good First Bugs meeting. <br />
<br />
{{#widget:Widget:Google Calendar<br />
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ<br />
}}<br />
<br />
=Details & How to Join=<br />
* Meetings occur every other Wednesday at [http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 8:30am Pacific] <br />
* Need help converting to your local time? Click [https://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 here].<br />
* Meeting notes are [https://docs.google.com/document/d/1ZI6Hk9yenig4BXr6TnOl06KNFwnb0GtpvZXEkHjMbQY/edit# available here]. <br />
<br />
* Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU<br />
*IRC: [https://wiki.mozilla.org/IRC irc.mozilla.org], #Addons channel<br />
*To join from a telephone, dial one of the following numbers depending on your nearest location: <br />
**US Toll Free +1 800 707 2533, pin 2000, conf 8960 <br />
**US/CA/Mountain View +1 650 903 0800, extension 2000, 8960<br />
**US/CA/San Francisco: +1 415 762 5700, extension 2000, 8960<br />
**US/OR/Portland: +1 971 544 8000, extension 2000, 8960 <br />
**CA/BC/Vancouver: +1 778 785 1540, extension 2000, 8960 <br />
**CA/ON/Toronto: +1 416 848 3114, extension 2000, 8960 <br />
**UK/London: +44 (0)207 855 3000, extension 2000, 8960<br />
**FR/Paris: +33 (0) 184 883 737, Press 1 for English or 2 for French, extension 2000, 8960 <br />
**DE/Berlin: +49 30 983 333 000, extension 2000, 8960<br />
**NZ/Auckland: +64 9 555 1100, extension 2000, 8960<br />
<br />
==Triage Guidelines==<br />
All "Good First Bugs" should have:<br />
*Clear description of the issue<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code onboarding process]<br />
*Mentor<br />
<br />
==Bug Queries==<br />
====="Maybe Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20maybe%20good%20first%20bug These are tagged "contrib: maybe good first bug"]. We triage these and change the tag to "Good First Bugs" if determined to be good for new contributors.<br />
<br />
====="Good First Bugs" that need a mentor on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20good%20first%20bug,needs:%20mentor These are tagged "contrib: good first bug" and "needs: mentor"]. We triage these and add replace the "needs: mentor" label by "contrib: mentor assigned" after we decided on a mentor.<br />
<br />
====="Good First Bugs" that are assigned to a contributor on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20good%20first%20bug,contrib:%20assigned These are tagged "contrib: good first bug" and "contrib: assigned"]. We triage these and check-in with contributors on their progress and remove "contrib: assigned" after a longer period of inactivity or no response.<br />
<br />
====="Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20good%20first%20bug This is the query] contributors see. We should spot-check them to ensure they are properly triaged.<br />
<br />
=====WebExtensions Bugs on Bugzilla=====<br />
*These are WebExtensions bugs that [https://mzl.la/2tdJuSD don't have a mentor]<br />
*These are WebExtensions bugs that [https://mzl.la/2lmvVvx have an assignee but haven't been commented on for 3 weeks]<br />
<br />
=====Add-ons Manager Bugs on Bugzilla=====<br />
*These are Add-ons Manager bugs that [https://mzl.la/2pecPvR don't have a mentor]<br />
*These are Add-ons Manager bugs that [https://mzl.la/2oIyb30 have an assignee but haven't been commented on for 3 weeks]<br />
<br />
= Looking for the WebExtensions APIs triage wiki? = <br />
The [[WebExtensions/Triage|WebExtensions APIs triage]] now has its own wiki! Please head over to [[WebExtensions/Triage#Purpose_of_Meeting|its wiki page]] to stay up to date about the WebExtensions APIs triage.<br />
<br />
= Archive =<br />
=====2018=====<br />
[https://docs.google.com/document/d/1ZI6Hk9yenig4BXr6TnOl06KNFwnb0GtpvZXEkHjMbQY/edit# All meetings starting May 30, 2018]<br />
<br />
=====2017=====<br />
[https://docs.google.com/document/d/1MduEIKmXDdj3p94PJDrPPPYvbSfEdrrMF-UhMnHPqEQ/edit# November 28, 2017]<br /><br />
[https://docs.google.com/document/d/1g3RMfKZ3671NcusMqkoOiKwfPekRe-VI7Rzqxo6F_Ao/edit# November 14, 2017] <br /><br />
[https://docs.google.com/document/d/1qqE6fkqr-RNWaFvMpv0Z8O5FLDgQ3AT5eGdbTt7lRGg/edit# October 31, 2017]<br /><br />
[https://docs.google.com/document/d/1oUFGD57_NGbtV5y8k_yIS3GN8pFO3M_K1SWQhzlq6Ho/edit# October 17, 2017]<br /><br />
[https://docs.google.com/document/d/1X5RmNq2tGC5Aw3npIKqxB2vhnVhg9uOoXh2TggduTPU/edit#heading=h.hhpni8ijl0wx October 3, 2017]<br /><br />
[https://docs.google.com/document/d/1pw5y-GHwDLPV9bYK4HWCiZtslqFtAeL3G9bC4ZDbdjs/edit# September 26, 2017]<br /><br />
[https://docs.google.com/document/d/13gmYyN0qCjzV7YAsqGpbeeHr3al0yiWP7ayqKJPLS2w/edit#heading=h.hhpni8ijl0wx September 5, 2017]<br /><br />
[https://docs.google.com/document/d/11SdY-aRhvPU3SvH8jpj0covj3Teq9_GJl8wMeEeSVwo/edit# August 22, 2017]<br /><br />
[https://docs.google.com/document/d/1I-i1FQ38nwFHNl4hnzTctdsYHXOjJpeAgm1Bm3VoUUA/edit# August 8, 2017]<br /><br />
[https://docs.google.com/document/d/1l5zlSASqZAzzJGZhHtLWY1yaUwCKZiHXXGP1k_2W-TU/edit# August 1, 2017] - WebExtensions Only <br /><br />
[https://docs.google.com/document/d/1BBIZhiHG1zlQiu6744jiAYyWJLa-B0iRu9vzWypkvF4/edit# July 25, 2017] <br /><br />
[https://docs.google.com/document/d/1gWszBunGAyOJ_V8_HMECXJuZ4Gd_HTM_M7xjDSwSxeo/edit#heading=h.t2yykqfh2jii July 18, 2017] - WebExtensions only <br /><br />
[https://docs.google.com/document/d/1MEMC7EyZ2VVInbWod7FD2SFGp36osoxQkhUm5f0aNSs/edit# July 11, 2017] <br /><br />
[https://docs.google.com/document/d/1s2j85VfYKTDftppFU-K7pgRs6sEuMTHVXqf3RL5iYvs/edit# June 20, 2017] - WebExtensions only<br /><br />
[https://docs.google.com/document/d/1A_M0YD86Plcs6eHyM2KXkDXY074BHZ3fZvaWXCljQLI/edit# June 13, 2017] <br /><br />
[https://docs.google.com/document/d/1pTNjK5i_8gHt3EeiUiu5KCUVeRcfwn7ybCPDBSx6CLM/edit June 6, 2017 - WebExtensions only] <br /><br />
[https://docs.google.com/document/d/1hKKRpGFIaAaI3G_HfPX2Nk8pCchyhUIKJB9y5sIrVV4/edit# May 30, 2017] <br /><br />
[https://docs.google.com/document/d/1-j08Zo4sbwAuRZndNNtdIRlDM8TblddDA-PAeRgYMWU/edit#heading=h.du5ihvu5p6ro May 23, 2017] - WebExtensions only <br /><br />
[https://docs.google.com/document/d/1vrhHNOelBty4hXcjQ8VbFk-azHRFFDVyGka7H0VpEa8/edit# May 16, 2017] <br /><br />
[https://docs.google.com/document/d/1q7UD3DxsT5z0lO3EbOyF9Iln32Wg_e9LYMdHZ80BEb4/edit#heading=h.du5ihvu5p6ro May 9, 2017] - WebExtensions APIs only<br/><br />
[https://docs.google.com/document/d/1vf8AaW8tKKbMn4KhsqEYhrYqVTUGaERHQmzanEp2Cls/edit# May 2, 2017]<br /><br />
[https://docs.google.com/document/d/1WScwIH2D5tiL7vT4_lC44oFigR53xatWsUEwyjWvs7k/edit# April 25] - WebExtensions APIs only<br /><br />
[https://docs.google.com/document/d/1zKqhDqXoH9vi88q4DGtOHm1hsCF8ZwLNvCrrCE5htbc/edit# April 18, 2017]<br /><br />
[https://docs.google.com/document/d/1V4NP4tWnjHigS2lAosCLfkU2FTcrQnoQzzXZmmB1uzk/edit April 4, 2017]<br /><br />
[https://docs.google.com/document/d/1YbQGbkNWwVGvXgjzJ541s-d4AVImRLThMKnBM3Yo1Lw/edit#heading=h.t2yykqfh2jii March 28, 2017] - GFB only<br /><br />
[https://docs.google.com/document/d/1xM6iKOSGo9cDWw3ZA27PT-AVlx1Mvd79sxC6pYNhBqU/edit#heading=h.t2yykqfh2jii March 21, 2017]<br /><br />
[https://docs.google.com/document/d/1zzfedbTKAHUmm4UctxSOIJV3iKayXQ8TuXPodXW8wC0/edit#heading=h.sbitm9gruxfs March 7, 2017]<br /><br />
[https://docs.google.com/document/d/1H4sjnRFc87NZXZsM6XIgwWaoV2bdRFepiG28G7WzgPs/edit?usp=sharing Feb 21, 2017]<br /><br />
[https://docs.google.com/document/d/1X5OUNgpUcMLkHrOPbg-OLWSA2hzoRykRZd2gyTJ9vgU/edit# Feb 7, 2017]<br /><br />
[https://docs.google.com/document/d/1add-6FL8mzksvzbyB83HUmEkVmKERd-nt740AYr-4PE/edit# Jan 24, 2017]<br /><br />
[https://docs.google.com/document/d/18K97o1juaHSeYEkes1iMz8AayjuVkUuIK844ErGaa-c/edit?usp=sharing Jan 10, 2017]<br />
<br />
=====2016=====<br />
[https://docs.google.com/document/d/1S1QrBK1hrulE7dlLiQzjMupHUUSwDYRYAOXiqtMHe-k/edit?usp=sharing Dec 13, 2016]<br /><br />
[https://docs.google.com/document/d/1IMBFXHNpg_A-15VdJM1Hh8DUUXF1xNFy87W1w8ZEOBk/edit#heading=h.du5ihvu5p6ro Nov 29, 2016]<br /><br />
[https://docs.google.com/document/d/1cMvAtlIZpykpxZ0bG2J2lh7Mx1WcVfLrHSDJZHFvexc/edit Nov 15, 2016]<br /><br />
[https://docs.google.com/document/d/1i5CT821JFutWL-f3AZ3VhlYIIzulnMttjNp1JsYba8M/edit# Nov 1, 2016]<br /><br />
[https://docs.google.com/document/d/1elytPf_HqAqqFC6EM0-hrJp7kWJA-LfKILXV1tzNLTU/edit Oct 18, 2016]<br /><br />
[https://docs.google.com/document/d/1BDIbINMGgjoWlZxHmw-MnLm3HEqB38oUNTJUPAippGo/edit Oct 4, 2016]<br /><br />
[https://docs.google.com/document/d/1gABxxstInPy5XMsmoYMhZBMsLGFWNsgWMhgjUlt7-o8/edit Sept 20, 2016]<br /><br />
[https://docs.google.com/document/d/14cqCfgbyGoBXe7ttho0L3mIe4FcSSlzHH3L4fBFnLzA/edit Sept 6, 2016]<br /><br />
[https://docs.google.com/document/d/1GDpdcO1EHefRL3B5p5g1emdp_lY-YFWjwXv8YG1EgWo/edit August 23, 2016]<br /><br />
[https://docs.google.com/document/d/1rZvIfFILAHozLGTrg5C7Q7lXyEZ2gfMDw7cVkEo34io/edit August 9, 2016]<br /><br />
[https://docs.google.com/document/d/1A5hKaon2Z3nSCQc9ToYTOjr2cIpmmeZmu9EnbhVjHd0/edit July 26, 2016]<br /><br />
[https://docs.google.com/document/d/18wCqoUzNYshOWDjuJjePFivb4T5nD0WlFE06NKn3YQ0/edit July 12, 2016]<br /><br />
[https://docs.google.com/document/d/1uBo-WVFP2v-dyeYyDtfPD9ipN8JeIw7sCag4CYonQqY/edit# June 28, 2016]<br /><br />
[https://docs.google.com/document/d/1lYqcEWaktMXPmAefRB9PW9iSBM95rlVKFOO-vFRewdE/edit May 31, 2016]<br /><br />
[https://docs.google.com/document/d/1Bq7gTVhsGfTW58A9MUurruu5jc2w5OHSeaoRbmWRQV4/edit May 17, 2016]<br /><br />
[https://docs.google.com/document/d/1EkZXtIx7TkQxnFn_2ei3SR7j9xeDVc1WSl3suY2n8RU/edit April 28, 2016]<br /><br />
[https://docs.google.com/document/d/13yPW-ojA_jzXUe7_fxDvYQavsr5yEHZzHXXCMcuZgCA/edit April 14, 2016]<br /><br />
[https://docs.google.com/document/d/1hSABd9dd8UktXGJuf0iXn_8Fpuz09VEqkxrxMY_AvZw/edit Mar 31, 2016]<br /><br />
[https://docs.google.com/document/d/1ss0i_zAZDytsyBnMGF1gdRI6LjRWqvQS9Q0ueKzQV1Q/edit Mar 3, 2016]<br /><br />
[https://docs.google.com/document/d/1GkHWjHRDcUd7WD2BFF-6zhdyce4lK8qMX23O6C0eRIA/edit Feb 18, 2016]<br /><br />
[https://docs.google.com/document/d/1cM2JIIgw1i7TJe3oOojCtJvEhJoBGdHgNvjS2hRfBcw/edit Feb 4, 2016]<br /> <br />
[https://docs.google.com/document/d/1OZVV_HVXWAY-1u-nPhb4MrXOsycVFbXkXGEhhTomoaM/edit Jan 21, 2016]<br /><br />
[https://docs.google.com/document/d/1GwqhWsSsBp5vfLW7-5Di8_CzIfepwK9YVZAnQuLxK9I/edit Jan 7, 2016]<br />
<br />
=====2015=====<br />
[https://docs.google.com/document/d/18Csoja50IhnjqraFzxEYyVIJp-j79GLO2gCrvTSYHUI/edit Nov. 19, 2015]<br /><br />
[https://docs.google.com/document/d/1gbhL0S4amQ447ddIX7mEZsSaGoiFt8fTw22FKe_GbIo/edit Oct. 29, 2015]<br /><br />
[https://docs.google.com/document/d/1EoLSXHKCqJzTatj6CLLpjomwXnN5zUOA897brO_1aJQ/edit Oct. 15, 2015]<br />
<br />
=====Aug - Oct 2015=====<br />
https://drive.google.com/drive/folders/0B2aDMRMZ7uzvYzA4Wm1VYVhvemM<br />
<br />
=Onboarding information template=<br />
If this is your first contribution, please refer to https://wiki.mozilla.org/Add-ons/Contribute/Code on how to get started.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Contribute/Triage&diff=1195842Add-ons/Contribute/Triage2018-06-20T20:37:16Z<p>Jorge.villalobos: Updated WE queries due to Product change.</p>
<hr />
<div>= Purpose of Meeting =<br />
Recurring triage sessions to accomplish these community goals:<br />
<br />
* Ensure add-on bugs marked "Good First Bug" are fresh and updated for new contributors. If you are a new contributor who wants to write code for add-on related projects, please [https://wiki.mozilla.org/Add-ons/Contribute/Code start here].<br />
<br />
=Next Meeting=<br />
Check the Developer Communication calendar for the next Good First Bugs meeting. <br />
<br />
{{#widget:Widget:Google Calendar<br />
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ<br />
}}<br />
<br />
=Details & How to Join=<br />
* Meetings occur every other Wednesday at [http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 8:30am Pacific] <br />
* Need help converting to your local time? Click [https://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 here].<br />
* Meeting notes are [https://docs.google.com/document/d/1ZI6Hk9yenig4BXr6TnOl06KNFwnb0GtpvZXEkHjMbQY/edit# available here]. <br />
<br />
* Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU<br />
*IRC: [https://wiki.mozilla.org/IRC irc.mozilla.org], #Addons channel<br />
*To join from a telephone, dial one of the following numbers depending on your nearest location: <br />
**US Toll Free +1 800 707 2533, pin 2000, conf 8960 <br />
**US/CA/Mountain View +1 650 903 0800, extension 2000, 8960<br />
**US/CA/San Francisco: +1 415 762 5700, extension 2000, 8960<br />
**US/OR/Portland: +1 971 544 8000, extension 2000, 8960 <br />
**CA/BC/Vancouver: +1 778 785 1540, extension 2000, 8960 <br />
**CA/ON/Toronto: +1 416 848 3114, extension 2000, 8960 <br />
**UK/London: +44 (0)207 855 3000, extension 2000, 8960<br />
**FR/Paris: +33 (0) 184 883 737, Press 1 for English or 2 for French, extension 2000, 8960 <br />
**DE/Berlin: +49 30 983 333 000, extension 2000, 8960<br />
**NZ/Auckland: +64 9 555 1100, extension 2000, 8960<br />
<br />
==Triage Guidelines==<br />
All "Good First Bugs" should have:<br />
*Clear description of the issue<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code onboarding process]<br />
*Mentor<br />
<br />
==Bug Queries==<br />
====="Maybe Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20maybe%20good%20first%20bug These are tagged "contrib: maybe good first bug"]. We triage these and change the tag to "Good First Bugs" if determined to be good for new contributors.<br />
<br />
====="Good First Bugs" that need a mentor on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20good%20first%20bug,needs:%20mentor These are tagged "contrib: good first bug" and "needs: mentor"]. We triage these and add replace the "needs: mentor" label by "contrib: mentor assigned" after we decided on a mentor.<br />
<br />
====="Good First Bugs" that are assigned to a contributor on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20good%20first%20bug,contrib:%20assigned These are tagged "contrib: good first bug" and "contrib: assigned"]. We triage these and check-in with contributors on their progress and remove "contrib: assigned" after a longer period of inactivity or no response.<br />
<br />
====="Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20good%20first%20bug This is the query] contributors see. We should spot-check them to ensure they are properly triaged.<br />
<br />
=====WebExtensions Bugs on Bugzilla=====<br />
*These are WebExtensions bugs that [https://mzl.la/2tdJuSD don't have a mentor]<br />
*These are WebExtensions bugs that [https://mzl.la/2lmvVvx have an assignee but haven't been commented on for 3 weeks]<br />
<br />
=====Add-ons Manager Bugs on Bugzilla=====<br />
*These are Add-ons Manager bugs that [https://mzl.la/2pecPvR don't have a mentor]<br />
*These are Add-ons Manager bugs that [https://mzl.la/2oIyb30 have an assignee but haven't been commented on for 3 weeks]<br />
<br />
= Looking for the WebExtensions APIs triage wiki? = <br />
The [[https://wiki.mozilla.org/WebExtensions/Triage|WebExtensions APIs triage]] now has its own wiki! Please head over to [[https://wiki.mozilla.org/WebExtensions/Triage#Purpose_of_Meeting|wiki.mozilla/org/WebExtensions/Triage]] to stay up to date about the WebExtensions APIs triage. <br />
<br />
= Archive =<br />
=====2018=====<br />
[https://docs.google.com/document/d/1ZI6Hk9yenig4BXr6TnOl06KNFwnb0GtpvZXEkHjMbQY/edit# All meetings starting May 30, 2018]<br />
<br />
=====2017=====<br />
[https://docs.google.com/document/d/1MduEIKmXDdj3p94PJDrPPPYvbSfEdrrMF-UhMnHPqEQ/edit# November 28, 2017]<br /><br />
[https://docs.google.com/document/d/1g3RMfKZ3671NcusMqkoOiKwfPekRe-VI7Rzqxo6F_Ao/edit# November 14, 2017] <br /><br />
[https://docs.google.com/document/d/1qqE6fkqr-RNWaFvMpv0Z8O5FLDgQ3AT5eGdbTt7lRGg/edit# October 31, 2017]<br /><br />
[https://docs.google.com/document/d/1oUFGD57_NGbtV5y8k_yIS3GN8pFO3M_K1SWQhzlq6Ho/edit# October 17, 2017]<br /><br />
[https://docs.google.com/document/d/1X5RmNq2tGC5Aw3npIKqxB2vhnVhg9uOoXh2TggduTPU/edit#heading=h.hhpni8ijl0wx October 3, 2017]<br /><br />
[https://docs.google.com/document/d/1pw5y-GHwDLPV9bYK4HWCiZtslqFtAeL3G9bC4ZDbdjs/edit# September 26, 2017]<br /><br />
[https://docs.google.com/document/d/13gmYyN0qCjzV7YAsqGpbeeHr3al0yiWP7ayqKJPLS2w/edit#heading=h.hhpni8ijl0wx September 5, 2017]<br /><br />
[https://docs.google.com/document/d/11SdY-aRhvPU3SvH8jpj0covj3Teq9_GJl8wMeEeSVwo/edit# August 22, 2017]<br /><br />
[https://docs.google.com/document/d/1I-i1FQ38nwFHNl4hnzTctdsYHXOjJpeAgm1Bm3VoUUA/edit# August 8, 2017]<br /><br />
[https://docs.google.com/document/d/1l5zlSASqZAzzJGZhHtLWY1yaUwCKZiHXXGP1k_2W-TU/edit# August 1, 2017] - WebExtensions Only <br /><br />
[https://docs.google.com/document/d/1BBIZhiHG1zlQiu6744jiAYyWJLa-B0iRu9vzWypkvF4/edit# July 25, 2017] <br /><br />
[https://docs.google.com/document/d/1gWszBunGAyOJ_V8_HMECXJuZ4Gd_HTM_M7xjDSwSxeo/edit#heading=h.t2yykqfh2jii July 18, 2017] - WebExtensions only <br /><br />
[https://docs.google.com/document/d/1MEMC7EyZ2VVInbWod7FD2SFGp36osoxQkhUm5f0aNSs/edit# July 11, 2017] <br /><br />
[https://docs.google.com/document/d/1s2j85VfYKTDftppFU-K7pgRs6sEuMTHVXqf3RL5iYvs/edit# June 20, 2017] - WebExtensions only<br /><br />
[https://docs.google.com/document/d/1A_M0YD86Plcs6eHyM2KXkDXY074BHZ3fZvaWXCljQLI/edit# June 13, 2017] <br /><br />
[https://docs.google.com/document/d/1pTNjK5i_8gHt3EeiUiu5KCUVeRcfwn7ybCPDBSx6CLM/edit June 6, 2017 - WebExtensions only] <br /><br />
[https://docs.google.com/document/d/1hKKRpGFIaAaI3G_HfPX2Nk8pCchyhUIKJB9y5sIrVV4/edit# May 30, 2017] <br /><br />
[https://docs.google.com/document/d/1-j08Zo4sbwAuRZndNNtdIRlDM8TblddDA-PAeRgYMWU/edit#heading=h.du5ihvu5p6ro May 23, 2017] - WebExtensions only <br /><br />
[https://docs.google.com/document/d/1vrhHNOelBty4hXcjQ8VbFk-azHRFFDVyGka7H0VpEa8/edit# May 16, 2017] <br /><br />
[https://docs.google.com/document/d/1q7UD3DxsT5z0lO3EbOyF9Iln32Wg_e9LYMdHZ80BEb4/edit#heading=h.du5ihvu5p6ro May 9, 2017] - WebExtensions APIs only<br/><br />
[https://docs.google.com/document/d/1vf8AaW8tKKbMn4KhsqEYhrYqVTUGaERHQmzanEp2Cls/edit# May 2, 2017]<br /><br />
[https://docs.google.com/document/d/1WScwIH2D5tiL7vT4_lC44oFigR53xatWsUEwyjWvs7k/edit# April 25] - WebExtensions APIs only<br /><br />
[https://docs.google.com/document/d/1zKqhDqXoH9vi88q4DGtOHm1hsCF8ZwLNvCrrCE5htbc/edit# April 18, 2017]<br /><br />
[https://docs.google.com/document/d/1V4NP4tWnjHigS2lAosCLfkU2FTcrQnoQzzXZmmB1uzk/edit April 4, 2017]<br /><br />
[https://docs.google.com/document/d/1YbQGbkNWwVGvXgjzJ541s-d4AVImRLThMKnBM3Yo1Lw/edit#heading=h.t2yykqfh2jii March 28, 2017] - GFB only<br /><br />
[https://docs.google.com/document/d/1xM6iKOSGo9cDWw3ZA27PT-AVlx1Mvd79sxC6pYNhBqU/edit#heading=h.t2yykqfh2jii March 21, 2017]<br /><br />
[https://docs.google.com/document/d/1zzfedbTKAHUmm4UctxSOIJV3iKayXQ8TuXPodXW8wC0/edit#heading=h.sbitm9gruxfs March 7, 2017]<br /><br />
[https://docs.google.com/document/d/1H4sjnRFc87NZXZsM6XIgwWaoV2bdRFepiG28G7WzgPs/edit?usp=sharing Feb 21, 2017]<br /><br />
[https://docs.google.com/document/d/1X5OUNgpUcMLkHrOPbg-OLWSA2hzoRykRZd2gyTJ9vgU/edit# Feb 7, 2017]<br /><br />
[https://docs.google.com/document/d/1add-6FL8mzksvzbyB83HUmEkVmKERd-nt740AYr-4PE/edit# Jan 24, 2017]<br /><br />
[https://docs.google.com/document/d/18K97o1juaHSeYEkes1iMz8AayjuVkUuIK844ErGaa-c/edit?usp=sharing Jan 10, 2017]<br />
<br />
=====2016=====<br />
[https://docs.google.com/document/d/1S1QrBK1hrulE7dlLiQzjMupHUUSwDYRYAOXiqtMHe-k/edit?usp=sharing Dec 13, 2016]<br /><br />
[https://docs.google.com/document/d/1IMBFXHNpg_A-15VdJM1Hh8DUUXF1xNFy87W1w8ZEOBk/edit#heading=h.du5ihvu5p6ro Nov 29, 2016]<br /><br />
[https://docs.google.com/document/d/1cMvAtlIZpykpxZ0bG2J2lh7Mx1WcVfLrHSDJZHFvexc/edit Nov 15, 2016]<br /><br />
[https://docs.google.com/document/d/1i5CT821JFutWL-f3AZ3VhlYIIzulnMttjNp1JsYba8M/edit# Nov 1, 2016]<br /><br />
[https://docs.google.com/document/d/1elytPf_HqAqqFC6EM0-hrJp7kWJA-LfKILXV1tzNLTU/edit Oct 18, 2016]<br /><br />
[https://docs.google.com/document/d/1BDIbINMGgjoWlZxHmw-MnLm3HEqB38oUNTJUPAippGo/edit Oct 4, 2016]<br /><br />
[https://docs.google.com/document/d/1gABxxstInPy5XMsmoYMhZBMsLGFWNsgWMhgjUlt7-o8/edit Sept 20, 2016]<br /><br />
[https://docs.google.com/document/d/14cqCfgbyGoBXe7ttho0L3mIe4FcSSlzHH3L4fBFnLzA/edit Sept 6, 2016]<br /><br />
[https://docs.google.com/document/d/1GDpdcO1EHefRL3B5p5g1emdp_lY-YFWjwXv8YG1EgWo/edit August 23, 2016]<br /><br />
[https://docs.google.com/document/d/1rZvIfFILAHozLGTrg5C7Q7lXyEZ2gfMDw7cVkEo34io/edit August 9, 2016]<br /><br />
[https://docs.google.com/document/d/1A5hKaon2Z3nSCQc9ToYTOjr2cIpmmeZmu9EnbhVjHd0/edit July 26, 2016]<br /><br />
[https://docs.google.com/document/d/18wCqoUzNYshOWDjuJjePFivb4T5nD0WlFE06NKn3YQ0/edit July 12, 2016]<br /><br />
[https://docs.google.com/document/d/1uBo-WVFP2v-dyeYyDtfPD9ipN8JeIw7sCag4CYonQqY/edit# June 28, 2016]<br /><br />
[https://docs.google.com/document/d/1lYqcEWaktMXPmAefRB9PW9iSBM95rlVKFOO-vFRewdE/edit May 31, 2016]<br /><br />
[https://docs.google.com/document/d/1Bq7gTVhsGfTW58A9MUurruu5jc2w5OHSeaoRbmWRQV4/edit May 17, 2016]<br /><br />
[https://docs.google.com/document/d/1EkZXtIx7TkQxnFn_2ei3SR7j9xeDVc1WSl3suY2n8RU/edit April 28, 2016]<br /><br />
[https://docs.google.com/document/d/13yPW-ojA_jzXUe7_fxDvYQavsr5yEHZzHXXCMcuZgCA/edit April 14, 2016]<br /><br />
[https://docs.google.com/document/d/1hSABd9dd8UktXGJuf0iXn_8Fpuz09VEqkxrxMY_AvZw/edit Mar 31, 2016]<br /><br />
[https://docs.google.com/document/d/1ss0i_zAZDytsyBnMGF1gdRI6LjRWqvQS9Q0ueKzQV1Q/edit Mar 3, 2016]<br /><br />
[https://docs.google.com/document/d/1GkHWjHRDcUd7WD2BFF-6zhdyce4lK8qMX23O6C0eRIA/edit Feb 18, 2016]<br /><br />
[https://docs.google.com/document/d/1cM2JIIgw1i7TJe3oOojCtJvEhJoBGdHgNvjS2hRfBcw/edit Feb 4, 2016]<br /> <br />
[https://docs.google.com/document/d/1OZVV_HVXWAY-1u-nPhb4MrXOsycVFbXkXGEhhTomoaM/edit Jan 21, 2016]<br /><br />
[https://docs.google.com/document/d/1GwqhWsSsBp5vfLW7-5Di8_CzIfepwK9YVZAnQuLxK9I/edit Jan 7, 2016]<br />
<br />
=====2015=====<br />
[https://docs.google.com/document/d/18Csoja50IhnjqraFzxEYyVIJp-j79GLO2gCrvTSYHUI/edit Nov. 19, 2015]<br /><br />
[https://docs.google.com/document/d/1gbhL0S4amQ447ddIX7mEZsSaGoiFt8fTw22FKe_GbIo/edit Oct. 29, 2015]<br /><br />
[https://docs.google.com/document/d/1EoLSXHKCqJzTatj6CLLpjomwXnN5zUOA897brO_1aJQ/edit Oct. 15, 2015]<br />
<br />
=====Aug - Oct 2015=====<br />
https://drive.google.com/drive/folders/0B2aDMRMZ7uzvYzA4Wm1VYVhvemM<br />
<br />
=Onboarding information template=<br />
If this is your first contribution, please refer to https://wiki.mozilla.org/Add-ons/Contribute/Code on how to get started.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Projects&diff=1194985Add-ons/Projects2018-06-04T14:40:04Z<p>Jorge.villalobos: Status update</p>
<hr />
<div>These are projects that are being worked on in Add-ons.<br />
<br />
== Firefox/Quantum Platform ==<br />
<br />
=== Mission-critical technical needs ===<br />
; Remove support for unpacked extensions<br />
: The add-ons manager codebase currently support two separate code paths, one for unpacked and one for packed. This doubles the maintenance and testing burden, and unpacked, in particular, is prone to bugs and performance issues. It is no longer recommended on MDN. [targeting 62]<br />
<br />
; Telemetry improvements<br />
: Telemetry of the add-ons manager (about:addons) and performance of addons is currently incomplete. [targeting 62]<br />
<br />
=== New WebExtension APIs ===<br />
New WebExtension APIs help us promote standards and differentiate Firefox. Introducing new APIs continues the promise of the migration to Web Extensions.<br />
<br />
These are the confirmed and prioritized APIs, with their corresponding tentative target release version in parentheses:<br />
{| class="wikitable"<br />
|-<br />
! API !! target release<br />
|-<br />
| userScripts || 62<br />
|-<br />
| topSites || 62<br />
|-<br />
| desktopCapture (TBD) || 63<br />
|-<br />
| declarativeContent || 62<br />
|-<br />
| Session management || 63 (TBD)<br />
|-<br />
| Toolbars || 63 (TBD)<br />
|-<br />
| Overlays || 64 (TBD)<br />
|}<br />
<br />
* '''In discussion:''' color filter API<br />
* '''Future:''' link to prioritized backlog (in progress)<br />
* '''Future:''' link to long-term backlog (in progress)<br />
<br />
=== Continuation of migration to Extensions ===<br />
; Remove uses of bootstrapped extensions<br />
: Removing support for bootstrapped extensions continues the process that was begun when we removed support for arbitrary bootstrapped extensions (on release and beta) and allows for the removal of more unused code. The remainder of bootstrapped extensions should be converted to web extensions or achieve their aim some other way (these are primarily internal). [targeting 64]<br />
<br />
=== Security ===<br />
; Privacy Manifest Flags<br />
: We want to add support a number of privacy flags that developers can use to report the add-on's privacy practices to users. This would be set using the "privacy" key in the manifest, and would be displayed by the Add-on Manager. [targeting TBD, follows AMO]<br />
<br />
=== Performance improvements ===<br />
; Storage.local backend change to indexedDB<br />
: Improve performance and memory usage; also part of quantum flow. [targeting 62]<br />
<br />
=== Engineering improvements ===<br />
; Context menu improvements<br />
: Follow-on work for context menus and associated APIs. [targeting TBD (63 or 64)]<br />
<br />
; Resolve browser_style issues<br />
: The browser_style manifest key is unclear in how it relates to built-in themes, user themes, and how maintenance should extend to add-ons requirements which may or may not be present in extensions.css. [targeting TBD]<br />
<br />
; Improve support for incognito<br />
: There are outstanding issues with extensions, private browsing, and the incognito manifest key. [targeting 62]<br />
<br />
; Themes resolution<br />
: The introduction of static themes and the Theming API introduce a host of UX issues on AMO and in Firefox that depend on a more concrete definition of "themes" and constraints to the Theming API. This affects both sides of Add-ons, the Visuals team, and community. [targeting 63]<br />
<br />
; Delayed background startup pref'd on beyond Nightly<br />
: This fixes an issue with proxy and webRequest (at least), and results in extensions not needing to start during browser startup. [targeting 62]<br />
<br />
=== UI improvements ===<br />
; Tabs post-launch<br />
: Follow-on work from the release of Tab Hiding in 61 to complete visual indications and UI. [targeting 62]<br />
<br />
; UI for exposing how extensions change Firefox <br />
: As part of increasing awareness of extensions, we need to show users in the Firefox UI what extensions do to their browser after they are installed. This includes, but is not limited to, showing permissions, allowing optional permission control, showing command (keyboard shortcut) combinations, notifying of collisions, and allowing the user to override key functionality (search engine, home page, new tab), and more. [ongoing]<br />
<br />
=== Discoverability ===<br />
; Feed desired extension that triggered install to /firstrun<br />
: A substantial opportunity for add-on installation is to determine if a user installed Firefox from an AMO detail page. Add-ons users (whether new or pre-existing) retain at a higher rate than non-Add-ons users. [targeting 63]<br />
<br />
<br />
== addons.mozilla.org ==<br />
<br />
=== Mission-critical technical needs ===<br />
; <strike>AMO Salesforce integration<br />
: Legal requires integration basket API (for Salesforce) for about:addons newsletter signups. [targeting 2018.05.24]</strike><br />
<br />
; <strike>Serve JSON update manifests<br />
: In order to remove RDF support, updates must stop using RDF and start using JSON. JSON has been supported since 45, and RDF and JSON support complicates tests that need to be rewritten in order to remove support for legacy (non-restartless) add-ons. [targeting 2018.05.24]</strike><br />
<br />
; Hybrid Content Telemetry on the discovery pane<br />
: Legal requires that we remove uses of GA from Firefox, and while this is technically hosted on AMO, it is effectively in Firefox. [targeting 2018.06.28]<br />
<br />
; Data sync from PROD to DEV and STAGE<br />
: Out of date data continues to be a problem for testing on dev and stage in AMO, and a periodic, automated, safe, and selective sync will solve this.<br />
<br />
; Code review<br />
: Reviewers and staff need to be able to inspect any code submitted to AMO in order to respond to user or security complaints. The code and diff viewer for code review are based on libraries that aren't being actively maintained, and regularly require code changes in order to work.<br />
<br />
; Antispam - Akismet<br />
: There's a increasing amount of spam that is being manually removed from AMO. To combat this we can use Akismet's spam API to give an indication of whether any piece of UGC is spam or not; implementing this means we need to send all UGC to akismet.<br />
<br />
=== Continuation of migration to Extensions ===<br />
; Support Static Themes on AMO<br />
: AMO needs to support extension-based themes for developers, reviewers, and end users. This includes deprecating existing theme APIs and discontinue (XUL-based) complete themes. [targeting Q3]<br />
<br />
; Support static themes on frontend<br />
: Enable the presentation of static themes on AMO. [targeting Q3]<br />
<br />
; Theme Migration<br />
: Migrate lightweight themes to static themes. [targeting Q3]<br />
<br />
; WebExtensions Dictionaries<br />
: In order to move away from legacy packaging and legacy manifests, we should move dictionaries to WebExtensions packaging. <br />
<br />
; Dynamic Theme Classification<br />
: We need to make a distinction between two types of themes: static and dynamic. All themes should be shown under 'themes' on AMO, but we need to determine how a developer specifies that, submits it, and what precautions or limitations we should put in place to protect users as much as is reasonable and prudent.<br />
<br />
=== Continuation of migration to new front-end ===<br />
; Finish User Profile<br />
: This project is to track all the remaining tickets for adding the user profile page and user profile editing into the new frontend. [targeting 2018.06.28]<br />
<br />
=== Security ===<br />
; Two-factor auth for add-on devs<br />
: Bringing MFA to AMO to add more security around developer accounts that publish add-ons in order to prevent malicious content from being pushed to user browsers.<br />
<br />
; Privacy Manifest Flags<br />
: We want to add support a number of privacy flags that developers can use to report the add-on's privacy practices to users. This would be set using the "privacy" key in the manifest, and would be displayed on AMO.<br />
<br />
=== Engineering improvements ===<br />
; Support bigger screenshot uploads<br />
: In order to improve image quality on AMO, larger screenshots must be supported for upload. [targeting ?]<br />
<br />
; <strike>A/B Testing Framework<br />
: https://github.com/mozilla/addons-frontend/issues/4262<br />
In order to enable A/B testing on AMO, we need to implement a testing solution (existing, React-based).</strike><br />
<br />
; Finishing collections on user pages<br />
: A collection is list of add-ons curated by one or more users. This tracks a limited feature set that we are porting from the legacy site to the new one. [targeting 2018.06.28]<br />
<br />
=== UI improvements ===<br />
; Disco Pane Improvements<br />
: We believe that improving how we display and organize the content in discopane will result in more add-ons installs. This includes showing recommendations on discopage, UI changes, content strategy, etc.<br />
<br />
; New User Onboarding<br />
: Improve the experience of first-time visitors to AMO in order to encourage return visits and downloads.<br />
<br />
=== Discoverability ===<br />
; TAAR / Recommendations<br />
: ???<br />
<br />
; Tags<br />
: ???<br />
<br />
<br />
== web-ext ==<br />
<br />
[https://github.com/mozilla/web-ext Web-ext] is a command-line tool to assist developers in extension development and submission.<br />
<br />
<br />
== WebExtension browser API polyfill ==<br />
<br />
[https://github.com/mozilla/webextension-polyfill This polyfill] is for add-on developers that want to use a single codebase to create cross-browser extensions (e.g. Firefox ''and'' Chrome) using the Promise-based API that Firefox natively provides.<br />
<br />
<br />
== Add-ons Linter ==<br />
<br />
The [https://github.com/mozilla/addons-linter JavaScript-based Add-ons Linter] is used in AMO submission and web-ext to analyze developer code for errors, warnings, and constraints to ensure quality and security standards prior to submission and publication.<br />
<br />
<br />
== Marketing/Community Engagement ==<br />
<br />
=== Reduce engineering overhead ===<br />
; Admin tools, phase 1<br />
: In order to administer AMO, admins have to use a variety of disparate and unintegrated tools; this requires separate upkeep and privilege/permission schemes. This project unifies those tools and sets the stage for future content curation tools.<br />
<br />
; Curation tools<br />
: This admin tool will enable content curators to customize the AMO homepage using a set of pre-built homepage modules. This replaces the need for manual changes by engineering staff and grants content publishing control to content strategists and editorial/campaign managers.<br />
<br />
=== Growth opportunities ===<br />
; Non-fx Install Flow (ReturnToAMO)<br />
: Users who choose to install Firefox from an add-ons listing page (on AMO) currently dead-end having installed Firefox. Converting those users to add-ons users by presenting them with the ability to install the add-on whose page they installed from during their first run will increase both user population and retention.<br />
<br />
; AMO Rebranding<br />
: Create a brand for AMO that makes it easy for users to refer to it. Potentially retire the term "add-on" and focus on extensions and themes, which both resonate better with users and compete directly with Chrome.<br />
<br />
; AMO Rating and Review Flow<br />
: Add-on ratings are a critical feature on AMO, allowing users to tell the world about the usefulness of an add-on and share their experiences. They help users know which add-ons are higher quality, and give developers encouragement and feedback to continue their development. AMO needs a rating system that encourages and highlights legitimate ratings, and mitigates abuse by bad actors. Rating should be easy. Blocking and moderation of written review should be both effective and transparent.<br />
<br />
<br />
== Status reports (legacy) ==<br />
<br />
{{Special:PrefixIndex/Add-ons/Projects/}}</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Reviewers&diff=1194043Add-ons/Reviewers2018-05-17T16:06:50Z<p>Jorge.villalobos: Fixing a broken link</p>
<hr />
<div><br />
= Introduction =<br />
The Add-on Reviewer Team is a Mozilla community made up of add-on developers, theme designers, and add-ons enthusiasts who want to ensure that users, designers, and developers have a good experience with [https://addons.mozilla.org/en-US/firefox/ addons.mozilla.org] (AMO). <br />
<br />
[[File:Mozfest Review Team.jpg|frame|center]]<br />
<br />
<br />
== Add-on Reviewers ==<br />
[https://mozillians.org/group/addon-reviewers/ The Add-on Reviewer Team] is made up of add-on developers dedicated to the security and reliability of add-ons for Firefox. They review new and updated add-ons as part of the add-on post-review process to ensure that extensions listed on AMO comply with established add-on policies. <br />
<br />
==== Resources for Add-on Reviewers ====<br />
*[https://developer.mozilla.org/Add-ons/AMO/Policy Add-on Policies]<br />
*[[Add-ons/Reviewers/Guide|AMO Reviewer Guide]]<br />
*[[Add-ons/Reviewers/Peer_Mentor_Program|Peer Mentor Program]]<br />
*[[Add-ons/Reviewers/Recognition|Reviewer Recognition Program]]<br />
<br />
==== Become an Add-on Reviewer ==== <br />
Sorry, applications for add-on reviewers are currently closed. Please watch this page to learn when they have been re-opened. <br />
<br />
*[[Add-ons/Reviewers/Applying|How to become a reviewer]]<br />
<br />
== Content Reviewers == <br />
Content reviewers are add-on enthusiasts who help ensure that add-ons listed on AMO comply with Mozilla’s [https://www.mozilla.org/about/legal/acceptable-use/ Acceptable Use Policy] and are not spam. <br />
<br />
==== Resources for Content Reviewers ====<br />
* [[Add-ons/Reviewers/Content_Review_Guidelines#Guidelines_for_Content_Review|Content Guidelines & Review Process]]<br />
<br />
=== Become a Content Reviewer===<br />
To become an Content reviewer, you need to have read and understood our [[Add-ons/Reviewers/Content_Review_Guidelines#Guidelines_for_Content_Review|content guidelines]] and Mozilla’s [https://www.mozilla.org/about/legal/acceptable-use/ Acceptable Use Policy]. No technical experience is required. <br />
<br />
If you are interested in becoming a content reviewer, please [https://goo.gl/forms/Cr0qnk1JgZiglDqB2 fill out this form] to apply.<br />
<br />
== Theme Reviewers ==<br />
Theme reviewers are theme designers who ensure that themes submitted to AMO comply with Mozilla’s [https://www.mozilla.org/about/legal/acceptable-use/ Acceptable Use Policy]. <br />
<br />
==== Become a Theme Reviewer ==== <br />
Sorry, applications for theme reviewers are currently closed. Please watch this page to be notified when applications re-open. <br />
<br />
==Contact Us==<br />
You can contact us at the [irc://irc.mozilla.org/addon-reviewers #addon-reviewers] IRC channel (irc.mozilla.org). We also monitor the [https://discourse.mozilla-community.org/c/add-ons Add-ons Forum].<br />
<br />
== Meet Ups ==<br />
*Reviewer meetup at MozFest 2017 in London: [https://www.flickr.com/photos/mozamoteam/albums/72157690298325996 Photos]<br />
*A couple of members from the Add-ons team attended [https://fosdem.org/2017/ FOSDEM] in Brussels, Belgium in 2017.<br />
*Reviewer meetup at Mozlando 2015: [https://blog.mozilla.org/addons/files/2016/02/DSC_4087-e1454965785705.jpg Photo]<br />
*Reviewer meetup at MozFest 2014 in London: [https://www.flickr.com/photos/mozamoteam/sets/72157648969050906 Photos] and [https://mozamy.wordpress.com/2014/11/04/add-on-and-app-reviewer-meetup-at-mozfest-2014/ blog post]<br />
*Reviewer meetup at Summit 2013 in Brussels: [https://www.flickr.com/photos/mozamoteam/sets/72157655324482831 Photos]<br />
*Reviewer meetup MozCamp EU 2012 in Warsaw: [http://www.flickr.com/photos/mozamoteam/tags/amoeditormeetup/ Photos] and [https://blog.mozilla.org/addons/2012/09/17/mozcamp-2012-wrap-up/ blog post]</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=WebExtensions/Triage&diff=1189222WebExtensions/Triage2018-02-20T18:10:41Z<p>Jorge.villalobos: New new doc</p>
<hr />
<div>= Purpose of Meeting =<br />
Recurring triage sessions to accomplish these community goals:<br />
* Transparency: Decide whether APIs tagged "design-decision-needed" are "design-decision-approved" or "wontfix" to ensure transparency for the direction of WebExtensions. <br />
* Participation: Give guidance on and assign advisors to APIs marked "design-decision-approved" to make it easier for contributors to get involved.<br />
* Experiments: Discuss and provide feedback for [http://webextensions-experiments.readthedocs.io/en/latest/index.html WebExtensions Experiments].<br />
<br />
=Next Meeting=<br />
[https://docs.google.com/document/d/1-edU5RRFo2TupsOW400AcTOj8yyQnXd0F7uSsqkEzck/edit February 20, 2018]<br />
<br />
=Details & How to Join=<br />
* Every Tuesday at [http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 10:30am Pacific] (18:30 UTC)<br />
* Need help converting to your local time? [https://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 Click here].<br />
* Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU<br />
*IRC: [https://wiki.mozilla.org/IRC irc.mozilla.org], #Addons channel<br />
*To join from a telephone, dial one of the following numbers depending on your nearest location: <br />
**US Toll Free +1 800 707 2533, pin 369, conf 98960 <br />
**US/CA/Mountain View +1 650 903 0800, extension 2000, 8960<br />
**US/CA/San Francisco: +1 415 762 5700, extension 2000, 8960<br />
**US/OR/Portland: +1 971 544 8000, extension 2000, 8960 <br />
**CA/BC/Vancouver: +1 778 785 1540, extension 2000, 8960 <br />
**CA/ON/Toronto: +1 416 848 3114, extension 2000, 8960 <br />
**UK/London: +44 (0)207 855 3000, extension 2000, 8960<br />
**FR/Paris: +33 (0) 184 883 737, Press 1 for English or 2 for French, extension 2000, 8960 <br />
**DE/Berlin: +49 30 983 333 000, extension 2000, 8960<br />
**NZ/Auckland: +64 9 555 1100, extension 2000, 8960<br />
<br />
==About This Triage==<br />
* We normally spend 5 minutes per bug<br />
* The more information in the bug, the better<br />
* The goal of the triage is to give a general thumbs up or thumbs down on a proposal; we won't be going deep into implementation details<br />
* If you're interested in submitting a proposal for a new API, please read the [[WebExtensions/Vision|WebExtensions Vision]].<br />
<br />
==Triage Guidelines==<br />
Bugs marked "design-decision-needed" should be:<br />
*Tagged with "design-decision-approved" or "wontfix" (including reason)<br />
<br />
Bugs marked "design-decision-approved" should have:<br />
*Clear description of the API and suggested implementation if possible<br />
*Priority & impact<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code#Develop_Web_Extensions_APIs onboarding process]<br />
*Advisor<br />
<br />
==Bug Queries==<br />
====="design-decision-needed"=====<br />
These are determined from the Monday WebExtensions triage. They are APIs we [https://mzl.la/2edmiid need more discussion] on.<br />
<br />
====="design-decision-approved"=====<br />
These are APIs we would [https://mzl.la/2dVs5Ys like to have]. They should meet the triage criteria listed above.<br />
<br />
==WebExtensions Experiments==<br />
* Submit your [http://webextensions-experiments.readthedocs.io/en/latest/index.html WebExtensions Experiment] by opening an issue on the [https://github.com/web-ext-experiments/about/issues web-ext-experiments github repo].<br />
* Be sure to include the following in your issue: <br />
** Link to where your experiment is located<br />
** A quick overview of what it does<br />
** Any Bugzilla bugs that it might address<br />
** If you’d like to move your repository over to this organisation and we can create a repository for you<br />
* A comment will be added to the issue when your WebExtensions Experiment has been added to a meeting agenda.<br />
<br />
<br />
= Archive =<br />
=====2018=====<br />
[https://docs.google.com/document/d/1731b2kkN1wndNzVvo--5gwUcagbOSKGNYv4769r68NM/edit# February 6, 2018] <br /><br />
[https://docs.google.com/document/d/1x80jYXicAotNjlitY5RZDcSRpRM3lmaSHp_q4co4OEg/edit# January 30, 2018] <br /><br />
[https://docs.google.com/document/d/1Mc0h5OVd30WBjCORssdifZRXYQrk6WcTqX1cw6ADO9k/edit# January 23, 2018] <br /><br />
[https://docs.google.com/document/d/13AiUqFgtLsuJ17QjzUOQ7nBN1U_ZEO0yzMaHLLl0JKk/edit# January 16, 2018] <br /> <br />
[https://docs.google.com/document/d/15JYw3L1490dKbr6yTLz1uirH8rfhcSiLJCubSWDlnfs/edit#heading=h.edrw957gm8hg January 9, 2018] <br /><br />
<br />
=====2017=====<br />
[https://docs.google.com/document/d/1KwfTum8Ow5w4afPAOvShpu_d_MNtahhOIqL3-Em9lLc/edit#| December 19, 2017] <br /><br />
[https://docs.google.com/document/d/1vH4wqJJZt1jk-cpx5NOq67b1UNekeQog6bz2HFOHe5E/edit# December 5, 2017] <br /><br />
[https://docs.google.com/document/d/1MduEIKmXDdj3p94PJDrPPPYvbSfEdrrMF-UhMnHPqEQ/edit# November 28, 2017] <br /><br />
[https://docs.google.com/document/d/1g3RMfKZ3671NcusMqkoOiKwfPekRe-VI7Rzqxo6F_Ao/edit# November 14, 2017] <br /><br />
[https://docs.google.com/document/d/1qqE6fkqr-RNWaFvMpv0Z8O5FLDgQ3AT5eGdbTt7lRGg/edit# October 31, 2017]<br /><br />
[https://docs.google.com/document/d/1oUFGD57_NGbtV5y8k_yIS3GN8pFO3M_K1SWQhzlq6Ho/edit# October 17, 2017]<br /><br />
[https://docs.google.com/document/d/1X5RmNq2tGC5Aw3npIKqxB2vhnVhg9uOoXh2TggduTPU/edit#heading=h.hhpni8ijl0wx October 3, 2017]<br /><br />
[https://docs.google.com/document/d/1pw5y-GHwDLPV9bYK4HWCiZtslqFtAeL3G9bC4ZDbdjs/edit# September 26, 2017]<br /><br />
[https://docs.google.com/document/d/13gmYyN0qCjzV7YAsqGpbeeHr3al0yiWP7ayqKJPLS2w/edit#heading=h.hhpni8ijl0wx September 5, 2017]<br /><br />
[https://docs.google.com/document/d/11SdY-aRhvPU3SvH8jpj0covj3Teq9_GJl8wMeEeSVwo/edit# August 22, 2017]<br /><br />
[https://docs.google.com/document/d/1I-i1FQ38nwFHNl4hnzTctdsYHXOjJpeAgm1Bm3VoUUA/edit# August 8, 2017]<br /><br />
[https://docs.google.com/document/d/1l5zlSASqZAzzJGZhHtLWY1yaUwCKZiHXXGP1k_2W-TU/edit# August 1, 2017] - WebExtensions Only <br /><br />
[https://docs.google.com/document/d/1BBIZhiHG1zlQiu6744jiAYyWJLa-B0iRu9vzWypkvF4/edit# July 25, 2017] <br /><br />
[https://docs.google.com/document/d/1gWszBunGAyOJ_V8_HMECXJuZ4Gd_HTM_M7xjDSwSxeo/edit#heading=h.t2yykqfh2jii July 18, 2017] - WebExtensions only <br /><br />
[https://docs.google.com/document/d/1MEMC7EyZ2VVInbWod7FD2SFGp36osoxQkhUm5f0aNSs/edit# July 11, 2017] <br /><br />
[https://docs.google.com/document/d/1s2j85VfYKTDftppFU-K7pgRs6sEuMTHVXqf3RL5iYvs/edit# June 20, 2017] - WebExtensions only<br /><br />
[https://docs.google.com/document/d/1A_M0YD86Plcs6eHyM2KXkDXY074BHZ3fZvaWXCljQLI/edit# June 13, 2017] <br /><br />
[https://docs.google.com/document/d/1pTNjK5i_8gHt3EeiUiu5KCUVeRcfwn7ybCPDBSx6CLM/edit June 6, 2017 - WebExtensions only] <br /><br />
[https://docs.google.com/document/d/1hKKRpGFIaAaI3G_HfPX2Nk8pCchyhUIKJB9y5sIrVV4/edit# May 30, 2017] <br /><br />
[https://docs.google.com/document/d/1-j08Zo4sbwAuRZndNNtdIRlDM8TblddDA-PAeRgYMWU/edit#heading=h.du5ihvu5p6ro May 23, 2017] - WebExtensions only <br /><br />
[https://docs.google.com/document/d/1vrhHNOelBty4hXcjQ8VbFk-azHRFFDVyGka7H0VpEa8/edit# May 16, 2017] <br /><br />
[https://docs.google.com/document/d/1q7UD3DxsT5z0lO3EbOyF9Iln32Wg_e9LYMdHZ80BEb4/edit#heading=h.du5ihvu5p6ro May 9, 2017] - WebExtensions APIs only<br/><br />
[https://docs.google.com/document/d/1vf8AaW8tKKbMn4KhsqEYhrYqVTUGaERHQmzanEp2Cls/edit# May 2, 2017]<br /><br />
[https://docs.google.com/document/d/1WScwIH2D5tiL7vT4_lC44oFigR53xatWsUEwyjWvs7k/edit# April 25] - WebExtensions APIs only<br /><br />
[https://docs.google.com/document/d/1zKqhDqXoH9vi88q4DGtOHm1hsCF8ZwLNvCrrCE5htbc/edit# April 18, 2017]<br /><br />
[https://docs.google.com/document/d/1V4NP4tWnjHigS2lAosCLfkU2FTcrQnoQzzXZmmB1uzk/edit April 4, 2017]<br /><br />
[https://docs.google.com/document/d/1xM6iKOSGo9cDWw3ZA27PT-AVlx1Mvd79sxC6pYNhBqU/edit#heading=h.t2yykqfh2jii March 21, 2017]<br /><br />
[https://docs.google.com/document/d/1zzfedbTKAHUmm4UctxSOIJV3iKayXQ8TuXPodXW8wC0/edit#heading=h.sbitm9gruxfs March 7, 2017]<br /><br />
[https://docs.google.com/document/d/1H4sjnRFc87NZXZsM6XIgwWaoV2bdRFepiG28G7WzgPs/edit?usp=sharing Feb 21, 2017]<br /><br />
[https://docs.google.com/document/d/1X5OUNgpUcMLkHrOPbg-OLWSA2hzoRykRZd2gyTJ9vgU/edit# Feb 7, 2017]<br /><br />
[https://docs.google.com/document/d/1add-6FL8mzksvzbyB83HUmEkVmKERd-nt740AYr-4PE/edit# Jan 24, 2017]<br /><br />
[https://docs.google.com/document/d/18K97o1juaHSeYEkes1iMz8AayjuVkUuIK844ErGaa-c/edit?usp=sharing Jan 10, 2017]<br />
<br />
=====2016=====<br />
[https://docs.google.com/document/d/1S1QrBK1hrulE7dlLiQzjMupHUUSwDYRYAOXiqtMHe-k/edit?usp=sharing Dec 13, 2016]<br /><br />
[https://docs.google.com/document/d/1IMBFXHNpg_A-15VdJM1Hh8DUUXF1xNFy87W1w8ZEOBk/edit#heading=h.du5ihvu5p6ro Nov 29, 2016]<br /><br />
[https://docs.google.com/document/d/1cMvAtlIZpykpxZ0bG2J2lh7Mx1WcVfLrHSDJZHFvexc/edit Nov 15, 2016]<br /><br />
[https://docs.google.com/document/d/1i5CT821JFutWL-f3AZ3VhlYIIzulnMttjNp1JsYba8M/edit# Nov 1, 2016]<br /><br />
[https://docs.google.com/document/d/1elytPf_HqAqqFC6EM0-hrJp7kWJA-LfKILXV1tzNLTU/edit Oct 18, 2016]<br /><br />
[https://docs.google.com/document/d/1BDIbINMGgjoWlZxHmw-MnLm3HEqB38oUNTJUPAippGo/edit Oct 4, 2016]<br /><br />
[https://docs.google.com/document/d/1gABxxstInPy5XMsmoYMhZBMsLGFWNsgWMhgjUlt7-o8/edit Sept 20, 2016]<br /><br />
[https://docs.google.com/document/d/14cqCfgbyGoBXe7ttho0L3mIe4FcSSlzHH3L4fBFnLzA/edit Sept 6, 2016]<br /><br />
[https://docs.google.com/document/d/1GDpdcO1EHefRL3B5p5g1emdp_lY-YFWjwXv8YG1EgWo/edit August 23, 2016]<br /><br />
[https://docs.google.com/document/d/1rZvIfFILAHozLGTrg5C7Q7lXyEZ2gfMDw7cVkEo34io/edit August 9, 2016]<br /><br />
[https://docs.google.com/document/d/1A5hKaon2Z3nSCQc9ToYTOjr2cIpmmeZmu9EnbhVjHd0/edit July 26, 2016]<br /><br />
[https://docs.google.com/document/d/18wCqoUzNYshOWDjuJjePFivb4T5nD0WlFE06NKn3YQ0/edit July 12, 2016]<br /><br />
[https://docs.google.com/document/d/1uBo-WVFP2v-dyeYyDtfPD9ipN8JeIw7sCag4CYonQqY/edit# June 28, 2016]<br /><br />
[https://docs.google.com/document/d/1lYqcEWaktMXPmAefRB9PW9iSBM95rlVKFOO-vFRewdE/edit May 31, 2016]<br /><br />
[https://docs.google.com/document/d/1Bq7gTVhsGfTW58A9MUurruu5jc2w5OHSeaoRbmWRQV4/edit May 17, 2016]<br /><br />
[https://docs.google.com/document/d/1EkZXtIx7TkQxnFn_2ei3SR7j9xeDVc1WSl3suY2n8RU/edit April 28, 2016]<br /><br />
[https://docs.google.com/document/d/13yPW-ojA_jzXUe7_fxDvYQavsr5yEHZzHXXCMcuZgCA/edit April 14, 2016]<br /><br />
[https://docs.google.com/document/d/1hSABd9dd8UktXGJuf0iXn_8Fpuz09VEqkxrxMY_AvZw/edit Mar 31, 2016]<br /><br />
[https://docs.google.com/document/d/1ss0i_zAZDytsyBnMGF1gdRI6LjRWqvQS9Q0ueKzQV1Q/edit Mar 3, 2016]<br /><br />
[https://docs.google.com/document/d/1GkHWjHRDcUd7WD2BFF-6zhdyce4lK8qMX23O6C0eRIA/edit Feb 18, 2016]<br /><br />
[https://docs.google.com/document/d/1cM2JIIgw1i7TJe3oOojCtJvEhJoBGdHgNvjS2hRfBcw/edit Feb 4, 2016]<br /> <br />
[https://docs.google.com/document/d/1OZVV_HVXWAY-1u-nPhb4MrXOsycVFbXkXGEhhTomoaM/edit Jan 21, 2016]<br /><br />
[https://docs.google.com/document/d/1GwqhWsSsBp5vfLW7-5Di8_CzIfepwK9YVZAnQuLxK9I/edit Jan 7, 2016]</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=WebExtensions/Triage&diff=1189221WebExtensions/Triage2018-02-20T18:04:03Z<p>Jorge.villalobos: New doc</p>
<hr />
<div>= Purpose of Meeting =<br />
Recurring triage sessions to accomplish these community goals:<br />
* Transparency: Decide whether APIs tagged "design-decision-needed" are "design-decision-approved" or "wontfix" to ensure transparency for the direction of WebExtensions. <br />
* Participation: Give guidance on and assign advisors to APIs marked "design-decision-approved" to make it easier for contributors to get involved.<br />
* Experiments: Discuss and provide feedback for [http://webextensions-experiments.readthedocs.io/en/latest/index.html WebExtensions Experiments].<br />
<br />
=Next Meeting=<br />
[https://docs.google.com/document/d/1CXE_kCDJvFYJ7ybEa4osaSremwJNjRqL89RQzZdWGnk/edit February 20, 2018]<br />
<br />
=Details & How to Join=<br />
* Every Tuesday at [http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 10:30am Pacific] (18:30 UTC)<br />
* Need help converting to your local time? [https://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 Click here].<br />
* Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU<br />
*IRC: [https://wiki.mozilla.org/IRC irc.mozilla.org], #Addons channel<br />
*To join from a telephone, dial one of the following numbers depending on your nearest location: <br />
**US Toll Free +1 800 707 2533, pin 369, conf 98960 <br />
**US/CA/Mountain View +1 650 903 0800, extension 2000, 8960<br />
**US/CA/San Francisco: +1 415 762 5700, extension 2000, 8960<br />
**US/OR/Portland: +1 971 544 8000, extension 2000, 8960 <br />
**CA/BC/Vancouver: +1 778 785 1540, extension 2000, 8960 <br />
**CA/ON/Toronto: +1 416 848 3114, extension 2000, 8960 <br />
**UK/London: +44 (0)207 855 3000, extension 2000, 8960<br />
**FR/Paris: +33 (0) 184 883 737, Press 1 for English or 2 for French, extension 2000, 8960 <br />
**DE/Berlin: +49 30 983 333 000, extension 2000, 8960<br />
**NZ/Auckland: +64 9 555 1100, extension 2000, 8960<br />
<br />
==About This Triage==<br />
* We normally spend 5 minutes per bug<br />
* The more information in the bug, the better<br />
* The goal of the triage is to give a general thumbs up or thumbs down on a proposal; we won't be going deep into implementation details<br />
* If you're interested in submitting a proposal for a new API, please read the [[WebExtensions/Vision|WebExtensions Vision]].<br />
<br />
==Triage Guidelines==<br />
Bugs marked "design-decision-needed" should be:<br />
*Tagged with "design-decision-approved" or "wontfix" (including reason)<br />
<br />
Bugs marked "design-decision-approved" should have:<br />
*Clear description of the API and suggested implementation if possible<br />
*Priority & impact<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code#Develop_Web_Extensions_APIs onboarding process]<br />
*Advisor<br />
<br />
==Bug Queries==<br />
====="design-decision-needed"=====<br />
These are determined from the Monday WebExtensions triage. They are APIs we [https://mzl.la/2edmiid need more discussion] on.<br />
<br />
====="design-decision-approved"=====<br />
These are APIs we would [https://mzl.la/2dVs5Ys like to have]. They should meet the triage criteria listed above.<br />
<br />
==WebExtensions Experiments==<br />
* Submit your [http://webextensions-experiments.readthedocs.io/en/latest/index.html WebExtensions Experiment] by opening an issue on the [https://github.com/web-ext-experiments/about/issues web-ext-experiments github repo].<br />
* Be sure to include the following in your issue: <br />
** Link to where your experiment is located<br />
** A quick overview of what it does<br />
** Any Bugzilla bugs that it might address<br />
** If you’d like to move your repository over to this organisation and we can create a repository for you<br />
* A comment will be added to the issue when your WebExtensions Experiment has been added to a meeting agenda.<br />
<br />
<br />
= Archive =<br />
=====2018=====<br />
[https://docs.google.com/document/d/1731b2kkN1wndNzVvo--5gwUcagbOSKGNYv4769r68NM/edit# February 6, 2018] <br /><br />
[https://docs.google.com/document/d/1x80jYXicAotNjlitY5RZDcSRpRM3lmaSHp_q4co4OEg/edit# January 30, 2018] <br /><br />
[https://docs.google.com/document/d/1Mc0h5OVd30WBjCORssdifZRXYQrk6WcTqX1cw6ADO9k/edit# January 23, 2018] <br /><br />
[https://docs.google.com/document/d/13AiUqFgtLsuJ17QjzUOQ7nBN1U_ZEO0yzMaHLLl0JKk/edit# January 16, 2018] <br /> <br />
[https://docs.google.com/document/d/15JYw3L1490dKbr6yTLz1uirH8rfhcSiLJCubSWDlnfs/edit#heading=h.edrw957gm8hg January 9, 2018] <br /><br />
<br />
=====2017=====<br />
[https://docs.google.com/document/d/1KwfTum8Ow5w4afPAOvShpu_d_MNtahhOIqL3-Em9lLc/edit#| December 19, 2017] <br /><br />
[https://docs.google.com/document/d/1vH4wqJJZt1jk-cpx5NOq67b1UNekeQog6bz2HFOHe5E/edit# December 5, 2017] <br /><br />
[https://docs.google.com/document/d/1MduEIKmXDdj3p94PJDrPPPYvbSfEdrrMF-UhMnHPqEQ/edit# November 28, 2017] <br /><br />
[https://docs.google.com/document/d/1g3RMfKZ3671NcusMqkoOiKwfPekRe-VI7Rzqxo6F_Ao/edit# November 14, 2017] <br /><br />
[https://docs.google.com/document/d/1qqE6fkqr-RNWaFvMpv0Z8O5FLDgQ3AT5eGdbTt7lRGg/edit# October 31, 2017]<br /><br />
[https://docs.google.com/document/d/1oUFGD57_NGbtV5y8k_yIS3GN8pFO3M_K1SWQhzlq6Ho/edit# October 17, 2017]<br /><br />
[https://docs.google.com/document/d/1X5RmNq2tGC5Aw3npIKqxB2vhnVhg9uOoXh2TggduTPU/edit#heading=h.hhpni8ijl0wx October 3, 2017]<br /><br />
[https://docs.google.com/document/d/1pw5y-GHwDLPV9bYK4HWCiZtslqFtAeL3G9bC4ZDbdjs/edit# September 26, 2017]<br /><br />
[https://docs.google.com/document/d/13gmYyN0qCjzV7YAsqGpbeeHr3al0yiWP7ayqKJPLS2w/edit#heading=h.hhpni8ijl0wx September 5, 2017]<br /><br />
[https://docs.google.com/document/d/11SdY-aRhvPU3SvH8jpj0covj3Teq9_GJl8wMeEeSVwo/edit# August 22, 2017]<br /><br />
[https://docs.google.com/document/d/1I-i1FQ38nwFHNl4hnzTctdsYHXOjJpeAgm1Bm3VoUUA/edit# August 8, 2017]<br /><br />
[https://docs.google.com/document/d/1l5zlSASqZAzzJGZhHtLWY1yaUwCKZiHXXGP1k_2W-TU/edit# August 1, 2017] - WebExtensions Only <br /><br />
[https://docs.google.com/document/d/1BBIZhiHG1zlQiu6744jiAYyWJLa-B0iRu9vzWypkvF4/edit# July 25, 2017] <br /><br />
[https://docs.google.com/document/d/1gWszBunGAyOJ_V8_HMECXJuZ4Gd_HTM_M7xjDSwSxeo/edit#heading=h.t2yykqfh2jii July 18, 2017] - WebExtensions only <br /><br />
[https://docs.google.com/document/d/1MEMC7EyZ2VVInbWod7FD2SFGp36osoxQkhUm5f0aNSs/edit# July 11, 2017] <br /><br />
[https://docs.google.com/document/d/1s2j85VfYKTDftppFU-K7pgRs6sEuMTHVXqf3RL5iYvs/edit# June 20, 2017] - WebExtensions only<br /><br />
[https://docs.google.com/document/d/1A_M0YD86Plcs6eHyM2KXkDXY074BHZ3fZvaWXCljQLI/edit# June 13, 2017] <br /><br />
[https://docs.google.com/document/d/1pTNjK5i_8gHt3EeiUiu5KCUVeRcfwn7ybCPDBSx6CLM/edit June 6, 2017 - WebExtensions only] <br /><br />
[https://docs.google.com/document/d/1hKKRpGFIaAaI3G_HfPX2Nk8pCchyhUIKJB9y5sIrVV4/edit# May 30, 2017] <br /><br />
[https://docs.google.com/document/d/1-j08Zo4sbwAuRZndNNtdIRlDM8TblddDA-PAeRgYMWU/edit#heading=h.du5ihvu5p6ro May 23, 2017] - WebExtensions only <br /><br />
[https://docs.google.com/document/d/1vrhHNOelBty4hXcjQ8VbFk-azHRFFDVyGka7H0VpEa8/edit# May 16, 2017] <br /><br />
[https://docs.google.com/document/d/1q7UD3DxsT5z0lO3EbOyF9Iln32Wg_e9LYMdHZ80BEb4/edit#heading=h.du5ihvu5p6ro May 9, 2017] - WebExtensions APIs only<br/><br />
[https://docs.google.com/document/d/1vf8AaW8tKKbMn4KhsqEYhrYqVTUGaERHQmzanEp2Cls/edit# May 2, 2017]<br /><br />
[https://docs.google.com/document/d/1WScwIH2D5tiL7vT4_lC44oFigR53xatWsUEwyjWvs7k/edit# April 25] - WebExtensions APIs only<br /><br />
[https://docs.google.com/document/d/1zKqhDqXoH9vi88q4DGtOHm1hsCF8ZwLNvCrrCE5htbc/edit# April 18, 2017]<br /><br />
[https://docs.google.com/document/d/1V4NP4tWnjHigS2lAosCLfkU2FTcrQnoQzzXZmmB1uzk/edit April 4, 2017]<br /><br />
[https://docs.google.com/document/d/1xM6iKOSGo9cDWw3ZA27PT-AVlx1Mvd79sxC6pYNhBqU/edit#heading=h.t2yykqfh2jii March 21, 2017]<br /><br />
[https://docs.google.com/document/d/1zzfedbTKAHUmm4UctxSOIJV3iKayXQ8TuXPodXW8wC0/edit#heading=h.sbitm9gruxfs March 7, 2017]<br /><br />
[https://docs.google.com/document/d/1H4sjnRFc87NZXZsM6XIgwWaoV2bdRFepiG28G7WzgPs/edit?usp=sharing Feb 21, 2017]<br /><br />
[https://docs.google.com/document/d/1X5OUNgpUcMLkHrOPbg-OLWSA2hzoRykRZd2gyTJ9vgU/edit# Feb 7, 2017]<br /><br />
[https://docs.google.com/document/d/1add-6FL8mzksvzbyB83HUmEkVmKERd-nt740AYr-4PE/edit# Jan 24, 2017]<br /><br />
[https://docs.google.com/document/d/18K97o1juaHSeYEkes1iMz8AayjuVkUuIK844ErGaa-c/edit?usp=sharing Jan 10, 2017]<br />
<br />
=====2016=====<br />
[https://docs.google.com/document/d/1S1QrBK1hrulE7dlLiQzjMupHUUSwDYRYAOXiqtMHe-k/edit?usp=sharing Dec 13, 2016]<br /><br />
[https://docs.google.com/document/d/1IMBFXHNpg_A-15VdJM1Hh8DUUXF1xNFy87W1w8ZEOBk/edit#heading=h.du5ihvu5p6ro Nov 29, 2016]<br /><br />
[https://docs.google.com/document/d/1cMvAtlIZpykpxZ0bG2J2lh7Mx1WcVfLrHSDJZHFvexc/edit Nov 15, 2016]<br /><br />
[https://docs.google.com/document/d/1i5CT821JFutWL-f3AZ3VhlYIIzulnMttjNp1JsYba8M/edit# Nov 1, 2016]<br /><br />
[https://docs.google.com/document/d/1elytPf_HqAqqFC6EM0-hrJp7kWJA-LfKILXV1tzNLTU/edit Oct 18, 2016]<br /><br />
[https://docs.google.com/document/d/1BDIbINMGgjoWlZxHmw-MnLm3HEqB38oUNTJUPAippGo/edit Oct 4, 2016]<br /><br />
[https://docs.google.com/document/d/1gABxxstInPy5XMsmoYMhZBMsLGFWNsgWMhgjUlt7-o8/edit Sept 20, 2016]<br /><br />
[https://docs.google.com/document/d/14cqCfgbyGoBXe7ttho0L3mIe4FcSSlzHH3L4fBFnLzA/edit Sept 6, 2016]<br /><br />
[https://docs.google.com/document/d/1GDpdcO1EHefRL3B5p5g1emdp_lY-YFWjwXv8YG1EgWo/edit August 23, 2016]<br /><br />
[https://docs.google.com/document/d/1rZvIfFILAHozLGTrg5C7Q7lXyEZ2gfMDw7cVkEo34io/edit August 9, 2016]<br /><br />
[https://docs.google.com/document/d/1A5hKaon2Z3nSCQc9ToYTOjr2cIpmmeZmu9EnbhVjHd0/edit July 26, 2016]<br /><br />
[https://docs.google.com/document/d/18wCqoUzNYshOWDjuJjePFivb4T5nD0WlFE06NKn3YQ0/edit July 12, 2016]<br /><br />
[https://docs.google.com/document/d/1uBo-WVFP2v-dyeYyDtfPD9ipN8JeIw7sCag4CYonQqY/edit# June 28, 2016]<br /><br />
[https://docs.google.com/document/d/1lYqcEWaktMXPmAefRB9PW9iSBM95rlVKFOO-vFRewdE/edit May 31, 2016]<br /><br />
[https://docs.google.com/document/d/1Bq7gTVhsGfTW58A9MUurruu5jc2w5OHSeaoRbmWRQV4/edit May 17, 2016]<br /><br />
[https://docs.google.com/document/d/1EkZXtIx7TkQxnFn_2ei3SR7j9xeDVc1WSl3suY2n8RU/edit April 28, 2016]<br /><br />
[https://docs.google.com/document/d/13yPW-ojA_jzXUe7_fxDvYQavsr5yEHZzHXXCMcuZgCA/edit April 14, 2016]<br /><br />
[https://docs.google.com/document/d/1hSABd9dd8UktXGJuf0iXn_8Fpuz09VEqkxrxMY_AvZw/edit Mar 31, 2016]<br /><br />
[https://docs.google.com/document/d/1ss0i_zAZDytsyBnMGF1gdRI6LjRWqvQS9Q0ueKzQV1Q/edit Mar 3, 2016]<br /><br />
[https://docs.google.com/document/d/1GkHWjHRDcUd7WD2BFF-6zhdyce4lK8qMX23O6C0eRIA/edit Feb 18, 2016]<br /><br />
[https://docs.google.com/document/d/1cM2JIIgw1i7TJe3oOojCtJvEhJoBGdHgNvjS2hRfBcw/edit Feb 4, 2016]<br /> <br />
[https://docs.google.com/document/d/1OZVV_HVXWAY-1u-nPhb4MrXOsycVFbXkXGEhhTomoaM/edit Jan 21, 2016]<br /><br />
[https://docs.google.com/document/d/1GwqhWsSsBp5vfLW7-5Di8_CzIfepwK9YVZAnQuLxK9I/edit Jan 7, 2016]</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Hotfix&diff=1186439Add-ons/Hotfix2018-01-08T23:16:04Z<p>Jorge.villalobos: Updated contact info</p>
<hr />
<div>'''Please note: we are in the process of [https://wiki.mozilla.org/Add-ons/HotfixRemoval removing the Hotfix], you should be using a system or go faster add-on instead.'''<br />
<br />
The add-on hotfix is a tool used to ship changes to Firefox users that don't need to be distributed under the normal update mechanism. Examples of this are configuration changes that don't justify a point release, or changes that need to be pushed to users in older versions of Firefox.<br />
<br />
Hotfix updates are automatically pushed to all Firefox users (starting from version 11).<br />
<br />
==How to develop a new hotfix==<br />
<br />
'''Please note: we are in the process of [https://wiki.mozilla.org/Add-ons/HotfixRemoval removing the Hotfix], you should be using a system or go faster add-on instead.'''<br />
<br />
The code for the hotfixes is at https://hg.mozilla.org/releases/firefox-hotfixes/.<br />
<br />
A new hotfix will live in a top-level dir following the convention vYYYYMMDD.XX. You can start by copying one of the existing ones into a new folder. The version must be greater than the version of the previously released one. Don't forget to update the [http://hg.mozilla.org/releases/firefox-hotfixes/file/tip/README README] file (in the root srcdir) to include the bug number where the hotfix was developed and a description of what it does.<br />
<br />
Package the hotfix by running <code>HOTFIX=vYYYYMMDD.XX make package</code> in the root srcdir. This instruction can also be found in the [http://hg.mozilla.org/releases/firefox-hotfixes/file/tip/README README] file.<br />
<br />
Tips:<br />
* It's nicer to use <code>hg copy</code> to copy the folder so that the commit will display only the changes between the files.<br />
* Whenever we change a pref in a hotfix, we need to change the pref name in Firefox, otherwise users will get stuck with this custom value which won't be reset when Firefox updates<br />
<br />
== Testing the hotfix locally ==<br />
<br />
To test the hotfix locally, get the .xpi file and drag&drop it into Firefox's window.<br />
<br />
Things to look out for:<br />
<br />
* Test that the hotfix does what it is expected to do, obviously.<br />
* Test that the hotfix uninstalls itself after completing its task. Most of the hotfixes we've shipped so far performs an immediate task and uninstalls itself right afterwards, but there were some exceptions where it needs to remain installed until certain conditions are met.<br />
* Test the extension with the oldest Firefox version that it supports (minVersion), to make sure the code in the hotfix does not use any API or JS syntax that was introduced only on later versions.<br />
* Test on all target OSes.<br />
* Disable the strict compatibility checking and install the hotfix on an unsupported version to test that it does not perform its task, as expected. (The hotfix has code to check that it only runs on its target versions even with strictCompatiblity off).<br />
<br />
== Testing the hotfix on the staging server ==<br />
<br />
To test the hotfix on the staging server, get it signed and uploaded to addons.allizom.org. After that is done, do the following steps in a clean Firefox profile:<br />
<br />
If testing on a Firefox version earlier than 24, make sure you have the right signature fingerprint configured. See the Signatures section for more details.<br />
<br />
* Check if <code>extensions.hotfix.id</code> is set to firefox-hotfix@mozilla.org (it should be the default).<br />
* Set <code>extensions.logging.enabled</code> to true. This will log messages from the Add-ons Manager to the Console, and to stdout if in a debug build.<br />
* Set <code>extensions.update.interval</code> to 10.<br />
* In the pref <code>extensions.update.background.url</code> (<code>extensions.update.url</code> for Firefox < 13), change the ''versioncheck-bg.addons.mozilla.org'' part from the string with ''versioncheck.allizom.org''.<br />
* Restart Firefox and open the Add-ons Manager and the Console. Wait a while for the Add-ons Manager to check for updates (messages about it should show in the Console).<br />
** Note that there might be other pending update checks that will run before, for example an update check for the "default theme" add-on, with id={972ce4c6-7e08-4474-a285-3208198ce6fd}.<br />
** If the hotfix is not being downloaded, get the URL from the logs and check that the RDF returned at that URL contains information about the hotfix. To make this easier, see the update check section.<br />
** After a successful update check is performed, the hotfix should be downloaded and installed.<br />
* Check that the hotfix performed its action correctly.<br />
* Check that the pref <code>extensions.hotfix.lastVersion</code> was set to the correct version name of the hotfix being tested.<br />
* Check that the hotfix was not downloaded and installed to incompatible Firefox versions.<br />
* Check that it uninstalled itself after completing its task. If you have the Add-ons Manager tab open, you might need to close and re-open it for the hotfix to disappear.<br />
<br />
=== Signatures===<br />
<br />
The hotfix extension is signed and the Add-ons Manager will only install it if it matches a pinned signature, stored in the <code>extensions.hotfix.certs.1.sha1Fingerprint</code> pref.<br />
<br />
The signature has changed over time (in Firefox 16.0.2 and Firefox 24), and users with current installations were updated to the newer signatures through a hotfix itself ([https://bugzilla.mozilla.org/show_bug.cgi?id=803596 bug 803596] and [https://bugzilla.mozilla.org/show_bug.cgi?id=874513 bug 874513]).<br />
<br />
This means that a clean profile from Firefox 10 - 23 won't have the right signature from start, and it needs to be updated to proceed with the testing. The current correct value for the pref is <code>91:53:98:0C:C1:86:DF:47:8F:35:22:9E:11:C9:A7:31:04:49:A1:AA</code><br />
===Triggering the update check===<br />
<br />
To not wait on the update interval and manually trigger the update check, you can run the following code snippet. Please only do this when debugging things or when there's plenty of evidence that the timer update trigger is working properly.<br />
<br />
<pre><br />
Components.utils.import("resource://gre/modules/AddonManager.jsm");<br />
AddonManagerPrivate.backgroundUpdateCheck();<br />
</pre><br />
<br />
Run this in a privileged script context, such as the Browser Console or Scratchpad set to the Browser environment.<br />
<br />
== Deployment ==<br />
<br />
'''Please note: we are in the process of [https://wiki.mozilla.org/Add-ons/HotfixRemoval removing the Hotfix], you should be using a system or go faster add-on instead.'''<br />
<br />
# The intent to ship a new hotfix needs to be sent to release-drivers@m.o and moc@m.c by the developer, by a release manager, or by someone from the AMMO team ([https://mail.mozilla.org/private/release-drivers/2015-August/029924.html Example 1], [https://mail.mozilla.org/private/release-drivers/2015-September/030005.html Example 2] - Needs access to the r-d archives)<br />
# Bug is filed ([https://bugzilla.mozilla.org/show_bug.cgi?id=1244321 Example 1], [https://bugzilla.mozilla.org/show_bug.cgi?id=1237209 Example 2])<br />
# File a new bug in addons.mozilla.org::Administration, and assign it to the Add-ons team for signing and staging. (:theone or :jorgev, otherwise contact the ACE team, ace-team@m.c) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1196078 Example 1], [https://bugzilla.mozilla.org/show_bug.cgi?id=1201129 Example 2]) with the following instructions (replace vYYYYMMDD.NN with the hotfix version):<br />
#:To generate the hotfix XPI, do the following:<br />
#: <br/><br />
#:hg clone https://hg.mozilla.org/releases/firefox-hotfixes<br />
#:cd firefox-hotfixes<br />
#:HOTFIX=vYYYYMMDD.NN make package<br />
#: <br/><br />
#:Then sign the xpi generated at build/hotfix-vYYYYMMDD.NN.xpi<br />
#: <br/><br />
#:Please deploy to addons-dev.allizom.org for QA<br />
# File is signed and is attached to the signing bug.<br />
# Signed file is uploaded to [https://addons-dev.allizom.org/firefox/addon/firefox-hotfix/ addons-dev.allizom.org] and published.<br />
# Bug is reassigned to QA for testing.<br />
# QA signs off, hotfix owner signs off, release management signs off.<br />
# Bug is reassigned to Add-ons team for final deployment.<br />
# Add-ons team notifies release-drivers@m.o and moc@m.c about the deployment, including bug number.<br />
# Signed file is uploaded to [https://addons.mozilla.org/firefox/addon/firefox-hotfix/ addons.mozilla.org] and published.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Blocklisting/Testing&diff=1184379Blocklisting/Testing2017-11-17T20:55:20Z<p>Jorge.villalobos: Updated testing info</p>
<hr />
<div>= Testing Staged Blocklist =<br />
<br />
To test a staged block:<br />
<br />
# Go to about:config, find the <code>extensions.blocklist.url</code> pref and change the <code>https://blocklists.settings.services.mozilla.com/v1/blocklist/</code> part of the value to <code>https://settings.prod.mozaws.net/v1/preview/</code><br />
<br />
= Forcing a Blocklist Ping =<br />
<br />
# In Firefox 30 and above, you must first enable chrome debugging<br />
#* Open the debugging tools (Tools Menu > Web Developer > Web Console) on Windows -> ALT key to expose the menu bar.<br />
#* Open the Options Panel (Gear icon on the developer tools toolbar, left of the Console Tab)<br />
#* Find and check Advanced Settings > Enabled chrome debugging<br />
#** You can also enabled chrome debugging via the <code>devtools.chrome.enabled</code> preference under about:config<br />
#* Restart Firefox<br />
# Open Browser Console (Tools > Web Developer > Browser Console)<br />
# Paste and run this snippet:<br />
Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsITimerCallback).notify(null);<br />
<br />
= Testing Graphics Blocklist entries =<br />
<br />
(Note: this only applies to Windows.)<br />
<br />
# If the blocklist entry is on staging, see above for testing a staged blocklist first.<br />
# Ensure you're currently hardware accelerated by opening about:support and looking at the Graphics section. Check that you have:<br />
## Direct2D true (if on Windows 7 or Vista with the platform update)<br />
## Hardware accelerated windows 1/1 Direct3D 9 (or 10)<br />
# Force a blocklist ping, as above.<br />
# Wait 5 seconds.<br />
# Restart your browser.<br />
# Open about:support and look at the Graphics section again. Ensure that:<br />
## Direct2D is false<br />
## Hardware accelerated windows 0/1<br />
<br />
= Quickly Checking Features =<br />
In addition to the above section, features can also be checked for disabled/enabled status by the following:<br />
<table width="100%" border="1"><br />
<tr><br />
<th>Feature</th><br />
<th>Enabled</th><br />
<th>Disabled</th><br />
</tr><br />
<tr><br />
<td>Direct2D (Windows)</td><br />
<td>about:support will show "Direct2D Enabled: true"</td><br />
<td>about:support will show "Direct2D Enabled: false"</td><br />
</tr><br />
<tr><br />
<td>Direct3D 9 Layers (Windows)</td><br />
<td>about:support will show "GPU Accelerated Windows: 2/2 Direct3D 9" *if it says Direct3D 10, this is not possible to test on this setup</td><br />
<td>about:support will show "GPU Accelerated Windows: 0/2" and will not list the rendering API</td><br />
</tr><br />
<tr><br />
<td>Direct3D 10 Layers (Windows)</td><br />
<td>about:support will show "GPU Accelerated Windows: 2/2 Direct3D 10" *if it says Direct3D 9, this is not possible to test on this setup</td><br />
<td>about:support will show "GPU Accelerated Windows: 0/2" and will not list the rendering API</td><br />
</tr><br />
<tr><br />
<td>Direct3D 10.1 Layers (Windows)</td><br />
<td>about:support will show "GPU Accelerated Windows: 2/2 Direct3D 10" *if it says Direct3D 9, this is not possible to test on this setup</td><br />
<td>about:support will show "GPU Accelerated Windows: 0/2" and will not list the rendering API</td><br />
</tr><br />
<tr><br />
<td>OpenGL Layers (Android, Linux, Mac)</td><br />
<td>about:support will show "GPU Accelerated Windows: 1/1 OpenGL"</td><br />
<td>about:support will show "GPU Accelerated Windows: 0/1" and will not list the rendering API</td><br />
</tr><br />
<tr><br />
<td>WebGL, OpenGL Variant (Android, Linux, Mac, sometimes Windows)</td><br />
<td>about:support will show "WebGL Renderer: <your renderer>" and it will not contain anything about being blocked for a driver version or similar messages *NOTE: if it contains the word "ANGLE" on windows, it is NOT using OpenGL, even if after that it says "OpenGL ES 2.0" or some such</td><br />
<td>about:support will show "WebGL Renderer: <some error>" which contains some information about why the renderer is blocked</td><br />
</tr><br />
<tr><br />
<td>WebGL, ANGLE Variant (Windows)</td><br />
<td>about:support will show "WebGL Renderer: ANGLE( <your render> )" and will not contain anything about being blocked for a driver version or similar messages. *NOTE: DO NOT assume that if it says "OpenGL ES 2.0" or some such that it is using OpenGL; the only important thing is that it says "ANGLE"</td><br />
<td>about:support will show "WebGL Renderer: <some error>" which contains some information about why the renderer is blocked</td><br />
</tr><br />
<tr><br />
<td>WebGL MSAA</td><br />
<td>Go to https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/sdk/demos/mozilla/spore/index.html and compare the model to [[media:msaa_comparison.png|this reference]]; if it looks like the left image, MSAA is enabled.</td><br />
<td>Go to https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/sdk/demos/mozilla/spore/index.html and compare the model to [[media:msaa_comparison.png|this reference]]; if it looks like the right image, MSAA is disabled. *NOTE: this is not a scientific test. MSAA may be disabled but you cannot be certain that it's blocked. the card could simply not support it. the best way to be sure is to download a utility that checks your GPU's available extensions and if antialiasing is not in that list, it is simply not supported</td><br />
</tr><br />
</table><br />
*NOTE: Direct3D 10 and Direct3D 10.1 are impossible to distinguish visually.<br />
<br />
== Spoofing Hardware Details for Blocklist Testing ==<br />
<br />
Sometimes you don't have hardware or software available to test a given blocklist entry. On Windows, you can spoof your hardware and software details to the graphics blacklist using environment variables.<br />
<br />
<!-- suck it mediawiki --><br />
<table width="100%" border="1"><br />
<tr><br />
<th>Environment Variable</th><br />
<th>Sample Value(s)</th>r<br />
<th>Meaning</th><br />
</tr> <br />
<tr><br />
<td>'''MOZ_GFX_SPOOF_DRIVER_VERSION'''</td> <br />
<td>8.17.18.2563</td> <br />
<td>The version of the driver you want to spoof.</td> <br />
</tr><br />
<tr><br />
<td>'''MOZ_GFX_SPOOF_VENDOR_ID'''</td> <br />
<td>0x1002</td> <br />
<td>The PCI vendor ID of the card you want to spoof.</td> <br />
</tr><br />
<tr><br />
<td>'''MOZ_GFX_SPOOF_DEVICE_ID'''</td> <br />
<td>0x3245</td> <br />
<td>The PCI device ID of the card you want to spoof.</td> <br />
</tr><br />
<tr><br />
<td>'''MOZ_GFX_SPOOF_WINDOWS_VERSION'''</td> <br />
<td><br />
<table width="100%" border="1"><br />
<tr><td>Windows 2000</td><td>0x50000</td></tr><br />
<tr><td>Windows XP</td><td>0x50001</td></tr><br />
<tr><td>Windows Server 2003</td><td>0x50002</td></tr><br />
<tr><td>Windows Vista</td><td>0x60000</td></tr><br />
<tr><td>Windows 7</td><td>0x60001</td></tr><br />
</table><br />
</td> <br />
<td>The numeric ID of the Windows version you want to spoof.</td> <br />
</tr><br />
</table><br />
<br />
= Testing on Android =<br />
Testing on Android is somewhat different than other platforms, especially for the downloadable blocklist. There's no way to force a ping, so the best way to do it is to set the automatic ping interval very low and wait. Here are some settings you should use which are set in about:config:<br />
<br />
# "Reset" app.update.lastUpdateTime.blocklist-background-update-timer<br />
# Make sure extensions.blocklist.enabled is true (should default this way)<br />
# Set extensions.blocklist.interval to 10<br />
# "Reset" extensions.blocklist.pingCountTotal<br />
# "Reset" extensions.blocklist.pingCountVersion<br />
# <strike>Set extensions.blocklist.url to the following to block Nexus S devices from using WebGL: http://people.mozilla.org/~dsherk/blocklist-nexus_s.xml *NOTE: this is just a way to test it. To test blocking on other devices, you will have to write up your own xml file.</strike><br />
<br />
Note that, even though the interval is set to 10, it can take several minutes for it to ping. I've found that closing Fennec (by opening the menu and hitting Quit, not just hitting the Home button) and re-opening it makes it ping shortly after start.<br />
<br />
= Logging States =<br />
Enable logging to help debug via the browser console:<br />
* open a new tab and type '''about:config''' into the URL<br />
* change the <code>extensions.logging.enabled</code> preference from <code>false</code> to <code>true</code><br />
* open the browser console using the steps from [[Blocklisting/Testing#Forcing_a_Blocklist_Ping|Forcing a Blocklist Ping]] and force a ping<br />
<br />
You'll receive similar output via the browser console:<br />
<br />
Blocklist state for firefox-devedition@mozilla.org@personas.mozilla.org changed from 0 to 0<br />
Blocklist state for Shockwave Flash changed from 0 to 4<br />
<br />
The definitions of each state can be found in the following [https://mxr.mozilla.org/mozilla-central/source/xpcom/system/nsIBlocklistService.idl#15 source file]<br />
<br />
= Upgrade Testing =<br />
Check when the blocklist was implemented and which version it was implemented. Verify that upgrading to the newest version will not cause an issue.<br />
[ outcome from {{bug|838845}} ]<br />
<br />
= Flash (Downloading/Uninstalling) =<br />
<br />
* [https://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html Flash Download Archives]<br />
* [https://helpx.adobe.com/flash-player/kb/uninstall-flash-player-windows.html Uninstalling Flash on Windows]<br />
* [https://helpx.adobe.com/flash-player/kb/uninstall-flash-player-mac-os.html Uninstalling Flash on OSX]<br />
<br />
= Java (Downloading/Installing/Uninstalling) = <br />
<br />
'''Note:''' Currently only x86 versions of JRE work with FX, JRE x64 builds will not appear under about:addons or about:plugins [07/15/2015]<br />
<br />
* [http://www.oracle.com/technetwork/java/archive-139210.html Oracle Download Archives]<br />
* [https://www.java.com/en/download/help/mac_uninstall_java.xml Uninstalling Java on OSX]<br />
* [https://www.java.com/en/download/help/linux_install.xml Installing/Uninstalling Java Plugin on Linux]<br />
<br />
= Silverlight (Downloading) =<br />
<br />
Quick guide on downloading older versions of Silverlight:<br />
<br />
* View the [https://www.microsoft.com/getsilverlight/locale/en-us/html/Microsoft%20Silverlight%20Release%20History.htm Silverlight Release History]<br />
* Click on the version of Silverlight that you would like to download<br />
** in this example, we'll use '''Silverlight 5 Build 5.1.41105.0 Released December 8, 2015'''<br />
* Click on the "Knowledge Base" link for the version you would like to download (Example: KB3106614)<br />
* Once the knowledge base page is opened, look under '''How to obtain and install the update'''<br />
* Click on the Microsoft Security Bulletin link that's provided under "Method 2: Microsoft Download Center"<br />
* This will take you to a '''Microsoft Security Bulletin''' page that includes the download links to the appropriate version of Silverlight</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Disable_Thunderbird_and_SeaMonkey_Compatibility&diff=1183731Add-ons/Disable Thunderbird and SeaMonkey Compatibility2017-11-08T17:51:09Z<p>Jorge.villalobos: Compat removal instructions for mass dev communication</p>
<hr />
<div>Legacy add-on listings on AMO (addons.mozilla.org) can be compatible with multiple applications, like Firefox, Thunderbird, and SeaMonkey. In order to disable compatibility with Thunderbird and SeaMonkey for your add-on, follow these steps:<br />
<br />
# Go to the [https://addons.mozilla.org/developers/addons Developer Hub].<br />
# Click on "Edit Information" for your add-on.<br />
# Then click on "Manage Status & Versions" on the sidebar menu.<br />
# For each version listed on that page:<br />
## Click on its link to go to its details page.<br />
## In the Compatibility section, remove Thunderbird and SeaMonkey compatibility by clicking on the X to the right, and then click on Save Changes at the bottom of the page.<br />
<br />
Once all versions have been cleared of Thunderbird and SeaMonkey compatibility, your add-on should no longer be considered compatible with those applications by AMO. The files can still be installed on those applications if the users choose to.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2017-09-25&diff=1181188WeeklyUpdates/2017-09-252017-09-25T16:49:30Z<p>Jorge.villalobos: /* Speakers */</p>
<hr />
<div><br />
{{WeeklyUpdateNav}}<br />
* Every Monday @ 11:00am Pacific Time (19:00 UTC) <br />
* https://air.mozilla.org/channels/project-meeting/ to watch and listen<br />
* join irc.mozilla.org #airmozilla for backchannel discussion<br />
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak. <br />
{{conf|8600}}<br />
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br />
* Thanks to Tech Speakers Anjana, Mijanur, Nikita, Rizky, Sumanth, Srushtika, Shagufta, Vigneshwer who spoke over the weekend at conferences & events in Germany, Malaysia, Siberia, Indonesia, Singapore, Poland, and India, including Mozilla's Dev Roadshow events in Southeast Asia this weekend....<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
* [[Add-ons/Community/Meetings|Add-ons Community Meeting]]<br />
** 17:00 - 17:30 UTC (10am - 10:30 Pacific) | ACE Vidyo Room<br />
* [[Add-ons/Contribute/Triage|WebExtensions APIs Triage Meeting]]<br />
** 17:30 - 18:00 UTC (10:30 - 11am Pacific) | ACE Vidyo Room<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
*SUMO Day Firefox 56 [https://support.mozilla.org/en-US/kb/social-support-guidelines Social] and in the [https://support.mozilla.org Support Forums]: <br />
**Sign up today: [https://public.etherpad-mozilla.org/p/sumo-day Etherpad with all the details] and see you there! <br />
**Curious about how support works at mozilla? Contact guigs@mozilla.com<br />
**Who the heck is SUMO?[https://support.mozilla.org/en-US/get-involved Read more here]<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br />
<br />
=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
== Speakers ==<br />
<br />
The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! [https://mozillians.org/u/USERNAME Presenter]<br />
! Title<br />
! Topic<br />
! Location<br />
! Sharing<br />
! Media<br />
! More Details<br />
|-<br />
| Who Are You?<br />
| What Do You Do?<br />
| What are you going to talk about?<br />
| Where are you presenting from? (Moz Space, your house, space)<br />
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
| Amy Schapiro<br />
| Senior Manager, Fellowship Programs<br />
| Mozilla's newest Fellow cohorts<br />
| Toronto<br />
| No<br />
| --<br />
| Blog post: [https://blog.mozilla.org/blog/2017/09/13/mozilla-announces-15-new-fellows-science-advocacy-media/ Mozilla Announces 15 New Fellows for Science, Advocacy, and Media]<br />
|-<br />
| Brett Gaylor<br />
| Advocacy media at the Foundation<br />
| Paperstorm comes to the U.S.<br />
| Toronto<br />
| Yes<br />
| [https://docs.google.com/presentation/d/1qd1WynzcxwlQ7ObFefdU0kqG6a8Q9xSeMWhisWJnO4c/edit#slide=id.p Slides]<br />
| https://paperstorm.it/<br />
|-<br />
| Kadir Topal<br />
| Senior Product Manager, MDN<br />
| Emerging Technologies Weekly Update <br />
| Remote<br />
| No<br />
| NA<br />
| https://wiki.mozilla.org/WeeklyUpdates/EmergingTechnology<br />
|-<br />
| Michael Van Kleeck<br />
| Enterprise Solutions Architect<br />
| The Weekly MinIT! <br />
| PDX<br />
| No<br />
| n/a<br />
| Weekly MinIT now at https://wiki.mozilla.org/IT/WeeklyMinIT<br />
|-<br />
| Shyam Mani<br />
| Manager, Web Operations<br />
| We're here to help! <br />
| SFO<br />
| Yes<br />
| [https://docs.google.com/presentation/d/139fMwecgwbzObNkjcEtvmzGzKaxW8pOzeeQ914XKJ9A/edit Slides] <br />
| N/A<br />
|-<br />
| Scott Idler<br />
| Senior Devops Engineer<br />
| DevOps Cohort @ Mozilla <br />
| Remote<br />
| No<br />
| N/A <br />
| [https://mana.mozilla.org/wiki/display/DO/DevOps+Cohort DevOps Cohort] [https://mana.mozilla.org/wiki/display/DO/Best+Practices Best Practices] <br />
|-<br />
| Asa Dotzler<br />
| Firefox Roadmap<br />
| Firefox Weekly Update<br />
| MTV<br />
| No<br />
| n/a<br />
| https://wiki.mozilla.org/Firefox/Roadmap/Updates#2017-09-25<br />
|-<br />
| Amy Tsay<br />
| Add-on product manager<br />
| Extension Finder utility<br />
| MTV<br />
| No<br />
| n/a<br />
| https://mozilla.github.io/extension-finder/<br />
|-<br />
| Jorge Villalobos<br />
| AMO Product Manager<br />
| Reducing add-on review wait times<br />
| Remote<br />
| No<br />
| n/a<br />
| https://blog.mozilla.org/addons/2017/09/21/review-wait-times-get-shorter/<br />
|-<br />
| John Gruen<br />
| Firefox Screenshots<br />
| Hey, we're launching Screenshots<br />
| NYC<br />
| Yes<br />
| n/a<br />
| https://screenshots.firefox.com<br />
|-<br />
| Lizz Noonan<br />
| Diversity and Inclusion<br />
| TechWomen 2017<br />
| SF<br />
| No<br />
| https://youtu.be/KAZnVdz282Q<br />
| https://www.techwomen.org/<br />
|-<br />
|}<br />
<br />
= Welcome! =<br />
<br />
Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! ''Who is being introduced?''<br />
! ''Who are you? (the introducer)''<br />
! ''Where are you doing the introduction?''<br />
! ''Where are they from?''<br />
! ''How will they be part of Mozilla?''<br />
|-<br />
<!-- Insert new rows here --><br />
|[https://mozillians.org/u/jteh/ James Teh]<br />
|David Bolter<br />
|Toronto Office<br />
|Brisbane, Australia<br />
|Working on the accessibility engineering team!<br />
|-<br />
|Chris Valaas<br />
|Vyas Swaminathan<br />
|San Francisco Office<br />
|Portland Office<br />
|Data Operations Engineer<br />
|-<br />
|}<br />
<br />
= Fireside Chat =<br />
A chance to hear from leadership at Mozilla, and have a short Q&A about a specific topic.<br />
<br />
===This Week===<br />
<br />
'''Name''', "Title"<br />
<br />
===Topics===<br />
<br />
You can submit questions in advance on the Moderator page (link), or ask them live on Air Mozilla using a Mozilla Space mic or in #airmozilla on IRC.<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Salesforce&diff=1170915Add-ons/Salesforce2017-05-10T22:39:51Z<p>Jorge.villalobos: First version, some basic reporting stuff</p>
<hr />
<div>=How to access=<br />
* Go to https://sso.mozilla.com/salescloud<br />
* If you can't access it and think you should, ask shell<br />
= How to create a report=<br />
# Click on Reports in toolbar.<br />
# Click on New Report...<br />
# Under Select Report Type, select Accounts & Contacts > AMO Developer Contacts w DevAddOn<br />
# Drag the fields to use for filtering from the sidebar to the filters section.<br />
# Always include the AMO Developer? field, set to "Yes"<br />
# Drag the fields to display in the report to the preview section.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Extension_Signing&diff=1169627Add-ons/Extension Signing2017-04-27T22:56:32Z<p>Jorge.villalobos: Adding Dev Edition back, after confirmation we will still support unsigned add-ons there</p>
<hr />
<div>Mozilla requires all extensions to be signed by Mozilla in order for them to be installable in Release and Beta versions of Firefox. Extensions submitted on [https://addons.mozilla.org/ addons.mozilla.org (AMO)] are signed as part of the review process, and a [http://addons-server.readthedocs.io/en/latest/topics/api/signing.html signing service] is also offered. Additional information on the extension submission and signing process is [https://developer.mozilla.org/en-US/Add-ons/Distribution available on MDN].<br />
<br />
== Algorithm ==<br />
<br />
Extension signing is controlled by Mozilla and requires access to a private signing infrastructure exposed by [https://addons.mozilla.org/ AMO], and internal services like [https://github.com/mozilla-services/autograph Autograph].<br />
<br />
Add-ons and Extensions are XPI files (zip archives) where each file in the archives is hashed, and the manifest containing all the hashes is signed. When signing an extension, a manifest file containing the hash of each file in the XPI is first generated. The manifest file is stored in the signed XPI under '''META-INF/manifest.mf'''. The snippet below shows an example of manifest file.<br />
<source><br />
Manifest-Version: 1.0<br />
<br />
Name: install.rdf<br />
Digest-Algorithms: MD5 SHA1<br />
MD5-Digest: rzkfLZ5nC80leZsgMSGT3w==<br />
SHA1-Digest: +43YVUxeOYeiJeOKeJaRdancg5I=<br />
<br />
Name: bootstrap.js<br />
Digest-Algorithms: MD5 SHA1<br />
MD5-Digest: 2rUx2iRkGHx9yehpvoF2Wg==<br />
SHA1-Digest: 7F7q7SUdOpxp7EYDFLENUqrNWMo=<br />
<br />
Name: test.txt<br />
Digest-Algorithms: MD5 SHA1<br />
MD5-Digest: tT4aaxDCqRgFrpVHhe//Wg==<br />
SHA1-Digest: 8mPWZnQPS9arW9Tu/vmC+JHgnYA=<br />
</source><br />
<br />
A signature file is then created containing the hash of the manifest file (eg. `openssl dgst -binary -sha1 manifest.mf | base64`). The signature file is stored in the XPI under '''META-INF/mozilla.sf'''. An example is shown below:<br />
<source><br />
Signature-Version: 1.0<br />
MD5-Digest-Manifest: OlmmwIHcPmhoIt4uMxdh8A==<br />
SHA1-Digest-Manifest: 82zZH0Aq6GaTNMq+PnBlzep6fEA=<br />
</source><br />
<br />
A PKCS7 detached signature is computed on "mozilla.sf", using a signing certificate generated for each signature. The signing certificate, also called end-entity cert, is issued by an intermediate certificate of the Firefox private PKI. No special key usage or extended key usage is required in the end-entity cert, but its subject CN must match the add-on ID (for example, add-on ID test@tests.mozilla.org would have a cert CN set to that value).<br />
<br />
Note: If the add-on ID is longer than 64 characters, we use the SHA256 hash of the add-on ID in the end-entity subject CN, to work around issues with long string in certificates (see [https://bugzilla.mozilla.org/show_bug.cgi?id=1203787 bug 1203787]).<br />
<br />
The [https://tools.ietf.org/html/rfc2315 PKCS #7 (section 9.1 SignedData type)] signature is a binary file stored in the XPI under '''META-INF/mozilla.rsa'''. Because it is a standard PKCS7 signature, it can be verified using OpenSSL, as follows:<br />
<source lang:bash><br />
$ openssl cms -verify -inform der -in META-INF/mozilla.rsa -content META-INF/mozilla.sf -CAfile test.addons.signing.root.ca.crt -purpose any<br />
Signature-Version: 1.0<br />
MD5-Digest-Manifest: OlmmwIHcPmhoIt4uMxdh8A==<br />
SHA1-Digest-Manifest: 82zZH0Aq6GaTNMq+PnBlzep6fEA=<br />
<br />
Verification successful<br />
</source><br />
<br />
Both the end-entity and the intermediate certificates are also stored in the<br />
SignedData.Certificates document. The root cert is not stored in the document<br />
but shipped with Firefox directly.<br />
<br />
When installing add-ons, Firefox does the following verifications:<br />
<br />
* verify the signature of `mozilla.sf` using `mozilla.rsa`<br />
* verify the signing cert chains back to the Firefox Root CA<br />
* verify the hash of `manifest.mf` matches the hash stored in `mozilla.sf`<br />
* verify the hashes of all files in the XPI match the hashes stored in `manifest.mf`<br />
* verify all files in the XPI are listed in `manifest.mf`<br />
<br />
=== Signing of special add-ons ===<br />
There are three special cases of add-ons developed by Mozilla: System add-ons, Mozilla Extensions and Hotfixes.<br />
<br />
If the add-on is a system add-on, the Organizational Unit (OU) of the end-entity certificate must be set to "Mozilla Components".<br />
<br />
If the add-on is a Mozilla Extension, the OU of the EE cert must be set to "Mozilla Extensions".<br />
<br />
If the add-on is a hotfix, the add-on ID must match the pref `extensions.hotfix.id`<br />
(currently `firefox-hotfix@mozilla.org`) and the public key hash of the end-entity cert must match the fingerprints set in `extensions.hotfix.certs.1.sha1Fingerprint` or<br />
`extensions.hotfix.certs.2.sha1Fingerprint`.<br />
<br />
refs:<br />
* https://dxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/internal/XPIProvider.jsm<br />
* https://developer.mozilla.org/en-US/docs/Signing_a_XPI<br />
<br />
== Documentation ==<br />
* [http://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/ Introducing Extension Signing], Add-ons Blog.<br />
* [https://blog.mozilla.org/addons/2015/04/15/the-case-for-extension-signing/ The Case for Extension Signing], Add-ons Blog.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=signed-addons Main tracking bug].<br />
<br />
== Timeline ==<br />
Check the [[RapidRelease/Calendar|Firefox Release Calendar]] for specific dates. The following timelines are for Desktop:<br />
<br />
* '''Firefox 40-42''': Firefox warns about signatures but doesn't enforce them.<br />
* '''Firefox 43''': Firefox enforces the use of signatures by default, but has a preference that allows signature enforcement to be disabled (''xpinstall.signatures.required'' in about:config).<br />
* '''Firefox 48''': (Pushed from Firefox 46). Release and Beta versions of Firefox for Desktop will not allow unsigned extensions to be installed, with no override. Firefox for Android will enforce add-on signing, and will retain a preference &mdash; which will be removed in a future release &mdash; to allow the user to disable signing enforcement.<br />
<br />
The first ESR version to include signing support will be the Firefox ESR 52 release. <br />
<br />
All Firefox extensions - for Desktop and Android - on AMO that have passed review are now signed.<br />
<br />
For unlisted (non-AMO) add-ons, submission and signing is active through [https://addons.mozilla.org AMO], and there is a [https://blog.mozilla.org/addons/2015/11/20/signing-api-now-available/ Signing API available] for automated submission and retrieval of unlisted add-ons.<br />
<br />
== Unbranded Builds ==<br />
<br />
Unbranded builds are available from the continuous integration builds on archive.mozilla.org. Links to the latest beta and release builds, as well as the root directories for those treeherder builds are below, and subdirectories are named from the epoch timestamp of when the build was generated.<br />
<br />
=== Latest Builds ===<br />
<br />
'''Release builds''' <br />
<br />
Latest release (Firefox 52.0 - [https://hg.mozilla.org/releases/mozilla-release/rev/44d6a57ab554 changeset 44d6a57ab554]) builds:<br />
<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/1488485271/firefox-52.0.en-US.linux-x86_64-add-on-devel.tar.bz2 Linux Installer] ([https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/1488485271/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/1488485271/firefox-52.0.en-US.mac64-add-on-devel.dmg Mac OSX Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/1488485271/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/1488485271/firefox-52.0.en-US.win32-add-on-devel.installer.exe Windows 32-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/1488485271/ build directory]) <br />
*[http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/1488485271/firefox-52.0.en-US.win64-add-on-devel.installer.exe Windows 64-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/1488485271/ build directory]) <br />
<br />
'''Beta builds'''<br />
<br />
Latest beta (53.0b6 - [https://hg.mozilla.org/releases/mozilla-beta/rev/62467dd7218f changeset 62467dd7218f]) builds:<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/1490284823/firefox-53.0.en-US.linux-x86_64-add-on-devel.tar.bz2 Linux Installer] ([https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/1490284823/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/1490284823/firefox-53.0.en-US.mac64-add-on-devel.dmg Mac OSX Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/1490284823/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/1490284823/firefox-53.0.en-US.win32-add-on-devel.installer.exe Windows 32-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/1490284823/ build directory]) <br />
*[http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/1490284823/firefox-53.0.en-US.win64-add-on-devel.installer.exe Windows 64-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/1490284823/ build directory])<br />
<br />
=== Treeherder Root Directories ===<br />
<br />
'''Release'''<br />
<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/ Linux]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/ Mac OSX]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/ Windows 32-bit]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/ Windows 64-bit]<br />
<br />
'''Beta'''<br />
<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/ Linux]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/ OSX]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/ Windows 32-bit]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/ Windows 64-bit]<br />
<br />
== FAQ ==<br />
* Which add-on types will need to be signed?<br />
** Only extensions ([https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#type type 2] in install.rdf)--this includes WebExtensions. Themes, dictionaries, language packs, and plugins don't need to be signed.<br />
<br />
* Will other applications like Thunderbird, Seamonkey, Palemoon, etc. require extensions to be signed?<br />
** The leaders of each of those projects will decide if they want to enforce signing, keep it as a setting, or deactivate it by default. We haven't heard about any other applications planning to support this.<br />
<br />
* Will signed extensions work on other applications or older versions of Firefox?<br />
** Yes, the signature system is built on top of the [https://developer.mozilla.org/en-US/docs/Signing_a_XPI existing add-on signing feature], which has been supported in Firefox and other applications.<br />
<br />
* Will there be a setting or other overrides to disable signature checks?<br />
** Firefox Release and Beta versions will not have any way to disable signature checks. Signature checks can be disabled in other versions, as described in detail below.<br />
<br />
* What are my options if I want to install unsigned extensions in Firefox?<br />
** The [https://nightly.mozilla.org/ Nightly] and [https://www.mozilla.org/firefox/developer/ Developer Edition] versions of Firefox have a preference to disable signature enforcement. There are also be special [https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds unbranded versions of Release and Beta] that have this preference, so that add-on developers can work on their add-ons without having to sign every build. To disable signature checks, you will need to set the <code>xpinstall.signatures.required</code> preference to "false".<br />
*** type <code>about:config</code> into the URL bar in Firefox<br />
*** in the Search box type <code>xpinstall.signatures.required</code><br />
*** double-click the preference, or right-click and selected "Toggle", to set it to <code>false</code>.<br />
<br />
* How do the [[Add-ons/Extension_Signing#Unbranded_Builds|unbranded versions of Firefox]] work?<br />
** They work just like Firefox, with two differences: they have a setting to disable mandatory signature checks, and they don't have the Firefox name and logo (instead using a generic name and logo). These builds are available in the en-US locale only.<br />
<br />
* What about private add-ons used in enterprise environments?<br />
** The ESR release supports signing starting with version 45-based releases. Signing enforcement is enabled by default in these releases, and enforcement can be disabled using the <code>xpinstall.signatures.required</code> preference.<br />
<br />
* How do I get my add-ons signed if they are hosted on addons.mozilla.org (AMO)?<br />
** No action is required. We automatically signed reviewed versions of all add-ons currently hosted on AMO. All new versions will be signed automatically after they pass review. <br />
<br />
* How do I get my add-ons signed if they are not hosted on addons.mozilla.org (AMO)?<br />
** You will need to create an AMO account and submit your add-on. There will be an option where you indicate the add-on won't be listed on AMO, and you'll be able to submit your add-on files without having them published on the site. Please read the [https://developer.mozilla.org/en-US/Add-ons/Distribution Distribution Policy] for more details.<br />
** You can also use the [https://developer.mozilla.org/en-US/Add-ons/SDK/Tools/jpm#jpm_sign jpm sign] command to generate a signed XPI that can be self-hosted.<br />
** There is an [http://olympia.readthedocs.org/en/latest/topics/api/signing.html API you can use] for signing.<br />
<br />
* How does the signing process work for unlisted add-ons?<br />
** For unlisted add-ons, files submitted for signing go through an automated review process. If they pass this review, they are automatically signed and a download link is sent back to the developer. This process should normally take seconds.<br />
** There is an [http://olympia.readthedocs.org/en/latest/topics/api/signing.html API you can use] for signing.<br />
<br />
* What about [https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Maintenance#How_do_I_submit_a_Beta_add-on.3F Beta versions on AMO]? Will they be reviewed and signed?<br />
** Yes. Beta versions will be treated like non-AMO add-ons. They will be automatically validated and signed if they pass validation.<br />
<br />
* Will I need to sign the custom version of an existing add-on I created with my own code changes, locale additions, etc.?<br />
** If you use it on Release or Beta, yes. You will also need to change the add-on ID in order to submit it for signing.<br />
<br />
* Is this a way for Mozilla to censor add-ons they don't like, enforce copyright, government demands, etc.?<br />
** No, the purpose of this is to protect users from malicious add-ons. We have [https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Reviews a set of guidelines] for when it is appropriate to blocklist an add-on and have refused multiple times to block for other reasons.<br />
<br />
* Will there be an upload and signing API so I don't have to manually upload each new version of the add-on?<br />
** Yes. The [http://olympia.readthedocs.org/en/latest/topics/api/signing.html signing API is documented here].<br />
<br />
* Will this protect users against all forms of add-on malware?<br />
** No, there is no perfect solution for this. Fighting malware requires defenses on many levels: operating system,, application, user, and even industry. Extension signing is a big step in protecting Firefox against malicious add-ons, but there is much more to do in other fronts to ensure the best experience for our users.<br />
<br />
== Feedback and Questions ==<br />
For questions about signing, you can use [https://developer.mozilla.org/en-US/Add-ons#Contact_us any of our communication channels].</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Extension_Signing&diff=1168962Add-ons/Extension Signing2017-04-21T17:52:55Z<p>Jorge.villalobos: Updated text for the removal of Aurora, and some other tweaks</p>
<hr />
<div>Mozilla requires all extensions to be signed by Mozilla in order for them to be installable in Release and Beta versions of Firefox. Extensions submitted on [https://addons.mozilla.org/ addons.mozilla.org (AMO)] are signed as part of the review process, and a [http://addons-server.readthedocs.io/en/latest/topics/api/signing.html signing service] is also offered. Additional information on the extension submission and signing process is [https://developer.mozilla.org/en-US/Add-ons/Distribution available on MDN].<br />
<br />
== Algorithm ==<br />
<br />
Extension signing is controlled by Mozilla and requires access to a private signing infrastructure exposed by [https://addons.mozilla.org/ AMO], and internal services like [https://github.com/mozilla-services/autograph Autograph].<br />
<br />
Add-ons and Extensions are XPI files (zip archives) where each file in the archives is hashed, and the manifest containing all the hashes is signed. When signing an extension, a manifest file containing the hash of each file in the XPI is first generated. The manifest file is stored in the signed XPI under '''META-INF/manifest.mf'''. The snippet below shows an example of manifest file.<br />
<source><br />
Manifest-Version: 1.0<br />
<br />
Name: install.rdf<br />
Digest-Algorithms: MD5 SHA1<br />
MD5-Digest: rzkfLZ5nC80leZsgMSGT3w==<br />
SHA1-Digest: +43YVUxeOYeiJeOKeJaRdancg5I=<br />
<br />
Name: bootstrap.js<br />
Digest-Algorithms: MD5 SHA1<br />
MD5-Digest: 2rUx2iRkGHx9yehpvoF2Wg==<br />
SHA1-Digest: 7F7q7SUdOpxp7EYDFLENUqrNWMo=<br />
<br />
Name: test.txt<br />
Digest-Algorithms: MD5 SHA1<br />
MD5-Digest: tT4aaxDCqRgFrpVHhe//Wg==<br />
SHA1-Digest: 8mPWZnQPS9arW9Tu/vmC+JHgnYA=<br />
</source><br />
<br />
A signature file is then created containing the hash of the manifest file (eg. `openssl dgst -binary -sha1 manifest.mf | base64`). The signature file is stored in the XPI under '''META-INF/mozilla.sf'''. An example is shown below:<br />
<source><br />
Signature-Version: 1.0<br />
MD5-Digest-Manifest: OlmmwIHcPmhoIt4uMxdh8A==<br />
SHA1-Digest-Manifest: 82zZH0Aq6GaTNMq+PnBlzep6fEA=<br />
</source><br />
<br />
A PKCS7 detached signature is computed on "mozilla.sf", using a signing certificate generated for each signature. The signing certificate, also called end-entity cert, is issued by an intermediate certificate of the Firefox private PKI. No special key usage or extended key usage is required in the end-entity cert, but its subject CN must match the add-on ID (for example, add-on ID test@tests.mozilla.org would have a cert CN set to that value).<br />
<br />
Note: If the add-on ID is longer than 64 characters, we use the SHA256 hash of the add-on ID in the end-entity subject CN, to work around issues with long string in certificates (see [https://bugzilla.mozilla.org/show_bug.cgi?id=1203787 bug 1203787]).<br />
<br />
The [https://tools.ietf.org/html/rfc2315 PKCS #7 (section 9.1 SignedData type)] signature is a binary file stored in the XPI under '''META-INF/mozilla.rsa'''. Because it is a standard PKCS7 signature, it can be verified using OpenSSL, as follows:<br />
<source lang:bash><br />
$ openssl cms -verify -inform der -in META-INF/mozilla.rsa -content META-INF/mozilla.sf -CAfile test.addons.signing.root.ca.crt -purpose any<br />
Signature-Version: 1.0<br />
MD5-Digest-Manifest: OlmmwIHcPmhoIt4uMxdh8A==<br />
SHA1-Digest-Manifest: 82zZH0Aq6GaTNMq+PnBlzep6fEA=<br />
<br />
Verification successful<br />
</source><br />
<br />
Both the end-entity and the intermediate certificates are also stored in the<br />
SignedData.Certificates document. The root cert is not stored in the document<br />
but shipped with Firefox directly.<br />
<br />
When installing add-ons, Firefox does the following verifications:<br />
<br />
* verify the signature of `mozilla.sf` using `mozilla.rsa`<br />
* verify the signing cert chains back to the Firefox Root CA<br />
* verify the hash of `manifest.mf` matches the hash stored in `mozilla.sf`<br />
* verify the hashes of all files in the XPI match the hashes stored in `manifest.mf`<br />
* verify all files in the XPI are listed in `manifest.mf`<br />
<br />
=== Signing of special add-ons ===<br />
There are three special cases of add-ons developed by Mozilla: System add-ons, Mozilla Extensions and Hotfixes.<br />
<br />
If the add-on is a system add-on, the Organizational Unit (OU) of the end-entity certificate must be set to "Mozilla Components".<br />
<br />
If the add-on is a Mozilla Extension, the OU of the EE cert must be set to "Mozilla Extensions".<br />
<br />
If the add-on is a hotfix, the add-on ID must match the pref `extensions.hotfix.id`<br />
(currently `firefox-hotfix@mozilla.org`) and the public key hash of the end-entity cert must match the fingerprints set in `extensions.hotfix.certs.1.sha1Fingerprint` or<br />
`extensions.hotfix.certs.2.sha1Fingerprint`.<br />
<br />
refs:<br />
* https://dxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/internal/XPIProvider.jsm<br />
* https://developer.mozilla.org/en-US/docs/Signing_a_XPI<br />
<br />
== Documentation ==<br />
* [http://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/ Introducing Extension Signing], Add-ons Blog.<br />
* [https://blog.mozilla.org/addons/2015/04/15/the-case-for-extension-signing/ The Case for Extension Signing], Add-ons Blog.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=signed-addons Main tracking bug].<br />
<br />
== Timeline ==<br />
Check the [[RapidRelease/Calendar|Firefox Release Calendar]] for specific dates. The following timelines are for Desktop:<br />
<br />
* '''Firefox 40-42''': Firefox warns about signatures but doesn't enforce them.<br />
* '''Firefox 43''': Firefox enforces the use of signatures by default, but has a preference that allows signature enforcement to be disabled (''xpinstall.signatures.required'' in about:config).<br />
* '''Firefox 48''': (Pushed from Firefox 46). Release and Beta versions of Firefox for Desktop will not allow unsigned extensions to be installed, with no override. Firefox for Android will enforce add-on signing, and will retain a preference &mdash; which will be removed in a future release &mdash; to allow the user to disable signing enforcement.<br />
<br />
The first ESR version to include signing support will be the Firefox ESR 52 release. <br />
<br />
All Firefox extensions - for Desktop and Android - on AMO that have passed review are now signed.<br />
<br />
For unlisted (non-AMO) add-ons, submission and signing is active through [https://addons.mozilla.org AMO], and there is a [https://blog.mozilla.org/addons/2015/11/20/signing-api-now-available/ Signing API available] for automated submission and retrieval of unlisted add-ons.<br />
<br />
== Unbranded Builds ==<br />
<br />
Unbranded builds are available from the continuous integration builds on archive.mozilla.org. Links to the latest beta and release builds, as well as the root directories for those treeherder builds are below, and subdirectories are named from the epoch timestamp of when the build was generated.<br />
<br />
=== Latest Builds ===<br />
<br />
'''Release builds''' <br />
<br />
Latest release (Firefox 52.0 - [https://hg.mozilla.org/releases/mozilla-release/rev/44d6a57ab554 changeset 44d6a57ab554]) builds:<br />
<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/1488485271/firefox-52.0.en-US.linux-x86_64-add-on-devel.tar.bz2 Linux Installer] ([https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/1488485271/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/1488485271/firefox-52.0.en-US.mac64-add-on-devel.dmg Mac OSX Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/1488485271/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/1488485271/firefox-52.0.en-US.win32-add-on-devel.installer.exe Windows 32-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/1488485271/ build directory]) <br />
*[http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/1488485271/firefox-52.0.en-US.win64-add-on-devel.installer.exe Windows 64-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/1488485271/ build directory]) <br />
<br />
'''Beta builds'''<br />
<br />
Latest beta (53.0b6 - [https://hg.mozilla.org/releases/mozilla-beta/rev/62467dd7218f changeset 62467dd7218f]) builds:<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/1490284823/firefox-53.0.en-US.linux-x86_64-add-on-devel.tar.bz2 Linux Installer] ([https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/1490284823/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/1490284823/firefox-53.0.en-US.mac64-add-on-devel.dmg Mac OSX Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/1490284823/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/1490284823/firefox-53.0.en-US.win32-add-on-devel.installer.exe Windows 32-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/1490284823/ build directory]) <br />
*[http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/1490284823/firefox-53.0.en-US.win64-add-on-devel.installer.exe Windows 64-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/1490284823/ build directory])<br />
<br />
=== Treeherder Root Directories ===<br />
<br />
'''Release'''<br />
<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/ Linux]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/ Mac OSX]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/ Windows 32-bit]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/ Windows 64-bit]<br />
<br />
'''Beta'''<br />
<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/ Linux]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/ OSX]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/ Windows 32-bit]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/ Windows 64-bit]<br />
<br />
== FAQ ==<br />
* Which add-on types will need to be signed?<br />
** Only extensions ([https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#type type 2] in install.rdf)--this includes WebExtensions. Themes, dictionaries, language packs, and plugins don't need to be signed.<br />
<br />
* Will other applications like Thunderbird, Seamonkey, Palemoon, etc. require extensions to be signed?<br />
** The leaders of each of those projects will decide if they want to enforce signing, keep it as a setting, or deactivate it by default. We haven't heard about any other applications planning to support this.<br />
<br />
* Will signed extensions work on other applications or older versions of Firefox?<br />
** Yes, the signature system is built on top of the [https://developer.mozilla.org/en-US/docs/Signing_a_XPI existing add-on signing feature], which has been supported in Firefox and other applications.<br />
<br />
* Will there be a setting or other overrides to disable signature checks?<br />
** Firefox Release and Beta versions will not have any way to disable signature checks. Signature checks can be disabled in other versions, as described in detail below.<br />
<br />
* What are my options if I want to install unsigned extensions in Firefox?<br />
** The [https://nightly.mozilla.org/ Nightly] versions of Firefox have a preference to disable signature enforcement. There are also be special [https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds unbranded versions of Release and Beta] that have this preference, so that add-on developers can work on their add-ons without having to sign every build. To disable signature checks, you will need to set the <code>xpinstall.signatures.required</code> preference to "false".<br />
*** type <code>about:config</code> into the URL bar in Firefox<br />
*** in the Search box type <code>xpinstall.signatures.required</code><br />
*** double-click the preference, or right-click and selected "Toggle", to set it to <code>false</code>.<br />
<br />
* How do the [[Add-ons/Extension_Signing#Unbranded_Builds|unbranded versions of Firefox]] work?<br />
** They work just like Firefox, with two differences: they have a setting to disable mandatory signature checks, and they don't have the Firefox name and logo (instead using a generic name and logo). These builds are available in the en-US locale only.<br />
<br />
* What about private add-ons used in enterprise environments?<br />
** The ESR release supports signing starting with version 45-based releases. Signing enforcement is enabled by default in these releases, and enforcement can be disabled using the <code>xpinstall.signatures.required</code> preference.<br />
<br />
* How do I get my add-ons signed if they are hosted on addons.mozilla.org (AMO)?<br />
** No action is required. We automatically signed reviewed versions of all add-ons currently hosted on AMO. All new versions will be signed automatically after they pass review. <br />
<br />
* How do I get my add-ons signed if they are not hosted on addons.mozilla.org (AMO)?<br />
** You will need to create an AMO account and submit your add-on. There will be an option where you indicate the add-on won't be listed on AMO, and you'll be able to submit your add-on files without having them published on the site. Please read the [https://developer.mozilla.org/en-US/Add-ons/Distribution Distribution Policy] for more details.<br />
** You can also use the [https://developer.mozilla.org/en-US/Add-ons/SDK/Tools/jpm#jpm_sign jpm sign] command to generate a signed XPI that can be self-hosted.<br />
** There is an [http://olympia.readthedocs.org/en/latest/topics/api/signing.html API you can use] for signing.<br />
<br />
* How does the signing process work for unlisted add-ons?<br />
** For unlisted add-ons, files submitted for signing go through an automated review process. If they pass this review, they are automatically signed and a download link is sent back to the developer. This process should normally take seconds.<br />
** There is an [http://olympia.readthedocs.org/en/latest/topics/api/signing.html API you can use] for signing.<br />
<br />
* What about [https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Maintenance#How_do_I_submit_a_Beta_add-on.3F Beta versions on AMO]? Will they be reviewed and signed?<br />
** Yes. Beta versions will be treated like non-AMO add-ons. They will be automatically validated and signed if they pass validation.<br />
<br />
* Will I need to sign the custom version of an existing add-on I created with my own code changes, locale additions, etc.?<br />
** If you use it on Release or Beta, yes. You will also need to change the add-on ID in order to submit it for signing.<br />
<br />
* Is this a way for Mozilla to censor add-ons they don't like, enforce copyright, government demands, etc.?<br />
** No, the purpose of this is to protect users from malicious add-ons. We have [https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Reviews a set of guidelines] for when it is appropriate to blocklist an add-on and have refused multiple times to block for other reasons.<br />
<br />
* Will there be an upload and signing API so I don't have to manually upload each new version of the add-on?<br />
** Yes. The [http://olympia.readthedocs.org/en/latest/topics/api/signing.html signing API is documented here].<br />
<br />
* Will this protect users against all forms of add-on malware?<br />
** No, there is no perfect solution for this. Fighting malware requires defenses on many levels: operating system,, application, user, and even industry. Extension signing is a big step in protecting Firefox against malicious add-ons, but there is much more to do in other fronts to ensure the best experience for our users.<br />
<br />
== Feedback and Questions ==<br />
For questions about signing, you can use [https://developer.mozilla.org/en-US/Add-ons#Contact_us any of our communication channels].</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Contribute/Triage&diff=1168612Add-ons/Contribute/Triage2017-04-18T17:30:42Z<p>Jorge.villalobos: Updating bug queries to use the keyword and whiteboard</p>
<hr />
<div>= Purpose of Meeting =<br />
A bi-weekly triage session to accomplish these community goals:<br />
* '''WebExtensions APIs''': <br />
** Transparency: Decide whether APIs tagged "design-decision-needed" are "design-decision-approved" or "wontfix" to ensure transparency for the direction of WebExtensions. <br />
** Participation: Give guidance on and assign advisors to APIs marked "design-decision-approved" to make it easier for contributors to get involved.<br />
** Experiments: Discuss and provide feedback for [http://webextensions-experiments.readthedocs.io/en/latest/index.html WebExtensions Experiments].<br />
* '''Good First Bugs''': Ensure add-on bugs marked "Good First Bug" are fresh and updated for new contributors. If you are a new contributor who wants to write code for add-on related projects, please [https://wiki.mozilla.org/Add-ons/Contribute/Code start here].<br />
<br />
=Next Meeting=<br />
<br />
[https://docs.google.com/document/d/1zKqhDqXoH9vi88q4DGtOHm1hsCF8ZwLNvCrrCE5htbc/edit# April 18, 2017]<br />
<br />
=Details & How to Join=<br />
* Time: Every other Tuesday at:<br />
**[http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 10:00am Pacific] - Good First Bugs<br />
**[http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 10:30am Pacific] - WebExtensions APIs & Experiments<br />
* Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU<br />
*IRC: [https://wiki.mozilla.org/IRC irc.mozilla.org], #Addons channel<br />
<br />
=WebExtensions APIs Triage=<br />
==Triage Guidelines==<br />
Bugs marked "design-decision-needed" should be:<br />
*Tagged with "design-decision-approved" or "wontfix" (including reason)<br />
<br />
Bugs marked "design-decision-approved" should have:<br />
*Clear description of the API and suggested implementation if possible<br />
*Priority & impact<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code#Develop_Web_Extensions_APIs onboarding process]<br />
*Advisor<br />
<br />
==Bug Queries==<br />
====="design-decision-needed"=====<br />
These are determined from the Monday WebExtensions triage. They are APIs we [https://mzl.la/2edmiid need more discussion] on.<br />
<br />
====="design-decision-approved"=====<br />
These are APIs we would [https://mzl.la/2dVs5Ys like to have]. They should meet the triage criteria listed above.<br />
<br />
==WebExtensions Experiments==<br />
* Submit your [http://webextensions-experiments.readthedocs.io/en/latest/index.html WebExtensions Experiment] by opening an issue on the [https://github.com/web-ext-experiments/about/issues web-ext-experiments github repo].<br />
* Be sure to include the following in your issue: <br />
** Link to where your experiment is located<br />
** A quick overview of what it does<br />
** Any Bugzilla bugs that it might address<br />
** If you’d like to move your repository over to this organisation and we can create a repository for you<br />
* A comment will be added to the issue when your WebExtensions Experiment has been added to a meeting agenda.<br />
<br />
=Good First Bugs Triage=<br />
==Triage Guidelines==<br />
All "Good First Bugs" should have:<br />
*Clear description of the issue<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code onboarding process]<br />
*Mentor<br />
<br />
==Bug Queries==<br />
====="Maybe Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20maybe%20good%20first%20bug These are tagged "contrib: maybe good first bug"]. We triage these and change the tag to "Good First Bugs" if determined to be good for new contributors.<br />
<br />
====="Good First Bugs" that need a mentor on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20good%20first%20bug,needs:%20mentor These are tagged "contrib: good first bug" and "needs: mentor"]. We triage these and add replace the "needs: mentor" label by "contrib: mentor assigned" after we decided on a mentor.<br />
<br />
====="Good First Bugs" that are assigned to a contributor on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20good%20first%20bug,contrib:%20assigned These are tagged "contrib: good first bug" and "contrib: assigned"]. We triage these and check-in with contributors on their progress and remove "contrib: assigned" after a longer period of inactivity or no response.<br />
<br />
====="Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=contrib:%20good%20first%20bug This is the query] contributors see. We should spot-check them to ensure they are properly triaged.<br />
<br />
=====WebExtensions Bugs on Bugzilla=====<br />
*These are WebExtensions bugs that [https://mzl.la/2oIxRRQ don't have a mentor]<br />
*These are WebExtensions bugs that [https://mzl.la/2okrott have an assignee but haven't been commented on for 3 weeks]<br />
<br />
=====Add-ons Manager Bugs on Bugzilla=====<br />
*These are Add-ons Manager bugs that [https://mzl.la/2pecPvR don't have a mentor]<br />
*These are Add-ons Manager bugs that [https://mzl.la/2oIyb30 have an assignee but haven't been commented on for 3 weeks]<br />
<br />
= Archive =<br />
=====2017=====<br />
[https://docs.google.com/document/d/1V4NP4tWnjHigS2lAosCLfkU2FTcrQnoQzzXZmmB1uzk/edit April 4, 2017]<br /><br />
[https://docs.google.com/document/d/1YbQGbkNWwVGvXgjzJ541s-d4AVImRLThMKnBM3Yo1Lw/edit#heading=h.t2yykqfh2jii March 28, 2017] - GFB only<br /><br />
[https://docs.google.com/document/d/1xM6iKOSGo9cDWw3ZA27PT-AVlx1Mvd79sxC6pYNhBqU/edit#heading=h.t2yykqfh2jii March 21, 2017]<br /><br />
[https://docs.google.com/document/d/1zzfedbTKAHUmm4UctxSOIJV3iKayXQ8TuXPodXW8wC0/edit#heading=h.sbitm9gruxfs March 7, 2017]<br /><br />
[https://docs.google.com/document/d/1H4sjnRFc87NZXZsM6XIgwWaoV2bdRFepiG28G7WzgPs/edit?usp=sharing Feb 21, 2017]<br /><br />
[https://docs.google.com/document/d/1X5OUNgpUcMLkHrOPbg-OLWSA2hzoRykRZd2gyTJ9vgU/edit# Feb 7, 2017]<br /><br />
[https://docs.google.com/document/d/1add-6FL8mzksvzbyB83HUmEkVmKERd-nt740AYr-4PE/edit# Jan 24, 2017]<br /><br />
[https://docs.google.com/document/d/18K97o1juaHSeYEkes1iMz8AayjuVkUuIK844ErGaa-c/edit?usp=sharing Jan 10, 2017]<br />
<br />
=====2016=====<br />
[https://docs.google.com/document/d/1S1QrBK1hrulE7dlLiQzjMupHUUSwDYRYAOXiqtMHe-k/edit?usp=sharing Dec 13, 2016]<br /><br />
[https://docs.google.com/document/d/1IMBFXHNpg_A-15VdJM1Hh8DUUXF1xNFy87W1w8ZEOBk/edit#heading=h.du5ihvu5p6ro Nov 29, 2016]<br /><br />
[https://docs.google.com/document/d/1cMvAtlIZpykpxZ0bG2J2lh7Mx1WcVfLrHSDJZHFvexc/edit Nov 15, 2016]<br /><br />
[https://docs.google.com/document/d/1i5CT821JFutWL-f3AZ3VhlYIIzulnMttjNp1JsYba8M/edit# Nov 1, 2016]<br /><br />
[https://docs.google.com/document/d/1elytPf_HqAqqFC6EM0-hrJp7kWJA-LfKILXV1tzNLTU/edit Oct 18, 2016]<br /><br />
[https://docs.google.com/document/d/1BDIbINMGgjoWlZxHmw-MnLm3HEqB38oUNTJUPAippGo/edit Oct 4, 2016]<br /><br />
[https://docs.google.com/document/d/1gABxxstInPy5XMsmoYMhZBMsLGFWNsgWMhgjUlt7-o8/edit Sept 20, 2016]<br /><br />
[https://docs.google.com/document/d/14cqCfgbyGoBXe7ttho0L3mIe4FcSSlzHH3L4fBFnLzA/edit Sept 6, 2016]<br /><br />
[https://docs.google.com/document/d/1GDpdcO1EHefRL3B5p5g1emdp_lY-YFWjwXv8YG1EgWo/edit August 23, 2016]<br /><br />
[https://docs.google.com/document/d/1rZvIfFILAHozLGTrg5C7Q7lXyEZ2gfMDw7cVkEo34io/edit August 9, 2016]<br /><br />
[https://docs.google.com/document/d/1A5hKaon2Z3nSCQc9ToYTOjr2cIpmmeZmu9EnbhVjHd0/edit July 26, 2016]<br /><br />
[https://docs.google.com/document/d/18wCqoUzNYshOWDjuJjePFivb4T5nD0WlFE06NKn3YQ0/edit July 12, 2016]<br /><br />
[https://docs.google.com/document/d/1uBo-WVFP2v-dyeYyDtfPD9ipN8JeIw7sCag4CYonQqY/edit# June 28, 2016]<br /><br />
[https://docs.google.com/document/d/1lYqcEWaktMXPmAefRB9PW9iSBM95rlVKFOO-vFRewdE/edit May 31, 2016]<br /><br />
[https://docs.google.com/document/d/1Bq7gTVhsGfTW58A9MUurruu5jc2w5OHSeaoRbmWRQV4/edit May 17, 2016]<br /><br />
[https://docs.google.com/document/d/1EkZXtIx7TkQxnFn_2ei3SR7j9xeDVc1WSl3suY2n8RU/edit April 28, 2016]<br /><br />
[https://docs.google.com/document/d/13yPW-ojA_jzXUe7_fxDvYQavsr5yEHZzHXXCMcuZgCA/edit April 14, 2016]<br /><br />
[https://docs.google.com/document/d/1hSABd9dd8UktXGJuf0iXn_8Fpuz09VEqkxrxMY_AvZw/edit Mar 31, 2016]<br /><br />
[https://docs.google.com/document/d/1ss0i_zAZDytsyBnMGF1gdRI6LjRWqvQS9Q0ueKzQV1Q/edit Mar 3, 2016]<br /><br />
[https://docs.google.com/document/d/1GkHWjHRDcUd7WD2BFF-6zhdyce4lK8qMX23O6C0eRIA/edit Feb 18, 2016]<br /><br />
[https://docs.google.com/document/d/1cM2JIIgw1i7TJe3oOojCtJvEhJoBGdHgNvjS2hRfBcw/edit Feb 4, 2016]<br /> <br />
[https://docs.google.com/document/d/1OZVV_HVXWAY-1u-nPhb4MrXOsycVFbXkXGEhhTomoaM/edit Jan 21, 2016]<br /><br />
[https://docs.google.com/document/d/1GwqhWsSsBp5vfLW7-5Di8_CzIfepwK9YVZAnQuLxK9I/edit Jan 7, 2016]<br />
<br />
=====2015=====<br />
[https://docs.google.com/document/d/18Csoja50IhnjqraFzxEYyVIJp-j79GLO2gCrvTSYHUI/edit Nov. 19, 2015]<br /><br />
[https://docs.google.com/document/d/1gbhL0S4amQ447ddIX7mEZsSaGoiFt8fTw22FKe_GbIo/edit Oct. 29, 2015]<br /><br />
[https://docs.google.com/document/d/1EoLSXHKCqJzTatj6CLLpjomwXnN5zUOA897brO_1aJQ/edit Oct. 15, 2015]<br />
<br />
=====Aug - Oct 2015=====<br />
https://drive.google.com/drive/folders/0B2aDMRMZ7uzvYzA4Wm1VYVhvemM<br />
<br />
=Onboarding information template=<br />
If this is your first contribution, please refer to https://wiki.mozilla.org/Add-ons/Contribute/Code on how to get started.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Delete-Account&diff=1167007Add-ons/Delete-Account2017-03-29T15:10:23Z<p>Jorge.villalobos: First draft.</p>
<hr />
<div>=How to delete an account on addons.mozilla.org=<br />
# Go to https://addons.mozilla.org/users/edit. Log in if necessary.<br />
# Scroll down to the bottom of the page and click on the Delete Account link.<br />
<br />
If you're an add-on developer, you will need to delete or change the ownership of your add-ons before you can delete your account.<br />
<br />
If you have any problems deleting your account, please contact amo-admins AT mozilla DOT org for assistance.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/AMO-Manual&diff=1166238Add-ons/AMO-Manual2017-03-20T23:26:35Z<p>Jorge.villalobos: Note on channels</p>
<hr />
<div>This is a collection of guides that should help AMO Engineers and other Mozillians navigate the madness that is the add-ons world.<br />
=Add-on types=<br />
[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#type MDN Doc] for add-on types.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Type !! In <code>install.rdf</code> !! In AMO DB !! Notes<br />
|-<br />
| Extension || 2 || 1 ||<br />
|-<br />
| Lightweight theme || ''N/A'' || 9 ||<br />
|-<br />
| Dictionary || 64 || 3 || Language for the Firefox spellchecker.<br />
|-<br />
| Search Engine || ''N/A'' || 4 || For the Firefox search box. [https://developer.mozilla.org/en-US/Add-ons/Creating_OpenSearch_plugins_for_Firefox See doc].<br />
|-<br />
| Language pack || 8 || 5 || Localization for Firefox UI. Most are automatically published from Firefox sources.<br />
|-<br />
| Complete theme || 4 || 2 || Deprecated. Will be dropped in Firefox 57.<br />
|-<br />
| Multi-package installer || 32 || 1 || Discontinued.<br />
|-<br />
| Telemetry Experiment || 128 || ''N/A'' ||<br />
|-<br />
| WebExtension Experiment || 256 || ''N/A'' ||<br />
|}<br />
<br />
WebExtension packages don't have types. They are all treated like extensions, with the exception of new themes (WIP).<br />
<br />
The AMO DB has a couple more types that are no longer in use: 7 - Plugins, 6 - Language Packs (Add-on), 11 - Apps.<br />
<br />
= Compatibility =<br />
<br />
[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#targetApplication MDN doc] on compatibility for legacy add-ons.<br />
<br />
Compatibility with the client depends on various factors. They are listed here in order of priority (next one overrides previous one):<br />
* Default compatibility.<br />
** Legacy add-ons with a <code>maxVersion</code> lower than Firefox 4.0a1 have strict compatibility, so the <code>maxVersion</code> must be respected.<br />
** For all other add-ons, the <code>maxVersion</code> doesn't matter.<br />
** The <code>minVersion</code> for legacy add-ons should always be respected.<br />
** WebExtensions have default minimum compatibility of Firefox 42.0a1.<br />
** Application support (Firefox / Thunderbird / SeaMonkey / Android) is read from the manifest and can be altered during submission (All Desktop / Windows / Linux / Mac OS / Android).<br />
* Strict compatibility.<br />
** Legacy add-ons with the <code>[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#strictCompatibility strictCompatibility]</code> manifest flag must have the <code>maxVersion</code> respected.<br />
** WebExtensions [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/applications that declare so] must have the <code>strict_min_version</code> and <code>strict_max_version</code> respected. A <code>strict_min_version</code> lower than 42.0a1 should be ignored.<br />
* AMO Metadata (editable in Developer Hub).<br />
** For add-ons with strict compatibility (legacy and WebExtensions) this overrides what is declared in the manifest.<br />
** Application support can also be altered here.<br />
* Compatibility overrides. These are admin overrides that declare a version range for an add-on is '''not''' compatible with a version range of an application (usually Firefox).<br />
<br />
This doesn't apply to lightweight themes and search engines.<br />
<br />
=Add-on and File Statuses=<br />
This table explains the different add-on and file status combinations during the life cycle of a listed add-on:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Case !! Add-on status !! File status (latest listed) !! Notes<br />
|-<br />
| New listed add-on, incomplete submission || Incomplete (0) || Awaiting Review (3) ||<br />
|-<br />
| New listed add-on, submitted for review || Awaiting Review (3) || Awaiting Review (3) ||<br />
|-<br />
| Rejected after review (no previous approvals) || Incomplete (0) || Disabled by Mozilla (5), all files || Also when admins want to take down an add-on and let the developer submit a fix.<br />
|-<br />
| Approved and listed || Approved (4) || Approved (4) ||<br />
|-<br />
| Approved, updated submitted || Approved (4) || Awaiting Review (3) || Previously-approved version appears on listing page.<br />
|-<br />
| Disabled by an admin || Disabled by Mozilla (5) || Any || Add-ons in this state can't be accessed by their developer.<br />
|-<br />
| Deleted || Deleted (11) || No files ||<br />
|}<br />
<br />
Unlisted versions are submitted and auto-Approved (4) without affecting the add-on status. So, add-ons that are exclusively unlisted have an add-on status of Incomplete (0) and Approved (4) files.<br />
<br />
An add-on version can have multiple files, and it used to be possible for them to have a different review status. That's the reason the review status is stored in the file rather than the version. Most if not all cases preventing the status to be moved up to the version are fixed now.<br />
<br />
For add-ons with listed versions, Beta (7) is another valid file status. Like unlisted versions, they are submitted and auto-approved. They are listed in the Developer Channel section in the listing page ([https://addons.mozilla.org/addon/noscript/#beta-channel for example]). <br />
<br />
A version can be listed or unlisted depending on its <code>channel</code>, which is set to 1 for Unlisted and 2 for Listed. The channel for a version can't be changed.<br />
<br />
A developer can hide their listing page using the <code>inactive</code> field in the add-on.<br />
<br />
= Featured Add-ons and Collections=<br />
TODO</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/AMO-Manual&diff=1166236Add-ons/AMO-Manual2017-03-20T23:23:23Z<p>Jorge.villalobos: Some add-on status fun</p>
<hr />
<div>This is a collection of guides that should help AMO Engineers and other Mozillians navigate the madness that is the add-ons world.<br />
=Add-on types=<br />
[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#type MDN Doc] for add-on types.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Type !! In <code>install.rdf</code> !! In AMO DB !! Notes<br />
|-<br />
| Extension || 2 || 1 ||<br />
|-<br />
| Lightweight theme || ''N/A'' || 9 ||<br />
|-<br />
| Dictionary || 64 || 3 || Language for the Firefox spellchecker.<br />
|-<br />
| Search Engine || ''N/A'' || 4 || For the Firefox search box. [https://developer.mozilla.org/en-US/Add-ons/Creating_OpenSearch_plugins_for_Firefox See doc].<br />
|-<br />
| Language pack || 8 || 5 || Localization for Firefox UI. Most are automatically published from Firefox sources.<br />
|-<br />
| Complete theme || 4 || 2 || Deprecated. Will be dropped in Firefox 57.<br />
|-<br />
| Multi-package installer || 32 || 1 || Discontinued.<br />
|-<br />
| Telemetry Experiment || 128 || ''N/A'' ||<br />
|-<br />
| WebExtension Experiment || 256 || ''N/A'' ||<br />
|}<br />
<br />
WebExtension packages don't have types. They are all treated like extensions, with the exception of new themes (WIP).<br />
<br />
The AMO DB has a couple more types that are no longer in use: 7 - Plugins, 6 - Language Packs (Add-on), 11 - Apps.<br />
<br />
= Compatibility =<br />
<br />
[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#targetApplication MDN doc] on compatibility for legacy add-ons.<br />
<br />
Compatibility with the client depends on various factors. They are listed here in order of priority (next one overrides previous one):<br />
* Default compatibility.<br />
** Legacy add-ons with a <code>maxVersion</code> lower than Firefox 4.0a1 have strict compatibility, so the <code>maxVersion</code> must be respected.<br />
** For all other add-ons, the <code>maxVersion</code> doesn't matter.<br />
** The <code>minVersion</code> for legacy add-ons should always be respected.<br />
** WebExtensions have default minimum compatibility of Firefox 42.0a1.<br />
** Application support (Firefox / Thunderbird / SeaMonkey / Android) is read from the manifest and can be altered during submission (All Desktop / Windows / Linux / Mac OS / Android).<br />
* Strict compatibility.<br />
** Legacy add-ons with the <code>[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#strictCompatibility strictCompatibility]</code> manifest flag must have the <code>maxVersion</code> respected.<br />
** WebExtensions [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/applications that declare so] must have the <code>strict_min_version</code> and <code>strict_max_version</code> respected. A <code>strict_min_version</code> lower than 42.0a1 should be ignored.<br />
* AMO Metadata (editable in Developer Hub).<br />
** For add-ons with strict compatibility (legacy and WebExtensions) this overrides what is declared in the manifest.<br />
** Application support can also be altered here.<br />
* Compatibility overrides. These are admin overrides that declare a version range for an add-on is '''not''' compatible with a version range of an application (usually Firefox).<br />
<br />
This doesn't apply to lightweight themes and search engines.<br />
<br />
=Add-on and File Statuses=<br />
This table explains the different add-on and file status combinations during the life cycle of a listed add-on:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Case !! Add-on status !! File status (latest listed) !! Notes<br />
|-<br />
| New listed add-on, incomplete submission || Incomplete (0) || Awaiting Review (3) ||<br />
|-<br />
| New listed add-on, submitted for review || Awaiting Review (3) || Awaiting Review (3) ||<br />
|-<br />
| Rejected after review (no previous approvals) || Incomplete (0) || Disabled by Mozilla (5), all files || Also when admins want to take down an add-on and let the developer submit a fix.<br />
|-<br />
| Approved and listed || Approved (4) || Approved (4) ||<br />
|-<br />
| Approved, updated submitted || Approved (4) || Awaiting Review (3) || Previously-approved version appears on listing page.<br />
|-<br />
| Disabled by an admin || Disabled by Mozilla (5) || Any || Add-ons in this state can't be accessed by their developer.<br />
|-<br />
| Deleted || Deleted (11) || No files ||<br />
|}<br />
<br />
Unlisted versions are submitted and auto-Approved (4) without affecting the add-on status. So, add-ons that are exclusively unlisted have an add-on status of Incomplete (0) and Approved (4) files.<br />
<br />
An add-on version can have multiple files, and it used to be possible for them to have a different review status. That's the reason the review status is stored in the file rather than the version. Most if not all cases preventing the status to be moved up to the version are fixed now.<br />
<br />
For add-ons with listed versions, Beta (7) is another valid file status. Like unlisted versions, they are submitted and auto-approved. They are listed in the Developer Channel section in the listing page ([https://addons.mozilla.org/addon/noscript/#beta-channel for example]). <br />
<br />
A version can be listed or unlisted depending on its <code>channel</code>, which is set to 1 for Unlisted and 2 for Listed.<br />
<br />
A developer can hide their listing page using the <code>inactive</code> field in the add-on.<br />
<br />
= Featured Add-ons and Collections=<br />
TODO</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2017-03-20&diff=1166170WeeklyUpdates/2017-03-202017-03-20T17:21:52Z<p>Jorge.villalobos: Adding myself</p>
<hr />
<div><br />
{{WeeklyUpdateNav}}<br />
* Every Monday @ 11:00am Pacific Time (19:00 UTC) <br />
* https://air.mozilla.org/channels/project-meeting/ to watch and listen<br />
* join irc.mozilla.org #airmozilla for backchannel discussion<br />
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak. <br />
{{conf|8600}}<br />
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br />
* A hearty thank you to everyone who participated in the AMO mobile redesign testing: bobchao, Hossain Al Ikram, Kazi Nuzhat Tasnem, Nazir Ahmed Sabbir, Maruf Rahman, Tanvir Rahman, Roman Syed, Md.Majedul islam, Saddam Hossain, Md. Almas Hossain, Sayed Ibn Masud, Akash, Sajal Ahmed, Aminul Islam Alvi, Subash.M, Surentharan, Karthikeyan Sethumadhavan, AbiramiSD<br />
* Thank you to Viswaprasanth Ks, Martin Giger, Michael Kohler, and Andre Garzia for running the "Build Your Own WebExtension" activity for the India-Tamilnadu, Switzerland, and Brazil communities as part of Activate!<br />
* Thanks to Mozilla Tech Speakers and friends who spoke about Firefox, Mozilla & the Web at #FOSSASIA in Singapore this weekend: Bob Reyes, Mijanur, Trishul, Diky, Dietrich, Santosh, & Chiko<br />
* Thanks to Julien Wajsberg for his first post on Mozilla Hacks: [https://hacks.mozilla.org/2017/03/internationalize-your-keyboard-controls/ Internationalize your keyboard controls]<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
* [[Add-ons/Contribute/Triage#Next_Meeting|WebExtensions Triage]]<br />
** Good first bugs triage: 10:00am PST; WebExtensions Triage: 10:30am PST<br />
** Join the add-ons team to discuss good first bugs, design-decision-needed WebExtensions APIs, and WebExtensions Experiments!<br />
** To submit a WebExtensions Experiment for discussion, please open an issue on the [https://github.com/web-ext-experiments/about/issues web-ext-experiments github repo].<br />
<br />
*[http://austinjavascript.com/posts/meetups/2017/03/13/ Mozilla Developer Roadshow] with AustinJS will present WebAssembly with Lin Clark and Luke Wagner<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
* '''[https://indiewebcamp.com/events/2017-03-22-homebrew-website-club Homebrew Website Club Meetup]''' (nearly every Wednesday somewhere)<br/><strong>Be a part of the open web with your own website.</strong><br />
** '''Berlin (GERMANY)''', <br/>'''London (ENGLAND)''', <br/>'''Baltimore (<abbr title="Maryland">MD</abbr>)''', <br/>'''Bellingham (<abbr title="Washington">WA</abbr>)''', <br/>'''San Francisco''' (this week @MatterVC in South Park)<br />
** 17:30-18:30 Quiet Writing Hour, finish that blog post, wiki edit, etc.!<br />
** 18:30-19:30 IndieWeb meetup, demos, & hack night <blockquote><p>Create or update your personal web site!<br/>Share what you've gotten working, ask the experts questions.</p><p>Join a community with like-minded interests. <br/>Bring friends that want a personal site!</p></blockquote> Any questions? See '''[https://indiewebcamp.com/events/2017-03-22-homebrew-website-club the wiki page for details]''' <br/>or join IRC: http://indieweb.org/irc/today<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
*[http://bsidesok.com BSide Ok] is happening the 23rd and 24th of March in Tulsa, Oklahoma<br />
** BsidesOK is a community-driven event focused on improving information security awareness and skills. <br />
**Mozillians Luke Crouch and Josh Mize attending and speaking<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br />
*[https://generalassemb.ly/education/how-css-grid-is-reinventing-webpage-design/new-york-city/34842 Mozilla Developer Roadshow] at General Assembly NYC will present CSS Grid and Layout with Jen Simmons<br />
<br />
=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
== Speakers ==<br />
<br />
The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! [https://mozillians.org/u/USERNAME Presenter]<br />
! Title<br />
! Topic<br />
! Location<br />
! Sharing<br />
! Media<br />
! More Details<br />
|-<br />
| Who Are You?<br />
| What Do You Do?<br />
| What are you going to talk about?<br />
| Where are you presenting from? (Moz Space, your house, space)<br />
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
| Tom Ritter<br />
| Security Engineering<br />
| Third Party Library Alerts<br />
| Remote<br />
| No<br />
| [https://github.com/mozilla-services/third-party-library-alert This webpage] (or not, it's not necessary)<br />
| https://github.com/mozilla-services/third-party-library-alert<br />
|-<br />
| Jenn Beard<br />
| Gigabit Fund Manager at the Mozilla Foundation<br />
| Mozilla Gigabit Community Fund is expanding to two new cities: Eugene, OR and Lafayette, LA<br />
| Remote (Kansas City)<br />
| --<br />
| --<br />
| https://blog.mozilla.org/blog/2017/03/14/public-private-partnership-gigabit-innovation-internet-health/<br />
|-<br />
| Hugo<br />
| Pocket Product Manager<br />
| Weekly Pocket Update<br />
| SF (Pocket Office)<br />
| No<br />
| --<br />
| --<br />
|-<br />
| Winnie Aoieong & Liz Compton<br />
| Finance & Legal Ops<br />
| Introduction to CASA (Replacement of Project Kick-Off Form)<br />
| SF (Winnie) & MV (Liz)<br />
| No<br />
| --<br />
| --<br />
|-<br />
| Joe Cheng<br />
| Firefox Product Management<br />
| Firefox for Android updates<br />
| Toronto<br />
| No, if someone can advance the slides for me<br />
| https://goo.gl/myLGuI<br />
| --<br />
|-<br />
| [https://mozillians.org/u/jorgev/ Jorge Villalobos]<br />
| AMO Product Manager<br />
| Migrating to WebExtensions<br />
| Costa Rica<br />
| No<br />
| --<br />
| [https://blog.mozilla.org/addons/2017/03/17/migrating-webextensions-dont-forget-users/ Blog post]<br />
|-<br />
|}<br />
<br />
= Welcome! =<br />
<br />
Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! ''Who is being introduced?''<br />
! ''Who are you? (the introducer)''<br />
! ''Where are you doing the introduction?''<br />
! ''Where are they from?''<br />
! ''How will they be part of Mozilla?''<br />
|-<br />
<!-- Insert new rows here --><br />
| Susy Struble<br />
| Patrick Finch<br />
| SF Commons<br />
| Bay Area<br />
| Open Innovation team<br />
<br />
|-<br />
| Sierra Reed<br />
| Liz Hull<br />
| PDX + MTV (Sierra is in MTV)<br />
| Bay Area<br />
| Social + Influencer Relations<br />
|-<br />
| Justin O'Kelly<br />
| Jen Boscacci<br />
| MTV + SF (Justin is in SF)<br />
| Seattle<br />
| Executive Communications<br />
|}<br />
<br />
= Fireside Chat =<br />
A chance to hear from leadership at Mozilla, and have a short Q&A about a specific topic.<br />
<br />
===This Week===<br />
<br />
'''Next steps for Mozilla’s Internet Health efforts: Issue Briefs'''<br />
<br />
===Presenters===<br />
<br />
'''Chris Riley''', Head of Public Policy<br />
<br />
'''Sam Burton''', Director, Insights, Mozilla Foundation <br />
<br />
===Topic===<br />
<br />
Earlier this year, we published our first Internet Health Report, an open source research project that highlights the current state of, and what lies ahead for, the Internet. In the report we broke down the concept of Internet health into five issues. Now, we are publishing in-depth issue briefs about each of them: online privacy and security, decentralization, open innovation, web literacy, and digital inclusion. We believe these issues are the building blocks to a healthy and vibrant Internet. Through these briefs, we talk a little bit more about what these issues mean to Mozilla, what problems we are trying to solve to improve Internet health, and what we are doing as an organization to make a difference.<br />
<br />
You can submit questions in advance on the [https://moderator.mozilla.org/e/fireside-chat-3-20-next-steps-for-mozilla-s-internet-health-efforts-issue-briefs-with-denelle-dixon-chief-legal-and-business-officer-and-chris-riley-head-of-public-policy-and-sam-burton-issues-insights-impact-lead-mozilla-foundation Moderator Page], or ask them live on Air Mozilla using a Mozilla Space mic or in #airmozilla on IRC.<br />
<br />
[https://blog.mozilla.org/blog/2017/03/15/five-issues-that-will-determine-the-future-of-internet-health/ Blog post announcing the briefs].<br />
* [https://blog.mozilla.org/wp-content/uploads/2017/03/IHPbriefs_online_Privacy_March_2017.pdf Online privacy & security]<br />
* [https://ffp4g1ylyit3jdyti1hqcvtb-wpengine.netdna-ssl.com/wp-content/uploads/2017/03/IHPbriefs_decentralization_March_2017.pdf Decentralization]<br />
* [https://ffp4g1ylyit3jdyti1hqcvtb-wpengine.netdna-ssl.com/wp-content/uploads/2017/03/IHPbriefs_openness_March_2017.pdf Openness]<br />
* [https://ffp4g1ylyit3jdyti1hqcvtb-wpengine.netdna-ssl.com/wp-content/uploads/2017/03/IHPbriefs_web_Literacy_March_2017.pdf Web literacy]<br />
* [https://ffp4g1ylyit3jdyti1hqcvtb-wpengine.netdna-ssl.com/wp-content/uploads/2017/03/IHPbriefs_digital_Inclusion_March_2017.pdf Digital inclusion]<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/AMO-Manual&diff=1166060Add-ons/AMO-Manual2017-03-17T23:51:27Z<p>Jorge.villalobos: Added a couple of placeholders</p>
<hr />
<div>This is a collection of guides that should help AMO Engineers and other Mozillians navigate the madness that is the add-ons world.<br />
=Add-on types=<br />
[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#type MDN Doc] for add-on types.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Type !! In <code>install.rdf</code> !! In AMO DB !! Notes<br />
|-<br />
| Extension || 2 || 1 ||<br />
|-<br />
| Lightweight theme || ''N/A'' || 9 ||<br />
|-<br />
| Dictionary || 64 || 3 || Language for the Firefox spellchecker.<br />
|-<br />
| Search Engine || ''N/A'' || 4 || For the Firefox search box. [https://developer.mozilla.org/en-US/Add-ons/Creating_OpenSearch_plugins_for_Firefox See doc].<br />
|-<br />
| Language pack || 8 || 5 || Localization for Firefox UI. Most are automatically published from Firefox sources.<br />
|-<br />
| Complete theme || 4 || 2 || Deprecated. Will be dropped in Firefox 57.<br />
|-<br />
| Multi-package installer || 32 || 1 || Discontinued.<br />
|-<br />
| Telemetry Experiment || 128 || ''N/A'' ||<br />
|-<br />
| WebExtension Experiment || 256 || ''N/A'' ||<br />
|}<br />
<br />
WebExtension packages don't have types. They are all treated like extensions, with the exception of new themes (WIP).<br />
<br />
The AMO DB has a couple more types that are no longer in use: 7 - Plugins, 6 - Language Packs (Add-on), 11 - Apps.<br />
<br />
= Compatibility =<br />
<br />
[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#targetApplication MDN doc] on compatibility for legacy add-ons.<br />
<br />
Compatibility with the client depends on various factors. They are listed here in order of priority (next one overrides previous one):<br />
* Default compatibility.<br />
** Legacy add-ons with a <code>maxVersion</code> lower than Firefox 4.0a1 have strict compatibility, so the <code>maxVersion</code> must be respected.<br />
** For all other add-ons, the <code>maxVersion</code> doesn't matter.<br />
** The <code>minVersion</code> for legacy add-ons should always be respected.<br />
** WebExtensions have default minimum compatibility of Firefox 42.0a1.<br />
** Application support (Firefox / Thunderbird / SeaMonkey / Android) is read from the manifest and can be altered during submission (All Desktop / Windows / Linux / Mac OS / Android).<br />
* Strict compatibility.<br />
** Legacy add-ons with the <code>[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#strictCompatibility strictCompatibility]</code> manifest flag must have the <code>maxVersion</code> respected.<br />
** WebExtensions [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/applications that declare so] must have the <code>strict_min_version</code> and <code>strict_max_version</code> respected. A <code>strict_min_version</code> lower than 42.0a1 should be ignored.<br />
* AMO Metadata (editable in Developer Hub).<br />
** For add-ons with strict compatibility (legacy and WebExtensions) this overrides what is declared in the manifest.<br />
** Application support can also be altered here.<br />
* Compatibility overrides. These are admin overrides that declare a version range for an add-on is '''not''' compatible with a version range of an application (usually Firefox).<br />
<br />
This doesn't apply to lightweight themes and search engines.<br />
<br />
=Add-on and File Statuses=<br />
TODO<br />
<br />
= Featured Add-ons and Collections=<br />
TODO</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/AMO-Manual&diff=1166058Add-ons/AMO-Manual2017-03-17T23:43:07Z<p>Jorge.villalobos: Tweaks</p>
<hr />
<div>This is a collection of guides that should help AMO Engineers and other Mozillians navigate the madness that is the add-ons world.<br />
=Add-on types=<br />
[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#type MDN Doc] for add-on types.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Type !! In <code>install.rdf</code> !! In AMO DB !! Notes<br />
|-<br />
| Extension || 2 || 1 ||<br />
|-<br />
| Lightweight theme || ''N/A'' || 9 ||<br />
|-<br />
| Dictionary || 64 || 3 || Language for the Firefox spellchecker.<br />
|-<br />
| Search Engine || ''N/A'' || 4 || For the Firefox search box. [https://developer.mozilla.org/en-US/Add-ons/Creating_OpenSearch_plugins_for_Firefox See doc].<br />
|-<br />
| Language pack || 8 || 5 || Localization for Firefox UI. Most are automatically published from Firefox sources.<br />
|-<br />
| Complete theme || 4 || 2 || Deprecated. Will be dropped in Firefox 57.<br />
|-<br />
| Multi-package installer || 32 || 1 || Discontinued.<br />
|-<br />
| Telemetry Experiment || 128 || ''N/A'' ||<br />
|-<br />
| WebExtension Experiment || 256 || ''N/A'' ||<br />
|}<br />
<br />
WebExtension packages don't have types. They are all treated like extensions, with the exception of new themes (WIP).<br />
<br />
The AMO DB has a couple more types that are no longer in use: 7 - Plugins, 6 - Language Packs (Add-on), 11 - Apps.<br />
<br />
= Compatibility =<br />
<br />
[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#targetApplication MDN doc] on compatibility for legacy add-ons.<br />
<br />
Compatibility with the client depends on various factors. They are listed here in order of priority (next one overrides previous one):<br />
* Default compatibility.<br />
** Legacy add-ons with a <code>maxVersion</code> lower than Firefox 4.0a1 have strict compatibility, so the <code>maxVersion</code> must be respected.<br />
** For all other add-ons, the <code>maxVersion</code> doesn't matter.<br />
** The <code>minVersion</code> for legacy add-ons should always be respected.<br />
** WebExtensions have default minimum compatibility of Firefox 42.0a1.<br />
** Application support (Firefox / Thunderbird / SeaMonkey / Android) is read from the manifest and can be altered during submission (All Desktop / Windows / Linux / Mac OS / Android).<br />
* Strict compatibility.<br />
** Legacy add-ons with the <code>[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#strictCompatibility strictCompatibility]</code> manifest flag must have the <code>maxVersion</code> respected.<br />
** WebExtensions [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/applications that declare so] must have the <code>strict_min_version</code> and <code>strict_max_version</code> respected. A <code>strict_min_version</code> lower than 42.0a1 should be ignored.<br />
* AMO Metadata (editable in Developer Hub).<br />
** For add-ons with strict compatibility (legacy and WebExtensions) this overrides what is declared in the manifest.<br />
** Application support can also be altered here.<br />
* Compatibility overrides. These are admin overrides that declare a version range for an add-on is '''not''' compatible with a version range of an application (usually Firefox).<br />
<br />
This doesn't apply to lightweight themes and search engines.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/AMO-Manual&diff=1166057Add-ons/AMO-Manual2017-03-17T23:36:49Z<p>Jorge.villalobos: First draft</p>
<hr />
<div>This is a collection of guides that should help AMO Engineers and other Mozillians navigate the madness that is the add-ons world.<br />
=Add-on types=<br />
[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#type MDN Doc] for add-on types.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Type !! In <code>install.rdf</code> !! In AMO DB !! Notes<br />
|-<br />
| Extension || 2 || 1 ||<br />
|-<br />
| Lightweight theme || ''N/A'' || 9 ||<br />
|-<br />
| Dictionary || 64 || 3 || Language for the Firefox spellchecker.<br />
|-<br />
| Search Engine || ''N/A'' || 4 || For the Firefox search box. [https://developer.mozilla.org/en-US/Add-ons/Creating_OpenSearch_plugins_for_Firefox See doc].<br />
|-<br />
| Language pack || 8 || 5 || Localization for Firefox UI. Most are automatically published from Firefox sources.<br />
|-<br />
| Complete theme || 4 || 2 || Deprecated. Will be dropped in Firefox 57.<br />
|-<br />
| Multi-package installer || 32 || 1 || Discontinued.<br />
|-<br />
| Telemetry Experiment || 128 || ''N/A'' ||<br />
|-<br />
| WebExtension Experiment || 256 || ''N/A'' ||<br />
|}<br />
<br />
WebExtension packages don't have types. They are all treated like extensions, with the exception of new themes (WIP).<br />
<br />
The AMO DB has a couple more types that are no longer in use: 7 - Plugins, 6 - Language Packs (Add-on), 11 - Apps.<br />
<br />
= Compatibility =<br />
<br />
[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#targetApplication MDN doc] on compatibility.<br />
<br />
Compatibility with the client depends on various factors. They are listed here in order of priority (next one overrides previous one):<br />
* Default compatibility.<br />
** Legacy add-ons with a <code>maxVersion</code> lower than Firefox 4.0a1 have strict compatibility, so the <code>maxVersion</code> must be respected.<br />
** For all other add-ons, the <code>maxVersion</code> doesn't matter.<br />
** The <code>minVersion</code> for legacy add-ons should always be respected.<br />
** WebExtensions have default minimum compatibility of Firefox 42.0a1.<br />
** Application support (Firefox / Thunderbird / SeaMonkey / Android) is read from the manifest and can be altered during submission (All Desktop / Windows / Linux / Mac OS / Android).<br />
* Strict compatibility.<br />
** Legacy add-ons with the <code>[https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#strictCompatibility strictCompatibility]</code> manifest flag must have the <code>maxVersion</code> respected.<br />
** WebExtensions [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/applications that declare so] must have the <code>strict_min_version</code> and <code>strict_max_version</code> respected. A <code>strict_min_version</code> lower than 42.0a1 should be ignored.<br />
* AMO Metadata.<br />
** For add-ons with strict compatibility (legacy and WebExtensions), the editable metadata in the DevHub overrides what is declared in the manifest.<br />
** Application support can also be altered here.<br />
* Compatibility overrides. These are admin overrides that declare a version range for an add-on is not compatible with a version range of an application (usually Firefox).</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Reviewers/Guide/Reviewing&diff=1164770Add-ons/Reviewers/Guide/Reviewing2017-03-06T21:26:37Z<p>Jorge.villalobos: Updated email address</p>
<hr />
<div>= Performing a Review =<br />
'''Reviewer Intro Tour:''' ask your guide to select an add-on for you to review. Don't submit your first review without their pre-approval!<br />
<br />
Add-on reviewers have a big responsibility. We need to ensure add-ons are safe to use, of good quality, and clearly presented to users. We also need to make sure developers get quick, clear, and actionable reviews.<br />
<br />
Our general policy is to '''only reject when necessary'''. Rejection is necessary when an add-on has security or privacy issues, doesn't meet our content policies, or fits one of the special cases spelled out later in this guide.<br />
<br />
== Policies and actions ==<br />
The rest of this page explains policies and recommended actions for common add-on issues. Add-ons must be reviewed '''completely''', and all issues written down as they are found. Once the review is complete, the sum of all noted issues is used to determine what the review resolution should be. Regardless of the result, all issues should be included in the notes sent to developers.<br />
<br />
= Step 1: Review Add-on Metadata =<br />
<br />
Our review process does not involve reviewing for copyright infringement of any kind. The [http://en.wikipedia.org/wiki/Digital_Millennium_Copyright_Act DMCA] gives us protection from liability for hosting content that infringes copyright because of how hard it would be to review each add-on we host for copyright infringement. If you see something egregious, feel free to escalate it for super-review but we do not specifically review any content for copyright concerns.<br />
<br />
If you have any concerns about the legality or legitimacy of an add-on, please email amo-admins AT mozilla DOT org.<br />
<br />
== Policies and Actions ==<br />
<br />
{| cellspacing="0" cellpadding="1" border="0" style="width: 80%"<br />
|+ <br />
|-<br />
! style="border-bottom: 2px solid black" scope="col" | Issue <br />
! style="border-bottom: 2px solid black" scope="col" | Action <br />
! style="border-bottom: 2px solid black" scope="col" | Notes<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | The add-on doesn't comply with the Mozilla [https://www.mozilla.org/en-US/about/legal/acceptable-use/ Conditions of Use].<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | These are add-ons which do things like: <br />
* Anything illegal.<br />
* Threaten, harass, or violate privacy.<br />
* Harm users such as by using viruses, malware, or other malicious code.<br />
* Have the direct purpose of facilitating access to pornography. This includes, add-ons that specifically interact with, or direct users to, porn sites, but does not include add-ons such as image downloaders that may be used to access pornography but also have other purposes. <br />
<br />
Make sure to read the rest of the list [https://www.mozilla.org/en-US/about/legal/acceptable-use/ here].<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | The add-on improperly uses Mozilla trademarks in its name.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | We allow the use of certain trademarks when appended to the name of an add-on (e.g., "Video downloader for Firefox", "Inspector for Mozilla") in such a way as not to cause confusion as to the origin of the add-on. We do not allow uses which may suggest that the add-on is a Mozilla product (e.g., "Firefox downloader", "My Mozilla downloader", "Firefox++"). When in doubt, ask an admin or request super-review.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | The add-on doesn't provide enough information in its descriptions for users to figure out what it does.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Request more information <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Explain clearly why the provided description is insufficient, and what needs to be done to improve it. Once the developer has corrected the deficiencies and contacted us, the review may be completed without a further upload.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | The add-on name and/or code appear copied or very similar to a popular add-on (like AdBlock Plus).<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Request super-review<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | These add-ons can include malicious code, and trick users into mistaking them for the original. We accept add-on forks, and add-ons with similar features to other add-ons, but we need to be very careful to ensure that they do not mislead users.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Missing Privacy Policy when necessary.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Request more information<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | A Privacy Policy is required if an add-on sends any user information to a remote server, even if it is not personally-identifying. Even stats pings require a Privacy Policy. Reject if there's no reply from the developer.<br />
|}<br />
<br />
== Add-on Relevance ==<br />
<br />
Add-ons must not be rejected because a reviewer doesn't find them useful. We let AMO users make that call, and add-ons that aren't very useful won't gain much usage and have low search rankings, so they'll stay mostly out of the way.<br />
<br />
However, if it looks like an add-on shouldn't be '''listed''' on AMO, because it's intended for an internal company deployment, for testing purposes, or only private use, it should be rejected with the suggestion to go unlisted instead, and a link to the [https://developer.mozilla.org/en-US/Add-ons/Distribution Distribution page].<br />
<br />
Add-ons that are potentially dangerous and have a limited audience (like SSL certificate installers) should be Rejected, while noting to the developer that they can submit the add-on as [https://developer.mozilla.org/en-US/Add-ons/Distribution Unlisted].<br />
<br />
= Step 2: Automatic validation =<br />
<br />
We have an extensive set of tests that identify common bad practices and possible security problems with add-on code. Reviewers must run the code validator and inspect the results when performing a review. Each Add-on History entry has a validation link, and you'll want to validate the latest one.<br />
<br />
[[Image:Validation-link.png|center|Add-on validation link]] <br />
<br />
Clicking on the link will take you to the validation page, where the automatic code validator will run for that version of the add-on and then the results will be displayed. We recommend opening this link in a new tab.<br />
<br />
==== Policies and actions ====<br />
<br />
{| width="80%" cellspacing="0" cellpadding="1" border="0"<br />
|-<br />
! style="border-bottom: 2px solid black" scope="col" | Issue <br />
! style="border-bottom: 2px solid black" scope="col" | Action <br />
! style="border-bottom: 2px solid black" scope="col" | Notes<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Using <code>eval()</code>, <code>Function()</code> to evaluate JS code.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | <code>eval</code> may sometimes be allowed when it is used carefully to patch Firefox functions with local code.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Using <code>setTimeout()</code>, <code>setInterval()</code>, or properties like <code>onclick</code> to evaluate JS code.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | They may be used with hardcoded JS strings, but using closures is preferred. Only reject if it's clear from the surrounding code that remote code is being evaluated.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Remote script injection. <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add-ons can use data-only APIs, but should never download and execute remote code, not even in the scope of a webpage. Any use of the <code><script></code> tag (like <code>createElement("script")</code>) needs to be carefully analyzed. Using remote [http://en.wikipedia.org/wiki/Proxy_auto-config PAC] files is not allowed.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | <code><browser></code> or <code><iframe></code> elements with no <code>type</code> attribute, used in privileged documents.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | See the [https://developer.mozilla.org/en/XUL/iframe#a-browser.type iframe documentation]. The type must be one of <code>"content"</code>, <code>"content-targetable"</code>, or <code>"content-primary"</code>. This must be done ''before'' anything is loaded on that <code>iframe</code>. If the <code>iframe</code> or <code>browser</code> is used to load only chrome content, and it is clear from the code that it will never load anything else, <code>type="chrome"</code> may be used when necessary.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Storing passwords or other sensitive user data in the preferences.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Passwords and other sensitive data should be stored in the login service rather than in preferences.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Changing Firefox preferences without user consent.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | These include: network preferences, update system preferences, homepage, User Agent string. They also must be restored to their previous values when the add-on is uninstalled.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Inserting content with <code>innerHTML</code>.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject if it's clear from the surrounding code that the code being injected is remote and unsanitized. The canned response points to the [https://developer.mozilla.org/en-US/Add-ons/Overlay_Extensions/XUL_School/DOM_Building_and_HTML_Insertion preferred documentation] about this topic. Assignments to <code>innerHTML</code> will result in the execution of any JavaScript code present in the injected string. Since this issue can often be confusing to developers, make sure to include a reference to a code file and line where this occurs.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Using DOM Mutation events.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | [https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver Mutation Observers] are the recommended alternative.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Native object prototype extension / Using the Prototype library.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | This only applies in XUL overlays, where the prototype extension affects the prototypes used by Firefox code and other overlays.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Changing security preferences, permissions, certificates (<code>nsIX509CertDB</code>).<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Request super-review<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | <br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Using <code>nsIProcess</code>.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Request super-review<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | <br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Using JS c-types.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Request super-review<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | <br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Localization errors.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Ignore <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Errors which result in breakage should result in rejection when built-in Firefox UIs are affected, and just a note if only add-on interfaces are affected. Otherwise, they should be ignored.<br />
|}<br />
<br />
There are many other validation flags of varying importance. If you're unsure about which action to take, please ask on the mailing list.<br />
<br />
= Step 3: Code Review =<br />
<br />
All add-on code must be reviewed. Automation can't detect all possible security or code quality issues, which is why we have human reviewers.<br />
<br />
All Add-on History entries have a View Contents link that take you to the code browser page. Updates also have a Compare link, which will show you the code with the changed sections highlighted. For updates, the compare link should be used. Validation results are integrated into the code viewer, so you can see validation warnings in context. It's okay if you prefer to use other tools for code analysis and diffing.<br />
<br />
== Libraries, frameworks and other unreadable code ==<br />
<br />
It's very common for add-ons to use libraries or frameworks such as jQuery or Bootstrap. Some add-ons use complex frameworks like Kango, usually to achieve cross-browser compatibility. Finally, the Add-ons SDK generates various files around the actual add-on code. Our code validator will try to detect them, but won't work in every case. If detected, the library code won't generate validator warnings and it will be greyed out in the code viewer.<br />
<br />
All libraries on [https://github.com/mozilla/amo-validator/blob/master/validator/testcases/hashes-allowed.txt this list] should be ignored, even if the validator doesn't detect them correctly. All other libraries should be handled carefully. The reviewer should find the original library file and diff it against the one included in the add-on, and also ensure the library doesn't do anything dangerous.<br />
<br />
Aside from libraries, many add-ons can include minified, obfuscated or compiled code. Since this code can't be easily reviewed without the original sources, only admin reviewers should review them. The Add-on History entry should indicate if the source code has been provided by the developer. If that's not the case, you can use the canned info request.<br />
<br />
== Policies and Actions ==<br />
<br />
{| width="80%" cellspacing="0" cellpadding="1" border="0"<br />
|-<br />
! style="border-bottom: 2px solid black" scope="col" | Issue <br />
! style="border-bottom: 2px solid black" scope="col" | Action <br />
! style="border-bottom: 2px solid black" scope="col" | Notes<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Remote code download or execution, custom update code.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | As explained in the validation section, no remote code execution is allowed.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Using plain HTTP for security-sensitive operations.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Sending passwords over unprotected HTTP if there's a secure alternative. Sending passwords in the URL or other headers than POSTDATA. Performing any security-sensitive operations over HTTP when there's a secure alternative. <br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Using non-release version of Add-ons SDK.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | The validator can detect many experimental versions of the SDK, but that doesn't make it OK to use in add-ons.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Using outdated Add-ons SDK library.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | We accept the two most recent minor releases of the Add-on SDK.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Bad or no namespacing.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | All scripts that are included in the main window overlay should have proper namespacing to avoid name conflicts with other add-ons. The name should normally correspond to the add-on name in order to guarantee its uniqueness.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Privacy issues.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | An add-on can claim to work with a popular website like Twitter, but then send the user data through some other site, most likely owned by the developer. There needs to be a justified reason to handle user data in this manner, and the privacy policy and add-on descriptions need to be very clear about this. Passwords should never be handled in this way, and they should only be transmitted directly to the original API provider (Reject otherwise).<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Preference names without "extensions." or "services.sync.extensions." prefix.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add-on preferences should use the "extensions." prefix, and should also have a reasonable namespace (like "extensions.myVideoDownloader.").<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Performance problems.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Synchronous (non-local) HTTP requests, synchronous SQL queries, noticeably inefficient code, random UI freezes, loading large amounts of JS code directly in overlays. Reject if the issues cause noticeable lag while testing.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Writing files outside of the profile folder.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Some add-ons need helper files like SQL DBs or logs. Those files must be written in the profile folder, not the extension installation folder or other locations.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Bootstrapped or SDK add-on doesn't clean up after itself. <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Some things to look for: the add-on must not require a restart for any of its features to fully work, must not require a restart after being disabled or uninstalled, must unregister all observers and remove all UI when disabled or uninstalled. [http://maglione-k.users.sourceforge.net/bootstrapped.xhtml More details].<br />
|- style="vertical-align: top;"<br />
| style="padding: 0.5ex 1ex 1ex 0pt; border-bottom: 1px solid black;" | Using non-standard preferences UI.<br />
| style="padding: 0.5ex 1ex 1ex 0pt; border-bottom: 1px solid black;" | Add note<br />
| style="padding: 0.5ex 1ex 1ex 0pt; border-bottom: 1px solid black;" | If an add-on has a preferences UI, it should use one of the [https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#optionsURL supported methods].<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Duplicate / hidden files or folders.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | See canned response.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | New version doesn't follow previous review requests.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Ignore if they are minor issues.<br />
|}<br />
<br />
In general you should apply your judgement and try to identify code that may appear suspicious or out of place. Try to understand what everything does and how it all fits together.<br />
<br />
== WebExtensions Policies and Actions ==<br />
<br />
This is a draft of WebExtensions Policies as WebExtensions are relatively new.<br />
<br />
{| width="80%" cellspacing="0" cellpadding="1" border="0"<br />
|-<br />
! style="border-bottom: 2px solid black" scope="col" | Issue <br />
! style="border-bottom: 2px solid black" scope="col" | Action <br />
! style="border-bottom: 2px solid black" scope="col" | Notes<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Abuse of chrome.storage.sync<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | It's noted in the docs that chrome.storage.sync is for storing preferences and other small amounts of data. It is not provided with any expectations of performance, stability or being able to store large amounts of data.<br />
|- style="vertical-align: top;"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | manifest.json includes permissions "nativeMessaging"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Request super-review<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | nativeMessaging must be carefully reviewed by an admin.<br />
|}<br />
<br />
= Step 4: Feature Review =<br />
<br />
The last step in a review is to install and test the add-on.<br />
<br />
Add-ons are normally cross-platform, in which case there will only be a single XPI to test. If the add-on is offered for a limited number of platforms or has different files for different platforms, there will be individual links for each one in the Add-on History entry.<br />
<br />
Regarding application support (Firefox / SeaMonkey / Thunderbird), you don't need to test the add-on on all of them. If the add-on supports Firefox and others, it's OK to only test using Firefox.<br />
<br />
== Testing setup ==<br />
<br />
* '''Always use a separate profile for testing''', never your main profile. See [https://developer.mozilla.org/en/Setting_up_extension_development_environment Setting up an extension development environment]. <br />
* Ideally you should perform your tests in a virtual machine. It is always useful in case you need to test in multiple platforms. [https://www.virtualbox.org/ VirtualBox] is free and works well. <br />
* Use [https://firefox.com/developer Firefox Developer Edition] for testing. If something needs to be tested on Beta or Release, you'll need to use the [[Addons/Extension_Signing|unbranded builds that can disable add-on signing enforcement]].<br />
* The [https://addons.mozilla.org/addon/extension-test Extension Test add-on] helps detect loose variables and DOM IDs, prototype extension, dangerous category registration, and other difficult to spot problems.<br />
* Test with the Browser Console always open, and look for errors or log messages generated by the add-on.<br />
<br />
== Policies and actions ==<br />
<br />
{| width="80%" cellspacing="0" cellpadding="1" border="0"<br />
|-<br />
! style="border-bottom: 2px solid black" scope="col" | Issue <br />
! style="border-bottom: 2px solid black" scope="col" | Action <br />
! style="border-bottom: 2px solid black" scope="col" | Notes<br />
|- style="vertical-align: top;" id="security-violations"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Security violations.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Adding HTTP content to HTTPS pages. If the add-on injects content like iframes or images, make sure to visit HTTPS sites the add-on supports and look for any security warnings in the URL bar.<br />
|- style="vertical-align: top;" id="no-surprises-violations"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | [https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Reviews#Privacy_and_User_Consent No Surprises] violation <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Changing homepage, default search provider, including unexpected ads or content changes without explicit user opt-in.<br />
|- style="vertical-align: top;" id="affiliate"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Affiliate linking.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Some add-ons add affiliate codes to Amazon links (or similar) in order to make money. At the moment we allow this as long as (1) the add-on follows the No Surprises policy, (2) the feature doesn't replace or remove any existing affiliate codes, (3) the affiliate codes aren't inserted in the merchant website's links (inserting Amazon affiliate codes in Amazon.com pages).<br />
|- style="vertical-align: top;" id="privacy-violations"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Privacy violations.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Incorrect or insufficient privacy policies, not respecting Private Browsing Mode.<br />
|- style="vertical-align: top;" id="modal-startup"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Showing a modal dialog at startup.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Reject<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Opening modal (blocking) dialogs at startup is not allowed. Non-modal dialogs, separate windows or new tabs are allowed.<br />
|- style="vertical-align: top;" id="errors"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Errors in the Browser Console.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Make sure the errors only occur with the add-on installed and are generated from add-on code and not Firefox code. In the latter case, it should only be noted.<br />
|- style="vertical-align: top;" id="confusing"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add-on is very hard to use even with instructions.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | If the testing instructions for the add-on are missing, use Request more information. We have [[Add-ons/Reviewers/Guide/Logins|frequently-used test accounts listed here]] (ask an admin for the password).<br />
|- style="vertical-align: top;" id="sticky-toolbar-buttons"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Toolbar buttons are not customizable.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Add note<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | It must be possible to remove add-on buttons from the toolbar and move them to the menu panel.<br />
|- style="vertical-align: top;" id="third-party-software"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Requires third party software or paid registration. <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Request super-review <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" |<br />
|- style="vertical-align: top;" id="content-ads"<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Inserts ads into content.<br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | Request super-review <br />
| style="padding: .5ex 1ex 1ex 0; border-bottom: 1px solid black;" | The rules in these cases are complex. They need to be clearly labeled as coming from the add-on, can't remove or replace existing ads, and need to follow No Surprises. There are also security concerns and privacy concerns that can lead to rejection.<br />
|}<br />
<br />
Other tests to perform:<br />
<br />
*Test all add-on features, within reason. If there are too many, focus on the main features.<br />
*Remove all added toolbar buttons, disable all added toolbars, and restart the browser. Make sure that buttons and toolbars are all removable and do not reappear on restart. Make sure that missing toolbar buttons do not cause errors to appear in the Error Console.<br />
*Open the Customize Toolbar UI and make sure that all buttons have appropriate icons and label text.<br />
*Open the add-on's preferences window, from the Add-ons Manager and elsewhere, and verify that preference changes apply properly. Make sure the window fits all of its contents (a common problem in Mac OS).<br />
<br />
= Step 5: Resolution =<br />
<br />
Choose the appropriate resolution and include all of your notes. Make sure you use a courteous and professional tone, and be as helpful as you can when pointing out problems or areas for improvement. The canned responses are very useful in formatting a response. Once you're ready, click the ''Save'' button. <br />
<br />
'''Reviewer Intro Tour:''' remember to ask the guide to give your response a look before sending it. After submitting your first review, make sure you spend some time reading the rest of the guide.<br />
<br />
[[Add-ons/Reviewers/Guide/Moderation|Next: Moderation]]</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons&diff=1164382Add-ons2017-03-02T22:48:05Z<p>Jorge.villalobos: Removed my blog</p>
<hr />
<div>=What=<br />
'''Mission''': Add-ons are a safe, simple, and powerful way for people to personalize their web experience.<br />
<p></p><br />
This is the home page for Add-ons at Mozilla.<br />
<p></p><br />
Including but not limited to:<br />
* Firefox Add-ons<br />
* Firefox for Android Add-ons<br />
* [https://addons.mozilla.org/firefox/ addons.mozilla.org (AMO)]<br />
* [[Add-ons/Extension_Signing|Extension Signing]]<br />
* [[WebExtensions|WebExtensions]]<br />
<br />
Looking for [[Add-ons/2017|2017 plans]]?<br />
<br />
=Who=<br />
<br />
*Note:* This is a list of people employed by Mozilla. But we are way more than that, please add yourselves in if you want.<br />
<br />
=== Engineering ===<br />
<br />
Engineering Managers:<br />
<br />
* Andy McKay ([https://phonebook.mozilla.org/#search/Andy%20McKay internal], [http://mckay.pub blog], [https://mozillians.org/en-US/u/andym/ Mozillian profile])<br />
* Stuart Colville ([https://phonebook.mozilla.org/#search/Stuart%20Colville internal], [https://muffinresearch.co.uk/ blog], [https://mozillians.org/en-US/u/scolville/ Mozillian Profile])<br />
<br />
Engineers:<br />
<br />
* Kumar McMillan ([https://phonebook.mozilla.org/#search/Kumar%20McMillan internal], [http://farmdev.com/ blog], [https://mozillians.org/en-US/u/scolville/ Mozillian Profile])<br />
* Mark Striemer ([https://phonebook.mozilla.org/#search/Mark%20Striemer internal])<br />
* Kris Maglione ([https://phonebook.mozilla.org/#search/kris%20m internal], [http://blog.5digits.org/ blog],[https://mozillians.org/en-US/u/John-Galt/ Mozillian Profile])<br />
* tofumatt (Matthew Riley MacPherson) ([https://phonebook.mozilla.org/#search/tofumatt internal])<br />
* Christopher Grebs ([https://phonebook.mozilla.org/#search/Christopher%20Grebs internal])<br />
* Luca Greco ([https://mozillians.org/en-US/u/luca/ Mozillian Profile])<br />
* Andrew Swan ([https://phonebook.mozilla.org/#search/Andrew%20Swan internal])<br />
* Matthew Wein ([https://phonebook.mozilla.org/#search/Matthew%20Wein internal])<br />
* Bob Silverberg ([https://phonebook.mozilla.org/#search/Bob%20Silverberg internal])<br />
* Mathieu Pillard ([https://phonebook.mozilla.org/#search/Mathieu%20Pillard internal]])<br />
* Shane Caraveo ([https://phonebook.mozilla.org/#search/Shane%20Caraveo internal], [https://mozillians.org/en-US/u/scaraveo/ Mozillian Profile])<br />
* Andrew Williamson ([https://phonebook.mozilla.org/?search/eviljeff internal], [https://mozillians.org/en-US/u/eviljeff/ Mozillian Profile]<br />
<br />
What [http://www.timeanddate.com/worldclock/meetingtime.html?p1=256&p2=136&p3=64&p4=195&p5=265&p6=202 time zones are we in]?<br />
<br />
Looking for the [http://addons.readthedocs.org/en/latest/server/push-duty.html push duty roster] maybe?<br />
<br />
=== User Experience ===<br />
* Markus Jaritz, UX Designer ([https://phonebook.mozilla.org/tree.php#search/markus@mozilla.com internal], [https://mozillians.org/en-US/u/mjaritz/ Mozillians])<br />
* Blake Winton, UX Engineer ([https://phonebook.mozilla.org/tree.php#search/bwinton@mozilla.com internal], [https://mozillians.org/en-US/u/bwinton/ Mozillians])<br />
* Philip Walmsley, Senior Visual Designer ([https://phonebook.mozilla.org/search.php?format=vcard&query=pwalmsley@mozilla.com internal])<br />
* ''more to come as we work on things other than the API...''<br />
<br />
=== Program and Product Management ===<br />
* Kev Needham, Product Manager ([https://phonebook.mozilla.org/tree.php#search/kneedham@mozilla.com internal], [http://kev.deadsquid.com/ blog], [https://mozillians.org/en-US/u/kev/ mozillians profile])<br />
* Shell Escalante, Program Manager ([https://phonebook.mozilla.org/#search/shell@mozilla.com internal], IRC:shell)<br />
<br />
=== [[Add-ons/ACE|Add-on Community Experience (ACE team)]] ===<br />
Developer Experience:<br />
* Jorge Villalobos, ([https://phonebook.mozilla.org/#search/jorge internal], [https://mozillians.org/en-US/u/jorgev/ mozillians profile])<br />
* Andreas Wagner, ([https://phonebook.mozilla.org/#search/andreas%20wagner internal], [https://mozillians.org/en-US/u/TheOne/ mozillians profile])<br />
* Philipp Kewisch, ([https://phonebook.mozilla.org/#search/kewisch internal], [https://mozillians.org/en-US/u/kewisch/ mozillians profile])<br />
<br />
Community & Editorial:<br />
* Amy Tsay, ([https://phonebook.mozilla.org/#search/tsay internal], [https://mozillians.org/en-US/u/amyt/ mozillians profile])<br />
* Scott DeVaney ([https://phonebook.mozilla.org/#search/devaney internal], [https://mozillians.org/en-US/u/sdevaney/ mozillians profile])<br />
* Caitlin Neiman ([https://phonebook.mozilla.org/#search/neiman internal], [https://mozillians.org/en-US/u/cneiman/ mozillians profile])<br />
<br />
=== QA ===<br />
* Krupa Raj, ([https://phonebook.mozilla.org/#search/krupa internal], [https://mozillians.org/en-US/u/kruparaj/ mozillians profile])<br />
* Victor Carciu<br />
* Madalin Cotetiu<br />
* Valentina Peleskei<br />
<br />
=Getting in touch=<br />
<br />
* Mailing list: https://mail.mozilla.org/listinfo/dev-addons<br />
<br />
* [[IRC|IRC]]:<br />
** #teamaddons: team chat <br />
** #addons: support for extensions, themes, plugins and addons.mozilla.org<br />
** #amo: addons.mozilla.org bugs and development<br />
** #amo-editors: add-on reviews and policy<br />
** #extdev: extension development<br />
** #themedev: theme development<br />
** #webextensions: web extensions<br />
<br />
* Blog: https://blog.mozilla.org/addons/<br />
* Forum: https://discourse.mozilla-community.org/c/add-ons<br />
<br />
== Meetings ==<br />
<br />
Please see the add-ons Calendar or mailing lists:<br />
<br />
* Mailing Lists: [https://mail.mozilla.org/listinfo/dev-addons dev-addons]<br />
* Calendar: [https://www.google.com/calendar/embed?src=mozilla.com_lr5jsh38i6dmr72uu4d1nv7dcc%40group.calendar.google.com Preview], [https://www.google.com/calendar/ical/mozilla.com_lr5jsh38i6dmr72uu4d1nv7dcc%40group.calendar.google.com/public/basic.ics iCal import]<br />
<br />
Most meetings are in the Add-ons Vidyo room. To access remotely:<br />
<br />
* Using Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=gBI6Q6943nQv <br />
* To join from a telephone: US Toll Free +1 800 707 2533, pin 369, conf 98839<br />
<br />
Minutes:<br />
<br />
* Most meetings [https://docs.google.com/document/d/1oNq9vZCNgMUnjJ0prfeWzudibtMwkCoNfVxN3a7j90A/edit add their minutes here].<br />
<br />
===Contribute to Add-ons===<br />
Support user freedom by helping to keep Firefox the most customizable browser available.<br />
*See how you can help: https://wiki.mozilla.org/Add-ons/Contribute<br />
*Subscribe to the [https://discourse.mozilla-community.org/c/add-ons/contribute Add-ons Contribution] forum to be kept in the loop about contribution opportunities and events. Click on the menu at the top-right corner of the page and select "Watching".<br />
<br />
=Status & Roadmap=<br />
[https://wiki.mozilla.org/Firefox/AddOns/Status/current Current Status] on 5 focus areas<br />
<p></p><br />
[https://docs.google.com/document/d/17o2l7VV9OBwXxGeEUQf0-4dZhlbbrJPkGbIXA-ht2Tg/edit# Weekly detailed notes] of current event discussions in Product, Engineering, Community, & UX<br />
<p></p><br />
[https://mozilla.aha.io/published/0d49e74c6853d3d721010bd9d4f67f34?page=1 Roadmap]: to the best of our ability, always in progress, so expect changes<br />
<br />
== Multi-process Firefox ==<br />
<br />
For information on the roll out of multi-process Firefox and add-ons, please see [https://wiki.mozilla.org/Electrolysis#Add-ons_Schedule the schedule]<br />
<br />
===Communications Calendar===<br />
Planning to communicate changes or coming features. One example is blogs, audiences, channels, and who will be writing/reviewing.<br />
<p></p><br />
{{#widget:Widget:Google Calendar<br />
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ<br />
}}<br />
<br />
=Product Backlog=<br />
* Improve work prioritization, so the team is always working on the most important features.<br />
* Simplify continual planning, so the plan matches reality.<br />
* Improve visibility so that the stakeholders make the best decisions about the direction of the product (call out risks early, relative priorities, trade-offs)<br />
<p> </p><br />
<p> </p><br />
<br />
==Triage Guidelines==<br />
===Bugzilla===<br />
<p> </p><br />
* '''Priorities''' follow this Standard:<br />
** Priority 1 - Blocker, must-fix before shipping or a priority feature we are including in this release.<br />
** Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping. For Features we'd really like it, but wouldn't hold shipping for it.<br />
** Priority 3 - Average Bug. definitely a problem, but doesn't stop someone from using the product. <br />
** Priority 4 - Minor or polish bugs that are real issues (especially in aggregate) and annoying.<br />
** Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability.<br />
<p> </p><br />
*'''Importance''' will be left at "normal" unless a bug is on the line of being one Priority higher and lower - and then will be marked "Major" or "Minor" accordingly.<br />
<p> </p><br />
*Optional '''Whiteboard tag'''<br />
**Adding a '''short descriptive area tag''' in the whiteboard when possible, to visually group bugs quickly in a list. ex: "[tabs] triaged"<br />
*Triaged bug mark-up<br />
**Adding '''triaged''' tag to the end of the Whiteboard for bugs that have been assigned a priority, so we know what has been triaged. No [] needed<br />
<br />
===Github===<br />
<p> </p><br />
*Added labels to [http://addons.readthedocs.org/en/latest/repositories.html add-ons repositories] for:<br />
**'''P1''' - either bug we would block next targeted featured for or a time-critical major bug<br />
**'''P2''' - either feature we'd really like, but wouldn't delay releasing the P1's for (good to look at after passing milestone). or Major impact bug, considering severity × probability. Not a blocker for shipping.<br />
**'''backlog''' - We know it's not in our immediate plans or roadmaps - but it's been noted<br />
*Added column to waffle boards for "triaged"<br />
**Move bugs from '''untriaged''' to '''triaged''' column after they've been looked at and Prioritized.<br />
<br />
==Common Queries==<br />
===[https://wiki.mozilla.org/WebExtensions#Useful_queries Webextensions]===<br />
<br />
===AMO===<br />
*Experimenting with [https://wiki.mozilla.org/Add-ons#Github new triage process], will change as needed <br />
*[https://waffle.io/mozilla/addons?source=mozilla%2Faddons-server,mozilla%2Faddons.mozilla.org-mod,mozilla%2Famo-validator,mozilla%2Faddons-frontend,mozilla%2Faddons-linter,mozilla%2Faddons,mozilla%2Fdispensary Triage Query]<br />
<br />
===Add-ons Manager===<br />
Handles installing, running and updating add-ons within Firefox. Also has pages like about:addons. In bugzilla - product: Toolkit, component<br />
*[http://mzl.la/1T6QAeZ Untriaged bugs within past 120 days]<br />
**follow [https://wiki.mozilla.org/Add-ons#Bugzilla bugzilla triage guidelines], process always open to change<br />
*[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=12941866&o1=substring&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=triaged&component=Add-ons%20Manager&product=Toolkit Triaged bugs] have '''triaged''' tag added to end of '''whiteboard'''</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons&diff=1164381Add-ons2017-03-02T22:47:15Z<p>Jorge.villalobos: Removing some old stuff</p>
<hr />
<div>=What=<br />
'''Mission''': Add-ons are a safe, simple, and powerful way for people to personalize their web experience.<br />
<p></p><br />
This is the home page for Add-ons at Mozilla.<br />
<p></p><br />
Including but not limited to:<br />
* Firefox Add-ons<br />
* Firefox for Android Add-ons<br />
* [https://addons.mozilla.org/firefox/ addons.mozilla.org (AMO)]<br />
* [[Add-ons/Extension_Signing|Extension Signing]]<br />
* [[WebExtensions|WebExtensions]]<br />
<br />
Looking for [[Add-ons/2017|2017 plans]]?<br />
<br />
=Who=<br />
<br />
*Note:* This is a list of people employed by Mozilla. But we are way more than that, please add yourselves in if you want.<br />
<br />
=== Engineering ===<br />
<br />
Engineering Managers:<br />
<br />
* Andy McKay ([https://phonebook.mozilla.org/#search/Andy%20McKay internal], [http://mckay.pub blog], [https://mozillians.org/en-US/u/andym/ Mozillian profile])<br />
* Stuart Colville ([https://phonebook.mozilla.org/#search/Stuart%20Colville internal], [https://muffinresearch.co.uk/ blog], [https://mozillians.org/en-US/u/scolville/ Mozillian Profile])<br />
<br />
Engineers:<br />
<br />
* Kumar McMillan ([https://phonebook.mozilla.org/#search/Kumar%20McMillan internal], [http://farmdev.com/ blog], [https://mozillians.org/en-US/u/scolville/ Mozillian Profile])<br />
* Mark Striemer ([https://phonebook.mozilla.org/#search/Mark%20Striemer internal])<br />
* Kris Maglione ([https://phonebook.mozilla.org/#search/kris%20m internal], [http://blog.5digits.org/ blog],[https://mozillians.org/en-US/u/John-Galt/ Mozillian Profile])<br />
* tofumatt (Matthew Riley MacPherson) ([https://phonebook.mozilla.org/#search/tofumatt internal])<br />
* Christopher Grebs ([https://phonebook.mozilla.org/#search/Christopher%20Grebs internal])<br />
* Luca Greco ([https://mozillians.org/en-US/u/luca/ Mozillian Profile])<br />
* Andrew Swan ([https://phonebook.mozilla.org/#search/Andrew%20Swan internal])<br />
* Matthew Wein ([https://phonebook.mozilla.org/#search/Matthew%20Wein internal])<br />
* Bob Silverberg ([https://phonebook.mozilla.org/#search/Bob%20Silverberg internal])<br />
* Mathieu Pillard ([https://phonebook.mozilla.org/#search/Mathieu%20Pillard internal]])<br />
* Shane Caraveo ([https://phonebook.mozilla.org/#search/Shane%20Caraveo internal], [https://mozillians.org/en-US/u/scaraveo/ Mozillian Profile])<br />
* Andrew Williamson ([https://phonebook.mozilla.org/?search/eviljeff internal], [https://mozillians.org/en-US/u/eviljeff/ Mozillian Profile]<br />
<br />
What [http://www.timeanddate.com/worldclock/meetingtime.html?p1=256&p2=136&p3=64&p4=195&p5=265&p6=202 time zones are we in]?<br />
<br />
Looking for the [http://addons.readthedocs.org/en/latest/server/push-duty.html push duty roster] maybe?<br />
<br />
=== User Experience ===<br />
* Markus Jaritz, UX Designer ([https://phonebook.mozilla.org/tree.php#search/markus@mozilla.com internal], [https://mozillians.org/en-US/u/mjaritz/ Mozillians])<br />
* Blake Winton, UX Engineer ([https://phonebook.mozilla.org/tree.php#search/bwinton@mozilla.com internal], [https://mozillians.org/en-US/u/bwinton/ Mozillians])<br />
* Philip Walmsley, Senior Visual Designer ([https://phonebook.mozilla.org/search.php?format=vcard&query=pwalmsley@mozilla.com internal])<br />
* ''more to come as we work on things other than the API...''<br />
<br />
=== Program and Product Management ===<br />
* Kev Needham, Product Manager ([https://phonebook.mozilla.org/tree.php#search/kneedham@mozilla.com internal], [http://kev.deadsquid.com/ blog], [https://mozillians.org/en-US/u/kev/ mozillians profile])<br />
* Shell Escalante, Program Manager ([https://phonebook.mozilla.org/#search/shell@mozilla.com internal], IRC:shell)<br />
<br />
=== [[Add-ons/ACE|Add-on Community Experience (ACE team)]] ===<br />
Developer Experience:<br />
* Jorge Villalobos, ([https://phonebook.mozilla.org/#search/jorge internal], [http://xulforge.com/blog/ blog], [https://mozillians.org/en-US/u/jorgev/ mozillians profile])<br />
* Andreas Wagner, ([https://phonebook.mozilla.org/#search/andreas%20wagner internal], [https://mozillians.org/en-US/u/TheOne/ mozillians profile])<br />
* Philipp Kewisch, ([https://phonebook.mozilla.org/#search/kewisch internal], [https://mozillians.org/en-US/u/kewisch/ mozillians profile])<br />
<br />
Community & Editorial:<br />
* Amy Tsay, ([https://phonebook.mozilla.org/#search/tsay internal], [https://mozillians.org/en-US/u/amyt/ mozillians profile])<br />
* Scott DeVaney ([https://phonebook.mozilla.org/#search/devaney internal], [https://mozillians.org/en-US/u/sdevaney/ mozillians profile])<br />
* Caitlin Neiman ([https://phonebook.mozilla.org/#search/neiman internal], [https://mozillians.org/en-US/u/cneiman/ mozillians profile])<br />
<br />
=== QA ===<br />
* Krupa Raj, ([https://phonebook.mozilla.org/#search/krupa internal], [https://mozillians.org/en-US/u/kruparaj/ mozillians profile])<br />
* Victor Carciu<br />
* Madalin Cotetiu<br />
* Valentina Peleskei<br />
<br />
=Getting in touch=<br />
<br />
* Mailing list: https://mail.mozilla.org/listinfo/dev-addons<br />
<br />
* [[IRC|IRC]]:<br />
** #teamaddons: team chat <br />
** #addons: support for extensions, themes, plugins and addons.mozilla.org<br />
** #amo: addons.mozilla.org bugs and development<br />
** #amo-editors: add-on reviews and policy<br />
** #extdev: extension development<br />
** #themedev: theme development<br />
** #webextensions: web extensions<br />
<br />
* Blog: https://blog.mozilla.org/addons/<br />
* Forum: https://discourse.mozilla-community.org/c/add-ons<br />
<br />
== Meetings ==<br />
<br />
Please see the add-ons Calendar or mailing lists:<br />
<br />
* Mailing Lists: [https://mail.mozilla.org/listinfo/dev-addons dev-addons]<br />
* Calendar: [https://www.google.com/calendar/embed?src=mozilla.com_lr5jsh38i6dmr72uu4d1nv7dcc%40group.calendar.google.com Preview], [https://www.google.com/calendar/ical/mozilla.com_lr5jsh38i6dmr72uu4d1nv7dcc%40group.calendar.google.com/public/basic.ics iCal import]<br />
<br />
Most meetings are in the Add-ons Vidyo room. To access remotely:<br />
<br />
* Using Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=gBI6Q6943nQv <br />
* To join from a telephone: US Toll Free +1 800 707 2533, pin 369, conf 98839<br />
<br />
Minutes:<br />
<br />
* Most meetings [https://docs.google.com/document/d/1oNq9vZCNgMUnjJ0prfeWzudibtMwkCoNfVxN3a7j90A/edit add their minutes here].<br />
<br />
===Contribute to Add-ons===<br />
Support user freedom by helping to keep Firefox the most customizable browser available.<br />
*See how you can help: https://wiki.mozilla.org/Add-ons/Contribute<br />
*Subscribe to the [https://discourse.mozilla-community.org/c/add-ons/contribute Add-ons Contribution] forum to be kept in the loop about contribution opportunities and events. Click on the menu at the top-right corner of the page and select "Watching".<br />
<br />
=Status & Roadmap=<br />
[https://wiki.mozilla.org/Firefox/AddOns/Status/current Current Status] on 5 focus areas<br />
<p></p><br />
[https://docs.google.com/document/d/17o2l7VV9OBwXxGeEUQf0-4dZhlbbrJPkGbIXA-ht2Tg/edit# Weekly detailed notes] of current event discussions in Product, Engineering, Community, & UX<br />
<p></p><br />
[https://mozilla.aha.io/published/0d49e74c6853d3d721010bd9d4f67f34?page=1 Roadmap]: to the best of our ability, always in progress, so expect changes<br />
<br />
== Multi-process Firefox ==<br />
<br />
For information on the roll out of multi-process Firefox and add-ons, please see [https://wiki.mozilla.org/Electrolysis#Add-ons_Schedule the schedule]<br />
<br />
===Communications Calendar===<br />
Planning to communicate changes or coming features. One example is blogs, audiences, channels, and who will be writing/reviewing.<br />
<p></p><br />
{{#widget:Widget:Google Calendar<br />
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ<br />
}}<br />
<br />
=Product Backlog=<br />
* Improve work prioritization, so the team is always working on the most important features.<br />
* Simplify continual planning, so the plan matches reality.<br />
* Improve visibility so that the stakeholders make the best decisions about the direction of the product (call out risks early, relative priorities, trade-offs)<br />
<p> </p><br />
<p> </p><br />
<br />
==Triage Guidelines==<br />
===Bugzilla===<br />
<p> </p><br />
* '''Priorities''' follow this Standard:<br />
** Priority 1 - Blocker, must-fix before shipping or a priority feature we are including in this release.<br />
** Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping. For Features we'd really like it, but wouldn't hold shipping for it.<br />
** Priority 3 - Average Bug. definitely a problem, but doesn't stop someone from using the product. <br />
** Priority 4 - Minor or polish bugs that are real issues (especially in aggregate) and annoying.<br />
** Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability.<br />
<p> </p><br />
*'''Importance''' will be left at "normal" unless a bug is on the line of being one Priority higher and lower - and then will be marked "Major" or "Minor" accordingly.<br />
<p> </p><br />
*Optional '''Whiteboard tag'''<br />
**Adding a '''short descriptive area tag''' in the whiteboard when possible, to visually group bugs quickly in a list. ex: "[tabs] triaged"<br />
*Triaged bug mark-up<br />
**Adding '''triaged''' tag to the end of the Whiteboard for bugs that have been assigned a priority, so we know what has been triaged. No [] needed<br />
<br />
===Github===<br />
<p> </p><br />
*Added labels to [http://addons.readthedocs.org/en/latest/repositories.html add-ons repositories] for:<br />
**'''P1''' - either bug we would block next targeted featured for or a time-critical major bug<br />
**'''P2''' - either feature we'd really like, but wouldn't delay releasing the P1's for (good to look at after passing milestone). or Major impact bug, considering severity × probability. Not a blocker for shipping.<br />
**'''backlog''' - We know it's not in our immediate plans or roadmaps - but it's been noted<br />
*Added column to waffle boards for "triaged"<br />
**Move bugs from '''untriaged''' to '''triaged''' column after they've been looked at and Prioritized.<br />
<br />
==Common Queries==<br />
===[https://wiki.mozilla.org/WebExtensions#Useful_queries Webextensions]===<br />
<br />
===AMO===<br />
*Experimenting with [https://wiki.mozilla.org/Add-ons#Github new triage process], will change as needed <br />
*[https://waffle.io/mozilla/addons?source=mozilla%2Faddons-server,mozilla%2Faddons.mozilla.org-mod,mozilla%2Famo-validator,mozilla%2Faddons-frontend,mozilla%2Faddons-linter,mozilla%2Faddons,mozilla%2Fdispensary Triage Query]<br />
<br />
===Add-ons Manager===<br />
Handles installing, running and updating add-ons within Firefox. Also has pages like about:addons. In bugzilla - product: Toolkit, component<br />
*[http://mzl.la/1T6QAeZ Untriaged bugs within past 120 days]<br />
**follow [https://wiki.mozilla.org/Add-ons#Bugzilla bugzilla triage guidelines], process always open to change<br />
*[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=12941866&o1=substring&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=triaged&component=Add-ons%20Manager&product=Toolkit Triaged bugs] have '''triaged''' tag added to end of '''whiteboard'''</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons&diff=1164379Add-ons2017-03-02T22:45:17Z<p>Jorge.villalobos: Removed eviljeff from ACE Team</p>
<hr />
<div>=What=<br />
'''Mission''': Add-ons are a safe, simple, and powerful way for people to personalize their web experience.<br />
<p></p><br />
This is the home page for Add-ons at Mozilla.<br />
<p></p><br />
Including but not limited to:<br />
* Firefox Add-ons<br />
* Firefox for Android Add-ons<br />
* [https://developer.mozilla.org/Firefox_OS/Add-ons Firefox OS Add-ons]<br />
* [https://addons.mozilla.org/firefox/ addons.mozilla.org (AMO)]<br />
*[[Add-ons/Projects|See projects page]]<br />
* [[Add-ons/Extension_Signing|Extension Signing]]<br />
* [[WebExtensions|Web Extensions]]<br />
<br />
Looking for [[Add-ons/2017|2017 plans]]?<br />
<br />
=Who=<br />
<br />
*Note:* This is a list of people employed by Mozilla. But we are way more than that, please add yourselves in if you want.<br />
<br />
=== Engineering ===<br />
<br />
Engineering Managers:<br />
<br />
* Andy McKay ([https://phonebook.mozilla.org/#search/Andy%20McKay internal], [http://mckay.pub blog], [https://mozillians.org/en-US/u/andym/ Mozillian profile])<br />
* Stuart Colville ([https://phonebook.mozilla.org/#search/Stuart%20Colville internal], [https://muffinresearch.co.uk/ blog], [https://mozillians.org/en-US/u/scolville/ Mozillian Profile])<br />
<br />
Engineers:<br />
<br />
* Kumar McMillan ([https://phonebook.mozilla.org/#search/Kumar%20McMillan internal], [http://farmdev.com/ blog], [https://mozillians.org/en-US/u/scolville/ Mozillian Profile])<br />
* Mark Striemer ([https://phonebook.mozilla.org/#search/Mark%20Striemer internal])<br />
* Kris Maglione ([https://phonebook.mozilla.org/#search/kris%20m internal], [http://blog.5digits.org/ blog],[https://mozillians.org/en-US/u/John-Galt/ Mozillian Profile])<br />
* tofumatt (Matthew Riley MacPherson) ([https://phonebook.mozilla.org/#search/tofumatt internal])<br />
* Christopher Grebs ([https://phonebook.mozilla.org/#search/Christopher%20Grebs internal])<br />
* Luca Greco ([https://mozillians.org/en-US/u/luca/ Mozillian Profile])<br />
* Andrew Swan ([https://phonebook.mozilla.org/#search/Andrew%20Swan internal])<br />
* Matthew Wein ([https://phonebook.mozilla.org/#search/Matthew%20Wein internal])<br />
* Bob Silverberg ([https://phonebook.mozilla.org/#search/Bob%20Silverberg internal])<br />
* Mathieu Pillard ([https://phonebook.mozilla.org/#search/Mathieu%20Pillard internal]])<br />
* Shane Caraveo ([https://phonebook.mozilla.org/#search/Shane%20Caraveo internal], [https://mozillians.org/en-US/u/scaraveo/ Mozillian Profile])<br />
* Andrew Williamson ([https://phonebook.mozilla.org/?search/eviljeff internal], [https://mozillians.org/en-US/u/eviljeff/ Mozillian Profile]<br />
<br />
What [http://www.timeanddate.com/worldclock/meetingtime.html?p1=256&p2=136&p3=64&p4=195&p5=265&p6=202 time zones are we in]?<br />
<br />
Looking for the [http://addons.readthedocs.org/en/latest/server/push-duty.html push duty roster] maybe?<br />
<br />
=== User Experience ===<br />
* Markus Jaritz, UX Designer ([https://phonebook.mozilla.org/tree.php#search/markus@mozilla.com internal], [https://mozillians.org/en-US/u/mjaritz/ Mozillians])<br />
* Blake Winton, UX Engineer ([https://phonebook.mozilla.org/tree.php#search/bwinton@mozilla.com internal], [https://mozillians.org/en-US/u/bwinton/ Mozillians])<br />
* Philip Walmsley, Senior Visual Designer ([https://phonebook.mozilla.org/search.php?format=vcard&query=pwalmsley@mozilla.com internal])<br />
* ''more to come as we work on things other than the API...''<br />
<br />
=== Program and Product Management ===<br />
* Kev Needham, Product Manager ([https://phonebook.mozilla.org/tree.php#search/kneedham@mozilla.com internal], [http://kev.deadsquid.com/ blog], [https://mozillians.org/en-US/u/kev/ mozillians profile])<br />
* Shell Escalante, Program Manager ([https://phonebook.mozilla.org/#search/shell@mozilla.com internal], IRC:shell)<br />
<br />
=== [[Add-ons/ACE|Add-on Community Experience (ACE team)]] ===<br />
Developer Experience:<br />
* Jorge Villalobos, ([https://phonebook.mozilla.org/#search/jorge internal], [http://xulforge.com/blog/ blog], [https://mozillians.org/en-US/u/jorgev/ mozillians profile])<br />
* Andreas Wagner, ([https://phonebook.mozilla.org/#search/andreas%20wagner internal], [https://mozillians.org/en-US/u/TheOne/ mozillians profile])<br />
* Philipp Kewisch, ([https://phonebook.mozilla.org/#search/kewisch internal], [https://mozillians.org/en-US/u/kewisch/ mozillians profile])<br />
<br />
Community & Editorial:<br />
* Amy Tsay, ([https://phonebook.mozilla.org/#search/tsay internal], [https://mozillians.org/en-US/u/amyt/ mozillians profile])<br />
* Scott DeVaney ([https://phonebook.mozilla.org/#search/devaney internal], [https://mozillians.org/en-US/u/sdevaney/ mozillians profile])<br />
* Caitlin Neiman ([https://phonebook.mozilla.org/#search/neiman internal], [https://mozillians.org/en-US/u/cneiman/ mozillians profile])<br />
<br />
=== QA ===<br />
* Krupa Raj, ([https://phonebook.mozilla.org/#search/krupa internal], [https://mozillians.org/en-US/u/kruparaj/ mozillians profile])<br />
* Victor Carciu<br />
* Madalin Cotetiu<br />
* Valentina Peleskei<br />
<br />
=Getting in touch=<br />
<br />
* Mailing list: https://mail.mozilla.org/listinfo/dev-addons<br />
<br />
* [[IRC|IRC]]:<br />
** #teamaddons: team chat <br />
** #addons: support for extensions, themes, plugins and addons.mozilla.org<br />
** #amo: addons.mozilla.org bugs and development<br />
** #amo-editors: add-on reviews and policy<br />
** #extdev: extension development<br />
** #themedev: theme development<br />
** #webextensions: web extensions<br />
<br />
* Blog: https://blog.mozilla.org/addons/<br />
* Forum: https://discourse.mozilla-community.org/c/add-ons<br />
<br />
== Meetings ==<br />
<br />
Please see the add-ons Calendar or mailing lists:<br />
<br />
* Mailing Lists: [https://mail.mozilla.org/listinfo/dev-addons dev-addons]<br />
* Calendar: [https://www.google.com/calendar/embed?src=mozilla.com_lr5jsh38i6dmr72uu4d1nv7dcc%40group.calendar.google.com Preview], [https://www.google.com/calendar/ical/mozilla.com_lr5jsh38i6dmr72uu4d1nv7dcc%40group.calendar.google.com/public/basic.ics iCal import]<br />
<br />
Most meetings are in the Add-ons Vidyo room. To access remotely:<br />
<br />
* Using Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=gBI6Q6943nQv <br />
* To join from a telephone: US Toll Free +1 800 707 2533, pin 369, conf 98839<br />
<br />
Minutes:<br />
<br />
* Most meetings [https://docs.google.com/document/d/1oNq9vZCNgMUnjJ0prfeWzudibtMwkCoNfVxN3a7j90A/edit add their minutes here].<br />
<br />
===Contribute to Add-ons===<br />
Support user freedom by helping to keep Firefox the most customizable browser available.<br />
*See how you can help: https://wiki.mozilla.org/Add-ons/Contribute<br />
*Subscribe to the [https://discourse.mozilla-community.org/c/add-ons/contribute Add-ons Contribution] forum to be kept in the loop about contribution opportunities and events. Click on the menu at the top-right corner of the page and select "Watching".<br />
<br />
=Status & Roadmap=<br />
[https://wiki.mozilla.org/Firefox/AddOns/Status/current Current Status] on 5 focus areas<br />
<p></p><br />
[https://docs.google.com/document/d/17o2l7VV9OBwXxGeEUQf0-4dZhlbbrJPkGbIXA-ht2Tg/edit# Weekly detailed notes] of current event discussions in Product, Engineering, Community, & UX<br />
<p></p><br />
[https://mozilla.aha.io/published/0d49e74c6853d3d721010bd9d4f67f34?page=1 Roadmap]: to the best of our ability, always in progress, so expect changes<br />
<br />
== Multi-process Firefox ==<br />
<br />
For information on the roll out of multi-process Firefox and add-ons, please see [https://wiki.mozilla.org/Electrolysis#Add-ons_Schedule the schedule]<br />
<br />
===Communications Calendar===<br />
Planning to communicate changes or coming features. One example is blogs, audiences, channels, and who will be writing/reviewing.<br />
<p></p><br />
{{#widget:Widget:Google Calendar<br />
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ<br />
}}<br />
<br />
=Product Backlog=<br />
* Improve work prioritization, so the team is always working on the most important features.<br />
* Simplify continual planning, so the plan matches reality.<br />
* Improve visibility so that the stakeholders make the best decisions about the direction of the product (call out risks early, relative priorities, trade-offs)<br />
<p> </p><br />
<p> </p><br />
<br />
==Triage Guidelines==<br />
===Bugzilla===<br />
<p> </p><br />
* '''Priorities''' follow this Standard:<br />
** Priority 1 - Blocker, must-fix before shipping or a priority feature we are including in this release.<br />
** Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping. For Features we'd really like it, but wouldn't hold shipping for it.<br />
** Priority 3 - Average Bug. definitely a problem, but doesn't stop someone from using the product. <br />
** Priority 4 - Minor or polish bugs that are real issues (especially in aggregate) and annoying.<br />
** Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability.<br />
<p> </p><br />
*'''Importance''' will be left at "normal" unless a bug is on the line of being one Priority higher and lower - and then will be marked "Major" or "Minor" accordingly.<br />
<p> </p><br />
*Optional '''Whiteboard tag'''<br />
**Adding a '''short descriptive area tag''' in the whiteboard when possible, to visually group bugs quickly in a list. ex: "[tabs] triaged"<br />
*Triaged bug mark-up<br />
**Adding '''triaged''' tag to the end of the Whiteboard for bugs that have been assigned a priority, so we know what has been triaged. No [] needed<br />
<br />
===Github===<br />
<p> </p><br />
*Added labels to [http://addons.readthedocs.org/en/latest/repositories.html add-ons repositories] for:<br />
**'''P1''' - either bug we would block next targeted featured for or a time-critical major bug<br />
**'''P2''' - either feature we'd really like, but wouldn't delay releasing the P1's for (good to look at after passing milestone). or Major impact bug, considering severity × probability. Not a blocker for shipping.<br />
**'''backlog''' - We know it's not in our immediate plans or roadmaps - but it's been noted<br />
*Added column to waffle boards for "triaged"<br />
**Move bugs from '''untriaged''' to '''triaged''' column after they've been looked at and Prioritized.<br />
<br />
==Common Queries==<br />
===[https://wiki.mozilla.org/WebExtensions#Useful_queries Webextensions]===<br />
<br />
===AMO===<br />
*Experimenting with [https://wiki.mozilla.org/Add-ons#Github new triage process], will change as needed <br />
*[https://waffle.io/mozilla/addons?source=mozilla%2Faddons-server,mozilla%2Faddons.mozilla.org-mod,mozilla%2Famo-validator,mozilla%2Faddons-frontend,mozilla%2Faddons-linter,mozilla%2Faddons,mozilla%2Fdispensary Triage Query]<br />
<br />
===Add-ons Manager===<br />
Handles installing, running and updating add-ons within Firefox. Also has pages like about:addons. In bugzilla - product: Toolkit, component<br />
*[http://mzl.la/1T6QAeZ Untriaged bugs within past 120 days]<br />
**follow [https://wiki.mozilla.org/Add-ons#Bugzilla bugzilla triage guidelines], process always open to change<br />
*[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=12941866&o1=substring&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=triaged&component=Add-ons%20Manager&product=Toolkit Triaged bugs] have '''triaged''' tag added to end of '''whiteboard'''</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Blocklisting/Admin&diff=1163482Blocklisting/Admin2017-02-21T20:25:59Z<p>Jorge.villalobos: Fixed typo</p>
<hr />
<div>Blocklist entries are added through the Kinto Web Administration tool. Only authorized members of the Add-ons Team can manipulate the blocklist.<br />
<br />
# Login via the [https://settings-writer.prod.mozaws.net/v1/admin/ Kinto admin page] (VPN connection is required)<br />
# '''Authentication method''': Basic Auth<br />
# '''Username''': jdoe@mozilla.com. This is your full LDAP email address.<br />
# '''Password''': your_ldap_password<br />
<br />
All blocks are first created in the '''staging''' bucket, are later moved to the '''blocklist-preview''' bucket for testing and review, and then deployed to the final '''blocklists''' bucket.<br />
<br />
== Extension blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''addons'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled''' checkbox checked.<br />
#* You'll generally want to enter the '''Add-on ID''', '''Version Range''' (0 to * to block all versions), and '''Severity''' of the block.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The '''Target Application''' is only necessary for blocks that only target specific applications, which should also be very rare.<br />
#* The '''Preferences''' fields are used in case the add-on changed important Firefox preferences that need to be reset.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. If the extension being blocked is malware, add " (malware)" at the end of the name. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/addons/records public JSON endpoint].<br />
===Testing===<br />
To test a staged block:<br />
# You must first enable chrome debugging: in <code>about:config</code>, set <code>devtools.chrome.enabled</code> to <code>true</code>.<br />
# Go to <code>about:config</code>, find the <code>extensions.blocklist.url</code> pref and change its value to https://firefox.settings.services.mozilla.com/v1/preview/3/%APP_ID%/%APP_VERSION%/%PRODUCT%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/%PING_COUNT%/%TOTAL_PING_COUNT%/%DAYS_SINCE_LAST_PING%/<br />
# Open Browser Console (Tools > Web Developer > Browser Console)<br />
#Paste and run this snippet:<br />
Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsITimerCallback).notify(null);<br />
<br />
====JSON Example====<br />
<br />
<pre><br />
{<br />
"guid":"{de71f09a-3342-48c5-95c1-4b0f17567554}",<br />
"blockID":"i1493",<br />
"enabled":true,<br />
"last_modified":1484867614757,<br />
"details":{<br />
"who":"All users who have this add-on installed.",<br />
"created":"2017-01-12T22:17:59Z",<br />
"bug":"https://bugzilla.mozilla.org/show_bug.cgi?id=1329654",<br />
"name":"Search for Firefox Convertor (malware)",<br />
"why":"This is a malicious add-on that is installed using a fake name. It changes search and homepage settings."<br />
},<br />
"versionRange":[<br />
{<br />
"targetApplication":[<br />
<br />
],<br />
"minVersion":"0",<br />
"maxVersion":"1.3.9",<br />
"severity":3<br />
}<br />
],<br />
"prefs":[<br />
<br />
],<br />
"id":"d6ec9f54-9945-088e-ba68-40117eaba24e",<br />
"schema":1484335370642<br />
}<br />
</pre><br />
===Deploying===<br />
# Click on '''staging bucket''' :: '''addons'''<br />
# The staged blocks should be shown with an option to Approve.<br />
# Approve :)<br />
<br />
== Plugin blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''plugins'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled checkbox''' checked.<br />
#* Plugins are usually identified by their '''Filename'''. '''Name''' and '''Description''' regular expression matches are used when the '''Filename''' doesn't work. [http://mzl.la/SemegK Regexp Pal] is a good tool for testing regular expression blocks.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these]. It's generally only needed for Linux blocks, since Linux and Android distributions use the same filename and plugins are never blocked on Android.<br />
#* The '''Version Range''' should always be set (0 to * to block all versions).<br />
#* The '''Severity''' should always be set to 0 (click to activate).<br />
#* The '''Vulnerability status''' should be set depending on whether the latest version is being blocked or not.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The '''Target Application''' is only necessary for blocks that only target specific applications, which should be very rare.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/plugins/records public JSON endpoint].<br />
<br />
===Testing===<br />
<br />
To test a staged block:<br />
# You must first enable chrome debugging: in <code>about:config</code>, set <code>devtools.chrome.enabled</code> to <code>true</code>.<br />
# Go to <code>about:config</code>, find the <code>extensions.blocklist.url</code> pref and change its value to https://firefox.settings.services.mozilla.com/v1/preview/3/%APP_ID%/%APP_VERSION%/%PRODUCT%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/%PING_COUNT%/%TOTAL_PING_COUNT%/%DAYS_SINCE_LAST_PING%/<br />
# Open Browser Console (Tools > Web Developer > Browser Console)<br />
#Paste and run this snippet:<br />
Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsITimerCallback).notify(null);<br />
<br />
===Deploying===<br />
# Click on '''staging bucket''' :: '''plugins'''<br />
# The staged blocks should be shown with an option to Approve.<br />
# Approve :)<br />
<br />
== Graphics card blocks ==<br />
# Go to the [https://addons.mozilla.org/admin/models/blocklist/blocklistdetail/ blocklist detail page] and click on Add blocklist detail.<br />
# Enter a name and descriptions for the block. These detail pages aren't exposed to users, so these descriptions aren't very important.<br />
# Set the Bug field to the blocklist bug.<br />
# In the Blocklist Gfx #1 section, set the data that should have been detailed on the blocklist bug.<br />
<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''gfx'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields, which should be detailed in the bug report. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled checkbox''' checked.<br />
#* The '''name''' and '''bug''' fields are used for internal record keeping and won't be shown to users. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/plugins/records public JSON endpoint].<br />
===Testing===<br />
To test a staged block:<br />
# You must first enable chrome debugging: in <code>about:config</code>, set <code>devtools.chrome.enabled</code> to <code>true</code>.<br />
# Go to <code>about:config</code>, find the <code>extensions.blocklist.url</code> pref and change its value to https://firefox.settings.services.mozilla.com/v1/preview/3/%APP_ID%/%APP_VERSION%/%PRODUCT%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/%PING_COUNT%/%TOTAL_PING_COUNT%/%DAYS_SINCE_LAST_PING%/<br />
# Open Browser Console (Tools > Web Developer > Browser Console)<br />
#Paste and run this snippet:<br />
Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsITimerCallback).notify(null);<br />
<br />
===Deploying===<br />
# Click on '''staging bucket''' :: '''gfx'''<br />
# The staged blocks should be shown with an option to Approve.<br />
# Approve :)</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Blocklisting/Admin&diff=1163332Blocklisting/Admin2017-02-20T18:58:13Z<p>Jorge.villalobos: Updating testing info</p>
<hr />
<div>Blocklist entries are added through the Kinto Web Administration tool. Only authorized members of the Add-ons Team can manipulate the blocklist.<br />
<br />
# Login via the [https://settings-writer.prod.mozaws.net/v1/admin/ Kinto admin page] (VPN connection is required)<br />
# '''Authentication method''': Basic Auth<br />
# '''Username''': jdoe@mozilla.com. This is your full LDAP email address.<br />
# '''Password''': your_ldap_password<br />
<br />
All blocks are first created in the '''staging''' bucket, are later moved to the '''blocklist-preview''' bucket for testing and review, and then deployed to the final '''blocklists''' bucket.<br />
<br />
== Extension blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''addons'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled''' checkbox checked.<br />
#* You'll generally want to enter the '''Add-on ID''', '''Version Range''' (0 to * to block all versions), and '''Severity''' of the block.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The '''Target Application''' is only necessary for blocks that only target specific applications, which should also be very rare.<br />
#* The '''Preferences''' fields are used in case the add-on changed important Firefox preferences that need to be reset.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. If the extension being blocked is malware, add " (malware)" at the end of the name. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/addons/records public JSON endpoint].<br />
===Testing===<br />
To test a staged block:<br />
# You must first enable chrome debugging: in <code>about:config</code>, set <code>devtools.chrome.enabled</code> to <code>true</code>.<br />
# Go to <code>about:config</code>, find the <code>extensions.blocklist.url</code> pref and change its value to https://firefox.settings.services.mozilla.com/v1/preview/3/%APP_ID%/%APP_VERSION%/%PRODUCT%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/%PING_COUNT%/%TOTAL_PING_COUNT%/%DAYS_SINCE_LAST_PING%/<br />
# Open Browser Console (Tools > Web Developer > Browser Console)<br />
#Paste and run this snippet:<br />
Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsITimerCallback).notify(null);</code><br />
<br />
====JSON Example====<br />
<br />
<pre><br />
{<br />
"guid":"{de71f09a-3342-48c5-95c1-4b0f17567554}",<br />
"blockID":"i1493",<br />
"enabled":true,<br />
"last_modified":1484867614757,<br />
"details":{<br />
"who":"All users who have this add-on installed.",<br />
"created":"2017-01-12T22:17:59Z",<br />
"bug":"https://bugzilla.mozilla.org/show_bug.cgi?id=1329654",<br />
"name":"Search for Firefox Convertor (malware)",<br />
"why":"This is a malicious add-on that is installed using a fake name. It changes search and homepage settings."<br />
},<br />
"versionRange":[<br />
{<br />
"targetApplication":[<br />
<br />
],<br />
"minVersion":"0",<br />
"maxVersion":"1.3.9",<br />
"severity":3<br />
}<br />
],<br />
"prefs":[<br />
<br />
],<br />
"id":"d6ec9f54-9945-088e-ba68-40117eaba24e",<br />
"schema":1484335370642<br />
}<br />
</pre><br />
===Deploying===<br />
# Click on '''staging bucket''' :: '''addons'''<br />
# The staged blocks should be shown with an option to Approve.<br />
# Approve :)<br />
<br />
== Plugin blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''plugins'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled checkbox''' checked.<br />
#* Plugins are usually identified by their '''Filename'''. '''Name''' and '''Description''' regular expression matches are used when the '''Filename''' doesn't work. [http://mzl.la/SemegK Regexp Pal] is a good tool for testing regular expression blocks.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these]. It's generally only needed for Linux blocks, since Linux and Android distributions use the same filename and plugins are never blocked on Android.<br />
#* The '''Version Range''' should always be set (0 to * to block all versions).<br />
#* The '''Severity''' should always be set to 0 (click to activate).<br />
#* The '''Vulnerability status''' should be set depending on whether the latest version is being blocked or not.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The '''Target Application''' is only necessary for blocks that only target specific applications, which should be very rare.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/plugins/records public JSON endpoint].<br />
<br />
===Testing===<br />
<br />
To test a staged block:<br />
# You must first enable chrome debugging: in <code>about:config</code>, set <code>devtools.chrome.enabled</code> to <code>true</code>.<br />
# Go to <code>about:config</code>, find the <code>extensions.blocklist.url</code> pref and change its value to https://firefox.settings.services.mozilla.com/v1/preview/3/%APP_ID%/%APP_VERSION%/%PRODUCT%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/%PING_COUNT%/%TOTAL_PING_COUNT%/%DAYS_SINCE_LAST_PING%/<br />
# Open Browser Console (Tools > Web Developer > Browser Console)<br />
#Paste and run this snippet:<br />
Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsITimerCallback).notify(null);</code><br />
<br />
===Deploying===<br />
# Click on '''staging bucket''' :: '''plugins'''<br />
# The staged blocks should be shown with an option to Approve.<br />
# Approve :)<br />
<br />
== Graphics card blocks ==<br />
# Go to the [https://addons.mozilla.org/admin/models/blocklist/blocklistdetail/ blocklist detail page] and click on Add blocklist detail.<br />
# Enter a name and descriptions for the block. These detail pages aren't exposed to users, so these descriptions aren't very important.<br />
# Set the Bug field to the blocklist bug.<br />
# In the Blocklist Gfx #1 section, set the data that should have been detailed on the blocklist bug.<br />
<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''gfx'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields, which should be detailed in the bug report. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled checkbox''' checked.<br />
#* The '''name''' and '''bug''' fields are used for internal record keeping and won't be shown to users. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/plugins/records public JSON endpoint].<br />
===Testing===<br />
To test a staged block:<br />
# You must first enable chrome debugging: in <code>about:config</code>, set <code>devtools.chrome.enabled</code> to <code>true</code>.<br />
# Go to <code>about:config</code>, find the <code>extensions.blocklist.url</code> pref and change its value to https://firefox.settings.services.mozilla.com/v1/preview/3/%APP_ID%/%APP_VERSION%/%PRODUCT%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/%PING_COUNT%/%TOTAL_PING_COUNT%/%DAYS_SINCE_LAST_PING%/<br />
# Open Browser Console (Tools > Web Developer > Browser Console)<br />
#Paste and run this snippet:<br />
Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsITimerCallback).notify(null);</code><br />
<br />
===Deploying===<br />
# Click on '''staging bucket''' :: '''gfx'''<br />
# The staged blocks should be shown with an option to Approve.<br />
# Approve :)</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Blocklisting/Admin&diff=1163067Blocklisting/Admin2017-02-15T23:55:49Z<p>Jorge.villalobos: Adding testing process</p>
<hr />
<div>Blocklist entries are added through the Kinto Web Administration tool. Only authorized members of the Add-ons Team can manipulate the blocklist.<br />
<br />
# Login via the [https://settings-writer.prod.mozaws.net/v1/admin/ Kinto admin page] (VPN connection is required)<br />
# '''Authentication method''': Basic Auth<br />
# '''Username''': jdoe@mozilla.com. This is your full LDAP email address.<br />
# '''Password''': your_ldap_password<br />
<br />
All blocks are first created in the '''staging''' bucket, are later moved to the '''blocklist-preview''' bucket for testing and review, and then deployed to the final '''blocklists''' bucket.<br />
<br />
== Extension blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''addons'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled''' checkbox checked.<br />
#* You'll generally want to enter the '''Add-on ID''', '''Version Range''' (0 to * to block all versions), and '''Severity''' of the block.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The '''Target Application''' is only necessary for blocks that only target specific applications, which should also be very rare.<br />
#* The '''Preferences''' fields are used in case the add-on changed important Firefox preferences that need to be reset.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. If the extension being blocked is malware, add " (malware)" at the end of the name. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/addons/records public JSON endpoint].<br />
===Testing===<br />
To test a staged block:<br />
# You must first enable chrome debugging: in <code>about:config</code>, set <code>devtools.chrome.enabled</code> to <code>true</code>.<br />
# Go to <code>about:config</code>, find the <code>services.blocklist.bucket</code> pref and change its value from <code>blocklists</code> to <code>blocklists-preview</code>.<br />
# Open Browser Console (Tools > Web Developer > Browser Console)<br />
#Paste and run this snippet:<br />
Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsITimerCallback).notify(null);</code><br />
<br />
====JSON Example====<br />
<br />
<pre><br />
{<br />
"guid":"{de71f09a-3342-48c5-95c1-4b0f17567554}",<br />
"blockID":"i1493",<br />
"enabled":true,<br />
"last_modified":1484867614757,<br />
"details":{<br />
"who":"All users who have this add-on installed.",<br />
"created":"2017-01-12T22:17:59Z",<br />
"bug":"https://bugzilla.mozilla.org/show_bug.cgi?id=1329654",<br />
"name":"Search for Firefox Convertor (malware)",<br />
"why":"This is a malicious add-on that is installed using a fake name. It changes search and homepage settings."<br />
},<br />
"versionRange":[<br />
{<br />
"targetApplication":[<br />
<br />
],<br />
"minVersion":"0",<br />
"maxVersion":"1.3.9",<br />
"severity":3<br />
}<br />
],<br />
"prefs":[<br />
<br />
],<br />
"id":"d6ec9f54-9945-088e-ba68-40117eaba24e",<br />
"schema":1484335370642<br />
}<br />
</pre><br />
===Deploying===<br />
# Click on '''staging bucket''' :: '''addons'''<br />
# The staged blocks should be shown with an option to Approve.<br />
# Approve :)<br />
<br />
== Plugin blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''plugins'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled checkbox''' checked.<br />
#* Plugins are usually identified by their '''Filename'''. '''Name''' and '''Description''' regular expression matches are used when the '''Filename''' doesn't work. [http://mzl.la/SemegK Regexp Pal] is a good tool for testing regular expression blocks.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these]. It's generally only needed for Linux blocks, since Linux and Android distributions use the same filename and plugins are never blocked on Android.<br />
#* The '''Version Range''' should always be set (0 to * to block all versions).<br />
#* The '''Severity''' should always be set to 0 (click to activate).<br />
#* The '''Vulnerability status''' should be set depending on whether the latest version is being blocked or not.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The '''Target Application''' is only necessary for blocks that only target specific applications, which should be very rare.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/plugins/records public JSON endpoint].<br />
===Testing===<br />
To test a staged block:<br />
# You must first enable chrome debugging: in <code>about:config</code>, set <code>devtools.chrome.enabled</code> to <code>true</code>.<br />
# Go to <code>about:config</code>, find the <code>services.blocklist.bucket</code> pref and change its value from <code>blocklists</code> to <code>blocklists-preview</code>.<br />
# Open Browser Console (Tools > Web Developer > Browser Console)<br />
#Paste and run this snippet:<br />
Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsITimerCallback).notify(null);</code><br />
<br />
===Deploying===<br />
# Click on '''staging bucket''' :: '''plugins'''<br />
# The staged blocks should be shown with an option to Approve.<br />
# Approve :)<br />
<br />
== Graphics card blocks ==<br />
# Go to the [https://addons.mozilla.org/admin/models/blocklist/blocklistdetail/ blocklist detail page] and click on Add blocklist detail.<br />
# Enter a name and descriptions for the block. These detail pages aren't exposed to users, so these descriptions aren't very important.<br />
# Set the Bug field to the blocklist bug.<br />
# In the Blocklist Gfx #1 section, set the data that should have been detailed on the blocklist bug.<br />
<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''gfx'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields, which should be detailed in the bug report. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled checkbox''' checked.<br />
#* The '''name''' and '''bug''' fields are used for internal record keeping and won't be shown to users. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/plugins/records public JSON endpoint].<br />
===Testing===<br />
To test a staged block:<br />
# You must first enable chrome debugging: in <code>about:config</code>, set <code>devtools.chrome.enabled</code> to <code>true</code>.<br />
# Go to <code>about:config</code>, find the <code>services.blocklist.bucket</code> pref and change its value from <code>blocklists</code> to <code>blocklists-preview</code>.<br />
# Open Browser Console (Tools > Web Developer > Browser Console)<br />
#Paste and run this snippet:<br />
Components.classes["@mozilla.org/extensions/blocklist;1"].getService(Components.interfaces.nsITimerCallback).notify(null);</code><br />
<br />
===Deploying===<br />
# Click on '''staging bucket''' :: '''gfx'''<br />
# The staged blocks should be shown with an option to Approve.<br />
# Approve :)</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Contribute/Triage&diff=1162151Add-ons/Contribute/Triage2017-02-07T18:21:57Z<p>Jorge.villalobos: Generalizing GFB queries to cover inconsistent good first bug tags</p>
<hr />
<div>= Purpose of Meeting =<br />
A bi-weekly triage session to accomplish these community goals:<br />
* '''WebExtensions APIs''': <br />
** Transparency: Decide whether APIs tagged "design-decision-needed" are "design-decision-approved" or "wontfix" to ensure transparency for the direction of WebExtensions. <br />
** Participation: Give guidance on and assign advisors to APIs marked "design-decision-approved" to make it easier for contributors to get involved.<br />
* '''Good First Bugs''': Ensure add-on bugs marked "Good First Bug" are fresh and updated for new contributors. If you are a new contributor who wants to write code for add-on related projects, please [https://wiki.mozilla.org/Add-ons/Contribute/Code start here].<br />
<br />
=Next Meeting=<br />
Next meeting is [https://docs.google.com/document/d/1X5OUNgpUcMLkHrOPbg-OLWSA2hzoRykRZd2gyTJ9vgU/edit# Feb 7].<br />
<br />
=Details & How to Join=<br />
* Time: Every other Tuesday at:<br />
**[http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 10:00am Pacific] - Good First Bugs<br />
**[http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 10:30am Pacific] - WebExtensions<br />
* Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU<br />
*IRC: [https://wiki.mozilla.org/IRC irc.mozilla.org], #Addons channel<br />
<br />
=WebExtensions APIs Triage=<br />
==Triage Guidelines==<br />
Bugs marked "design-decision-needed" should be:<br />
*Tagged with "design-decision-approved" or "wontfix" (including reason)<br />
<br />
Bugs marked "design-decision-approved" should have:<br />
*Clear description of the API and suggested implementation if possible<br />
*Priority & impact<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code#Develop_Web_Extensions_APIs onboarding process]<br />
*Advisor<br />
<br />
==Bug Queries==<br />
====="design-decision-needed"=====<br />
These are determined from the Monday WebExtensions triage. They are APIs we [https://mzl.la/2edmiid need more discussion] on.<br />
<br />
====="design-decision-approved"=====<br />
These are APIs we would [https://mzl.la/2dVs5Ys like to have]. They should meet the triage criteria listed above.<br />
<br />
=Good First Bugs Triage=<br />
==Triage Guidelines==<br />
All "Good First Bugs" should have:<br />
*Clear description of the issue<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code onboarding process]<br />
*Mentor<br />
<br />
==Bug Queries==<br />
=====addons-server "Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=good%20first%20bug This is the query] contributors see. We should spot-check them to ensure they are properly triaged.<br />
<br />
=====addons-server "Maybe Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=maybe%20good%20first%20bug These are tagged "Maybe Good First Bugs"]. We triage these and change the tag to "Good First Bugs" if determined to be good for new contributors.<br />
<br />
=====WebExtensions Bugs on Bugzilla=====<br />
*These are WebExtensions bugs that [https://mzl.la/2lmxzwc don't have a mentor]<br />
*These are WebExtensions bugs that [https://mzl.la/2kocVNC have an assignee but haven't been commented on for 3 weeks]<br />
<br />
=====Add-ons Manager Bugs on Bugzilla=====<br />
*These are Add-ons Manager bugs that [https://mzl.la/2kP5Y8S don't have a mentor]<br />
*These are Add-ons Manager bugs that [https://mzl.la/2jZ24pP have an assignee but haven't been commented on for 3 weeks]<br />
<br />
= Archive =<br />
=====2017=====<br />
[https://docs.google.com/document/d/1add-6FL8mzksvzbyB83HUmEkVmKERd-nt740AYr-4PE/edit# Jan 24, 2017]<br /><br />
[https://docs.google.com/document/d/18K97o1juaHSeYEkes1iMz8AayjuVkUuIK844ErGaa-c/edit?usp=sharing Jan 10, 2017]<br />
<br />
=====2016=====<br />
[https://docs.google.com/document/d/1S1QrBK1hrulE7dlLiQzjMupHUUSwDYRYAOXiqtMHe-k/edit?usp=sharing Dec 13, 2016]<br /><br />
[https://docs.google.com/document/d/1IMBFXHNpg_A-15VdJM1Hh8DUUXF1xNFy87W1w8ZEOBk/edit#heading=h.du5ihvu5p6ro Nov 29, 2016]<br /><br />
[https://docs.google.com/document/d/1cMvAtlIZpykpxZ0bG2J2lh7Mx1WcVfLrHSDJZHFvexc/edit Nov 15, 2016]<br /><br />
[https://docs.google.com/document/d/1i5CT821JFutWL-f3AZ3VhlYIIzulnMttjNp1JsYba8M/edit# Nov 1, 2016]<br /><br />
[https://docs.google.com/document/d/1elytPf_HqAqqFC6EM0-hrJp7kWJA-LfKILXV1tzNLTU/edit Oct 18, 2016]<br /><br />
[https://docs.google.com/document/d/1BDIbINMGgjoWlZxHmw-MnLm3HEqB38oUNTJUPAippGo/edit Oct 4, 2016]<br /><br />
[https://docs.google.com/document/d/1gABxxstInPy5XMsmoYMhZBMsLGFWNsgWMhgjUlt7-o8/edit Sept 20, 2016]<br /><br />
[https://docs.google.com/document/d/14cqCfgbyGoBXe7ttho0L3mIe4FcSSlzHH3L4fBFnLzA/edit Sept 6, 2016]<br /><br />
[https://docs.google.com/document/d/1GDpdcO1EHefRL3B5p5g1emdp_lY-YFWjwXv8YG1EgWo/edit August 23, 2016]<br /><br />
[https://docs.google.com/document/d/1rZvIfFILAHozLGTrg5C7Q7lXyEZ2gfMDw7cVkEo34io/edit August 9, 2016]<br /><br />
[https://docs.google.com/document/d/1A5hKaon2Z3nSCQc9ToYTOjr2cIpmmeZmu9EnbhVjHd0/edit July 26, 2016]<br /><br />
[https://docs.google.com/document/d/18wCqoUzNYshOWDjuJjePFivb4T5nD0WlFE06NKn3YQ0/edit July 12, 2016]<br /><br />
[https://docs.google.com/document/d/1uBo-WVFP2v-dyeYyDtfPD9ipN8JeIw7sCag4CYonQqY/edit# June 28, 2016]<br /><br />
[https://docs.google.com/document/d/1lYqcEWaktMXPmAefRB9PW9iSBM95rlVKFOO-vFRewdE/edit May 31, 2016]<br /><br />
[https://docs.google.com/document/d/1Bq7gTVhsGfTW58A9MUurruu5jc2w5OHSeaoRbmWRQV4/edit May 17, 2016]<br /><br />
[https://docs.google.com/document/d/1EkZXtIx7TkQxnFn_2ei3SR7j9xeDVc1WSl3suY2n8RU/edit April 28, 2016]<br /><br />
[https://docs.google.com/document/d/13yPW-ojA_jzXUe7_fxDvYQavsr5yEHZzHXXCMcuZgCA/edit April 14, 2016]<br /><br />
[https://docs.google.com/document/d/1hSABd9dd8UktXGJuf0iXn_8Fpuz09VEqkxrxMY_AvZw/edit Mar 31, 2016]<br /><br />
[https://docs.google.com/document/d/1ss0i_zAZDytsyBnMGF1gdRI6LjRWqvQS9Q0ueKzQV1Q/edit Mar 3, 2016]<br /><br />
[https://docs.google.com/document/d/1GkHWjHRDcUd7WD2BFF-6zhdyce4lK8qMX23O6C0eRIA/edit Feb 18, 2016]<br /><br />
[https://docs.google.com/document/d/1cM2JIIgw1i7TJe3oOojCtJvEhJoBGdHgNvjS2hRfBcw/edit Feb 4, 2016]<br /> <br />
[https://docs.google.com/document/d/1OZVV_HVXWAY-1u-nPhb4MrXOsycVFbXkXGEhhTomoaM/edit Jan 21, 2016]<br /><br />
[https://docs.google.com/document/d/1GwqhWsSsBp5vfLW7-5Di8_CzIfepwK9YVZAnQuLxK9I/edit Jan 7, 2016]<br />
<br />
=====2015=====<br />
[https://docs.google.com/document/d/18Csoja50IhnjqraFzxEYyVIJp-j79GLO2gCrvTSYHUI/edit Nov. 19, 2015]<br /><br />
[https://docs.google.com/document/d/1gbhL0S4amQ447ddIX7mEZsSaGoiFt8fTw22FKe_GbIo/edit Oct. 29, 2015]<br /><br />
[https://docs.google.com/document/d/1EoLSXHKCqJzTatj6CLLpjomwXnN5zUOA897brO_1aJQ/edit Oct. 15, 2015]<br />
<br />
=====Aug - Oct 2015=====<br />
https://drive.google.com/drive/folders/0B2aDMRMZ7uzvYzA4Wm1VYVhvemM<br />
<br />
=Onboarding information template=<br />
If this is your first contribution, please refer to https://wiki.mozilla.org/Add-ons/Contribute/Code on how to get started.</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Blocklisting/Admin&diff=1161271Blocklisting/Admin2017-01-27T23:04:11Z<p>Jorge.villalobos: GFX blocks</p>
<hr />
<div>Blocklist entries are added through the Kinto Web Administration tool. Only authorized members of the Add-ons Team can manipulate the blocklist.<br />
<br />
# Login via the [https://settings-writer.prod.mozaws.net/v1/admin/ Kinto admin page] (VPN connection is required)<br />
# '''Authentication method''': Basic Auth<br />
# '''Username''': jdoe@mozilla.com. This is your full LDAP email address.<br />
# '''Password''': your_ldap_password<br />
<br />
All blocks are first created in the '''staging''' bucket, are later moved to the '''blocklist-preview''' bucket for testing and review, and then deployed to the final '''blocklists''' bucket.<br />
<br />
== Extension blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''addons'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled''' checkbox checked.<br />
#* You'll generally want to enter the '''Add-on ID''', '''Version Range''' (0 to * to block all versions), and '''Severity''' of the block.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The '''Target Application''' is only necessary for blocks that only target specific applications, which should also be very rare.<br />
#* The '''Preferences''' fields are used in case the add-on changed important Firefox preferences that need to be reset.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. If the extension being blocked is malware, add " (malware)" at the end of the name. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/addons/records public JSON endpoint].<br />
===Testing===<br />
<br />
====JSON Example====<br />
<br />
<pre><br />
{<br />
"guid":"{de71f09a-3342-48c5-95c1-4b0f17567554}",<br />
"blockID":"i1493",<br />
"enabled":true,<br />
"last_modified":1484867614757,<br />
"details":{<br />
"who":"All users who have this add-on installed.",<br />
"created":"2017-01-12T22:17:59Z",<br />
"bug":"https://bugzilla.mozilla.org/show_bug.cgi?id=1329654",<br />
"name":"Search for Firefox Convertor (malware)",<br />
"why":"This is a malicious add-on that is installed using a fake name. It changes search and homepage settings."<br />
},<br />
"versionRange":[<br />
{<br />
"targetApplication":[<br />
<br />
],<br />
"minVersion":"0",<br />
"maxVersion":"1.3.9",<br />
"severity":3<br />
}<br />
],<br />
"prefs":[<br />
<br />
],<br />
"id":"d6ec9f54-9945-088e-ba68-40117eaba24e",<br />
"schema":1484335370642<br />
}<br />
</pre><br />
===Deploying===<br />
# Click on '''blocklist-preview bucket''' :: '''addons'''<br />
<br />
== Plugin blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''plugins'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled checkbox''' checked.<br />
#* Plugins are usually identified by their '''Filename'''. '''Name''' and '''Description''' regular expression matches are used when the '''Filename''' doesn't work. [http://mzl.la/SemegK Regexp Pal] is a good tool for testing regular expression blocks.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these]. It's generally only needed for Linux blocks, since Linux and Android distributions use the same filename and plugins are never blocked on Android.<br />
#* The '''Version Range''' should always be set (0 to * to block all versions).<br />
#* The '''Severity''' should always be set to 0 (click to activate).<br />
#* The '''Vulnerability status''' should be set depending on whether the latest version is being blocked or not.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The '''Target Application''' is only necessary for blocks that only target specific applications, which should be very rare.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/plugins/records public JSON endpoint].<br />
===Testing===<br />
<br />
===Deploying===<br />
# Click on '''blocklist-preview bucket''' :: '''plugins'''<br />
<br />
== Graphics card blocks ==<br />
# Go to the [https://addons.mozilla.org/admin/models/blocklist/blocklistdetail/ blocklist detail page] and click on Add blocklist detail.<br />
# Enter a name and descriptions for the block. These detail pages aren't exposed to users, so these descriptions aren't very important.<br />
# Set the Bug field to the blocklist bug.<br />
# In the Blocklist Gfx #1 section, set the data that should have been detailed on the blocklist bug.<br />
<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''gfx'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields, which should be detailed in the bug report. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled checkbox''' checked.<br />
#* The '''name''' and '''bug''' fields are used for internal record keeping and won't be shown to users. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/plugins/records public JSON endpoint].<br />
===Testing===<br />
<br />
===Deploying===<br />
# Click on '''blocklist-preview bucket''' :: '''gfx'''</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Blocklisting/Admin&diff=1161270Blocklisting/Admin2017-01-27T22:57:37Z<p>Jorge.villalobos: Plugin blocks on kinto</p>
<hr />
<div>Blocklist entries are added through the Kinto Web Administration tool. Only authorized members of the Add-ons Team can manipulate the blocklist.<br />
<br />
# Login via the [https://settings-writer.prod.mozaws.net/v1/admin/ Kinto admin page] (VPN connection is required)<br />
# '''Authentication method''': Basic Auth<br />
# '''Username''': jdoe@mozilla.com. This is your full LDAP email address.<br />
# '''Password''': your_ldap_password<br />
<br />
All blocks are first created in the '''staging''' bucket, are later moved to the '''blocklist-preview''' bucket for testing and review, and then deployed to the final '''blocklists''' bucket.<br />
<br />
== Extension blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''addons'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled''' checkbox checked.<br />
#* You'll generally want to enter the '''Add-on ID''', '''Version Range''' (0 to * to block all versions), and '''Severity''' of the block.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The '''Target Application''' is only necessary for blocks that only target specific applications, which should also be very rare.<br />
#* The '''Preferences''' fields are used in case the add-on changed important Firefox preferences that need to be reset.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. If the extension being blocked is malware, add " (malware)" at the end of the name. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/addons/records public JSON endpoint], or on [https://addons.mozilla.org/en-US/firefox/blocked/ addons.mozilla.org].<br />
===Testing===<br />
<br />
====JSON Example====<br />
<br />
<pre><br />
{<br />
"guid":"{de71f09a-3342-48c5-95c1-4b0f17567554}",<br />
"blockID":"i1493",<br />
"enabled":true,<br />
"last_modified":1484867614757,<br />
"details":{<br />
"who":"All users who have this add-on installed.",<br />
"created":"2017-01-12T22:17:59Z",<br />
"bug":"https://bugzilla.mozilla.org/show_bug.cgi?id=1329654",<br />
"name":"Search for Firefox Convertor (malware)",<br />
"why":"This is a malicious add-on that is installed using a fake name. It changes search and homepage settings."<br />
},<br />
"versionRange":[<br />
{<br />
"targetApplication":[<br />
<br />
],<br />
"minVersion":"0",<br />
"maxVersion":"1.3.9",<br />
"severity":3<br />
}<br />
],<br />
"prefs":[<br />
<br />
],<br />
"id":"d6ec9f54-9945-088e-ba68-40117eaba24e",<br />
"schema":1484335370642<br />
}<br />
</pre><br />
===Deploying===<br />
# Click on '''blocklist-preview bucket''' :: '''addons'''<br />
<br />
== Plugin blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''plugins'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the '''Enabled checkbox''' checked.<br />
#* Plugins are usually identified by their '''Filename'''. '''Name''' and '''Description''' regular expression matches are used when the '''Filename''' doesn't work. [http://mzl.la/SemegK Regexp Pal] is a good tool for testing regular expression blocks.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these]. It's generally only needed for Linux blocks, since Linux and Android distributions use the same filename and plugins are never blocked on Android.<br />
#* The '''Version Range''' should always be set (0 to * to block all versions).<br />
#* The '''Severity''' should always be set to 0 (click to activate).<br />
#* The '''Vulnerability status''' should be set depending on whether the latest version is being blocked or not.<br />
#* The '''OS''' can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The '''Target Application''' is only necessary for blocks that only target specific applications, which should be very rare.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket.<br />
# Notify your reviewer/QA that the block is ready for testing.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/plugins/records public JSON endpoint], or on [https://addons.mozilla.org/en-US/firefox/blocked/ addons.mozilla.org].<br />
===Testing===<br />
<br />
===Deploying===<br />
# Click on '''blocklist-preview bucket''' :: '''addons'''<br />
<br />
== Graphics card blocks ==<br />
# Go to the [https://addons.mozilla.org/admin/models/blocklist/blocklistdetail/ blocklist detail page] and click on Add blocklist detail.<br />
# Enter a name and descriptions for the block. These detail pages aren't exposed to users, so these descriptions aren't very important.<br />
# Set the Bug field to the blocklist bug.<br />
# In the Blocklist Gfx #1 section, set the data that should have been detailed on the blocklist bug.<br />
<br />
===XML Examples===<br />
<pre><gfxBlacklistEntry blockID="g95"><br />
<os>WINNT 6.1</os><br />
<vendor>0x1002</vendor><br />
<devices><br />
<device>0x9802</device><br />
<device>0x9803</device><br />
<device>0x9803</device><br />
<device>0x9804</device><br />
<device>0x9805</device><br />
<device>0x9806</device><br />
<device>0x9807</device><br />
</devices><br />
<feature>DIRECT3D_9_LAYERS</feature><br />
<featureStatus>BLOCKED_DEVICE</featureStatus><br />
<driverVersion>1.0.0.0</driverVersion><br />
<driverVersionComparator>GREATER_THAN_OR_EQUAL</driverVersionComparator><br />
</gfxBlacklistEntry></pre></div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Blocklisting/Admin&diff=1161265Blocklisting/Admin2017-01-27T22:32:42Z<p>Jorge.villalobos: More kinto stuff</p>
<hr />
<div>Blocklist entries are added through the Kinto Web Administration tool. Only authorized members of the Add-ons Team can manipulate the blocklist.<br />
<br />
# Login via the [https://settings-writer.prod.mozaws.net/v1/admin/ Kinto admin page] (VPN connection is required)<br />
# '''Authentication method''': Basic Auth<br />
# '''Username''': jdoe@mozilla.com. This is your full LDAP email address.<br />
# '''Password''': your_ldap_password<br />
<br />
All blocks are first created in the '''staging''' bucket, are later moved to the '''blocklist-preview''' bucket for testing and review, and then deployed to the final '''blocklists''' bucket.<br />
<br />
== Extension blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''addons'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the Enabled checkbox checked.<br />
#* You'll generally want to enter the add-on ID, version range (0 to * to block all versions), and severity of the block.<br />
#* The OS can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The Target Application is only necessary for blocks that only target specific applications, which should also be very rare.<br />
#* The Preferences fields are used in case the add-on changed important Firefox preferences that need to be reset.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. If the extension being blocked is malware, add " (malware)" at the end of the name. '''bug''' should be a Bugzilla URL.<br />
# When done, click on '''Create Record'''. This saves the block in the '''staging''' bucket.<br />
# If you don't need to make more changes to the block, click on '''Request review''' back in the main bucket view. The block should be moved to the '''blocklists-preview''' bucket<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/addons/records public JSON endpoint], or on [https://addons.mozilla.org/en-US/firefox/blocked/ addons.mozilla.org].<br />
===Testing===<br />
<br />
====JSON Example====<br />
<br />
<pre><br />
{<br />
"guid":"{de71f09a-3342-48c5-95c1-4b0f17567554}",<br />
"blockID":"i1493",<br />
"enabled":true,<br />
"last_modified":1484867614757,<br />
"details":{<br />
"who":"All users who have this add-on installed.",<br />
"created":"2017-01-12T22:17:59Z",<br />
"bug":"https://bugzilla.mozilla.org/show_bug.cgi?id=1329654",<br />
"name":"Search for Firefox Convertor (malware)",<br />
"why":"This is a malicious add-on that is installed using a fake name. It changes search and homepage settings."<br />
},<br />
"versionRange":[<br />
{<br />
"targetApplication":[<br />
<br />
],<br />
"minVersion":"0",<br />
"maxVersion":"1.3.9",<br />
"severity":3<br />
}<br />
],<br />
"prefs":[<br />
<br />
],<br />
"id":"d6ec9f54-9945-088e-ba68-40117eaba24e",<br />
"schema":1484335370642<br />
}<br />
</pre><br />
<br />
<br />
===Deploying===<br />
# Click on '''blocklist-preview bucket''' :: '''addons'''<br />
<br />
== Plugin blocks ==<br />
# Go to the [https://addons.mozilla.org/admin/models/blocklist/blocklistdetail/ blocklist detail page] and click on Add blocklist detail.<br />
# Enter a clear name and descriptions for the block. End users will read these, so they need to be clear as to why the block was put in place and what options are available. If the extension being blocked is malware, add " (malware)" at the end of the name.<br />
#* See the [https://addons.mozilla.org/firefox/blocked/ Blocked Add-ons page] for examples.<br />
# Set the Bug field to the blocklist bug. The bug should also have instructions for end users if the plugin is heavily used.<br />
# In the Blocklist Plugin #1 section, set the identification criteria and Severity.<br />
#* Plugins rarely have a GUID, so we use the filename field to identify plugins. Since filenames are OS-specific, the OS field is usually redundant.<br />
#* The OS can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these].<br />
#* Plugin version numbers can also be tricky and inconsistent, specially on Linux, where the version number isn't properly detected. We generally use regular expressions in the Name or Descriptions to identify the versions to block.<br />
#* Regular expressions in plugins should be meticulously tested. [http://mzl.la/SemegK Regexp Pal] is a good tool for this.<br />
#* The Severity should be 1 for soft blocks and 3 for hard blocks. A severity set to 2 (reserved for a medium block), or no severity will also produce a hard block. To avoid ambiguity, these options shouldn't be used. Hard blocks should be limited to malware.<br />
#* A Severity set to 0 has different meanings depending on the vulnerability status value. If not set, it is an update prompt block. If set to 1 or 2, it means it's a click-to-play block (1 when there's a known fixed update, 2 when there isn't).<br />
To limit a block to a specific application versions, the detail can be added with an invalid filename, to keep it temporarily disabled. Then you can add a [https://addons.mozilla.org/admin/models/blocklist/blocklistapp/ blocklist app item] and link it to the detail item. Once that's done, the Severity or GUID can be set to their real values.<br />
<br />
===XML Examples===<br />
This is how the different block types look in blocklist.xml.<br />
<br />
Soft block on Mac OS (where version numbers work correctly):<br />
<pre><pluginItem blockID="p85"><br />
<match name="filename" exp="JavaPlugin2_NPAPI\.plugin" /><br />
<versionRange minVersion="0" maxVersion="13.6.0" severity="1"><br />
</versionRange><br />
</pluginItem></pre><br />
<br />
Update prompt block:<br />
<pre><pluginItem blockID="p134"><br />
<match name="name" exp="Java\(TM\) Platform SE 7 U[5-6](\s[^\d\._U]|$)" /><br />
<match name="filename" exp="npjp2\.dll" /><br />
<versionRange severity="0"><br />
</versionRange><br />
</pluginItem></pre><br />
<br />
Hard block with target application:<br />
<pre><pluginItem blockID="p27"><br />
<match name="name" exp="QuickTime Plug-in 7[.]1[.]" /><br />
<match name="filename" exp="npqtplugin.?[.]dll" /><br />
<versionRange ><br />
<targetApplication id="{ec8030f7-c20a-464f-9b0e-13a3a9e97384}"><br />
<versionRange minVersion="3.0a1" maxVersion="3.*" /><br />
</targetApplication><br />
</versionRange><br />
</pluginItem></pre><br />
<br />
== Graphics card blocks ==<br />
# Go to the [https://addons.mozilla.org/admin/models/blocklist/blocklistdetail/ blocklist detail page] and click on Add blocklist detail.<br />
# Enter a name and descriptions for the block. These detail pages aren't exposed to users, so these descriptions aren't very important.<br />
# Set the Bug field to the blocklist bug.<br />
# In the Blocklist Gfx #1 section, set the data that should have been detailed on the blocklist bug.<br />
<br />
===XML Examples===<br />
<pre><gfxBlacklistEntry blockID="g95"><br />
<os>WINNT 6.1</os><br />
<vendor>0x1002</vendor><br />
<devices><br />
<device>0x9802</device><br />
<device>0x9803</device><br />
<device>0x9803</device><br />
<device>0x9804</device><br />
<device>0x9805</device><br />
<device>0x9806</device><br />
<device>0x9807</device><br />
</devices><br />
<feature>DIRECT3D_9_LAYERS</feature><br />
<featureStatus>BLOCKED_DEVICE</featureStatus><br />
<driverVersion>1.0.0.0</driverVersion><br />
<driverVersionComparator>GREATER_THAN_OR_EQUAL</driverVersionComparator><br />
</gfxBlacklistEntry></pre></div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Blocklisting/Admin&diff=1161264Blocklisting/Admin2017-01-27T22:23:36Z<p>Jorge.villalobos: Doing some refactoring for the kinto instructions</p>
<hr />
<div>Blocklist entries are added through the Kinto Web Administration tool. Only authorized members of the Add-ons Team can manipulate the blocklist.<br />
<br />
# Login via the [https://settings-writer.prod.mozaws.net/v1/admin/ Kinto admin page] (VPN connection is required)<br />
# '''Authentication method''': Basic Auth<br />
# '''Username''': jdoe@mozilla.com. This is your full LDAP email address.<br />
# '''Password''': your_ldap_password<br />
<br />
All blocks are first created in the '''staging''' bucket, are later moved to the '''blocklist-preview''' bucket for testing and review, and then deployed to the final '''blocklists''' bucket.<br />
<br />
== Extension blocks ==<br />
===Staging===<br />
# Click on '''staging bucket''' :: '''addons'''<br />
# Click on "Create" (or edit/delete icons if you need to change an existing record)<br />
# Enter in the appropriate fields. Example below (see the current list<sup>1</sup> for more examples)<br />
#* Keep the Enabled checkbox checked.<br />
#* You'll generally want to enter the add-on ID, version range (0 to * to block all versions), and severity of the block.<br />
#* The OS can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these], but OS-specific blocks are rarely needed.<br />
#* The Target Application is only necessary for blocks that only target specific applications, which should also be very rare.<br />
#* The Preferences fields are used in case the add-on changed important Firefox preferences that need to be reset.<br />
#* The '''name''', '''why''', '''who''', and '''bug''' fields are shown to end users, so they need to be clear as to why the block was put in place and what options are available. If the extension being blocked is malware, add " (malware)" at the end of the name. '''bug''' should be a Bugzilla URL.<br />
<br />
<sup>1</sup> Data for the blocklist can be found in the [https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/addons/records public JSON endpoint], or on [https://addons.mozilla.org/en-US/firefox/blocked/ addons.mozilla.org].<br />
===Testing===<br />
<br />
====JSON Example====<br />
<br />
<pre><br />
{<br />
"guid":"{de71f09a-3342-48c5-95c1-4b0f17567554}",<br />
"blockID":"i1493",<br />
"enabled":true,<br />
"last_modified":1484867614757,<br />
"details":{<br />
"who":"All users who have this add-on installed.",<br />
"created":"2017-01-12T22:17:59Z",<br />
"bug":"https://bugzilla.mozilla.org/show_bug.cgi?id=1329654",<br />
"name":"Search for Firefox Convertor (malware)",<br />
"why":"This is a malicious add-on that is installed using a fake name. It changes search and homepage settings."<br />
},<br />
"versionRange":[<br />
{<br />
"targetApplication":[<br />
<br />
],<br />
"minVersion":"0",<br />
"maxVersion":"1.3.9",<br />
"severity":3<br />
}<br />
],<br />
"prefs":[<br />
<br />
],<br />
"id":"d6ec9f54-9945-088e-ba68-40117eaba24e",<br />
"schema":1484335370642<br />
}<br />
</pre><br />
<br />
<br />
===Deploying===<br />
<br />
== Plugin blocks ==<br />
# Go to the [https://addons.mozilla.org/admin/models/blocklist/blocklistdetail/ blocklist detail page] and click on Add blocklist detail.<br />
# Enter a clear name and descriptions for the block. End users will read these, so they need to be clear as to why the block was put in place and what options are available. If the extension being blocked is malware, add " (malware)" at the end of the name.<br />
#* See the [https://addons.mozilla.org/firefox/blocked/ Blocked Add-ons page] for examples.<br />
# Set the Bug field to the blocklist bug. The bug should also have instructions for end users if the plugin is heavily used.<br />
# In the Blocklist Plugin #1 section, set the identification criteria and Severity.<br />
#* Plugins rarely have a GUID, so we use the filename field to identify plugins. Since filenames are OS-specific, the OS field is usually redundant.<br />
#* The OS can be set to [https://developer.mozilla.org/en-US/docs/OS_TARGET any of these].<br />
#* Plugin version numbers can also be tricky and inconsistent, specially on Linux, where the version number isn't properly detected. We generally use regular expressions in the Name or Descriptions to identify the versions to block.<br />
#* Regular expressions in plugins should be meticulously tested. [http://mzl.la/SemegK Regexp Pal] is a good tool for this.<br />
#* The Severity should be 1 for soft blocks and 3 for hard blocks. A severity set to 2 (reserved for a medium block), or no severity will also produce a hard block. To avoid ambiguity, these options shouldn't be used. Hard blocks should be limited to malware.<br />
#* A Severity set to 0 has different meanings depending on the vulnerability status value. If not set, it is an update prompt block. If set to 1 or 2, it means it's a click-to-play block (1 when there's a known fixed update, 2 when there isn't).<br />
To limit a block to a specific application versions, the detail can be added with an invalid filename, to keep it temporarily disabled. Then you can add a [https://addons.mozilla.org/admin/models/blocklist/blocklistapp/ blocklist app item] and link it to the detail item. Once that's done, the Severity or GUID can be set to their real values.<br />
<br />
===XML Examples===<br />
This is how the different block types look in blocklist.xml.<br />
<br />
Soft block on Mac OS (where version numbers work correctly):<br />
<pre><pluginItem blockID="p85"><br />
<match name="filename" exp="JavaPlugin2_NPAPI\.plugin" /><br />
<versionRange minVersion="0" maxVersion="13.6.0" severity="1"><br />
</versionRange><br />
</pluginItem></pre><br />
<br />
Update prompt block:<br />
<pre><pluginItem blockID="p134"><br />
<match name="name" exp="Java\(TM\) Platform SE 7 U[5-6](\s[^\d\._U]|$)" /><br />
<match name="filename" exp="npjp2\.dll" /><br />
<versionRange severity="0"><br />
</versionRange><br />
</pluginItem></pre><br />
<br />
Hard block with target application:<br />
<pre><pluginItem blockID="p27"><br />
<match name="name" exp="QuickTime Plug-in 7[.]1[.]" /><br />
<match name="filename" exp="npqtplugin.?[.]dll" /><br />
<versionRange ><br />
<targetApplication id="{ec8030f7-c20a-464f-9b0e-13a3a9e97384}"><br />
<versionRange minVersion="3.0a1" maxVersion="3.*" /><br />
</targetApplication><br />
</versionRange><br />
</pluginItem></pre><br />
<br />
== Graphics card blocks ==<br />
# Go to the [https://addons.mozilla.org/admin/models/blocklist/blocklistdetail/ blocklist detail page] and click on Add blocklist detail.<br />
# Enter a name and descriptions for the block. These detail pages aren't exposed to users, so these descriptions aren't very important.<br />
# Set the Bug field to the blocklist bug.<br />
# In the Blocklist Gfx #1 section, set the data that should have been detailed on the blocklist bug.<br />
<br />
===XML Examples===<br />
<pre><gfxBlacklistEntry blockID="g95"><br />
<os>WINNT 6.1</os><br />
<vendor>0x1002</vendor><br />
<devices><br />
<device>0x9802</device><br />
<device>0x9803</device><br />
<device>0x9803</device><br />
<device>0x9804</device><br />
<device>0x9805</device><br />
<device>0x9806</device><br />
<device>0x9807</device><br />
</devices><br />
<feature>DIRECT3D_9_LAYERS</feature><br />
<featureStatus>BLOCKED_DEVICE</featureStatus><br />
<driverVersion>1.0.0.0</driverVersion><br />
<driverVersionComparator>GREATER_THAN_OR_EQUAL</driverVersionComparator><br />
</gfxBlacklistEntry></pre></div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/developer/communication/nov2016_update&diff=1154988Add-ons/developer/communication/nov2016 update2016-11-16T21:08:01Z<p>Jorge.villalobos: Change internal links to remove annoying 'm'</p>
<hr />
<div>=Evolution in Add-on Development=<br />
[[WebExtensions|WebExtensions]] are becoming the standard for add-on development in Firefox. It will be the only type of add-on supported in Firefox by the end of 2017. <br />
<br />
This page contains timelines, tutorials, and other resources to help you port your add-on to WebExtensions. If you're looking for resources on creating a new add-on, please head over to [https://developer.mozilla.org/en-US/Add-ons/WebExtensions MDN].<br />
<br />
=====What's New=====<br />
*[http://webextensions-experiments.readthedocs.io/ WebExtensions Experiments]: prototype WebExtension APIs without having to build Firefox<br />
*Help plan and prioritize WebExtensions APIs by joining the new bi-weekly [[Add-ons/Contribute/Triage|public triage]].<br />
*Thanks to [https://github.com/aterranova-bv aterranova-bv] for the new [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Examples#Emoji_Substitution Emoji Substitution WebExtension Example]!<br />
<br />
=Timelines & Roadmaps=<br />
*[https://trello.com/b/ZpIDuMAW/addon-planning Add-on planning]: see what the add-on team is working on<br />
*[https://trello.com/b/MwClom9J/addon-impacting-changes Impacting changes]: see what changes are coming up that impact compatibility<br />
*[https://trello.com/b/PC9kB14s/webextensions-roadmap WebExtensions Roadmap]: see which APIs are coming up<br />
<br />
=Migration paths for developers of legacy add-ons=<br />
=====1) SDK add-on=====<br />
Here is the comparison chart showing [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Comparison_with_the_Add-on_SDK SDK APIs and their WebExtensions counterparts]. If you don't see the APIs you need to port to WebExtensions, please take a look at [https://wiki.mozilla.org/index.php?title=Add-ons/developer/communication/nov2016_update&action=edit#Don.27t_See_the_WebExtensions_APIs_You_Need.3F some more] options below.<br />
<br />
=====2) XUL or XPCOM add-on=====<br />
Here is the comparison chart showing [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Comparison_with_XUL_XPCOM_extensions XUL/XPCOM APIs and their WebExtensions counterparts]. If you don't see the APIs you need to port to WebExtensions, please take a look at some [https://wiki.mozilla.org/index.php?title=Add-ons/developer/communication/nov2016_update&action=edit#Don.27t_See_the_WebExtensions_APIs_You_Need.3F more options] below.<br />
<br />
=Don't See the WebExtensions APIs You Need?=<br />
<br />
*If you're experienced with Mozilla infrastructure and would like to develop WebExtensions APIs directly for Firefox, here is a list of [https://mzl.la/2dVs5Ys approved APIs] that you can start contributing to.<br />
<br />
*If you want to prototype and tinker with WebExtensions APIs without having to build Firefox, [http://webextensions-experiments.readthedocs.io/en/latest/index.html WebExtensions Experiments] is for you!<br />
<br />
*If you just want to request a WebExtensions API, please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Toolkit&component=WebExtensions:%20Untriaged file a bug]. These will be triaged and processed in a [[Add-ons/Contribute/Triage|bi-weekly public meeting]].<br />
<br />
[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Embedded_WebExtensions Embedded WebExtensions] - In Firefox 51, you will be able to embed a WebExtensions add-on inside an existing SDK or bootstrapped add-on. This is especially useful to developers of SDK or bootstrapped add-ons who want to start migrating to WebExtensions and take advantage of new APIs like Native Messaging, but can’t fully migrate yet. It’s also useful for developers who want to complete data migration towards WebExtensions, and who want to take parts of their add-on that are not compatible with [https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox multiprocess Firefox] and make them compatible.<br />
<br />
Not all add-ons will be able to migrate to WebExtensions without having to drop any features. But we want to work with you to get as many add-ons migrated as possible with the functionality you created intact. We invite you to contribute to its evolution, and we look forward to [[Add-ons/developer/communication#Get_in_Touch|working with you]].<br />
<br />
=Tools=<br />
*[https://compatibility-lookup.services.mozilla.com/ Lookup tool] to check your add-on type and get porting resource recommendations<br />
<br />
=Documentation=<br />
*[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_a_legacy_Firefox_add-on Porting guides that map SDK and XUL APIs to available WebExtensions APIs]<br />
*[https://developer.mozilla.org/en-US/Add-ons/WebExtensions How-to guides] covering common add-on developer cases, like [https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Intercept_HTTP_requests intercepting web requests] and [https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Add_a_button_to_the_toolbar adding a button to the toolbar]<br />
*[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Comparison_with_the_Add-on_SDK Comparison with the Add-on SDK]<br />
*[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Comparison_with_XUL_XPCOM_extensions Comparison with XUL/XPCOM extensions]<br />
*[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs Browser compatibility table] for all WebExtensions APIs<br />
*[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Examples Examples of WebExtensions]<br />
<br />
=Blog Posts=<br />
*Nov 3, 2016: [https://blog.mozilla.org/addons/2016/11/03/more-ways-to-contribute-to-webextensions/ More ways to contribute to WebExtensions]<br />
*Sep 29, 2016: [https://blog.mozilla.org/addons/2016/09/29/webextensions-in-firefox-51/ WebExtensions in Firefox 51]<br />
*Sep 28, 2016: [https://blog.mozilla.org/addons/2016/09/28/migrating-an-sdk-add-on-to-multiprocess-firefox/ How Video DownloadHelper Became Compatible with Multiprocess Firefox]<br />
*Sep 13, 2016: [https://blog.mozilla.org/addons/2016/09/13/webextensions-and-parity-with-chrome/ WebExtensions and parity with Chrome]<br />
*Aug 25, 2016: [https://blog.mozilla.org/addons/2016/08/25/webextensions-in-firefox-50/ WebExtensions in Firefox 50]<br />
*Aug 12, 2016: [https://blog.mozilla.org/addons/2016/08/12/webextensions-taking-root/ WebExtensions Taking Root]<br />
*July 27, 2016: [https://blog.mozilla.org/addons/2016/07/27/linting-and-automatically-reloading-webextensions/ Linting and Automatically Reloading WebExtensions]<br />
*July 21, 2016: [https://blog.mozilla.org/addons/2016/07/21/new-webextensions-guides-and-how-tos-on-mdn/ New WebExtensions Guides and How-tos on MDN]<br />
*July 14, 2016: [https://blog.mozilla.org/addons/2016/07/14/webextensions-support-on-amo/ WebExtensions support on AMO]<br />
*June 9, 2016: [https://blog.mozilla.org/addons/2016/06/09/webextensions-for-firefox-49/ WebExtensions in Firefox 49]<br />
*May 9, 2016: [https://blog.mozilla.org/addons/2016/05/09/results-of-the-webextensions-api-survey/ Results of the WebExtensions API Survey]<br />
*Apr 29, 2016: [https://blog.mozilla.org/addons/2016/04/29/webextensions-in-firefox-48/ WebExtensions in Firefox 48]<br />
*Apr 26, 2016: [https://blog.mozilla.org/addons/2016/04/26/migrating-popup-alt-attribute-from-xulxpcom-to-webextensions/ Migrating Popup ALT Attribute from XUL/XPCOM to WebExtensions]<br />
*Apr 14, 2016: [https://blog.mozilla.org/addons/2016/04/14/developing-extensions-with-web-ext-1-0/ Developing Extensions With Web-ext 1.0]<br />
*Mar 30, 2016: [https://blog.mozilla.org/addons/2016/03/30/tinkering-with-webextensions/ Tinkering with WebExtensions]<br />
*Mar 14, 2016: [https://blog.mozilla.org/addons/2016/03/14/webextensons-whats-in-it-for-developers/ Advantages of WebExtensions for Developers]<br />
*Mar 11, 2016: [https://blog.mozilla.org/addons/2016/03/11/webextensions-in-firefox-47/ WebExtensions in Firefox 47]<br />
*Feb 2, 2016: [https://blog.mozilla.org/addons/2016/02/02/webextensions-in-firefox-46/ WebExtensions in Firefox 46]<br />
*Jan 9, 2016: [https://discourse.mozilla-community.org/t/webextensions-first-impressions/6459 WebExtensions First Impressions]<br />
*Dec 21, 2015: [https://blog.mozilla.org/addons/2015/12/21/webextensions-in-firefox-45-2/ WebExtensions in Firefox 45]<br />
*Aug 21, 2015: [https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ The Future of Developing Firefox Add-ons]<br />
<br />
=Add-on Developer Communication Calendar=<br />
This calendar includes public meetings, scheduled blog posts, office hours, release milestones that affect add-on developers, and more. Links to add it to your own calendar: [https://calendar.google.com/calendar/ical/mozilla.com_ofjlct07k1784v1u51bqk476bk%40group.calendar.google.com/public/basic.ics iCal] | [https://calendar.google.com/calendar/embed?src=mozilla.com_ofjlct07k1784v1u51bqk476bk%40group.calendar.google.com&ctz=America/Los_Angeles HTML]<br />
<br />
{{#widget:Widget:Google Calendar<br />
|id=bW96aWxsYS5jb21fb2ZqbGN0MDdrMTc4NHYxdTUxYnFrNDc2YmtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ<br />
}}<br />
<br />
=Get in Touch=<br />
* [[IRC|IRC]]:<br />
** #teamaddons: team chat <br />
** #addons: support for extensions, themes, plugins and addons.mozilla.org<br />
** #amo: addons.mozilla.org bugs and development<br />
** #amo-editors: add-on reviews and policy<br />
** #extdev: extension development<br />
** #themedev: theme development<br />
** #webextensions: web extensions<br />
<br />
* Mailing List: [https://mail.mozilla.org/listinfo/dev-addons dev-addons]<br />
* Blog: https://blog.mozilla.org/addons/<br />
* Forum: https://discourse.mozilla-community.org/c/add-ons</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Reviewers&diff=1154852Add-ons/Reviewers2016-11-15T20:27:43Z<p>Jorge.villalobos: Text tweak to remove app reference</p>
<hr />
<div>__NOTOC__ <br />
== Introduction ==<br />
[https://mozillians.org/en-US/group/249-amo-editors The AMO Reviewer Team] (also known as AMO Editors) is a Mozilla community made up of add-on developers dedicated to the security and reliability of all add-ons for Mozilla applications. They review new and updated add-ons as part of the add-on review process, and decide if they are appropriate for publication. They do so according to established [https://developer.mozilla.org/Mozilla/Add-ons/AMO/Policy/Reviews Review Policies].<br />
<br />
== Join us ==<br />
<br />
Add-ons are an integral part of what makes Firefox innovative, useful, and fun--and AMO Reviewers help keep it that way! As a key member of the Mozilla community, editors enjoy these privileges and perks:<br />
<br />
* <b>[https://wiki.mozilla.org/Add-ons/Reviewers/Points_and_Incentives Earn gear:]</b> accumulate points to earn gear, from t-shirts to Android tablets<br />
* <b>Review privileges:</b> submissions authored by reviewers are fast-tracked when possible<br />
* <b>Invitations to events:</b> top reviewers are regularly invited to Mozilla [[Coincidental_work_weeks|events]] worldwide<br />
[[File:Mozlondon-addons.jpg|700px|center||Add-ons Meetup in London, June 2016]]<br />
<br />
<br />
[[Add-ons/Reviewers/Applying|Join us today!]]<br />
<br />
== Contact us ==<br />
<br />
You can contact us at amo-editors at mozilla.org and the [irc://irc.mozilla.org/amo-editors #amo-editors] IRC channel (irc.mozilla.org). We also monitor the [https://discourse.mozilla-community.org/c/add-ons Add-ons Forum].<br />
<br />
== Meetups ==<br />
*Reviewer meetup at Mozlando 2015: [https://blog.mozilla.org/addons/files/2016/02/DSC_4087-e1454965785705.jpg Photo]<br />
*Reviewer meetup at MozFest 2014 in London: [https://www.flickr.com/photos/mozamoteam/sets/72157648969050906 Photos] and [https://mozamy.wordpress.com/2014/11/04/add-on-and-app-reviewer-meetup-at-mozfest-2014/ blog post]<br />
*Reviewer meetup at Summit 2013 in Brussels: [https://www.flickr.com/photos/mozamoteam/sets/72157655324482831 Photos]<br />
*Reviewer meetup MozCamp EU 2012 in Warsaw: [http://www.flickr.com/photos/mozamoteam/tags/amoeditormeetup/ Photos] and [https://blog.mozilla.org/addons/2012/09/17/mozcamp-2012-wrap-up/ blog post]<br />
<br />
== Resources ==<br />
<br />
*[[Add-ons/Reviewers/Applying|How to become a reviewer]] <br />
*[https://developer.mozilla.org/en-US/Add-ons/AMO/Policy Add-on Policies]<br />
*[[Add-ons/Reviewers/Guide|AMO Reviewer Guide]]</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Contribute/Triage&diff=1154836Add-ons/Contribute/Triage2016-11-15T18:22:24Z<p>Jorge.villalobos: Updating WE queries</p>
<hr />
<div>= Purpose of Meeting =<br />
A bi-weekly triage session to accomplish these community goals:<br />
* '''WebExtensions APIs''': <br />
** Transparency: Decide whether APIs tagged "design-decision-needed" are "design-decision-approved" or "wontfix" to ensure transparency for the direction of WebExtensions. <br />
** Participation: Give guidance on and assign advisors to APIs marked "design-decision-approved" to make it easier for contributors to get involved.<br />
* '''Good First Bugs''': Ensure add-on bugs marked "Good First Bug" are fresh and updated for new contributors. If you are a new contributor who wants to write code for add-on related projects, please [https://wiki.mozilla.org/Add-ons/Contribute/Code start here].<br />
<br />
=Next Meeting=<br />
Next meeting is [https://docs.google.com/document/d/1cMvAtlIZpykpxZ0bG2J2lh7Mx1WcVfLrHSDJZHFvexc/edit Nov 15, 2016]<br />
<br />
=Details & How to Join=<br />
* Time: Every other Tuesday at:<br />
**[http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 10:00am Pacific] - Good First Bugs<br />
**[http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 10:30am Pacific] - WebExtensions<br />
* Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU<br />
*IRC: [https://wiki.mozilla.org/IRC irc.mozilla.org], #Addons channel<br />
<br />
=WebExtensions APIs Triage=<br />
==Triage Guidelines==<br />
Bugs marked "design-decision-needed" should be:<br />
*Tagged with "design-decision-approved" or "wontfix" (including reason)<br />
<br />
Bugs marked "design-decision-approved" should have:<br />
*Clear description of the API and suggested implementation if possible<br />
*Priority & impact<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code#Develop_Web_Extensions_APIs onboarding process]<br />
*Advisor<br />
<br />
==Bug Queries==<br />
====="design-decision-needed"=====<br />
These are determined from the Monday WebExtensions triage. They are APIs we [https://mzl.la/2edmiid need more discussion] on.<br />
<br />
====="design-decision-approved"=====<br />
These are APIs we would [https://mzl.la/2dVs5Ys like to have]. They should meet the triage criteria listed above.<br />
<br />
=Good First Bugs Triage=<br />
==Triage Guidelines==<br />
All "Good First Bugs" should have:<br />
*Clear description of the issue<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code onboarding process]<br />
*Mentor<br />
<br />
==Bug Queries==<br />
=====addons-server "Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=good%20first%20bug This is the query] contributors see. We should spot-check them to ensure they are properly triaged.<br />
<br />
=====addons-server "Maybe Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=maybe%20good%20first%20bug These are tagged "Maybe Good First Bugs"]. We triage these and change the tag to "Good First Bugs" if determined to be good for new contributors.<br />
<br />
=====WebExtensions Bugs on Bugzilla=====<br />
*These are WebExtensions bugs that [https://mzl.la/2fCKNSu don't have a mentor]<br />
*These are WebExtensions bugs that [https://mzl.la/2f1sb0l have an assignee but haven't been commented on for 3 weeks]<br />
<br />
=====Add-ons Manager Bugs on Bugzilla=====<br />
*These are Add-ons Manager bugs that [https://mzl.la/2acSvC0 don't have a mentor]<br />
*These are Add-ons Manager bugs that [https://mzl.la/2ajmxp8 have an assignee but haven't been commented on for 3 weeks]<br />
<br />
= Archive =<br />
=====2016=====<br />
[https://docs.google.com/document/d/1i5CT821JFutWL-f3AZ3VhlYIIzulnMttjNp1JsYba8M/edit# Nov 1, 2016]<br /><br />
[https://docs.google.com/document/d/1elytPf_HqAqqFC6EM0-hrJp7kWJA-LfKILXV1tzNLTU/edit Oct 18, 2016]<br /><br />
[https://docs.google.com/document/d/1BDIbINMGgjoWlZxHmw-MnLm3HEqB38oUNTJUPAippGo/edit Oct 4, 2016]<br /><br />
[https://docs.google.com/document/d/1gABxxstInPy5XMsmoYMhZBMsLGFWNsgWMhgjUlt7-o8/edit Sept 20, 2016]<br /><br />
[https://docs.google.com/document/d/14cqCfgbyGoBXe7ttho0L3mIe4FcSSlzHH3L4fBFnLzA/edit Sept 6, 2016]<br /><br />
[https://docs.google.com/document/d/1GDpdcO1EHefRL3B5p5g1emdp_lY-YFWjwXv8YG1EgWo/edit August 23, 2016]<br /><br />
[https://docs.google.com/document/d/1rZvIfFILAHozLGTrg5C7Q7lXyEZ2gfMDw7cVkEo34io/edit August 9, 2016]<br /><br />
[https://docs.google.com/document/d/1A5hKaon2Z3nSCQc9ToYTOjr2cIpmmeZmu9EnbhVjHd0/edit July 26, 2016]<br /><br />
[https://docs.google.com/document/d/18wCqoUzNYshOWDjuJjePFivb4T5nD0WlFE06NKn3YQ0/edit July 12, 2016]<br /><br />
[https://docs.google.com/document/d/1uBo-WVFP2v-dyeYyDtfPD9ipN8JeIw7sCag4CYonQqY/edit# June 28, 2016]<br /><br />
[https://docs.google.com/document/d/1lYqcEWaktMXPmAefRB9PW9iSBM95rlVKFOO-vFRewdE/edit May 31, 2016]<br /><br />
[https://docs.google.com/document/d/1Bq7gTVhsGfTW58A9MUurruu5jc2w5OHSeaoRbmWRQV4/edit May 17, 2016]<br /><br />
[https://docs.google.com/document/d/1EkZXtIx7TkQxnFn_2ei3SR7j9xeDVc1WSl3suY2n8RU/edit April 28, 2016]<br /><br />
[https://docs.google.com/document/d/13yPW-ojA_jzXUe7_fxDvYQavsr5yEHZzHXXCMcuZgCA/edit April 14, 2016]<br /><br />
[https://docs.google.com/document/d/1hSABd9dd8UktXGJuf0iXn_8Fpuz09VEqkxrxMY_AvZw/edit Mar 31, 2016]<br /><br />
[https://docs.google.com/document/d/1ss0i_zAZDytsyBnMGF1gdRI6LjRWqvQS9Q0ueKzQV1Q/edit Mar 3, 2016]<br /><br />
[https://docs.google.com/document/d/1GkHWjHRDcUd7WD2BFF-6zhdyce4lK8qMX23O6C0eRIA/edit Feb 18, 2016]<br /><br />
[https://docs.google.com/document/d/1cM2JIIgw1i7TJe3oOojCtJvEhJoBGdHgNvjS2hRfBcw/edit Feb 4, 2016]<br /> <br />
[https://docs.google.com/document/d/1OZVV_HVXWAY-1u-nPhb4MrXOsycVFbXkXGEhhTomoaM/edit Jan 21, 2016]<br /><br />
[https://docs.google.com/document/d/1GwqhWsSsBp5vfLW7-5Di8_CzIfepwK9YVZAnQuLxK9I/edit Jan 7, 2016]<br />
<br />
=====2015=====<br />
[https://docs.google.com/document/d/18Csoja50IhnjqraFzxEYyVIJp-j79GLO2gCrvTSYHUI/edit Nov. 19, 2015]<br /><br />
[https://docs.google.com/document/d/1gbhL0S4amQ447ddIX7mEZsSaGoiFt8fTw22FKe_GbIo/edit Oct. 29, 2015]<br /><br />
[https://docs.google.com/document/d/1EoLSXHKCqJzTatj6CLLpjomwXnN5zUOA897brO_1aJQ/edit Oct. 15, 2015]<br />
<br />
=====Aug - Oct 2015=====<br />
https://drive.google.com/drive/folders/0B2aDMRMZ7uzvYzA4Wm1VYVhvemM</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Reviewers/Admins&diff=1152041Add-ons/Reviewers/Admins2016-10-20T20:39:18Z<p>Jorge.villalobos: Minor URL update</p>
<hr />
<div>== How to add an add-on to the [https://addons.mozilla.org/language-tools/ Language Tools page] ==<br />
This should only be done for language packs and dictionaries. The developers will usually email amo-admins or amo-editors to request this. If the email was to amo-editors, make sure to forward/cc to amo-admins.<br />
# Go to the add-on management page ([https://addons.mozilla.org/developers/addon/myeja/edit for example]).<br />
# Scroll down, locate the Admin Settings box, and click on the Edit button.<br />
# In the Target Locate textbox, enter the 2 or 5-digit locale code. You can find it in the code of the add-on.<br />
# If there's another add-on of the same type already listed for that locale in the Language Tools page, you should use the Additional Locale Info to differentiate them. Try asking the developer why their add-on is different. While it's okay to have dupes, they should be very rare.<br />
<br />
== How to change the blocklist==<br />
The [[Blocklisting/Admin|Blocklist Admin page]] explains the process. Only full admins (currently, Jorge and Andy) can do this at the moment. There's a plan to move the administration of the blocklist to a more flexible tool.<br />
==How to remove an ID from the blacklist==<br />
Only full admins (currently, Jorge and Andy) can do this at the moment. [https://github.com/mozilla/olympia/issues/978 This bug] tracks creating a proper tool that support this for all admin reviewers.<br />
<br />
# First, make sure the developer requesting this actually owns the ID.<br />
# Go to the [https://addons.mozilla.org/admin/models/addons/blacklistedguid/ blacklist management page].<br />
# Look for the ID and click on it. If the ID was deleted long ago, it might be easier to look it up on the DB first to find the blacklist entry ID.<br />
# Delete<br />
<br />
==Shortcuts to Admin Queues==<br />
The following are links to the queues, but showing admin only.<br />
# [https://addons.mozilla.org/en-US/editors/queue/new?searching=True&text_query=&admin_review=1&application_id=&max_version=&waiting_time_days=#review-actions New Submissions Queue]<br />
# [https://addons.mozilla.org/en-US/editors/queue/updates?searching=True&text_query=&admin_review=1&application_id=&max_version=&waiting_time_days=#review-actions Updated Queue]<br />
<br />
==Managing featured add-ons on AMO==<br />
*[https://addons.mozilla.org/firefox/discovery/modules Set promos in the carousel and the order they appear in] (the main graphic at the top of the AMO homepage)<br />
*[https://addons.mozilla.org/admin/monthly-pick Set the Pick-of-the-Month in the carousel]<br />
*[https://addons.mozilla.org/firefox/collections/mozilla/featured-add-ons/ Set featured add-ons] (cycles through the Featured Extensions box on the homepage and appears when the Featured filter is applied]<br />
<br />
==Mailing List==<br />
Sign up for the amo-editors@mozilla.org mailing list here - https://mail.mozilla.org/listinfo/amo-editors<br />
<br />
==Re-reviewing an Addon==<br />
This section requires use of the "Admin" page. This addon page looks easy but is very complicated. It allows you select and submit invalid choice combinations without telling you. You cannot know which ones are valid without being very familiar with the code internals. Therefore, if you are not familiar with the code or valid combinations, do not do this. Instead reach out to seniors.<br />
<br />
This is a workaround for a current bug. In order to change a review, do not go to the admin page and change the review, but go to the admin page and set it to "Awaiting Review". [https://addons.mozilla.org/en-US/admin/addon/manage/512640/ (example of Admin page)]. Then return to the review page [https://addons.mozilla.org/en-US/editors/review/octotree (example of review page)] then submit your new review.<br />
<br />
==Reviewing XPTs==<br />
When you see a .xpt in a file do not worry about it, it is just definitions. What you need to review, is the javascript in the file backing those function definitions.<br />
<br />
==Reviewing Addons with Binary Components==<br />
Unlike with addons with minified/obfuscated code, we do not request the reproduction steps, and then reproduce it. We simply review the attached files, and then run all the binary files through a virus scan on the [http://www.virustotal.com Virus Total Website]. If you are prompted, "a previous scan exists", make sure to do a new scan, as the old one probably is no longer applicable.<br />
<br />
==Canned Emails==<br />
* How to make my unlisted addon - listed?<br />
Hi there,<br />
Unlisted addons are automatically approved without review, therefore we do not allow a quick way to jump to listed status.<br />
<br />
To go from unlisted to listed. You have two options:<br />
1) Change the addon id in install.rdf and create a brand new listing from https://addons.mozilla.org/developers/addon/submit/agreement<br />
2) Keep the same addon id, but delete the listing, then email an admin (amo-admins@mozilla.org) to delete that id from the database, then create new listing<br />
<br />
The benefit of option 1, you can link in the "notes for reviewers" to the old listing so the reviewer can do a diff of the code. Otherwise they will do a brand new review which can take time.<br />
<br />
Here is some more information on the subject - https://developer.mozilla.org/en-US/Add-ons/Distribution<br />
<br />
Thank you<br />
<br />
* How to update users of my unlisted addon?<br />
Hi,<br />
Please see https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#updateURL and https://developer.mozilla.org/en-US/docs/Extension_Versioning,_Update_and_Compatibility<br />
<br />
Thank you<br />
<br />
* No need for sources attachment<br />
Hi,<br />
This is a note. Please do not attach source files unless it is the human readable version of your minified/obfuscated/binary code. Third party libraries do not needed source attachments, you just need to provide us the URL to the location of its repository/commit/version/zip.<br />
<br />
I have removed your addon from the admin queue so it does not unnecessarily go through this extended process.<br />
<br />
Thank you<br />
<br />
* How to provide sources for minimized/obfuscated 3rd party libraries<br />
Dear Author,<br />
Please provide links to each of the minimized/obfuscated 3rd party library contained in your addon. For example if you included "jquery_slipbhover.min.js" you would link us to the exact commit, of the version you use. This commit should contain a bit exact version of the minified version in your addon, and also the human readable version. If no repository exists, then you would link us to the zip file, or etc.<br />
<br />
Another example: If you include jQuery UI custom build, you would tell me go here - http://jqueryui.com/download/ - and then you would tell me what options to use to build that.<br />
<br />
Please update this information in the "Notes for Reviewers" section (which is version specific), or in the "Whiteboard" section, and then let me know by replying to this email so I may continue.<br />
<br />
Thank you<br />
<br />
* If they threaten to ditch Firefox, you should make clear to them we aren't acting due to that comment<br />
Hi,<br />
<br />
[reply to their non-threat parts of their email]<br />
<br />
I am not very happy about the threat that you want to ask your users to switch browsers. Not because of the browser switch itself, but because you are using this as an argument to persuade me into accepting the review. The add-on review process is not guided by business decisions or number of active users, we want to make sure users are safe and look at the code to decide on this. I would appreciate if you could refrain from making such statements in the future.<br />
<br />
Thank you<br />
<br />
==Install Methods for Popular Techniques==<br />
* Closure Compiler<br />
# Do not use binary if they supply it, ask them for the version, and then get the original/unmodified version from here [https://github.com/google/closure-compiler/wiki/Binary-Downloads Github :: google - closure-compiler - Binary Downloads]<br />
* YUI Compressor<br />
# Do not use binary if they supply it, ask them for version, and get original/unmodified from [https://github.com/yui/yuicompressor/releases/ Github :: yui - Yuicompressor Releases]<br />
* Installing Grunt<br />
# Install node (comes with npm)<br />
# From command line run `npm install -g grunt` then run `npm install -g grunt-cli`<br />
* Installing Gulp<br />
# Install node (comes with npm)<br />
# From command line run `npm install -g grunt` then run `npm install -g gulp`<br />
* Changing Node/NPM Version<br />
* Windows - Use [https://github.com/coreybutler/nvm-windows nvm-windows] or [https://github.com/marcelklehr/nodist nodist] npm packages<br />
* Unix Based - Use [https://github.com/creationix/nvm nvm] npm package<br />
<br />
==Reviewing Addon with Node/NPM Based Build Tools==<br />
# Sometimes the version of node and the version of npm make a difference. Make sure they provide that.<br />
# Review the package.json, ensure that the scripts pointed too (usually on npm website or github repositories) are safe. Most are popular stuff<br />
# `cd` into the directory containing the `package.json`<br />
# Type `npm install`. You may need `sudo` on Unix based, or on Windows you should have right clicked, and ran Command Prompt as Administrator<br />
# Then the developer should provide you with what to run, you can tell by looking at their script, usually typing "grunt" or "gulp" does the trick</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Contribute/Triage&diff=1151703Add-ons/Contribute/Triage2016-10-18T16:55:51Z<p>Jorge.villalobos: Reverting link; there's one already</p>
<hr />
<div>= Purpose of Meeting =<br />
A bi-weekly triage session to accomplish these community goals:<br />
* '''WebExtensions APIs''': <br />
** Transparency: Decide whether APIs tagged "design-decision-needed" are "design-decision-approved" or "wontfix" to ensure transparency for the direction of WebExtensions. <br />
** Community participation: Give guidance on and assign advisors to APIs marked "design-decision-approved" to make it easier for contributors to get involved.<br />
* '''Good First Bugs''': Ensure add-on bugs marked "Good First Bug" are fresh and updated for new contributors. If you are a new contributor who wants to write code for add-on related projects, please [https://wiki.mozilla.org/Add-ons/Contribute/Code start here].<br />
<br />
=Next Meeting=<br />
Next meeting is Oct 18, 2016<br />
<br />
=Details & How to Join=<br />
* Time: Every other [http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 Tuesday at 10am Pacific]<br />
* Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU<br />
*IRC: [https://wiki.mozilla.org/IRC irc.mozilla.org], #Addons channel<br />
<br />
=WebExtensions APIs Triage=<br />
==Triage Guidelines==<br />
Bugs marked "design-decision-needed" should be:<br />
*Tagged with "design-decision-approved" or "wontfix" (including reason)<br />
<br />
Bugs marked "design-decision-approved" should have:<br />
*Clear description of the API and suggested implementation if possible<br />
*Priority & impact<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code#Develop_Web_Extensions_APIs onboarding process]<br />
*Advisor<br />
<br />
==Bug Queries==<br />
====="design-decision-needed"=====<br />
These are determined from the Monday WebExtensions triage. They are APIs we [https://mzl.la/2edmiid need more discussion] on.<br />
<br />
====="design-decision-approved"=====<br />
These are APIs we would [https://mzl.la/2dVs5Ys like to have]. They should meet the triage criteria listed above.<br />
<br />
=Good First Bugs Triage=<br />
==Triage Guidelines==<br />
All "Good First Bugs" should have:<br />
*Clear description of the issue<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code onboarding process]<br />
*Mentor<br />
<br />
==Bug Queries==<br />
=====addons-server "Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=good%20first%20bug This is the query] contributors see. We should spot-check them to ensure they are properly triaged.<br />
<br />
=====addons-server "Maybe Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=maybe%20good%20first%20bug These are tagged "Maybe Good First Bugs"]. We triage these and change the tag to "Good First Bugs" if determined to be good for new contributors.<br />
<br />
=====WebExtensions Bugs on Bugzilla=====<br />
*These are WebExtensions bugs that [https://mzl.la/2a2PMIw don't have a mentor]<br />
*These are WebExtensions bugs that [https://mzl.la/2afcm4h have an assignee but haven't been commented on for 3 weeks]<br />
<br />
=====Add-ons Manager Bugs on Bugzilla=====<br />
*These are Add-ons Manager bugs that [https://mzl.la/2acSvC0 don't have a mentor]<br />
*These are Add-ons Manager bugs that [https://mzl.la/2ajmxp8 have an assignee but haven't been commented on for 3 weeks]<br />
<br />
= Archive =<br />
=====2016=====<br />
[https://docs.google.com/document/d/1BDIbINMGgjoWlZxHmw-MnLm3HEqB38oUNTJUPAippGo/edit Oct 4, 2016]<br /><br />
[https://docs.google.com/document/d/1gABxxstInPy5XMsmoYMhZBMsLGFWNsgWMhgjUlt7-o8/edit Sept 20, 2016]<br /><br />
[https://docs.google.com/document/d/14cqCfgbyGoBXe7ttho0L3mIe4FcSSlzHH3L4fBFnLzA/edit Sept 6, 2016]<br /><br />
[https://docs.google.com/document/d/1GDpdcO1EHefRL3B5p5g1emdp_lY-YFWjwXv8YG1EgWo/edit August 23, 2016]<br /><br />
[https://docs.google.com/document/d/1rZvIfFILAHozLGTrg5C7Q7lXyEZ2gfMDw7cVkEo34io/edit August 9, 2016]<br /><br />
[https://docs.google.com/document/d/1A5hKaon2Z3nSCQc9ToYTOjr2cIpmmeZmu9EnbhVjHd0/edit July 26, 2016]<br /><br />
[https://docs.google.com/document/d/18wCqoUzNYshOWDjuJjePFivb4T5nD0WlFE06NKn3YQ0/edit July 12, 2016]<br /><br />
[https://docs.google.com/document/d/1uBo-WVFP2v-dyeYyDtfPD9ipN8JeIw7sCag4CYonQqY/edit# June 28, 2016]<br /><br />
[https://docs.google.com/document/d/1lYqcEWaktMXPmAefRB9PW9iSBM95rlVKFOO-vFRewdE/edit May 31, 2016]<br /><br />
[https://docs.google.com/document/d/1Bq7gTVhsGfTW58A9MUurruu5jc2w5OHSeaoRbmWRQV4/edit May 17, 2016]<br /><br />
[https://docs.google.com/document/d/1EkZXtIx7TkQxnFn_2ei3SR7j9xeDVc1WSl3suY2n8RU/edit April 28, 2016]<br /><br />
[https://docs.google.com/document/d/13yPW-ojA_jzXUe7_fxDvYQavsr5yEHZzHXXCMcuZgCA/edit April 14, 2016]<br /><br />
[https://docs.google.com/document/d/1hSABd9dd8UktXGJuf0iXn_8Fpuz09VEqkxrxMY_AvZw/edit Mar 31, 2016]<br /><br />
[https://docs.google.com/document/d/1ss0i_zAZDytsyBnMGF1gdRI6LjRWqvQS9Q0ueKzQV1Q/edit Mar 3, 2016]<br /><br />
[https://docs.google.com/document/d/1GkHWjHRDcUd7WD2BFF-6zhdyce4lK8qMX23O6C0eRIA/edit Feb 18, 2016]<br /><br />
[https://docs.google.com/document/d/1cM2JIIgw1i7TJe3oOojCtJvEhJoBGdHgNvjS2hRfBcw/edit Feb 4, 2016]<br /> <br />
[https://docs.google.com/document/d/1OZVV_HVXWAY-1u-nPhb4MrXOsycVFbXkXGEhhTomoaM/edit Jan 21, 2016]<br /><br />
[https://docs.google.com/document/d/1GwqhWsSsBp5vfLW7-5Di8_CzIfepwK9YVZAnQuLxK9I/edit Jan 7, 2016]<br />
<br />
=====2015=====<br />
[https://docs.google.com/document/d/18Csoja50IhnjqraFzxEYyVIJp-j79GLO2gCrvTSYHUI/edit Nov. 19, 2015]<br /><br />
[https://docs.google.com/document/d/1gbhL0S4amQ447ddIX7mEZsSaGoiFt8fTw22FKe_GbIo/edit Oct. 29, 2015]<br /><br />
[https://docs.google.com/document/d/1EoLSXHKCqJzTatj6CLLpjomwXnN5zUOA897brO_1aJQ/edit Oct. 15, 2015]<br />
<br />
=====Aug - Oct 2015=====<br />
https://drive.google.com/drive/folders/0B2aDMRMZ7uzvYzA4Wm1VYVhvemM</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Contribute/Triage&diff=1151702Add-ons/Contribute/Triage2016-10-18T16:54:34Z<p>Jorge.villalobos: Added triage link</p>
<hr />
<div>= Purpose of Meeting =<br />
A bi-weekly triage session to accomplish these community goals:<br />
* '''WebExtensions APIs''': <br />
** Transparency: Decide whether APIs tagged "design-decision-needed" are "design-decision-approved" or "wontfix" to ensure transparency for the direction of WebExtensions. <br />
** Community participation: Give guidance on and assign advisors to APIs marked "design-decision-approved" to make it easier for contributors to get involved.<br />
* '''Good First Bugs''': Ensure add-on bugs marked "Good First Bug" are fresh and updated for new contributors. If you are a new contributor who wants to write code for add-on related projects, please [https://wiki.mozilla.org/Add-ons/Contribute/Code start here].<br />
<br />
=Next Meeting=<br />
Next meeting is Oct 18, 2016<br />
<br />
=Details & How to Join=<br />
* Time: Every other [http://www.worldtimebuddy.com/?qm=1&lid=1850147,5375480,2643743,1277333&h=5375480&date=2016-10-18&sln=10-11 Tuesday at 10am Pacific]<br />
* Vidyo: ACE room - https://v.mozilla.com/flex.html?roomdirect.html&key=63EeximucvH3QIFBKbpuBCVBAQU<br />
*IRC: [https://wiki.mozilla.org/IRC irc.mozilla.org], #Addons channel<br />
<br />
=WebExtensions APIs Triage=<br />
==Triage Guidelines==<br />
[https://bugzilla.mozilla.org/buglist.cgi?order=Bug%20Number&list_id=13269690&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=design-decision-needed&component=WebExtensions%3A%20Android&component=WebExtensions%3A%20Compatibility&component=WebExtensions%3A%20Developer%20tools&component=WebExtensions%3A%20Experiments&component=WebExtensions%3A%20Frontend&component=WebExtensions%3A%20General&component=WebExtensions%3A%20Request%20Handling&component=WebExtensions%3A%20Untriaged&product=Toolkit Bugs marked "design-decision-needed"] should be:<br />
*Tagged with "design-decision-approved" or "wontfix" (including reason)<br />
<br />
Bugs marked "design-decision-approved" should have:<br />
*Clear description of the API and suggested implementation if possible<br />
*Priority & impact<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code#Develop_Web_Extensions_APIs onboarding process]<br />
*Advisor<br />
<br />
==Bug Queries==<br />
====="design-decision-needed"=====<br />
These are determined from the Monday WebExtensions triage. They are APIs we [https://mzl.la/2edmiid need more discussion] on.<br />
<br />
====="design-decision-approved"=====<br />
These are APIs we would [https://mzl.la/2dVs5Ys like to have]. They should meet the triage criteria listed above.<br />
<br />
=Good First Bugs Triage=<br />
==Triage Guidelines==<br />
All "Good First Bugs" should have:<br />
*Clear description of the issue<br />
*Link to [https://wiki.mozilla.org/Add-ons/Contribute/Code onboarding process]<br />
*Mentor<br />
<br />
==Bug Queries==<br />
=====addons-server "Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=good%20first%20bug This is the query] contributors see. We should spot-check them to ensure they are properly triaged.<br />
<br />
=====addons-server "Maybe Good First Bugs" on GitHub=====<br />
[https://waffle.io/mozilla/addons?label=maybe%20good%20first%20bug These are tagged "Maybe Good First Bugs"]. We triage these and change the tag to "Good First Bugs" if determined to be good for new contributors.<br />
<br />
=====WebExtensions Bugs on Bugzilla=====<br />
*These are WebExtensions bugs that [https://mzl.la/2a2PMIw don't have a mentor]<br />
*These are WebExtensions bugs that [https://mzl.la/2afcm4h have an assignee but haven't been commented on for 3 weeks]<br />
<br />
=====Add-ons Manager Bugs on Bugzilla=====<br />
*These are Add-ons Manager bugs that [https://mzl.la/2acSvC0 don't have a mentor]<br />
*These are Add-ons Manager bugs that [https://mzl.la/2ajmxp8 have an assignee but haven't been commented on for 3 weeks]<br />
<br />
= Archive =<br />
=====2016=====<br />
[https://docs.google.com/document/d/1BDIbINMGgjoWlZxHmw-MnLm3HEqB38oUNTJUPAippGo/edit Oct 4, 2016]<br /><br />
[https://docs.google.com/document/d/1gABxxstInPy5XMsmoYMhZBMsLGFWNsgWMhgjUlt7-o8/edit Sept 20, 2016]<br /><br />
[https://docs.google.com/document/d/14cqCfgbyGoBXe7ttho0L3mIe4FcSSlzHH3L4fBFnLzA/edit Sept 6, 2016]<br /><br />
[https://docs.google.com/document/d/1GDpdcO1EHefRL3B5p5g1emdp_lY-YFWjwXv8YG1EgWo/edit August 23, 2016]<br /><br />
[https://docs.google.com/document/d/1rZvIfFILAHozLGTrg5C7Q7lXyEZ2gfMDw7cVkEo34io/edit August 9, 2016]<br /><br />
[https://docs.google.com/document/d/1A5hKaon2Z3nSCQc9ToYTOjr2cIpmmeZmu9EnbhVjHd0/edit July 26, 2016]<br /><br />
[https://docs.google.com/document/d/18wCqoUzNYshOWDjuJjePFivb4T5nD0WlFE06NKn3YQ0/edit July 12, 2016]<br /><br />
[https://docs.google.com/document/d/1uBo-WVFP2v-dyeYyDtfPD9ipN8JeIw7sCag4CYonQqY/edit# June 28, 2016]<br /><br />
[https://docs.google.com/document/d/1lYqcEWaktMXPmAefRB9PW9iSBM95rlVKFOO-vFRewdE/edit May 31, 2016]<br /><br />
[https://docs.google.com/document/d/1Bq7gTVhsGfTW58A9MUurruu5jc2w5OHSeaoRbmWRQV4/edit May 17, 2016]<br /><br />
[https://docs.google.com/document/d/1EkZXtIx7TkQxnFn_2ei3SR7j9xeDVc1WSl3suY2n8RU/edit April 28, 2016]<br /><br />
[https://docs.google.com/document/d/13yPW-ojA_jzXUe7_fxDvYQavsr5yEHZzHXXCMcuZgCA/edit April 14, 2016]<br /><br />
[https://docs.google.com/document/d/1hSABd9dd8UktXGJuf0iXn_8Fpuz09VEqkxrxMY_AvZw/edit Mar 31, 2016]<br /><br />
[https://docs.google.com/document/d/1ss0i_zAZDytsyBnMGF1gdRI6LjRWqvQS9Q0ueKzQV1Q/edit Mar 3, 2016]<br /><br />
[https://docs.google.com/document/d/1GkHWjHRDcUd7WD2BFF-6zhdyce4lK8qMX23O6C0eRIA/edit Feb 18, 2016]<br /><br />
[https://docs.google.com/document/d/1cM2JIIgw1i7TJe3oOojCtJvEhJoBGdHgNvjS2hRfBcw/edit Feb 4, 2016]<br /> <br />
[https://docs.google.com/document/d/1OZVV_HVXWAY-1u-nPhb4MrXOsycVFbXkXGEhhTomoaM/edit Jan 21, 2016]<br /><br />
[https://docs.google.com/document/d/1GwqhWsSsBp5vfLW7-5Di8_CzIfepwK9YVZAnQuLxK9I/edit Jan 7, 2016]<br />
<br />
=====2015=====<br />
[https://docs.google.com/document/d/18Csoja50IhnjqraFzxEYyVIJp-j79GLO2gCrvTSYHUI/edit Nov. 19, 2015]<br /><br />
[https://docs.google.com/document/d/1gbhL0S4amQ447ddIX7mEZsSaGoiFt8fTw22FKe_GbIo/edit Oct. 29, 2015]<br /><br />
[https://docs.google.com/document/d/1EoLSXHKCqJzTatj6CLLpjomwXnN5zUOA897brO_1aJQ/edit Oct. 15, 2015]<br />
<br />
=====Aug - Oct 2015=====<br />
https://drive.google.com/drive/folders/0B2aDMRMZ7uzvYzA4Wm1VYVhvemM</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Extension_Signing&diff=1151385Add-ons/Extension Signing2016-10-14T17:58:24Z<p>Jorge.villalobos: Changed reference to discontinued newsgroup</p>
<hr />
<div>Mozilla now requires all extensions to be signed by Mozilla in order for them to be installable in Release and Beta versions of Firefox. Signing will be done through [http://addons.mozilla.org/ addons.mozilla.org (AMO)] and will be mandatory for all extensions, regardless of where they are hosted.<br />
<br />
== Documentation ==<br />
* [http://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/ Introducing Extension Signing], Add-ons Blog.<br />
* [https://blog.mozilla.org/addons/2015/04/15/the-case-for-extension-signing/ The Case for Extension Signing], Add-ons Blog.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=signed-addons Main tracking bug].<br />
<br />
== Timeline ==<br />
Check the [[RapidRelease/Calendar|Firefox Release Calendar]] for specific dates. The following timelines are for Desktop:<br />
<br />
* '''Firefox 40-42''': Firefox warns about signatures but doesn't enforce them.<br />
* '''Firefox 43''': Firefox enforces the use of signatures by default, but has a preference that allows signature enforcement to be disabled (''xpinstall.signatures.required'' in about:config).<br />
* '''Firefox 48''': (Pushed from Firefox 46). Release and Beta versions of Firefox for Desktop will not allow unsigned extensions to be installed, with no override. Firefox for Android will enforce add-on signing, and will retain a preference &mdash; which will be removed in a future release &mdash; to allow the user to disable signing enforcement.<br />
<br />
The first ESR version to include signing support will be the Firefox ESR 52 release. <br />
<br />
All Firefox extensions - for Desktop and Android - on AMO that have passed review are now signed.<br />
<br />
For unlisted (non-AMO) add-ons, submission and signing is active through [https://addons.mozilla.org AMO], and there is a [https://blog.mozilla.org/addons/2015/11/20/signing-api-now-available/ Signing API available] for automated submission and retrieval of unlisted addons.<br />
<br />
== Unbranded Builds ==<br />
<br />
Unbranded builds are available from the continuous integration builds on archive.mozilla.org. Links to the latest beta and release builds, as well as the root directories for those treeherder builds are below, and subdirectories are named from the epoch timestamp of when the build was generated.<br />
<br />
=== Latest Builds ===<br />
<br />
'''Release builds''' <br />
<br />
Latest release (Firefox 49.0.1 - [https://hg.mozilla.org/releases/mozilla-release/rev/2d931a5eaf8a changeset 2d931a5eaf8a]) builds:<br />
<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/1474569299/firefox-49.0.1.en-US.linux-x86_64-add-on-devel.tar.bz2 Linux Installer] ([https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/1474569299/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/1474569299/firefox-49.0.1.en-US.mac64-add-on-devel.dmg Mac OSX Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/1474569299/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/1474569299/firefox-49.0.1.en-US.win32-add-on-devel.installer.exe Windows 32-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/1474569299/ build directory]) <br />
*[http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/1474569299/firefox-49.0.1.en-US.win64-add-on-devel.installer.exe Windows 64-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/1474569299/ build directory]) <br />
<br />
'''Beta builds'''<br />
<br />
Latest beta (50.0b1 - [https://hg.mozilla.org/releases/mozilla-beta/rev/91faf7ec36cd changeset 91faf7ec36cd]) builds:<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/1474412235/firefox-50.0.en-US.linux-x86_64-add-on-devel.tar.bz2 Linux Installer] ([https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/1474412235/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/1474412235/firefox-50.0.en-US.mac64-add-on-devel.dmg Mac OSX Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/1474412235/ build directory]) <br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/1474412235/firefox-50.0.en-US.win32-add-on-devel.installer.exe Windows 32-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/1474412235/ build directory]) <br />
*[http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/1474412235/firefox-50.0.en-US.win64-add-on-devel.installer.exe Windows 64-bit Installer] ([http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/1474412235/ build directory])<br />
<br />
=== Treeherder Root Directories ===<br />
<br />
'''Release'''<br />
<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-linux64-add-on-devel/ Linux]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-macosx64-add-on-devel/ Mac OSX]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32-add-on-devel/ Windows 32-bit]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/ Windows 64-bit]<br />
<br />
'''Beta'''<br />
<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-linux64-add-on-devel/ Linux]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-macosx64-add-on-devel/ OSX]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win32-add-on-devel/ Windows 32-bit]<br />
* [http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-beta-win64-add-on-devel/ Windows 64-bit]<br />
<br />
== FAQ ==<br />
* Which add-on types will need to be signed?<br />
** Only extensions ([https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#type type 2] in install.rdf)--this includes WebExtensions. Themes, dictionaries, language packs, and plugins don't need to be signed.<br />
<br />
* Will other applications like Thunderbird, Seamonkey, Palemoon, etc. require extensions to be signed?<br />
** The leaders of each of those projects will decide if they want to enforce signing, keep it as a setting, or deactivate it by default. We haven't heard about any other applications planning to support this.<br />
<br />
* Will signed extensions work on other applications or older versions of Firefox?<br />
** Yes, the signature system is built on top of the [https://developer.mozilla.org/en-US/docs/Signing_a_XPI existing add-on signing feature], which has been supported in Firefox and other applications.<br />
<br />
* Will there be a setting or other overrides to disable signature checks?<br />
** Firefox Release and Beta versions will not have any way to disable signature checks. Signature checks can be disabled in other versions, as described in detail below.<br />
<br />
* What are my options if I want to install unsigned extensions in Firefox?<br />
** The [https://www.mozilla.org/firefox/developer/ Developer Edition] and [https://nightly.mozilla.org/ Nightly] versions of Firefox will have a setting to disable signature enforcement. There are also be special [https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds unbranded versions of Release and Beta] that will have this setting (see , so that add-on developers can work on their add-ons without having to sign every build. To disable signature checks, you will need to set the <code>xpinstall.signatures.required</code> preference to "false".<br />
*** type <code>about:config</code> into the URL bar in Firefox<br />
*** in the Search box type <code>xpinstall.signatures.required</code><br />
*** double-click the preference, or right-click and selected "Toggle", to set it to <code>false</code>.<br />
<br />
* How will the [[Add-ons/Extension_Signing#Unbranded_Builds|unbranded versions of Firefox]] work?<br />
** They work just like Firefox, with two differences: they will have a setting to disable mandatory signature checks, and they will not have the Firefox name and logo (instead using a generic name and logo). These builds are available in the en-US locale only.<br />
<br />
* What about private add-ons used in enterprise environments?<br />
** The ESR release will support signing starting with version 45-based releases. Signing enforcement will be enabled by default in these releases, and enforcement can be disabled using the <code>xpinstall.signatures.required</code> preference.<br />
<br />
* How do I get my add-ons signed if they are hosted on addons.mozilla.org (AMO)?<br />
** No action is required. We automatically signed reviewed versions of all add-ons currently hosted on AMO. All new versions will be signed automatically after they pass review. <br />
<br />
* How do I get my add-ons signed if they are not hosted on addons.mozilla.org (AMO)?<br />
** You will need to create an AMO account and submit your add-on. There will be an option where you indicate the add-on won't be listed on AMO, and you'll be able to submit your add-on files without having them published on the site. Please read the [https://developer.mozilla.org/en-US/Add-ons/Distribution Distribution Policy] for more details.<br />
** You can also use the [https://developer.mozilla.org/en-US/Add-ons/SDK/Tools/jpm#jpm_sign jpm sign] command to generate a signed XPI that can be self-hosted.<br />
** There is an [http://olympia.readthedocs.org/en/latest/topics/api/signing.html API you can use] for signing.<br />
<br />
* How does the signing process work for unlisted add-ons?<br />
** For unlisted add-ons, files submitted for signing will go through an automated review process. If they pass this review, they are automatically signed and a download link is sent back to the developer. This process should normally take seconds. If the file doesn't pass review, the developer will have the option to request a manual review, which should take less than two days. This is not the same process that currently applies to AMO add-ons, which has been typically slower.<br />
** There is an [http://olympia.readthedocs.org/en/latest/topics/api/signing.html API you can use] for signing.<br />
<br />
* What about [https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Maintenance#How_do_I_submit_a_Beta_add-on.3F Beta versions on AMO]? Will they be reviewed and signed?<br />
** Yes. Beta versions will be treated like non-AMO add-ons. They will be automatically validated and signed if they pass validation.<br />
<br />
* Will I need to sign the custom version of an existing add-on I created with my own code changes, locale additions, etc.?<br />
** If you use it on Release or Beta, yes. You will also need to change the add-on ID in order to submit it for signing.<br />
<br />
* Is this a way for Mozilla to censor add-ons they don't like, enforce copyright, government demands, etc.?<br />
** No, the purpose of this is to protect users from malicious add-ons. We have [https://developer.mozilla.org/en-US/Add-ons/Add-on_guidelines clear guidelines] for when it is appropriate to blocklist an add-on and have refused multiple times to block for other reasons.<br />
<br />
* Will there be an upload and signing API so I don't have to manually upload each new version of the add-on?<br />
** Yes. The [http://olympia.readthedocs.org/en/latest/topics/api/signing.html signing API is documented here].<br />
<br />
* Will this protect users against all forms of add-on malware?<br />
** No, there is no perfect solution for this. Fighting malware requires defenses on many levels: operating system,, application, user, and even industry. Extension signing is a big step in protecting Firefox against malicious add-ons, but there is much more to do in other fronts to ensure the best experience for our users.<br />
<br />
== Feedback and Questions ==<br />
For questions about signing, you can use [https://developer.mozilla.org/en-US/Add-ons#Contact_us any of our communication channels].</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Reviewers&diff=1151335Add-ons/Reviewers2016-10-13T23:19:04Z<p>Jorge.villalobos: Centered photo</p>
<hr />
<div>__NOTOC__ <br />
== Introduction ==<br />
[https://mozillians.org/en-US/group/249-amo-editors The AMO Reviewer Team] (also known as AMO Editors) is a Mozilla community made up of add-on developers dedicated to the security and reliability of all add-ons for Mozilla applications. They review new and updated add-ons as part of the add-on review process, and decide if they are appropriate for publication. They do so according to established [https://developer.mozilla.org/Mozilla/Add-ons/AMO/Policy/Reviews Review Policies].<br />
<br />
== Join us ==<br />
<br />
Add-ons are an integral part of what makes Firefox innovative, useful, and fun--and AMO Reviewers help keep it that way! As a key member of the Mozilla community, editors enjoy these privileges and perks:<br />
<br />
* <b>[https://wiki.mozilla.org/Add-ons/Reviewers/Points_and_Incentives Earn gear:]</b> accumulate points to earn gear, from t-shirts to Android tablets<br />
* <b>Review privileges:</b> full reviews and updates of add-ons and apps authored by reviewers are fast-tracked<br />
* <b>Invitations to events:</b> top reviewers are regularly invited to Mozilla [[Coincidental_work_weeks|events]] worldwide<br />
[[File:Mozlondon-addons.jpg|700px|center||Add-ons Meetup in London, June 2016]]<br />
<br />
<br />
[[Add-ons/Reviewers/Applying|Join us today!]]<br />
<br />
== Contact us ==<br />
<br />
You can contact us at amo-editors at mozilla.org and the [irc://irc.mozilla.org/amo-editors #amo-editors] IRC channel (irc.mozilla.org). We also monitor the [https://discourse.mozilla-community.org/c/add-ons Add-ons Forum].<br />
<br />
== Meetups ==<br />
*Reviewer meetup at Mozlando 2015: [https://blog.mozilla.org/addons/files/2016/02/DSC_4087-e1454965785705.jpg Photo]<br />
*Reviewer meetup at MozFest 2014 in London: [https://www.flickr.com/photos/mozamoteam/sets/72157648969050906 Photos] and [https://mozamy.wordpress.com/2014/11/04/add-on-and-app-reviewer-meetup-at-mozfest-2014/ blog post]<br />
*Reviewer meetup at Summit 2013 in Brussels: [https://www.flickr.com/photos/mozamoteam/sets/72157655324482831 Photos]<br />
*Reviewer meetup MozCamp EU 2012 in Warsaw: [http://www.flickr.com/photos/mozamoteam/tags/amoeditormeetup/ Photos] and [https://blog.mozilla.org/addons/2012/09/17/mozcamp-2012-wrap-up/ blog post]<br />
<br />
== Resources ==<br />
<br />
*[[Add-ons/Reviewers/Applying|How to become a reviewer]] <br />
*[https://developer.mozilla.org/en-US/Add-ons/AMO/Policy Add-on Policies]<br />
*[[Add-ons/Reviewers/Guide|AMO Reviewer Guide]]</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=Add-ons/Reviewers&diff=1151334Add-ons/Reviewers2016-10-13T23:18:04Z<p>Jorge.villalobos: Added photo to reviewer page</p>
<hr />
<div>__NOTOC__ <br />
== Introduction ==<br />
[https://mozillians.org/en-US/group/249-amo-editors The AMO Reviewer Team] (also known as AMO Editors) is a Mozilla community made up of add-on developers dedicated to the security and reliability of all add-ons for Mozilla applications. They review new and updated add-ons as part of the add-on review process, and decide if they are appropriate for publication. They do so according to established [https://developer.mozilla.org/Mozilla/Add-ons/AMO/Policy/Reviews Review Policies].<br />
<br />
== Join us ==<br />
<br />
Add-ons are an integral part of what makes Firefox innovative, useful, and fun--and AMO Reviewers help keep it that way! As a key member of the Mozilla community, editors enjoy these privileges and perks:<br />
<br />
* <b>[https://wiki.mozilla.org/Add-ons/Reviewers/Points_and_Incentives Earn gear:]</b> accumulate points to earn gear, from t-shirts to Android tablets<br />
* <b>Review privileges:</b> full reviews and updates of add-ons and apps authored by reviewers are fast-tracked<br />
* <b>Invitations to events:</b> top reviewers are regularly invited to Mozilla [[Coincidental_work_weeks|events]] worldwide<br />
[[File:Mozlondon-addons.jpg|700px|||Add-ons Meetup in London, June 2016]]<br />
<br />
<br />
[[Add-ons/Reviewers/Applying|Join us today!]]<br />
<br />
== Contact us ==<br />
<br />
You can contact us at amo-editors at mozilla.org and the [irc://irc.mozilla.org/amo-editors #amo-editors] IRC channel (irc.mozilla.org). We also monitor the [https://discourse.mozilla-community.org/c/add-ons Add-ons Forum].<br />
<br />
== Meetups ==<br />
*Reviewer meetup at Mozlando 2015: [https://blog.mozilla.org/addons/files/2016/02/DSC_4087-e1454965785705.jpg Photo]<br />
*Reviewer meetup at MozFest 2014 in London: [https://www.flickr.com/photos/mozamoteam/sets/72157648969050906 Photos] and [https://mozamy.wordpress.com/2014/11/04/add-on-and-app-reviewer-meetup-at-mozfest-2014/ blog post]<br />
*Reviewer meetup at Summit 2013 in Brussels: [https://www.flickr.com/photos/mozamoteam/sets/72157655324482831 Photos]<br />
*Reviewer meetup MozCamp EU 2012 in Warsaw: [http://www.flickr.com/photos/mozamoteam/tags/amoeditormeetup/ Photos] and [https://blog.mozilla.org/addons/2012/09/17/mozcamp-2012-wrap-up/ blog post]<br />
<br />
== Resources ==<br />
<br />
*[[Add-ons/Reviewers/Applying|How to become a reviewer]] <br />
*[https://developer.mozilla.org/en-US/Add-ons/AMO/Policy Add-on Policies]<br />
*[[Add-ons/Reviewers/Guide|AMO Reviewer Guide]]</div>Jorge.villaloboshttps://wiki.mozilla.org/index.php?title=File:Mozlondon-addons.jpg&diff=1151333File:Mozlondon-addons.jpg2016-10-13T23:15:09Z<p>Jorge.villalobos: Add-ons Meetup in London, June 2016.</p>
<hr />
<div>Add-ons Meetup in London, June 2016.</div>Jorge.villalobos