Intent to implement: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Suggested Additions based on existing emails)
(→‎Suggested Additions: Web designer / developer use-cases)
Line 13: Line 13:
* '''Tests''' - URLs / paths to tests
* '''Tests''' - URLs / paths to tests
* '''Security & Privacy Concerns'''
* '''Security & Privacy Concerns'''
* '''Web designer / developer use-cases''' - Provide a URL to at least briefly documented use-cases for web designers and developers that illustrate when they would use this feature.


== Others intent to implement ==
== Others intent to implement ==

Revision as of 01:43, 31 March 2015

This article is a stub. You can help MozillaWiki by expanding it.

Intent to implement is part of Mozilla's Suggested implementation process for specification work and refers to announcement emails sent to dev-platform starting with the subject "Intent to implement".

Email Template

For sending an "Intent to implement" email, use:

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
  • Web designer / developer use-cases - Provide a URL to at least briefly documented use-cases for web designers and developers that illustrate when they would use this feature.

Others intent to implement

Other browsers and engines sometimes send intent to implement emails to their own lists, e.g.:

Blink

List
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