Intent to implement: Difference between revisions

Obsolete this document as it's redundant
(Suggested Additions based on existing emails)
(Obsolete this document as it's redundant)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{stub}}
#REDIRECT [[ExposureGuidelines]]
 
'''<dfn>Intent to implement</dfn>''' is part of Mozilla's [[WebAPI/ExposureGuidelines#Suggested_implementation_process|Suggested implementation process]] for [[WebAPI/DesignGuidelines#Specification_work|specification work]] and refers to announcement emails sent to [https://lists.mozilla.org/listinfo/dev-platform dev-platform] starting with the subject "Intent to implement".
 
== Email Template ==
For sending an "Intent to implement" email, use:
* [[WebAPI/ExposureGuidelines#Intent_to_Implement|Intent to implement email template]]
 
=== Suggested Additions ===
Suggested additions to any "Intent to implement" email, based on existing dev-platform examples, and questions asked on dev-platform in response to intent to ship emails.
* '''Do other browser engines implement this?''' Answer with:
** Shipped (since version X, behind what flags if any), Intent to implement emailed (mailing list URL), Considering (citation)
* '''Tests''' - URLs / paths to tests
* '''Security & Privacy Concerns'''
 
== Others intent to implement ==
Other browsers and engines sometimes send intent to implement emails to their own lists, e.g.:
 
=== Blink ===
;List
:[https://groups.google.com/a/chromium.org/forum/#!forum/blink-dev blink-dev]
;Example Intent to Implement
:https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ODWmcKNQl0I
;Chromium Dashboard of web platform features
:https://www.chromestatus.com/features
 
== See Also ==
* [[WebAPI/DesignGuidelines]]
* [[WebAPI/ExposureGuidelines]]
Confirmed users
112

edits