Requests for Comment/CVT changes

I propose a change to the CVT group since Miraheze is getting bigger, and also, making some wikis not opted out from CVT.

Discussion
Me, myself, think that CVT groups are way too manipulating. Therefore we need to set more rules (e.g. eligibility criteria, inactivity criteria, appointment criteria, etc) in order to make Miraheze's CVT group become better.

I agree with Spike that eligibility criteria should not contain the number of edits, but CVT members should have at least one eligibility criteria to ensure that the candidate is active.

Proposal 1

 * The rules for CVT remain the same as they are.

Proposal 2

 * A CVT may not be appointed or voted unless they are a wiki creator.

Proposal 1 (500 globally)

 * A candidate must have at least 500 global edits.

Proposal 2 (1000 globally)

 * A candidate must have at least 1000 global edits.

Proposal 3 (2000 globally)

 * A candidate must have at least 2000 global edits.

Proposal 4 (500 globally, 100 on meta)

 * A candidate must have at least 500 global edits and at least 100 edits on meta.

Proposal 5 (1000 globally, 100 on meta)

 * A candidate must have at least 1000 global edits and at least 100 edits on meta.

Proposal 6 (2000 globally, 200 on meta)

 * A candidate must have at least 2000 global edits and at least 200 edits on meta.

Proposal 1 (1 month)

 * A candidate must be at least 1 month old since registered.

Proposal 2 (2 months)

 * A candidate must be at least 2 months old since registered.

Proposal 3 (3 months)

 * A candidate must be at least 3 months old since registered.

Proposal 4 (6 months)

 * A candidate must be at least 6 months old since registered.

Proposal 5 (1 year)

 * A candidate must be at least 1 year (12 months) old since registered.

Proposal 1 (not required)

 * No local/global permission is required to run as a candidate.

Proposal 2 (admin on 1+ wiki(s))

 * A candidate must have an administrator permission in at least 1 wiki.

Proposal 3 (admin on 2+ wikis)

 * A candidate must have an administrator permission in at least 2 wikis.

Proposal 4 (admin on 3+ wikis)

 * A candidate must have an administrator permission in at least 3 wikis.

Proposal 1
The rules for the appointment remain the same as they are.

Proposal 2
Voters who elect a CVT must be autoconfirmed.

Proposal 3
Voters who elect a CVT must be logged in.

Proposal 4
Voters who elect a steward must have more than 10 edits in at least one of the wikis on Miraheze (by the time when the voting begins).

Proposal 5
Voters who elect a CVT must be registered for at least 7 days by the time the voting begins.

Proposal 6
Voters who elect a CVT must be registered for at least 14 days by the time the voting begins.

Proposal 7
Voters who elect a CVT must be registered for at least 1 month by the time the voting begins.

Proposal 1
The rules for an election to be successful remain the same as they are.

Proposal 2
CVT will be elected by a community vote where:
 * at least 10 users share their view;
 * there is a support ratio of at least 80%.

Proposal 3
CVT will be elected by a community vote where:
 * at least 10 users share their view;
 * there is a support ratio of at least 70%.

Proposal 4
CVT will be elected by a community vote where:
 * at least 20 users share their view;
 * there is a support ratio of at least 70%.

Proposal 5
CVT will be elected by a community vote where:
 * At least 5 users share their view;
 * There is a support ration of at least 80%.

Proposal 6
CVT will be elected by a community vote where:
 * At least 5 users share their view:
 * there is a support ratio of at least 70%.

Removal of rights
(Note: There can be multiple ways to revoke, so proposals are not mutually exclusive and can work together)

Proposal 1 (Revocation)

 * The Meta community can initiate a vote of no confidence or a request of removal at any time. In order for it to pass it needs to:


 * receives at least the minimum number of votes needed for appointing;
 * have 50% or more support for removal of rights

Proposal 2 (Revocation)

 * The Meta community can initiate a vote of no confidence or a request of removal at any time. In order for it to pass it needs to:


 * receives at least the minimum number of votes needed for appointing;
 * have 75% or more support for removal of rights

Proposal 3 (Revocation)

 * A vote of no confidence or request for removal must include a reason for why users are requesting that a administrator be removed, and is not determined solely by the number of votes.

Proposal 4 (Inactivity)

 * CVT who do not participate in the community in some form (responding to questions, dealing with issues, administrative tasks on Meta as a minimum) for 1 year will be deemed inactive and have their administrator rights revoked by a bureaucrat.

Proposal 5 (Inactivity)

 * CVT who do not participate in the community in some form (responding to questions, dealing with issues, administrative tasks on Meta as a minimum) for 6 months will be deemed inactive and have their administrator rights revoked by a bureaucrat.

Proposal 6 (Readdition)

 * Once a CVT has their rights revoked for any reason, they must make a successful request satisfy the agreed criteria above in order to regain the rights.

Proposal 7 (Readdition)

 * CVT can be given the rights back if there are no issues raised by the community in a period of 24 hours and if they were not previously revoked per a vote of no confidence.

Proposal 1

 * Nothing is changing.

Proposal 2

 * CVT members can no longer protect or unprotect pages on wikis and delete and undelete pages on wikis (CVT members are no longer "global sysops"). Instead, the right will be transferred to a new user group known as global sysops.

Proposal 3

 * Implement proposal 3 but add a thing: CVT members will be added to the globalsysop rights if the member has a need for it and is active enough (ask on SN).

Proposal 1

 * Wikis that are not Miraheze Management Wikis (e.g. weather.miraheze.org is opted out from CVT) cannot be opted out from CVT unless Stewards and Staff hold a community meeting (not on IRC, but face-to-face) with the wiki founder to discuss, after discussion the whole Meta community will participate in a press release (Spike is the PR Manager) and a large vote will be submitted on this wiki to agree yes/no on the request to opt out from CVT.