Revision as of 19:08, 16 October 2008

Goals

Revive the addons compatibility dashboard
- Something like http://people.mozilla.com/~polvi/threedom/status-bars.html to track full list of addons sorted by usage popularity and identify current compat version. get it to update every night.
Set up tracking bugs for the top 50-60 addons to track progress on contacting, updating, and feedback about how things are going with getting compatible. ala https://bugzilla.mozilla.org/showdependencytree.cgi?id=364745&hide_resolved=0
Figure out plan for scaling review queue if/when it gets flooded in Nov/Dec/Jan
Try and get a few addon developers involved early to give feedback on coverage and quality of the documentation. Target Web Developer Addons since these kind of addons also help to increase use of the beta releases if they are available at beta release time.

Send out emails to developers and editors
Post to blog and newsgroup detailed information about what is changing and how to update
Out reach to press or on-line awareness like http://lifehacker.com/393559/firefox-3-add+on-compatibility-report
Develop communication around how and when to flip version compability number. e.g like http://developer.mozilla.org/devnews/index.php/2008/03/24/firefox-add-on-compatibility-plan-for-addonsmozillaorg/

@@ Line 15: / Line 15: @@
 * Set up tracking bugs for the top 50-60 addons to track progress on contacting, updating, and feedback about how things are going with getting compatible.  ala https://bugzilla.mozilla.org/showdependencytree.cgi?id=364745&hide_resolved=0
 * Figure out plan for scaling review queue if/when it gets flooded in Nov/Dec/Jan
+* Try and get a few addon developers involved early to give feedback on coverage and quality of the documentation.  Target Web Developer Addons since these kind of addons also help to increase use of the beta releases if they are available at beta release time.
 == Outreach ==