United Operations Charter

1.0 Mission Statement:

United Operations is hereby established to serve as a community for fostering teamwork, simulation and cooperation in gaming. We are a mature community bound by a set of common principles:

• 1.1 - We believe that the virtues of friendship, fun, professionalism, respect, cooperation, teamwork and courtesy are more important than power.
  
• 1.2 - No member of the community shall be granted privileges, powers, protections, exemptions or otherwise receive special treatments which exceed those held or available in common. No member shall willfully act or conspire to supplant the rule of the charter.
  
• 1.3 - All regulars will be respected enough to have a common influence on the direction and administration of the community.
  
• 1.4 - Gaming involving tactical play and simulation is most fulfilling - although we welcome diversity in moderation.
  
• 1.5 - We value merit over title and action over pretense. All of our regulars are valuable assets in their own way, and will excel within their domain.
  
• 1.6 - We are a free community - monies will never be requested of our regulars, and those who ever do donate will never benefit from it.
  
• 1.7 - Freedom of speech - no regular will be penalized for expressing his opinions. This is a community of mature people.
  
• 1.8 - We value the input of regulars, and we are eager to devote our time and effort to educating and welcoming new additions.

2.0 Operations:

Operations are the standard method of community involvement in the decision making process and can be enacted across all aspects of the community:

• 2.1 - Operations of the community are decided by fully inducted Regulars.
  
• 2.2 - Any Regular may propose an operation by posting a forum poll. Standard operations (standard being all except those operations specifically defined in this document)
  
• 2.3 - Only Regulars may participate in votes and each is allotted the power of one (1) vote.
  
• 2.4 - Officers have the power of one (1) vote, as per their status as Regulars, in operations of the community.
  
• 2.5 - Proposals shall require a minimum 2/3 majority vote to be passed.
  
• 2.6 - Polls shall be created with a 7-day expiry.
  
• 2.7 - Polls shall have the "Public Poll" option disabled.
  
• 2.8 - If a proposal is not accepted, it may be resubmitted after a minimum of two (2) weeks from poll conclusion has elapsed.

3.0 Addons & Modifications:

Operations to add or remove UO Modpack add-on's and modifications (mods) must pass with a three fourths (3/4) majority vote lasting two (2) weeks.

• 3.1 - Defective or broken mods may be removed from server by the AOO and GSO's without prior notice.
  
• 3.2 - Mod stability and compatibility will be the responsibility of the Mod submitter.
  
• 3.3 - Client-side mods may be submitted for UO Modpack inclusion only if they significantly enhance gameplay, teamwork, and/or realism. (eg: Shacktac Fireteam Hud)

4.0 Rules:

Operations to add or amended rules must pass with a three fourths (3/4) majority vote lasting two (2) weeks. We submit to the following rules in order to benefit the community at large:

• 4.1 - Cheating and hacking shall result in immediate and permanent removal from our community.
  
• 4.2 - The chain of command shall be respected during games.
  
• 4.3 - Players shall not intentionally team kill or otherwise disrupt game play.
  
• 4.4 - Player shall not engage in forum/TeamSpeak spamming or otherwise disruptive behavior.
  
• 4.5 - Players shall respect each other and act accordingly.
  
• 4.6 - The rules of this community, the provisions so outlined in this document and the Standard Operating Procedures shall inform player conduct expectations.
  
• 4.7 - The rules of this community shall be applied equally across all mediums and services including, the forums, TeamSpeak, and game servers.
  
• 4.8 - All operations of government must be publicly displayed. Any regular may request and shall be entitled to any and all information regarding administrative operations.
  
• 4.9 - Sobriety will be required by regulars in leadership positions: both within the game and within the community’s offices.

5.0 Personnel:

• 5.1 - Non-regulars:
  
  • 5.1.1 - Non-regulars have no representation in operations of government, although they are free to express their opinions and are a valued part of the community.
    
  • 5.1.2 - Non-regulars are gifted with but not guaranteed due process, protection of the charter or standard operating procedures. Non-regulars are guests who may be removed by the summary justice of other regulars and overseeing officers of respective areas if there are blatant violations of the charter rules, standard operating procedures or other clearly demonstrable reason. Blatant offenders may be summarily banned or otherwise disciplined without guaranteed instrument of redress. Summary instances of justice may be contested and overturned by a majority standard operation lasting seven (7) days. These operations function as standard operations as defined in the charter.
    
  • 5.1.3 - Non-regulars are guaranteed no privileges or rights which are awarded to regulars, either in the charter or in standard operating procedures. Where privileges or rights are afforded, they are at the discretion of the regular or official authority.
