Difference between revisions 1822 and 1823 on testwikidatawiki

{{RFCSubpage}}
I hereby propose to restructure our "minor" user groups a bit and introduce autopromotion to some more user groups other than autoconfirmed.

==Current situation==
*(auto)confirmed: Nonsensical rights
*autopatrolled: autopatrol + patrol + Nonsensical rights
*rollback: rollback + autopatrol + patrol + Nonsensical rights
*propertycreator: property-creation (o.ä.) + autopatrol + patrol + Nonsensical rights⏎
⏎
== Defining account age and number of edits which are required for autopromotion to autopatroller/rollbacker ==

Currently, all users with 50 or more edits get '''autoconfirmed''' and the user rights '''autopatrolled''' and '''rollback''' are handed out manually to non-vandals by admins. As every user with more than 50 edits is already trusted here not to be a vandal, I feel both the autopatrolled and the rollback right could be assigned withby autopromotion as well. This would mean that admins still keep control over these user rights but the software automatically promotes users who have shown with their edits that they can be trusted to have their edits patrolled. The ability for admins to manually remove these rights or assign them before the number of edits defined in this RFC is reached remains.

=== 100 edits + at least 60 days old account ===

===Autopromotion to autopatrolled===
==== Users who have 100 edits + at least 60 days old account should get autopromoted to autopatrolled ====

====  Users who have who have 500 edits + at least 60 days old account ====

=== 100 edits + at least 60 days old account (autopatrolled only) ===

=== 500 edits + at least 60 days old account (rollbacker only) ===

=== No autopromotion (autopatrolled)= No, autopromotion to autopatrolled is teh evil ====

===Autopromotion to rollbacker===
=== Users who have 100 edits + at least 60 days old account should get autopromoted to rollbacker ===

=== Users who have 500 edits + at least 60 days old account should get autopromoted to rollbacker ===

=== No, autopromotion (to rollbacker) ===

=== No autopromotion at al is teh evil ===

== Removal of the confirmed user group ==

As hHardly any manually confirmed user is not autopatrolled at the same time and all autopatrolled users are automatically "confirmed" since [https://gerrit.wikimedia.org/r/#/c/88694/4/wmf-config/InitialiseSettings.php,unified this change], I furthermore propose to remove the now redundant user group "confirmed user" completely.

=== Support ===

=== Oppose ===

== Merge autopatrolled and rollbacker user group ==

If the proposal for autopromotion above passes and the same number of edits for autopromotion to autopatrolled is required as for autopromotion to rollbacker, it would be senseful to merge them and remove one of the groups completely. Currently, all rollbackers are already autopatrolleduser who gets manually confirmed is not given autopatrolled as well by the sysop at fault. As the rights of the autopatrolled group now also contain the (auto)confirmed rights (see [https://gerrit.wikimedia.org/r/#/c/88694/4/wmf-config/InitialiseSettings.php,unified this change]), I furthermore propose to remove the now redundant user group "confirmed user" completely.

=== Support ===

=== Oppose ===

== Merge autopatrolled and rollbacker user group ==

If the proposal above to introduce autopromotion for both autopatrolled and rollback passes, and if the requirements for both groups will be the same, it would make sense to merge them. The only difference between the groups is that rollbackers also have the rollback right, all other rights (autopatrol, patrol, confirmed stuff) are included in both. My proposal is hence to remove the rollback group, and to give the rollback right to autopatrollers, if the above case happens.

=== Support ===

=== Oppose ===