Community Administrator: Difference between revisions
(→Duties: edited to be closer to reality) |
|||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
==Duties== | ==Duties== | ||
Regular duties of the Community Administrator include: | Regular duties of the Community Administrator include: | ||
* | *Adding regular updates supplied by the [[Development Zone Lead]] to [[Allegiance Update]] | ||
*Adding regular updates supplied by the [[Community Core Zone Lead]] to [[Allegiance Update]] | |||
*Enabling the [[Zone Lead]]s to perform their roles | |||
* | |||
* | |||
*Administering the FreeAllegiance.org forums | *Administering the FreeAllegiance.org forums | ||
*Administering the ASGS Database | |||
*Appointing squad officers as directed by each squad's leader | *Appointing squad officers as directed by each squad's leader | ||
*Creating and disbanding squads as they meet/fail to meet the squad requirements | *Creating and disbanding squads as they meet/fail to meet the squad requirements | ||
*Unlinking accounts that have become accidentally | *Unlinking accounts that have become accidentally linked | ||
Performing these tasks takes considerable amount of time. As a result, many are delegated to players designated as [[Zone Lead]]s who are in charge of particular areas. In this way, the work is divided into many small tasks which can be completed in parallel. As an added side benefit, this delegation removes the bottleneck of requiring one man to perform every task allowing the community to act more autonomously. | Performing these tasks takes considerable amount of time. As a result, many are delegated to players designated as [[Zone Lead]]s who are in charge of particular areas. In this way, the work is divided into many small tasks which can be completed in parallel. As an added side benefit, this delegation removes the bottleneck of requiring one man to perform every task allowing the community to act more autonomously. | ||
| Line 20: | Line 17: | ||
The first Community Administrator was Pook, who was also the author of the [[ASGS]] system and Systems Administrator of the ASGS server. On October 13th, 2005 Pook stepped down as Community Administrator and appointed Tigereye in his place, while continuing with his Systems Administrator role until Tigereye was adequately trained. | The first Community Administrator was Pook, who was also the author of the [[ASGS]] system and Systems Administrator of the ASGS server. On October 13th, 2005 Pook stepped down as Community Administrator and appointed Tigereye in his place, while continuing with his Systems Administrator role until Tigereye was adequately trained. | ||
Currently, Tigereye is both the Community Administrator and Systems Administrator | Currently, Tigereye is both the Community Administrator and Systems Administrator. | ||
[[Category: Articles yet to be categorised]] | |||
Latest revision as of 18:10, 2 November 2009
The Community Administrator is the player appointed by the FreeAllegiance Lobby Server owner to ensure smooth operation of the FreeAllegiance community.
Duties
Regular duties of the Community Administrator include:
- Adding regular updates supplied by the Development Zone Lead to Allegiance Update
- Adding regular updates supplied by the Community Core Zone Lead to Allegiance Update
- Enabling the Zone Leads to perform their roles
- Administering the FreeAllegiance.org forums
- Administering the ASGS Database
- Appointing squad officers as directed by each squad's leader
- Creating and disbanding squads as they meet/fail to meet the squad requirements
- Unlinking accounts that have become accidentally linked
Performing these tasks takes considerable amount of time. As a result, many are delegated to players designated as Zone Leads who are in charge of particular areas. In this way, the work is divided into many small tasks which can be completed in parallel. As an added side benefit, this delegation removes the bottleneck of requiring one man to perform every task allowing the community to act more autonomously.
History
The first Community Administrator was Pook, who was also the author of the ASGS system and Systems Administrator of the ASGS server. On October 13th, 2005 Pook stepped down as Community Administrator and appointed Tigereye in his place, while continuing with his Systems Administrator role until Tigereye was adequately trained.
Currently, Tigereye is both the Community Administrator and Systems Administrator.
