Add-ons/developer/communication: Difference between revisions
< Add-ons
Jump to navigation
Jump to search
(comms plan) |
m (posts) |
||
| Line 9: | Line 9: | ||
=AMO Blog Editorial Calendar= | =AMO Blog Editorial Calendar= | ||
=Relevant Blog Posts= | |||
==Signing== | |||
*[https://blog.mozilla.org/addons/2015/12/18/signing-firefox-add-ons-with-jpm-sign/ Signing Firefox add-ons with jpm sign] | |||
*[https://blog.mozilla.org/addons/2015/11/20/signing-api-now-available/ Signing API now available] | |||
==Multiprocess (e10s) Firefox Compatibility== | |||
*[https://blog.mozilla.org/addons/2015/11/23/test-your-add-ons-for-multi-process-firefox-compatibility/ Test your add-ons for Multi-process Firefox compatibility] | |||
Revision as of 00:10, 20 January 2016
Add-on Developer Communications Plan
There are a lot of changes coming up for add-on development in 2016. Here is the communication plan to help ease transitions for add-on developers.
Timeline
Developer Profiles
The first step of this plan is to compile a list of developer profiles. For each group, figure out how they will be affected, what their migration paths are, what we should communicate to them, and how. This is a collaborative process; the document for collecting these profiles is here.