Bar and Grill policy - Revision history

RS David: recat

2009-04-09T19:53:14Z

recat

← Older revision		Revision as of 19:53, 9 April 2009
Line 52:		Line 52:
	[[Leonard Cable\|LCable]] 101		[[Leonard Cable\|LCable]] 101

	[[Category:~~Policies~~]]		[[Category:IRC]]

ThePoet444: /* Current access list */

2007-03-19T08:03:48Z

Current access list

← Older revision		Revision as of 08:03, 19 March 2007
Line 37:		Line 37:
	''Note: This list may not be completely up-to-date; please use the [http://cservice.undernet.org/live/ Channel Service website] for the latest list. You may also type '''/msg X ACCESS #RS_Bar_and_Grill *''' to receive this information via IRC.''		''Note: This list may not be completely up-to-date; please use the [http://cservice.undernet.org/live/ Channel Service website] for the latest list. You may also type '''/msg X ACCESS #RS_Bar_and_Grill *''' to receive this information via IRC.''

	~~8 September 2006~~:		19 March 2007:
	[[Shikkie Kaaran\|shikkie]] 500		[[Shikkie Kaaran\|shikkie]] 500
	[[~~Licah Fox~~\|~~LicahFox~~]] 496		[[Dave Trebonious-Astoris\|dave1453]] 496
	~~[[Leonard Cable\|LCable]] 490~~		[[Patrick Blastfire\|Blastfire]] 452
	[[Patrick Blastfire\|Blastfire]] 452		[[Joshua Hawkins\|ThePoet444]] 450
	[[~~Snappleguy~~\|~~SnapGuy~~]] 450		[[David "Heavy" Pasiechnyk\|RSDavid]] 305
	[[~~Indiana Bridger\|Indy]] 314~~		[[Kaz Falcion\|rskaz]] 302
	~~[[Anton Nels\|AntonUPS]] 308~~		[[Michael Raven\|Scorbolt]] 300
	~~[[Joshua Hawkins~~\|~~ThePoet444~~]] ~~306~~		[[Codyman\|Codyman]] 250
	[[Kaz Falcion\|rskaz]] 302		[[Eric Skrevski\|EMW1824]] 210
	[[Michael Raven\|Scorbolt]] 300		[[Richard Gross\|JKRich]] 204
	~~[[Dave Trebonious-Astoris\|dave1453]] 254~~		[[Max Cal\|MCal]] 202
	[[Codyman\|Codyman]] 250		[[Sair\|supersair]] 101
	[[Eric Skrevski\|EMW1824]] 210		[[Leonard Cable\|LCable]] 101
	[[Richard Gross\|JKRich]] 204
	[[Max Cal\|MCal]] 202
	[[Sair\|supersair]] 101

	[[Category:Policies]]		[[Category:Policies]]

Ray Djo: /* Current access list */

2006-10-16T22:11:57Z

Current access list

← Older revision		Revision as of 22:11, 16 October 2006
Line 41:		Line 41:
	[[Licah Fox\|LicahFox]] 496		[[Licah Fox\|LicahFox]] 496
	[[Leonard Cable\|LCable]] 490		[[Leonard Cable\|LCable]] 490
			[[Patrick Blastfire\|Blastfire]] 452
	[[Snappleguy\|SnapGuy]] 450		[[Snappleguy\|SnapGuy]] 450
	[[Indiana Bridger\|Indy]] 314		[[Indiana Bridger\|Indy]] 314

DaLe: fixed link to Anton's wiki article

2006-09-25T20:00:43Z

fixed link to Anton's wiki article

← Older revision		Revision as of 20:00, 25 September 2006
Line 43:		Line 43:
	[[Snappleguy\|SnapGuy]] 450		[[Snappleguy\|SnapGuy]] 450
	[[Indiana Bridger\|Indy]] 314		[[Indiana Bridger\|Indy]] 314
	[[Anton ~~"Ups"~~ Nels\|AntonUPS]] 308		[[Anton Nels\|AntonUPS]] 308
	[[Joshua Hawkins\|ThePoet444]] 306		[[Joshua Hawkins\|ThePoet444]] 306
	[[Kaz Falcion\|rskaz]] 302		[[Kaz Falcion\|rskaz]] 302

Licah Fox: /* General guidelines */

2006-09-09T02:21:16Z

General guidelines

← Older revision		Revision as of 02:21, 9 September 2006
Line 6:		Line 6:

	This policy will not attempt to cover any specific situations, but seeks to provide general guidelines for B&G operators. The following apply:		This policy will not attempt to cover any specific situations, but seeks to provide general guidelines for B&G operators. The following apply:
	* It is most important to act as a responsible operator and carefully follow the progression of consequences when you are dealing with a person you do not know, or know only a little. These people ~~most likely~~ are not very familiar with the B&G and its peculiar environment.		* It is most important to act as a responsible operator and carefully follow the progression of consequences when you are dealing with a person you do not know, or know only a little. These people are not likely to be very familiar with the B&G and its peculiar environment.
	* The more familiar and comfortable that you are with the person in question, the more lax you may be with these rules. Situations known colloquially as "ops abuse" are allowed when the parties involved understand that all is in jest. However, if any party involved requests to be left alone, his or her wishes must be respected.		* The more familiar and comfortable that you are with the person in question, the more lax you may be with these rules. Situations known colloquially as "ops abuse" are allowed when the parties involved understand that all is in jest. However, if any party involved requests to be left alone, his or her wishes must be respected.

Licah Fox: /* Progression of consequences */

2006-09-09T02:14:13Z

Progression of consequences

← Older revision		Revision as of 02:14, 9 September 2006
Line 11:		Line 11:
	=== Progression of consequences ===		=== Progression of consequences ===
	This progression should be followed in all instances except where the offending party is clearly and deliberately trying to antagonize one or more people in the channel. For such problems, the op may proceed to step 4 immediately.		This progression should be followed in all instances except where the offending party is clearly and deliberately trying to antagonize one or more people in the channel. For such problems, the op may proceed to step 4 immediately.

			In almost no instance should an op kick someone without appropriate warning; as a reminder, it is possible to keep someone from talking by banning them, but not kicking them. This allows for time to give them a warning without their continuing the offensive behavior.

	# Notification of channel policy and how the person is breaching it		# Notification of channel policy and how the person is breaching it

Licah Fox at 02:11, 9 September 2006

2006-09-09T02:11:38Z

← Older revision		Revision as of 02:11, 9 September 2006
Line 2:		Line 2:

	== Ops policy ==		== Ops policy ==
			=== General guidelines ===
			The RS Bar and Grill is largely self-run, with most denizens well aware of the various borders that exist and normally not presenting a serious problem that requires operators. However, occasions sometimes arise when rules are breached and need to be maintained.

			This policy will not attempt to cover any specific situations, but seeks to provide general guidelines for B&G operators. The following apply:
			* It is most important to act as a responsible operator and carefully follow the progression of consequences when you are dealing with a person you do not know, or know only a little. These people most likely are not very familiar with the B&G and its peculiar environment.
			* The more familiar and comfortable that you are with the person in question, the more lax you may be with these rules. Situations known colloquially as "ops abuse" are allowed when the parties involved understand that all is in jest. However, if any party involved requests to be left alone, his or her wishes must be respected.

	=== Progression of consequences ===		=== Progression of consequences ===
			This progression should be followed in all instances except where the offending party is clearly and deliberately trying to antagonize one or more people in the channel. For such problems, the op may proceed to step 4 immediately.

	# Notification of channel policy and how the person is breaching it		# Notification of channel policy and how the person is breaching it
	# Warning that continued similar behavior will result in a kick		# Warning that continued similar behavior will result in a kick

Licah Fox: /* Ops policy */

2006-09-09T01:50:54Z

Ops policy

← Older revision		Revision as of 01:50, 9 September 2006
Line 2:		Line 2:

	== Ops policy ==		== Ops policy ==
	~~This section~~ will ~~detail~~ the ~~guidelines that all B&G ops~~ are to ~~follow~~.
			=== Progression of consequences ===
			# Notification of channel policy and how the person is breaching it
			# Warning that continued similar behavior will result in a kick
			# Single kick with a clear reason
			# Ban temporarily (without kicking), warning that continued similar behavior will result in a kickban, unban
			# Kick and ban; kick reason should include the length of the ban. Recommended ban lengths are from 30 minutes to 1 day, with longer bans for each subsequent offense. Bans for longer than 3 days must be approved by the RSFC & RSXO. The maximum ban length is one month.

	== Access policy ==		== Access policy ==

Licah Fox at 20:24, 8 September 2006

2006-09-08T20:24:17Z

New page

This policy concerns the '''[[RS Bar and Grill]]'''.

== Ops policy ==
This section will detail the guidelines that all B&G ops are to follow.

== Access policy ==
* B&G operator status is granted to all qualifying personnel that demonstrate the ability to be an operator.
* No two users will have equal access. In cases of equal positions, such as two Fleet COs, the officer who has served longer in their position will have a higher access level, or else the matter will be resolved at the B&G manager's discretion.
* Access may be revoked temporarily or permanently for repeated failure to observe the Ops Policy.

Access is granted as follows:
* 500: Channel owner (Shik)
* 490-499: RS leaders ([[RSFC]], [[RSXO]])
* 400-489: B&G managers (often members of the [[Internet Office]])
* 300-399: Fleet COs
* 250-299: Aldermen
* 200-249: Fleet XOs
* 100-199: Assistant ops designated by the B&G manager(s)

=== Current access list ===
''Note: This list may not be completely up-to-date; please use the [http://cservice.undernet.org/live/ Channel Service website] for the latest list. You may also type '''/msg X ACCESS #RS_Bar_and_Grill *''' to receive this information via IRC.''

8 September 2006:
[[Shikkie Kaaran|shikkie]] 500
[[Licah Fox|LicahFox]] 496
[[Leonard Cable|LCable]] 490
[[Snappleguy|SnapGuy]] 450
[[Indiana Bridger|Indy]] 314
[[Anton "Ups" Nels|AntonUPS]] 308
[[Joshua Hawkins|ThePoet444]] 306
[[Kaz Falcion|rskaz]] 302
[[Michael Raven|Scorbolt]] 300
[[Dave Trebonious-Astoris|dave1453]] 254
[[Codyman|Codyman]] 250
[[Eric Skrevski|EMW1824]] 210
[[Richard Gross|JKRich]] 204
[[Max Cal|MCal]] 202
[[Sair|supersair]] 101

[[Category:Policies]]