The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Should we increase the minimum activity requirements for administrators to an average of 20 edits per year, over a 5 year period?
WormTT(
talk) 19:04, 17 March 2022 (UTC)
Administrators are trusted members of the community and therefore have certain additional tools. However, standards for administrators have risen over the years, and many legacy administrators do not meet the standards we would expect of new administrators. One such expectation is that of activity levels. Ever since 2011, we have removed administrators who are fully inactive for over a year. However, we still have many administrators who fall far below a reasonable level of activity to be considered well versed in the changes in policies and procedures of Wikipedia.
As such, this proposal suggests updating the Procedural removal for inactive administrators, as per below.
Collapsed current text, to be modified |
---|
The following discussion has been closed. Please do not modify it. |
Administrators who have made neither edits nor administrative actions for at least 12 months may be desysopped.[13] This desysopping is reversible in some cases (see #Restoration of adminship) and never considered a reflection on the user's use of, or rights to, the admin tools. The admin must be contacted on their user talk page and via email (if possible) one month before the request for desysopping and again several days before the desysopping goes into effect. Desysopping on inactivity grounds should be handled by English Wikipedia bureaucrats. The summary in the user rights log should make it clear that the desysopping is purely procedural. If necessary, the user's userpage should be edited to clarify the status — particularly if any categorization is involved. |
Administrators who meet one or both of the following criteria may be desysopped for inactivity:
This desysopping is reversible in some cases (see Wikipedia:Administrators#Restoration of adminship) and never considered a reflection on the user's use of, or rights to, the admin tools. The admin must be contacted on their user talk page on two different occasions before the desysopping goes into effect. Desysopping on inactivity grounds should be handled by English Wikipedia bureaucrats. The summary in the user rights log should make it clear that the desysopping is purely procedural.
If necessary, the user's userpage should be edited to clarify the status — particularly if any categorization is involved.
This raises the bar for Administrator activity levels from more than 0 edits in a rolling 12 month period (i.e. 0 edits per year over 1 year) to 100 edits in a rolling 5 year period (i.e. average 20 edits per year over 5 years). This would encourage those admins who participate less in our project to increase their participation to a minimal level, rather than simply encouraging them to make a token edit each year.
Administrators should be given ample opportunity to increase their level of contribution, should this well-publicised RfC be successful it should go into force at a date that the community can get ready for. All administrators should be notified of the change if the RfC is closed successfully. All administrators who will be eligible to be desysopped should be notified of the risk at least twice on their talk page before removal. For those at risk of being desysopped for criterion 1 they will be notified one month prior and several days prior. For those at risk of being desysopped for criterion 2 they will be notified 3 months prior and 1 month prior. In addition, any editors who are falling lower than an average of 50 edits per year over a 5 year period should be notified by talk page message annually that they are at risk of falling below the required level in the future.
These numerical values will also help Bureaucrats in their judgement for "Restoration of adminship", under the "A bureaucrat is not reasonably convinced that the user has returned to activity or intends to return to activity as an editor" requirement. An admin should show that they are unlikely to fall back to inactivity criteria before being resysopped.
A report run on 18 March 2022 has shown that this change will affect 197 administrators, approximately 20% of the group, warning a further 163. It should be noted that these activity requirements should be considered minimal and can be increased in the future. Regarding a stricter alternative with some consideration below (100 a year over a rolling three year period - i.e. 300 edits in the last three years) this would remove 396 administrators and hypothetically warn a subsequent 67.
This is a volunteer project. We all have a perfect right to go away for a while and do other things.This is exactly my point. If some-one chooses to contribute as an admin, great! If they don't choose to do so, that's also great. If they choose to contribute as an admin and then decide later they won't continue to do so, that's also great. It's only "harsh" to ask for the tools back in the latter case because we've somehow come to think of RfA's as judgements on a person's worthiness. It isn't (or shouldn't be) and asking for editors to either use the tools or give them up is basic practicality. In the real world, it's routine for volunteers and professionals alike that they don't continue to have access to systems and sites where they once performed work but no longer do so. Why is this different? Because they might possibly, maybe come back and contribute? If they make that choice, then they can ask for the tools back. There is no bad faith in asking people to not play games with tools just so they can maintain the bit. Eggishorn (talk) (contrib) 16:28, 19 March 2022 (UTC)
valuable admin workmentioned. Aside from being a name on the list, and a potential security risk due to the increased attack surface (inactive users are less likely to be maintaining good password practice), what benefit does a long term inactive admin provide? Sideswipe9th ( talk) 16:59, 19 March 2022 (UTC)
the admin corps doesn't want high turnover because they prefer the current political consensus of editors they get along with. One admin (WTT) proposed this RfC and a second admin (me) proposed an even stricter threshold that has gained some traction. And by my count the admin corp is overwhelmingly supporting this RfC. Best, Barkeep49 ( talk) 18:35, 18 March 2022 (UTC)
los[ing] trusted servants, including less active ones, then why do you favor Barkeep's more? Honestly, WTT's (original) proposal (i.e. the '100 edits within five years' rule) gives admins a couple more years and more chances, if not more forgiving, than Barkeep's ('100 edits within three years' rule). Right? BTW, let's not make too many alternative proposals for now or do the same way NSPORTS RfC was. George Ho ( talk) 21:11, 19 March 2022 (UTC)
if they are that worried that there isn't community consensus for privileges maybe they shouldn't hold them. Bungle ( talk • contribs) 19:28, 21 March 2022 (UTC)
I don't think Barkeep's proposal is necessary at this time; there appears to be a high level of support for the initial proposal, so if it is found to be ineffective, tightening the criteria shouldn't be difficult. -- Sable232 ( talk) 00:52, 24 March 2022 (UTC)
As Dennis Brown suggested above, having a system in place to remove inactive admins through a community discussion might be a better way. I agree with this because (as he said) it requires active involvement from the community. So how about something like this, instead of Worm's proposal?
Collapsed current text, to be modified |
---|
The following discussion has been closed. Please do not modify it. |
Administrators who have made neither edits nor administrative actions for at least 12 months may be desysopped.[13] This desysopping is reversible in some cases (see #Restoration of adminship) and never considered a reflection on the user's use of, or rights to, the admin tools. The admin must be contacted on their user talk page and via email (if possible) one month before the request for desysopping and again several days before the desysopping goes into effect. Desysopping on inactivity grounds should be handled by English Wikipedia bureaucrats. The summary in the user rights log should make it clear that the desysopping is purely procedural. If necessary, the user's userpage should be edited to clarify the status — particularly if any categorization is involved. |
Collapsed proposed text by Worm That Turned |
---|
The following discussion has been closed. Please do not modify it. |
Administrators who meet one or both of the following criteria may be desysopped for inactivity:
This desysopping is reversible in some cases (see Wikipedia:Administrators#Restoration of adminship) and never considered a reflection on the user's use of, or rights to, the admin tools. The admin must be contacted on their user talk page on two different occasions before the desysopping goes into effect. Desysopping on inactivity grounds should be handled by English Wikipedia bureaucrats. The summary in the user rights log should make it clear that the desysopping is purely procedural. |
Administrators who meet one or both of the following criteria may be desysopped for inactivity through a publicized community discussion:
This desysopping for inactivity is not reversible without a new Request for adminship. The admin must be contacted on their user talk page thirty (30) days prior to and at the time the desysopping discussion is begun. The discussion should last for a minimum of seven (7) days. English Wikipedia Bureaucrats should determine the consensus of the desysopping discussion and, if the consensus is to desysop, handle the desysopping on inactivity grounds. The summary in the user rights log should make it clear that the desysopping is purely procedural per a community discussion (with a link to that discussion).
Thoughts? ··· 日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 17:54, 18 March 2022 (UTC)
solution looking for a problem, this is even more so: we have a perfectly good inactivity process, of which the details are occasionally tweaked (such as is happening today). This, on the other hand, would re-write the entire procedure. It's not just an alternate proposal, but an alternate policy. SN54129 18:05, 18 March 2022 (UTC)
I'm not convinced that the apparently desired "uplift" to reflect the strong uplift opinions expressed can be identified through the closing consensus. Maybe 2-3 options now would been a more practical, speedy solutions than tiny increments over seemingly geological time? Leaky caldron ( talk) 13:49, 19 March 2022 (UTC)
If necessary, the user's userpage should be edited to clarify the status — particularly if any categorization is involved.line isn't intended to be removed?
has made less than 100 editsshould be
has made fewer than 100 edits(emphasis added), no?
Jonathunder stats | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The following discussion has been closed. Please do not modify it. | ||||||||||||||
|
RoySmith, It's quite simple to run them, yes - and you'll see that Jonathunder didn't hit either of these criteria either. However, you'll note that nowhere in my rationale, nor in the proposal, do I mention the recent 3 cases we've had at Arbcom - where the big issue was less that the admins were "out of touch" and more that they weren't willing to enter into discussion in a manner we'd hope for. This proposal is unrelated to those cases. WormTT( talk) 14:44, 21 March 2022 (UTC)
In response to some of the more recent comments on trust, I'm repeating a comment I made under a now-collapsed section: My sense from the support statements and past conversations on this topic is that editors generally prefer that those who are enforcing policies be actively part of the community, so that they are invested in the success of their actions. Editing over the last five years is an imperfect measure, but I think it's a reasonable first approximation. The recent responses to some of the requests to reacquire administrative privileges are along these same lines: it's highly recommended to have substantial periods of editing to demonstrate your level of engagement with the project. (As mentioned by others, there are also those who want to reduce the potential attack surface for security purposes.) isaacl ( talk) 15:43, 10 April 2022 (UTC)
jc37's discussion about lack of trust, etc. |
---|
The following discussion has been closed. Please do not modify it. |
Ok, so we have these proposals every so often, and they nibble a bit more and a bit more. But even if we ignore the nonsense of the editcountitis, I just can't get past how this really comes across as ABF ("Assuming bad faith", as opposed to AGF - "Assuming good faith") I have no doubt that for some at least (looks at User:Worm That Turned), this is well-meant. And for others, throwing darts at admins has long been a past time on Wikipedia. And I'm also not surprised at the abundance of meetoo/"sounds good to me" votes above. But here's the thing. At RfA we make a huge deal about how it is about community trust. It's part of why RfA is what it is. Because everyone has their own personal standard of where they draw the line on trusting someone with the tools and responsibility of adminship. And every person to be affected by this proposal passed the community threshhold of trust at the time they were imparted the tools. So now, for no given reason, we are saying we are removing the tools because we don't trust you. We don't trust that you have kept yourself up to date on current policy or process or practice. Well, how the blank do you know? So these admins are guilty until proven innocent? If they haven't been editing - which is the only way we have to tell anything, by a person's edits - how do you know what they have been reading? Sounds like assuming bad faith, to me. Or we don't trust the process of days gone by. Maybe we feel that the levels of trust back then aren't good enough now. To that I ask - then why is this based upon activity? If we are to say that and be neutral about it. then ALL admins from back then should ALL lose the tools and be required to pass a new RfA. To do otherwise invalidates the arguement. Of course, that's presuming that either of these are the real rationales. Reading between the lines (and admittedly, reading these types of proposals over the years have stretched my good faith for some of the commenters' rationales) - a lot of this feels like it's just an excuse to remove the tools from everyone who doesn't have a fanbase, social tribe, or clique. (Another example of "us vs them") Thus making the less-than-active editors easier targets. As I said above, I honestly believe that the proposal is well-meant, but it comes across as VERY un-wiki to me. Oh and to all those arguing that admins are "gaming the system" by doing token edits, I'll put forth 2 things. First, if we trusted them, we wouldn't be requiring it in the first place, and second, isn't this proposal a form of gaming the system to nibble at gettng rid of admins that some see as "undesirable"? I have no doubt that the all-too-common vote counter will come across and close this proposal as "successful", but that doesn't make it right. Adminship has always been about trust, and, always should be. I'm sorry to see the extent of the lack of trust on this page. - jc37 17:04, 21 March 2022 (UTC)
I note that Jc37 has not contributed to mainspace since September 2021, and the last time he did was to edit-war on Justice League, so as far as trusting them with the admin toolset, my gut feeling is "no". Ritchie333 (talk) (cont) 18:01, 22 March 2022 (UTC)
Trust - section break
|
Tangentially, what plans have we for gathering and publishing data on the effects of this proposal, if it passes? From a quick skim, people seem curious about the proposal's effects on legacy admin activity and on admin backlogs. Rotideypoc41352 ( talk · contribs) 02:43, 29 March 2022 (UTC)
Per Wikipedia:Requests for comment#Duration:"An RfC should last until enough comment has been received that consensus is reached, or until it is apparent that it won't be. There is no required minimum or maximum duration...". The result here seems clear enough, and has for some time. Beeblebrox ( talk) 18:44, 5 April 2022 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Should we increase the minimum activity requirements for administrators to an average of 20 edits per year, over a 5 year period?
WormTT(
talk) 19:04, 17 March 2022 (UTC)
Administrators are trusted members of the community and therefore have certain additional tools. However, standards for administrators have risen over the years, and many legacy administrators do not meet the standards we would expect of new administrators. One such expectation is that of activity levels. Ever since 2011, we have removed administrators who are fully inactive for over a year. However, we still have many administrators who fall far below a reasonable level of activity to be considered well versed in the changes in policies and procedures of Wikipedia.
As such, this proposal suggests updating the Procedural removal for inactive administrators, as per below.
Collapsed current text, to be modified |
---|
The following discussion has been closed. Please do not modify it. |
Administrators who have made neither edits nor administrative actions for at least 12 months may be desysopped.[13] This desysopping is reversible in some cases (see #Restoration of adminship) and never considered a reflection on the user's use of, or rights to, the admin tools. The admin must be contacted on their user talk page and via email (if possible) one month before the request for desysopping and again several days before the desysopping goes into effect. Desysopping on inactivity grounds should be handled by English Wikipedia bureaucrats. The summary in the user rights log should make it clear that the desysopping is purely procedural. If necessary, the user's userpage should be edited to clarify the status — particularly if any categorization is involved. |
Administrators who meet one or both of the following criteria may be desysopped for inactivity:
This desysopping is reversible in some cases (see Wikipedia:Administrators#Restoration of adminship) and never considered a reflection on the user's use of, or rights to, the admin tools. The admin must be contacted on their user talk page on two different occasions before the desysopping goes into effect. Desysopping on inactivity grounds should be handled by English Wikipedia bureaucrats. The summary in the user rights log should make it clear that the desysopping is purely procedural.
If necessary, the user's userpage should be edited to clarify the status — particularly if any categorization is involved.
This raises the bar for Administrator activity levels from more than 0 edits in a rolling 12 month period (i.e. 0 edits per year over 1 year) to 100 edits in a rolling 5 year period (i.e. average 20 edits per year over 5 years). This would encourage those admins who participate less in our project to increase their participation to a minimal level, rather than simply encouraging them to make a token edit each year.
Administrators should be given ample opportunity to increase their level of contribution, should this well-publicised RfC be successful it should go into force at a date that the community can get ready for. All administrators should be notified of the change if the RfC is closed successfully. All administrators who will be eligible to be desysopped should be notified of the risk at least twice on their talk page before removal. For those at risk of being desysopped for criterion 1 they will be notified one month prior and several days prior. For those at risk of being desysopped for criterion 2 they will be notified 3 months prior and 1 month prior. In addition, any editors who are falling lower than an average of 50 edits per year over a 5 year period should be notified by talk page message annually that they are at risk of falling below the required level in the future.
These numerical values will also help Bureaucrats in their judgement for "Restoration of adminship", under the "A bureaucrat is not reasonably convinced that the user has returned to activity or intends to return to activity as an editor" requirement. An admin should show that they are unlikely to fall back to inactivity criteria before being resysopped.
A report run on 18 March 2022 has shown that this change will affect 197 administrators, approximately 20% of the group, warning a further 163. It should be noted that these activity requirements should be considered minimal and can be increased in the future. Regarding a stricter alternative with some consideration below (100 a year over a rolling three year period - i.e. 300 edits in the last three years) this would remove 396 administrators and hypothetically warn a subsequent 67.
This is a volunteer project. We all have a perfect right to go away for a while and do other things.This is exactly my point. If some-one chooses to contribute as an admin, great! If they don't choose to do so, that's also great. If they choose to contribute as an admin and then decide later they won't continue to do so, that's also great. It's only "harsh" to ask for the tools back in the latter case because we've somehow come to think of RfA's as judgements on a person's worthiness. It isn't (or shouldn't be) and asking for editors to either use the tools or give them up is basic practicality. In the real world, it's routine for volunteers and professionals alike that they don't continue to have access to systems and sites where they once performed work but no longer do so. Why is this different? Because they might possibly, maybe come back and contribute? If they make that choice, then they can ask for the tools back. There is no bad faith in asking people to not play games with tools just so they can maintain the bit. Eggishorn (talk) (contrib) 16:28, 19 March 2022 (UTC)
valuable admin workmentioned. Aside from being a name on the list, and a potential security risk due to the increased attack surface (inactive users are less likely to be maintaining good password practice), what benefit does a long term inactive admin provide? Sideswipe9th ( talk) 16:59, 19 March 2022 (UTC)
the admin corps doesn't want high turnover because they prefer the current political consensus of editors they get along with. One admin (WTT) proposed this RfC and a second admin (me) proposed an even stricter threshold that has gained some traction. And by my count the admin corp is overwhelmingly supporting this RfC. Best, Barkeep49 ( talk) 18:35, 18 March 2022 (UTC)
los[ing] trusted servants, including less active ones, then why do you favor Barkeep's more? Honestly, WTT's (original) proposal (i.e. the '100 edits within five years' rule) gives admins a couple more years and more chances, if not more forgiving, than Barkeep's ('100 edits within three years' rule). Right? BTW, let's not make too many alternative proposals for now or do the same way NSPORTS RfC was. George Ho ( talk) 21:11, 19 March 2022 (UTC)
if they are that worried that there isn't community consensus for privileges maybe they shouldn't hold them. Bungle ( talk • contribs) 19:28, 21 March 2022 (UTC)
I don't think Barkeep's proposal is necessary at this time; there appears to be a high level of support for the initial proposal, so if it is found to be ineffective, tightening the criteria shouldn't be difficult. -- Sable232 ( talk) 00:52, 24 March 2022 (UTC)
As Dennis Brown suggested above, having a system in place to remove inactive admins through a community discussion might be a better way. I agree with this because (as he said) it requires active involvement from the community. So how about something like this, instead of Worm's proposal?
Collapsed current text, to be modified |
---|
The following discussion has been closed. Please do not modify it. |
Administrators who have made neither edits nor administrative actions for at least 12 months may be desysopped.[13] This desysopping is reversible in some cases (see #Restoration of adminship) and never considered a reflection on the user's use of, or rights to, the admin tools. The admin must be contacted on their user talk page and via email (if possible) one month before the request for desysopping and again several days before the desysopping goes into effect. Desysopping on inactivity grounds should be handled by English Wikipedia bureaucrats. The summary in the user rights log should make it clear that the desysopping is purely procedural. If necessary, the user's userpage should be edited to clarify the status — particularly if any categorization is involved. |
Collapsed proposed text by Worm That Turned |
---|
The following discussion has been closed. Please do not modify it. |
Administrators who meet one or both of the following criteria may be desysopped for inactivity:
This desysopping is reversible in some cases (see Wikipedia:Administrators#Restoration of adminship) and never considered a reflection on the user's use of, or rights to, the admin tools. The admin must be contacted on their user talk page on two different occasions before the desysopping goes into effect. Desysopping on inactivity grounds should be handled by English Wikipedia bureaucrats. The summary in the user rights log should make it clear that the desysopping is purely procedural. |
Administrators who meet one or both of the following criteria may be desysopped for inactivity through a publicized community discussion:
This desysopping for inactivity is not reversible without a new Request for adminship. The admin must be contacted on their user talk page thirty (30) days prior to and at the time the desysopping discussion is begun. The discussion should last for a minimum of seven (7) days. English Wikipedia Bureaucrats should determine the consensus of the desysopping discussion and, if the consensus is to desysop, handle the desysopping on inactivity grounds. The summary in the user rights log should make it clear that the desysopping is purely procedural per a community discussion (with a link to that discussion).
Thoughts? ··· 日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 17:54, 18 March 2022 (UTC)
solution looking for a problem, this is even more so: we have a perfectly good inactivity process, of which the details are occasionally tweaked (such as is happening today). This, on the other hand, would re-write the entire procedure. It's not just an alternate proposal, but an alternate policy. SN54129 18:05, 18 March 2022 (UTC)
I'm not convinced that the apparently desired "uplift" to reflect the strong uplift opinions expressed can be identified through the closing consensus. Maybe 2-3 options now would been a more practical, speedy solutions than tiny increments over seemingly geological time? Leaky caldron ( talk) 13:49, 19 March 2022 (UTC)
If necessary, the user's userpage should be edited to clarify the status — particularly if any categorization is involved.line isn't intended to be removed?
has made less than 100 editsshould be
has made fewer than 100 edits(emphasis added), no?
Jonathunder stats | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The following discussion has been closed. Please do not modify it. | ||||||||||||||
|
RoySmith, It's quite simple to run them, yes - and you'll see that Jonathunder didn't hit either of these criteria either. However, you'll note that nowhere in my rationale, nor in the proposal, do I mention the recent 3 cases we've had at Arbcom - where the big issue was less that the admins were "out of touch" and more that they weren't willing to enter into discussion in a manner we'd hope for. This proposal is unrelated to those cases. WormTT( talk) 14:44, 21 March 2022 (UTC)
In response to some of the more recent comments on trust, I'm repeating a comment I made under a now-collapsed section: My sense from the support statements and past conversations on this topic is that editors generally prefer that those who are enforcing policies be actively part of the community, so that they are invested in the success of their actions. Editing over the last five years is an imperfect measure, but I think it's a reasonable first approximation. The recent responses to some of the requests to reacquire administrative privileges are along these same lines: it's highly recommended to have substantial periods of editing to demonstrate your level of engagement with the project. (As mentioned by others, there are also those who want to reduce the potential attack surface for security purposes.) isaacl ( talk) 15:43, 10 April 2022 (UTC)
jc37's discussion about lack of trust, etc. |
---|
The following discussion has been closed. Please do not modify it. |
Ok, so we have these proposals every so often, and they nibble a bit more and a bit more. But even if we ignore the nonsense of the editcountitis, I just can't get past how this really comes across as ABF ("Assuming bad faith", as opposed to AGF - "Assuming good faith") I have no doubt that for some at least (looks at User:Worm That Turned), this is well-meant. And for others, throwing darts at admins has long been a past time on Wikipedia. And I'm also not surprised at the abundance of meetoo/"sounds good to me" votes above. But here's the thing. At RfA we make a huge deal about how it is about community trust. It's part of why RfA is what it is. Because everyone has their own personal standard of where they draw the line on trusting someone with the tools and responsibility of adminship. And every person to be affected by this proposal passed the community threshhold of trust at the time they were imparted the tools. So now, for no given reason, we are saying we are removing the tools because we don't trust you. We don't trust that you have kept yourself up to date on current policy or process or practice. Well, how the blank do you know? So these admins are guilty until proven innocent? If they haven't been editing - which is the only way we have to tell anything, by a person's edits - how do you know what they have been reading? Sounds like assuming bad faith, to me. Or we don't trust the process of days gone by. Maybe we feel that the levels of trust back then aren't good enough now. To that I ask - then why is this based upon activity? If we are to say that and be neutral about it. then ALL admins from back then should ALL lose the tools and be required to pass a new RfA. To do otherwise invalidates the arguement. Of course, that's presuming that either of these are the real rationales. Reading between the lines (and admittedly, reading these types of proposals over the years have stretched my good faith for some of the commenters' rationales) - a lot of this feels like it's just an excuse to remove the tools from everyone who doesn't have a fanbase, social tribe, or clique. (Another example of "us vs them") Thus making the less-than-active editors easier targets. As I said above, I honestly believe that the proposal is well-meant, but it comes across as VERY un-wiki to me. Oh and to all those arguing that admins are "gaming the system" by doing token edits, I'll put forth 2 things. First, if we trusted them, we wouldn't be requiring it in the first place, and second, isn't this proposal a form of gaming the system to nibble at gettng rid of admins that some see as "undesirable"? I have no doubt that the all-too-common vote counter will come across and close this proposal as "successful", but that doesn't make it right. Adminship has always been about trust, and, always should be. I'm sorry to see the extent of the lack of trust on this page. - jc37 17:04, 21 March 2022 (UTC)
I note that Jc37 has not contributed to mainspace since September 2021, and the last time he did was to edit-war on Justice League, so as far as trusting them with the admin toolset, my gut feeling is "no". Ritchie333 (talk) (cont) 18:01, 22 March 2022 (UTC)
Trust - section break
|
Tangentially, what plans have we for gathering and publishing data on the effects of this proposal, if it passes? From a quick skim, people seem curious about the proposal's effects on legacy admin activity and on admin backlogs. Rotideypoc41352 ( talk · contribs) 02:43, 29 March 2022 (UTC)
Per Wikipedia:Requests for comment#Duration:"An RfC should last until enough comment has been received that consensus is reached, or until it is apparent that it won't be. There is no required minimum or maximum duration...". The result here seems clear enough, and has for some time. Beeblebrox ( talk) 18:44, 5 April 2022 (UTC)