Revision as of 06:45, 26 January 2015 view source9cfilorux (talk | contribs)Extended confirmed users, Pending changes reviewers11,027 edits →Let's get real about rollback: re huggle etc← Previous edit | Latest revision as of 08:36, 30 December 2024 view source Primefac (talk | contribs)Edit filter managers, Autopatrolled, Bureaucrats, Checkusers, Oversighters, Administrators208,903 edits →How can I request permission again if I already met the requirements: just noting | ||
Line 1: | Line 1: | ||
{{pp-vandalism|small=yes}} | |||
{{shortcut|WT:PERM|WT:RFPERM|WT:RPE}} | |||
{{Talkheader}} | {{Talkheader|WT:PERM|WT:RFPERM}} | ||
{{User:MiszaBot/config | |||
{{WikiProject Misplaced Pages|class=Template|importance=NA}} | |||
|algo=old(90d) | |||
{{Archive basics | |||
|archive = Misplaced Pages talk:Requests for permissions/Archive %(counter)d | |archive = Misplaced Pages talk:Requests for permissions/Archive %(counter)d | ||
|counter = |
|counter = 11 | ||
|maxarchivesize = 150K | |||
}}<!-- Technical 13 added ] --> | |||
|archiveheader = {{tan}} | |||
{{User:ClueBot III/ArchiveThis | |||
|minthreadsleft=5 | |||
|archiveprefix=Misplaced Pages talk:Requests for permissions/Archive | |||
|minthreadstoarchive=2 | |||
|format= %%i | |||
}} | |||
|numberstart=2 | |||
__TOC__ | |||
|maxarchsize=100000 | |||
|age=1488 | |||
|index=no | |||
}}{{-}} | |||
== Private requests for permissions == | |||
== Temporary grant to Stuartyeates and Giantflightlessbirds for GLAM workshop == | |||
{{archive top}} | |||
These should be OK, reviewing your accounts now. {{U|Stuartyeates}} please verify if from 2014-11-21 through 2014-11-28 is sufficient for these needs? Also, the '''interface''' is available all the time at ]; having account creator allows you to bypass certain safeguards and throttles, notably the 6 accounts-per-day limit. — ] <sup>]</sup> 02:32, 30 October 2014 (UTC) | |||
:Those dates look great to me, thank you. I had no idea it was going to be as easy as ]; perhaps my experience of ] led me to expect a huge cumbersome thing. ] (]) 06:25, 30 October 2014 (UTC) | |||
*Moved question from request page. <span style="font-family:Trebuchet MS">] <small>(])</small></span> 01:26, 14 November 2014 (UTC) | |||
{{archive bottom}} | |||
From time to time I receive emails from editors asking me to grant them a permission. I don't know why they do so via email rather than PERM (I guess they contact me because I'm active there), but I direct them to make a request on-wiki, for several reasons: our long-standing principle that, although there is no rule against off-wiki discussions, ]; to leave a documentation trail that all editors can follow; to give a chance for other editors to share relevant information on the request; and, because ] is frequently backlogged, to avoid the impression of someone pushing in the queue. I do make quite frequently make grants (especially of autopatrolled) without any request or following discussions elsewhere on-wiki, but I don't think that's quite the same. | |||
== Account Creator technical change == | |||
{{archive top|RFC Passed}} | |||
{{notice|Notice: a proposal to change the technical implementation of this group's permissions is being held at ].}} <span style="font-size: smaller;" class="autosigned"> — Preceding ] comment added 04:29, 01 Dec 2014</span><!--Template:Undated--> | |||
{{archive bottom}} | |||
I've noticed that not all admins agree with me on this point. Grants that don't go through PERM are relatively common, and sometimes an off-wiki request is explicitly mentioned in the log. For example, looking at one user today, I noticed that they managed to accrue autopatrolled, PCR, page mover, rollbacker, trial new page reviewer and permanent new page reviewer with only a single PERM request – the rest were all apparently solicited from different admins on one of the ]. | |||
== RfC: Should WP:PERM take advantage of ] or ]? == | |||
This doesn't feel right to me, so I thought I'd ask for other opinions on the practice of requesting permissions privately. Is there a guideline on this somewhere? If not, should we have one? – ] <small>(])</small> 07:10, 10 June 2024 (UTC) | |||
I've noticed that on a few occasions the {{Tl|Admin dashboard}} has had page size transclusion issues, and I think that these could be greatly reduced by taking advantage of {{U|ClueBot III}}'s ability to archive discussions that are already closed (I'll not that it is used on this very talk page). Another benefit of this is that it would allow ] (or more specifically, the new and improved version waiting to be incorporated into the main version (])) to be used for on the fly archiving when the dashboards are hitting page size limits for a quick fix. Thanks for any consideration on this. — <span class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></span> 05:35, 3 December 2014 (UTC) | |||
:The transcluded PERM subpages are already being archived by ]; does it just need some tweaking? — ] <sup>]</sup> 18:07, 3 December 2014 (UTC) | |||
:* There are some sections (ie: ]) that have been marked as done for almost 4 weeks now, and there are many that where marked as done over a week ago. I see no reason that the sections marked as "done" explicitly should be kept on the page for more than 24 hours (or 3 days max) as the user that received the additional group to their rights would have gotten a notification through the system. Anyone that would know to look at the PERM page to object to a user being granted certain rights should be experienced enough to know to look at the archives if it has been longer than that in most cases I would think. — <span class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></span> 18:53, 3 December 2014 (UTC) | |||
:: It might have something to do with: | |||
{{User:KingpinBot/report|hide=no}} | |||
:: :/ — <span class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></span> 19:05, 3 December 2014 (UTC) | |||
:We certainly could use a different system, but need to get the old one to stop first so they don't collide, {{ping|Kingpin13}} - any thoughts? — ] <sup>]</sup> 14:53, 4 December 2014 (UTC) | |||
:* Apparently Equazcion has retired, and as such, he's "redirected" his script to mine and I've taken over maintenance. {{U|Xaosflux}}, I can't think of anything it would hurt by having the archiving systems overlap. Is there something you have in mind that could be a problem I'm not thinking of? Thanks. — <span class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></span> 15:49, 4 December 2014 (UTC) | |||
:::As far as one-click types go, nope; I'm just referring to bot managed. — ] <sup>]</sup> 16:12, 4 December 2014 (UTC) | |||
:::* I should be able to use the {{Tl|Archive basics}} to make the pages one-click compatible, I just need to look at what the archival structure is suppose to be. — <span class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></span> 17:36, 4 December 2014 (UTC) | |||
:::: Ahh, {{U|Xaosflux}}, I now understand what you are saying. KingpinBot archives them based on status (approved or not approved) and cluebot wouldn't do that, at least not without some help from {{U|Cobi}} (the maintainer) to tweak stuffs... It's going to require me to to some tweaking to make it so that OCA is usable as well for the same reason unless it is decided to do away with the whole separate categorized archives method... Should this be posted on {{Tl|CENT}} to get some more input or a note put on ] maybe? Thanks for your help. — <span class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></span> 18:19, 4 December 2014 (UTC) | |||
:::::We don't really need a formal RFC type discussion on this, it is a completely non-controversial task in that noone opposes having an archive; if one set of archiving tools is more reliable than another for this set of pages, discussion on this page is all that is needed to swap / augment. This page, or at least one of its subpages, would make a good test for one-click archive options as well. — ] <sup>]</sup> 19:36, 4 December 2014 (UTC) | |||
:::::* I wasn't suggesting a formal "30 days and closed by uninvolved" RfC, just wondering if there should be a short note on AN to see if anyone else has any feedback on whether or not it should be continued to be archived by KpBot in the current format splitting the approved from declined (which I think is a bad idea as it means that "other" parties that may have been following a certain request have to look in two places instead of one to find the result if it wasn't the result they expected) or if we should configure CBot to archive it all on one archive page. I'll need to know this before I make a special module for OCA to archive these discussions (if it is the first option, it may require two clicks to archive correctly each time). — <span class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></span> 20:20, 4 December 2014 (UTC) | |||
::::::*Oh sure, an in-link from AN to this thread would be good to get some more eyes on this-I would like to hear from Kingpin too (already pinged) — ] <sup>]</sup> 20:36, 4 December 2014 (UTC) | |||
{{Od}}{{Done|{{Diff|Misplaced Pages:Administrators' noticeboard|636660202|636659891|'''Done'''}}}} — <span class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></span> 20:57, 4 December 2014 (UTC) | |||
*Let's not make a big fuss about this proposal because all that will be achieved by inviting a broader community will be no consensus at all. The issue only really concerns the admins who patrol the PERM requests and who accord or decline them, and any bots that do the archiving. There is quite a small group of admins who work here and they do so fairly regularly. Whatever solutions the bot handlers reach, what we need to bear in mind are : | |||
#Are we 100% certain that users who receive the additional group to their rights are given a notification through the system. AFAIK, the recommendation is that they check back at PERM (or check their rights log). | |||
#Are we 100% certain that users who ''do not'' receive the additional group to their rights are given a notification through the system. AFAIK, the recommendation is that they check back at PERM (admins are not obliged to inform them). | |||
#I think it appropriate to archive all admin decisions after seven (7) days in order to give 'weekend Wikipedians' a chance to log in. | |||
#IMO, requests not yet handled by an admin should ideally be left permanently open until adressed. Exception: if NACd as 'not done' by a '''''truly''''' competent user such as {{U|Armbrust}} who has been doing it for years. Note: we do not want to invite a plethora of other NAO/NAC to these pages from admin wannabes - the unnecessary 'clerking' is bad enough already. | |||
--] (]) 03:48, 20 December 2014 (UTC) | |||
::KingpinBot was on Christmas holiday, sorry. Running again now. As far as problems with if the bot does die for good, I can always be contacted via email and make the source code available to someone else to run it (clearly I'm not particularly active myself these days). {{ping|Technical 13}} As far as the problem of having to look in multiple places for an archived discussion if you don't know the result, I made a search box at ] a while ago specifically to deal with this problem. - ]<sup>]</sup> (]) 19:29, 11 January 2015 (UTC) | |||
::* {{U|Kingpin13}} where is KpBot located? If it's on toollabs or someplace I can access, I would be happy to push the restart button when needed. ] — <span class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></span> 20:00, 11 January 2015 (UTC) | |||
*{{ping|Kingpin13}}, {{ping|Technical 13}}, {{ping|Armbrust}}: I think we need to take a look at my questions above which no one has taken the trouble to address. Also, the archiving is still too fast, we have users reposting their declined requests within two days. All declined requests should preferably only be archived after 7 days. And thank you , Armbrust, for stepping into the breach and doing what you have been doing for years so much better than a bot. We ae getting to the stage on Misplaced Pages where in many cases we are placing too much reliance on bots. --] (]) 05:13, 12 January 2015 (UTC) | |||
*:The control for how long the bot waits before archiving is at ]. Feel free to up the number. As far as the reliance on bots goes, it's not a problem with the bot or bots in general so much as this operator in this case. This kind of task is a complete waste of time to do manually. - ]<sup>]</sup> (]) 10:31, 12 January 2015 (UTC) | |||
*:* To repeat, in case you missed it above {{U|Kingpin13|Kingpin}}, is it possible that I can get access to restart kingpinbot when these outages occur? — <code class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></code> 22:07, 18 January 2015 (UTC) | |||
*:*:The bot is written in F# so I think there would be a bit of work involved in running it on the toolserver? - ]<sup>]</sup> (]) 14:18, 21 January 2015 (UTC) | |||
*:*:* {{U|Kingpin13}}, there is no ] anymore, so I'm guessing you mean on ]? I don't see why it would be an issue with running it on labs, but I can certainly check for you. I'll note that it doesn't have to be on labs for me to restart it (] isn't for example ), but that would be a decision that's entirely up to you. :) — <code class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></code> 16:19, 21 January 2015 (UTC) | |||
*Please bear in mind that this is coming from someone with no clue about bot programming, but perhaps it would make sense to leave declined requests a bit longer than accepted ones in order to insure the user has seen them? When granting permissions, I certainly hope all of us are leaving the standard talk page messages for the user whose requests are granted, making the {{done}} notation here is just a formality so others know not to review the request and the bot knows to archive it. There is not, and should not be any such protocol for declined requests. If we leave everything up for a week the page could get quite crowded at times, if the bot could remove accepted requests that would cut it way down. So, is that possible and if so should we do it? ] (]) 21:46, 18 January 2015 (UTC) | |||
* The problem I have with leaving these requests around longer is that they are already left around too long as it is which has constantly caused page size transclusion errors with {{Tl|Admin dashboard}}. I'd rather see them archived immediately when resolved and then have the archiver post a message on the requester's talk page giving them the result and a link to the archived result. — <code class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></code> 22:07, 18 January 2015 (UTC) | |||
::I kind of like that idea, but not the immediate part. Just today I ran across what I feel to be a poorly reasoned decline of a request, and have asked the declining admin to reconsider and/or provide more solid reasoning for their decline. If the request has been bot-archived the as soon as it was declined I would never have known. There is also a minor issue of at the request for confirmation. As we all know, most request there are declined. However, we are dealing almost exclusively with brand new users there. I for one feel it is important in almost all cases to welcome those users, even (especially actually) if they deeply misunderstand what Misplaced Pages is and how it works. Unfortunately not everyone sees it that way and there are some who just decline requests without following it up with a welcome on their talk page, so I end up following up for them and welcoming all the people they decline. As this is an editor retention/] issue I feel it is pretty important. | |||
::Somewhere in between "a week" and "immediately" lies a middle ground that will keep the page from being cluttered but alow some time for review. ] (]) 23:04, 25 January 2015 (UTC) | |||
::* What if it was immediate with a 7 day rolling archive like RFPP has? Then admins that want to follow the feed can but it won't break the dashboard for others. As for the concerns of biteyness with new user's requesting confirmed, part of the process of archiving those requests could be to automatically welcome those users with a template designed specifically for them. Kind of like what I do with ] for Account Creation (since the bot that is suppose to do the welcoming for that project has been down longer than I've been a member). Thoughts? — <code class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></code> 23:28, 25 January 2015 (UTC) | |||
:The occasionally mentioned "discussion on Discord" is at least sometimes just the admin asking the user if they would like the perm (rather than the other way around). At least one admin who has done that discourages perm requests from being made on Discord. | |||
==] at 400 mainspace edits?== | |||
:But some users might be shy about having a request declined at ] (like a much smaller version of ]). | |||
{{archive top}} | |||
:Since perm grants are entirely at an admin's discretion and don't require consensus (which is what should be done on-wiki), I think it's fine to leave it up to them to decide whether to entertain requests by email or direct message. ] ] 09:03, 10 June 2024 (UTC) | |||
I see administrators usually declining users under 400 mainspace edits by suggesting to enroll in CVUA after the user has reached 400 mainspace edits ("when you have made 400 or so edits to articles you may wish to enroll at the Counter Vandalism Academy to learn more"). However, on the CVUA page, under Goals, it says 200 mainspace edits minimum instead of 400 to enroll in the program. Shouldn't it be suggested at 200 mainspace edits instead of 400? <span style="color: #3BB9FF; font-weight: 700; font-style: italic; font-family: Lato, sans-serif'">HelloThereMinions</span> <sup>],</sup> <sup>]</sup> 04:22, 28 December 2014 (UTC) | |||
::Permissions grants require consensus, just like everything else. – ] <small>(])</small> 09:31, 10 June 2024 (UTC) | |||
:{{done}} <b>]</b> (] • ] • ]) 05:18, 28 December 2014 (UTC) | |||
:::There could be a requirement for consensus, but each perm page generally says something like ]'s "{{tq|An administrator may grant page mover rights to users they otherwise deem competent and may deny the requests if they do not see a need for the tools or have other concerns.}}" ] ] 09:56, 10 June 2024 (UTC) | |||
{{archive bottom}} | |||
:::I'm not sure saying they require consensus is the correct phrasing. For instance, administrators are allowed to grant autopatrolled at their own discretion, that's part of the toolkit that we trust admins with. ] (]) 12:23, 10 June 2024 (UTC) | |||
::::Yes but if two (or more) admins disagree on whether to grant autopatrolled, what do we do? Seek consensus. It doesn't come up very often, but there certainly have been e.g. AN threads where a grant has been challenged and overturned on that basis. Even if there's no discussion, consensus is still there, ]. | |||
::::I understand the "discretion" language in many (not all) of the PERM guidelines to mean that an editor is not automatically entitled to a right if they might the guideline criteria (and vice-versa) – not that it's literally only up to single admins to decide, with no community oversight. – ] <small>(])</small> 13:19, 10 June 2024 (UTC) | |||
:::::We don't have a minimum time that a request for a permission must stay up, so an admin can immediately process a request and then it'll be cleaned out. If there's issues with that user then yeah, ANI. I don't think it's always entirely necessary to force a request at perm simply for the sake of bureaucracy. I do not like to handle perm requests at my talk page either, but in rare circumstances for exceptional users, I'll be more than happy to grant them tools that may help them to improve the encyclopedia. If there's a chance it may at all be controversial, or I don't know them enough to make that call without digging deeper, then I too send them to perm (which is most of the time). | |||
:::::I think, unless it states otherwise anywhere, the implication has always been that an administrator may grant permissions at their own discretion without a formal request in most situations. I don't personally see an issue with that until an administrator's judgement comes into question. | |||
:::::Also, ] states {{tq|Administrators may grant this user right to anyone at their discretion if they feel that the user's page creations are prolific; this reduces the workload of new page reviewers. In these cases, they are free to assign the user right to other editors (including themselves) without a formal request or discussion beforehand.}} – This makes the autopatrolled example not a good one, since, I believe, it's the only perm with this type of language specifically called out. ] (]) 13:59, 10 June 2024 (UTC) | |||
:I outright decline direct requests and point editors to the respective pages instead. That said, I have also granted permissions to editors without them asking about it; this applies to editors whose work I'm familiar with. ''']]''' 11:10, 10 June 2024 (UTC) | |||
::This is what I do as well; if I know the editor (and they need it) I'll usually grant, otherwise I'll send 'em to PERM. ] (]) 11:59, 10 June 2024 (UTC) | |||
:Just noting that I am firmly opposed to ''requiring'' that permission requests go through PERM. ] (]) 12:01, 10 June 2024 (UTC) | |||
::To be clear, I'm not suggesting that. My basic question here is whether granting permissions following a private request is something we should discourage, and if so whether we should write that down along the lines of ]. – ] <small>(])</small> 13:23, 10 June 2024 (UTC) | |||
:It's very admin-discretionary. In general, if someone asks me for a perm I'll ask them to drop a request at ]. It certainly shouldn't be a requirement as there are all sorts of use cases were it would be unnecessary paperwork. — ] <sup>]</sup> 19:55, 10 June 2024 (UTC) | |||
== Error? == | |||
== ] removal request == | |||
Hi, I've been approved yet when I try to log in to AWB it says "This user does not have enough privileges to make automatics edits on this wiki" ] (]) 17:08, 15 August 2024 (UTC) | |||
{{archive top|{{done}} — ] <sup>]</sup> 15:01, 31 December 2014 (UTC)}} | |||
:See {{slink|Wikipedia_talk:AutoWikiBrowser#AWB_Permission_error}}, there is a version update that fixes the issue. ] (]) 17:51, 15 August 2024 (UTC) | |||
* {{rfplinks|1=NE Ent}} | |||
::I updated to 6.3.1.1 but it still comes back with an error when I try to log in ] (]) 17:59, 15 August 2024 (UTC) | |||
:Please '''remove''' autopatrolled from my account <small>]</small> 22:34, 22 December 2014 (UTC) | |||
:::Post on that thread, then, about your issues, so that you can get feedback from that project. ] (]) 18:02, 15 August 2024 (UTC) | |||
::{{done}} — ] <sup>]</sup> 22:57, 22 December 2014 (UTC) | |||
{{archive bottom}} | |||
== ECP Protection Removal Appeal == | |||
== Semi-protected edit request on 10 January 2015 == | |||
{{archive top}} | |||
{{edit semi-protected|Misplaced Pages:Requests for permissions/File mover|answered=yes}} | |||
<!-- Begin request --> | |||
So I can submit my request. | |||
<!-- End request --> | |||
]]]] 20:19, 10 January 2015 (UTC) | |||
:] '''Not done for now:'''<!-- Template:ESp --> It's unclear what you are asking for. This is the page for requesting permissions, but you need to state exactly what permissions you are requesting and why you are requesting them. Thanks. — <span class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></span> 21:00, 10 January 2015 (UTC) | |||
{{archive bottom}} | |||
How do I appeal a removal? I have repeatedly tried to reach out to the person who removed my ability to do so. But no response! ] (]) 15:44, 7 September 2024 (UTC) | |||
== ] == | |||
{{archive top}} | |||
(From ]) | |||
* {{rfplinks|1=Ajaxfiore}} | |||
:I would like to renounce my Rollback privileges. ] (]) 03:55, 14 January 2015 (UTC) | |||
::{{done}} — ] <sup>]</sup> 05:23, 14 January 2015 (UTC) | |||
{{archive bottom}} | |||
:And it’s been months. ] (]) 15:45, 7 September 2024 (UTC) | |||
== Pending Changes Reviewer == | |||
::Requests for ExCon can be made at ]. Keep in mind you'll need to make a convincing argument as to why you should have it back after it was removed. ] (]) 16:41, 7 September 2024 (UTC) | |||
{{archive top}} | |||
* {{rfplinks|1=Ajaxfiore}} | |||
:I would also like to renounce my Reviewer privileges. ] (]) 15:06, 14 January 2015 (UTC) | |||
::{{done}} — '''] <sup>]</sup>''' 16:31, 14 January 2015 (UTC) | |||
{{archive bottom}} | |||
== Concern == | |||
== Semi-protected edit request on 19 January 2015 == | |||
{{u|TParis}}, just a courtesy note that I have reverted you granting autopatrolled to User:GnocchiFan over concerns raised by User:TechnoSquirrel69. What concerns me more, though, is that you granted autopatrolled to four users within five minutes. You cannot possibly have looked at those users' contributions in detail and assessed the quality of their work in such a short period of time. AP isn't a numerical exercise; we are assessing whether users consistently produce clean articles free of concerns. There is no substitute to looking at a sample of their recent articles. When I assess users, I generally look at their last ten articles created, including the edit history of those articles, to see whether other users had to fix issues. If you don't want to invest that effort, please don't patrol the request page. ''']]''' 20:29, 3 October 2024 (UTC) | |||
{{edit semi-protected|Misplaced Pages:Requests for permissions/Account creator|answered=yes}} | |||
<!-- Begin request --> | |||
I would like to change the photograph currently showing on wikipedia on my page information for Diana Binks. Please confirm how i can do this by email to binksdb@outlook.com Many thanks . Diana Binks | |||
:You should've discussed it first. The encyclopedia was not in so grave of a danger that you couldn't have paused and discussed.--v/r - ]] 20:31, 3 October 2024 (UTC) | |||
<!-- End request --> | |||
::Sure, I could and should have posted this item first. What I'm saying, though, is that you are clearly acting outside what other admins who are active here are doing. And that is a concern that needed to be raised. ''']]''' 20:34, 3 October 2024 (UTC) | |||
:::Other admins talk to each other before reverting admin actions.--v/r - ]] 20:36, 3 October 2024 (UTC) | |||
::::@], I'm surprised to read this, since when I just dropped by your talk page I was greeted by a notice that said {{tq|'''Are you an admin reverting a decision I made?''' You are welcome to leave a note, but please understand I completely trust your judgement and ] should not be a stopping block for you.}} I would myself have taken that as an implicit request ''not'' to speak to you about it in advance. -- ] (]) 20:44, 3 October 2024 (UTC) | |||
:::::I believe I wrote that in 2011. My personality and views may have changed since then.--v/r - ]] 21:19, 3 October 2024 (UTC) | |||
::::::Then it sounds like it's on you for not updating it. There's no reason for others to assume that wasn't still the case. ] (]) 00:17, 4 October 2024 (UTC) | |||
:::::::I'm allowed to feel the way I feel.--v/r - ]] 02:17, 4 October 2024 (UTC) | |||
::::Yes, as I said above: {{tq|I could and should have posted this item first}}. The reason that I acted immediately is that I wanted to avoid User:GnocchiFan getting excited about you having granted AP and then learning that it's been reverted. When I went to their talk page (after I removed the flag), I see that you had not issued the relevant notification, though. Seeing all the bot notifications on the request page, it's clear that you've missed that step for all those users. ''']]''' 20:46, 3 October 2024 (UTC) | |||
:::::Yes. Back 13 years ago when I was working ], we still believed that the encyclopedia was no big deal and we granted tools to users that wouldn't abuse them. I can understand not wanting the user to get excited, but I also don't think the issues raised are significant because they address other Misplaced Pages, and even Wikimedia, goals. You bring up as a point that you feel I was too hasty in granting the permission, but I feel you were too hasty in reverting. As you know, ] will quickly end up at Arbcom. So when one admin reverts another - it's very much "final". It's not like editors reverting in editor space. Typically, we afford each other the courtesy of discussion because of this. It's fine though, I'm no longer interested in helping here.--v/r - ]] 21:19, 3 October 2024 (UTC) | |||
::::::AP isn't a tool though and it doesn't really help anyone but NPP. Do you still believe, after receiving feedback, that granting AP to four users in a five minute stretch was appropriate? I'm not confident, given the speed of granting, that the concerns raised were properly considered. | |||
::::::I'm very disappointed that an admin receives feedback and decides to immediately quit in the area, that's not the temperament we hope for in admins. ] (]) 00:11, 4 October 2024 (UTC) | |||
:::::::I don't think it'll be a great loss to ]. I'll contribute in places I am more confident and comfortable contributing in.--v/r - ]] 02:07, 4 October 2024 (UTC) | |||
:{{nacc}} - not an admin so I won't opine on the matter at hand now, but I think this might be better placed in ]. ] | ] | ] (they/them) 20:47, 3 October 2024 (UTC) | |||
::I think we are capable of sorting this out here, Zippybonzo. In fact, I'd say it's already sorted (from my perspective it is, at least). ''']]''' 20:49, 3 October 2024 (UTC) | |||
:::👍 :) ] | ] | ] (they/them) 20:52, 3 October 2024 (UTC) | |||
:::I do appreciate you bringing this up {{yo|Schwede66|p=,}} and I agree with you that discussions don't necessarily need to jump to the bigger venues. No admin is perfect, we all need feedback and to adjust our practices from time to time. ] (]) 00:14, 4 October 2024 (UTC) | |||
===Side note on review speed=== | |||
Just noting, which is somewhat relevant to this thread but a comment in general: the speed at which an admin acts on requests is not necessarily the speed at which they reviewed them. Take for example ] or ], wherein I will regularly spend a good amount of time reviewing ''all'' of the editors, then make a single edit to each of the relevant locations to enact all of the requests as necessary. If it were something like ], with the script it necessitates multiple edits but the time spent before actioning is still the same.{{pb}}I'll split this into it's own subsection, as I have not looked into the original speed of review and therefore do not want to say that what I describe above is what happened in the main thread, but more that it's something to consider going forward. ] (]) 13:39, 5 October 2024 (UTC) | |||
:Yeah I think unless it's really extreme, looking at the time between edits/action is a poor way to judge how much attention has been given. How much time I spend on PERM requests varies a lot. Declines can be near-instant if you spot a deal-breaker. Sometimes I'm already familiar with the editor's work from some other context and don't have to spend much time checking again. Sometimes I'll look at a request and mull over it for a day or two before actioning it. Judge the results, not the timestamps. – ] <small>(])</small> 08:26, 31 October 2024 (UTC) | |||
==Discussion at ]== | |||
] (]) 11:55, 19 January 2015 (UTC) | |||
] You are invited to join the discussion at ]. –] <small>(])</small> 21:50, 30 October 2024 (UTC)<!-- ] --> | |||
:] '''Not done:''' this is the ] for discussing improvements to the page ]. Please make your request at the talk page for the article concerned.<!-- Template:ESp --> ] 17:36, 19 January 2015 (UTC) | |||
== How can I request permission again if I already met the requirements == | |||
{{edit protected|answered=yes}} | |||
: Oversight and Checkuser should also include identification. Yes it's on the pages focusing on them but it wouldn't hurt to mention it here. | |||
How can I request permission again if I already met the requirements for template editor? I've already met criteria #3, which is to have at least 150 total edits to the Template and Module namespaces. ] (]) 22:49, 29 December 2024 (UTC) | |||
:{{comment}} Not sure that's needed here, a link is provided to more information, that should suffice. <span style="font-family:Trebuchet MS">] <small>(])</small></span> 18:25, 24 January 2015 (UTC) | |||
:] '''Not done:''' please establish a ] for this alteration before using the {{tlx|edit protected}} template.<!-- Template:EP --> — <code class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></code> 19:05, 24 January 2015 (UTC) | |||
:You simply request them again. But you don't request them just to have them. It'd be preferable if you'd have actually made requests to restricted templates. ] (]) 23:12, 29 December 2024 (UTC) | |||
== Let's get real about rollback == | |||
::Just noting that after their initial request was ], they to hit 150. I consider this gaming, and while I don't see any issue with them requesting in the future, a quick look at their edit requests means they would probably not meet ] points 5 or 6 anyway. ] (]) 08:36, 30 December 2024 (UTC) | |||
I think some of us may be taking request for rollback a bit too seriously. I think we should be aware of the reality of the situation when reviewing these request, to wit: | |||
:*Rollback is really no more "powerful" than the undo function, it's just ever-so-slightly easier | |||
:*If someone misuses it it is a matter of just a few keystrokes to remove it again | |||
:*] has a ''much'' better rollback function and all you have to do to access it is turn it on in your preferences literally the second you register an account | |||
Personally I never had rollback until I became an admin and I never missed it because I use twinkle. Actually, I would rather not have it as it just gets in my way but apparently if you are an admin you have it whether you want it or not. The point is, this is an extremely low-level user right, there is literally ''nothing'' a user with rollback can damage that a user without it couldn't, and we implicitly grant it to every single registered account by having twinkle available to them from day one. | |||
I don't know that any formal policy changes are needed here or anything, but I'd like to discuss the matter with PERM regulars and anyone else with an interest in rollback requests. ] (]) 23:32, 25 January 2015 (UTC) | |||
* {{U|Beeblebrox}}, I agree with most of what you said. Twinkle isn't available from day one, it's available from whenever autoconfirmed is obtained (day 4 if they have 10 edits). Also, the only real reasons to have rollback is to be able to use a few userscripts and tools like Stiki and Huggle. I'm actually wondering if the hat shouldn't just be done away with or rolled into reviewer or something. Scripts and tools that rely on it could certainly be updated. Is there any valid reason for keeping it around and not doing this? — <code class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></code> 23:43, 25 January 2015 (UTC) | |||
*:It's actually possible to use Twinkle without being registered, but ]. If "real" rollback is ever changed to not bypass things like the spamblacklist, I'd support removing the rollbacker group and giving the right to autoconfirmed (or maybe even user). ] (]) 23:50, 25 January 2015 (UTC) | |||
:After considering a request many times, I find the TW more easy since pressing UNDO usually fails from an edit conflict. The difference of course is the twinkle and the permission allows it on one click. You just have to be more careful. ] (]) 23:45, 25 January 2015 (UTC) | |||
*...Or instead of having the rollback, why don't we just do a dummy edit on a previous version of the page we want to restore, save, and magically, a non-rollback ... rollback! Seriously, I always found this user right to be a bit redundant, given that the function can be accomplished via other means. ] (]) 00:24, 26 January 2015 (UTC) | |||
*I think getting rid of it as a separate user right probably makes a lot of sense. It could instead be an optional gadget like twinkle. I know it is a prerequisite for some anti-vandal tools, but frankly I don't really think it should be the job of admins at PERM to act as the gatekeepers for those tools, unless they want it done directly as is done with AWB. However, to make that change will require a big RFC, and I'm in the middle of putting together one of those on an entirely separate issue right now and it will probably need me to babysit it for a while after it goes live. Anyone up for it? I can at least offer ]. ] (]) 00:32, 26 January 2015 (UTC) | |||
** Me starting such an RfC would guarantee its demise, so unless no-one else wants to do it, I'd rather not. — <code class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></code> 00:56, 26 January 2015 (UTC) | |||
*Possibly not worth worrying about, but rollback links--unlike Twinkle links--show up on the history and recent changes, which makes it easier to revert edits that are obviously revert worthy without checking the diff (e.g. if it's an obvious malicious blanking as per the size change and summary, or when edit warring with a vandal or reverting oneself), and also makes it possible to see which edits in recent changes are current revisions. Twinkle also opens popup windows, which may not be desirable, is allegedly slower, and may stop working when we upgrade to MW 1.26. I don't know about anyone else, but I'd rather have rollback than resort to using Twinkle's "vandalism" links (I haven't got round to asking, though). ]] 01:35, 26 January 2015 (UTC) | |||
** Twinkle links show up on History and I never use RC because that feed is useless here so can't say for sure there. Twinkle is compliant with the upcoming changes, and as long as you're not using any of the other {{Cl|JavaScripts using deprecated elements|count=y}} scripts (you can comment them out until fixed) you should be fine. — <code class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></code> 01:56, 26 January 2015 (UTC) | |||
**: Oh, and the default popup behaviour can be overridden in preferences. — <code class="nowrap">{{U|]}} <sup>(] • ] • ])</sup></code> 01:58, 26 January 2015 (UTC) | |||
**::After discussing this on IRC we've concluded that, no, there are no links on the page created by appending the query string <code>?action=history</code> (which is what I meant by "the history", as opposed to the diff view). Yes, Twinkle links could be added to the history, and to RC as well I'm sure, which I disagree is useless. I see that my concerns are not strictly valid: there is no pressing need for rollback to exist, as Twinkle performs the same function. But is it really worth it to get rid of rollback? I don't see what we'd gain by doing so; we'd have less examination of those wanting the right, thus increasing the risk that it would be misused (indeed Twinkle can be abused, but having at least some people go through the scrutiny of rollback requests cuts down on that kind of thing), and modifying the Twinkle script and its preferences seems a great deal of fiddling for little benefit. ]] 06:26, 26 January 2015 (UTC) | |||
*I don't want to sound negative, but do we really need to be discussing ''any'' of this? Is it a high priority for our volunteer programmers who have badly functioning tools on Labs to fix? Frankly I never really understood the difference between Twinkle's rollback and the user right Rollback - which leads me once more to think thst it's only of interest to the hat collectors and greasy pole climbers. Was there ever anything ''essentially'' wrong with the archiving? Except perhaps that the declined request were archived too soon. Do we even need a bot at all to do the archiving? We had a ] for years who actualy did a good job of it as de facto PERM clerk. He also fixed a lot of other stuff on the fly too, such as malformed requests, vandalism, and other junk. --] (]) 03:38, 26 January 2015 (UTC) | |||
*:Rollback is (was?) necessary to use some other tools like Huggle, which is the only reason why I ever got it. <span style="font-variant:small-caps">]</span> (]) 06:14, 26 January 2015 (UTC) | |||
*::I assume that if rollback were eliminated, one would gain access to those tools via a request on wherever you make special requests now. This would create more work, potentially balancing out the reduction in work created by eliminating the rollback request page, though there would be some overlap between current requests for rollback and future requests for access to those tools. ]] 06:45, 26 January 2015 (UTC) |
Latest revision as of 08:36, 30 December 2024
This is the talk page for discussing improvements to the Requests for permissions page. |
|
Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11Auto-archiving period: 3 months |
Private requests for permissions
From time to time I receive emails from editors asking me to grant them a permission. I don't know why they do so via email rather than PERM (I guess they contact me because I'm active there), but I direct them to make a request on-wiki, for several reasons: our long-standing principle that, although there is no rule against off-wiki discussions, decisions affecting Misplaced Pages should be made on Misplaced Pages; to leave a documentation trail that all editors can follow; to give a chance for other editors to share relevant information on the request; and, because WP:PERM is frequently backlogged, to avoid the impression of someone pushing in the queue. I do make quite frequently make grants (especially of autopatrolled) without any request or following discussions elsewhere on-wiki, but I don't think that's quite the same.
I've noticed that not all admins agree with me on this point. Grants that don't go through PERM are relatively common, and sometimes an off-wiki request is explicitly mentioned in the log. For example, looking at one user today, I noticed that they managed to accrue autopatrolled, PCR, page mover, rollbacker, trial new page reviewer and permanent new page reviewer with only a single PERM request – the rest were all apparently solicited from different admins on one of the unofficial Misplaced Pages Discord servers.
This doesn't feel right to me, so I thought I'd ask for other opinions on the practice of requesting permissions privately. Is there a guideline on this somewhere? If not, should we have one? – Joe (talk) 07:10, 10 June 2024 (UTC)
- The occasionally mentioned "discussion on Discord" is at least sometimes just the admin asking the user if they would like the perm (rather than the other way around). At least one admin who has done that discourages perm requests from being made on Discord.
- But some users might be shy about having a request declined at WP:PERM (like a much smaller version of WP:RFA).
- Since perm grants are entirely at an admin's discretion and don't require consensus (which is what should be done on-wiki), I think it's fine to leave it up to them to decide whether to entertain requests by email or direct message. SilverLocust 💬 09:03, 10 June 2024 (UTC)
- Permissions grants require consensus, just like everything else. – Joe (talk) 09:31, 10 June 2024 (UTC)
- There could be a requirement for consensus, but each perm page generally says something like WP:PMCRITERIA's "
An administrator may grant page mover rights to users they otherwise deem competent and may deny the requests if they do not see a need for the tools or have other concerns.
" SilverLocust 💬 09:56, 10 June 2024 (UTC) - I'm not sure saying they require consensus is the correct phrasing. For instance, administrators are allowed to grant autopatrolled at their own discretion, that's part of the toolkit that we trust admins with. Hey man im josh (talk) 12:23, 10 June 2024 (UTC)
- Yes but if two (or more) admins disagree on whether to grant autopatrolled, what do we do? Seek consensus. It doesn't come up very often, but there certainly have been e.g. AN threads where a grant has been challenged and overturned on that basis. Even if there's no discussion, consensus is still there, implicitly.
- I understand the "discretion" language in many (not all) of the PERM guidelines to mean that an editor is not automatically entitled to a right if they might the guideline criteria (and vice-versa) – not that it's literally only up to single admins to decide, with no community oversight. – Joe (talk) 13:19, 10 June 2024 (UTC)
- We don't have a minimum time that a request for a permission must stay up, so an admin can immediately process a request and then it'll be cleaned out. If there's issues with that user then yeah, ANI. I don't think it's always entirely necessary to force a request at perm simply for the sake of bureaucracy. I do not like to handle perm requests at my talk page either, but in rare circumstances for exceptional users, I'll be more than happy to grant them tools that may help them to improve the encyclopedia. If there's a chance it may at all be controversial, or I don't know them enough to make that call without digging deeper, then I too send them to perm (which is most of the time).
- I think, unless it states otherwise anywhere, the implication has always been that an administrator may grant permissions at their own discretion without a formal request in most situations. I don't personally see an issue with that until an administrator's judgement comes into question.
- Also, Misplaced Pages:APATCRITERIA states
Administrators may grant this user right to anyone at their discretion if they feel that the user's page creations are prolific; this reduces the workload of new page reviewers. In these cases, they are free to assign the user right to other editors (including themselves) without a formal request or discussion beforehand.
– This makes the autopatrolled example not a good one, since, I believe, it's the only perm with this type of language specifically called out. Hey man im josh (talk) 13:59, 10 June 2024 (UTC)
- There could be a requirement for consensus, but each perm page generally says something like WP:PMCRITERIA's "
- Permissions grants require consensus, just like everything else. – Joe (talk) 09:31, 10 June 2024 (UTC)
- I outright decline direct requests and point editors to the respective pages instead. That said, I have also granted permissions to editors without them asking about it; this applies to editors whose work I'm familiar with. Schwede66 11:10, 10 June 2024 (UTC)
- This is what I do as well; if I know the editor (and they need it) I'll usually grant, otherwise I'll send 'em to PERM. Primefac (talk) 11:59, 10 June 2024 (UTC)
- Just noting that I am firmly opposed to requiring that permission requests go through PERM. Primefac (talk) 12:01, 10 June 2024 (UTC)
- To be clear, I'm not suggesting that. My basic question here is whether granting permissions following a private request is something we should discourage, and if so whether we should write that down along the lines of Misplaced Pages:Blocking policy#Dealing with off-wiki block requests. – Joe (talk) 13:23, 10 June 2024 (UTC)
- It's very admin-discretionary. In general, if someone asks me for a perm I'll ask them to drop a request at WP:PERM. It certainly shouldn't be a requirement as there are all sorts of use cases were it would be unnecessary paperwork. — xaosflux 19:55, 10 June 2024 (UTC)
Error?
Hi, I've been approved yet when I try to log in to AWB it says "This user does not have enough privileges to make automatics edits on this wiki" Kowal2701 (talk) 17:08, 15 August 2024 (UTC)
- See Misplaced Pages talk:AutoWikiBrowser § AWB Permission error, there is a version update that fixes the issue. Primefac (talk) 17:51, 15 August 2024 (UTC)
- I updated to 6.3.1.1 but it still comes back with an error when I try to log in Kowal2701 (talk) 17:59, 15 August 2024 (UTC)
- Post on that thread, then, about your issues, so that you can get feedback from that project. Primefac (talk) 18:02, 15 August 2024 (UTC)
- I updated to 6.3.1.1 but it still comes back with an error when I try to log in Kowal2701 (talk) 17:59, 15 August 2024 (UTC)
ECP Protection Removal Appeal
How do I appeal a removal? I have repeatedly tried to reach out to the person who removed my ability to do so. But no response! Pentock (talk) 15:44, 7 September 2024 (UTC)
- And it’s been months. Pentock (talk) 15:45, 7 September 2024 (UTC)
- Requests for ExCon can be made at Misplaced Pages:Requests for permissions/Extended confirmed. Keep in mind you'll need to make a convincing argument as to why you should have it back after it was removed. Primefac (talk) 16:41, 7 September 2024 (UTC)
Concern
TParis, just a courtesy note that I have reverted you granting autopatrolled to User:GnocchiFan over concerns raised by User:TechnoSquirrel69. What concerns me more, though, is that you granted autopatrolled to four users within five minutes. You cannot possibly have looked at those users' contributions in detail and assessed the quality of their work in such a short period of time. AP isn't a numerical exercise; we are assessing whether users consistently produce clean articles free of concerns. There is no substitute to looking at a sample of their recent articles. When I assess users, I generally look at their last ten articles created, including the edit history of those articles, to see whether other users had to fix issues. If you don't want to invest that effort, please don't patrol the request page. Schwede66 20:29, 3 October 2024 (UTC)
- You should've discussed it first. The encyclopedia was not in so grave of a danger that you couldn't have paused and discussed.--v/r - TP 20:31, 3 October 2024 (UTC)
- Sure, I could and should have posted this item first. What I'm saying, though, is that you are clearly acting outside what other admins who are active here are doing. And that is a concern that needed to be raised. Schwede66 20:34, 3 October 2024 (UTC)
- Other admins talk to each other before reverting admin actions.--v/r - TP 20:36, 3 October 2024 (UTC)
- @TParis, I'm surprised to read this, since when I just dropped by your talk page I was greeted by a notice that said
Are you an admin reverting a decision I made? You are welcome to leave a note, but please understand I completely trust your judgement and my pride should not be a stopping block for you.
I would myself have taken that as an implicit request not to speak to you about it in advance. -- asilvering (talk) 20:44, 3 October 2024 (UTC)- I believe I wrote that in 2011. My personality and views may have changed since then.--v/r - TP 21:19, 3 October 2024 (UTC)
- Then it sounds like it's on you for not updating it. There's no reason for others to assume that wasn't still the case. Hey man im josh (talk) 00:17, 4 October 2024 (UTC)
- I'm allowed to feel the way I feel.--v/r - TP 02:17, 4 October 2024 (UTC)
- Then it sounds like it's on you for not updating it. There's no reason for others to assume that wasn't still the case. Hey man im josh (talk) 00:17, 4 October 2024 (UTC)
- I believe I wrote that in 2011. My personality and views may have changed since then.--v/r - TP 21:19, 3 October 2024 (UTC)
- Yes, as I said above:
I could and should have posted this item first
. The reason that I acted immediately is that I wanted to avoid User:GnocchiFan getting excited about you having granted AP and then learning that it's been reverted. When I went to their talk page (after I removed the flag), I see that you had not issued the relevant notification, though. Seeing all the bot notifications on the request page, it's clear that you've missed that step for all those users. Schwede66 20:46, 3 October 2024 (UTC)- Yes. Back 13 years ago when I was working WP:PERM, we still believed that the encyclopedia was no big deal and we granted tools to users that wouldn't abuse them. I can understand not wanting the user to get excited, but I also don't think the issues raised are significant because they address other Misplaced Pages, and even Wikimedia, goals. You bring up as a point that you feel I was too hasty in granting the permission, but I feel you were too hasty in reverting. As you know, wheel warring will quickly end up at Arbcom. So when one admin reverts another - it's very much "final". It's not like editors reverting in editor space. Typically, we afford each other the courtesy of discussion because of this. It's fine though, I'm no longer interested in helping here.--v/r - TP 21:19, 3 October 2024 (UTC)
- AP isn't a tool though and it doesn't really help anyone but NPP. Do you still believe, after receiving feedback, that granting AP to four users in a five minute stretch was appropriate? I'm not confident, given the speed of granting, that the concerns raised were properly considered.
- I'm very disappointed that an admin receives feedback and decides to immediately quit in the area, that's not the temperament we hope for in admins. Hey man im josh (talk) 00:11, 4 October 2024 (UTC)
- I don't think it'll be a great loss to WP:PERM. I'll contribute in places I am more confident and comfortable contributing in.--v/r - TP 02:07, 4 October 2024 (UTC)
- Yes. Back 13 years ago when I was working WP:PERM, we still believed that the encyclopedia was no big deal and we granted tools to users that wouldn't abuse them. I can understand not wanting the user to get excited, but I also don't think the issues raised are significant because they address other Misplaced Pages, and even Wikimedia, goals. You bring up as a point that you feel I was too hasty in granting the permission, but I feel you were too hasty in reverting. As you know, wheel warring will quickly end up at Arbcom. So when one admin reverts another - it's very much "final". It's not like editors reverting in editor space. Typically, we afford each other the courtesy of discussion because of this. It's fine though, I'm no longer interested in helping here.--v/r - TP 21:19, 3 October 2024 (UTC)
- @TParis, I'm surprised to read this, since when I just dropped by your talk page I was greeted by a notice that said
- Other admins talk to each other before reverting admin actions.--v/r - TP 20:36, 3 October 2024 (UTC)
- Sure, I could and should have posted this item first. What I'm saying, though, is that you are clearly acting outside what other admins who are active here are doing. And that is a concern that needed to be raised. Schwede66 20:34, 3 October 2024 (UTC)
- (Non-administrator comment) - not an admin so I won't opine on the matter at hand now, but I think this might be better placed in Misplaced Pages:Administrative action review. Zippybonzo | talk | contribs (they/them) 20:47, 3 October 2024 (UTC)
- I think we are capable of sorting this out here, Zippybonzo. In fact, I'd say it's already sorted (from my perspective it is, at least). Schwede66 20:49, 3 October 2024 (UTC)
- 👍 :) Zippybonzo | talk | contribs (they/them) 20:52, 3 October 2024 (UTC)
- I do appreciate you bringing this up @Schwede66, and I agree with you that discussions don't necessarily need to jump to the bigger venues. No admin is perfect, we all need feedback and to adjust our practices from time to time. Hey man im josh (talk) 00:14, 4 October 2024 (UTC)
- I think we are capable of sorting this out here, Zippybonzo. In fact, I'd say it's already sorted (from my perspective it is, at least). Schwede66 20:49, 3 October 2024 (UTC)
Side note on review speed
Just noting, which is somewhat relevant to this thread but a comment in general: the speed at which an admin acts on requests is not necessarily the speed at which they reviewed them. Take for example WT:AFCP or WP:PERM/AWB, wherein I will regularly spend a good amount of time reviewing all of the editors, then make a single edit to each of the relevant locations to enact all of the requests as necessary. If it were something like WP:PERM/PM, with the script it necessitates multiple edits but the time spent before actioning is still the same.
I'll split this into it's own subsection, as I have not looked into the original speed of review and therefore do not want to say that what I describe above is what happened in the main thread, but more that it's something to consider going forward. Primefac (talk) 13:39, 5 October 2024 (UTC)
- Yeah I think unless it's really extreme, looking at the time between edits/action is a poor way to judge how much attention has been given. How much time I spend on PERM requests varies a lot. Declines can be near-instant if you spot a deal-breaker. Sometimes I'm already familiar with the editor's work from some other context and don't have to spend much time checking again. Sometimes I'll look at a request and mull over it for a day or two before actioning it. Judge the results, not the timestamps. – Joe (talk) 08:26, 31 October 2024 (UTC)
Discussion at Misplaced Pages talk:File mover § Is this page a policy?
You are invited to join the discussion at Misplaced Pages talk:File mover § Is this page a policy?. –Novem Linguae (talk) 21:50, 30 October 2024 (UTC)
How can I request permission again if I already met the requirements
How can I request permission again if I already met the requirements for template editor? I've already met criteria #3, which is to have at least 150 total edits to the Template and Module namespaces. Abhiramakella (talk) 22:49, 29 December 2024 (UTC)
- You simply request them again. But you don't request them just to have them. It'd be preferable if you'd have actually made requests to restricted templates. Hey man im josh (talk) 23:12, 29 December 2024 (UTC)
- Just noting that after their initial request was bot-marked as them only having 106 template edits, they spammed 44 more to hit 150. I consider this gaming, and while I don't see any issue with them requesting in the future, a quick look at their edit requests means they would probably not meet WP:TPEGRANT points 5 or 6 anyway. Primefac (talk) 08:36, 30 December 2024 (UTC)