DALnet Policies and Procedures

This document is the policies and procedures that define DALnet's organizational structure, operating procedures and service.

It is the goal of the DALnet IRC Network to provide a network to which people may connect for the purpose of chatting, an environment in which those people may feel safe and enjoy themselves and friendly staff available to assist. All clients connecting to DALnet must agree to refrain from using DALnet to engage in illegal activities, including the transfer of "warez" or "kiddie porn".

A. Channel Registration.

On DALnet, channels are registered by users. Unlike other networks, the current op-holder does NOT necessarily own the channel. DALnet has a service called ChanServ, with which a user can register a channel and assign ops and superops, as well as perform various other functions relating to channel security and management.

Prohibits illegal activities -- DALnet reserves the right to deny use of its nickname and channel registration services to users who are suspected of abusing those services or otherwise engaging in illegal activities.

B. Nickname Registration.

DALnet's users may register their nickname and decide whether they will allow anyone else to use it. If a nick is not used within the expiration time set by the Services Team, NickServ will expire its registration and the nick will be available to anyone who wishes to register it.

Please note the following restrictions:
1. Mass/Multiple nickname registrations.
2. Mass/Multiple channel registrations.
3. Flooding/spamming users via MemoServ.
4. Use of *!*@*.* in access/aop/sop lists.

C. IRC Operator Service.

DALnet's IRC Operators offer assistance with services and IRC questions, help managing problem behavior and maintaining network stability.

D. Help Services.

DALnet offers comprehensive Help Services. There are online help channels, many thorough FAQ files, web pages explaining DALnet's services and assistance is available via email which is answered by a team of volunteers.

A. Chief Executive Officer (CEO).

The Chief Executive Officer represents DALnet's foundation and provides the network's vision and direction. The CEO works in conjunction with the Executive Board and Server Admins to maintain the network and facilitate operations and enforcement of policy. The CEO may also appoint a Co-CEO.

A.1. Chief Operating Officer (COO).

A.2. Technical Director.

The Technical Director provides administrative oversight to the technical operations of the network. The TD works in conjunction with the CEO, AOB and technical Team Leads to ensure optimal technical resources and maintenance.

A.3. Human Resources Director.

The Human Resources Director coordinates staffing and communication resources, working with the teams, CEO and AOB to ensure organization and effective performance of DALnet staff.

B. Executive Board (EB).

The five-member (currently three) Executive Board is appointed at the discretion of the CEO. The AOB works in consultation with the CEO and Admins regarding new server applications and overall network operations. Executive Board decisions are passed by a majority vote.

C. Server Admins (Admins).

Admin responsibilities include:

1. Upkeep of the server's software and upgrade of the software to the current DALnet version within a reasonable time after the version's release.
2. Keeping the server's configuration updated and consistent with DALnet practices.
3. Keeping up-to-date on DALnet policies, procedures and activities.
4. Provide opinions and suggestions in the majority of CFOs.
5. Keeping DALnet administration as a whole informed of any prolonged absences.
6. Appointing a representative to fulfill his or her duties when necessary, and informing the DALnet administration as a whole of the appointment.
7. Informing the DALnet administration as a whole of any changes in a timely fashion.
8. All IRC Operator responsibilities.
9. Direct supervision and responsibility for their IRC Operators.

Admin rights include:

1. Appointing IRC Operators who can be trusted to act in the best interests of the server and of DALnet as a whole.
2. Upgrading the server's machine or link, providing the machine remains in the same location net-wise, or making other changes as necessary in keeping the server in the best possible working condition, where "best possible working condition" is defined at the discretion of the Admin.
3. Setting up one additional server to expand the capability of the site, even if this includes running additional processes on different machines, providing that the machines are of comparable capability and the server's location does not change.
4. Take whatever steps necessary to ensure a smooth transition during hardware or software upgrades or during an emergency situation.

