Confirmed users
455
edits
User:Shaver/AMO Extension Policy: Difference between revisions
Jump to navigation
Jump to search
User:Shaver/AMO Extension Policy (view source)
Revision as of 22:40, 22 November 2006
, 22 November 2006no edit summary
No edit summary |
|||
| Line 35: | Line 35: | ||
* OK: "Network Explorer" | * OK: "Network Explorer" | ||
* Not OK: "Opera 9" | * Not OK: "Opera 9" | ||
= Categorization = | |||
Categories are used to help users navigate the collection of add-ons more narrowly, such that they are better able to find an add-on that will suit their current need. Add-ons should be categorized according to the major capability provided by the add-on. In the vast majority of cases this means that an add-on should be in only one or two categories. | |||
Add-ons which represent a bundle of largely-unrelated functionality will need to decide which of their features is most important to them. (We could add a "grab-bag" category for extensions like the Conduit-based toolbars which provide everything ranging from a "pop-up blocker" to RSS feeds, with many stops in between.) | |||
= Collection of user data = | = Collection of user data = | ||
| Line 41: | Line 47: | ||
* description of the add-on must include a link to the privacy policy for the organization/site to which the data is reported | * description of the add-on must include a link to the privacy policy for the organization/site to which the data is reported | ||
* the privacy policy must clearly indicate what data is collected, by whom, and what the data is used for, as well as who the user should contact for | * the privacy policy must clearly indicate what data is collected, by whom, and what the data is used for, as well as who the user should contact for | ||
* the collection of personal data should be restricted to that data which is necessary for the proper operation of the add-on; additional instrumentation or data collection for usability analysis or other such ends should be on an opt-in basis | |||
The privacy policy document should be clear and factual, and focus on what _is_ done with the data; it is not a marketing vehicle, and should not spend significant space describing what is _not_ done with the data. | The privacy policy document should be clear and factual, and focus on what _is_ done with the data; it is not a marketing vehicle, and should not spend significant space describing what is _not_ done with the data. | ||