Style Issue: Difference between revisions
(StyleIssue (Imported from MoinMoin)) |
((Imported from MoinMoin)) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
==How should I list a style isue?== |
==How should I list a style isue?== |
||
[[Image:Attention.png]] ''This is a first draft of the issue |
[[Image:Attention.png]] ''This is a first draft of the issue tracking process in this wiki.'' |
||
You can list it on [[Minor Style Issue|MinorStyleIssue]]. '''But''' this page is not well maintained, and the issue will probably not get much attention and therefore not get fixed. |
You can list it on [[Minor Style Issue|MinorStyleIssue]]. '''But''' this page is not well maintained, and the issue will probably not get much attention and therefore not get fixed. |
||
| Line 23: | Line 23: | ||
The very important [[Open Style Issue|OpenStyleIssue]]<code><nowiki></nowiki></code>s get an ''additional''<code><nowiki>CategoryHighPriorityOpenStyleIssue</nowiki></code>. The page [[High Priority Open Style Issue|HighPriorityOpenStyleIssue]] is one of the exceptions to the no-lists rule above. Since these issues are of high priority, there will not only be an automated list, but also a human-maintained list with short descriptions. |
The very important [[Open Style Issue|OpenStyleIssue]]<code><nowiki></nowiki></code>s get an ''additional''<code><nowiki>CategoryHighPriorityOpenStyleIssue</nowiki></code>. The page [[High Priority Open Style Issue|HighPriorityOpenStyleIssue]] is one of the exceptions to the no-lists rule above. Since these issues are of high priority, there will not only be an automated list, but also a human-maintained list with short descriptions. |
||
[[User:mo|mo]] has volunteered to take care of [[Style Issues|StyleIssues]]. He has no special authority, but he will simply be the guy who does the work: keeping track of discussions on |
[[User:mo|mo]] has volunteered to take care of [[Style Issues|StyleIssues]]. He has no special authority, but he will simply be the guy who does the work: keeping track of discussions on the [[Style Mailing List|StyleMailingList]], adding new pages as needed into the above scheme and describing the issues. |
||
Deciding upon prioities is something that should be done based on rough consensus within the [[Style Council|StyleCouncil]] and with the [[Main Developer|MainDeveloper]]<code><nowiki></nowiki></code>s. |
Deciding upon prioities is something that should be done based on rough consensus within the [[Style Council|StyleCouncil]] and with the [[Main Developer|MainDeveloper]]<code><nowiki></nowiki></code>s. |
||
Revision as of 21:09, 3 October 2005
Style issues are problems of any kind with the current OfficialStyleGuidelines. They get listed on the pages around here:
Warning: This feature is very experimental, it might get completely refactored or even deleted
How should I list a style isue?
This is a first draft of the issue tracking process in this wiki.
You can list it on MinorStyleIssue. But this page is not well maintained, and the issue will probably not get much attention and therefore not get fixed.
Never ever create a list of StyleIssues on any other page. (exceptions might come up over time :-) )
Ideally create a page with a GoodWikiName that describes the issue. Then you assign CategoryOpenStyleIssue to that page. And whoopla, it gets added to the automatic list on OpenStyleIssues. And for God's sake, please intertwingle the page.
Issues that are not going to be fixed or are not really issues that the StyleCouncil thinks to be worth spending thoughts on will get CategoryNoStyleIssue. They can still remain in the wiki, be linked to and discussed. Perhaps one day they become an issue again...
An issue that got fixed remains in the wiki. It just gets assigned CategoryClosedStyleIssue.
The very important OpenStyleIssues get an additionalCategoryHighPriorityOpenStyleIssue. The page HighPriorityOpenStyleIssue is one of the exceptions to the no-lists rule above. Since these issues are of high priority, there will not only be an automated list, but also a human-maintained list with short descriptions.
mo has volunteered to take care of StyleIssues. He has no special authority, but he will simply be the guy who does the work: keeping track of discussions on the StyleMailingList, adding new pages as needed into the above scheme and describing the issues.
Deciding upon prioities is something that should be done based on rough consensus within the StyleCouncil and with the MainDevelopers.