• 5.2 - Regulars:
  
  • 5.2.1 - Regulars represent the core of the community. Regulars are players who wish to take part in the organization and administration of the community:
    
    • 5.2.1.1 - New Regulars are inducted by a successful one (1) week 2/3rd majority vote.
      
    • 5.2.1.2 - Rejected inductees will be notified and be given a reason for their rejection based on community consensus.
  • 5.2.2 - There are two methods to initiate a vote for regular status:
    
    • 5.2.2.1 - Self Selection: Any registered forum user may ask to be inducted as a regular.
      
    • 5.2.2.2 - Appointment: Any regular can appoint a player to be voted on as a regular.
  • 5.2.3 - All applicants must be registered and active members of the forums for a minimum of 45 days prior to application.
    
  • 5.2.4 - All applicants are expected to participate reasonable in Teamspeak activities prior to application.
    
  • 5.2.5 - Polls shall be created with a 7-day expiry enabled.
    
  • 5.2.6 - Polls shall have the "Public Poll" option disabled.
    
  • 5.2.7 - Operations of Regular removal must be decided by a two (2) week 2/3rd majority vote.
    
  • 5.2.8 Any Regular may resign their position as a Regular by post in the UO Forum. The resignation takes effect in 72 hours unless said Regular retracts their resignation by post in the UO Forum.
• 5.3 - Officers:
  
  • 5.3.1 - Officers are expert volunteers oriented to perform a defined task within a category of expertise:
    
  • 5.3.2 - Regulars may volunteer to become Officers.
    
  • 5.3.3 - Operations for the induction of new Officers must be decided by a majority vote lasting two (2) weeks.
    
  • 5.3.4 - Operations of Officer removal must be decided by a two thirds vote lasting two (2) weeks
    
  • 5.3.5 - Officers may not have any privileges or powers exceeding their tasks.
    
  • 5.3.6 - Categories of expertise are as follows:
    
    • 5.3.6.1 - Officer of Web Services: These Officers are tasked with ensuring the forums and website are operational.
      
    • 5.3.6.2 - Officer of the Game Server: These Officers are tasked with ensuring the healthy operation of the game servers, including remote access and administration, as well as maintenance and expansion scouting.These Officers are tasked with ensuring that players have an effective and simple means by which to update their games and play here at United Operations.
      
    • 5.3.6.3 - Officer of Mission Making: These Officers are tasked with managing the missions currently on the game and test servers, verifying problem missions and removing them through a transparent process, and educating the community on the addition of new missions to the servers.
      
    • 5.3.6.4 - Officer of Public Relations: These Officers are tasked with monitoring, improving and developing inter-community relationships, promoting and expanding the community base, and for promoting events.
      
    • 5.3.6.5 - Officer of the Training Center: These Officers are tasked with the implementation of official training courses within the community, the development of courses that coincide with the standard of play at UO, raising the overall standard of play, producing training plans, and the hiring/dismissal of instructors within the department.
  • 5.3.7 - All elected officers shall be granted the powers to administer the TeamSpeak server.
    
  • 5.3.8 - Officers may delegate their pre-existing duties and powers, as defined by the charter, to other regulars. Each office must maintain a clearly worded definition of delegated powers and a complete list of those who are tasked with them. Definitions and lists must be publicly viewable on the forum. Delegates may be voted out of their positions by a general operation (simple majority poll with a week duration). Delegates voted out of a position cannot be granted delegated powers again under that office unless voted upon by the community of regulars.
    
  • 5.3.9 - Any Officer may resign their position as an Officer by post in the UO Forum. The resignation takes effect in 72 hours unless said Officer retracts their resignation by post in the UO Forum.

6.0 Standard Operating Procedures:

The Standard Operating Procedures (SOPs) serve as a guide for the conduct of operations within each category of expertise delineated under the officer section of this document. The SOPs may contain relevant procedures, expectations, and documentation. The following apply to community action and interaction with the SOPs:

• 6.1 - It is the primary responsibility of the Officer(s) overseeing each area of expertise to maintain and update the SOPs of their particular section as needed or required.
  
• 6.2 - Operations to add, remove or amend line-item SOPs are considered standard operations and are treated as such.

7.0 Revision and forum discussion information:

Historical References:

• December 15, 2010: by Sandiford
  
• May 31, 2011: by Impulse 9
  
• June 13, 2011: by Krause
  
• June 16, 2011: by Sceaduwe - Formatting only.
  
• June 24, 2011: by Hawkeye - Formatting only.
  
• June 29, 2011: by Hawkeye
  
• July 14, 2011: by Impulse 9
  
• August 2, 2011: by Impulse9
  
• September 1, 2011: by Hawkeye - SOP link
  
• November 16, 2011 by Krause
  
• November 25, 2011 by Krause
  
• January 4, 2012: by Sceaduwe - Copied from forum.