Draft IRC Channel Policy v1.1

Jason Lynch <jason@aexoden.com>

Preface

This document is a generic IRC channel policy that can be used as a base for a more specific policy. Its primary ideals are that of privacy, friendliness, understanding, and open access for all users, regardless of ISP, race, ethnic background, creed, religion, age, intelligence, or disposition.

You may wish to rewrite this or any other section to apply to your specific channel. In addition, you may wish to include other information about your channel.

Version History

v1.1 (2006 Nov 27)

Some minor rewording to improve readability.

v1.0 (Unknown date)

Initial version.

Chapter I - Channel Rules

  1. No excessive flooding. Flooding the channel makes it difficult for users to keep up, and can also make conversation hard to follow. In addition, it can make things difficult for users with slow connections.
  2. Entering the channel with the sole purpose of advertising another channel, network, web site, etc. is discouraged. This often disturbs users, and will rarely result in someone actually visiting what you are advertising. However, pasting appropriate links in the course of conversation is absolutely encouraged.
  3. No excessive swearing or other abusive language. Some people, for whatever reason, may be offended by this language. It is up to the channel operators to decide what it is excessive.
  4. No constantly capitalized lines. This is considered shouting.
  5. No harassing a user. Publicly harassing a user is prohibited.
  6. Don't ask for operator or any other status. These positions will be given out as they are needed.

Chapter II - What We Cannot Do

  1. Being kicked or banned in another channel is not sufficient grounds for equal punishment in this channel. A user may only be punished in this channel for doing something in this channel.
  2. Extending from the previous one, a user harassing someone privately is also not grounds for discipline in this channel. Use your client's ignore feature.

Chapter III - Discipline System

  1. The goal of any useful discipline system is reform, not exclusion, and as such, the following system is a guideline. Immediately banning a user is a terrible thing to do, and as such, is not a permitted first step. However, in some cases, it may be prudent to temporarily remove a user from a channel while the situation is explained to him.
    1. After a first offense, the operator should publicly or privately message the user, explaining why what they are doing is against the rules and give them a fair and valid warning.
    2. If this fails to work, or the behavior is such that it is difficult to do (e.g. flooding), the next step is to kick the user. In many cases, this will help control the behavior. In many others, however, it just riles them up.
    3. In the event the first two options fail, a temporary ban or silencing for 30-60 minutes is recommended. These bans must be designed to affect as few people as possible.
    4. If the user returns after this, a longer ban of 24-72 hours is recommended.
    5. If after this ban expires, the user returns and continues their behavior, a semi-permanent ban of 1-6 months, depending on the severity of the transgression, may be required. Once again, these bans must be as specific as possible. In the case of difficult to isolate users (e.g. Java users with dynamic IP addresses), it may be necessary to kick the user on sight, or use multiple single-IP address bans. ISP-wide bans may be used as a last resort, but these bans should never last more than a couple of hours.
    6. Finally, the network administrator and possibly the user's ISP should be contacted if no other solution can be found.

Chapter IV - Problem Resolution

  1. If you are kicked or banned and don't understand why, first contact the person responsible for your kicking or banning. If he fails to explain, or if you believe he is abusing his powers, please contact the channel founder and explain the situation in detail, providing logs if necessary.