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

Oper Guide

From ECNet Wiki
Jump to: navigation, search

This article is a network operator guide is a basic handbook on how to handle the day-to-day operational affairs. Portions of this guide will only apply to local, global, and server admins, but all of it is good to read for all involved as it gives you perspective. I will mark when each section only applies to one group. Please note this is not the final word on most subjects, but rather a rough guide. Much of being an operator is developing a situational awareness of the state of the IRC network and responding rapidly as it changes with efficient and instinctive maneuvers and counter-maneuvers. This takes time, and there is no substitute for experience.

Abusive Users[edit]

Users who abuse the network are a very very narrow portion of our user base, however users do abuse the network and when this happens there must be consequences. These consequences may range from small to large. In the end it is the judgement call on the operator what they do. If you're a local operator, you can't do much other than bring it to the attention of the other operators who are of a higher rank than yourself, or if the user is on your server to K:line or kill them.

Users may be banned globally for any violation of ECNet rules. They may be K:lined for any violation of server rules. The server rules are not made by ECNet, though most of the rules are the same for servers as ECNet requires a bare minimum. Here are some basic guidelines for global bans (G:lines or GZ:lines)

  • Banning for channel affairs, including being an "asshole" or abusing a user is NOT valid and will be considered operator abuse
  • Banning a user for simply insulting you or another user is not a valid ban, and it considered oper abuse. Just use an ignore.
  • Banning a user for avoiding /ignores or channel bans is valid.
  • Banning a user for spamming when not authorized by channel admins is valid.
  • Banning a user because they appear like a bot is valid, but please include contact details in case it is for an error.
  • Banning bots which are abusive is always permitted, once again please PLEASE PLEASE include contact details.

During a bot flood there is no need to leave contact details for bot bans, leave them blank and DefServ will pick up what is left over at the end and switch it to akills. For all other G:lines, it is good to include at least a simple reason so that the user can know why they are banned.

Relations To Opers/Admins[edit]

Generally operators relate well, but this is not always the case. You should try to work with the other staff and not cause trouble as much as possible. If you feel you can't resolve problems with another operator and feel they are either abusing their power or negatively impacting the network, you should talk to your admin, who will either talk to the abuse committee or the oper's admin and work something out.

Unless you've had problems with someone in the past, generally it's a good idea that if another operator, local, global, whatever, requests a K:line or G:line or anything else you can do, to do it, but demand they provide a reason and cite that they requested it in your reason. Generally this keeps it straight who did what and leads to accountability within our ranks, which is always a good thing.

Admins are technically superior to operators, but you don't answer to anyone but your admin and the lead network admin technically, even though other admins are your indirect superiors. In general just treat them like another global operator.

Rank[edit]

ECNet officially recognizes three ranks: Local Op, Global Op, Server Admin

In reality global operators can be labeled many things and have various permissions, including: netadmin, global operator, operator, can_overirde, etc. These permissions are only used for determining powers on the IRCd and do not apply to ECNet rules and regulations (other than who can do what, which is not a policy issue, but a practicality issue).

Generally pulling rank is not an issue, but technically only rank brackets occur on an individual server then the lead network administrator is officially in charge of all other staff members (though even his power is limited). The only time this is generally done is general orders or sanctions made by an admin (ie: an admin asking one of his operators to watch a new local operator who he thinks might be causing issues, watching a certain user, etc).

ECNet operates on having free exchange of ideas and approaches. NEVER be afraid to speak "out of turn", as long as you're not rude even if you're the lowest trainy local operator on a test link leaf server on a crappy connection and you're talking to the lead net admin, your ideas will be heard and considered, and if they're good implemented. Ideas are ideas-ego shouldn't come into it, and neither should rank.