Staff:Guidelines

Current revision as of 02:35, 12 February 2011

Our number one goal is to provide outstanding "customer service" to our users. To that end, we only have one rule:

Use your best judgement in all situations.

The information given here is written as general staff guidelines. All staff must answer to their team manager (and/or admin), and because of that, where these guidelines conflict with instructions you have been given by your superior, you should listen to your superior.

Staff Requirements

Being a staff member on DareNET is a privilege, and like most others, it comes with responsibility. There are a few requirements and "duties" for all staff members, which are detailed in this section.

Keep in mind that IRC is meant to be fun. If you don't feel like doing something at a particular time, don't do it (but be polite about it, especially if a user is requesting help from you). However, if you find that you're rarely in the mood for doing "staff stuff", then perhaps being a staff member is not for you.

While there is no minimum hours one most devote to helping out per week/month, we do expect ALL staff to be active on the network and mailing lists on a continuing basis. Staff found to be "inactive" will be asked to resign. Inactive shall be defined as staff who continually are not present or take part in the network's day-to-day operations.

You are expected to:

Help maintain the network.
Help users.
Enforce DareNET's AUP.
Follow the guidelines and instructions given in this guide.
Behave in a fitting manner for a DareNET staff member.
Keep up to date on DareNET matters, rules and policies.
Participate in mailing list discussions.
Not share confidential information with non-staff.

Help maintain the network

You should monitor the state of the network. For the most part, this means watching for netsplits and lag, reconnecting and rerouting servers if necessary. You should look into anything that seems strange or just plain "wrong" on the network, bringing it to the attention of the appropriate individuals if need be.

Help users

All staff should help users. If a user approaches you for help, and you are unable to help him/her yourself for any reason (e.g., you don't know the answer, you're busy, etc.), you should direct the user to #support or try to locate someone else who can assist the user. At the very least you should politely indicate that you are unable to help.

Enforce DareNET's AUP

As a staff member you are expected to uphold DareNET's rules. Use the means available to you to deal with any violation of rules in an appropriate manner.

Do not share confidential information with non-staff

As a staff member, you will be informed of many confidential issues, facts and matters. Whether these are related to DareNET's security, its users or services, it is extremely important that you do not disclose such information to anyone who is not a DareNET staff member. This especially concerns information obtained through privileged sources (e.g., staff mailing list, globops, staff channel, etc.).

Conduct

As a staff member, your conduct on the network reflects upon yourself, your peers, network leadership and DareNET's image. You should act in a professional manner, especially when carrying out network duties. A good question to ask yourself is, "is what I'm about to do going to reflect badly on DareNET in any way, shape or form?" Repeatedly protraying DareNET in a "bad light" will probably cause you to be dismissed from staff.

Interaction with users

The manner in which you present yourself will almost always make a difference in how efficiently and effectively you are able to handle any issue with users. You should remain calm and matter of fact at all times when dealing with users in an "official" capacity. If you become upset or angry, you will be less effective and possibly even unintentionally make the situation worse. If you are unable to remain objective, consider asking another staff member to handle the issue for you. Staff need to work as a team and recognizing our individual strengths or weaknesses is an integral part of good team work. It is better for DareNET to have staff who are able to rely on others for help, than to risk handling a situation poorly.

DareNET staff should NOT look down on users, make fun of or ridicule them. Users should be treated with respect. If you feel that you are above the network's users, you should rethink your view, as it probably won't be long until someone is tapping you on the shoulder asking you to resign. You are staff to the serve the network, and thus, its users.

When handling situations involving users, we've found that the following recommendations allow staff to handle the situation in a good and professional manner. Some of them, obviously, only apply to specific situations:

Be polite and respectful.

Give the benefit of the doubt. If you have had a complaint about a user, ask them to tell you what the problem is themselves before confronting them about their reported behavior.

State the issues clearly, without personal criticism. For example, saying "I received a complaint about someone repeatedly flooding this channel. Do you know what happened?" will open up communication and the possibility of finding a peaceful solution. Whereas, just saying "I /KILL lamers for flooding." will most likely result in an escalation of the problem.

Clearly state the rule or policy that was violated. For example, "Flooding is not allowed on DareNET because it interferes with other users' ability to chat." is not only instructional, but also states the network's position on the issue.

