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 Chat (such as one of these permanent autoconfirmed members).

FAQ: Difference between revisions

From WHATWG Wiki
Jump to navigation Jump to search
(Drop Outlook question, it's very unlikely to be read and useful again)
(Replaced content with "{{moved|the [https://whatwg.org/faq WHATWG FAQ], the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ], and the [https://whatwg.org/mailing-list WHATWG...")
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{moved|the [https://whatwg.org/faq WHATWG FAQ] and the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ]}}
{{moved|the [https://whatwg.org/faq WHATWG FAQ], the [https://github.com/whatwg/html/blob/master/FAQ.md HTML Standard FAQ], and the [https://whatwg.org/mailing-list WHATWG Mailing List] page.}}
 
== Mailing List ==
 
=== +1 ===
 
Please note that content-free agreement (such as +1s) have no effect on
the WHATWG list and are therefore discouraged. Editors of specs discussed
in the WHATWG only consider the quality of the arguments presented, and  
not the volume of agreement.
 
You should therefore only post to the list if you have a substantive new point
to make, for example if you have seen a flaw in an argument presented so far,
or have a new idea to contribute, or have some information that has not yet
been brought to the table.
 
=== Should I top-post or reply inline? ===
 
'''Please reply inline or make the reply self-contained, and trim extraneous quotes from previous emails in your replies.'''
 
Basically, please remove anything after the last line you have written, so that people don't have to scroll down to find out what else you wrote, and make sure that your email makes sense on its own, as it will probably be read out of context years later.
 
That is, you should reply like this:
 
<pre>
Ian wrote:
> What do you want?
 
I want cats!
 
> When do you want it?
 
Now!
</pre>
 
You should definitely not reply like this (because this requires people to read your email backwards):
 
<pre class="error" >
No
 
Ian wrote:
> Is this a good example of how to post emails?
</pre>
 
You should also not reply like this (because this leaves people to wonder if there is any text lower down that you have written):
 
<pre class="error" >
This is a bad way to write email.
 
Ian wrote:
> Is this a good way to write email?
> Lorem ipsum foo bar baz.
> Unrelated other bits that aren't replied to.
> Yet more text
</pre>
 
You should also not reply like this (with no context at all), because the reader will not know what you are referring to:
 
<pre class="error" >
No, I think that's a bad idea. It wouldn't be good for the readers, for instance.
</pre>
 
Quote enough original text or provide an introduction yourself.

Latest revision as of 17:34, 24 January 2018

This page has moved to the WHATWG FAQ, the HTML Standard FAQ, and the WHATWG Mailing List page.