Category talk:Feedback: Difference between revisions
Jump to navigation
Jump to search
m (→Improving these pages: fixed tags) |
m (Robot: fixing template case.) |
||
| Line 6: | Line 6: | ||
* Write up some guidelines on what is a good bug report and what isn't (what info to include, be succinct, etc). | * Write up some guidelines on what is a good bug report and what isn't (what info to include, be succinct, etc). | ||
* Decide on some basic standard page templates for grouping the bugs. E.g. group them by "map errors", "script file errors", "code errors". | * Decide on some basic standard page templates for grouping the bugs. E.g. group them by "map errors", "script file errors", "code errors". | ||
* Implement a rudimentary classification system - class A, B, C. Perhaps some small traffic light icons (red = A, green = C, etc) of similar size to {{ | * Implement a rudimentary classification system - class A, B, C. Perhaps some small traffic light icons (red = A, green = C, etc) of similar size to {{HL2}} could be placed next to each bug, so the list can easily be scan-read. Cosmetic bugs crowding out more serious bugs is the single biggest problem with these lists, imo. | ||
Thoughts? --[[User:Giles|Giles]] 10:23, 7 Jun 2006 (PDT) | Thoughts? --[[User:Giles|Giles]] 10:23, 7 Jun 2006 (PDT) | ||
Latest revision as of 19:25, 19 January 2009
Improving these pages
It strikes me that a lot could be done to improve these pages. There are real signal/noise problems here that, at least in my opinion, are stopping these pages from being as useful as they could be. Some suggestions:
- Separate feature requests and bug reports with subcategories (Category:Feature Requests and Category:Bug Reports).
- Create a
{{bugreport}}template(s) to standardise the intro to the pages and to encourage a common bug report format. - Write up some guidelines on what is a good bug report and what isn't (what info to include, be succinct, etc).
- Decide on some basic standard page templates for grouping the bugs. E.g. group them by "map errors", "script file errors", "code errors".
- Implement a rudimentary classification system - class A, B, C. Perhaps some small traffic light icons (red = A, green = C, etc) of similar size to
could be placed next to each bug, so the list can easily be scan-read. Cosmetic bugs crowding out more serious bugs is the single biggest problem with these lists, imo.
Thoughts? --Giles 10:23, 7 Jun 2006 (PDT)
Previous Discussion
I have a feeling this page won't be seeing any Valve devs. Ever. --Alph Tech STUART 21:10, 2 Jun 2006 (PDT)
- You are wrong... --dutchmega 02:45, 3 Jun 2006 (PDT)