canmove, Confirmed users
901
edits
ExposureGuidelines: Difference between revisions
→Declaring Intent
| Line 28: | Line 28: | ||
# APIs which will be hidden behind preferences. APIs like this can also skip the required API review (see below). | # APIs which will be hidden behind preferences. APIs like this can also skip the required API review (see below). | ||
=Declaring Intent= | =Declaring Intent to Implement= | ||
Developers of new APIs intended to be exposed to the web at large via Mozilla products must send an email to [https://lists.mozilla.org/listinfo/dev-platform dev-platform] declaring their intent to implement this API. This email must have a subject line that begins with "Intent to implement:" and whose body describes the feature and links to relevant documentation. It must also demonstrate that an API is standardized as [[#Standardization|defined below]]. Implementors must also use this email to request API review from the Mozilla [[Special:MyPage/APIExposurePolicy#API_review|API review]] team. These emails must be sent ''early on'' in the process of any new API's development, especially if this work is being done as part of a standards body (ie. before [http://www.w3.org/2005/10/Process-20051014/tr#q74 W3C CR status]). This will expose the API to a(n even) larger audience which can help improve its quality and avoid APIs which are designed by domain experts but aren't "webby" or friendly to JS developers. The API review team can help with the latter concern. | Developers of new APIs intended to be exposed to the web at large via Mozilla products must send an email to [https://lists.mozilla.org/listinfo/dev-platform dev-platform] declaring their intent to implement this API. This email must have a subject line that begins with "Intent to implement:" and whose body describes the feature and links to relevant documentation. It must also demonstrate that an API is standardized as [[#Standardization|defined below]]. Implementors must also use this email to request API review from the Mozilla [[Special:MyPage/APIExposurePolicy#API_review|API review]] team. These emails must be sent ''early on'' in the process of any new API's development, especially if this work is being done as part of a standards body (ie. before [http://www.w3.org/2005/10/Process-20051014/tr#q74 W3C CR status]). This will expose the API to a(n even) larger audience which can help improve its quality and avoid APIs which are designed by domain experts but aren't "webby" or friendly to JS developers. The API review team can help with the latter concern. | ||