1. Move the server netwise or physically to a location generally regarded as inferior, except as a temporary or emergency measure, as decided by the CEO.
2. Drastically alter the location of the server netwise or physically.
3. Link a server which has not been officially accepted by the DALnet administration. An exception can be made in the case of emergency, testing, or training situations with the approval of the CEO. These exceptions are not to last more than thirty days, after which time a review of the situation is required by the EB.

a. IRC Operators - Server Team Staff (IRCops).

A DALnet IRC Operator assists the Admin in server maintenance as assigned and helps maintain network stability. IRCops assist users in becoming oriented to the DALnet network, DALnet Services and in the mediation of disputes. IRCops offer assistance in resolving conflict and work with other administrative staff to maintain a safe environment.

D. Specialized Teams.

The following teams have been empowered by DALnet's Executive Board to function within the scope of their team policies and procedures as presented to the EB.

DALnet's CEO and Executive Board provide general administrative support to the network and it's staff. Team Leaders, as appointed by dalvenjah in consultation with the EB, have the authority to make policy and staffing decisions regarding the team and it's operations. Complaints about a team, it's policies or it's staff, may be submitted to JAG for review. Only in an Emergency Situation as defined in Section II. B. will a member of the AOB or the CEO overrule the decision or policy of a Team Leader.

1. Help Services (Help Committee).
2. Hostmaster
3. ircd Coding Team.
4. Postmaster
5. Kline Team.
6. Web Team.
7. Routing Team.
8. Services (Services root staff).
9. Training Team.

A. Server Links.

1. Linking New Servers To DALnet.

a) A completed server application will be sent to apply@dal.net; this application is available from http://www.dal.net/vote/server-app.txt

b) After the application is processed, it will be posted to the main DALnet mailing list, dalnet@dal.net, and any other list(s) as required. This will start the CFD (Call For Discussion) process, which will last no more than 5 days after the application has been posted. ALL discussion must take place on the main list, except when portions have the potential to compromise the security of any DALnet server.

c) During the CFD period, DALnet staff should make every effort to look the application over carefully in order to help the Executive Board make the most informed decision possible.

After the CFD period, there will be a 2 day CFO (Call For Opinions) period. During this time, admins will vote in their opinion of whether the server under consideration should be linked or not. This time limit will be strictly enforced.

Also during this 2 day period, Routing should state which hub uplinks would be the best for the proposed server. The Executive Board will not vote until this is done, and it must be done within the 2 day period.

d) The Executive Board will vote on the application within a maximum of 2 days, and the results will be posted to the main DALnet mailing list and any other list(s) as required.

e) After the results are announced, comments are welcome from admins (as well as IRCops and users) as to what they think about the decision, the reasons the members of the Executive Board gave for their decision, and any particular voting pattern by members of the Executive Board that they see.

f) If a Yes vote is reached, current hub admins should get together with the new admin and exchange C/N/H line information. Servers which receive a No vote may re-apply in 3 months, and must go through the full application process once more. There will be only one re-application per server/admin/co-admin allowed.

2. Additional Links.

Additional servers (beyond one extra) may be added to expand the capability of the site with the approval of the EB, routing team, or CEO.

3. Emergency Links.

The Routing Director, CEO or a member of the Executive Board may link a server on an emergency temporary basis for a period of 30 days during which time a server application will be submitted and approved or the server delinked.

4. De-linking a DALnet server.

A server may be delinked by a majority vote of the Executive Board.

If the Executive Board votes in favor of delinking, all DALnet servers shall remove C/N lines within 7 days. If the Executive Board votes against the removal of the server the following will happen:

1. Any actions stated in the vote are to be put into effect immediately.
2. The server should then have a probationary period of 60 days from the closing of the vote, or from the time it re-links to the network.
3. At the end of the probationary period, another vote can be requested if another Admin feels the server/Admin did not fulfill the duties necessary of a DALnet server and Admin.

