Charter
From DareNET Wiki
|
| This article has been replaced by smaller policy documents, contained here. |
 | This page has been marked as Historical. Information posted here may be inaccurate and out of date. This information is kept for sentimental and/or historical reference purposes. |
Contents |
Introduction
The Charter acts as a repository of the rules and procedures for the network. Established within are the rights and responsibilities of the users and network staff, as well as policies that are to be followed by both.
Purpose
DareNET is an online community which has been built around an IRC network. We are dedicated to providing a safe, fun and friendly environment in which to communicate. We value stability over popularity, and will not compromise on quality of staff or servers in the vain effort to bloat our server count or attract more users. We have also adopted a laissez-faire policy towards channel management, allowing channel owners to have a free hand in running their channels.
Disclaimer
DareNET's administration does not log or monitor any traffic that may pass through its servers for content or clarity. By retaining a connection to any part of DareNET, you state that you know and are willing to comply and accept these, as well as any future terms of service, network policies and user guidelines.
No responsibility for computer damage, data loss, or any other related damage shall be implied by any DareNET server administrator, operator or agent. By using any DareNET server, you hereby state and agree that you release DareNET, its servers, administrators, operators, agents and any other volunteer of DareNET from any and all responsibility or legal liability which might result from your use of DareNET servers.
DareNET administrators and operators reserve the right to deny access to and use of the DareNET IRC network or any of its other resources, including, but not limited to, IRC services, mailing lists, discussion forums, directories and FTP sites, to any user, group, site or domain without the benefit of prior warning or notification if necessary.
Please remember that you are a guest on the network at all times, and you are expected to conduct yourself accordingly.
The failure of DareNET to excercise or enforce any right or provision of this document shall not constitute a waiver of such right or provision.
Acceptable Use Policy (AUP)
The following rules should be observed at all times while connected to the IRC network:
- No network/server/channel ban evasions.
- No faked or altered user@host information.
- No loading of malicious bots onto the network.
- No creating excessive connections (clones) from your connection.
- No flooding of any kind.
- No engaging in denial of service attacks on users or network infrastructure.
- You may only advertise in channels where you are on the userlist or with the channel owner's permission. Directly advertising to DareNET users (e.g. mass-advertising/inviting) is prohibited.
These rules are in addition to the usage agreement with the user's ISP and with any local laws, statues, rules and regulations pertaining to (1) the user's use of any DareNET service, (2) the communications means by which the user connects their terminal, personal computer or other device to DareNET services or to services provided to and by DareNET, and (3) the local DareNET server the user connects to as stated or referenced in its Message of the Day (/MOTD).
DareNET network staff will interpret this AUP if there is any ambiguity as to how it applies to your situation.
Consequences for Violation
If you violate any rule or regulation stated within this document or in the message of the day (MOTD) of the DareNET server you're connected to, you will be subject to progressive disciplinary action, including, but not limited to, loss of services privileges, denial of access to any DareNET server or the entire network, or legal action where applicable. Denial of access to a particular DareNET server can be made at the server administrator's discretion. Your Internet provider may be denied access to the server or network if you successfully evade a ban.
DareNET is under no circumstances to be used for illegal activities. Observed and verifiable instances may be reported to the appropriate authorities. And, although DareNET itself is an unmoderated forum, DareNET's administration will cooperate fully with any officially recognized law enforcement agency to the best of its capability when required to do so by law.
Appealing a Violation
If you are banned or denied access to a DareNET server, service or the entire network, you should follow the procedure outlined below. However, please note, that DareNET's server administrators are under no obligation to take any further action if you are denied access.
- If you are K-lined (banned from a specific server), contact the server admin (such contact information can be found our server listing page) and request the removal of the ban, explaining how future incidents can be avoided.
- If you are G-lined (banned from the entire network), or would like to appeal some other corrective action (e.g. suspended account/channel), please contact our Abuse Team by e-mailing abuse@darenet.org for further assistance.
Network Governance
DareNET's network staff are responsible for the vast majority of the network's day-to-day operations. This includes answering user queries and requests, maintaining their servers (and network as a whole), and, if necessary, acting in response to any threats to the network or violations of the network's AUP.
Specific duties and tasks are delegated to established teams, which are comprised of various staff members. All staff members are encouraged to participate in any such entities for which they are eligible.
The downside to all of this is that there really is very little "power" for a new administrator or operator. But people should decide what they are good at and volunteer for the relevant teams, then they can work their way up. Theoretically, the Executive Board should notice people who are working hard and put them in positions of authority.
Network Staff
There are presently two different classifications of staff here on DareNET, which are:
IRC Operator staff.
These are the individuals who hold an O-line on a server linked to the network.
Support staff.
These highly dedicated individuals are the first contact for many users support related needs, and as such are heavily relied upon. They may or may not hold an O-line on the network.
Conduct
All members of network staff are expected to conduct themselves in a civil, professional manner at all times. Network staff are also expected and required to act in accordance with the rules mentioned above as well as the following:
- All staff members must register their primary nickname to their NickServ account.
- All staff members should not use *@* as an allowed mask for their NickServ account.
- All staff members must be subscribed to the appropriate mailing lists, and keep up-to-date on issues discussed on these lists.
- Staff members will NOT interfere in channel matters, unless it is absolutely necessary to do so in order to ensure network rules and policies are enforced.
- Staff members must not use their position or authority to intimidate, threaten or harass users.
- Staff members are only permitted to use staff commands, usermodes, and services access for the enforcement of network rules, to aide network users or as required for maintenance of the network's servers.
- Your access limitations are set by network management, not what you or users think it is set at.
Chain of Command
The chain of command is laid out as follows:
- Executive Board
- Server Administrator | Team Leader
- IRC Operator
- Support Operator
- Support Agent
You are required to respect the judgement and authority of the people above you in this chain.
Server Administrators
Server administrators are those individuals who have been granted a permlink to DareNET, and as such have a few additional rights and responsibilities.
Admins responsibilities include:
- Direct supervision and responsibility for their IRC operators.
- Upkeep of their server's software. This includes upgrading to the current DareNET version within a reasonable time after the version's release.
- Keeping their server's configuration updated and consistent with DareNET's current practices.
- Provide opinions and suggestions in the majority of CFDs open to Admins.
- Vote in ALL CFVs open to Admins.
- Appointing a server representative to fullfill their duties when absent, and informing the admins list of the appointment. NOTE: This is not the same as a Co-Admin, which DareNET does not recognize.
Admins rights include:
- Appointing IRC operators who can be trusted to act in the best interest of the server and of the network as a whole, provided current policies regarding staff additions are followed.
- 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 best possible working condition, where "best possible working condition" is defined at the discretion of the Admin.
- Take whatever steps necessary to ensure a smooth transition during hardware or software upgrades or during an emergency.
Admins will not:
- Drastically alter the location of the server net-wise or physically.
- Link a server which has not been officially accepted through an Admin vote or by the Routing Team.
Complaints and Misconduct
Should a user or staff member observe a member of staff acting in a manner contradictory to the network rules or the network's best interests, a complaint may be submitted to the Abuse Team. If the Abuse Team determines that a complaint is justified, it will be referred to the competent authority for disposition. Upon receipt of complaint, the Abuse Team may also take temporary action against the staff member in question if they feel it is necessary to prevent harm to the network. Such temporary action will be rescinded once a decision is reached by the competent authority.
In the rare event a staff member is observed to be acting in a manner detrimental to the network and their actions warrant immediate action, any member of staff with equal or higher access may take any corrective actions deemed necessary, including revocation of access and remove from the network. Staff members with lesser access are encouraged to approach a staff member with higher access if necessary.
All actions of this type must be immediately reported to the Excutive Board who will discuss the action and its suitability. Should the Executive Board determine the action was unwarranted, they may take disciplinary action against the instigating staff member.
New Operators
New IRC operators may be brought onto the network in two manners: appointment from a current server administrator, or as part of a newly linked server.
Before appointing a user as a new IRC operator, the need for new staff must be identified by the Server Administrators, as a whole. Once this need is shown, the admin may then add the individual's O-line, provided they have not reached their server's oper limit (see below). It is the admin's responsibility to ensure their new oper is given proper access to channels, mailing lists, website, webmail account, etc.
When applying to link a server, the prospective server administrator may choose a maximum of three (3) operators, including themselves. These individuals must be named on the link application. Acceptance of the link application and linking of a server does not automatically allow for a new IRC operator.
Executive Board
The Executive Board was created to seat those individuals who put more time and energy into the network than most. They are charged with overseeing the operational responsibilites and affairs of DareNET. They also ensure that the values and vision held at the founding of the network continue to be followed. As such, they are the network's main governing body, and have the last word on all aspects of network management.
Executive Board members are expected conduct themselves in a rational, reasonable manner and posses diplomacy and communication skills. Technical aptitude or skill set is not a requirement, though may prove to be useful.
The Executive Board exists as effective team leaders for the Admins. While each team leader is free to run their team's associated mailing lists as they see fit, the Executive Board expects admins to conduct themselves professionally on the admin list. That means admins are expected to compose legible, non-abusive e-mails without excessive quoting. Failure to comply with this reasonable request will tead to the Executive Board requesting the admin appoint a more polite individual to respresent the server on the admins list.
Now, after hearing this, some people will scream "Executive Boards are fascist! Give all admins equal control, let everyone contribute!". Well, it is not our intention to prevent our admins, or any staff member for that matter, from contributing. We welcome all staff members to go beyond the call of duty, for which they will indeed be rewarded. We believe that to be more realistic and fair as opposed to a network which talks about equality and then tolerates some individuals who do nothing and others who do all the work, yet give equal status to all.
Abuse Team
The Abuse Team was established as a mediator between users and the network staff with the overall outcome of a peaceful resolution to queries raised with the Abuse Team.
It is the Abuse Team's aim to mediate between you, the user, and the network staff in occurrences such as incorrect K/G-Lines and KILLs which you want to pursue with the best possible peaceful and worthwhile outcome. The Team also deals with disputes regarding K/G-Lines and the addition / maintenance of Connection Limit Increase (trusts) requests.
Team Lead
The Abuse Team shall be headed by an individual appointed by the Executive Board. This individual shall be responsible for ensuring the team is staffed with competent individuals, and that all tasks and duties are completed in a timely and efficient manner.
Team Membership
Abuse Team members are appointed by the team lead. Contact the team lead for additional details.
Current Lead: NiTeMaRe
Routing Team
The Routing Team operates under the cognizance of the Executive Board. It is directly responsible for reviewing, qualifying and effecting links, delinks and server link applications to DareNET. As such, the team shall is charged with handling and reviewing new link applications and monitoring the performance of all servers linked to DareNET according to published policies and procedures.
Team Lead
The Routing Team shall be headed by an individual appointed by the Excutive Board. This individual shall be responsible for ensuring the team is staffed with competent individuals, and meets its objectives.
Team Membership
Routing Team members are charged with reviewing applications for new servers and voting to grant or decline new testlinks, reviewing existing servers for performance on the active network, and coordinating routing issues as required.
Members are appointed by the team lead, as the need arises. Those interested in joining should contact the team lead.
Current Lead: blahx
Support Team
The Support Team is responsible for assisting users with matters pertaining to DareNET and IRC in general. This includes providing helpful documentation, helping users who join #support, answering e-mail queries, replying in the support forum, etc.
Team Lead
The Support Team shall be headed by an individual appointed by the Executive Board. This individual shall be responsible for the organization and operation of DareNET's end-user support.
Team Membership
Support Team members are appointed by the team lead. Contact the team lead for additional details.
Current Lead: Sparkle
Web Team
The Web Team is responsible for maintaining and developing DareNET's web properties.
Team Lead
The Web Team shall be headed by an individual appointed by the Excutive Board. This individual shall be responsible for ensuring the team is staffed with competent individuals, and that all tasks and duties are completed in a timely and efficient manner.
Team Membership
Web Team members are appointed by the team lead. Contact the team lead for additional details.
Current Lead: SecretAgent
Network Servers
Network servers shall be maintained by their administrators and respective operators in conjunction with the Routing Team, and in accordance with policies established by the Routing Team.
Link Requirements
A complete list of hardware, bandwidth, and software-related requirements for network servers can be seen here.
Link Applications
Prospective server administrators interested in linking their server must file a link application, which can be found at http://www.darenet.org/linkapp. Upon receipt of a link application, the Routing Team will discuss the application for one week to determine the suitability of the prospective server. After discussion, voting will be held for 48 hours. A simple majority vote of the Routing Team is necessary to approve the application for a test link.
Test Link
The test link phase lasts for four weeks unless earlier terminated by the Routing Team. During this time, the new server will be linked to the network. For the first week, the server will not be added to the primary host records for client access. For the second two weeks, the server will be set up for client access. The performance of the new server will be monitored, especially pertaining to network connectivity and handling of user load.
During the last week of the test link phase, the Routing Team will discuss the link. At the end of the phase, the Routing Team will submit their notes to the Admins list for further review. The Admins will then have 48 hours to vote on whether to grant the server a permanent link, delink the server or extend the test link period for two weeks, after which they will vote again. A simple majority is required to approve any option.
IRC Operator Limits
Each server shall be limited to three (3) primary operator blocks: The server admin, and two (2) operators. An admin may appeal to the Executive Board to allow for additional primary operator blocks, with their decision being final.
NOTE: DareNET does not recognize Co-Admins / Assistant Admins.
Server Naming Convention
All servers linked to DareNET are expected to follow our standard naming convention. For more details and information, please read over our Server Naming Guidelines.
Network Channels
DareNET currently operates three (3) official network channels, which are as follows:
#DareNET
This is our virtual lobby. Anyone is welcomed to join and participate in the fun. Discussion ranges from the technical to the trivial.
#Support
This is DareNET's primary help channel, and is monitored by staff. Users can obtain help with all things DareNET, and general IRC assistance. Additionally, this also where channel registrations are requested.
NOTE: Idling is not permitted in this channel. Additionally, upon entering #support, you should tell HelpServ a short description of your problem. This is important because it enables the staff member to gather the appropriate information before needing to talk to you for further information.
For example:
/msg HelpServ I forgot my password and tried using RESETPASS, but I'm not receiving the e-mail. My account name is JoeUser.
#Routing
This channel is maintained by the Routing Team, and is where individuals can obtain assistance with link applications, or other technical issues relating to DareNET.
Changes to this Document
This document is to be maintained by the Executive Board. Any network staff member may propose changes to this document to the Executive Board, who will then discuss the changes and hold a vote on whether to make the changes as is, in a revised form, or not at all.
