View source for Omu Staff Policy

# CRITICAL STAFF POLICY
## STAFF ARE RESPONSIBLE FOR FOLLOWING SS14 HUB RULES ANY VIOLATIONS OF THE HUB RULES WILL RESULT IN REMOVAL FROM THE TEAM.
### Do not harass, bully, brigade, defame, or Release  players PII, developers, or communities.
#### EXAMPLES OF PII OMU WILL WORK WITH
##### IP ADDRESSES
##### EMAIL ADDRESSES
##### GIVEN NAMES
## ALL STAFF MUST FOLLOW DISCORD TOS THIS IS MANDATORY TO CONTINUE TO PARTICIPATE WITH OMU STATION FAILURE TO COMPLY WILL RESULT IN REMOVAL FROM THE TEAM.
## STAFF OPEN DOOR POLICY
### Any issues involving one or multiple staff members may make an internal Open Door Complaint to the next level of staff (I.E. Speaking with the Head Maintainer about a Maintainer or Trial Maint.)
### An Open Door Complaint must be made in the following format and within Thirty (30) days of occurring.
#### Subject, What is the Complaint/OpenDoor about
#### Policy violations, What policies are violated
#### Evidence/Detail, What information is relevant to the complaint.
### AFTER AN OPEN DOOR COMPLAINT IS MADE NO PARTY INVOLVED MAY SPEAK ABOUT IT OR THE RESULTS THEREOF THE COMPLAINT ANY DECISION MADE BY THE HEADS OF STAFF ARE FINAL.
### Any Player, Staff, Or discord member may request an open door with relevant members of staff. 
## Heads of staff can veto decisions of non heads.

# Administration Procedure
## Administration Conduct
### Staff are to be caring and professional with the community, and are to remain focused on resolving issues in a non-inflammatory manner. 
### Admins are responsible for their actions in game, especially where it pertains to player enjoyment and round quality. Admins are to put the enjoyment of players over their own desires for a round
### Staff are held to the same rules as all players, with a higher standard for decency and conduct. 
### Sensitive or player information is never to be leaked without Head of Staff permission. 
### If there is a disagreement between any staff for any reason, the aggrieved staff should speak with a Head level member of staff about it instead of having an altercation. 
## Banning
### Bans are to be carried out within the boundaries of the banning chart.
### Bans can be issued outside of the chart, but are to be reviewed by another staff member post de facto. 
### Admins can never handle an Ahelp or rulebreak that they were involved with in any way. 
### Admins must deadmin in round unless they are the only admin online. This does not apply to Head Admins. 
### Admins should not jump into a non Ahelped situation unless the situation in question is sufficiently severe. 
### Admins should note any extremely noteworthy behaviour using player notes. 
### Admins should announce to other online admins in game, deadminned or not, when going AFK or disconnecting. 

# Maintenance and Repo
## In line with 1a, Maintainers are to be polite and respectful when performing duties. 
## All push, commit, PR, and other names of files are expected to be appropriately and helpfully named. 
## PRs should be fully documented. Maintainers can close PRs that are not properly documented or appropriately named. 
## Maintainers are given admin permissions, and allowed to perform admin duties, but are held to the same standards as admins. 
### Ideally Maintainers will not do actions as admins unless it's needed
### Maintainers can do events with an admin's assistance for the purpose of testing things.
## Maintainers should not close PR’s without sufficient reason. 
## Maintainers should not self-merge PR’s without sufficient reason.

# Decorum and Expectation
## Staff are to remain mature, respectable, and caring for the community, as it ties into 2.A.

# Events and “for fun” admin actions.
## ALL IN-ROUND ACTIONS MUST BE TAKEN WITH PLAYER ENJOYMENT, IMMERSION, AND ROUND QUALITY IN MIND
### In round actions are defined as full events, emergent events, in round major actions, in round minor actions, and AA (Admin abuse).
### Staff are expected to perform actions within reason, and in amounts that do not bother the players.
## Full events are to be logged and scheduled within the event chart, pre planned, and announced to players in advance. Ideally these events should be announced in the discord the day prior as well, and such events should be limited to a total of three per week, and no more than one per day.
### Said events should be high effort, well planned, and engage players in a fun and memorable way, (historical examples of this includes LARP day, or Christmas ops)
## Emergent events are in-round actions taken by an admin to enhance the quality and engagement with a round. Examples of this include a CCO visiting the station, ERT, Deathsquad, or the like. Such events should be voted on, and in the case of ERT/DS, the opposing forces should be asked if they would like the additional challenge.
### During emergent events, admins are especially responsible for maintaining player satisfaction. Emergent events are no excuse to “go wild”
### Staff should not be performing emergent actions constantly or excessively. 
## Round major actions are round influencing actions admins can perform for the round that MUST BE VOTED ON. 
### Examples of such include:  voting to add more antags, voting for a special cargo shipment, and other such actions which will rewrite the course of a round. 
## Round minor actions are round influencing actions that DO NOT need to be voted on. 
### Examples of this includes: giving out minor items like magic crayons, harmless spawns like mothroaches, spawning items as is appropriate in response to well written faxes to CC, and otherwise is left to the admins discretion.
## Admin abuse is a loose and broad topic, but the following is expected 
### Admin abuse should only occur with the player’s consent, implicit or explicit
### Admin abuse should have minimized consequences on other players
### Admin abuse of an extreme degree is treated as an emergent event. 

# Discord Staff policy
## All Staff are expected to follow Omustation Discord Rules, and are subject to the Discord Banning and Warning Policy.
## De-escalation is priority number ONE when it comes to issues involving discord users.
### Manage your own emotions, do not add on to an argument that is ongoing.
### Maintain Respect to a reasonable degree, If you feel you are unable to address a situation ask for help Privately or in Staff Channels.
## Discord Banning & Warning Enforcement
### Staff are encouraged to follow the Discord Warn and Banning policy found in Document 2 of the Omu Station Documents
#### Unless asked for assistance, only one staff member may deal with a Discord situation and its resolution.
#### Staff are permitted to go lighter on the punishment but not mandated to.
## Running Discord Events
### All staff are permitted to run events within regard to the discord but should be available to moderate their own event.
### Ensuring that discord rules and policies are more important than the event itself.
## Channel & Role, Creation/Archival/Deletion
### ONLY HEADS ARE PERMITTED TO ARCHIVE/DELETE CHANNELS ANY VIOLATION OF THIS MAY RESULT IN DEMOTION.
### Channel creations are able to be made upon a reasonable request from the staff team.
### Role deletion, for any roles that are to be deleted due to any reason an agreed consensus must be reached before doing so. Failure to obtain permission may result in demotion.
### Role creation, for any roles that are added they must be non-demeaning and clear their use.
### Role Assignment, DO NOT ASSIGN STAFF ROLES TO NON STAFF MEMBERS UNLESS TOLD TO DO SO. Any assignment to roles can be done within reason.