Update:FutureFeatures: Difference between revisions

 
(3 intermediate revisions by 2 users not shown)
Line 61: Line 61:
* Addon Upload API (e.g. for MozDev)
* Addon Upload API (e.g. for MozDev)
* Enable optional Google Analytics for addons authors
* Enable optional Google Analytics for addons authors
* Firefox 3 compatibility/outreach [Polvi is managing]
* Revitalizing Community
* Revitalizing Community
* Developer leaderboard/Amazon-like ranking
* Developer leaderboard/Amazon-like ranking
Line 69: Line 68:
* Identify binary components via script iterating over all addons
* Identify binary components via script iterating over all addons
* Allow Ext Devs to check if binary components exist in their addon
* Allow Ext Devs to check if binary components exist in their addon
* For logged in editors, provide links to review queue from add-on pages an search results


= Infrastructure =
= Infrastructure =
Line 75: Line 75:
* Can we offer performance tools for addons (Talos, other)?
* Can we offer performance tools for addons (Talos, other)?


= Policies =
 
* Write editor role description, how to do a review, etc...
** Upon Update:
** Upon New nomination:
* Can we auto-check for JS security issues: remote JS include with HTTP
* Preference for app-update url (?)


= Community Building =
= Community Building =
* Editor Leaderboard
* Editor Leaderboard
* Editor tools feature requests
** Make it easier to search for an add-on in a queue, with the results providing links to the review page
** If you are logged in as an editor, and go to a page for an add-on in the sandbox, then somewhere on the page there should be a 'Review' link
* AMO Treasure Hunt
* AMO Treasure Hunt
* AddOns Planet for article publishing
* AddOns Planet for article publishing
1,071

edits