Confirmed users, Bureaucrats and Sysops emeriti
2,974
edits
Improved missing plugin experience: Difference between revisions
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 5: | Line 5: | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature product manager=Asa Dotzler | |||
|Feature feature manager=Justin Dolske | |Feature feature manager=Justin Dolske | ||
|Feature qa lead=AndreiD | |Feature qa lead=AndreiD | ||
| Line 11: | Line 12: | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature overview=Our current experience when a plugin is missing is pretty abysmal, and rarely works for anything else than a very small set of plugins. We want to fix the experience for the small set of plugins that have a lot of users, and stop pretending to supply an auto-detect service for the others. | |Feature overview=Our current experience when a plugin is missing is pretty abysmal, and rarely works for anything else than a very small set of plugins. We want to fix the experience for the small set of plugins that have a lot of users, and stop pretending to supply an auto-detect service for the others. | ||
This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.) | |||
|Feature requirements=* Ability to detect and point to relevant locations for the major plugins | |Feature requirements=* Ability to detect and point to relevant locations for the major plugins | ||
* Mozilla needs to host permanent redirect URLs for this, so we can change quickly, should downstream providers suddenly change their URLs or similar | * Mozilla needs to host permanent redirect URLs for this, so we can change quickly, should downstream providers suddenly change their URLs or similar | ||