From LSWiki

Revision as of 12:57, 27 April 2007 (edit) Chaos (Talk | contribs) (→write_web) ← Previous diff		Current revision (05:00, 21 October 2009) (edit) Megnmax (Talk | contribs)
Line 22:		Line 22:
	===write_web===		===write_web===
-	Write access to /txt/web, and basic administrative access via the web site interface.	+	Write access to /txt/web, and basic administrative access via the Web site interface.
-	===unused_priv===	+	===restricted_content===
-	A presently not-in-use privilege flag. (Used to be a privilege that no longer has meaning under the current architecture.)	+	A read access flag used for content which needs to be restricted more heavily than read_sensitive.
	===read_d===		===read_d===
Line 58:		Line 58:
	===game_security===		===game_security===
-	Special privileging with respect to system security. Designates possessor as a lead developer.	+	Special privileging with respect to system security. Designates possessor as a lead developer. Includes superuser access to the Web site interface.
	===player_manipulation===		===player_manipulation===
-	Permission to perform actions with effects on players, such as 'heal' and 'perform zap'.	+	Permission to perform actions with effects on players, such as 'heal' and '[[perform zap]]'.
	===read_private===		===read_private===

---

Current revision

Contents 1 Privileges 1.1 Privilege List 1.1.1 guest 1.1.2 read 1.1.3 standard 1.1.4 read_w 1.1.5 write_w 1.1.6 write_web 1.1.7 restricted_content 1.1.8 read_d 1.1.9 write_d 1.1.10 read_lib 1.1.11 write_lib 1.1.12 read_secure 1.1.13 write_secure 1.1.14 documentation 1.1.15 game_messages 1.1.16 game_control 1.1.17 game_access 1.1.18 game_security 1.1.19 player_manipulation 1.1.20 read_private 1.1.21 write_private 1.1.22 player_files 1.1.23 promote 1.1.24 grant_access 1.1.25 qc_language 1.1.26 qc_code 1.1.27 qc_balance 1.1.28 qc_theme 1.1.29 inactive 1.1.30 read_sensitive 1.1.31 write_sensitive 1.1.32 save_files 1.2 Starting Privileges

Privileges

Privileges determine the administrative rights that a developer has. Newly promoted developers start with a basic set of privileges, and are assigned more based on two main factors: 1) their demonstration of trustworthiness, and 2) the access level they need in order to pursue the work they are doing.

Privilege List

The full list of privileges follows. Many privileges are closely related to the directory structure. Some privileges correspond to very general "ranking tiers" of developers; these are, in ascending order: developer, veteran developer, senior developer, elder developer, lead developer.

guest

A generally unused privilege, intended for cases where we might want to remove most privileges from a character but grant it a small "guest" level of access.

read

Basic read privileges appropriate to new developers.

standard

Basic read and write privileges appropriate to new developers, including the ability to write one's own /w directory.

read_w

General read access to the /w directory.

write_w

General write access to the /w directory.

write_web

Write access to /txt/web, and basic administrative access via the Web site interface.

restricted_content

A read access flag used for content which needs to be restricted more heavily than read_sensitive.

read_d

General read access to the /d directory.

write_d

General write access to the /d directory.

read_lib

General read access to the lib.

write_lib

General write access to the lib. Designates possessor as a senior developer.

read_secure

Read access to secure files.

write_secure

Write access to secure files. Designates possessor as an elder developer.

documentation

Write access to documentation files.

game_messages

Permission to cause players to see arbitrary text at will.

game_control

Permission to start and stop driver shutdowns.

game_access

Permission to incarnate as non-developer, non-test-character incarnoi.

game_security

Special privileging with respect to system security. Designates possessor as a lead developer. Includes superuser access to the Web site interface.

player_manipulation

Permission to perform actions with effects on players, such as 'heal' and 'perform zap'.

read_private

Read access to /w/<name>/p directories and other private files.

write_private

Write access to /w/<name>/p directories and other private files.

player_files

General read/write access to /usr directory.

promote

Permission to promote players to developers.

grant_access

Permission to add and remove privileges to and from developers.

qc_language

Permission to sign off for quality control on a project with respect to language issues.

qc_code

Permission to sign off for quality control on a project with respect to code issues.

qc_balance

Permission to sign off for quality control on a project with respect to balance issues.

qc_theme

Permission to sign off for quality control on a project with respect to theme issues. Implies general authority to determine what sort of content the world will contain.

inactive

A special privilege that, if present, disables most other privileges.

read_sensitive

Read permission for directories with "sensitive" content, e.g. /d/Affiliations. Designates possessor as a veteran developer.

write_sensitive

Write permission for directories with "sensitive" content, e.g. /d/Affiliations.

save_files

Write permission for ~Project/dat directories; mainly exists to allow /d content to write to these without privileging it more highly.

Starting Privileges

New developers currently start with the privileges read, standard, read_w, read_d, read_lib, and game_access.