OPERATING INSTRUCTIONS OF THE WINCHAT NETWORK 1.4b

WinChat servers not in compliance with this document will be removed from the Network.

0. Rule Sets 1. Users 2. Staff 3. Committees 4. Channels 5. Bots and Clones 6. Servers 7. Legal 8. Respect

Revision History: 1.0 by DeMENted, Dec 2000, approved by WinChat staff 1.1 by DeadMan, Feb 2001, approved by WinChat staff 1.2 by Astragal, May 2001, approved by NA 29-9-2001 1.3 by Astragal April 2002, approved by NA 20 April 2002 1.3a changed opping of bots in official channels. 20 May 2002 1.3b changed security and abuse sections, 31 July 2002 1.3c changed the approval of CSOPS, 1 Sept 2002. 1.3d added #winchat-bots 1 Spet 2002 1.3e modified 0.2 to “of those present” 27 Sept 2002 1.4a Major Edit, Added Devcom, reordered topics, changes in committees, voting, orgazizational stuff. Most changes marked with comments, deleted TA, deleted “on the winchat server” and other communications committee stuff Minor: deleted #asylum, chan characters, changed testlink.. 1.4b inci need orporates evo’s edits from NA meetings, limit on committees,exclusivity removed, etc.

0 Rule Set

0.1 General: The WinChat Network exists for the co-operative education of the staff and the amusement of the users. This rule set details the actions which the Administrators and Staff of the WinChat Network will take to maintain the network.

0.2 Initiation: This rule set exists to help us setup, run, maintain, and protect our network. The rule sets applies only after a NetAdmins meeting has voted by simple majority of those present to verify that the rules are in the network’s best interests.

0.3 Enforcement: Network Administrators (NA) will deal with any non-adherence of these instructions quickly and judiciously, first by warning the server admin of non-adherence, then by temporary or permanent removal of the server of the offending staff.

0.4 Modifications: Amendment to these rules can be added by majority vote of the NetAdmins. No one has the right to make any changes/amendment to the rule set without first holding a NA meeting. (see Voting)

1 Users

1.1 USERS are our base. Users are the network’s reason for being: the users should be treated as customers, or clients. No IRC Chat network can exist without users and the whole staff is charged with finding users, bringing them here, and, treating them well.

1.2 Abusive users: However, users can be abusive, to staff, servers and one another. Staff will handle those users who become truly abusive and obnoxious, or act in a way that threatens other users. Some actions that require operator intervention are: malicious flooding; channel takeovers; advertising; and, denial of service to other users.

1.3 Tolerance: Staff will not /Kill or /Gline a user because of the user’s attitude. Remember, each operator/staff represents this network, and a bad decision on your part reflects not just on you and your server, but on the entire network. Think before you act. [ceh1]

1.4 When in doubt: If you are unsure about how to deal with an abusive user, ask another staff member before you make your decision. Staff will be held accountable for their actions against users (see abuse committee). Remember, users are here for one purpose, to have a safe an enjoyable time on an IRCD server. Let’s make it that for them!

2 Staff

2.1 General Staff: The Staff members are the work force of WinChat. All staff, when opered, will wear the hostmask <ident>@<position>.<server>.winchat.net. All staff falls into one of four categories:

a Director of WinChat

b Server Owners (NetAdmins, or NA)

c Operators (IrcOPs = Operators + NA)

d Committee Members

2.2 Director Of Winchat.Net: sets guidance on all network questions asked by NetAdmins.

2.2.1 The Director is elected by ¾ [ceh2] majority of the NA, and holds the position until he relinquishes the position, or until the NA votes by a ¾ vote of all NA to reappoint[ceh3] the position.

2.2.2 The Director may not be a NetAdmin, and is entitled to the SA line.

2.2.3 The Director acts as “Tie-Breaker” [ceh4] in NetAdmin and Staff votes.

2.2.4 NetAdmins can override the Director’s decision by 2/3 majority.

2.2.5 The Director wears the mask @Director.WinChat.Net.

2.2.6 The Co-Director is the Director’s back-up. All duties usually performed by the Director will be performed by the Co-Director in the Director’s absence. This position is elected by simple majority of the NA, with the Director’s consent.

2.3 NetAdmin: (N flag). Network Administrators are the backbone of this network. These are the people dedicated to providing the network with their time and machines. They run the network and are involved with every other group.

2.3.1 There may be only one NetAdmin for each permanently linked server.

2.3.2 The NetAdmins are completely responsible for controlling their servers and their own staff. [See servers and operators]

2.3.3 A NetAdmin may have O line(s) on any other server as backup, but the backup line is restricted to Global Operator, (simple 0:line).

2.3.4 NetAdmins are not Gods! The NA group will hold each NetAdmin accountable for their actions. Simply put, this means that if one does something viewed by as wrong by others, there will be a meeting/vote to correct the problem, which as a last resort may result in the NetAdmin’s server being juped.

2.3.5 A NetAdmin may administer only one server.

2.4 Co-Admin: (C flag). The server Co-Admin is the NetAdmin’s backup person.

2.4.1 There is only one Co-Admin per server.

2.4.2 If a NetAdmin cannot make a meeting, or is unavailable for discussion, the Co-Admin replaces the NetAdmin temporarily.

2.4.3 Co-Admins must inform their NetAdmin of all of their actions taken in the NetAdmins absence; the NetAdmins are ultimately responsible for the actions of their Co-Admins

2.4.4 A NetAdmin on one server cannot be a Co-Admin on another server.

2.5 Server Admin[ceh5] : (A flag) the NA of a server may give out one A flag to an operator of choice.

2.6 Irc Operators: These are the people we depend upon to maintain the connectivity of network as a whole. They will control/help our users with anything they need.

2.6.1 Operators are responsible for setting the example to the users of our network. Both local and global opers are responsible to their admin and server.

2.6.2 Operators may not use their protective network commands (like /kill /gline /kline, etc.) for personal retaliation. Network commands have no place in personal disputes.

2.6.3 Global opers are also responsible to the WinChat network. If any problems arise with a local or global operator, their NetAdmin will be informed of the problem. The NetAdmin is expected to resolve the problem. If the NetAdmin is unwilling or unable to resolve the problem, then that NetAdmin’s server could be delinked (this requires a NA vote).

2.6.4 If the oper’s NetAdmin is unavailable, other NetAdmins will handle the situation until the NetAdmin becomes available.

2.6.5 There will be periodic meetings of all opers. The use and rules of rooms is set by the operators group. Operators are responsible for the coordination of these meetings.

2.6.6 All opers must be in #staff while opered.

2.7 Committees: Committee members are considered WinChat staff.

2.7.1 Committee members may participate in any all-staff (everybody) meetings.

2.7.2 Committee members are expected to behave with the dignity expected of any other WinChat staff

2.7.3 Committee heads are responsible for the behavior of the people on their committees. If a committee head does not deal with a problem with their staff, then they may be replaced as committee head by a vote of the NA.

2.8 All staff are expected to follow the guidelines in Respect .

2.9 Na Meetings: Voting, adding new principles, changing the WCOI.

2.9.1 Each NA is responsible for representing not only a personal view, but also the combined views or their staff. Each server administrator, or co-admin, is responsible for gathering the input from that server’s staff.

2.9.2 If the NA votes a decision that is considered not in the best interest of the network by the vast majority of staff, then the staff (opers and committees) may overrule the NA by a ¾ majority vote.

2.9.3 Any issue passed by a simple majority of the staff will become a rule of the network, which the NA may overrule by a ¾ majority vote.

2.9.4 Meetings of the NA and of the Staff are self-organized. Use the web-board and email groups (as well as IRC J) to prepare for meetings. Meetings are, in general, for the voting of issues, not discussion of issues.

2.9.5 All formal meetings must have a minimum of one week’s notice; all e-mail votes must remain open for at least five days. “Majority” is considered as more than ½ of those present or responding. Non-attendance or non-voting is considered an abstention.

3 Committees

Routing | Channel Services | DevCom | Abuse | Postmaster

3.1 Commitees in general.

3.1.1 The head of each committee is appointed and approved by a simple majority vote of NetAdmins.

3.1.2 The membership of each committee is basically up to the Head of that committee. The NA, by majority vote, may remove people from committees, if there is evidence of abuse, incompetence[ceh6] , or poor regard of the network.

3.1.3 Each committee may have a specific V-line assigned to that group. The head of a committee is responsible for the security and password for the vlines.

3.1.4 Each committee will maintain a relevant page on the website, or is responsible for communicating with DevCom, the content of their pages.

3.1.5 Each committee runs parallel, but separate to, the governing body of WinChat. While the committee follows a the protocol within the parameters outlined in the WCOI, all internal politics and rules remain internal to the committee.

