Hack This Site!

[Advertise With HackThisSite.org :: Hide These Ads]

Tomorrow's just a day away

HTS Staff Charter
Updated on May 3rd, 2009 by ScrAm
Related text documents:
HTS Introduction / Organizing Guide
HTS Meeting Organizing Guide

Almost after three whole years after this document was created, the HackThisSite Development Team decided to brush the dust off the old HackThisSite Documents and restore HackThisSite back to its previous glories. This document was originally created out of the need to develop a more structured, clearly defined set of duties, responsibilities, and access levels for those working for the HackThisSite project, after three years, it was renewed for the very same reason. As the community grows and new projects and controversies are introduced, it is important to maintain an element of order and structure to prevent things from spinning out of control.

These seperate sections to group staff simply define positions, duties, and access levels, and do not imply any sort of hierarchy or social class. Everyone part of staff has a role in participating in the decision making process, and we take steps to keep this organization democratic and have an ordered anarchist approach towards administration.

Root Level Administrators
weekend hacker, Kage, ScrAm, comperr, and Silent-Shadow
Xec96, Ikari, Buz (D. Kloosterman), IceShaman

Duties and responsibilities include

maintaining the dedicated server
keeping software up to date
setting access levels
coordinating with developers

Root level administrators also have the same responsibilities and duties as Staff Developers. Access includes complete root access to the dedicated server. However, do not expect them to be online. Especially Kage, he is our host, but he does not carry any responsibility for the site.

Root Level Administrators must exercise extreme discretion and maturity in dealing with staff and users. This unique position requires an enlightened, open-minded approach towards administration to prevent corruption and to set productive and creative examples to other members of the community.

Staff Developers
NightQuest, anarkakari, jokerrrr, seth_slade, and Anoresto

Staff developers are responsible for:

fix bugs
developing new aspects of the site
perform general site maintenance
brainstorm and
create projects for the site

Access includes an independent SVN account. Neither SQL nor forum access should be needed.
Developers are expected to maintain a level of activity on the site + other projects, and learn to communicate + work with other staff members in a friendly, cooperative and productive way. Developers should read the developer guideline.

IRC Staff
IRC Staff have the duty of maintaining peaceful, mature discussion on the IRC network to prevent abuse and immaturity. Separate IRC staff were made to prevent staff developers from being involved and distracted through babysitting the IRC channels so that they can concentrate on positive aspects of the staff. However, this rule does not apply to administrators or moderators.

IRC Staff have the responsibility and duty to be an unbiased, open minded, tolerant, and flexible IRC operator, and must work to resolve conflicts with a diplomatic and NOT disciplinary approach towards administration. We will also develop a system to report abuse of IRC admin in case of power struggle. Currently, you can report these problems to ScrAm.

Moderators
Monica, Sonic7145, eljonto, yourmysin, Defience, TheMindRapist, fiftysixer

Moderators have the duty of maintaining the various moderator functions on the site. These duties including:

accepting or rejecting new articles
looking over user comments
bringing uncooperative users to developer's attention
news gatherings

Moderators can act as the 'eyes and ears' for problems developing on the site or community and can help bring things to the attention to the other developers in terms of bug fixes or other problems.

Moderators are often a way to work up and gain the skills and work experience necessary to become a developer on the site, and will often work with developers or do beta testing.

Sub collectives and working groups
Examples: the n-zone, root this box, hack this zine, critical security etc.

Often times, sub-projects of HTS will be created with its own users to help develop test and participate with the project. These official sub collectives or working groups may create its own internal rules and staff and delegate responsibilities within itself. A sub collective may have one or more team leaders to help facilitate the project as well as communicate with the larger group. While people may be part of the 'n-zone team' and have access levels and duties corresponding to their position on the team, it does not necessarily imply being a part of HTS staff. Although it is usually a very good way of getting used to working with staff and provide a step up that may enable you to become part of staff one day.

This is a flexible document and may be changed with consensus to reflect newer circumstances.

HackThisSite is is the collective work of the HackThisSite staff, licensed under a CC BY-NC license.
We ask that you inform us upon sharing or distributing.

_{Page Generated: Sun, 12 Feb 2012 05:32:47 -0600 Exec:
3
Page loaded in 0.01075 seconds
Current Code Revision: Sun Sep 11 19:52:46 2011 +0000}

Donate

Challenges

Get Informed

Get Involved

Communicate

About HTS

Translate

Partners