With the vote for a temporary pause on policy having passed, we need to get moving on the actual meat of the issue: Rewriting/overhauling the charter. The following is meant as a skeleton for our (Admins) proposed process for this, created in combination by moose, Conwell, Bleep, Yossi, WhiteGuard, Zyn, and Dexanote.
1) Assessment: Where is the best place for staff to start Charter Overhaul. A few important topics that must be included somewhere in the Charter rewrite process:
- Screen and identify our current starting set of policy. [Currently in process via MAST]
- Staff definition and purview list/responsibility boundaries.
- Staff Hierarchy and Level Definitions
- Pain Points: Admin (Where does the admin role create difficulty for the site/what are the difficult parts of the admin role.)
- Pain Points: General Staff (Where does general staff create difficulty for the site/what are the difficult parts of general staff roles.)
- Pain Points: Community (Where does the community create difficulty for the site/what are the difficult parts of being a community member.)
2) Breakdown: Where can the charter be broken down into smaller bites? This shouldn’t be a difficult part of the process but is very important. How should the Charter be presented, section by section, for clarity and completeness?
Steps:
- Requirements for our use, versus the requirements for the document’s structure.
- Blockers (What is going to get in the way?)
- Charter inclusion vs Sub-document - Would a segment of information work best as a direct part of the Charter, or as a connected sub-document?
3) Review: How well will this all come together, per each section? A set of guidelines for authors to consider throughout their discussions and rewriting process. Each section being broken down should be analyzed through this lens.
- Accountability? Useful Accountability?
- What possible harm can come from this section? How can it be mitigated?
- Longevity? Will the SCP Wiki Staff of 2032 be doing this exact same thing? How often should Staff be reviewing the charter for updates?
- User Friendly? Will staff actually be willing to run through these processes? Is the information presented in a manner that future staff can understand the intended use?
- Assignment Mechanism? How will this section be assigned to people? What kind of expertise or insight should be prioritized? What happens when they fail to do this work?
- How does the user base interface with this? How can they assure accountability?
What is to follow is a discussion, here on O5, for your recommendations for the process, and additions as well as any comments or concerns regarding the above. This would also be a good place to mention if you are interested in helping with a particular step.
Discussion is open for one week to all staff, as MAST works on assembling our current set of policies.
EDIT: Discussion has shifted to the following thread, with additional clarification: https://scp-wiki.wikidot.com/forum/t-14580539/discussion-charter-overhaul-skeleton-ii:electric-boogaloo
O5 Mirror: http://05command.wikidot.com/forum/t-14576416/discussion-charter-overhaul-skeleton
