Userpedia:Proposals
From Userpedia
Proposals can be new features (such as an extension), removal of a previously added feature that has tired out, or new policies that must be approved via consensus before any action(s) are done.
|
A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits must be signed.
Rules
- Users then vote on the voting start one day later and discuss on the issue during the 8 days. The "deadline" for the proposal one week after the voting start. at 24:00. (all times GMT)
- Any proposal that has three votes or less at deadline will automatically be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
- Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
- Every vote should have a reason accompanying it.
- At any time a vote may be rejected if at least three active users believe the vote truly has no merit or was cast in bad faith. However, there must be strong reasons supporting the invalidation.
- "# " should be added under the last vote of each support/oppose section to show another blank line.
- All proposals that end up in a tie will be extended for another week.
- All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of a Sysop, the proposer can ask for that help.
- There shouldn't be proposals about creating articles on a underrepresented or completely absent subject, unless there is major disagreement about whether the content should be included.
- If the Sysops deem a proposal unnecessary or potentially detrimental to the upkeep of Userpedia, they have the right to remove it at any time.
Contents |
New Features
None at the moment
Removals
None at the moment.
Splits & Merges
None at the moment.
Changes
Miscellaneous
None at the moment.
