STARLINK-IRC SERVER ADMIN AND OPER INFORMATION 
v1.3  April 8 1998

* * * * * * * * * * 
ADMIN AND OPER EXPECTATIONS
* * * * * * * * * *

Now that you have successfully connected, thought we'd like to let you 
know some of the stuff that is expected of a StarLink-IRC oper/admin.

The main focus is the users. Without users on our net, we have a bunch 
of servers and nobody to talk with. We expect the highest conduct when 
dealing with the users. Basically, as an IRCOP the idea is to be 
invisible to the users. We are only there when they require assistance 
(ie: they are being flooded, or they have questions about connecting).

Channel integrity is maintained by channel owners and operators through 
CStar with assistance from Channel Services (CService) as needed.  

Wherever possible whe do not send global messages. We use them for 
special (and required) messages only like:
 "Having to reboot Atlanta in 10 minutes..sorry for the inconvenience"

Another expectation will be server availability. It is expected that 
an Admin will not disconnect a server without prior notice whenever 
possible. Delaying until a non busy time is desirable, but emergency 
shutdowns don't always permit that. We do expect that a server admin 
can recompile the server ircd, and ensure that the ircd is in the 
system startup scripts (so if the server reboots, the ircd comes back 
up). The basic thought here is that if the server is not connected all 
of the time, the users can't connect to the network (see main focus).

The only other expectations are that IRC OPs have considerable power 
over users. We often have to separate "channel" things from Network 
things. We are here to protect the network, not to police the channels.
The network is policed by IRC OPs and Admins. CService uses CStar to 
maintain the integrity of channels, and IRC OPs/Admins use DeathStar 
to maintain the integrity of the net.  Abuse of a user or channel owner
is a very serious matter that can be grounds for losing an O: line or 
being removed from CService.

If you have any questions (and you will) feel free to discuss them 
with any other IRC OP, Admin, or Channel Services Rep. 

Note that there is an IRC OP/Admin meeting every week in #Oper for  
general discussion of whatever may be of interest. There are two
weekly meetings in #TownHall to meet with users at 9:00PM ET and all
are welcome to attend.

**NEW** APRIL 1999

SERVER ADMINISTRATOR : CONTACT REQUIREMENTS

To ensure net coordination, SL-IRC has instituted a policy on servers
that are incommunicado for an extended period. If your server 
disconnects from the net for no reason, it may be juped until the 
reason is known to us. In cases of a disconnected server, if the 
admin does not respond within a week, the server will be temporarliy 
delinked. If there is still no contact with the admin for an 
additional week, the server will be delinked. 

Additionally, if we cannot contact the administrator of a server 
(online on SL-IRC or via email) for a period of three weeks, the 
server may be juped or temporarily delinked. An email will be sent 
advising that the server is on probationary status and will be 
delinked if there is no reply within one week. If there is still no 
contact with the admin for an additional week, the server will be 
delinked. 

The above does not restrict or limit the right of SL-IRC to delink or 
jupe any server as necessary to protect network integrity.

** END NEW SECTION APRIL 1999 **