ExposureGuidelines: Difference between revisions

ExposureGuidelines (view source)

Revision as of 16:01, 26 June 2013

127 bytes added , 26 June 2013

→‎Declaring Intent to Implement

Overholt

canmove, Confirmed users

901

edits

@@ Line 29: / Line 29: @@
 =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.  This will act as a public service announcement and allow all interested parties to comment on technical or related issues.  The email must also demonstrate that an API is standardized as [[#Standardization|defined below]].  A third use of this email will be 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.
 =API review=