CommunityAdministrationNetwork/Server Owners - Revision history

A Meteorite: Misspelled "administration"

2007-11-04T20:41:38Z

Misspelled "administration"

← Older revision		Revision as of 20:41, 4 November 2007
Line 2:		Line 2:

	==Overview==		==Overview==
	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==

A Meteorite: CommunityAdminstrationNetwork/Server Owners moved to CommunityAdministrationNetwork/Server Owners: Misspelled "administration"

2007-11-04T20:34:07Z

CommunityAdminstrationNetwork/Server Owners moved to CommunityAdministrationNetwork/Server Owners: Misspelled "administration"

← Older revision		Revision as of 20:34, 4 November 2007
(No difference)

JeffM2501: /* Endorse Global Authentication */

2007-05-15T21:37:28Z

Endorse Global Authentication

← Older revision		Revision as of 21:37, 15 May 2007
Line 12:		Line 12:

	===Endorse Global Authentication===		===Endorse Global Authentication===
	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.		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===		===Provide a contact name and e-mail===

JeffM2501: /* Require Global Authentication */

2007-05-15T21:36:48Z

Require Global Authentication

← Older revision		Revision as of 21:36, 15 May 2007
Line 11:		Line 11:
	CAN is only for public servers. It is not available for private servers, due to its link with global authentication and web-based services.		CAN is only for public servers. It is not available for private servers, due to its link with global authentication and web-based services.

	===~~Require~~ Global Authentication===		===Endorse Global Authentication===
	Running a CAN server means that the server owner agrees to ~~only allow registered players~~ to ~~spawn and talk~~. ~~This is required and enforced by the~~ CANAdmin plug-in, ~~so it can do its work~~ using ~~BZIDs and does not have~~ to ~~do any form of IP bans~~ or ~~blocks~~.		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.

	===Provide a contact name and e-mail===		===Provide a contact name and e-mail===

71.177.36.120: /* Disputes with Administration actions */

2007-05-10T04:31:56Z

Disputes with Administration actions

← Older revision		Revision as of 04:31, 10 May 2007
Line 35:		Line 35:
	==Disputes with Administration actions==		==Disputes with Administration actions==

	The administration team is more ~~then~~ 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 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.		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.		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.

71.177.36.120: /* Understand the service */

2007-05-10T04:27:46Z

Understand the service

← Older revision		Revision as of 04:27, 10 May 2007
Line 24:		Line 24:

	===Understand the service===		===Understand the service===
	It is important that each server owner understand what services are being offered by the network, ~~and what services are not. 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.		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==		==Actions that will result in membership termination==

71.177.36.120: /* Run a minimum version of the BZFS server */

2007-05-10T04:22:06Z

Run a minimum version of the BZFS server

← Older revision		Revision as of 04:22, 10 May 2007
Line 21:		Line 21:

	===Run a minimum version of the BZFS server===		===Run a minimum version of the BZFS server===
	In order for the CANAdmin plug-in to work, it will require a specific version of BZFS. Server owners that can not build ~~there~~ 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.		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===		===Understand the service===

71.177.36.120: /* Understand the service */

2007-05-10T01:56:27Z

Understand the service

← Older revision		Revision as of 01:56, 10 May 2007
Line 24:		Line 24:

	===Understand the service===		===Understand the service===
	It is important that each server owner understand what services are being offered by the network, and what services are not. 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 ~~there~~ 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.		It is important that each server owner understand what services are being offered by the network, and what services are not. 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==		==Actions that will result in membership termination==

71.177.36.120: /* Provide a valid domain name and port for each server running */

2007-05-10T01:56:08Z

Provide a valid domain name and port for each server running

← Older revision		Revision as of 01:56, 10 May 2007
Line 18:		Line 18:

	===Provide a valid domain name and port for each server running===		===Provide a valid domain name and port for each server running===
	The CAN system needs to know the names and ports of each server that is run in order to verify ~~it's~~ membership in the network.		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===		===Run a minimum version of the BZFS server===

71.177.36.120: /* Require Global Authentication */

2007-05-10T01:55:47Z

Require Global Authentication

← Older revision		Revision as of 01:55, 10 May 2007
Line 12:		Line 12:

	===Require Global Authentication===		===Require Global Authentication===
	Running a CAN server means that the server owner agrees to only allow registered players to spawn and talk. This is required and enforced by the CANAdmin plug-in, so it can do ~~it's~~ work using BZIDs and does not have to do any form of IP bans or blocks.		Running a CAN server means that the server owner agrees to only allow registered players to spawn and talk. This is required and enforced by the CANAdmin plug-in, so it can do its work using BZIDs and does not have to do any form of IP bans or blocks.

	===Provide a contact name and e-mail===		===Provide a contact name and e-mail===