FANDOM


(List of pages that do need Cleanups)
Line 1: Line 1:
 
<div style="width: 100%; background: #dbf3ff; margin: 10px 0px; padding: 10px 0px; text-align: center">
 
<div style="width: 100%; background: #dbf3ff; margin: 10px 0px; padding: 10px 0px; text-align: center">
<font size=3>Any help improving the articles nominated on this page is greatly appreciated.</font><br>See the [[PvXwiki:Style and formatting|style and formatting]] guides for editing help.</div>
+
<font size=3> The Quality Controll Inititive</font><br>See the [[PvXwiki:Style and formatting|style and formatting]] guides for editing help.</div>
 
{{TOCright}}
 
{{TOCright}}
 
[[Category:Community projects]]
 
[[Category:Community projects]]
 
[[Category:Cleanup]]
 
[[Category:Cleanup]]
 
==Purpose==
 
==Purpose==
The Build Stubs and Quality Control project is a child of [[PvXwiki:Improvement Drive]]. It is here to document the site standard in build formatting and presentation, give precedure and examples of how to place cleanup tags and assist in improving the overall quality of every build article on PvX Wiki.
 
   
Shortly after the implimentation of [[PvX:Real Vetting]] the entire untested build section underwent an quality control sweep to help identify those builds that had been created during the large block of 'stagnant' time that still needed a little (or a lot) of general improvement in the presentation of the information available in those builds. After this point, Presentation Quality, was given a higher degree of necessity in order for a build to be considered for vetting.
+
The Build Stubs and Quality Control project is a child of [[PvXwiki:Improvement Drive]]. It is an attempt to organize and maintain a driving movement to uphold the basic quality standards of formating that every article on this wiki should posess.
   
This project is not here to define what makes a build good or bad, in the ways of game mechanics, but rather what constitues the standard in build presentation.
+
By mandating and upholding a minimum level of Article Quality the wiki will achive a greater overall success. Articles will be esier to read and refrence, knowledge and understanding of builds amongst contributors will increase, and overall the site will become much more pleasing to the eye. Also, if everyone reaches the same minimum level of build formatting, more emphasis is given to the build it'self, which in turn will garning more accurate results from the vetting system.
   
  +
This inititive is <b>not</b> to screen builds out of the vetting process, on the contrary it's here to assist in the improvement of those builds to the point that people are seeing the build mechanics instead of the poor build formatting, allowing for a more honest rating of the build and it's capabilities.
   
== The Cleanup Tag ==
+
On 01 July 2007; shortly after the implimentation of [[PvX:Real Vetting]], the entire untested and trial build sections underwent an quality control sweep to help identify those builds that had been created during the large block of stagnant time between migration and vetting policy implimentation. Following this sweep any Admin who views build found to be of inferior quality in Trial or Untested sections may choose have a cleanup tag placed onto the build and the build sent back to stubs. Included in this tag will be a detailed explination of what is wrong with the formatting of the build and the initial responsibility to fix the build will rest on the author. When the formatting is fixed, regardless of the build makeup of the article, it will be elidgable to be sent to untested or trial phases at the initiative of the author.
   
The existance of the Templates {cleanup| Explination} and {Cleanup2| Explination1 | Explination2} is to help identify those builds that do not meet minimun standards in formatting, presentation, and style. You place these tags onto a build in an attempt to assist in improving the build in those areas.
+
As I stated earlier it is the initial responsibility of the build author to try and fix the page. I ask this because people learn more by doing than by having it done for them. That being said however, they may ask for assistance from an admin, and depending on the user level of the author, an Admin will assist that author appropriately to get their build up to formatting standard.
   
It is not there to mark or distinguish good or bad builds from one another, the vetting sytem is used for that.
 
   
In most cases, a Cleanup tag placed on a build IS grounds for that build to be moved out of Testing or Trial status and directly into stubs untill the build is fixed. It is highly encouraged that whomever places such a tag be available to assist the author in cleaning up and improving the build to an appropriate standard.
 
   
== Examples of Quality Formatting and Presentation ==
+
== What is the Formatting Standard ==
   
