What you can do - Revision history

Zcorpan: Fix [GitHub repositories] link (thanks xfq)

2017-08-24T12:12:39Z

Fix [GitHub repositories] link (thanks xfq)

← Older revision		Revision as of 12:12, 24 August 2017
Line 20:		Line 20:
	== A rationale document ==		== A rationale document ==

	It basically would consist of watching the [~~GitHub repositories](~~https://github.com/whatwg) that are of interest,		It basically would consist of watching the [https://github.com/whatwg GitHub repositories] that are of interest,
	asking questions on [[IRC]], and then writing documentation to		asking questions on [[IRC]], and then writing documentation to
	explain the thinking behind different parts of the spec on the [[rationale]] page.		explain the thinking behind different parts of the spec on the [[rationale]] page.

Zcorpan: Brush up this page to not be so out of date

2017-08-24T08:30:04Z

Brush up this page to not be so out of date

← Older revision		Revision as of 08:30, 24 August 2017
Line 2:		Line 2:
	* Review [http://whatwg.org/specs/ the specifications] and [http://whatwg.org/mailing-list#specs send comments]! (See below for details.)		* Review [http://whatwg.org/specs/ the specifications] and [http://whatwg.org/mailing-list#specs send comments]! (See below for details.)
	* Write articles for our [http://blog.whatwg.org/ blog].		* Write articles for our [http://blog.whatwg.org/ blog].
	* Write [[Authoring\|tutorials]] for new ~~authors.~~		* Write [[Authoring\|tutorials]] for new web developers.
	* Monitor and respond to questions on [http://www.whatwg.org/mailing-list#help the help list] and [http://forums.whatwg.org/ the forums] ([http://forums.whatwg.org/bb3/search.php?search_id=unanswered unanswered topics]).
	* Maintain the document explaining the [[rationale]] of the decisions behind the spec. (See below for details.)		* Maintain the document explaining the [[rationale]] of the decisions behind the spec. (See below for details.)
	* Write [[test cases]].		* Write [[test cases]].
Line 13:		Line 12:
	The most useful thing would be going through the spec and finding bits that don't make sense.		The most useful thing would be going through the spec and finding bits that don't make sense.

	~~http~~://whatwg.org/~~html~~		https://html.spec.whatwg.org/multipage/

	You can 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'.".		You can use the link at the bottom (it says "File an issue about the selected text") 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]].'''		'''See also [[Reviewing]].'''
Line 21:		Line 20:
	== A rationale document ==		== A rationale document ==

	It basically would consist of watching the ~~e-mail lists~~, ~~the Bugzilla~~		It basically would consist of watching the [GitHub repositories](https://github.com/whatwg) that are of interest,
	~~bugs,~~ asking questions on [[IRC]], and then writing documentation to		asking questions on [[IRC]], and then writing documentation to
	explain the thinking behind different parts of the spec on the [[rationale]] page.		explain the thinking behind different parts of the spec on the [[rationale]] page.

Line 30:		Line 29:
	= How you can improve HTML =		= How you can improve HTML =

	''This ~~is the~~ text of an article Hixie wrote.''		''This text originated from an article Hixie wrote.''

	Are you trying to do something on the Web that you find you can't do because HTML simply doesn't have a way to do it?		Are you trying to do something on the Web that you find you can't do because HTML simply doesn't have a way to do it?

	With your help, we can improve HTML, add a feature to address your problem, and in ~~five to ten~~ years you'll finally be able to do it!		With your help, we can improve HTML, add a feature to address your problem, and in a few years you'll finally be able to do it!

	Here's how:		Here's how:
Line 50:		Line 49:
	Next, do one or more of the following with this description:		Next, do one or more of the following with this description:

	0. Discuss the topic on our [[IRC]] channel (#whatwg on Freenode) to see if you've missed anything obvious		* Discuss the topic on our [[IRC]] channel (#whatwg on Freenode) to see if you've missed anything obvious
			* Post it as an issue at http://whatwg.org/newbug

	~~1. Post it to whatwg@whatwg.org~~		Participate in any resulting discussions. Post a link to your issue to your own blog or to other social media sites to

	~~2. Post it on http://forums.whatwg.org/~~

	~~3. Post it on our blog http://blog.whatwg.org/ (ask for an account on our IRC channel, #whatwg on Freenode)~~

	~~4. Post it as a bug report at http://whatwg.org/newbug (you'll need to create an account)~~

	Participate in any resulting discussions. Post a link to your ~~e-mail, forum post, blog post, or bug report~~ to your own blog or to other social media sites to
	encourage others to participate. For best results, I recommend that you avoid creating new places for the discussion to occur (e.g. new mailing lists, wiki		encourage others to participate. For best results, I recommend that you avoid creating new places for the discussion to occur (e.g. new mailing lists, wiki
	pages, or working groups). Keeping the discussions in existing places ensures that experience participants will see your discussions and will be able to		pages, or working groups). Keeping the discussions in existing places ensures that experience participants will see your discussions and will be able to
Line 71:		Line 63:
	(You don't have to, though, and there's no guarantee that the solutions you propose will be adopted rather than some other ones.)		(You don't have to, though, and there's no guarantee that the solutions you propose will be adopted rather than some other ones.)

	~~If you posted on the forums or on~~ the ~~blog~~, ~~then once the discussion has settled down, ask for someone (e.g. zcorpan, for the forums, or whoever you spoke to on~~		When it comes to updating the standard, see https://whatwg.org/working-mode for what the process is. It boils down to writing a pull request for the standard and
	~~IRC, for the blog) to forward your proposal to the main whatwg@~~whatwg.org ~~mailing list. This will get~~ the ~~topic onto my (Hixie's) radar~~. ~~(Bugs are all already~~		writing test cases, and getting support from implementers.
	~~also on the radar, so you don't have~~ to ~~worry about those.)~~

	~~Eventually, I will see the e-mail(s) or bug. This can take~~ a ~~few months, because there's a lot of feedback to go through. I then take all the information in~~ the
	~~thread, related forum posts and blog posts,~~ and ~~anything else I can find; I sometimes talk to browser vendors, bring the topic up on IRC for some sanity checking~~
	~~with whoever is online, etc. And then I write a reply to all the e-mails~~, and ~~possibly update the spec accordingly. Lather, rinse, repeat~~.

	You may ask why browser vendors have a prominent role in this process. The answer is simple. The specification is not magical; it cannot force browser vendors to		You may ask why browser vendors have a prominent role in this process. The answer is simple. The specification is not magical; it cannot force browser vendors to
Line 86:		Line 73:

	If you want to participate in the process in ways other than reporting problems you find with the Web, there are various things you can do: participate in		If you want to participate in the process in ways other than reporting problems you find with the Web, there are various things you can do: participate in
	discussions on ~~the mailing list, forums, blog, or bug system~~; chat with us on IRC (#whatwg on Freenode); write test cases; write tutorials; review the spec...		discussions on GitHub; chat with us on IRC (#whatwg on Freenode); write test cases; write tutorials; review the spec...
	The best place to start is to join us on IRC and ask what you can do.		The best place to start is to join us on IRC and ask what you can do.

	We also have a FAQ: ~~http~~://~~wiki.~~whatwg.org/~~wiki/FAQ~~		We also have a FAQ: https://whatwg.org/faq

Philipj at 13:31, 11 August 2017

2017-08-11T13:31:04Z

← Older revision		Revision as of 13:31, 11 August 2017
Line 5:		Line 5:
	* Monitor and respond to questions on [http://www.whatwg.org/mailing-list#help the help list] and [http://forums.whatwg.org/ the forums] ([http://forums.whatwg.org/bb3/search.php?search_id=unanswered unanswered topics]).		* Monitor and respond to questions on [http://www.whatwg.org/mailing-list#help the help list] and [http://forums.whatwg.org/ the forums] ([http://forums.whatwg.org/bb3/search.php?search_id=unanswered unanswered topics]).
	* Maintain the document explaining the [[rationale]] of the decisions behind the spec. (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]].
	* Write [[test cases]].		* Write [[test cases]].
	* Write cool demos.		* Write cool demos.

GPHemsley: Eliminate redirect to Specs todo.

2012-10-12T22:06:13Z

Eliminate redirect to Specs todo.

← Older revision		Revision as of 22:06, 12 October 2012
Line 9:		Line 9:
	* Write cool demos.		* Write cool demos.
	* [[:Category:Implementations\|Implement HTML]]!		* [[:Category:Implementations\|Implement HTML]]!
	* Edit one of the many [[companion specifications]] that are lacking editors.		* Edit one of the many [[Specs todo\|companion specifications]] that are lacking editors.

	== Sending feedback ==		== Sending feedback ==

Zcorpan at 10:30, 29 August 2012

2012-08-29T10:30:20Z

← Older revision		Revision as of 10:30, 29 August 2012
Line 3:		Line 3:
	* Write articles for our [http://blog.whatwg.org/ blog].		* Write articles for our [http://blog.whatwg.org/ blog].
	* Write [[Authoring\|tutorials]] for new authors.		* Write [[Authoring\|tutorials]] for new authors.
	* 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] ([http://forums.whatwg.org/bb3/search.php?search_id=unanswered unanswered topics]).
	* Maintain the document explaining the [[rationale]] of the decisions behind the spec. (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]].

Hixie: /* How you can improve HTML */

2012-08-08T22:19:12Z

How you can improve HTML

← Older revision		Revision as of 22:19, 8 August 2012
Line 39:		Line 39:
	Here's how:		Here's how:

	First, write a description of the problem. What are you trying to do? This should be a high-level description. One way to see if you're describing it at a high		First, write a brief user-centric description of the problem. What are you trying to do? This should be a high-level description. One way to see if you're describing it at a high
	enough level is to consider whether your description makes as much sense for a Web developer as it does for, say, a mobile phone native app developer. So if your		enough level is to consider whether your description makes as much sense for a Web developer as it does for, say, a mobile phone native app developer. So if your
	description talks about HTML elements or JavaScript or HTTP headers, then it's probably too low level. If it talks about what a user sees, how a user interacts		description talks about HTML elements or JavaScript or HTTP headers, then it's probably too low level. If it talks about what a user sees, how a user interacts
	with a computer or device, or how a user uses a computer or device to create some sort of content or effect some sort of change, then you're on the right path.		with a computer or device, or how a user uses a computer or device to create some sort of content or effect some sort of change, then you're on the right path.
	If you hear people referring to "use cases", it is to this problem description that they refer.		If you hear people referring to "use cases", it is to this problem description that they refer. Some of the most useful information you can give is examples of what
			people are currently doing to work around the problem (e.g. they're writing native apps instead of Web pages, or they're using Flash or other extensions, etc).

	In particular, your description should not be a solution. Don't propose new elements or attributes, new APIs, new semantics, new features. The time for		In particular, your description should not be a solution. Don't propose new elements or attributes, new APIs, new semantics, new features. The time for
Line 56:		Line 57:
	2. Post it on http://forums.whatwg.org/		2. Post it on http://forums.whatwg.org/

	3. ~~Visit our IRC channel (#whatwg on Freenode) and ask for help posting~~ it on our blog at http://blog.whatwg.org/		3. Post it on our blog http://blog.whatwg.org/ (ask for an account on our IRC channel, #whatwg on Freenode)

	4. Post it as a bug report at http://whatwg.org/newbug (you'll need to create an account)		4. Post it as a bug report at http://whatwg.org/newbug (you'll need to create an account)

Tantek: /* How you can improve HTML */ l IRC

2012-08-08T21:28:27Z

How you can improve HTML: l IRC

← Older revision		Revision as of 21:28, 8 August 2012
Line 50:		Line 50:
	Next, do one or more of the following with this description:		Next, do one or more of the following with this description:

	0. Discuss the topic on our IRC channel (#whatwg on Freenode) to see if you've missed anything obvious		0. Discuss the topic on our [[IRC]] channel (#whatwg on Freenode) to see if you've missed anything obvious

	1. Post it to whatwg@whatwg.org		1. Post it to whatwg@whatwg.org

Hixie: /* How you can improve HTML */

2012-08-08T19:55:03Z

How you can improve HTML

← Older revision		Revision as of 19:55, 8 August 2012
Line 48:		Line 48:
	discussions of solutions is later.		discussions of solutions is later.

	Next, do one of the following with this description:		Next, do one or more of the following with this description:

	0. ~~Optionally, discuss~~ the topic on our IRC channel (#whatwg on Freenode) to see if you've missed anything obvious.		0. Discuss the topic on our IRC channel (#whatwg on Freenode) to see if you've missed anything obvious

	1. Post it to whatwg@whatwg.org		1. Post it to whatwg@whatwg.org

Hixie: /* How you can improve HTML */

2012-08-08T19:54:22Z

How you can improve HTML

← Older revision		Revision as of 19:54, 8 August 2012
Line 49:		Line 49:

	Next, do one of the following with this description:		Next, do one of the following with this description:

			0. Optionally, discuss the topic on our IRC channel (#whatwg on Freenode) to see if you've missed anything obvious.

	1. Post it to whatwg@whatwg.org		1. Post it to whatwg@whatwg.org
Line 54:		Line 56:
	2. Post it on http://forums.whatwg.org/		2. Post it on http://forums.whatwg.org/

	3. Visit ~~the~~ IRC channel #whatwg on Freenode and ask for help posting it on our blog at http://blog.whatwg.org/		3. Visit our IRC channel (#whatwg on Freenode) and ask for help posting it on our blog at http://blog.whatwg.org/

	4. Post it as a bug report at http://whatwg.org/newbug (you'll need to create an account)		4. Post it as a bug report at http://whatwg.org/newbug (you'll need to create an account)

Hixie: /* How you can improve HTML */

2012-08-08T19:50:09Z

How you can improve HTML

← Older revision		Revision as of 19:50, 8 August 2012
Line 56:		Line 56:
	3. Visit the IRC channel #whatwg on Freenode and ask for help posting it on our blog at http://blog.whatwg.org/		3. Visit the IRC channel #whatwg on Freenode and ask for help posting it on our blog at http://blog.whatwg.org/

	4. Post it as a bug report at http://~~goo~~.gl/~~AI6Oc~~ (you'll need to create an account)		4. Post it as a bug report at http://whatwg.org/newbug (you'll need to create an account)

	Participate in any resulting discussions. Post a link to your e-mail, forum post, blog post, or bug report to your own blog or to other social media sites to		Participate in any resulting discussions. Post a link to your e-mail, forum post, blog post, or bug report to your own blog or to other social media sites to