AMO:Roadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(19 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{amo}}
'''Note: This is out of date, please see [[Add-ons/Server]].'''


__NOTOC__
== Add-Ons and AMO Roadmap Q2 & Q3 2015 ==


= Core Roadmap =
=== Firefox 40: ===
* Add-On Signing
 
=== Firefox 41: ===
* Add-On Signing Enforced (no pref to disable, except in ESR)
* XPCOM Binary support deprecation
 
== historical roadmaps below ==
 
==AMO - Q1-Q4 2009 ==
[http://docs.google.com/Doc?id=dds6vwb4_5d3hvkfdt Link to Google Doc]
 
== AMO - Q3 & Q4 2008 ==
The goals listed here are aligned with the [[User:Bhashem/AddOns-AMO-Principles|AMO Principles]]. Appearing in the Q3 & Q4 cells are potential major features that are under consideration as part of the roadmap. Of course, there will be a ton of bug fixes [http://tinyurl.com/amo-allbugs selected from this list] as well.
 
Additionally, the roadmaps for the [[#API_Roadmap|AMO API]] and [[#Stats_Dashboards|stats dashboards]] appear further below.
 
<table class="fullwidth-table">
<tr>
<th style="width:15%"><center>Goal</center></th>
<th style="width:45%"><center>Q3 2008</center></th>
<th style="width:40%"><center>Q4 2008</center></th>
</tr>
 
<tr>
<td>Ease of Use</td>
<td><ul>
<li>Full-Text Search & find-as-you-type</li>
<li>Rework FAQ</li>
</ul></td>
<td><ul>
<li>AMO for Firefox Mobile/Fennec</li>
<li>Replaces Vanilla-based Forums</li>
</ul></td>
</tr>
 
<tr>
<td>Find & Discover</td>
<td><ul>
<li>Favorite-ing</li>
<li>Add-on newsfeed</li>
<li>[[Update:Remora:Search|Revise popularity algorithm]]</li>
</ul></td>
<td><ul>
<li>Add-on recommender</li>
<li>List Maker</li>
<li>Glimpse - installed add-on clustering</li>
</ul></td>
</tr>
 
<tr>
<td>Breadth</td>
<td><ul>
<li>Search engines expansion</li>
<li>Stub Entries for non-AMO add-ons</li>
</ul></td>
<td><ul>
<li>Add-on locale packs</li>
</ul></td>
</tr>
 
 
<tr>
<td>Add-on Devs</td>
<td><ul>
<li>Revised Dev Tools</li>
<li>Developer Survey</li>
<li>[[Update:API:UseCases_2.0|Updated Read & Stats API]]</li>
<li>Revised Devs Wiki</li>
</ul></td>
<td><ul>
<li>Public Stats Dashboard</li>
<li>Revised Sandbox/Review Queue</li>
<li>mini AMO on your site</li>
</ul></td>
</tr>
 
<tr>
<td>AMO Editors & Localizers</td>
<td><ul>
<li>Revised Editor Tools</li>
<li>Metadata Upload API</li>
<li>Version Diff'ers</li>
<li>Revised Editors' Wiki</li>
</ul></td>
<td><ul>
<li>New L10N Tools/[[Verbatim|Verbatim]] integration</li>
<li>Editor Leaderboard</li>
</ul></td>
</tr>
 
 
</table>


== v3.0 (Remora) ==
== v3.0 (Remora) ==
Line 33: Line 125:
v1.0 was released, based in part on work done in the  [[Update:Archive/1.0/Developers|security audit]].  Further revisions will be addressed on a case-by-case basis as our efforts turn towards v2.0, which is based on a much better framework.
v1.0 was released, based in part on work done in the  [[Update:Archive/1.0/Developers|security audit]].  Further revisions will be addressed on a case-by-case basis as our efforts turn towards v2.0, which is based on a much better framework.


== Stats Dashboards ==
= API Roadmap =
* The AMO API 1.0 release was the first iteration of a read-only API and primarily targeted Firefox 3 Beta 3 (also known as [[Update:RequirementsV33|AMO v3.3]])
* The [[Update:Remora_API_Docs|AMO API 1.1]] release included fixes to support the final ship of Firefox 3
* [[Update:API:UseCases_2.0|AMO API 2.0]] will include expanded read-only functionality (for stats), support add-on authors, an API key mechanism in order to allow AMO metadata and add-on uploads.
 
= Stats Dashboards =
* [https://stats.mozilla.com/urchin/session.cgi Urchin] is used for web analytics - tracking site page view and session stats
* [https://stats.mozilla.com/urchin/session.cgi Urchin] is used for web analytics - tracking site page view and session stats
* Download & Update pings are tracked via [https://stats.mozilla.com/dashboard custom dashboard]. Migrating to a [http://www.pentaho.com/ Pentaho-base system].
* Download & Update pings are tracked via [https://stats.mozilla.com/dashboard custom dashboard]. Migrating to a [http://www.pentaho.com/ Pentaho-base system].
Line 39: Line 136:
* Here is the [[Update:RequirementsStats|stats wishlist]].
* Here is the [[Update:RequirementsStats|stats wishlist]].


== Future Features ==
= Future Features =
This is a [[Update:FutureFeatures|list of features]] that we'd eventually like to add to AMO.
This is a [[Update:FutureFeatures|list of features]] that we'd eventually like to add to AMO.

Latest revision as of 22:12, 23 June 2016

Note: This is out of date, please see Add-ons/Server.

Add-Ons and AMO Roadmap Q2 & Q3 2015

Firefox 40:

  • Add-On Signing

Firefox 41:

  • Add-On Signing Enforced (no pref to disable, except in ESR)
  • XPCOM Binary support deprecation

historical roadmaps below

AMO - Q1-Q4 2009

Link to Google Doc

AMO - Q3 & Q4 2008

The goals listed here are aligned with the AMO Principles. Appearing in the Q3 & Q4 cells are potential major features that are under consideration as part of the roadmap. Of course, there will be a ton of bug fixes selected from this list as well.

Additionally, the roadmaps for the AMO API and stats dashboards appear further below.

Goal
Q3 2008
Q4 2008
Ease of Use
  • Full-Text Search & find-as-you-type
  • Rework FAQ
  • AMO for Firefox Mobile/Fennec
  • Replaces Vanilla-based Forums
Find & Discover
  • Add-on recommender
  • List Maker
  • Glimpse - installed add-on clustering
Breadth
  • Search engines expansion
  • Stub Entries for non-AMO add-ons
  • Add-on locale packs
Add-on Devs
  • Public Stats Dashboard
  • Revised Sandbox/Review Queue
  • mini AMO on your site
AMO Editors & Localizers
  • Revised Editor Tools
  • Metadata Upload API
  • Version Diff'ers
  • Revised Editors' Wiki
  • New L10N Tools/Verbatim integration
  • Editor Leaderboard

v3.0 (Remora)

The first Remora release was March 2007.

v3.1

AMO, Version 3.1 was released in September 2007. It includes support for download counters for the developer control panel

v3.2

AMO, v3.2 was released in Mar 2008. Its goal is an AMO site redesign and a PHP platform upgrade. A AMO v3.2 requirements document and the release announcement is available.

v3.3

AMO, v3.3 was released during Q1 & Q2 2008. Its goal was to offer an API to AMO to support Fx3's new "Get Add-ons" panel. A API requirements document is available.

v3.4

We shifted development to a rapid iteration cycle and AMO, v3.4 was released in Apr 2008 followed by several point releases. Its goal was to offer new navigation, a theme browser, advanced search. A series of blog posts about v3.4 features appear (3.4.1, 3.4.2, 3.4.3/3.4.4)

v3.5

AMO, v3.5 is a rewrite of the developer tools section of AMO currently scheduled for Jul 2008. Documented in a five-part blog post.

v2.0

addons.mozilla.org was rewritten to scale better for high-load public site.

We realize that rewriting has been a long time coming. This is why we have reevaluated our situation and have set more realistic short-term goals.

Read the v2.0 plan.

v1.0

v1.0 was released, based in part on work done in the security audit. Further revisions will be addressed on a case-by-case basis as our efforts turn towards v2.0, which is based on a much better framework.

API Roadmap

  • The AMO API 1.0 release was the first iteration of a read-only API and primarily targeted Firefox 3 Beta 3 (also known as AMO v3.3)
  • The AMO API 1.1 release included fixes to support the final ship of Firefox 3
  • AMO API 2.0 will include expanded read-only functionality (for stats), support add-on authors, an API key mechanism in order to allow AMO metadata and add-on uploads.

Stats Dashboards

Future Features

This is a list of features that we'd eventually like to add to AMO.