A server may be temporarily delinked (juped) if it shows considerable disruption to the rest of the network, such as failure to update the ircd files in a timely manner. This action should be no longer than 5 days. Otherwise, it qualifies for delink.

B. Emergency Situations.

An 'emergency situation' exists as declared by the CEO, or as agreed upon by a minimum of four members of the Executive Board. A brief statement describing the nature of the emergency, plan for its resolution and approximate termination date will be posted by the CEO or AOB on the Admins' mailing list within 24 hours of declaring the emergency exists.

A vote may be called to approve emergency measures if those measures are outside the rights granted to an Admin and have been in place for more than two weeks. A vote MUST be called prior to relink if a server remains down for longer than 45 days or has been delinked by a vote.

'Emergency measures' may be taken by an Admin if the measures are approved by the CEO or the Executive Board. Emergency measures may remain in place for the period of one month without a vote.

All changes of network configuration (C/Ns and autoconnects) are subject to the approval of the Routing Director, in conjunction with the Routing Team, and that any changes under consideration or placed into emergency action should be sent immediately to routing@dal.net.

DALnet servers will run the version of ircd approved by the Technical Director. The latest version can be found at:

http://www.bahamut.net.

Minimum requirements for DALnet servers are determined by the Routing Team and enforced in conjunction with the Executive Board, Technical Director and CEO.

Policy decisions include, but are not limited to, making changes to the charter, adding/removing servers or voting to bring action against an Admin or IRC Operator. Voting procedure:

1. A vote is called by the network CEO or designee.
2. A discussion is conducted and opinions are posted by the Admins.
3. Within 4 days, an Admin of each server, in consultation with the IRC Operators, will submit an opinion to cfv@dal.net during the Call For Opinion phase of the decision-making process.
4. The AOB reviews the opinions and submits a final vote within 48 hours to cfv@dal.net. The vote will pass with a majority of four Executive Board member votes. In the event of a tie, the CEO may cast the tiebreaking vote.

DALnet's CEO retains the right to veto decisions of the Executive Board. During the meeting of the EB, the CEO must ask that the issue be tabled for review at a later meeting, or the CEO must veto the Board's decision before the meeting is adjourned. When the CEO wishes to veto a decision the AOB made at a meeting the CEO did not attend, the CEO must inform AOB members of the veto via email within 24 hours of receiving a copy of the Executive Board's Meeting Minutes.

A. The procedure for registering a complaint about an IRC Operator or Admin is:

1. Try to resolve the problem by talking to the IRC Operator or Admin directly.
2. If there is still a problem, report it to the Admin on whose server he or she has an O: line. In the case of an Operator with more than one O: line, try to report to the Admin of the server the Operator was oper'd on at the time of the event, if possible.
3. If the problem remains unresolved after the Admin has investigated and made a decision, a report can be sent to the AOB with supporting documentation.

B. DALnet staff will not: Use profanity, exhibit sexual behavior in public while 'on duty', impose unwanted sexual behavior toward others, harrass staff or users, exhibit stalking behavior, abuse services, abuse oper commands, be disrespectful toward staff or users, neglect responsibility toward the server or damage property.

It will be assumed that an oper is 'On Duty' when at least one of the following conditions exists. The oper is:

1. +O
2. @ when doing so as a representative of DALnet staff
3. participating in the mediation of a dispute
4. monitoring user or channel situations, incognito or not
5. attending DALnet staff meetings
6. posting email on DALnet mailing lists
7. acting as a representative of DALnet

C. Possible consequences: Consequences for misbehavior by an IRCop are decided by the Admin alone or in conjunction with the CEO and/or EB. Consequences will be proportional and relevant to the offense and may include:

1. Demotion to a local o: for a probationary period.
2. Personal and public apology.
3. Replacing or reconstructing damaged records.
4. Removal of channel AOPs; temporarily or permanently for repeated misuse.
5. Removal of the O: line.
6. Removal of Services Admin or CSOP access.
7. Mailing list moderation.
8. Refusal of future O: line opportunities.