1,698
edits
Add-ons/Reviewers/Content Review Guidelines: Difference between revisions
Add-ons/Reviewers/Content Review Guidelines (view source)
Revision as of 23:02, 3 January 2020
, 3 January 2020updated for 2020
Caitmuenster (talk | contribs) (→Guidelines for Content Review: added section about private use add-ons) |
Caitmuenster (talk | contribs) (updated for 2020) |
||
| Line 2: | Line 2: | ||
==Focus of Content Review== | ==Focus of Content Review== | ||
The goal of content review is to screen listings on | The goal of content review is to screen listings on AMO for spam, abuse, and inappropriate content. Content reviewers do not review the code of extensions submitted to AMO unless they have been specifically trained to do so. | ||
==Guidelines for Content Review== | ==Guidelines for Content Review== | ||
| Line 17: | Line 17: | ||
* Large content block of SEO search terms | * Large content block of SEO search terms | ||
* Links to websites or chat services that are unrelated to the Firefox extension | * Links to websites or chat services that are unrelated to the Firefox extension | ||
''Duplicate submissions'' are not necessarily spam. For example, extensions with the same name for multiple locales are acceptable. If you see duplicate submissions, please report them to amo-admins for further investigations. | |||
====Copyright or Trademark Violations==== | ====Copyright or Trademark Violations==== | ||
| Line 24: | Line 24: | ||
For Mozilla trademarks, the usage of “Mozilla” and “Firefox” are generally not allowed in the add-on name, except in the following format: “ADD-ON NAME for Firefox.” | For Mozilla trademarks, the usage of “Mozilla” and “Firefox” are generally not allowed in the add-on name, except in the following format: “ADD-ON NAME for Firefox.” | ||
* Exceptions to this are extensions that are officially owned by the [https://addons.mozilla.org/en-US/firefox/user/4757633/ Mozilla account], such as Facebook Container and Firefox Color. | |||
====Private Use Add-ons==== | ====Private Use Add-ons==== | ||
Extensions that are intended for internal or private use, or for distribution testing, should not be listed on AMO and should be rejected. (These add-ons can be uploaded for self-distribution instead.) | Extensions that are intended for internal or private use, or for distribution testing, should not be listed on AMO and should be rejected. (These add-ons can be uploaded for [https://extensionworkshop.com/documentation/publish/self-distribution/ self-distribution] instead.) | ||
When in doubt if an extensions is intended for internal or private use, ask: | When in doubt if an extensions is intended for internal or private use, ask: | ||
| Line 34: | Line 35: | ||
However, if a user needs to take additional steps beyond registering for an individual account and paying for it, the extension would be considered '''private'''. Additional steps might include signing a business contract, being admitted to a specific university, or being a member of a closed club. The number of (potential) users is not relevant for making this determination. | However, if a user needs to take additional steps beyond registering for an individual account and paying for it, the extension would be considered '''private'''. Additional steps might include signing a business contract, being admitted to a specific university, or being a member of a closed club. The number of (potential) users is not relevant for making this determination. | ||
'''Beta versions''' of extensions can be listed on AMO as long as it is an open beta for a new product. When their beta extensions are ready for official release, developers should rename their extension to the final release name and not create a new listing on AMO. A beta or test release of an existing product, or a closed beta, should be rejected. You can site https://blog.mozilla.org/addons/2018/02/28/discontinuing-support-for-beta-versions/ in the rejection comment. | |||
====Add-on Summary and Description==== | |||
The Add-on Policies state, “The add-on listing should have an easy-to-read description about everything it does, and any information it collects.” The description should include an attempt to describe what the add-on does for its intended audience. '''Please do not reject an extension if you do not think the description and summary are sufficient'''. Use the “Reviewer Reply” tool and select the “Incomplete Description” canned response to message the developer. You can customize the canned response as you see fit. | |||
====Sexual Content==== | ====Sexual Content==== | ||
Any child pornography must be escalated to Mozilla for reporting to the National Center for Missing and Exploited Children (NCMEC). Please send an email to | Any child pornography must be escalated to Mozilla for reporting to the National Center for Missing and Exploited Children (NCMEC). Please send an email to cneiman [at] mozilla.com and include the following: | ||
* Review URL | * Review URL | ||
* Short description of the image | * Short description of the image | ||