Clearly state what the consequences are. For example, state "You are being warned. If I receive further complaints, you will be disconnected from the network. Any complaints after that may result in a network ban." This way everyone knows what to expect and there will be no need to engage in any debate with the user. Make sure you know what the appropriate action is for a particular violation and do not threaten to take action which goes against the network's policy for a particular issue.

Do not "threaten" an action until you are certain it is what you will do. While it is good to state possible consequences of an action, it is important users know that once we state we will do something, we follow it through. If staff vacillate, it can start to sound like empty threats and users may "test" repeatedly to see if we really mean what we say. It is better to avoid taking action until you are sure there is no other option, then doing so quickly and without further discussion. No profanity or name calling, just state the reason based on the offending behavior.

Do not criticize or ridicule users. Have patience for typos. Avoid embarrassing a user in front of others. Educate, not humiliate.

English may be a second (or latter) language for some users; therefore, some colloquialisms and slang may be confusing or easily misinterpreted. Please try to use correct grammar and punctuation as this will facilitate ease of communication.

Try to be sensitive to how others view the role of a staff member, specifically IRC operators. Control and privileges are easily misunderstood. Being aware of your own feelings in this regard can be helpful in your interactions with others.

Interactions with staff

When dealing with other staff members, how you conduct yourself is equally important as well. In general, it can have a huge influence on the overall morale, for better or worse.

Be polite and respectful.

Help other staff members if they ask for it.

If you think someone is doing a good job and have something nice and encouraging to say, say it. Positive input is appreciated, and can make a big difference.

If you think someone is not acting right, you may try to correct that person in private, POLITELY. Don't make defaming or derogatory comments about other staff members, especially not in public. It only lowers morale and doesn't help to solve the situation.

If you want to make a complaint about another staff member, see the section on Staff Misconduct. Do not flame the person in public, or attempt to "get to" them in other ways.

Staff misconduct

The procedure for registering a complaint about a DareNET staff member is:

Try to resolve the problem by talking to the other person directly.
If there is still a problem, report it to the person's superior. If the issue is related to some team, report it to the team's manager. If the person is an IRC operator and it's a generic complaint, report it to that person's admin. If you do not know the oper's "home" server, report it to the admin of the server they were on at the time.
If the problem remains unresolved after the superior investigated and made a decision, a report can be sent to the Operations team with supporting documentation (including all logs from all the meetings with the person and with the superior).
Any case unresolved by the Operations team may be reviewed by the Executive Board, who will make the final decision.

