Log in | Back to darenet.org

Staff:Network Organization

m (How DareNET works)
m (How DareNET works)
 
(3 intermediate revisions not shown)
Line 61: Line 61:
! style="text-align:left;"|Manager
! style="text-align:left;"|Manager
|-
|-
-
| Development
+
| Development <dev@darenet.org>
| SecretAgent <secretagent@darenet.org>
| SecretAgent <secretagent@darenet.org>
|-
|-
-
| Infrastructure
+
| Infrastructure <infrastructure@darenet.org>
| NiTeMaRe <nitemare@darenet.org>
| NiTeMaRe <nitemare@darenet.org>
|-
|-
-
| Support
+
| Support <support@darenet.org>
| Vicarious <vicarious@darenet.org>
| Vicarious <vicarious@darenet.org>
|}
|}
Line 83: Line 83:
As you can see, each part is important. None are too overbearing, and they are each needed for DareNET to function. Cooperation is the only way things can work.
As you can see, each part is important. None are too overbearing, and they are each needed for DareNET to function. Cooperation is the only way things can work.
-
The actual administration is based on the below control structure:
+
'''The actual administration is based on the below control structure:'''
* Server administrators are in charge of their servers, in conjunction with the Infrastructure team.
* Server administrators are in charge of their servers, in conjunction with the Infrastructure team.
Line 91: Line 91:
* The Executive Board and Operations team have the highest authority for network decisions.
* The Executive Board and Operations team have the highest authority for network decisions.
-
And responsibility is laid out as follows:
+
'''And responsibility is laid out as follows:'''
* Operators are answerable to their admin.
* Operators are answerable to their admin.
-
* Individual admins are answerable to the Executive Board.
+
* Individual admins are answerable to the Operations team.
* Team members are answerable to the team manager.
* Team members are answerable to the team manager.
* Teams are answerable to the Operations team.
* Teams are answerable to the Operations team.
* The Operations team is answerable to the Executive Board.
* The Operations team is answerable to the Executive Board.
* The Executive Board is answerable to the staff, as a whole.
* The Executive Board is answerable to the staff, as a whole.
 +
 +
[[Category:Staff Documentation]]

Current revision as of 05:34, 16 February 2011

DareNET's administrative foundation is formed by various teams, which 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, and all teams work under the oversight of the Operations team, which consists of the actual administrators of the physical servers that make up DareNET.

Each staff member is required to actively participate on at least one team.

In This Guide:

Team managers

These individuals are directly responsible for ensuring their teams are adequately staffed, while following any network staffing policies that may be in place. They supervise and manage the overall performance of members on their team. They're also responsible for ensuring the team achieves any team and network goals, visions and objectives.

Team managers are appointed through a method determined by the Operations team.

Teams

The following teams currently exist on DareNET:

Executive Board

eb@darenet.org

DareNET's main governing body, retaining ultimate authority in all network matters. However, 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 caretakers, the 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).

Operations team

ops@darenet.org

The Operations team is comprised of the administrators of the physical servers that make up DareNET. They jointly oversee the activities of the network and its various teams. The team has the authority to make decisions on broad network and policy issues.

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.

Development team

dev@darenet.org

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.

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.

Membership is decided by the development manager.

Infrastructure team

infrastructure@darenet.org

The Infrastructure team is responsible for maintaining a stable, secure, 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.

Membership is decided by the infrastructure manager.

Support team

support@darenet.org

Support is responsible for the customer service aspect of DareNET's day-to-day operations. As such, its members listen to requests, abuse reports and questions from our users and respond based on the network rules and current policies of DareNET.

Membership is decided by the support manager.

Current team managers

Team Manager
Development <dev@darenet.org> SecretAgent <secretagent@darenet.org>
Infrastructure <infrastructure@darenet.org> NiTeMaRe <nitemare@darenet.org>
Support <support@darenet.org> Vicarious <vicarious@darenet.org>

How DareNET works

The above list of teams and their brief descriptions do not go much towards actually explaining how DareNET's administration actually functions. To explain this, we first need to look at the key elements of DareNET's existence:

  • DareNET would be nothing without the users (thus, users make the network).
  • DareNET servers are operated and sponsored by the admins, without which there would be no IRC network at all.
  • DareNET was founded by the Executive Board, who in essence own and control the domain and some other vital resources.
  • The Operations team is the main decision making body on DareNET.
  • DareNET relies on its staff and teams for its day-to-day operations.

As you can see, each part is important. None are too overbearing, and they are each needed for DareNET to function. Cooperation is the only way things can work.

The actual administration is based on the below control structure:

  • Server administrators are in charge of their servers, in conjunction with the Infrastructure team.
  • Teams handle various issues, specific to their function.
  • The Infrastructure Manager oversees most technical aspects of DareNET.
  • The Operations team oversees non-technical operations on DareNET.
  • The Executive Board and Operations team have the highest authority for network decisions.

And responsibility is laid out as follows:

  • Operators are answerable to their admin.
  • Individual admins are answerable to the Operations team.
  • Team members are answerable to the team manager.
  • Teams are answerable to the Operations team.
  • The Operations team is answerable to the Executive Board.
  • The Executive Board is answerable to the staff, as a whole.