AMO:Editors/Featured and Recommended: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 4: Line 4:


= Featured Add-Ons =
= Featured Add-Ons =
* Featured Add-Ons are add-ons that get rotated into one of three slots on the [https://addons.mozilla.org/en-US/firefox/ main page of AMO]
See [https://addons.mozilla.org/en-US/developers/docs/policies/recommended Recommended Add-ons]
* Ideally, the types of add-ons to be featured should be already on the category-recommended list. By also being on the Reco List, the Firefox 3 addon's manager can help pull them using the API and offer them.
* Expectations should be set that participation in the Featured Add-Ons list will only be temporary
* In order to prevent staleness
** We should rotate the list every 3-4 weeks
** With 3 slots available, the following shows the number of unique pages that can be generated with the number of featured add-ons.
*** (5,3)=10, (6,3)=20, (7,3)=35, (8,3)=56, (9,3)=84, (10,3)=120
** Recognize that with a fewer number (e.g. 5) of add-ons on the featured list, you will get lots of repetition, seeing the same ones being promoted every time.
** At minimum, we should strive to have at least 10 featured add-ons
* When designing a list, we should try to sample from the various categories that AMO has. Currently AMO has about 14 categories. Ideally, we show not be showing more than five from each category.
* As this list may get exposure to more "beginner users", we should probably not show items from the Web Developer, Language Tools and Toolbars category. We can revisit this later.
* Mozilla Corp can potentially use "featured" as a way to help promote selected partner add-on (even if they are not on the Reco Lists)... this is not ideal. It's better to be organic, become Recommended first and let the community and users drive popularity.
* In order to not surprise the add-on developers/partner, we should try to notify them before we put them up there since they will likely get a surge in add-ons downloads - they may need to prep servers to handle load, etc... It's good to notify.
* We should keep a spreadsheet/record of what was the feature list at every point in time
* We should create "events" in the developer control panel for the featured add-on and watch the downloads/active usage charts
* We should review the performance of add-ons and if a featured add-on is not performing well, perhaps the description/image needs to be modified.
* We should gather some stats about how well add-ons perform when they are featured versus recommended versus simply public.
 
* How do you become a featured add-on?
** In general, Mozilla's policy should be to rotate add-ons from the Reco List onto the featured list. Everyone should get a fair chance!
** Based on Mozilla community discretion, it may decide to feature particular add-ons.
** Apply by emailing amo-admins@mozilla.org
** Featured add-ons must be hosted on AMO
 
* Technically, how do you make an add-on featured?
** Changing Featured Add-ons requires Admin Group access to AMO.
** Use the Admin Tools::Feature Manager to decide what is on that list
*** If added to the "Unspecified" list, then it is added to a global list (essentially adding it to all locales)
*** If added to the local-specific list, then the addon will be rotated in for that locale only.


= Recommended Lists =  
= Recommended Lists =  

Revision as of 23:44, 25 November 2009

AMO v3.2 Site Management

The following are a set of guidelines about how AMO admins and editors should manage the AMO site especially after launching the new v3.2 features. In particular, how to manage the new role of featured and recommended add-ons.

Featured Add-Ons

See Recommended Add-ons

Recommended Lists

See Recommended Add-ons

Building Recommendation Lists

If I were to design the idea recommendation list, I would consider whether:

  • The add-ons are generally compatible with each other
  • Not all of them are site-specific
  • Doesn't create a weird first-run experience when more than 2/3 are chosen
  • Represents a sample of the variety of add-ons that are available
  • Represents a cross-section of things that people do on the Internet, e.g. social networking, chat, VOIP, video, commerce, information retrieval, music, info/data organization, etc...

What are some of the ideal criteria for deciding if something should be recommended:

  • Has it been marked as a "favorite" by users?
  • Popularity based on AMO or other locations downloads, already in the hands of lots of users, mileage, tried and tested (at least 20,000 downloads?)
  • "perceived as useful", "well maintained" and "well tested".
  • Helps demonstrate an interesting browsing experience
  • Quality, works as expected, proven
  • Effect on performance (startup time, rendering time, UI zippiness)
  • Effect on memory usage (static and over time, no leaks)
  • Free of security holes
  • Has good feedback from reviewers and end users
  • Doesn't degenerate or severely affect the core Firefox user experience
  • Appropriate for New-to-Firefox Users (new demographic)
  • Demonstrates interesting capabilities
  • Brand compatible
  • Not severely incompatible with privacy policy/No spyware
  • Useful for a general populace
  • Compatibility with current Firefox release (and beta versions)
  • Documentation/associated content (e.g. support on relevant site, mktg, help info, etc…)
  • Licensing - is it trialware?, MPL, etc…
  • Hurdles to get going: does it require a new login? Or extra client software?
  • Compatibility with other extensions
  • Support for addon by developer, forums, docs, etc…

Trusted Add-on

  • What is a trusted add-on?
    • A trusted add-on will allow subsequent updates to be automatically pushed public without getting sandbox'ed. Being trusted means that the add-on will not be queued for review by an AMO editor.
    • AMO has a small, select group of addons on the trusted list.
  • How do you become a trusted add-on?
    • Add-on author should drop an email to amo-editors@mozilla.org explaining why they need trusted status
  • What is the criteria for becoming a trusted add-on?
    • Is the add-on of high quality with its own development branch and low update frequency?
    • Do the developers seem to care about security?
    • Do the developers want to fix bugs fast and have demonstrated that they've done that?
    • Non criteria:
      • reduce workload for AMO Editors
      • Limited audience for extensions, small group of editors
Retrieved from "https://wiki.allizom.org/index.php?title=AMO:Editors/Featured_and_Recommended&oldid=185891"