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).
Category:Feature Request: Difference between revisions
No edit summary |
No edit summary |
||
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]] |
Revision as of 12:03, 26 January 2011
This is a collection of proposals for specs. Before drafting a proposal, please read 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 and add this category using [[Category:Feature Request]]
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.
This category currently contains no pages or media.