Requests for Comment/CVT policy

Since the other Requests for Comment that we have had, the Counter Vandalism Team remains the only main right (global and local) that is vague in terms of policy, and does not mention any inactivity or revocation procedures, making it fully up to Stewards and also making it possible for a CVT member to be inactive for a unlimited amount of time, when one of the main roles of CVT (in my opinion) is to be actively involved in combating vandalism across wikis. Additionally, it is currently not very clear where and how CVT are allowed to intervene and whether some matters should be reserved for Stewards to handle. I am aware that there have been previous RfCs that have gone stale on this topic, but I hope this one will have more comments and discussions.

As usual, users are not limited to vote for one proposal and may vote for multiple proposals as long as they are not mutually exclusive, and are free to add new proposals if they feel like the current ones don't include what they want. Reception123 (talk) ('C' ) 09:26, 16 August 2019 (UTC)

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. —znotch190711 (temporary signature) 04:24, 17 August 2019 (UTC)
 * While I will be completely ignoring this RFC. 49.130.128.224 06:47, 17 August 2019 (UTC)

Proposal 1

 * CVTs should only act in their CVT capacity if:


 * there is vandalism, spam or any type of clear disruption on the wiki and there are no local sysops or bureaucrats acting in a reasonable amount of time
 * the global Special:AbuseLog shows attempted spam that hasn't been dealt with by local sysops or bureaucrats
 * a request to remove spam is made by a member of the local community

In any other case CVTs should not interfere on any wiki in their CVT capacity, and in doubt should leave the matter to a Steward.

a) Support

 * 1)  makes sense, I think the role of CVT should definitely be to concentrate on clear vandalism and leave more complicated matters to Stewards. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  Seems to clear up a lot.  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:12, 16 August 2019 (UTC)

Proposal 2

 * CVT members may not lock users unless they are clearly vandalizing or spamming a wiki. More complicated cases of disruption and not respecting local policies should be left to be dealt with by Stewards.

a) Support

 * 1)  per comment above. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)

b) Oppose
rather it was more than 1 wiki but otherwise okay. 1 wiki can be a normal block. ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:14, 16 August 2019 (UTC)

Proposal 1

 * CVTs are appointed by Stewards following a community discussion and vote held at Requests for global rights. Stewards have discretion in determining their appointment.

b) Oppose

 * 1)  Too vague, and it should be up to a clear community vote, not discretion. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  Too much discretion.  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:15, 16 August 2019 (UTC)

Proposal 2

 * CVTs will be elected by a community vote (on Requests for global rights) where:


 * at least 10 users share their view;
 * there is a support ratio of at least 80%.
 * a period of one week has passed since it started.

a) Support

 * 1)  Half of the number of votes for Stewards is a decent number for CVT. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  Sounds like a good number.  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:15, 16 August 2019 (UTC)

Proposal 3

 * CVTs will be elected by a community vote (on Requests for global rights) where:


 * at least 5 users share their view;
 * there is a support ratio of at least 80%.
 * a period of one week has passed since it started.

b) Oppose

 * 1)  Not enough users must share their view for a to elect a user hat does have quite a few rights across Miraheze. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  a bit low for a group with a lot of rights.  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:16, 16 August 2019 (UTC)

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

Proposal 1 (Revocation)

 * The global 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:


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

a) Support

 * 1)  makes sense. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  per reception  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:17, 16 August 2019 (UTC)

Proposal 2 (Revocation)

 * The global 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:


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

b) Oppose

 * 1)  75% is too much IMO. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  too high  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:17, 16 August 2019 (UTC)

Proposal 3 (Revocation)

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

a) Support

 * 1)  makes sense. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  Needs a reason to stop grudges.  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:18, 16 August 2019 (UTC)

Proposal 4 (Inactivity)

 * CVT members who do not participate in CVT duties in some form (countervandalism, locking abusive users, etc.) for for 1 year will be deemed inactive and have their CVT rights revoked by a Steward.

b) Oppose

 * 1)  One year is too long, as I said in the opening statement the point of a CVT member is to be active. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  too long.  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:19, 16 August 2019 (UTC)

Proposal 5 (Inactivity)

 * CVT members who do not participate in CVT duties in some form (countervandalism, locking abusive users, etc.) for 6 months will be deemed inactive and have their CVT rights revoked by a Steward.

a) Support

 * 1) CVTs should at least have some form of activity in 6 months. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  Good length of time to show activity.  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:20, 16 August 2019 (UTC)

Proposal 6 (Readdition)

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

a) Support

 * 1)  they should be able to show that they will be active again, and that they will benefit the community by having the rights. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  would be nice if they can be community.  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:23, 16 August 2019 (UTC)

Proposal 7 (Readdition)

 * An CVT member 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.

b) Oppose

 * 1)  per comment above. Reception123  (talk) ('C' ) 09:31, 16 August 2019 (UTC)
 * 2)  ^^  ~ RhinosF1 - (chat) · CA · contribs · Rights - ) 15:25, 16 August 2019 (UTC)