A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "What you can do"

From WHATWG Wiki
Jump to: navigation, search
(Sending feedback)
(update this page as the rationale document now exists)
Line 4: Line 4:
 
* Write [[HTML5 tutorial|tutorials]] for new authors and for authors moving to HTML5.
 
* Write [[HTML5 tutorial|tutorials]] for new authors and for authors moving to HTML5.
 
* Monitor and respond to questions on [http://www.whatwg.org/mailing-list#help the help list] and [http://forums.whatwg.org/ the forums].
 
* Monitor and respond to questions on [http://www.whatwg.org/mailing-list#help the help list] and [http://forums.whatwg.org/ the forums].
* Maintain a document explaining the rationale of the decisions behind the spec. If you're interested in doing that, please e-mail Ian Hickson (ian@hixie.ch). '''This would be very popular. We get requests for this all the time. We just haven't found someone with the time to do it.''' (See below for details.)
+
* Maintain the document explaining the [[rationale]] of the decisions behind the spec. (See below for details.)
 
* Help to edit the [[FAQ]].
 
* Help to edit the [[FAQ]].
 
* Write [[test cases]].
 
* Write [[test cases]].
Line 23: Line 23:
  
 
It basically would consist of watching the e-mail lists, the bugzilla
 
It basically would consist of watching the e-mail lists, the bugzilla
bugs, and IRC, and chatting with Hixie, and then writing documentation to
+
bugs, IRC, and chatting with Hixie, and then writing documentation to
explain the thinking behind different parts of the spec — probably on this
+
explain the thinking behind different parts of the spec on the [[rationale]] page.
wiki somewhere.
 
  
 
It could be as little work or as much work as you would want it to be. One
 
It could be as little work or as much work as you would want it to be. One
 
could easily imagine this becoming a group effort.
 
could easily imagine this becoming a group effort.

Revision as of 20:35, 5 May 2010

So you want to take part? You can!

Sending feedback

The most useful thing from an authoring standpoint would be going through the spec and finding bits that don't make sense. Start with the authoring view:

http://whatwg.org/html?style=author

Then use the widget at the bottom right (it says "Click the location of the error to select it, then type your message here:") to submit review comments on the spec. The best review comments are those along the lines of questions you couldn't find the answer to. For example, say you wanted to find out what elements you could put in a <p> element, and you couldn't work it out. Then you would file a bug "I couldn't find the answer to the question 'What elements are allowed inside <p> elements'.".

See also Reviewing HTML5.

A rationale document

It basically would consist of watching the e-mail lists, the bugzilla bugs, IRC, and chatting with Hixie, and then writing documentation to explain the thinking behind different parts of the spec on the rationale page.

It could be as little work or as much work as you would want it to be. One could easily imagine this becoming a group effort.