User:Polvi/PFS2: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (→Three teirs) |
||
| Line 2: | Line 2: | ||
Make plug-ins follow the same model as addons. | Make plug-ins follow the same model as addons. | ||
== Three | == Three tiers == | ||
# Plug-ins (effectively) bundled with Firefox since they are trusted | # Plug-ins (effectively) bundled with Firefox since they are trusted | ||
## very easy for the user to install in the UI | ## very easy for the user to install in the UI | ||
| Line 15: | Line 15: | ||
## ~10 clicks | ## ~10 clicks | ||
## ex: videoegg | ## ex: videoegg | ||
= Policy = | = Policy = | ||
Latest revision as of 22:50, 8 September 2007
Major Idea
Make plug-ins follow the same model as addons.
Three tiers
- Plug-ins (effectively) bundled with Firefox since they are trusted
- very easy for the user to install in the UI
- 1 click
- ex: flash, pdf, java
- Plug-ins tested/recommended/approved by Mozilla
- educates user about what they are doing
- ~3 clicks
- ex: silverlight, google gadgets, mathML
- Random plug-ins
- make sure user knows they are getting something potentially malicious
- ~10 clicks
- ex: videoegg
Policy
Currently there is no clear policy about what plug-ins can get into PFS. We need to define this based on the three tiers methodology.
Phase one: clean it up
Right now PFS has all sorts of plug-ins, some better than others. For an initial PFS revamp, we need to accomplish the following things.
- Ensure technical security through-out the site
- All communications over SSL
- Define policy for how plug-ins get added to PFS
- Re-organize plug-ins to match policy
- Probably meaning a lot of the current ones get the boot
Considerations
- What happens in ie7, opera, safari?