
ECNet's rules and regulations provide for the formation of teams
which maintain the network through powers delegated away from the
lead network administrator. These teams each have charters and are
formed for a separate purpose. A list of the currently active teams
are listed below.
Infrastructure Team - This team is responsible
for maintenance of the critical ECNet infrastructure. The members
are appointed by the chair, who is the lead network administrator.
The infrastructure group may approve services permissions modifications
via a vote, majority rules. They are required to give admin to server
administrators without exception. The infrastructure team is also
responsible for links. They may or may not approve a link via a
vote where majority rules. Once approved, a link is given a 10 day
test period during which everything is monitored and they are not
added to the DNS pool. After this period of time a vote will be
taken of the general consortium, a 2/3 majority is required to finalize
the link. If a link was denied, by the committee or by the consortium after the trial link, the chair of the committee may at his or her discretion require up to 90 days beore the applying organization or individual may reapply.
Oper Abuse Team - A team dedicated to looking
at abuse of IRC operator authority. The team chair is appointed
and dismissed by the lead network administrator. The chair of this
team may appoint whomever is willing to this team. The chair may
order investigations into reported operator power abuse. Once these investigations
have been completed, the team votes whether or not the incident
should require disciplinary action or if it was not operator abuse
or too minor to be concerned with. In this vote majority rules,
and the results will usually follow the following scheme, though at the discretion of the chair they may vary. On first offense, warning
and censure with a required apology to the user suffice. On the
second offense, the team chair will take it up with the admin of
the operator in question and ask for a temporary o:line revocation
as well as censure. On the third offense there is no option, a two
week o:line revocation is mandatory. On the fourth offense it is
at the chairs discretion as to what actions should be taken, up
to a full o:line revocation. Operators and users should be warned, lying to an abuse team member when being questioned during an investigation is considered perjury, and will result in a 30 day ban or removal of operator privileges. To submit an incident, email operabuse@ecnet.org
Training Team - The training team focuses on training IRCops and has no real authority. Training sessions are not mandatory but are optional and used to supplement training given by the administrator of the server an IRCop is part of. This includes training in permitted usage of anti-botflood measures as well as secret information regarding internal defense systems. The chair of this committee is the the lead network administrator.
Appeals Team - The appeals team was founded to deal with appeals to bans made. Unlike abuse, they deal with legitimate G:lines which were not abuse but may be misfounded. As such, operators are not censured as part of their operating, but rather G:lines are confirmed or removed. They are the final authority on all bans. Any abuse complaints accidentally misfiled as appeals are forwarded to the abuse team. This team consists of five members, three of them IRC operational staff (including admins, global operators, and local operators), the other two are general users of the network. They are voted into power on May 31, and November 31, serving a six month term. They are elected by the general consortium, and cannot be removed from power during their terms. Each one is by default up for reelection, but any member of the general consortium may nominate anyone. The vote is to occur in an approval style system, you give three opers you approve of, you give two users you approve of, the ones with most approval ratings are elected and their term begins on the first of June or first of December respectively. The appeals team is hereby granted authority to, as a collective, order the removal of G:lines they vote are not in line with ECNet's rules and purpose. An official appeal begins when the user emails the appeal team or otherwise registers a complaint. Complaints may only be made on G:lines of a duration greater than seven days. Once a complain is registered, an investigation if performed, and a vote is taken. Majority rules in if a G:line is justified. After which, one member will write a brief explanation of the group's reasoning. These opinions will be made publicly available for all to see as they are a matter of public record. Operators and users should be warned, lying to a member of the appeals team when being questioned during an investigation is considered perjury and is punishable by a 30 day ban or removal of operator status. Furthermore, all communications to and from the appeals team, besides deliberation, is a matter of public record, and shall be recorded along with the opinion. Should those who voted the other way wish to, they too may write an opinion stating why they were against the decision, and it too will be posted. All opinions will be posted to the wiki in a special section to be created. The decisions of the appeals committee may often act to clarify the rules if operators disagree. An operator may file a complaint on behalf of a user if they disagree with the G:line. Decisions of the appeals committee set precedent, and while an operator may not know if a rule is violated and may assume it has been at first, after appeals clarifies this, in future situations they must act consistently with this clarification of the rules or it is considered operator abuse. To file an appeal, please send an email being as precise as possible to appeals@ecnet.org.
Network Relations Team - This team serves to help network relations with users as well as other networks and make suggestions to the infrastructure committee and lead network administrator on changes that would help the network. This includes promotions to make the network grow, as well as holding meetings and asking users for feedback. The chair of this committee serves as the pleasure of the lead network administrator and all promotional activities must be approved by the lead network administrator prior to being done. Suggestions are non-binding and this team does not have the authority to enter any binding agreements with users or other networks.
|
|
|
|