Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
policies:operguidelines [2007/02/20 17:37]
js
policies:operguidelines [2014/11/12 13:05] (current)
rubin
Line 1: Line 1:
 ====== Network Operator Guidelines====== ====== Network Operator Guidelines======
-//Written by Rubin     +**A note to our users**: These rules act as a guide for us, your network operators and administrators, to act justly and fairly when dealing with security and disciplinary activities online. This is NOT our [[policies:aup|acceptable use policy]], which defines what you are allowed to do. These rules are "the law" for IRC Operators' immediate action, but can be overridden by the network at a high level (i.e.a vote by opers). 
-Friday16 April 2004//+
  
-A note to our users: These rules act as a guide for your administration to act justly and fairly when dealing with security and disciplinary activities online. This is NOT our terms of service, or our acceptable use policy. +===== Operator Guidelines ===== 
- +In general, if you are not sure if its OK to act, play it safe. Always try to solve problems FIRST without use of your oper.
-These are basic guidelines for Opers on the AfterNET IRC network. These rules are "the law" for immediate oper action, but can be overridden by the network at a high level (i.e., a vote by opers). In general, if you are not sure if its OK to act, play it safe. Always try to solve problems FIRST without use of your oper.+
  
 In most cases, where a real person is involved (not a bot, clone or trojan) you should try to talk to them first. Oper commands should be used as a last resort. Educate channel owners on how to set good bans, and use the tools they have first. G-Lines should be used only when there is no good alternative solution. Spammers may be killed without warning as long as they are really spammers (see below). In most cases, where a real person is involved (not a bot, clone or trojan) you should try to talk to them first. Oper commands should be used as a last resort. Educate channel owners on how to set good bans, and use the tools they have first. G-Lines should be used only when there is no good alternative solution. Spammers may be killed without warning as long as they are really spammers (see below).
Line 30: Line 28:
                   * The channel is being used as a "base" for an attack on the network.                   * The channel is being used as a "base" for an attack on the network.
                   * The channel's owner/operator has been massively spamming and simply glining them has not solved the problem.                   * The channel's owner/operator has been massively spamming and simply glining them has not solved the problem.
 +                  * The channel is opless -- discuss in the channel who they want, make a judgement call. be willing to reverse it if new information takes light later.
  
           * Overriding security in the channel services shall not be done without explicit permission from the channel's owner. Ownership must first be verified.           * Overriding security in the channel services shall not be done without explicit permission from the channel's owner. Ownership must first be verified.
Line 41: Line 39:
 === Other oper guidelines === === Other oper guidelines ===
  
-          * Missing servers should be reconnected automatically by X2, which will try once an hour if they don't return immediately. Regardless, opers should try to connect them as well. The X2 command "REROUTE C" will do this automatically to the proper hub. /connect server* 8888 hub* if x2 is missing.+          * Missing servers should be reconnected automatically by X3, which will try once an hour if they don't return immediately. Regardless, opers should try to connect them as well. The X3 command "REROUTE C" will do this automatically to the proper hub. /connect server* 4497 hub* if x3 is missing.
  
-          * Improperly routed servers should NOT be rerouted unless the routing is causing problems on the network or a current hub needs to stop hubbing. Netsplits should be avoided at all times as they are a huge inconvenience to the users. Improperly routed servers will correct themselves over time - as they split X2 will reconnect them properly.+          * Improperly routed servers should NOT be rerouted unless the routing is causing problems on the network or a current hub needs to stop hubbing. Netsplits should be avoided at all times as they are a huge inconvenience to the users. Improperly routed servers will correct themselves over time - as they split X3 will reconnect them properly.
  
           * Wallops are intended for official oper communication. The occasional social conversation is OK but should be stopped if it is bothering anyone.           * Wallops are intended for official oper communication. The occasional social conversation is OK but should be stopped if it is bothering anyone.
Line 53: Line 51:
 === Test link servers === === Test link servers ===
  
-          * Opers and admin on a testlink server MUST NOT use any oper power beyond the range of their own server without supervision, except in very extreme situations.+          * Opers and admin on a testlink server **MUST NOT** use any oper action beyond the range of their own server without supervision, except in very extreme situations.
  
-== Admin Guidelines ==+===== Admin Guidelines =====
  
 +          * Administrators are opers too, so must follow the Oper Guidelines.
  
-          * New opers are not to be added without first consulting with the group. Normally this is done via a msg to the mailing list.+          * New opers are not to be added without first consulting with the group. Normally this is done via a msg to the mailing list **before** adding an oper, allowing a day or so to hear any objections. If there is an objection, a vote can be had to settle it.
  
           * Every oper must have a 'sponsor'-- an admin who is 'their' admin. This admin's server is referred to as their 'home' server. If the server goes away, or the admin decides to un-sponsor an oper, all other admins have the option of picking up the opers sponsorship. If none do, the oper is removed.           * Every oper must have a 'sponsor'-- an admin who is 'their' admin. This admin's server is referred to as their 'home' server. If the server goes away, or the admin decides to un-sponsor an oper, all other admins have the option of picking up the opers sponsorship. If none do, the oper is removed.