Category:Proposals - Revision history

Kenrussell: Deleting temporary WorkerCanvas2 link

2015-01-27T20:33:36Z

Deleting temporary WorkerCanvas2 link

← Older revision		Revision as of 20:33, 27 January 2015
Line 4:		Line 4:

	[[Category:Spec coordination]]		[[Category:Spec coordination]]
	~~[[WorkerCanvas2]]~~

Kenrussell: Temporary link to create a new page

2015-01-27T20:32:26Z

Temporary link to create a new page

← Older revision		Revision as of 20:32, 27 January 2015
Line 4:		Line 4:

	[[Category:Spec coordination]]		[[Category:Spec coordination]]
			[[WorkerCanvas2]]

GPHemsley: added Category:Spec coordination using HotCat

2013-07-09T13:40:58Z

added Category:Spec coordination using HotCat

← Older revision		Revision as of 13:40, 9 July 2013
Line 2:		Line 2:

	You do not have to provide detailed answers for everything straight away. The most important information to provide at first is the problem description. Once we have detailed descriptions, use cases and an understanding of the limitations with existing markup, we can then begin to discuss the best way in which to address the problems and work out more of the more technical details.		You do not have to provide detailed answers for everything straight away. The most important information to provide at first is the problem description. Once we have detailed descriptions, use cases and an understanding of the limitations with existing markup, we can then begin to discuss the best way in which to address the problems and work out more of the more technical details.

			[[Category:Spec coordination]]

Annevk: does not need to be a subcategory

2011-01-26T12:53:24Z

does not need to be a subcategory

← Older revision		Revision as of 12:53, 26 January 2011
Line 2:		Line 2:

	You do not have to provide detailed answers for everything straight away. The most important information to provide at first is the problem description. Once we have detailed descriptions, use cases and an understanding of the limitations with existing markup, we can then begin to discuss the best way in which to address the problems and work out more of the more technical details.		You do not have to provide detailed answers for everything straight away. The most important information to provide at first is the problem description. Once we have detailed descriptions, use cases and an understanding of the limitations with existing markup, we can then begin to discuss the best way in which to address the problems and work out more of the more technical details.

	~~[[Category:Spec coordination]]~~

Annevk: teehee new better named category

2011-01-26T12:14:39Z

teehee new better named category

New page

This is a collection of proposals for [[specs]]. Before drafting a proposal, please read [[FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F|Is there a process for adding new features to a specification?]]. If you want to add a feature request, start by copying the [[Problem Solving]] template page onto a new page and fill out as much information as you can.

You do not have to provide detailed answers for everything straight away. The most important information to provide at first is the problem description. Once we have detailed descriptions, use cases and an understanding of the limitations with existing markup, we can then begin to discuss the best way in which to address the problems and work out more of the more technical details.

[[Category:Spec coordination]]