Difference between revisions of "Server Policy"
(Created page with "{{Stub}} == Admin Powers == === Sounds === * Sounds should not be used gratuitously. Save admin sounds for events and other situations.") |
|||
| (17 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
| + | [[Category:Staff]] | ||
| − | == | + | == Staff Roles == |
| + | ''This section is incomplete but accurate.'' | ||
| − | === Sounds === | + | === Administrative Staff === |
| − | * Sounds should not be used gratuitously. Save admin sounds for events and other situations. | + | Administrative staff handle all things to do with player activities on server. It is the role of the administration to determine where player actions contravene the server and to act to correct such instances. |
| + | |||
| + | ==== Head Administrator ==== | ||
| + | Head Administrators oversee the server as a whole, and act to maintain the administration rather than directly administering. Individually, they can override rulings made by administrators and moderators. Together, they can override decisions on server direction as made by the staff heads, as well as rulings made by individual headmins. | ||
| + | |||
| + | In the event that an administrator is unavailable, a head administrator may step in to act. However, this is discouraged, as receiving a ruling directly from a head administrator may leave a player feeling unable to seek appeal or recourse at a higher level. | ||
| + | |||
| + | ==== Administrator ==== | ||
| + | Administrators rule on player situations that need more complicated solutions than fall within a moderator's prerogative. Excessive rule-skirting, undesired behaviour and other complex issues fall under the Administrators' purview. Administrators also act as agents in enforcing IC rulings where the High Council is involved, and respond to faxes with the full authority of the council. | ||
| + | |||
| + | ==== Moderator ==== | ||
| + | Moderators act on straightforward issues involving player actions. Generally, this simply means enforcing rules as written in a cut and dry fashion, and helping collect information on situations that an Administrator would otherwise rule on. Moderators are the first line in ensuring that the server stays on track and appropriately in tone. | ||
| + | |||
| + | Moderators do not act on behalf of the High Council when exercising their moderation powers, but may make informational responses to faxes as supporting staff to a specific councillor. | ||
| + | |||
| + | As moderators do not have some server permissions granted directly to them, many of their rulings may need to have an administrator rubber stamp them and apply them. | ||
| + | |||
| + | === Supporting Staff === | ||
| + | Supporting staff handle all things to do with the server's state and development. | ||
| + | |||
| + | ==== Staff Head ==== | ||
| + | Staff Heads oversee the development of the server. Each one is given a specific family of tasks to oversee or maintain. Each staff head is either particular to Lore or Code tasks, and when there are four staff heads within either group, one of that group is granted the additional task of foreperson. | ||
| + | |||
| + | An additional, unique Staff Head role exists for maintaining the Rules. This role is also granted the powers and authority of an administrator, but is generally expected to focus on finding flaws in the rules and easing them out, over enforcing them, and to handle rule changes as dictated by headmins. | ||
| + | |||
| + | Staff Heads may respond to faxes regarding clear cut IC issues, in the same fashion as a moderator. | ||
| + | |||
| + | ==== Game Master ==== | ||
| + | A Game Master creates and runs larger events that may affect the lore or have permanent effects. They may also run normal events at will and create their own stories. Game Masters may also approve events by event operators. | ||
| + | |||
| + | Within the context of an event they are operating, Game Masters also receive authority just above that of a moderator. | ||
| + | |||
| + | ==== Event Operator ==== | ||
| + | Event Operators run normal events with the approval of a Game Master or Administrator. They also assist in events being run by Game Masters. | ||
| + | |||
| + | ==== Developer ==== | ||
| + | A member of development staff empowered to inspect and debug the server live, as well as provide technical support on the server where pertinent. | ||
| + | |||
| + | ==== Development Staff ==== | ||
| + | A contributor elevated to the rank of staff. Has a louder voice when making proposals to how the server should be improved. Is expected to be accurately authoritative when it comes to statements about the server. Works with the staff heads to make sure features are consistent with the playerbase's expectations. | ||
| + | |||
| + | === Special Staff === | ||
| + | |||
| + | ==== Host ==== | ||
| + | The font of all power, from which it is all delegated. Has final, unshakable authority over the server, when used. | ||
| + | |||
| + | ==== Liaison ==== | ||
| + | A player dedicated not to the server itself, but to the playerbase. Represents the playerbase within higher channels than regular staff, including a direct line of communication to the headmins and staff heads. | ||
| + | |||
| + | ==== Regular Staff ==== | ||
| + | A normal player elevated to the rank of staff, who participates in staff discussions, including those involving development staff, providing a layperson's perspective on changes and staff activities. | ||
| + | |||
| + | == Player Guidelines == | ||
| + | This section details how players should interact with the administration in certain situations. | ||
| + | |||
| + | === Appeals === | ||
| + | Both moderator and administrator rulings may be appealed. Once the appeal is submitted, a Head Administrator will appoint an Administrator to review the case, or in some circumstances, decide to review the case personally. The appointed administrator may not be the administrator who ruled, and should avoid being the administrator who applied a moderator's ruling. | ||
| + | |||
| + | === Feature Issues, Development Complaints & Bug Reports === | ||
| + | * Complaints should only be directed at Head Administrators. | ||
| + | * Issues with features that are neither complaints nor bugs should be posted on the issue tracker, though the appropriate Staff Head is also a valid recipient. | ||
| + | * Finally, bug reports may be discussed directly with the developer of a feature if they are particularly pressing or part of a testmerged PR. | ||
| + | |||
| + | The definitions of the three are left intentionally vague, but bad faith reports will be dealt with. | ||
| + | |||
| + | == Administration Policies == | ||
| + | |||
| + | === Development and Staff Head Policies === | ||
| + | |||
| + | ==== Staff Head Overruling ==== | ||
| + | Staff Heads have mostly unilateral powers when their task. However, tasks overlap, and the whole server is, in the end, a collective development effort. As such there are a handful of ways to overrule them. | ||
| + | |||
| + | * If both forepersons and the Rules staff head agree, a decision can be overruled immediately. | ||
| + | * If there is a foreperson, they can start a motion to overrule a decision made by one of the heads in their group. This vote must be unanimous, with the exception of the head that made the decision. In the case of a foreperson's overruling, a headmin can instead start that vote. | ||
| + | * With the approval of a headmin, all staff heads may undertake a standard vote (with abstention permitted). Headmins may vote in this as well. | ||
| + | * Finally, a 66% supermajority of headmins may make a final decision on a matter. | ||
| + | |||
| + | === On-Server Powers === | ||
| + | |||
| + | ==== Sounds ==== | ||
| + | * Sounds should not be used gratuitously. Save admin sounds for events and other worthwhile situations. | ||
Latest revision as of 02:19, 19 July 2024
Staff Roles
This section is incomplete but accurate.
Administrative Staff
Administrative staff handle all things to do with player activities on server. It is the role of the administration to determine where player actions contravene the server and to act to correct such instances.
Head Administrator
Head Administrators oversee the server as a whole, and act to maintain the administration rather than directly administering. Individually, they can override rulings made by administrators and moderators. Together, they can override decisions on server direction as made by the staff heads, as well as rulings made by individual headmins.
In the event that an administrator is unavailable, a head administrator may step in to act. However, this is discouraged, as receiving a ruling directly from a head administrator may leave a player feeling unable to seek appeal or recourse at a higher level.
Administrator
Administrators rule on player situations that need more complicated solutions than fall within a moderator's prerogative. Excessive rule-skirting, undesired behaviour and other complex issues fall under the Administrators' purview. Administrators also act as agents in enforcing IC rulings where the High Council is involved, and respond to faxes with the full authority of the council.
Moderator
Moderators act on straightforward issues involving player actions. Generally, this simply means enforcing rules as written in a cut and dry fashion, and helping collect information on situations that an Administrator would otherwise rule on. Moderators are the first line in ensuring that the server stays on track and appropriately in tone.
Moderators do not act on behalf of the High Council when exercising their moderation powers, but may make informational responses to faxes as supporting staff to a specific councillor.
As moderators do not have some server permissions granted directly to them, many of their rulings may need to have an administrator rubber stamp them and apply them.
Supporting Staff
Supporting staff handle all things to do with the server's state and development.
Staff Head
Staff Heads oversee the development of the server. Each one is given a specific family of tasks to oversee or maintain. Each staff head is either particular to Lore or Code tasks, and when there are four staff heads within either group, one of that group is granted the additional task of foreperson.
An additional, unique Staff Head role exists for maintaining the Rules. This role is also granted the powers and authority of an administrator, but is generally expected to focus on finding flaws in the rules and easing them out, over enforcing them, and to handle rule changes as dictated by headmins.
Staff Heads may respond to faxes regarding clear cut IC issues, in the same fashion as a moderator.
Game Master
A Game Master creates and runs larger events that may affect the lore or have permanent effects. They may also run normal events at will and create their own stories. Game Masters may also approve events by event operators.
Within the context of an event they are operating, Game Masters also receive authority just above that of a moderator.
Event Operator
Event Operators run normal events with the approval of a Game Master or Administrator. They also assist in events being run by Game Masters.
Developer
A member of development staff empowered to inspect and debug the server live, as well as provide technical support on the server where pertinent.
Development Staff
A contributor elevated to the rank of staff. Has a louder voice when making proposals to how the server should be improved. Is expected to be accurately authoritative when it comes to statements about the server. Works with the staff heads to make sure features are consistent with the playerbase's expectations.
Special Staff
Host
The font of all power, from which it is all delegated. Has final, unshakable authority over the server, when used.
Liaison
A player dedicated not to the server itself, but to the playerbase. Represents the playerbase within higher channels than regular staff, including a direct line of communication to the headmins and staff heads.
Regular Staff
A normal player elevated to the rank of staff, who participates in staff discussions, including those involving development staff, providing a layperson's perspective on changes and staff activities.
Player Guidelines
This section details how players should interact with the administration in certain situations.
Appeals
Both moderator and administrator rulings may be appealed. Once the appeal is submitted, a Head Administrator will appoint an Administrator to review the case, or in some circumstances, decide to review the case personally. The appointed administrator may not be the administrator who ruled, and should avoid being the administrator who applied a moderator's ruling.
Feature Issues, Development Complaints & Bug Reports
- Complaints should only be directed at Head Administrators.
- Issues with features that are neither complaints nor bugs should be posted on the issue tracker, though the appropriate Staff Head is also a valid recipient.
- Finally, bug reports may be discussed directly with the developer of a feature if they are particularly pressing or part of a testmerged PR.
The definitions of the three are left intentionally vague, but bad faith reports will be dealt with.
Administration Policies
Development and Staff Head Policies
Staff Head Overruling
Staff Heads have mostly unilateral powers when their task. However, tasks overlap, and the whole server is, in the end, a collective development effort. As such there are a handful of ways to overrule them.
- If both forepersons and the Rules staff head agree, a decision can be overruled immediately.
- If there is a foreperson, they can start a motion to overrule a decision made by one of the heads in their group. This vote must be unanimous, with the exception of the head that made the decision. In the case of a foreperson's overruling, a headmin can instead start that vote.
- With the approval of a headmin, all staff heads may undertake a standard vote (with abstention permitted). Headmins may vote in this as well.
- Finally, a 66% supermajority of headmins may make a final decision on a matter.
On-Server Powers
Sounds
- Sounds should not be used gratuitously. Save admin sounds for events and other worthwhile situations.
