canmove, Confirmed users
901
edits
ExposureGuidelines: Difference between revisions
→Implementation Process
| Line 33: | Line 33: | ||
# Email [https://lists.mozilla.org/listinfo/dev-platform dev-platform] declaring your ''intent to implement'' this API ('''FIXME''' CC joint list with Blink) ('''FIXME''' create email template ([https://docs.google.com/document/d/1vlTlsQKThwaX0-lj_iZbVTzyqY7LioqERU8DK3u3XjI/edit#bookmark=id.uptkx07pm53s Blink's template])). If you are implementing an API that is working its way through a standards body process such as the W3C's, it's best to email as soon as possible (ie. before [http://www.w3.org/2005/10/Process-20051014/tr#q74 W3C CR status] if possible). | # Email [https://lists.mozilla.org/listinfo/dev-platform dev-platform] declaring your ''intent to implement'' this API ('''FIXME''' CC joint list with Blink) ('''FIXME''' create email template ([https://docs.google.com/document/d/1vlTlsQKThwaX0-lj_iZbVTzyqY7LioqERU8DK3u3XjI/edit#bookmark=id.uptkx07pm53s Blink's template])). If you are implementing an API that is working its way through a standards body process such as the W3C's, it's best to email as soon as possible (ie. before [http://www.w3.org/2005/10/Process-20051014/tr#q74 W3C CR status] if possible). | ||
# Implement as normal. Code review rounds will take place, etc. | # Implement as normal. Code review rounds will take place, etc. | ||
# We are creating a Mozilla API review team which will be made up of Mozillians who have experience designing JS APIs and will have at least one representative from the JS team at all times. This team will monitor dev-platform for ''intent to implement'' emails and can assist with ensuring APIs are "webby" and friendly to JS developers. When new APIs are being implemented, a super-review from a member of the API review team (once it is in place) is requested. Module owners can choose to waive this request if they feel it is not necessary. | |||
=Shipping Process= | =Shipping Process= | ||