The wiki is currently undergoing some major improvements. If you need some information and you don't know where to look, please come to #ecnet

Difference between revisions of "Organizational Units"

From ECNet Wiki
Jump to: navigation, search
(New page: '''Organizational Units''' are sub-groups of the network staff that handles one or more specific administrative duties. These groups are sub-divided into directorships and teams. Directo...)
 
m (Protected "Organizational Units" [edit=sysop:move=sysop])
(No difference)

Revision as of 23:30, 7 March 2008

Organizational Units are sub-groups of the network staff that handles one or more specific administrative duties. These groups are sub-divided into directorships and teams. Directors are individuals overseeing an aspect of network operations, whereas teams are groups of people overseeing an area of network organization.

Network Relations Director

This person is charged with the management of network relations and promotional activities. This position is a primarily secretarily role. All promotional activites must have a protocol and be approved by the network relations director to prevent doubling-up or conflict. Protocols are codes of conduct for various types of promotions. New types of promotions require a new protocol be established. When this occurs, the person seeking permission to promote and the network relations director meet with the lead network administrator and establish a set of protocols. Once these protocols are established, future promotions of this type will not require the lead network administrator's approval. In matters of protocol, the lead network admin has final say and can override both the network relations director and the promoter. The lead network admin may also modify protocols at any time, he or she must notify the network relations director of any such changes. Documentation of all protocols are maintained by the network relations director.

The current network relations director is ClaireBear.

Infrastructure Team

The infrastructure team is responsible for overseeing the foundation of the network.

Responsibilities

  • Approve and revoke network operators for service administrator status, based on whether they show a need for these extra privileges
  • Approve links for new servers. Once approved, the link is given a ten day test period, then given a final vote by the general consortium.
  • Act on the suggestions made by the network relations team
  • Updating network-wide rules and policies (de facto)

Members

The infrastructure team is chaired by the lead network administrator, who appoints members at his discretion.

Oper Abuse Team

The oper abuse team investigates reported incidents of network operator authority misuse.

Responsibilities

  • Investigating and deliberating on cases brought to the team based on its operating procedures
  • Enforcing any sanctions made on operators, up to the full removal of an operator's o:line
  • Making recommendations to the infrastructure committee on any additional action needed

Members

The chair for the oper abuse team is appointed by the lead network administrator. The chair appoints members at their discretion.

Training Team

The training team is responsible for giving additional training to network operators.

Members

The training team is chaired by the lead network administrator, who appoints members at his discretion.

Appeals Team

Responsibilities

  • Dealing with appeals to g:lines by confirming or denying network bans set for seven or more days
  • Investigating and deliberating on cases brought to the team
  • Making a public statement about the reasoning for the final decision of the team, which set precedent
  • Forwarding resolved cases where there may be abuse of operator privileges to the oper abuse team

Members

  • None – Cases are handled by Heero until next election.

Appointment

Potential candidates are nominated by a server administrator and current members can run for re-election without endorsement. During the elections, all users on the network will vote for three operator candidates and two non-operator candidates that they support. On May 31 or November 31, the candidates with the most votes will assume their positions for a six month term.