ExposureGuidelines: Difference between revisions

→‎Suggested Additions: Add "How stable is the spec"
(Remove mention of Firefox OS)
(→‎Suggested Additions: Add "How stable is the spec")
Line 68: Line 68:


If you're looking for extra credit, or to preempt common questions, consider adding any or all of the following (all based on existing dev-platform examples, and questions asked on dev-platform in response to intent to ship emails).
If you're looking for extra credit, or to preempt common questions, consider adding any or all of the following (all based on existing dev-platform examples, and questions asked on dev-platform in response to intent to ship emails).
* '''How stable is the spec''' - Note that even if it's unstable that shouldn't stop us implementing; that mostly affects shipping.  So as long as we're pretty sure that the basic set of functionality is stable, even if the actual names of the values are not, implementing makes sense.
* '''Security & Privacy Concerns''' - consider providing a link to answers in [https://mikewest.github.io/spec-questionnaire/security-privacy/ this security/privacy questionnaire] for a spec feature, if the spec doesn't already answer it.
* '''Security & Privacy Concerns''' - consider providing a link to answers in [https://mikewest.github.io/spec-questionnaire/security-privacy/ this security/privacy questionnaire] for a spec feature, if the spec doesn't already answer it.
* '''Web designer / developer use-cases''' AKA '''Why a developer would use Feature X?''' - Provide a URL to at least briefly documented use-cases for web designers and developers that illustrate why and when they would use this feature.
* '''Web designer / developer use-cases''' AKA '''Why a developer would use Feature X?''' - Provide a URL to at least briefly documented use-cases for web designers and developers that illustrate why and when they would use this feature.
Confirmed users
346

edits