WebAPI/DesignGuidelines: Difference between revisions

Jump to navigation Jump to search
→‎Preparation: document on wiki
(→‎Preparation: if this is your first, get a co-editor. publicly document, Web Intents as example of scope creep to avoid, keep documenting on an open wiki page)
(→‎Preparation: document on wiki)
Line 8: Line 8:
** with some experience, you'll see fundamental issues with the web platform for which you can propose fixes!
** with some experience, you'll see fundamental issues with the web platform for which you can propose fixes!
** if this is your first web API, work with a co-editor that has bandwidth to help you.
** if this is your first web API, work with a co-editor that has bandwidth to help you.
* publicly discuss & document use-cases, motivations, and design sketches early, often, and widely (e.g. [[IRC]], applicable W3C/WHATWG lists, [https://lists.mozilla.org/listinfo/dev-webapi dev-webapi], [https://lists.mozilla.org/listinfo/dev-platform dev-platform], [https://lists.mozilla.org/listinfo/dev-gaia dev-gaia], blogs, Twitter, GitHub issues, etc.).
* publicly discuss & document use-cases, motivations, and design sketches early, often, and widely (e.g. [[IRC]], wiki (here on WikiMo or http://wiki.whatwg.org/ ), applicable W3C/WHATWG lists, [https://lists.mozilla.org/listinfo/dev-webapi dev-webapi], [https://lists.mozilla.org/listinfo/dev-platform dev-platform], [https://lists.mozilla.org/listinfo/dev-gaia dev-gaia], blogs, Twitter, GitHub issues, etc.).
* avoid scope creep by avoiding trying to fix unrelated problems.
* avoid scope creep by avoiding trying to fix unrelated problems.
** For an example of what NOT to do, see Google's "Web Intents", which scope creeped to try solve all data-to-code-or-service binding/launching problems.
** For an example of what NOT to do, see Google's "Web Intents", which scope creeped to try solve all data-to-code-or-service binding/launching problems.
canmove, Confirmed users
2,887

edits

Navigation menu