Confirmed users
745
edits
Add-ons/Projects: Difference between revisions
Jump to navigation
Jump to search
Added remainder of AMO stuff
(Added Security and Mission-critical for AMO) |
(Added remainder of AMO stuff) |
||
| Line 2: | Line 2: | ||
== Firefox/Quantum Platform == | == Firefox/Quantum Platform == | ||
=== Mission-critical technical needs === | |||
; Remove support for unpacked extensions | |||
: The add-ons manager codebase currently support two separate code paths, one for unpacked and one for packed. This doubles the maintenance and testing burden, and unpacked, in particular, is prone to bugs and performance issues. It is no longer recommended on MDN. [targeting 62] | |||
; Telemetry improvements | |||
: Telemetry of the add-ons manager (about:addons) and performance of addons is currently incomplete. [targeting 62] | |||
=== New WebExtension APIs === | === New WebExtension APIs === | ||
| Line 31: | Line 38: | ||
; Remove uses of bootstrapped extensions | ; Remove uses of bootstrapped extensions | ||
: Removing support for bootstrapped extensions continues the process that was begun when we removed support for arbitrary bootstrapped extensions (on release and beta) and allows for the removal of more unused code. The remainder of bootstrapped extensions should be converted to web extensions or achieve their aim some other way (these are primarily internal). [targeting 64] | : Removing support for bootstrapped extensions continues the process that was begun when we removed support for arbitrary bootstrapped extensions (on release and beta) and allows for the removal of more unused code. The remainder of bootstrapped extensions should be converted to web extensions or achieve their aim some other way (these are primarily internal). [targeting 64] | ||
=== Security === | === Security === | ||
| Line 76: | Line 76: | ||
== addons.mozilla.org == | == addons.mozilla.org == | ||
=== Mission-critical technical needs === | === Mission-critical technical needs === | ||
| Line 111: | Line 95: | ||
; Antispam - Akismet | ; Antispam - Akismet | ||
: There's a increasing amount of spam that is being manually removed from AMO. To combat this we can use Akismet's spam API to give an indication of whether any piece of UGC is spam or not; implementing this means we need to send all UGC to akismet. | : There's a increasing amount of spam that is being manually removed from AMO. To combat this we can use Akismet's spam API to give an indication of whether any piece of UGC is spam or not; implementing this means we need to send all UGC to akismet. | ||
=== Continuation of migration to Extensions === | |||
; Support Static Themes on AMO | |||
: AMO needs to support extension-based themes for developers, reviewers, and end users. This includes deprecating existing theme APIs and discontinue (XUL-based) complete themes. [targeting Q3] | |||
; Support static themes on frontend | |||
: Enable the presentation of static themes on AMO. [targeting Q3] | |||
; Theme Migration | |||
: Migrate lightweight themes to static themes. [targeting Q3] | |||
; WebExtensions Dictionaries | |||
: In order to move away from legacy packaging and legacy manifests, we should move dictionaries to WebExtensions packaging. | |||
; Dynamic Theme Classification | |||
: We need to make a distinction between two types of themes: static and dynamic. All themes should be shown under 'themes' on AMO, but we need to determine how a developer specifies that, submits it, and what precautions or limitations we should put in place to protect users as much as is reasonable and prudent. | |||
=== Continuation of migration to new front-end === | |||
; Finish User Profile | |||
: This project is to track all the remaining tickets for adding the user profile page and user profile editing into the new frontend. [targeting 2018.06.28] | |||
=== Security === | === Security === | ||
| Line 119: | Line 123: | ||
: We want to add support a number of privacy flags that developers can use to report the add-on's privacy practices to users. This would be set using the "privacy" key in the manifest, and would be displayed on AMO. | : We want to add support a number of privacy flags that developers can use to report the add-on's privacy practices to users. This would be set using the "privacy" key in the manifest, and would be displayed on AMO. | ||
=== Engineering improvements === | |||
; Support bigger screenshot uploads | |||
: In order to improve image quality on AMO, larger screenshots must be supported for upload. [targeting ?] | |||
<strike>; A/B Testing Framework | |||
: https://github.com/mozilla/addons-frontend/issues/4262 | |||
In order to enable A/B testing on AMO, we need to implement a testing solution (existing, React-based).</strike> | |||
; Finishing collections on user pages | |||
: A collection is list of add-ons curated by one or more users. This tracks a limited feature set that we are porting from the legacy site to the new one. [targeting 2018.06.28] | |||
=== UI improvements === | |||
; Disco Pane Improvements | |||
: We believe that improving how we display and organize the content in discopane will result in more add-ons installs. This includes showing recommendations on discopage, UI changes, content strategy, etc. | |||
; New User Onboarding | |||
: Improve the experience of first-time visitors to AMO in order to encourage return visits and downloads. | |||
=== Discoverability === | |||
; TAAR / Recommendations | |||
: ??? | |||
; Tags | |||
: ??? | |||
| Line 137: | Line 165: | ||
== Marketing/Community Engagement == | == Marketing/Community Engagement == | ||
=== Reduce engineering overhead === | |||
; Admin tools, phase 1 | |||
: In order to administer AMO, admins have to use a variety of disparate and unintegrated tools; this requires separate upkeep and privilege/permission schemes. This project unifies those tools and sets the stage for future content curation tools. | |||
; Curation tools | |||
: This admin tool will enable content curators to customize the AMO homepage using a set of pre-built homepage modules. This replaces the need for manual changes by engineering staff and grants content publishing control to content strategists and editorial/campaign managers. | |||
=== Growth opportunities === | |||
; Non-fx Install Flow (ReturnToAMO) | |||
: Users who choose to install Firefox from an add-ons listing page (on AMO) currently dead-end having installed Firefox. Converting those users to add-ons users by presenting them with the ability to install the add-on whose page they installed from during their first run will increase both user population and retention. | |||
; AMO Rebranding | |||
: Create a brand for AMO that makes it easy for users to refer to it. Potentially retire the term "add-on" and focus on extensions and themes, which both resonate better with users and compete directly with Chrome. | |||
; AMO Rating and Review Flow | |||
: Add-on ratings are a critical feature on AMO, allowing users to tell the world about the usefulness of an add-on and share their experiences. They help users know which add-ons are higher quality, and give developers encouragement and feedback to continue their development. AMO needs a rating system that encourages and highlights legitimate ratings, and mitigates abuse by bad actors. Rating should be easy. Blocking and moderation of written review should be both effective and transparent. | |||
== Status reports (legacy) == | == Status reports (legacy) == | ||
{{Special:PrefixIndex/Add-ons/Projects/}} | {{Special:PrefixIndex/Add-ons/Projects/}} | ||