DynastyNet: Policies and Guidelines

The DynastyNet Policy
Section 1
Board/Committee

1.  An Executive Board consisting of DynastyNet Admin, Server Admin, Server Co-Admin, and coders will be formed. New members 
will be added to the Eboard via links after a set time period to be determined by the Eboard in their by-laws, at the time 
the committee was formed.

1b.  Eboard members shall also have exclusively the position of Services Admin. Service Admin will be voted in by Eboard, 
and may also be removed by Eboard vote.

1c.  The position of Services Operator may be granted to any Global Operator upon a nomination by the Oper Committee and the 
passage of a majority vote of the Eboard.

1d.  Eboard will write and control amendments and additions to the Policies/Guidelines and its own By-Laws by a majority 
vote of Eboard members. Normal voting rules and regulations in effect as governed by the Eboard By-Laws.

2.  An Oper Committee of 5 will  be formed, to oversee all operators.  Consisting of Chair and Co-Chair, of which one must 
be an Eboard member, and one at least a global operator. Oper committee meetings will be open to all opers to attend for 
observation. The committee will form its own by-laws, subject to Eboard approval. OperCom may at their discretion, add more 
members, of which must be global operators.

2a.  Any oper that places an akill or gline longer than 6 hours will fill out the DynastyNet Akill-Gline Report form on the 
src.dynastnet.net website. OperCom will review the report and ask for logs if necessary. OperCom will handle all akill/gline 
complaints, and any removal/modification of such akill/gline deemed necessary. Any complaint against a placed akill/gline 
will be sent to opercom@dynastynet.net for 
consideration, any complaint received will be forwarded to the oper who placed the akill/gline. 

3.  A Help Committee of 5 will be formed, to oversee the help rooms. Consisting of Chair and Co-Chair, of which one must be 
an Eboard member, and one at least a global operator, and 3 helpers which may be users. The committee will form its own 
by-laws, subject to Eboard approval. HelpCom may at their discretion, add more members, of which may be users.

4.  A Server committee will be formed, to oversee all servers. The committee will keep the login/pass to all participating 
servers, for maintenance purposes. The committee will maintain their own by-laws subject to Eboard approval. The committee 
will consist of a Chair and Co-Chair who are members of Eboard, additional members will be chosen, due to their 
qualifications, and voted in by the committee, the amount to be determined by the committee's by-laws.
 
4a.  Server Committee will be responsible for all link applications, a copy of which to be sent to 
servercom@dynastynet.net. ServerCom will ask for, 
and obtain root authorization, from the shell owner, to their satisfaction, before following through on the application, in 
which ServerCom will set up their own guidelines for approval. If root authorization is not obtained, the application will 
be dismissed. Voting on completed applications and permanent linking status will be sent to Eboard for voting, with a 
recommendation from the Server Committee.

4b.  Any delinking procedure set forth by ServerCom will be sent to Eboard for final vote with a recommendation from the 
Server Committee.
     
Section 2
Servers/Opers

1.  Servers wishing to link to DynastyNet should talk to a member of ServerCom online. Applications for linking are 
subject to approval of all necessary forms required. Completed applications will be reviewed by ServerCom, and will be 
submitted for vote upon approval. Falsification of any information will result in the immediate dismissal of the 
application. After a dismissal, a new application will be reviewed after a 15 day waiting period.

2.  New links will have a 30-day probationary period. During the 30-day probation period, no operator can vote or apply to 
the Eboard. After the 30-day period ServerCom will recommend to Eboard to accept or deny the server as a permanent link, or 
extend the probationary period of the server to a time recommended by ServerCom.

3.  New servers linking are limited to Admin and Co-Admin as global operators.  After a server has been approved for a 
permanent link, the admin may request permission from OperCom to add one or more local opers.

3a.  The Admin and Co-Admin must meet with OperCom, prior to linking their server to DynastyNet, for an admin evaluation and 
a policy briefing so that they may be acquainted with DynastyNet's policies and rules. After this evaluation and briefing 
OperCom will inform the Admin and Co-admin of any further training required based on past experience and general knowledge 
shown during the evaluation. The Admin and Co-Admin shall setup a time with OperCom to take the oper test. If the Admin 
and/or Co-Admin does not pass the test OperCom reserves the right to reduce their oline status to that of local oper until 
such time as they successfully pass the test.

3b.  New opers that OperCom has approved shall be added to the server as local opers until such time as they complete oper 
training and pass the oper test. OperCom shall furnish the new oper an application, which shall be filled out, and returned 
to OperCom within 24 hours. OperCom will then set up times for the oper to take the required classes. The new opers shall 
not be granted a global oline until such time as they have passed the oper test that all opers on DynastyNet are required to 
pass to obtain global status.
 
3c.  Any current DynastyNet global oper or admin that links a server to DynastyNet will not be subject to the OperCom tests, 
and as the admin or co-admin of the server, the current oper/admin may be eligible for Eboard application status without the 
30 day waiting period.

4.  All local opers, on a new server, or added at a later date on an existing server will test after no less than a 30 day 
waiting period and attend classes required by OperCom. Local opers will have 30 days to schedule their test date after 
classes are completed. If not done within 30 days, opers will be required to schedule a retake of the classes, in which both 
the classes and the testing must be completed within 30 days. If this requirement is not completed the oper will remain a 
permanent local oper, pending Server Admins decision. After the test is passed it will go to vote. If an oper fails the test 
they will be required to retake the classes and retest within 30 days, providing their admin keeps them on. A third test 
will be denied. New Admin/Co-Admin will retest in 2 weeks. The Oper Committee will do all testing, and then sent to vote 
from all global/admin operators, no global/admin operator on a test server will have a vote.

5.  All  opers, on a new server, or on an existing server, who have been off-line for a period of more than 7 days, without 
prior notification to OperCom, are subject to immediate removal, pending a full review after returning, subject to the 
Admins request to reinstate such oper. Non working opers idling 24/7 who are consistently unavailable shall also be subject 
to immediate removal. The oper may request a review and re-addition subject to the Admins request to reinstate such oper.

6.  The server admin will notify OperCom immediately by email of any o:line removal. If the admin wishes to add a new oper 
they shall contact OperCom and request permission to add a new oper to their server.  OperCom approval is required before an 
admin may add a new oper. Once OperCom has approved the oline addition, OperCom will supply the new oper with an application 
that the oper must fill out and return to OperCom.

7.  If the owner of a server is absent and the need arises for an Admin or Co-admin or both to be replaced/appointed to a 
server, Eboard reserves the right to interview qualified opers for the position and make a decision on who to appoint. At 
which time OperCom shall upgrade the opers training to include the admin duties and ServerCom shall provide the new admin 
with all necessary passwords and information. Upon the return of the owner of the server, he may replace anyone he feels 
necessary with his own choice and, provided they are eligible, OperCom shall upgrade their training to include the admin 
duties. It shall be understood by the Admin and/or Co-admin that are appointed by Eboard that this is a temporary term that 
may be revoked at any time by either Eboard and/or the owner of the server. At such time that it is revoked they shall turn 
over all passwords and necessary information to Eboard and/or the owner.