how-to-play-2 - Revision history

Tantek: Protected "how-to-play-2" [edit=sysop:move=sysop]

2013-04-04T00:45:42Z

Protected "how-to-play-2" [edit=sysop:move=sysop]

← Older revision	Revision as of 00:45, 4 April 2013
(No difference)

Tantek: Reverted edits by ABIDEEN1 (Talk) to last version by Tantek

2013-04-04T00:45:36Z

Reverted edits by ABIDEEN1 (Talk) to last version by Tantek

Show changes

ABIDEEN1 at 00:25, 4 April 2013

2013-04-04T00:25:01Z

Show changes

Tantek: Reverted edits by Heecfyahoo.ca (Talk) to last version by Petershank

2013-02-22T07:49:05Z

Reverted edits by Heecfyahoo.ca (Talk) to last version by Petershank

Show changes

Heecfyahoo.ca at 06:25, 22 February 2013

2013-02-22T06:25:09Z

Show changes

Petershank: /* In General */ copyedit for clarity

2010-04-20T23:23:53Z

In General: copyedit for clarity

← Older revision		Revision as of 23:23, 20 April 2010
Line 23:		Line 23:
	==In General==		==In General==

	Thanks for getting involved in microformats development! This page ~~exists to help~~ you find your feet, sets out the methods we use to work productively, ~~along with~~ a few ground rules and expectations. If this is your first visit, please see the [[introduction]] page, too.		Thanks for getting involved in microformats development! This page helps you find your feet, sets out the methods we use to work productively, and provides a few ground rules and expectations. If this is your first visit, please see the [[introduction]] page, too.

	The most important ~~rule~~ to ~~foster~~ a healthy, productive open community?		The most important rules to fostering a healthy, productive open community:

	1. '''Be nice.'' You are expected, and should expect in return, ~~the people in this community~~ to act positively and treat ~~one another~~ with respect. ~~You should not assume ill-~~intent ~~in communications~~; ~~especially~~ in scientific~~, precise~~ debate as ~~can occur~~ in standards development, you should be careful not to perceive ~~someone~~'s tone ~~aggressively~~, and ~~should~~ be careful not to give that impression, either.		1. ''Be nice.'' You are expected, and should expect in return, to act positively and treat your fellow members of this community with respect. Assume good intent; in precise scientific debate (as frequently occurs in standards development) you should be careful not to automatically perceive another person's tone as aggressive, even when they feel strongly about their opinions and statements. Conversely, be careful not to give that impression, either.

	2. Microformat documentation (including the specifications) is released into the public domain. This mostly affects content on this wiki, but we encourage complete, open release of as much ~~microformats~~ related material as possible. We ask that users active before 2008 consider adding the [[Template:cc-public-domain-release]] to ~~your~~ User Page ~~to release your~~ contributions to microformats.org prior to 2008 into the public domain.		2. Microformat documentation (including the specifications) is released into the public domain. This mostly affects content on this wiki, but we encourage complete, open release of as much microformat-related material as possible. We ask that users active before 2008 consider adding the [[Template:cc-public-domain-release]] to their User Page so that their contributions to microformats.org made prior to 2008 will be released into the public domain .

	# When giving general examples, ensure that you use valid HTML or XHTML		# When giving general examples, ensure that you use valid HTML or XHTML
Line 40:		Line 40:
	# Use <nowiki>example.org</nowiki> for hypothetical URL examples rather than a presumed-fake domain name (which may eventually be registered, used for spam etc.) On the wiki, wrap example domains in <code><nowiki></code> elements so that the URLs are not converted into hyperlinks, e.g.: <code><nowiki><nowiki>http://example.org/</nowiki></nowiki></code>.		# Use <nowiki>example.org</nowiki> for hypothetical URL examples rather than a presumed-fake domain name (which may eventually be registered, used for spam etc.) On the wiki, wrap example domains in <code><nowiki></code> elements so that the URLs are not converted into hyperlinks, e.g.: <code><nowiki><nowiki>http://example.org/</nowiki></nowiki></code>.
	#* Use different domain suffixes or sub-domains to show interactions between domains: <nowiki>example.net</nowiki> or <nowiki>example.com</nowiki> or <nowiki>foo.example.org</nowiki> and <nowiki>bar.example.org</nowiki>.		#* Use different domain suffixes or sub-domains to show interactions between domains: <nowiki>example.net</nowiki> or <nowiki>example.com</nowiki> or <nowiki>foo.example.org</nowiki> and <nowiki>bar.example.org</nowiki>.


	==On the Wiki==		==On the Wiki==

BenWard: /* On the Wiki */ Fixed wrapping bullet point

2009-06-24T23:31:04Z

On the Wiki: Fixed wrapping bullet point

← Older revision		Revision as of 23:31, 24 June 2009
Line 50:		Line 50:
	# The microformats wiki exists to document microformats and some closely associated technologies and areas, namely [[POSH]], [[picoformats]]. Discussion in directly related areas and applications of microformats (in line with the [[principals\|microformats principals]] such as [[data-portability]] is also encouraged. Be aware that off-topic pages may be deleted. If in doubt, ask.		# The microformats wiki exists to document microformats and some closely associated technologies and areas, namely [[POSH]], [[picoformats]]. Discussion in directly related areas and applications of microformats (in line with the [[principals\|microformats principals]] such as [[data-portability]] is also encouraged. Be aware that off-topic pages may be deleted. If in doubt, ask.

	# Please use <abbr title="United States">U.S.</abbr> English ([[en-US]]) spelling for English documentation. This is by convention, following the [http://www.w3.org/2001/06/manual/#Spelling W3C Manual of Style Spelling Editorial Guideline]. #* With exception of: Proper native spellings of proper nouns, e.g. "BT Centre", "Business Design Centre, London, UK", "Centre of Canadian Studies".		# Please use <abbr title="United States">U.S.</abbr> English ([[en-US]]) spelling for English documentation. This is by convention, following the [http://www.w3.org/2001/06/manual/#Spelling W3C Manual of Style Spelling Editorial Guideline].
			#* With exception of: Proper native spellings of proper nouns, e.g. "BT Centre", "Business Design Centre, London, UK", "Centre of Canadian Studies".
	#* With exception of: Contributions to discussion content (content signed content within <code><div class="discussion"></code> blocks), which may be spelled in the author's native English.		#* With exception of: Contributions to discussion content (content signed content within <code><div class="discussion"></code> blocks), which may be spelled in the author's native English.

BenWard: Note about the broken OL numbering (I'm using extra line breaks for editing legibility). Please don't fix yet!

2009-06-22T09:26:42Z

Note about the broken OL numbering (I'm using extra line breaks for editing legibility). Please don't fix yet!

← Older revision		Revision as of 09:26, 22 June 2009
Line 1:		Line 1:
	'''This page is a work-in-progress, draft rewrite of [[how-to-play]]. The aim is to produce a document that's clearer to newcomers, and better structured in general. The initial version of the page is a direct copy of the current how-to-play, and will be modified from there on.'''		'''''This page is a work-in-progress, draft rewrite of [[how-to-play]]'''. The aim is to produce a document that's clearer to newcomers, and better structured in general. The initial version of the page is a direct copy of the current how-to-play, and will be modified from there on.''

			Note that the numbering of each item is not finalized, and the auto-numbering of lists is broken up by line breaks to favour legibility in editing the document for the time being. (Numbering will be resolving later.)

	==Sections:==		==Sections:==