3.1.6 Staff may head at most one committee, and serve on at most two committees.

3.2 ROUTING (Y and F flags, ident@routing.winchat.net): this group is responsible in configuring the way the servers on the network will connect, and how the network will deal with missing links, dropped servers, server security, and servers being attacked.

3.2.1 Routing: Maintains the /map, and long-term connectivity concerns of the network. Short-term connectivity is maintained by the opers based on the direction set by routing.

a Provide to the staff of any new server the entire technical documentation required for a server on the network (help files and conf files)..

b Assist a new NetAdmin on setting up a new server.

c Maintain an ideal connection map and determine leaf/hub relationships, based on reliability and /rping responses.

d Maintain a webpage of active servers and IP’s.

e Screen new server applications.

f Investigate and test upgrades to the IRCD, test alternate IRCD’s..

3.2.2 DNS Services: controls the WinChat.net domain name.

a This is not an elected position.

b Maintains the DNS address database, and the round robin.

c Provides DNS paths for servers, network web site, and server websites.

3.2.3 Security: This sub-group is responsible for the security of the network as a whole.

a Ensure all linked servers have the latest fixes/patches to their OS.

b Test all servers linked periodically to assure they are reasonably secure, and report results and fixes to Admin.

c Issue notices on new vulnerabilities and updates, and inform NetAdmins.

d Report of any surprise testing will be given to the server NA within one day.

3.2.4 Coding: Investigates and tests upgrades to the IRCD, tests alternate IRCDs.

a Coding is responsible mainly for server stability, security, and future features and upgrades to the IRCD code.

b Any new code or features must be thoroughly tested and demonstrated to NetAdmin before being implemented on the network. [ceh7]

3.3 CSERVICE (lower “a” flag, ^ (invisible) flag, vline: <ident>@cservice.winchat.net): this group maintains control of channel services and services as a whole.

3.3.1 CService is responsible for responding to users in all channel matters (registration, deleting, updating, passwords). [See Channels]

3.3.2 CService is responsible for responding to users in all nickname matters (Qlining nicks, control nick services, passwords). CService determines acceptable nickname parameters.

3.3.3 CService sets default clone limits and makes clone exemptions. [See Clones].

3.3.4 The Head of this committee will have executive access; senior members are designated and empowered as (root) SRA; other members have CSOP status.

3.3.5 CSOPs will be kept to a working minimum.

3.3.6 CService-coding: This subgroup is responsible for research and testing of services. Any modification of services must be tested and submitted to NA before implementation.

3.4 DEVCOM (ident@devcom.winchat.net): This group is responsible for the basic continual development of WinChat. They will work and assist in several areas, including but not limited to growth, advertising, and operator training assistance.

3.4.1 WebSite: Create and maintain, and promote a functional website.

3.4.2 Visibility: Ensure placement on IRC clients to further our presence to the general public, and look for ways to increase advertising of WinChat.

3.4.3 Help: Provide a working help & public relations department using both staff and knowledgeable users to ensure help to all, including but not limited to, IRC, services, and network help. This area is intended to grow as helpers in several areas are acquired.

3.4.4 Training: Create a starter pack of pertinent information to be used by the NA as they attain new staff members. This pack will not replace personal training that each NA is responsible for but will contain documents such as the WCOI, operator commands, server list & map, etc.

3.5 ABUSE (“abuse committee” no special flags, vline: ident@abuse.winchat.net): This committee has five members, the Head of Abuse is approved by the NA and makes four additional appointees.

3.5.1 Operator abuse of users or of other opers: Collects any complaints registered at abuse@winchat.net . Contacts the offending operator’s NA if warranted. Makes recommendations to NA as a group if the operator’s NA response is insufficient.

3.5.2 G-line resolution: Periodically culls the Gline lists. Is the moderator of complaints regarding unjustified G:lines.

3.5.3 Channel closures: The Dispute Committee is the recourse for users who claim their channel was improperly killed or closed.

3.6 POSTMASTER: (Maintains the mail groups on the mail server)

3.6.1 Each staff member will be assigned an email account. When you are added to staff, or want to change your account information, please email Postmaster@WinChat.net. Specify your “account name”, your “display name”, and your password. The account name is your email address @winchat.net.

3.6.2 Email for all staff will not be abused: no spamming, no unwanted mail or arguments, and no soliciting.

3.6.3 Abuse of a mail account will result in its removal.

3.6.4 The following mail groups are supported:

