Summary: This thread proposes that policy discussion threads would be posted both on O5 and on the Policy subform on the Wiki, allowing space for users to provide their thoughts on proposals and policy direction.
The Problem: Users feel like they have no input on site policy, and O5 threads routinely exclude them altogether from potential discussions (as well as often limiting the discussion to certain levels of staff, never mind from the userbase). Whilst it sometimes makes sense to ensure a discussion is being held amongst qualified staff members, it is important to note that this policy can appear both elitist and can make staff seem like a group that imposes policy upon users rather than crafts policy from user or site need. Policy creation on site has often been shaped in a strange manner - a forum exists for users to propose their own policies, but is rarely used, whereas there is no formal way for users to provide input on policy proposals that originate from within staff, which is the way the vast majority of policy comes about.
Users need a way to give input on policy as it is being formed. Although informal channels for policy input from users exist, they vary wildly in their utility and accessibility and are often unintentionally restrictive to many users. This proposal intends to provide a formal, accessible, and transparent method for users to air their opinions on specific policy proposals as they come up.
The Solution: Under this proposal, a new category on the mainsite forum would be created - named Staff Policy Discussions - and the requirements for proposing a policy would change to also require the simultaneous posting of an identical thread to this subforum, allowing space for users to air any concerns they may have with the policy, lend their support to its passing, or ask for clarification. Staff members would be asked not to post top-level comments on this thread. O5 policy threads could no longer be limited to any particular substrate of staff, and staff would be encouraged to port user comments from the mainsite thread to the O5 thread that they believe are valuable, insightful, or representative in order to facilitate further discussion on them.
Policy votes would still be held on O5 in the same manner as before - holding userbase-wide votes for every policy proposal would be unfeasible. The happenings on the mainsite policy thread would have no formal effect on the policy outside of that which the proponent decides to include - that is to say, consensus on the user thread would not be required in order to skip holding a voting thread.
For the purposes of this proposal, chat staff without site rank are to be treated as regular users and would be asked to post to the mainsite policy thread.
In order to facilitate this change, Section IIIA of the Site Charter would be modified to the following:
The Discussion Threads section of the Migration and Policy Discussion subforum is the place for staff discussion about possible policy changes. If a thread is posted within that subforum, an identical thread must be posted to the Staff Policy Discussions subforum on the SCP Wiki as a space where users are encouraged to leave any thoughts. The two must be linked to one another.
- Staff are responsible for maintaining an awareness of and remaining up-to-date on discussions about changes to site policy.
- Staff are responsible for contributing to discussions about site policy as they see fit.
- Simultaneously, staff are required to maintain a degree of professionalism and emotional control during policy discussions, which can become heated at times. If necessary, staff may recuse themselves from conversations in order to regain composure.
- 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.
Please leave your thoughts, questions, and concerns.
This discussion will run for one week at which point a vote will be held if there is no consensus on this policy. The discussion is open to staff of all levels, including JS, as well as input from the userbase via PM (users can contact me and I will add their comments to the thread).