DynastyNet: Policies and Guidelines

The DynastyNet Guidelines
version 1.2.7
written by: Dave Morey <dave> 
approved by: The DynastyNet Eboard

Section I - Introduction
    The DynastyNet IRC Network was established in the far-fetched idea of creating a sound environment, free from the 
vulgarities and rudeness of other nets, for people to come and chat. In the interests of furthering this idea, it becomes 
necessary for other IRC servers to join us in our quest for the unreal. We have as few 'rules' as possible, but they are a 
necessary part of keeping the IRC network running and operating smoothly. Our key is freedom of speech, we believe in it, 
and allow it. However, there has always been a controversy over what exactly is allowed and what isn't. I hope to clarify it 
here. Freedom of speech is limited when the speech is threatening or otherwise unwanted comments, such as slander or 
harassment. We will not allow the degrading of other users or the network. Having covered that topic, time to get down to 
business.

--------------------------------------------------------------------------------

Section II - Users Guidelines
    Users of DynastyNet are entitled to a chatting environment free from the vulgarities and rudeness found on much of the 
other IRC networks. We strive to provide an environment absent of pornographic material, as well as illegal/pirated software 
commonly referred to as warez, but not excluding mp3's. Users that are found distributing such material will quickly have 
their privilege of using the DynastyNet IRC Network revoked by means of kill, kline or akill. You are entitled to just as 
much leeway and freedom as the IRCops, but also have the same limitations. If you have a question, don't be afraid to ask. 
Operators are there to help. 

--------------------------------------------------------------------------------

Section III - Basic Rules and Operating Procedures

    A few keynotes on some issues that get covered just about every day:

IRCop Requests: 

    Currently the only way we accept new IRCops are through new links, or by a user proving that he/she is worthy of 
becoming one. When a user is considered to be an IRCop, he/she must first complete 4 of the Oper Skool classes, complete a 
30-day probationary period as a local oper, and pass an IRCop test, given by our Oper Committee. 

Server Link Requests: 

    The Administrator of the Server requesting a link is sent a Server Application form, which gives us an idea about the 
statistics, connection speed, etc. After receiving the Server App via email or DCC Send, The Board will review the 
application at their next meeting and decide there. An answer then is emailed to the Admin. 

User Complaints: 

    Basically, we need logs. If it is a channel dispute, or something that is more of an owner problem, they handle it. If 
it involves a member of the DynastyNet Staff, it will be handled in the same fashion as any other complaint. It is not our 
responsibility to maintain every single channel on DynastyNet. If the owner is unavailable or is perhaps involved in the 
dispute, then it becomes an issue. Do NOT base your decisions on personal matters. When you log on as an IRCop, you become a 
representative of DynastyNet. If users see IRCops 'taking sides' just because one of the people involved is your buddy, they 
don't sit back and take it. So be discrete, but judgemental and fair at the same time. 

Abuse: 

    In the event of the misuse of the network's services and/or functions by any DynastyNet staff member, proper action will 
be taken toward the offender.

--------------------------------------------------------------------------------

Section IV - Server Administrator Guidelines
    When you link to DynastyNet, you take on not only the responsibility of your own actions, but that of the people you 
have entrusted with IRCop status. Not only is your staff a representative of your server, but of you as well. IRCop status 
is not to be taken lightly. It is a major position, and care is taken in deciding who receives the honor of becoming one. 
This is not KiddieNet, nor will DynastyNet tolerate IRCops who insist on behaving as if it were KiddieNet. DynastyNet is a 
professional network, and the people involved in the workings of it are expected to be just as professional. All Admins are 
expected to follow the same guidelines that are expressed in the next section. 

--------------------------------------------------------------------------------

Section V - IRCop Guidelines
    Welcome IRCops of the DynastyNet IRC Network. Your title is a highly recognized and often crazed after position. DO NOT 
TAKE IT LIGHTLY! IRCops are the judge, jurors, and sometimes the executioners of IRC. Users respect you, believe it or not, 
and look up to you. Which is why it is so important that you act as responsibly and professionally as allowed. There are a 
few rules/guidelines that you must adhere to, they are as follows:

    Abuse of services will not be tolerated. Abusing such services to gain channel operator status in a channel you have no 
right being an operator in, is one of the major causes of o:line loss. For one thing, it intrudes on the channel atmosphere. 
Do NOT use ANY services to better yourself over something that is not a network issue. As was said above, if it is a channel 
Issue, we do not get involved. Only when it becomes a network issue do we get involved, i.e. pertains to more than one 
channel at a time, or puts other users of this Network at risk.

    Killing other IRCops or administrators is another reason for o:line loss, this one more serious than opping yourself in 
a user channel. We do not turn our killing power on each other. It is a childish way out of an argument or situation that 
can be handled other ways. We cannot stress /ignore or /silence enough. USE THOSE FIRST! If it becomes a major problem, talk 
to your Administrator or Co-Administrator. If the problem is your Administrator, talk to a Network Administrator. There is 
always someone above someone else. When an akill is issued for longer than the default 6 hours, an email should be sent to 
opercom@dynastynet.net 
with any logs explaining the circumstances. 

    When you do issue a kill, there is a mandatory kill message that is to explain each kill. They shall be free of vulgar 
or otherwise unnecessary language. We want to keep our users, and when they see another user get killed, or even themselves, 
with obscene, vulgar language, they tend to place in their mind a picture of the network. And it isn't a pretty one. You 
will be notified if a kill message is too risqué. Trust me. ;)

    Professionalism is the key here. When the network looks bad, we all look bad. But when we look good, the network shines. 
Now granted we don't go around using big words or proper sentence structure, that isn't what we mean. Your actions are what 
makes or breaks us. If it breaks us, heh, we break you. ;P

    There are a couple of channels that are the 'main' gatherings. Each server will probably have its own IRCop/Admin 
channel, but the network channels are:

#Dynasty - Main hangout of IRCops/Admins. NOT a help channel.

#Dynasty_Help - Main Help Channel. Again, channel operator status must be earned.

--------------------------------------------------------------------------------

Section VI - Service Operator Guidelines
    Service Operators are an important part of the Network. Its position is above IRCop status, and with it comes more 
responsibility and duties. You are capable of retrieving lost passwords and go through most channel modes. For each added 
capability, the severity of the punishment also increases. Abuse in this level is very illicit. Professionalism is called to 
a higher level. Abuse shall be handled promptly and without sanction, until a hearing can be held.

--------------------------------------------------------------------------------

Section VII - Service Administrator Guidelines
    Service Administrator is the highest level on the DynastyNet IRC Network and is the most called upon position. People in 
this position are constantly queried, messaged, in other words, flat-out swamped. This position handles much of what goes on 
behind the scenes: Link application review, IRCop examinations, and other such duties. Which is why conflicts between 
Service Administrators and opers/ssers must be settled quickly. Do not take matters into your own hands, consult other 
Service Admins and ask their opinions and try and get these issues resolved as quickly and as easily as possible. Abuse in 
this stage is at the highest level of concern. It will not be tolerated, and will be dealt with accordingly and swiftly. We 
are not above the law, and we will conform to and abide by the laws and rules stated above.