List links to the style guides.
+
We have several guides that dictate those standards we are to uphold:
  +
* [[PvXwiki:Style and formatting|Style and formatting]] &ndash; Guide for writing a build article, including an example ready for copy & paste.
  +
* [[PvXwiki:Writing good builds|Writing good builds]] &ndash; More notes on how to write a build that meets the standards and expectations of PvXwiki.
  +
* [[PvXwiki:Build Naming Policy|Build Naming Policy]] &ndash; Understanding the syntax for naming build articles.
   
Give verbal explinations of what people want to see: Conciseness, bulleted items, 3rd person, little chatter, visual refrences, propper organization.
+
== Examples of high quality formatted builds ==
   
* The PvP Build
+
== Those individuals who have made a pledge to assist in the Build Stubs Quality Control Program ==
* The Team Build
 
* The PvE Build
 
* The Guide
 
* The Farming Build
 
* The ??? Build
 
 
== Examples of Bad Formatting ==
 
 
Examples of bad formatting, and what to place in the delete tag.
 
 
== List of pages that do need Cleanups ==
 
 
[[Category:Cleanup|Cleanup]]
 
 
== Those individuals who have made a pledge to assist int he Build Stubs Quality Control Program ==
 
   
 
# ''''[[User:Shireen|<font face="arial" color="Green">Shireen</font>]]<small>[[PvXwiki:Administrators|sysop]]</small>''''
 
# ''''[[User:Shireen|<font face="arial" color="Green">Shireen</font>]]<small>[[PvXwiki:Administrators|sysop]]</small>''''

Revision as of 22:49, July 2, 2007

The Quality Controll Inititive
See the style and formatting guides for editing help.

Purpose

The Build Stubs and Quality Control project is a child of PvXwiki:Improvement Drive. It is an attempt to organize and maintain a driving movement to uphold the basic quality standards of formating that every article on this wiki should posess.

By mandating and upholding a minimum level of Article Quality the wiki will achive a greater overall success. Articles will be esier to read and refrence, knowledge and understanding of builds amongst contributors will increase, and overall the site will become much more pleasing to the eye. Also, if everyone reaches the same minimum level of build formatting, more emphasis is given to the build it'self, which in turn will garning more accurate results from the vetting system.

This inititive is not to screen builds out of the vetting process, on the contrary it's here to assist in the improvement of those builds to the point that people are seeing the build mechanics instead of the poor build formatting, allowing for a more honest rating of the build and it's capabilities.

On 01 July 2007; shortly after the implimentation of PvX:Real Vetting, the entire untested and trial build sections underwent an quality control sweep to help identify those builds that had been created during the large block of stagnant time between migration and vetting policy implimentation. Following this sweep any Admin who views build found to be of inferior quality in Trial or Untested sections may choose have a cleanup tag placed onto the build and the build sent back to stubs. Included in this tag will be a detailed explination of what is wrong with the formatting of the build and the initial responsibility to fix the build will rest on the author. When the formatting is fixed, regardless of the build makeup of the article, it will be elidgable to be sent to untested or trial phases at the initiative of the author.

As I stated earlier it is the initial responsibility of the build author to try and fix the page. I ask this because people learn more by doing than by having it done for them. That being said however, they may ask for assistance from an admin, and depending on the user level of the author, an Admin will assist that author appropriately to get their build up to formatting standard.


What is the Formatting Standard

We have several guides that dictate those standards we are to uphold:

  • Style and formatting – Guide for writing a build article, including an example ready for copy & paste.
  • Writing good builds – More notes on how to write a build that meets the standards and expectations of PvXwiki.
  • Build Naming Policy – Understanding the syntax for naming build articles.

Examples of high quality formatted builds

Those individuals who have made a pledge to assist in the Build Stubs Quality Control Program

  1. 'Shireensysop'
Community content is available under CC-BY-NC-SA 2.5 unless otherwise noted.