ChatNet policies. 7/31/01

This is a revised edition of the ChatNet Policy revised by the EC, sh0rty, Vagabond and Vampire.

Below you will find EC's revised Constitution. This was done because no one came up with a working solution to our ultimatum. Ideas were tossed around, but never finished. We will now work from this one.

The Constitution and Guiding Policy of the ChatNet IRC Network

Revision 9.0.2 [4/29/1999] Written by mlong of RockHill.SC.US.ChatNet.Org

Michael Long (mlong@mlong.net) Changes via cadmin discussion and approval.

Revision 9.1.0 [10/5/00] Revised by Executive Council, namely dr-who, bp and phantasy

Revision 9.1.1 [7/30/01] Revised by sh0rty of Atlanta.GA.US.ChatNet.Org [Ray Crane] (sh0rty@sh0rtyisgod.org) and Vagabond of Indianapolis.IN.US.ChatNet.Org

[Seth Fuller] (Vagabond@alias.chatnet.org)

Revision 10.0 [8/20/01] Revised by Executive Council of ChatNet (executive@chatnet.org)

[ INTRODUCTION ]

This document is designed to be a guiding document for the ideals, values, and ideas of the ChatNet IRC network.

[ IDEALS ]

This network is here for the enjoyment and entertainment of our users. It is also designed for the free flow of ideas and opinions between individuals. Individuals should be able to state opinions without being killed or G:lined by administration. ChatNet officials are here to assist in the smooth operation of the network and to ensure users have a pleasant online experience. At all costs, anyone impacting the fun and entertainment environment of the network (especially through harassment, flooding, and extreme unprofessionalism or rudeness to users) must be removed from the network. Glines and kill messages must be professional.

[ POLICIES AND RULES ]

There are few set policies on the ChatNet network other than this document. The administrators of this network want everyone to use common sense and to act sensibly and to the best of their abilities when conducting themselves on the network. ChatNet officials should use their best professional and moral judgment to the best of their abilities when dealing with situations on the network. As it becomes necessary, policies will be amended to this document.

[ ABUSE, AND COMPLAINTS ]

Complaints and/or abuse about Admins or Global Opers will be handled by the Abuse Commitee. They will investigate the complaint(s) and hand down judgment. Appeals of these punishments will be considered when there is grounds to do so. We will be working on a “three strike you're out for good” system, unless the offence is deemed to be a charge for immediate dismissal. Local opers will answer to their Admin. If complaints are lodged against them, then the Admin and Abuse Commitee will work together to decide what should be done.

If an oper and/or an admin is removed for abuse, then he/she will not be allowed to serve in any official capacity again.

This was changed as now the abuse commitee is handling complaints instead of EC.

[ PERSONAL DISPUTES ]

Personal disputes between ChatNet officials have no place on the mailing lists or in public. We are to remember that we are here for the users at all times. If you dont like someone, then learn to live with it. It happens in real life too. Remember that we are still users ourselves, and should follow the advice we give them. Using /ignore is a usefull tool.

[ ROUTINGCOM ]