BenWard: First steps of breaking existing how to play rules into sections, reoordering to improve comprehension, reworking some phrasing, making some more concise, and removing references to individuals.

2009-06-22T09:23:53Z

First steps of breaking existing how to play rules into sections, reoordering to improve comprehension, reworking some phrasing, making some more concise, and removing references to individuals.

Show changes

BenWard: Sketched out possible sections for new how-to-play

2009-06-22T07:52:12Z

Sketched out possible sections for new how-to-play

← Older revision		Revision as of 07:52, 22 June 2009
Line 1:		Line 1:
	'''This page is a work-in-progress, draft rewrite of [[how-to-play]]. The aim is to produce a document that's clearer to newcomers, and better structured in general. The initial version of the page is a direct copy of the current how-to-play, and will be modified from there on.'''		'''This page is a work-in-progress, draft rewrite of [[how-to-play]]. The aim is to produce a document that's clearer to newcomers, and better structured in general. The initial version of the page is a direct copy of the current how-to-play, and will be modified from there on.'''

	~~__NOTOC__~~		==Sections:==

			* In general
			** General guidelines that apply to all mediums, general attitude
			** Key pieces of information that people should ensure they understand before participating
			* On the wiki
			** Wiki specific guidelines, concerning page creation/editing/etc.
			* On mailing lists
			** Link to mailing lists page, but also give brief intro to them, such that people get a decent idea of what they're for/why they're here from reading this page.
			* In IRC
			** IRC specific stuff
			* Creating new microformats
			** Link to The Process, but provide brief overview to cover the gotchas of creating new microformats, since some devs will arrive at this page because they want to create a new format.

	If this is your first visit, please see the [[introduction]] page.		If this is your first visit, please see the [[introduction]] page.
	~~<entry-title>How to Play</entry-title>~~
	== Guidelines ==		== Guidelines ==
	Before contributing please observe these guidelines:		Before contributing please observe these guidelines: