User:Readem/Admin

The Project
Organize the Wiki Administrative Staff, as well as categorize each one. this is currently in development, and may change at a moments notice, due to the probably conflicts/contradictions each branch may possess against one another. After balancing each out, along with help from other adminstrators, this may eventually be implimented.

Please Note:These are not future changes! All concepts may be changes at will! It is merely an example of a possible system of organization! Both User and Admin participation is encouraged! Feel free to make suggestions on the talk page! Do not tamper, unless changing for some benefical purpose! Thanks in advance!

The Divisions
Each Admin to be placed into category:

List of Administrators
 * Gcardinal
 * Armond
 * Eronth
 * Hhhippo
 * Krowman
 * Readem
 * Auron
 * Defiant Elements
 * BrianG
 * Shireen

PR
PR, otherwise known as Public Relations, control banning, as well as solve conflict between users. They are the ones, that handle everyday scenrios. They also act as a source of Communication between users and admins of certain divisions. They have the ability to stop Build deletion, technical changes, as well as Policy (however there must be good reason, as well as solid support from the general public).
 * 1) (Insert Administrator Here)

Policy Adminstrative Staff (PAS)
Has direct control over the creation and removal of PvX Policy. They however, are never above the supposed "laws" that they pass. They also control, when or when not certain exceptions to policy apply. If policies contradict or interfere with another policy/division, they may be considered void until the PAS have decided accordingly. A policy may be voted against or removed, by other divisions, most specifically PR.
 * 1) (Insert Administrator Here)

T-Group
Has the Primary control of the Backgrounds of PvX. When it regards coding procedures, they should not be questioned for any reason and have the ability to impliment any changes (Technically speaking) to PvX, unless 3 or more divisions areagainst it. T-Group Member must be fully capable, as their work heavily relies upon their ability to code.
 * 1) (Insert Administrator Here)

Build Staff (NBS)
Has the authority over Vote Removal, Vote Sweeps, the deletion of inappropriate Builds, ect. Also has the ability to WELL any Build that seems appropriate (Mimic, Ineffective, ect). They may also bring to the attention of the T-group, technical difficulties regarding to builds exclusively.
 * 1) (Insert Administrator Here)

Inactive
Inactive Administrators (No placement)
 * 1) (Insert Administrator Here)

Other
Performs things not listed as a category.
 * 1) (Insert Administrator Here)