RoutingCom is responsible for maintaining, recruiting, filtering and linking the best servers available to ChatNet. In addition, RoutingCom is responsible for maintaining and distributing server lists to all known IRC clients and to the ChatNet webmaster(s). To this end, RoutingCom will be maintaining and publishing its own standards for determining the best servers to be linked, a website [http://routing.chatnet.org] for collecting applications, its own process for weeding out undesirable links, and making the initial 45 day probationary link to ChatNet. This process will be in writing and be posted on a website. The committee will also maintain the C/N/H/U/Q, ServerIDs, numeric M codes, and server configuration information that is essential to the function of this network. EC & Admins will choose a person whom it feels has the best ability to both understand routing and effectively lead a group. That person will pick his or her team, along with EC and proceed on accomplishing the tasks and goals of RoutingCom. The RoutingCom chair will serve as long as all parties are agreeable.

[ NEW SERVERS ]

*** New servers are automatically assigned to a probationary period of 45 days. At the beginning of a probationary period, RoutingCom hands over all data about the probationary server to cadmin. A week before the end of the probationary period, RoutingCom will announce to cadmin that it must vote on a permanent link of the server. The cadmin secretary will proceed to setup and track the vote. Cadmin can vote on the server link at anytime before the end of the probationary period. Cadmin can also extend the period of a probationary link if it so chooses. If a server is voted to not be confirmed, that server must be delinked from the network within 24 hours. This includes jupe and removing CN lines from hubs. New servers will not have voting rights until they are out of the probationary period, and they will not be on the admin-only mailing list until they are out of the probationary period. The server will also be placed in the round robin to see how many users it can bring/handle within 10 days of linking and will continue the evaluation process. Routing - Global opers of test-link servers are not to deal with the routing scheme of the rest of the network. If no Routing-Com members are present online, full-link server opers will handle the connectivity of the network. Test-link opers are allowed to move their server ONLY.

[ V-LINES (Vanity Lines)]

1. V-lines will conform to standarnd user@host naming conventions.

user@domain.tld (Top Level Domain)
user@host.domain.tld

The username will not contain the character "*" or ":". The hostname
will only contain alphanumeric characters, "-", and "_".

Acceptable:
my_name@2600.org
whatever@I.dont.care.as.long.as.it.meets.the.above.guidelines.ok

Unacceptable:
.@.
*@*
user@org
user@host..org
user@I.drive.a.ferrari

user@pull:my:finger

2. The Chatnet.Org domain will only be given to Chatnet Officials:
admins, opers, EC, CService, Routing.

3. V-Lines will not be offensive in nature. Use your best judgement.

If a server violates this policy, it will be notifed and will have 24 hours to correct the problem. It if is not corrected within this period it will be juped until the problem is corrected. (Certain circumstances may warrant a need to temporarily jupe the server the offending V-Line is resident on for network security.)

[ SERVER MODIFICATION ]

Your s_err.h file may be modified to display custom server messages/errors. These modifications cannot include any profound language as users will be seeing these messages.

[ MAILING LIST ]

There will be 3 mailing lists. One for Admins only, one for Admins, heads of committees (if needed), and test-link admins and one for opers. All Officials will be required to be the appropriate list(s). Opers must be on the Opers@ list, Admins must be on the Admins@ & Cadmin@ lists. Professionalism will be exerted on ALL lists. Argumentative e-mails can’t be avoided, but they can be limited. If a thread starts between two or more people, and someone requests it to be removed from the list and carried on in private (within reason), all parties MUST comply immediately.

[ CSERVICE ]

Admins and ircops can help to solve K9-channel problems if they have been properly trained by CService. You may contact Cservice for that training. CService is a self-governing body with respect to members (it appoints its own members as needed). Admins and ircops should not interfere with the daily operation of CService . They are directly accountable to EC.

[ FUN ]

Ircops and admins can use wallops but should limit these to the bare minimum as it draws unneeded attention to the opers and can leave a bad impression on Chatnet as a whole. Inappropriate language or subject matter will not be used in /wallops. Please keep in mind we have ChatWorld’s OpMSG for this purpose. Ircops can kill each other, and can use K9 say and act as long as things do not get out of hand. If someone asks you to stop, you should stop.

[ SPEAKING YOUR MIND ]

It is ok to express any negative feelings you have about the network, a policy, an admin, or an ircop BUT they cannot be public. Do not mouth off in #nuthouse, #chatnet or wallops...keep it private. Similarly, the official ChatNet channels are for assisting users only. Users are offered no protection from kicks and bans when they state opinions or chat excessively in official channels. Officials shall do whatever is necessary to ensure that their effectiveness in helping users is not hampered by individuals who wish to chat, insult, or otherwise tie-up official channels. Users in #nuthouse may be ban for any reason by an Admin/Oper as its now the offical "chat" channel of ChatNet where users and Officals can interact, users should not be given access in this channel.

[ OFFICIAL CHANNELS ]

An official may be in any channel which is allowed. Individual servers may enact their own policies regarding what channels ircops are allowed in if they wish. Only in the case that both K9 and Chatworld are down at the same time will ops in official channels be allowed to op others. Whenever k9 or Chatworld are available then the only acceptable way to gain ops in official channels will be thru one of those. No auto-ops scripts will be allowed. #ChatNet is the official administration channel. All ircops and admins will be in this channel when they are opered up and ACTIVE and willing to help users. If you do not want to help users, please do not hang out in #ChatNet.

#administration is the ChatNet officials channel or if you wish to chat, then #nuthouse is the channel for you.. #doghouse is the CService help channel. #help is the official help channel. All Admins/IRCOps will have their level on k9 established according to the channels individual "Code of Conduct" (CoC) and will be governed by their individual channel rules/guidelines. However, it is noted that any person who is legitimately +O in a channel (registered or not) may kick or ban any official for any reason. #help and #doghouse are help channels and should not be idled in as this confuses the user and the other helpers as to who can help and who is helping. If you aren't in there to help or there in some official capacity, then part. There are to be no scripts running in #Nuthouse, #ChatNet or #help. This includes bots from staff or users.

[ SERVICES ]

K9 is the official and only channel service. ChatWorld is the official and only operator service. There is no NickServ service, and private NickServ services or bots are banned from the network. No automated script or bot that is not an official service may have a O (global) line. You may kill or gline someone that uses your nick if they are trying to impersonate a Admin and/or a IRCop and/or Cservice. You MUST first message them asking them to change it, then kill, then gline.

[ BROADCASTS ]

Officials should ensure any global broadcasts they perform are of a substantive and needed basis. ChatWorld broadcasts will not be used for fun and games. We will be using it for announcements to the users.

[ CO-ADMINS ]

CO-ADMINS are the same as an Admin. They are of equal status. If this is not the case, then they cannot have a Co-Admin.

[ GLOBAL IRCops ]

Each server will be allowed to have 4 O:lines per *server. This includes the Co-Admin. This could mean you can have 3 *opers if you have a co-admin or 4 if you don't. These opers will be Global Opers and they will be accountable to All Admins and EC. However, if the Admin has a personal problem with any of the Global Opers, he/she should not try and discipline him/her, but refer it to another Admin or EC member. Global opers are to help users and help the Admins run their servers. They can also help local ircops when needed. global oper.

[ LOCAL IRCops ]

Local IRCops are responsible for the server they represent. Admins can add as many as they feel necessary to help run the server (within reason) People do not need a o:line to help the users. We can give them v:lines called helpers or something.

[ HELPERS ]

Helpers are responsible for helping the users of Chatnet. They need no o:line to help. Maybe v:lines if needed. The HelpTeam in #help, like Cservice, have their own policies but are overseen by EC.

[ NEWS-COM ]

This is the newsletter team. Only active members will be allowed. Dedicated members are always welcome.

[WEB-COM]

A group of people that keep the Chatnet website and Chatnet webring up to date.

[ K9 ]

Admins may add their own local ircops to official channels. If a local is added, it must be reported to the Cadmin list. Locals will be added at lvl 200 + there server numerical. ie: sh0rty on atlanta lvl 200 + 40 so sh0rty will be added lvl 240 in all official channels.

[ OPINION PROTECTION ]

No official may be removed for speaking their opinions or views as long as it is in a private setting (not visible to users). Admins can ask EC to remove a global oper from another server if there are grounds to do so.

[ EXECUTIVE COUNCIL ]

The executive council consists of appointees of Nu Tech Software Solutions, Inc., the sponsor of K9 and DNS, and well trusted members of the ChatNet administration as picked by other members. Currently the council consists of Dr-Who, BP, and pHaNtAsy. MrMud and LabattZ.

[ SERVER OFFICIALS ]

The following list is a list of recognized ChatNet officials. All officials must fall into these categories: -admin -global ircop -local ircop -committee member (RoutingCom,CService,Executive Council,TeamHelp etc.)

[ HIERARCHY ]

Executive Council govens all officials. Cservice, TeamHelp and other committees answer directly to EC. Global Ircops report to both Admins and Abuse. RoutingCom report to both Admins and EC [removed Abuse, Abuse can petition the EC to force changes on RoutingCOM if EC see’s fit] . Admins report to Abuse and EC. Local Ircops report to their Admins

[GENERAL IDEAS/POLICIES]

Spammers: Instead of just killing and glining these people. You may do those things, but you MUST also try and contact both the site they are advertising and the isp they are using to let them know of the spamming and that we do not allow it. If we cannot get satisfaction, then we should kline them off each server (unless we can set longer glines)

Clones: We feel that 20 clones should be allowed. If they are flood bots, then we will know about them as we know the channels they flood. After an excessive about 2-3 of 20 clones they should be masskilled with a warning stating to recieve a clone exemption. I want to see this lowered. 20 clones is obscene.

Viruses: We must try and help the user that is automatically sending viruses out before we kill and/or gline. We need to educate users, not just get rid of them the gline message should state a URL where the user can go to help rid of thevirus, as well as the Oper’s [only ppl with a global O: can G:, which makes them an Oper, on top of whatever else they are] email address so the user can contact them after doing so. This will ensure that users get the appropriate help they require.

[ #ChatNet ]

#ChatNet is a channel for users to be helped to the best of the staffs ability, this channel should have as much help as possible at all times. The more comfortable the user feels the more secure the net gets. This Channel should not be idled in by ANYONE including admins/opers. You may have an alias to welcome users and handle all questions and concerns in a serious manner. If a users idles for a extented amount of time then there should be a 1 min ban placed. When k9 is down for upgrades or due to inconvenient situations, opers should have a Cservice member verify access of users in the channels they are reqesting op status in, this will narrow down the chances for Takeovers as well as keep all channels in control. IF a cservice member is not available then all staff should use common judgement to fix the situations. IE: joining the channel and asking ppl there for objections to your oping that person. When in the situation k9 is down, Cservice is welcome to help in #ChatNet they should be oped and will provide the help needed. Any other time Cservice should not be in #ChatNet unless they have a question or problem that needs taken care of.

No excessive talking will be allowed in #ChatNet while users are being helped, if for any reason someone is being disruptive send a wall notice or private notice to them to control there selves, if this fails then feel free to set a limited ban on them, until the situation is resolved.

[ Domain Glines and K:lines]

Domain Glines should not be set by opers unless they have permission from administration or the EC.

All K:lines will we added to ALL servers this will be passed on via cadmin foropinions. when all are in agreement a global K:line will be added to theircd.conf file and will be perm removed from chatnet.

[ Kill messages ]

All kill messages should be appropriate for teens and should be handled in an appropriate manner, and professionalism. You should never kill for dos attack, as this is client to client, and does not effect our network servers. A warning should be issued for ALL kills, except massive amounts of floodnets and text flood. Oper should always resort to a warning first the proceed to a kill if this does not work.. If the problem keeps happening then you should set the appropriate time limit on glines.

[ GLINE ]

This should be a last resort for all Admin/Opers first speak to the person then if the problem persist kill the users with an appropriate warning, if the problem still continues a gline is needed. Spam should be glined and reported to the users ISP. Harrassment of Opers is NOT a reason for a gline, use /ignore. But if they evade this and continue to harrass, a gline may be called for. No other opers gline should be removed by another oper, although and admin may remove any opers gline if they have a good reason to do so.

[ CADMIN ]

Cadmin should be used for admins to express there opinons, vote, and get things done. If you don't plan on being active on this, then you need to reconsider your adminhood. All admins should vote on every proposal, and should give there opinions on things. This is a RIGHT for admins, it should be used, and if its not then EC and/or abuse reserves the right to remove it from any admin at the EC/abuse disgression. (what does this mean?) In other words, if an Admin refuses to vote repeatedly on issues, EC/Abuse reserves the right to nullify said admin’s vote in future issues, should the admin suddenly feel compelled to vote on a subject.

Cadmin is a right, you are on the list for a reason, and should exercise the right of this commitee or not be listed on it at all. This gives every admin no matter there server status the right to have an equal opportunity to get their opinons heard.

[ VOTING ]

Any modifications, additions, or deletions of portions of the constitution, policies, or anything that may impact ChatNet shall be voted on in the cadmin mailing list. Any proposal that may be brought up for a majority vote must have another admin second the vote. Each proposal must have the proposing admin call it to an official vote, and state so in his/her email. The proposal must be seconded within two (2) days of being proposed, or the proposal will be killed. A proposal may not be seconded by the co-admin of the server that proposed the vote. If there has been a motion made by another admin to second the proposal, then the list admin must recognize such and call the proposal to a vote, which will then end the two day period. The list admin will then send an email to cadmin recognizing there has been a motion made, and what day the vote will end (five days from list admins receiving the seconded vote). The period from which the proposal is called to vote, until the end of the vote will last five (5) days. During the five days, the proposal should be discussed in cadmin and each admin should ask his/her staff what their regards are to whatever motion may be on the floor. After the five day period is over and all votes have been cast, the list admin will tally the votes and submit the results to cadmin. All results will be anonymous, and will be represented by how many admins voted YES, and how many NO. A proposal must have at least 51% majority to pass. Any modifications to this document or ChatNet policies will be made accordingly. Any other matter, such as removal of a global oper for example, should be carried out within 48 hours of its passing. Failure to, for example remove an oper, would result in a JUPE until said server complies. Each admin may vote however he/she pleases, but it is suggested that each admin talk over whatever motion may be on the floor with his staff. ChatNet is a team effort, and everyone has a role.

Proxy Votes - During the two day proposal period, if the vote has yet to be seconded, a proxy vote may be submitted to the list admin. For example, if you are leaving town the day something is proposed, you may submit a 'YES' or 'NO' vote, just in case the proposal is brought to vote while you are away.

Eligible Voting - Either an admin or co-admin may vote for their server, but not both. Whoever is in charge of the server primarily, whether it be the admin or co-admin may vote for the server. Each server gets ONE vote. An admin who may have two or three servers to ChatNet still only gets ONE vote. ONE admin, ONE mind, ONE vote. Test-Link server admins may not participate in vote, but are free to discuss the proposal as they wish. Services such as ChatWorld and K9 will also be able to vote. The Head Coder of ChatWorld will be allowed to cast one vote, and the head of ChatNet Channel Services will be allowed to cast one vote.

As said earlier, EC has final say if they choose to (this is only exercised when the EC believes the decision that Cadmin has made is not in the best interest of the network or it’s users; or when Cadmin cannot reach an agreement on their own.

[ Opers ]

Opers list is used for opers to give there opinions and be heard this is a right for opers and should be used by all as well. This mailing list should not be for personal flaming You can do that all day in private message on irc. If you as an oper wish to propose something that you think will benifit chatnet you may at anytime go to your admin and he/she will take the appropriate action to get your idea heard.

[ BAD CHANNELS ]

Child pornography, animal sex, or incest channels are not welcome on Chatnet. These channels will be locked and shutdown permanently. Also, the people that are in these channels will be glined. We could also possibly contact the ISP’s and local Federal Officals.

Floodnet, and clone channels will also be locked and kept locked along with sub7 virus channels and illegal warez channels. All people in these channels will be removed from Chatnet, without question.

[ CHATWORLD ]

ChatWorld is the oper service bot, it is there for everyone to use and all opers will have a working knowledge of it, and at anytime in doubt should ask a global oper or admin to help. If you have a feeling that something is wrong and shouldn't be done, then chances are it shouldn't so trust your instinct. If you abuse your chatworld privileges then you could not only be removed from chatworld, but you could also lose your oper status.

[ WALLOPS ]

Even though wallops are for +w users only, a lot of clients auto set this mode for users. This command should be used to a bare minimum and restricted as much as possible. If you wish to chat to other ircops then feel free to go to #administration or use opmsg. Isn’t this duplicated above? (read way up)

[WINGATES]

Any server acting as a client server is required to run a WinGate scanning bot.

This bot will require a local o:line (NOT an O: [global])on the server, and your server will need to be compiled to allow local opers to add local GLINEs. You may use any version of eggdrop you wish, and the TCL may be found on the ChatNet Routing-Com FTP. ChatNet sustains a great number of clone/wingate floodbot attacks, and this scanning bot has been proven to substantially help the problem.

[Oper & Admin Training]

New Opers, New Admins, Testlink-Admins/Testlink-Opers must ALL pass the training requirements set out by the “Oper/Admin Training Committee” PRIOR to Opering up to perform daily tasks. This new committee will likely be closely associated with Routing-COM, and it’s members are still to be decided. At this point, Dkuntz has volunteered his time and expertise in forming this group and setting forth a quality standard that we will all eventually go through. No one with a global O: is exempt from this requirement. Further details of this committee will be written to this document once we finalize the details on this, and get the Committee Members properly trained and briefed.