canmove, Confirmed users
2,854
edits
WebAPI/DesignGuidelines: Difference between revisions
→Specification work: use a wiki, see Standards
(see also standards) |
(→Specification work: use a wiki, see Standards) |
||
| Line 50: | Line 50: | ||
If you get the OK from the standards community, go forth and write a specification. | If you get the OK from the standards community, go forth and write a specification. | ||
* have your work in a public location where people can comment and provide patches. | * have your work in a public location where people can comment and provide patches. | ||
** Etherpad, GitHub repo, Google Doc, etc. Anything that's collaborative. | ** Etherpad, Wiki (WikiMo or http://wiki.whatwg.org/ ), GitHub repo, Google Doc, etc. Anything that's collaborative. | ||
* actual standardization decisions will be made by relevant organization. | * actual standardization decisions will be made by relevant organization. | ||
** ex. a W3C Working Group, a W3C Community Group, the WHATWG, the IETF, etc. | ** ex. a W3C Working Group, a W3C Community Group, the WHATWG, the IETF, etc. | ||
** See [[Standards]] for a list of standards groups and organizations. | |||
* follow Mozilla's [[WebAPI/ExposureGuidelines|API exposure guidelines]] (notably sending "Intent to implement" emails). | * follow Mozilla's [[WebAPI/ExposureGuidelines|API exposure guidelines]] (notably sending "Intent to implement" emails). | ||
* carefully follow the processes of the standards organization within which you are working. | * carefully follow the processes of the standards organization within which you are working. | ||