Possible consequences of misbehavior are decided by the superior of that staff member (e.g., the oper's admin or the team manager, as appropriate) alone or in conjunction with the Operations team and/or Executive Board. The specific action taken will depend on the serverity of the misconduct, which may include:

Demotion for a probationary period.
Personal and/or public apology.
Replacing or reconstructing any damaged records.
Removal of channel access; temporarily or permanently for repeated offenses.
Removal of O-line or staff position.
Removal of services access.
Mailing list moderation or removal.
Refusal of future staff opportunities.
Banned from the network.

Channel ownership and control

DareNET staff are NOT to involve themselves in channel matters, period. I don't think we can stress this enough. Users are free to operate their channels as they wish (provided they do not break network rules) without interference from us, and you are to respect that right at all times.

Matters pertaining to channel registration should be handled by the Support team. If a channel's users or ops complain about how the channel is run, the issue should be solved by the channel's co-owners and (ultimately) by the owner. The owner has full control over the channel and may run it as (s)he pleases.

@@ Line 1: / Line 1: @@
-= Purpose =
+Our number one goal is to provide outstanding "customer service" to our users. To that end, we only have one rule:
-The purpose of this document is to briefly provide an overview on how DareNET operates, and to establish consistent guidelines and rules for DareNET staff to follow while carrying out their duties on the network. They MUST be adhered to at all times, regardless of one's position on the network. If a guideline states specific access is needed to carry out the desired effect, then it must be done by someone with equal or higher access. Simply "getting permission" from such an individual is not sufficient.
+#'''Use your best judgement in all situations.'''
-This document IS the final and ultimate rule book for staff conduct and activity. Any rule you have heard of that is not written within these guidelines or contained in one of the policy documents simply does not exist. If you continue to follow such "unwritten" rules after warning could have consequences up to and including your dismissal from staff.
+The information given here is written as general staff guidelines. All staff must answer to their team manager (and/or admin), and because of that, where these guidelines conflict with instructions you have been given by your superior, you should listen to your superior.
-These guidelines and rules are here because we want to present a consistent and united focus to our user base.
+== Staff Requirements ==
-= Network Organization =
+Being a staff member on DareNET is a privilege, and like most others, it comes with responsibility. There are a few requirements and "duties" for all staff members, which are detailed in this section.
-Various teams form the administrative foundations of DareNET. They can be divided roughly into two groups: administrative and broad policy/decision making teams, and those which center on providing a particular service or cover specific aspects of the network's operations. Regardless, each team is given the authority to autonomously carry out their responsibilities. Each team has a manager. All teams work under the oversight of the Operations team, which consists of the actual administrators of the physical servers that make up the network.
+Keep in mind that IRC is meant to be fun. If you don't feel like doing something at a particular time, don't do it (but be polite about it, especially if a user is requesting help from you). However, if you find that you're rarely in the mood for doing "staff stuff", then perhaps being a staff member is not for you.
-Each staff member is required to actively participate on at least one team.
+While there is no minimum hours one most devote to helping out per week/month, we do expect ALL staff to be active on the network and mailing lists on a continuing basis. Staff found to be "inactive" will be asked to resign. Inactive shall be defined as staff who continually are not present or take part in the network's day-to-day operations.
-Finally, everyone of DareNET's staff is also a member of the "DareNET Team" -- everyone is dedicated to making DareNET a better IRC network.
+You are expected to:
-== Team Managers ==
+* Help maintain the network.
+* Help users.
+* Enforce DareNET's [[Policy:Acceptable Use Policy|AUP]].
+* Follow the guidelines and instructions given in this guide.
+* Behave in a fitting manner for a DareNET staff member.
+* Keep up to date on DareNET matters, rules and policies.
+* Participate in mailing list discussions.
+* Not share confidential information with non-staff.
-Team managers are directly responsible for ensuring their teams are adequately staffed, provided they follow any network staffing policies that may be in place. Managers supervise and manage the overall performance of staff on their team. They are also responsible for ensuring the team achieves team and network goals, visions and objectives.
+=== Help maintain the network ===
-Team managers are appointed through a method determined by the Operations team.
+You should monitor the state of the network. For the most part, this means watching for netsplits and lag, reconnecting and rerouting servers if necessary. You should look into anything that seems strange or just plain "wrong" on the network, bringing it to the attention of the appropriate individuals if need be.
-== Teams ==
+=== Help users ===
-The following teams currently exist:
+All staff should help users. If a user approaches you for help, and you are unable to help him/her yourself for any reason (e.g., you don't know the answer, you're busy, etc.), you should direct the user to #support or try to locate someone else who can assist the user. At the very least you should politely indicate that you are unable to help.
-=== Executive Board ===
+=== Enforce DareNET's AUP ===
-DareNET's main governing body, retaining ultimate authority in all network matters. Most, if not all, areas of the network's operations have been delegated to various teams (outlined below) leaving the Executive Board to function in an oversight capacity. As such. the board's remit is only as caretakers for all network matters.
+As a staff member you are expected to uphold DareNET's rules. Use the means available to you to deal with any violation of rules in an appropriate manner.
-As caretakers, the Executive Board exists to hold, in trust, ownership of some essential resources, like dedicated servers (e.g., master dns, mail servers, etc.), the darenet.org domain, etc. The board also acts as an arbitrator in the mediation of disputes regarding network matters that cannot be resolved through other means (i.e., disputes referred to it by the Operations team).
+=== Do not share confidential information with non-staff ===
-Contact address: eb@darenet.org
+As a staff member, you will be informed of many confidential issues, facts and matters. Whether these are related to DareNET's security, its users or services, it is extremely important that you do not disclose such information to anyone who is not a DareNET staff member. This especially concerns information obtained through privileged sources (e.g., staff mailing list, globops, staff channel, etc.).
-=== Operations Team ===
+== Conduct ==
-The Operations team is comprised of the administrators of the physical servers that make up DareNET, who jointly oversee the activities of the network and its various teams. They have the authority to make decisions on broad network and policy issues.
+As a staff member, your conduct on the network reflects upon yourself, your peers, network leadership and DareNET's image. You should act in a professional manner, especially when carrying out network duties. A good question to ask yourself is, "is what I'm about to do going to reflect badly on DareNET in any way, shape or form?" Repeatedly protraying DareNET in a "bad light" will probably cause you to be dismissed from staff.
-Membership is limited to server administrators who have been "linked" to DareNET (in a permlink status) for at least three months. Non-IRC server administrators / sponsors of other DareNET servers may hold a non-voting seat on the team.
+== Interaction with users ==
-Contact address: ops@darenet.org
+The manner in which you present yourself will almost always make a difference in how efficiently and effectively you are able to handle any issue with users. You should remain calm and matter of fact at all times when dealing with users in an "official" capacity. If you become upset or angry, you will be less effective and possibly even unintentionally make the situation worse. If you are unable to remain objective, consider asking another staff member to handle the issue for you. Staff need to work as a team and recognizing our individual strengths or weaknesses is an integral part of good team work. It is better for DareNET to have staff who are able to rely on others for help, than to risk handling a situation poorly.
-=== Development Team ===
+DareNET staff should NOT look down on users, make fun of or ridicule them. Users should be treated with respect. If you feel that you are above the network's users, you should rethink your view, as it probably won't be long until someone is tapping you on the shoulder asking you to resign. You are staff to the serve the network, and thus, its users.
-The Development team is responsible for maintaining and developing much of the software the network is built upon, which includes, but is not limited to: ircd-darenet, webchat-darenet, website-darenet and services-darenet. The team may take on other projects, as decided by the development manager.
+When handling situations involving users, we've found that the following recommendations allow staff to handle the situation in a good and professional manner. Some of them, obviously, only apply to specific situations:
-The team is also responsible for providing a means where staff can easily report bugs, submit feature requests and provide feedback in regards to the team's core projects.
+* Be polite and respectful.
-Membership is decided by the development manager.
+* Give the benefit of the doubt. If you have had a complaint about a user, ask them to tell you what the problem is themselves before confronting them about their reported behavior.
-Contact address: dev@darenet.org
+* State the issues clearly, without personal criticism. For example, saying "I received a complaint about someone repeatedly flooding this channel. Do you know what happened?" will open up communication and the possibility of finding a peaceful solution. Whereas, just saying "I /KILL lamers for flooding." will most likely result in an escalation of the problem.
-=== Infrastructure Team ===
+* Clearly state the rule or policy that was violated. For example, "Flooding is not allowed on DareNET because it interferes with other users' ability to chat." is not only instructional, but also states the network's position on the issue.
-The Infrastructure team is responsible for maintaining a stable, geographically diverse and well structured infrastructure for not only the DareNET IRC network, but the organization as a whole. The team is directly responsible for maintaining the servers linked to the network, web servers, database servers, and name servers, in conjunction with their respective administrators. The team also maintains the IRC pool, reviews link applications and administers the test link process.
+* Clearly state what the consequences are. For example, state "You are being warned. If I receive further complaints, you will be disconnected from the network. Any complaints after that may result in a network ban." This way everyone knows what to expect and there will be no need to engage in any debate with the user. Make sure you know what the appropriate action is for a particular violation and do not threaten to take action which goes against the network's policy for a particular issue.
-Membership is decided by the infrastructure manager.
+* Do not "threaten" an action until you are certain it is what you will do. While it is good to state possible consequences of an action, it is important users know that once we state we will do something, we follow it through. If staff vacillate, it can start to sound like empty threats and users may "test" repeatedly to see if we really mean what we say. It is better to avoid taking action until you are sure there is no other option, then doing so quickly and without further discussion. No profanity or name calling, just state the reason based on the offending behavior.
-Contact address: infrastructure@darenet.org
+* Do not criticize or ridicule users. Have patience for typos. Avoid embarrassing a user in front of others. Educate, not humiliate.
-=== Support Team ===
+* English may be a second (or latter) language for some users; therefore, some colloquialisms and slang may be confusing or easily misinterpreted. Please try to use correct grammar and punctuation as this will facilitate ease of communication.
-The Support team is responsible for the customer service end of DareNET's day-to-day operations. As such, its members listen to requests and questions from our users and respond based on the network rules and current policies of DareNET.
+* Try to be sensitive to how others view the role of a staff member, specifically IRC operators. Control and privileges are easily misunderstood. Being aware of your own feelings in this regard can be helpful in your interactions with others.
-Membership is decided by the support manager.
+== Interactions with staff ==
-Contact address: support@darenet.org
+When dealing with other staff members, how you conduct yourself is equally important as well. In general, it can have a huge influence on the overall morale, for better or worse.
-== How DareNET Works ==
+* Be polite and respectful.
-The above list of teams and their brief descriptions do not go much towards explaining how DareNET's administration actually functions. To explain this, we first need to look at the key elements of DareNET's existence:
+* Help other staff members if they ask for it.
-* DareNET would be nothing without the users (thus, users make the network).
+* If you think someone is doing a good job and have something nice and encouraging to say, say it. Positive input is appreciated, and can make a big difference.
-* DareNET servers are operated and/or sponsored by the admins, without which there would be not IRC network at all.
-* DareNET was founded by the Executive Board, who in essence own and control the domain and other vital resources.
-* The Operations team is the main decision making body on DareNET.
-* DareNET relies on its staff and teams for its operations.
-As you can see, each part is important. None are too overbearing, and they are all needed for DareNET to function. Cooperation is the only way things can work.
+* If you think someone is not acting right, you may try to correct that person in private, POLITELY. Don't make defaming or derogatory comments about other staff members, especially not in public. It only lowers morale and doesn't help to solve the situation.
-The actual administration is based on the below control structure:
+* If you want to make a complaint about another staff member, see the section on Staff Misconduct. Do not flame the person in public, or attempt to "get to" them in other ways.
-* Server administrators are in charge of their servers, in conjunction with the Infrastructure team.
+== Staff misconduct ==
-* Teams handle various issues, specific to their function.
-* The Infrastructure manager oversees the technical aspects of DareNET.
-* The Operations team oversees non-technical operations on DareNET.
-* The EB and Operations team have the highest authority for network decisions.
-And responsibility is laid out as follows:
+The procedure for registering a complaint about a DareNET staff member is:
-* Operators are answerable to their admin.
+# Try to resolve the problem by talking to the other person directly.
-* Individual admins are answerable to the EB.
+# If there is still a problem, report it to the person's superior. If the issue is related to some team, report it to the team's manager. If the person is an IRC operator and it's a generic complaint, report it to that person's admin. If you do not know the oper's "home" server, report it to the admin of the server they were on at the time.
-* Team members are answerable to the team manager.
+# If the problem remains unresolved after the superior investigated and made a decision, a report can be sent to the Operations team with supporting documentation (including all logs from all the meetings with the person and with the superior).
-* Teams are answerable to the Operations team.
+# Any case unresolved by the Operations team may be reviewed by the Executive Board, who will make the final decision.
-* The Operations team is answerable to the EB.
-* The EB is answerable to the staff, as a whole.
+Possible consequences of misbehavior are decided by the superior of that staff member (e.g., the oper's admin or the team manager, as appropriate) alone or in conjunction with the Operations team and/or Executive Board. The specific action taken will depend on the serverity of the misconduct, which may include:
+* Demotion for a probationary period.
+* Personal and/or public apology.
+* Replacing or reconstructing any damaged records.
+* Removal of channel access; temporarily or permanently for repeated offenses.
+* Removal of O-line or staff position.
+* Removal of services access.
+* Mailing list moderation or removal.
+* Refusal of future staff opportunities.
+* Banned from the network.
+== Channel ownership and control ==
+DareNET staff are NOT to involve themselves in channel matters, period. I don't think we can stress this enough. Users are free to operate their channels as they wish (provided they do not break network rules) without interference from us, and you are to respect that right at all times.
+Matters pertaining to channel registration should be handled by the Support team. If a channel's users or ops complain about how the channel is run, the issue should be solved by the channel's co-owners and (ultimately) by the owner. The owner has full control over the channel and may run it as (s)he pleases.
+[[Category:Staff Documentation|Guidelines]]