Difference between revisions of "CommunityAdministrationNetwork/Server Owners"

From BZFlagWiki
Jump to: navigation, search
(Misspelled "administration")
Line 2: Line 2:
This page describes the information needed by server owners who are part of the [[CommunityAdminstrationNetwork/About|Community Administration Network]].
This page describes the information needed by server owners who are part of the [[CommunityAdministrationNetwork/About|Community Administration Network]].
==Membership Requirements==
==Membership Requirements==

Latest revision as of 20:41, 4 November 2007

CAN logo.png This page contains information about an idea called the Community Administration Network Project. It does not represent any rules, opinions, or regulations for the BZFlag project. The C.A.N. was an idea whose author has lost interest. The information is left here for others to use if they wish to take up similar projects.



This page describes the information needed by server owners who are part of the Community Administration Network.

Membership Requirements[edit]

Membership as a CAN server is rather simple, and requires the server owner to agree to a few small things, and install a single plug-in.

Publicly List[edit]

CAN is only for public servers. It is not available for private servers, due to its link with global authentication and web-based services.

Endorse Global Authentication[edit]

Running a CAN server means that the server owner agrees to use the global registration system. The CANAdmin plug-in will notify unregistered users that they should register, and provide a URL with instructions on how to register. The CANAdmin plug-in will also disallow any unregistered user, using a registered callsign to spawn, or be on the server for more then 5 min. Server owners should also have and use a global username.

Provide a contact name and e-mail[edit]

The CAN system needs a contact name and e-mail for each server or group of servers that it runs. This is so that the administration staff can contact the server owners if need be, and for the CAN website to send automatically generated usage/action logs every week. Servers with invalid contact information will be removed from the network.

Provide a valid domain name and port for each server running[edit]

The CAN system needs to know the names and ports of each server that is run in order to verify its membership in the network.

Run a minimum version of the BZFS server[edit]

In order for the CANAdmin plug-in to work, it will require a specific version of BZFS. Server owners that can not build their own BZFS simply need to ask, and the network staff can work with you to get a version that is compatible with the required server.

Understand the service[edit]

It is important that each server owner understand what services are and are not being offered by the network, as well as understanding what responsibilities do and don't come with network membership. Being a CAN member server does not automatically confer any network administration status or abilities to the server owner. While many server owners would make fine field agents or core administrators and may be asked to participate in the network in those positions, they will not be judged for those positions solely on their ownership of a server. Field Agent positions have their own set of criteria for membership and they will be chosen for those alone. Server owners do not lose any local administration ability by becoming a CAN member server.

Actions that will result in membership termination[edit]

There is a small number of actions that will result in the termination of the membership agreement with a server.

Modification of the CANAdmin plug-in[edit]

A server owner should never need to modify the plug-in, or change it in any way. Use of a modified plug-in can result in the removal of a server from the network. If a server owner requires additional features from the plug-in, they should contact the administration staff, so the features can be worked into the base plug-in code.

Disputes with Administration actions[edit]

The administration team is more than happy to work with server owners to resolve any issues or disputes that they may have with the actions of its agents. Accountability of agent actions is a primary goal of the network. If a server owner has any issue with an action, it is best that they talk to the administration team about it as soon as possible. Issues such as a "rogue agent" or a misplaced ban are taken very seriously by the network and the admin staff will do its best to have it resolved as soon as possible. If need be, the core administrators can "undo" all the actions of specific agents.

The administration staff asks that server owners not block access to the server for any of its agents except in the worst of circumstances, and that it not override the actions of the administration staff, as it will prevent the network from doing what has been agreed upon. If a server owner feels they must take actions such as these, the admin staff highly recommends opening a dialog as soon as possible.

Server owners are free to unload or remove the CANAdmin plug-in at any time to leave the network at their own discretion. The Core Administrators and the Network Administrator reserve the right to remove any server from the CAN network at any time, with notification.