Opers - Policy and Rules
These rules for apply to IRC Operators.
You will not interfere with channel management:
- Flooders can be dealt with by channel ops.
- Don't use your o-line or services abilities to manipulate a channel unless you are doing so to prevent abuse (make sure you have logs to support such usage!)
- If services are down and a channel owner requests ops, but you don't know anyone who is on the access list then ask advice from fellow IRC Operators.
You are expected to help users and respond to polite requests for help:
- If you are too busy, direct them to #scarynet or #cservice.
- Make sure you are not invisible (umode +i) whilst opered.
- If you want to make yourself available for help, make use of the usermode +H.
- You do not have to take abuse from users, but by the same token you may not at any point use your o-line or increased services access to exact revenge.
You are expected to take an active part in managing the network:
- As a global IRC Operator you should familiarise yourself with the proper routing of servers, in order to help the network recover from splits.
Participate in votes:
- New policy will be determined for the most part by vote of the opers. This includes linking of servers.
You will behave professionally in network channels:
- In network-owned channels you will not abuse users in any way. Abusive users will be banned and you will be expected to /ignore them.
You will behave professionally on other networks:
- If it is brought to our attention that you have brought our network into disrepute by e.g. mass advertising us on another network, you may be subject to disciplinary action.
Promote the network:
- Bring users, make us noticed, anyhow and anyway you can (besides spamming!)
Keep your admin informed:
- If you can't fulfill your duties or be present on the network for an extended period of time, explain to your admin. This is not likely to pose a problem if the situation is temporary.
All of the above rules for IRC Operators apply to admins as well.
Manage your server staff:
- Make sure they are trained.
- Make sure they are doing their job.
- Help them when they are unsure of what their duties are and/or how to do them.
- Deal with any complaints regarding them before they turn into real problems for the network.
- Comply with guidelines for adding IRC Operators (see "managing O-lines" below).
Maintain your ircd:
- When the Coding Team releases a new version of the ircd you have one week to apply the change. If the upgrade is a major one (incompatible with previous versions) then expect your ircd to be juped until the upgrade is complete.
Keep your colleagues informed:
- If you are unable to attend the network temporarily, inform yourstaff and colleagues, and arrange for an acting admin to vote on your behalf.
- If your server is not able to handle its normal client load for whatever reason, you are required to notify the Admin Team and expect it to be temporarily removed from the DNS pools so that it does not take clients. If your server is malfunctioning enough to seriously affect the rest of the network, expect it to be temporarily juped.
- Every IRC operator must have a "home server", and the admin of that server is responsible for the behaviour of the IRC operator no matter which Scarynet server (s)he connects to.
Number of IRC operators:
- Each server may have O-lines for up to four distinct members of staff. This includes the admin and co-admin (if present), it does not include O-lines for proxy scanners or other programs that are approved by the admin team for operation of the server or network. This figure will be increased as the network grows, and will be increased across the board.
- The Admin Team must be informed at least 48 hours prior to a local IRC operator being upgraded to global IRC operator. During this time, any objections will be made clear by members of the Admin Team and the promotion may be blocked by admin vote. When informing the Admin Team of planned oper promotions, it is preferable to do so before discussing the matter with the oper concerned.
- The only way to become a global IRC operator is to serve for at least 30 days as a local IRC operator. Exceptions to this policy may be made at the discretion of the Admin Team, for example in the case of an existing or former global operator moving to a new server. An admin is under no obligation to upgrade a local IRC Operator to global in 30 days; that is completely up to the admin concerned.
- Admins may appoint local IRC operators with a view to training them until they are eventually suitable candidates for global O:lines. A user must have had a registered username for 30 days to be eligible for local IRC Operator status.
- The Admin Team must be informed at least 48 hours prior to the addition of a local IRC operator so that any possible objections can be made clear. When informing the Admin Team of planned local oper additions, it is preferable to do so before discussing the matter with the user concerned.
Removal of operators:
- Admins may remove members of their staff at any time for any reason. They are required to notify the Admin Team of the removal but are not required to state reasoning.
- Not all network staff have O-lines. Having IRC Operator status is not required before you can help in the various teams. Likewise, losing an O-line does not prevent you from continuing to serve in a team. Team composition is the business of the team leader.
- Admins may be required to remove or restrict one of their staff member's o-lines due to vote of Admin Team or order of the EB. Failure to promptly (24hrs) do so may lead to action against the admin concerned.
- Each server may have as many backup O-lines as necessary. It is up to the admin of the server who they add backup O-lines for. It is suggested that admins are generous in giving out backup O-lines so that their server may be fixed ASAP should none of their regular staff be present. Backup O-lines for existing global operators may be added, removed or updated as the server's admin sees fit without consulting anyone.
Transitional Rules of Appliance
Since the network is already operational and there are admins/opers present prior to acceptance of those rules the following method will be applied in order to make sure they all work out, also for the existing staff:
- Existing opers will be tested on experience. If not enough experience is available, they will be degraded to local operator until enough experience has been trained in order to validate for global operator status.
- These rules are to be enforced regarding any acceptance of new opers on this network as of May 11th, 2006.