Policy
From Blitzed
Contents
|
[edit] Why Blitzed Is Not A Total Democracy
Blitzed was initially formed by two experienced IRC administrators. These admins and their servers had previously been linked to two small networks, and had taken issue with the administration of both networks. The admins concerned left because they didn't have as much influence over the networks as they would have liked. Hence, the things they felt needed to be done, were never dealt with properly. This led to the delinking of their servers from both networks.
Talk about forming a new network with a more constructive administration had been brought up, but everyone assumed it would be totally democratic with each admin having equal say in how the network was run; however, this simply isn't realistic. Not all admins are as interested in the network as others. Those who work hard and contribute should be put in positions of responsibility and rewarded for their efforts. This implies a higher level of control and power above that of the admins, and after much consideration we believe that to be the most effective way to run a network.
The Executive Board was created to seat those admins who put more time and energy into the network than most, but after hearing this, people have said "Executive Boards are fascist! Give all admins equal control, let everyone contribute!". Well, it is not our intention to prevent our admins from contributing. We welcome admins 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 admins who do nothing and others who do all the work, yet give equal status to all.
[edit] Overall Philosophy
We have founded the Blitzed IRC Network in order to provide a place where people can chat and have fun in a stable environment.
We aim to provide stand alone channel and nick management services giving users a free hand in running their own chat rooms.
We value stability above popularity, and we will not compromise on quality of staff or servers just to attract more users.
We have few network rules, those we do have are based on common sense.
We demand a lot from our staff, in the hope our staff can be proud of their collective achievement.
[edit] Government Of The Network
Blitzed will be governed day to day by a number of teams: Admins, Exploits, Help, IRCd, Services, Systems, and Web. The overall power on Blitzed is the Executive Board. The Staff List page contains an up-to-date list of the Executive Board members and each team.
The Executive Board will appoint team leaders for each of these teams. The team leaders will report to the Executive Board, with the exception of the Admin Team. All members of the EB will be subscribed to the admin list and mostly communicate with the admins (the EB are team leaders for the Admin Team).
Almost all policy issues will be dealt with by the Admin Team, by admin vote if necessary.
[edit] The Blitzed Teams
Blitzed staff are split into various teams, as mentioned above. Teams leaders select their staff by whatever method they see fit, informing the Admin Team of any changes.
The idea is that team leaders are given enough autonomy to form a team of people who are most likely to complete tasks in a timely manner with precision and accuracy, and to communicate with the EB to minimise arguments so that hopefully the EB will not have to get involved in the day to day running very often.
Inevitably, there will be fall-outs and disagreements. Servers will delink, people will quit IRC due to other commitments, but hopefully the EB will remain committed and stay together, and will be there to rebuild whatever might be lost. If all the admins tell us that we suck and all decide to delink, we will have no one but ourselves to blame for not listening to their issues. We aim to be efficient, professional, knowledgeable and capable overseers.
The downside of all this is that there really is very little "power" for a new admin. But people should decide what they are good at and volunteer for the relevant teams, then they can work their way up. Theoretically, the EB should notice people who are working hard and put them in positions of power.
The leader and members of each team can be found on our Staff List.
[edit] The Web Team
Mailing List: web@lists.blitzed.org.
This team's mailing list is open, to subscribe send an email to: web-request@lists.blitzed.org with subscribe in the body of the email.
Responsibilities:
All aspects of the web site, including some form of template to be used on all official Blitzed sites so they all look the same. That's mainly so that anyone can fix up quick sites that work and look okay without having to wait a month expecting the Web Team to do it all for them.
If you have a problem with the website please send an email to web@blitzed.org.
[edit] The Help Team
There's always going to be a certain number of email cries for help from users. This team deals with people who have been auto-killed or k-lined, and those who can't connect and need someone to email in order to get help.
Mailing List: help@lists.blitzed.org.
Responsibilities:
Producing help documents.
Documenting standards of conduct for IRC Operators.
Training helpers.
Running #help, the only official help channel, which also includes helpers who aren't IRC Operators.
Holding help sessions, when we have enough users to make it worthwhile.
Accepting abuse reports from users regarding staff, and making judgment calls on who should receive them.
[edit] The Services Team
This team looks after all aspects of services, including its maintenance and ongoing development.
Mailing List: services@lists.blitzed.org.
Responsibilities:
Developing and maintaining our services package.
Deciding where services.blitzed.org should be and who should have what level of access to it.
Providing at least one download site where admins and other networks can find our software.
[edit] The Systems Team
This team ensures smooth and efficient running of the DNS and mail for Blitzed.
Mailing List: systems@lists.blitzed.org.
Responsibilities:
Updating DNS and answering hostmaster@blitzed.org mails.
Quickly responding to outages by altering the DNS pools.
Updating mail aliases and lists and answering postmaster@blitzed.org mails.
[edit] The IRCd Team
Mailing List: ircd@lists.blitzed.org.
This team's mailing list is open, to subscribe, send an email to: ircd-request@lists.blitzed.org with subscribe in the body of the email.
Responsibilities:
Development of the network's chosen IRCd.
[edit] The Admin Team
This team is composed of all admins, co-admins and server representatives on the network. Any issue not strictly the business of any other team is dealt with by the Admin Team.
Mailing List: staff@lists.blitzed.org.
Responsibilities:
Training their IRC Operators.
Keeping track of what their IRC Operators are doing and dealing with misconduct accordingly.
Maintaining their ircd, e.g. upgrading it when there is a new release.
Promoting the network.
Upholding & updating network rules.
Any other business (by discussion and/or vote).
Deciding if a test linked server becomes perm linked.
[edit] The Exploits Team
This team's primary purpose is to prevent "trojan clients" from being used on Blitzed.
Mailing List: exploits@lists.blitzed.org.
Responsibilities
Locating and dealing with trojan clients ("drones") and their owners.
[edit] Other mailing lists
There are other informal mailing lists which do not correspond to any role on the network. Please see our mailing list manager site for more details.
[edit] Rules Of Conduct
[edit] For Users
- You will not evade bans.
- You will not mass advertise or mass invite.
- You will not place bots on servers that do not allow bots.
- You will not break clone limits.
- You will not engage in denial of service attacks on users or network infrastructure.
- You will not place Trojan clients (Sub7 bots, etc.) or other hostile bots on our network.
- You will not allow bots under your control to break any of these rules.
We do not automatically monitor the content of conversation or file transfer in order to enforce these policies, however if we become aware of breaches of our policy then we will take action.
The above actions are subject to warning, /kill or /AKILL. Repetitive abuse will be reported to the Services Team and leads to possible nick or channel suspension/loss. Repetitive abuse will also be reported to the offender's ISP.
Network staff will be there to help you, but if you abuse staff they may well /ignore you, or abuse you right back. Staff who are busy may direct you to #help.
[edit] For IRC Operators
- All of the above rules for users apply to IRC Operators.
- You will not interfere with channel management:
- Flooders can be dealt with by channel ops.
- Don't use your o-line or services abilities to manipulate a channel unless you are doing so to prevent abuse (make sure you have logs to support such usage!)
- If services are down and a channel owner requests ops, but you don't know anyone who is on the access list then ask advice from fellow IRC Operators.
- You are expected to help users and respond to polite requests for help:
- If you are too busy, direct them to #help.
- Make sure you are not invisible (umode +i) whilst opered.
- You do not have to take abuse from users, but by the same token you may not at any point use your o-line or increased services access to exact revenge.
- You are expected to take an active part in managing the network:
- As a global IRC Operator you should familiarise yourself with the proper routing of servers, in order to help the network recover from splits.
- You will behave professionally in network channels:
- Our only network-owned channel is #help (others may be founded in the future). In network-owned channels you will not abuse users in any way. Abusive users will be banned and you will be expected to /ignore them.
- You will behave professionally on other networks:
- If it is brought to our attention that you have brought our network into disrepute by e.g. mass advertising us on another network, you may be subject to disciplinary action.
- Keep your admin informed:
- If you can't fulfill your duties or be present on the network for an extended period of time, explain to your admin. This is not likely to pose a problem if the situation is temporary.
[edit] For Admins And Co-Admins
- All of the above rules for IRC Operators and users apply to admins.
- Manage your server staff:
- Make sure they are trained.
- Make sure they are doing their job.
- Help them when they are unsure of what their duties are and/or how to do them.
- Deal with any complaints regarding them before they turn into real problems for the network.
- Comply with guidelines for adding IRC Operators (see "managing O-lines" below).
- Maintain your ircd:
- When the Coding Team releases a new version of the ircd you have one week to apply the change. If the upgrade is a major one (incompatible with previous versions) then expect your ircd to be juped until the upgrade is complete.
- Promote the network:
- Bring users, make us noticed, anyhow and anyway you can (besides spamming!)
- Participate in votes:
- New policy will be determined for the most part by vote of the admins. This includes linking of servers (see admin vote).
- Keep your colleagues informed:
- If you are unable to attend the network temporarily, inform yourstaff and colleagues, and arrange for an acting admin to vote on your behalf.
- If your server is not able to handle its normal client load for whatever reason, you are required to notify the Admin Team and expect it to be temporarily removed from the DNS pools so that it does not take clients. If your server is malfunctioning enough to seriously affect the rest of the network, expect it to be temporarily juped.
[edit] Other Blitzed Policies
[edit] Acceptable Use Policy (AUP)
Any nickname is valid on The Blitzed IRC Network with the exception of nicks designed to trick users into believing you are part of the network or its staff, e.g. for the purposes of stealing passwords.
Any channel is valid on The Blitzed IRC Network with the exception of those clearly founded to advertise other networks, or trick users into believing they are official network administration channels. If your channel moves from Blitzed to another network, or you need to advertise another IRC network in your topic, we ask that you lock your channel +s so that its topic does not appear on a channel /list.
In enforcing the above policies we will use common sense. We will not take away someone's channel the first time they put the address of an IRC server in it and we will not ban every "official looking" nickname. If you are in doubt, please contact the Admin team.
We do not monitor the content of conversation or file transfer. We also do not provide any guarantees that our servers will be available to you either for chatting or file transfer. We provide our services on a "best effort" basis, but be assured that we take that duty very seriously.
[edit] Admin Voting Policy
The Admin Team is expected to be able to agree on a course of action without a vote for the most part. An informal "show of hands" is not regarded as a full admin vote. Admins are expected to use common sense as a full admin vote can be a lengthy process.
The actual voting process is described in a separate article.
As admins on this network, you are expected to participate in its running. If you are due to be away from the network temporarily (holiday/vacation/work trip etc.) then you must appoint an acting admin. This is usually your co-admin, but may be any individual who is not already serving as a member of staff on another server.
Neglecting to vote is a serious failing for you as an admin. Servers that persist in not voting WILL FACE A DELINK NO MATTER HOW MANY USERS THEY HAVE ON THEM OR WHO RUNS THEM. If you are not willing to help run the network, you do not belong here as an admin. Failure to vote may, at the discretion of the Executive Board, lead to temporary loss of voting privilege.
Most votes and their discussions are to be carried out on the Blitzed Public list, so that users are aware of what is going on. The vote may be held in private if the proponent so desires, but there should be good reason. If the vote is held in private, the proponent must still summarise the result to the public list after the vote is complete.
Currently votes are recorded by server admins emailing their votes to vote@blitzed.org. This email goes only to swat and Antony, who are responsible for reminding admins to vote and the counting/announcing of vote results.
[edit] Managing O-lines
[edit] Home servers
Every IRC operator must have a "home server", and the admin of that server is responsible for the behaviour of the IRC operator no matter which Blitzed server (s)he connects to.
[edit] Number of IRC operators
Each server may have O-lines for up to four distinct members of staff. This includes the admin and co-admin (if present), it does not include O-lines for proxy scanners or other programs that are approved by the admin team for operation of the server or network. This figure will be increased as the network grows, and will be increased across the board.
[edit] Global operators
The Admin Team must be informed by email to admins@lists.blitzed.org at least 48 hours prior to a local IRC operator being upgraded to global IRC operator. During this time, any objections will be made clear by members of the Admin Team and the promotion may be blocked by admin vote. When informing the Admin Team of planned oper promotions, it is preferable to do so before discussing the matter with the oper concerned.
The only way to become a global IRC operator is to serve for at least 30 days as a local IRC operator. Exceptions to this policy may be made at the discretion of the Admin Team, for example in the case of an existing or former global operator moving to a new server. An admin is under no obligation to upgrade a local IRC Operator to global in 30 days; that is completely up to the admin concerned.
[edit] Local operators
Admins may appoint local IRC operators with a view to training them until they are eventually suitable candidates for global O:lines. A user must have had a registered nickname for 30 days to be eligible for local IRC Operator status.
The Admin Team must be informed by email to admins@lists.blitzed.org at least 48 hours prior to the addition of a local IRC operator so that any possible objections can be made clear. When informing the Admin Team of planned local oper additions, it is preferable to do so before discussing the matter with the user concerned.
[edit] Removal of operators
Admins may remove members of their staff at any time for any reason. They are required to notify the Admin Team of the removal but are not required to state reasoning.
Not all network staff have O-lines. Having IRC Operator status is not required before you can help in the various teams. Likewise, losing an O-line does not prevent you from continuing to serve in a team. Team composition is the business of the team leader.
Admins may be required to remove or restrict one of their staff member's o-lines due to vote of Admin Team or order of the EB. Failure to promptly (24hrs) do so may lead to action against the admin concerned.
[edit] Backup operators
Each server may have as many backup O-lines as necessary. It is up to the admin of the server who they add backup O-lines for. It is suggested that admins are generous in giving out backup O-lines so that their server may be fixed ASAP should none of their regular staff be present. Backup O-lines for existing global operators may be added, removed or updated as the server's admin sees fit without consulting anyone.
[edit] Notification
After any change of oper status (e.g. adding an oper, moving an oper to another server, promotion from local to global, etc.) a news item should be created which will send notification to the web site and public mailing list.
[edit] Link Procedure
The server link procedure is determined by the Admin Team.
Applicants are expected to fill in the link application form. No link will be given unless the form is filled in, and still must be approved by the Admin Team.
The Admin Team will inform the public user list when a new application has been submitted.
The Admin Team will spend up to one week investigating the link application and voting to decide whether the server will be granted a test link with Blitzed. Voting on this matter will take place on the public mailing list. Justification for votes will be given where possible and any discussion, prior to voting, will also take place in public.
If they are unsure, the Admin Team may recommend that the server be linked to the test network first to assess its stability. The Admin Team may also request shell access to the applicant's server to verify details of the link application.
A newly test-linked server will have one global O-line for its admin. All other O-lines must be local. In addition the admin will have no services access.
Admins or IRC Operators listed on the application who already have services access or full IRC Operator status on the network (e.g. they are existing staff who are moving servers) may retain this access unless majority decision of Admin Team decrees otherwise.
During a test link period, the admin may not add any new IRC Operators to their server.
Minimum length of test-link is 30 days. Test-link may be extended at the discretion of the Admin Team. When the Admin Team is satisfied that the test-link has lasted long enough, admins will either fail the test-link (and not offer a permanent link), or will accept the server for perm link to Blitzed. All perm links must be approved by majority admin vote. Any server recommended to the Admin Team has shown promise from a routing aspect, and the Admin Team must assess actual performance of the server, and the character of the new admin, which is just as important. An Admin Team represantant will inform the applicant of the progress of their test-link (retarded/unreadable linkapp, accepted for test-link, denied test-link, failed test-link, accepted for perm-link) and copy the Admin Team on all correspondence. Applicants denied or failing their test-link may reapply the same server after 30 days if they believe they have rectified any problems with their initial application. Alternatively, an application may be sent for a different server, but the "30-day rule" still applies. Those listed as Admins and IRC Operators on applying servers must have a nick that has been registered on Blitzed for at least 30 days. This and other linking procedures may be altered on a case-by-case basis at the discretion of the Admin Team.
[edit] Delink Procedure
Any admin may call for the delink of another server by means of an admin vote. The server cited for delink may not vote. However, admins may not ABSTAIN on a delink vote.
[edit] Server routing
All global IRC Operators are expected to help with routing and recovering from network disruption. If server rerouting is required, an IRC Operator must first warn fellow staff:
/chatops I'm about to reroute penguin, scream now if this is bad
(wait 10 seconds or so)
Then users due to be affected by the upcoming split MUST be warned via services global notice or a mass-notice:
/notice $penguin.*blitzed.org haven users, the server you are using is shortly going to be rerouted to reduce lag. Please bear with us.
And finally the reroute takes place.
Please note that servers normally recover from netsplits themselves due to autoconnects defined in their configs. There should be no need to intervene unless there is a problem. For example, a server may be able to connect to its primary hub but packet loss on that link may be unacceptable, therefore requiring a reroute to its secondary hub.
Unnecessary rerouting of client servers is frowned upon - a few hundred milliseconds extra lag is not normally noticeable for users, unlike a netsplit.
The current optimal routing plan for the network is decided and documented by The Admin team.
[edit] Emergency Action
Any admin or services admin may take emergency action to immediately resolve or mitigate network problems. This includes actions that would normally require a full admin vote.
This can include immediate delink of servers or linking of new servers without the normal test-link procedure being followed.
The staff member is required to explain their actions in full to the Admin Team ASAP. Obviously, these actions should not be taken lightly and staff causing unnecessary damage to the network should expect to be reprimanded once the dust has settled.
[edit] The Executive Board
The EB has the last word on all aspects of network management.
The EB, however, is not in place to run the network itself. The EB expects each team to manage itself. Any member of staff who is unhappy with the management of the network should feel free to contact the EB either by mail or on the network itself.
The EB has the network's best interests at heart and wishes for hard-working staff to be rewarded, and not have to use their ultimate power to resolve conflict.
The EB exists as effective team leaders for the Admin Team. Each team leader is free to run their team's associated mailing lists as they see fit, however, the EB expects admins to conduct themselves professionally on the admin list. That means admins are expected to compose legible, non-abusive emails without excessive quoting. Failure to comply with this reasonable request will lead to the EB requesting the admin appoint a more polite acting admin to represent the server on the Admin Team.
[edit] Change Of Server Details
Admins are permitted to alter their server's details such as operating system, hardware, and/or bandwidth. The Admin Team should be informed of any such changes.
Should a server need to move location net-wise from its current local network, then the server may need to reapply for a test-link period. This, of course, will be approved/denied at the discretion of the Routing Team.
The Admin Team must be informed by email to admins@lists.blitzed.org at least 48 hours prior to the change of a server Admin so that any possible objections can be made clear. Should any objections not be resolved in discussion by the Admin Team then an admin vote will be called to decide whether the sdrver should go through a new test link period, continue to be permanently linked with the new Admin or be delinked.
[edit] Nick And Channel Dispute Policy
Nicks and channels are registered on a first come, first served basis. In situations where the Admin team believes there to be a clear case of nick or channel stealing, services admins may intervene to settle the situation at their discretion. The decision of the Admin team is final.
Users wishing to report nick or channel "stealing" should do so via email to the Admin team. Please include as much information about the event as possible, including logs.
Users should note that such cases of nick or channel "stealing" can only occur through carelessness such as sharing passwords, accidentally pasting them to public channels or picking passwords that are trivial to guess. In a dispute, decisions over nick/channel ownership will be made by admins based only on information such as logs from services and what staff members have personally witnessed. As such there is no guarantee that a nick or channel will be returned to its original owner in these situations.
Users who persistently "lose" their nicks/channels are also unlikely to be taken seriously.