This is a policy proposal for how policies will be planned, executed, implemented, and enforced. This will affect all teams, and thus junior staff and above from all teams may comment. This policy is split into two parts: A restructuring of how existing policies are organized, and a restructuring on how new policies come about. The motivation of this policy is that, currently, we have several disparate and outdated policies as drop-down menu in the top bar, and there is no policy in place to make sure new policies are kept in an organized fashion. This results in policies being lost, partially enforced, or forgotten.
Restructuring of Existing Policy
For existing policy, I would like to refer to our existing Staff Guides and Policies in the top bar. This will be reorganized into a tree structure. The directory page will contain a link to each staff policy, and this directory will be on the front page. This will be in coordination with the recently voted upon (but not concluded) active/inactive thread discussion. If the linked policy is not enacted before this restructuring, it will be on the top of the front page and the rest of the front page left alone.
The directory will look like this: http://scpsandbox2.wikidot.com/soulless-and-his-personal-projects-mk-ii
The purpose of this directory is that we have a single place that can be linked on the front page to look at, boldly, which refers to all other guides. (I know several guides are outdated; they can be updated over time.)
Benefits:
- A single guide directory with all related teams, and also purposes of each guide page
- Eliminates 2 pages: Staff Policy Hub and Team Policies Hub
- An easy reference that can be added to and taken from as necessary
Cons:
- A single guide hub with all related teams, which can become cramped as more policies are added
- A single table for all team-related guides, which may become/is already cramped
Suggested corollary changes:
- The single table for all team-related guides can be replaced, put in a discussion for the next admin-captain meeting
- Future consolidation of several guides to limit overlap
Restructuring New Policy Implementation:
This is a suggestion for new policies and will update the site charter's tab on Policy Issues. The following changes will take place:
F. Execution & Enforcement. (Adding a new section)
1. Upon successful voting, all parties responsible for the policy are also responsible for its implementation.
2. Staff-specific policies that are not on any guide on the Staff Policy Directory are not considered enforceable. If an existing policy is missing, an Administrator may use their Admin Fiat to implement the missing policy.
3. Any guide on the Staff Policy Directory that is edited must be accompanied with a post on the Staff Policy Directory discussion page; this post must contain a brief summary of the change (Motivation, Solution, Pro/Con) as well as Voting and Discussion thread links.
5. Policy changes to on-site guides (e.g. site rules, guide to newbies, etc) requires a brief summary of the change (Motivation, Solution) to be posted onto that guide's discussion page.
A. Policy Discussion. (Editing current section to add a line)
5. A policy proposal must include information on exact amendments to be made, which guides are to be edited, and a list of people responsible for its implementation.
Pros:
- This will put an enforceable policy in place for the enforcement of policies.
- This will make the guides actually important for functioning, as now policies not included will be illegitimate.
Cons:
- This adds rigidity
- If any existing policies are not covered right now, they will need to be Admin Fiated in
- Abuse of Admin Fiat to add in policies exists, although I believe this would be grounds for immediate removal from administrative position
Suggested corollary changes:
- The Staff Policy Directory is posted on the front page, with a big sign indicating that policies not in this directory are not official and need to be put in ASAP
- A "policy outline" can be suggested for staff to fill out in the future, so as to make policy suggestions easy as possible (Motivation, Solution, Pro/Con, Implementation, Enforcement, Optional FAQ?)
Living the dream, or dreaming the life?
