The Undernet Channel Service Guidelines
	---------------------------------------

Introduction
------------
Thanks to a lot of work by Seks and the rest of the Undernet
IRCops, Undernet now has a channel service. This service will
allow users to run a channel without running a bot. This
service replaces the need for a bot on a channel.

This channel service gives the opportunity to users to manage a 
channel. This is *not* ownership because the service will only 
be placed on the channel if that there is a general demand for.
It cannot be used in channel wars/op wars or in an attempt to
end "take over" a channel.

The Channel Service works the same way that a bot works.
It can control all channel modes (including ops). One
advantage that the service has is if ops are lost either due to
someone messing up and deop'ing everyone (or a flooder/hacker
doing it intentionally) then the bot can use Uworld (special
Undernet service) and regain ops. 

The Channel Service has many different modes. AlwaysOp will
ensure that the bot always has ops. If ops are ever lost or the
bot is unable to join the channel then the bot will use Uworld
to gain access. NoOp mode will make it so the Channel Service is
the only Op on the channel. All kicks, bans, topic, etc
have to be made through the bot. Mode changes still need to be done
manually. The bot also has flood protection against nick, kick, 
topic and mode changes to ensure that channel flooders are not a problem.

The Channel Service retains a userlist for every channel that it
is registered on. The manager of the channel (person who registered
the channel) controls the list for that particular channel.




Committee Guidelines
--------------------

The Channel Service committee is a sub committee of User-com (Undernet
user committee). They are in charge of the administration of the 
Channel Service. The Channel Service Committee (CSC) is not a place
to complain about how a channel is run (ie: content, rules, etc).
However the CSC will mediate discussion on the "managing" of the 
channel.

To get a channel registered an e-mail message must be sent to 
cservice@undernet.org containing the following information:

Name:
Nick:
E-mail Addresses:
Real Name:
Channel Name:
Purpose of the Channel:

All e-mail addresses that are used on IRC and at least one mail
address that the applicant can be reached at should be included.
If a hacked user@host is used on IRC, a valid mail address is
necessary.

At least 5 supporters are needed for the request to be processed. 
Each user may register 1 channel with some exceptions for
special service channels (for example #Help). The word user 
does not mean e-mail addresses or nicks, but users themselves.
This will be difficult to monitor but we would appreciate honesty
in regards to this. 

The proposal is then posted to alt.irc.undernet and the user-com
mailing list for a discussion period of 5 days.

Provided there is no objections a quick meeting on the channel with 
the applicant and at least 5 people that support the idea is required 
(this only takes a few mins to ensure that everyone is going to be 
aware of the channel service entering the channel). The channel service
will be moved into place. 

If there are valid objections to the Channel Service to be on that channel
and mediation is unsuccessful then the Channel Service will not be 
placed onto the channel. In this case the applicant should be encouraged
to reapply with a different channel name.

If once the Channel Service is in place, someone wishes to obeject,
the CSC will attempt to mediate a solution. If the objection is unreasonable
or unsupported by a reasonable number of users then the objection will
be ignored. If no mediated solution can be reached then the Channel
Service will be removed from the channel.

Any abuse of the channel service by the channel manager will result in the 
immediate removal of the service. Any abuse of other users will result
in their refusal of the service to that user. The above includes anyone
"testing". If testing is required, there is a test network of Undernet
servers that can be used. If a CSC administrator finds that the Channel
Service is being abused in any way, they may remove the channel service 
from the channel immediately and relay any necessary information to 
other CSC members and contact the manager of the channel immediately
with the reason for the removal. The removal will be open to immediate
review by the CSC to ensure that the service was abused and to decide
if the Channel Service should be returned the channel or not.

The registered channel manager must appear on the channel once every 3 weeks.
If the CSC is notified of a prolonged absence a the channel managing
may be transferred for the intermittant period. Any abuse of the Channel
Service done by the temporary channel manager will be both the responsibility of
the channel manager and the temporary manager.

A listing of channels that are covered by the Channel service will be made
available for FTP from ftp.undernet.org in /pub/irc/docs and 
changes to the document will be posted to user-com on a regular basis.

The Channel Service will not be responsible for any activity that occurs on
the channel. Anything that occurs on the channel are the resposibilities of the
people involved and has nothing to do with the Channel Service, its 
administrators,
and the Undernet as a whole, including the Operators that run it.