a NetAdmins@winchat.net (posting limited to NetAdmins).

b Routing@winchat.net

c Cservice@winchat.net

d DevCom@winchat.net

e Abuse@winchat.net

f Staff@winchat.net (everyone on staff)

g Postmaster@winchat.net

h Director@winchat.net

i Help@winchat.net

j OperTraining@winchat.net

4 Channels

4.1 Channel Interference: Staff will not get involved in registered channel politics (other than WinChat Official channels). Interfering in channel matters leads to user discontent and preferential treatment – this is not allowed.

4.1.1 Staff may be requested to monitor a registered channel for abusive use of a channel/user and then recommend to the channel owner what actions can be applied to rectify the matter.

4.1.2 If the registered channel owner or ops have tried everything to solve the problem and an abusive by the user persists, then the WinChat staff can interfere for the good of the network.

4.1.3 Staff will not interfere with un-registered channels, except for topic.

4.2 Channel Topics: Channels topics are set at the discretion of the Channel owner, but offensive channel topics are not allowed. Offensive channel topics include any topics that discriminate against race, sex, nationality, or religion; channels may not have any profanity in their topics.

4.2.1 Offensive topics will result in a warning to the channel ops and a request it be changed. If the topic is not changed within a reasonable amount of time, or if the topic is changed back to the offensive one, then staff may force change the topic, or close the channel.

4.2.2 Staff personnel must take note that some topics may not seem offensive to you but could be offensive to others: be conservative and use common sense.

4.3 Channel Names:. Channels with profane, obscene, or pedophiliac names will be closed.

4.4 Channel transfers: Channels can transferred only by the “successor” function in services. Staff has no way to verify the successor based on user claims.

4.5 Official WinChat Channels

4.5.1 #WINCHAT: This is the General Help channel where the WinChat Staff go when opered and actively helping. If you are in this channel, set your mode to +h, and pay attention to /helpops. In this channel, help/assist users with any user problems (or direct them to a proper channel if it is not related to IRC or Network related issues). This channel shall remain +G at all times. If the channel is busy or crowded, enforce a no-idling rule.

