Privileges
From LSWiki
Revision as of 07:28, 16 January 2007 (edit) Chaos (Talk | contribs) (→read_sensitive) ← Previous diff |
Revision as of 07:31, 16 January 2007 (edit) Chaos (Talk | contribs) Next diff → |
||
Line 3: | Line 3: | ||
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. | 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 [[Lost Souls directory structure|directory structure]]. Some privileges correspond to very general "ranking tiers" of developers; these are, in ascending order: developer, veteran developer, senior developer, elder developer, archon. | The full list of privileges follows. Many privileges are closely related to the [[Lost Souls directory structure|directory structure]]. Some privileges correspond to very general "ranking tiers" of developers; these are, in ascending order: developer, veteran developer, senior developer, elder developer, archon. | ||
- | ==guest== | + | ===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. | 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== | + | ===read=== |
Basic read privileges appropriate to new developers. | Basic read privileges appropriate to new developers. | ||
- | ==standard== | + | ===standard=== |
Basic read and write privileges appropriate to new developers, including the ability to write one's own /w directory. | Basic read and write privileges appropriate to new developers, including the ability to write one's own /w directory. | ||
- | ==read_w== | + | ===read_w=== |
General read access to the /w directory. | General read access to the /w directory. | ||
- | ==write_w== | + | ===write_w=== |
General write access to the /w directory. | General write access to the /w directory. | ||
- | ==write_web== | + | ===write_web=== |
Write access to /txt/web. | Write access to /txt/web. | ||
- | ==unused_priv== | + | ===unused_priv=== |
A presently not-in-use privilege flag. (Used to be a privilege that no longer has meaning under the current architecture.) | A presently not-in-use privilege flag. (Used to be a privilege that no longer has meaning under the current architecture.) | ||
- | ==read_d== | + | ===read_d=== |
General read access to the /d directory. | General read access to the /d directory. | ||
- | ==write_d== | + | ===write_d=== |
General write access to the /d directory. | General write access to the /d directory. | ||
- | ==read_lib== | + | ===read_lib=== |
General read access to the lib. | General read access to the lib. | ||
- | ==write_lib== | + | ===write_lib=== |
General write access to the lib. Designates possessor as a senior developer. | General write access to the lib. Designates possessor as a senior developer. | ||
- | ==read_secure== | + | ===read_secure=== |
Read access to secure files. | Read access to secure files. | ||
- | ==write_secure== | + | ===write_secure=== |
Write access to secure files. Designates possessor as an elder developer. | Write access to secure files. Designates possessor as an elder developer. | ||
- | ==documentation== | + | ===documentation=== |
Write access to documentation files. | Write access to documentation files. | ||
- | ==game_messages== | + | ===game_messages=== |
Permission to cause players to see arbitrary text at will. | Permission to cause players to see arbitrary text at will. | ||
- | ==game_control== | + | ===game_control=== |
Permission to start and stop driver shutdowns. | Permission to start and stop driver shutdowns. | ||
- | ==game_access== | + | ===game_access=== |
Permission to incarnate as non-developer, non-test-character incarnoi. | Permission to incarnate as non-developer, non-test-character incarnoi. | ||
- | ==game_security== | + | ===game_security=== |
Special privileging with respect to system security. Designates possessor as an archon. | Special privileging with respect to system security. Designates possessor as an archon. | ||
- | ==player_manipulation== | + | ===player_manipulation=== |
Permission to perform actions with effects on players, such as the 'heal' and 'perform zap'. | Permission to perform actions with effects on players, such as the 'heal' and 'perform zap'. | ||
- | ==read_private== | + | ===read_private=== |
Read access to /w/<name>/p directories and other private files. | Read access to /w/<name>/p directories and other private files. | ||
- | ==write_private== | + | ===write_private=== |
Write access to /w/<name>/p directories and other private files. | Write access to /w/<name>/p directories and other private files. | ||
- | ==player_files== | + | ===player_files=== |
General read/write access to /usr directory. | General read/write access to /usr directory. | ||
- | ==promote== | + | ===promote=== |
Permission to promote players to developers. | Permission to promote players to developers. | ||
- | ==grant_access== | + | ===grant_access=== |
Permission to add and remove privileges to and from developers. | Permission to add and remove privileges to and from developers. | ||
- | ==qc_language== | + | ===qc_language=== |
Permission to sign off for quality control on a project with respect to language issues. | Permission to sign off for quality control on a project with respect to language issues. | ||
- | ==qc_code== | + | ===qc_code=== |
Permission to sign off for quality control on a project with respect to code issues. | Permission to sign off for quality control on a project with respect to code issues. | ||
- | ==qc_balance== | + | ===qc_balance=== |
Permission to sign off for quality control on a project with respect to balance issues. | Permission to sign off for quality control on a project with respect to balance issues. | ||
- | ==qc_theme== | + | ===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. | 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== | + | ===inactive=== |
A special privilege that, if present, disables most other privileges. | A special privilege that, if present, disables most other privileges. | ||
- | ==read_sensitive== | + | ===read_sensitive=== |
Read permission for directories with "sensitive" content, e.g. /d/Affiliations. Designates possessor as a veteran developer. | Read permission for directories with "sensitive" content, e.g. /d/Affiliations. Designates possessor as a veteran developer. | ||
- | ==write_sensitive== | + | ===write_sensitive=== |
Write permission for directories with "sensitive" content, e.g. /d/Affiliations. | Write permission for directories with "sensitive" content, e.g. /d/Affiliations. | ||
- | ==save_files== | + | ===save_files=== |
Write permission for ~Project/dat directories; mainly exists to allow /d content to write to these without privileging it more highly. | Write permission for ~Project/dat directories; mainly exists to allow /d content to write to these without privileging it more highly. | ||
+ | |||
+ | ==Starting Privileges== | ||
+ | |||
+ | New developer start with the privileges [[privileges#read|read]] |
Revision as of 07:31, 16 January 2007
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, archon.
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.
unused_priv
A presently not-in-use privilege flag. (Used to be a privilege that no longer has meaning under the current architecture.)
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 an archon.
player_manipulation
Permission to perform actions with effects on players, such as the '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 developer start with the privileges read