AMO:Editors/Featured and Recommended
Jump to navigation
Jump to search
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
Recommended Lists
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