4.5.2 (deleted: #Asylum)

4.5.3 #STAFF: This is the networks official meeting room, used for staff meetings, scoldings, and other official business This room will be mode +O only and not be opened to normal users. Anything we say or do in this room should never leave the room in unofficial capacity. All staff must be in #staff when opered.

4.5.4 #(CITY_SERVER_CHANNEL): each server linked must have a staff channel. Example: Niceville.fl.us.WinChat.net will establish #Niceville for its staff. Topic heading for this channel will always display a topic which refers to the server.

4.5.5 Access to official channels: the channel owner will add NetAdmins as SOP’s. NetAdmins are responsible for adding and deleting their own staff as AOP’s.

4.5.6 #WINCHAT-BOTS (official bot channel) This channel does not lend bots. It will give a list of ALL bot rooms on winchat where users can obtain a bot. It is primarily mainly a bot help channel. The lead staff of this channel is subject to approval by the NA.

4.6 Channel Content. [See the legal section for other channel content consideration].

5 Bots and Clones

5.1 Bots (Robots): There are only 4 Official Bots on WinChat Network: NickServ, OperServ, MemoServ, ChanServ. There bot names are reserved and may not be used by any other users nor mimicked by any user.

5.1.1 Any nicks closely resembling these CService nicknames will be asked to change their nicks or be killed off the network. Repeated attempts by a user to mimic services will result in a G:line

5.1.2 Bots are allowed on the network and in channels. Anyone may control peaceful channel-maintenance and entertainment bots. Flood or kill bots are not permitted.

5.1.3 WinChat Network offers technical support on bots only in the #WinChat-Bots channel. WinChat does not endorse any official bot channel for supplying bots to channel owners. #WinChat-Bots will direct you to various bot-loaning channels.

5.1.4 No bot may be opered at any time (given ircOP status).

5.2 Clone Exceptions: Under normal circumstances, all Users are allowed a certain number of clones, where “clone” is defined as additional client connections from the same IP. This limit is set by CService, and may change from time to time.

5.2.1 WinChat Services will kill off any clients in excess of this limit, unless exempted.

5.2.2 Clone exemptions are requested and granted thru CService. The reason for an exemption request msut be entered in the exemption record.

5.2.3 Exempted clones may not be used to abuse users! If the user that has requested a clone exemption and is found to be abusing it, it will be removed immediately without explanation. Appeals to a termination may be addressed to abuse.

5.2.4 Sometimes bots just run amok. If it found that the clone/bot went awry and has been corrected, then the CSOPs may reinstate the clone exemption.

6 Servers

6.1 Server Configuration:

6.1.1 Servers must use the basic configuration files provided by routing.

6.1.2 Servers must use the IRCD code and version used by the network: see the routing web pages for the current version.

6.2 Server O:lines

6.2.1 On a server there can only be one O:line with the N flag (Network Administrator). The flags for a FULL ACCESS Network administrator are: OARDNz*^.

6.2.2 Restriction on Flags

a There is only one C (co-admin) line per server.

b There is only one S (server admin) line per server.

c The ^ (invisible) flag is reserved to NAs and CService.

d The a (little a) flag is reserved to CService opers.

6.2.3 The total Global staff (including all N,C,S, A Flags) is limited to 8. There is no limit on the number of local opers.

6.2.4 NetAdmins are completely responsible for the behavior of their opers.

6.3 Server Rule Set: Any special rules for a given server must appear in that server’s MOTD and on the server webpage.. Special rules set up by the NetAdmin of each server must stay within the rules of the WinChat network.

6.4 Server’s Code of Conduct: instructions given to the NetAdmins of the WinChat network. NetAdmins will hold their opers to the same standard.

6.4.1 Represent the network! The first thing to remember is that an operator on this network represents all of the servers in the WinChat network, and of the staff.. By giving us your time and bandwidth, you are a very important member of the administration. Please use common courtesy at all times when dealing with the users and the staff. Be sure you have the right answers before making any decisions, even if it means seeking the advice of another staff member.

6.4.2 The way we treat others measures our success. All the staff must present themselves in the best manner possible. Your choices as an operator and the way you run your server will run will affect the network. IRC is fun and is meant to be fun. If we treat others with respect then they will also have fun here.

6.4.3 Some of us do run windows, and run the servers are on our own computers. This means that you’re going to need to reboot and maybe even shut down every now and then. We are the first network to use IRCD for Windows that we know of, we are the first to run most of these servers on hybrid connections such as cable and DSL, and we are the first to use our own computers as the server computers.

6.4.4 Communicate! If you have to shut down or reboot or /squit PLEASE warn the users ahead of time by sending a network-wide or server-wide notice that you will be dropping the server. Unexpected disconnects and servers dropping occasionally are normal to all IRCD networks . When an admin knows his server is going to be down, whether it’s for maintenance, upgrade, or needs down time for a while, he/she should inform WinChat@WinChat.net and send regular reports on his current status of his server.

6.5 Connection: At all times try and stay linked to your default /map connection defined by routing, don’t go connecting to anyone else unless your default link is not online or is seriously lagged.

6.5.1 Run a firewall while running your server, and make sure that ports 6660-6669, and 4400 are open; also, that any server IPs you are going to link with are trusted on your firewall.

6.5.2 If a server linked to you happens to drop, issue the /connect command to try and bring it back. If a server that is normally supposed to link to you is now linked to a different server ask a NetAdmin or one of the globals on that server to send a warning message and move the server back. Don’t attempt to move it without asking unless no one is available to ask.

6.5.3 [a8] Any server remaining disconnected for more than three days without cause or explanation will be de-linked from the network.

6.6 G, K, and Z:lines: All opers can issue G:, K:, and Z:lines.

6.6.1 G:line ban a hostmask from connection to the IRC server temporarily. Timed G:lines are what are used the most on a network sever.

a Staff (Admins/Opers) will respect another staff’s G:line and not remove it unless the operator removing the G:line has asked the person that placed the G:line if it can be removed.

b Glines shall be at most 15 days for a first offense, 30 days for the second, and perm for the third.

c G:Lines may not be set for personal reasons.

d G:Lines with no reason set may be removed by Abuse Team Members without notification to the Oper or Admin who placed the G:Line .

6.6.2 K:line permanently bans a specific hostmask from connection to a single IRC server. These lines should not be used in where a G:line can be issued. K:lines need to be removed manually.

6.6.3 Z:line permanently bans a specific IP from the servers. This can affect not just one user, but all ISPs that fall within the range of IP’s specified. Z:lines are discouraged and should not be used. Before setting a Z:line, mail the reasons for the Z:line to the opers as to why a Z:line will be placed.

6.7 Test Links. This is the process of linking a new server to WinChat.

6.7.1 Fill out a server application, which ia reviewed by routing for technical feasibility. (ping responses, connection speed, operator interest & ability).

6.7.2 If routing approves the application, it will be voted on by NetAdmins for a 30-day testlink. NetAdmins don’t have to give reasons for their votes in this. (Note: this vote is generally a rubber-stamp; only objecting NAs place votes.)

6.7.3 During the link, routing/security will check the stability of your server, and our staff will get to know the new server’s staff.

6.7.4 At the end of the 30-day test period, the NetAdmins will vote to accept your server to the Network. This vote usually takes five days. Negative votes at this point will include a reason, so that the new server operator can improve and try again.

6.7.5 A test-link server can have only one N-flag during the test-link period. Your staff may have local o:lines, but no co-admin or global opers until the applying server has been voted in.

7 Legal

7.1 Un-moderated: IRC is an un-moderated medium. We cannot be responsible for the actions of those connecting clients to our network, and, although we do try to maintain certain standards, we cannot be responsible for distasteful users or behaviors on the net.

a Children should be supervised when on IRC, and

b Users should NEVER accept files from someone they don’t know.

7.2 Embassy: All Servers connect to WinChat.Net are considered Embassies. Users connecting to a certain foreign server will be considered as bound by the laws of the country in which the server is located. All users connect to servers will honor the Customs and Laws of the country in which the server is located.

7.2.1 Example: a minor in the USA is under 18; but a minor in Turkey is under 15 years old. If you are connected to the Ist* server, then a minor is under 15, but on a *.USA server, a minor is under 18.

7.2.2 The NetAdmin of that server must be aware of the basic law of the server’s location’s country, in order to apply certain judgments based on local laws.

7.3 “Warez” is strictly prohibited: Any channel or user distributing, listing, allowing, directing towards, or processing “warez” (illegal software) will be removed from the WinChat network. Channel owners will be notified once to remove warez services before they are shutdown. If the channel owner does not comply within a reasonable amount of time, the channel will be shut down.

7.4 Pornography is strictly prohibited: All pornography (porn) is strictly prohibited on this network. No exceptions. Adult channels are allowed as long as these channels do not deal, distribute, recommend, list, direct, or allow distributions of porn. Any channels found to violate this will be shut down and removed immediately, no warning will be given.

7.5 Enforcement: Distribution of Warez/Porn must be witnessed by staff personnel. A log MUST be made by staff to show proof. If the owner/chanop blames a user for this distribution, then the owner/chanop must show proof that these actions were not incurred by him but a user. If the channel owner is aware of such distribution and does nothing to stop it, then the channel is also to blame and will be removed. [see abuse for the appeals process].

8 [a9] Respect

8.1 The following section represents a guideline of conduct, not necessarily a set of literal rules. This sets forth the basic principles for being a staff member of the WinChat network. All staff are expected to behave in accordance with these principles.

8.2 Respect one another. IRC is a free speech medium, but opers here are expected to treat users and fellow staff with sensitivity and understanding. (If you want to be rude, demote yourself to user.)

8.3 When you kill someone in disrespect, or out of anger, you are violating this principle. When you attack someone's view and eliminate it from the forum you are disrespecting that person. Everyone has a right to their view. When you curse someone out or attack what they said you are disrespecting them. Your right to free speech ends when you are hurtful to another Treating people like dirt is wrong.

8.4 If you have a disagreement, try thinking before acting. Don't hatemail, don't spread lies/talk behind backs, don't kill in a fashion that is not considered fun from both sides, don't excessively argue (your point can be made in one pass), and don't make others feel that they can't voice their opinion without having to defend their right to say something!

8.5 Respect is a two-way street, if we all give a little on both sides we can pass without collision.

8.6 Do not scold people when you see them violating these principles. Scolding only exacerbates the situation. Remember that we are basically equals. Keeping the flow and spirit of a channel, of a network is more important than the exact application of rules.

8.7 When you see a staff acting out in a way that violates this principle of respect, report that staff to their NA or Committee head. The NA (or head) is responsible for disciplining their staff. If the NA fails to act, then the NetAdmin may take action to discipline the NA, usually by suspension or removal of the server.

8.8 Be assured, if you are in repeated disregard of the respect principle, you will be removed.

8.9 The flow of a channel and a network is a delicate thing. “Let the river flow” whenever possible.

---

[ceh1]changed heading to tolerance. removed "stifle a situation"