Wikipedia:Requests for permissions/Template editor

This is an old revision of this page, as edited by AirshipJungleman29 (talk | contribs) at 10:50, 6 August 2025 (+). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template editor

Howdy. I'm an active participant over at WP:DYK, and recently ran in WP:AELECT but did not pass the threshold. Discussion centered around lack of experience on WP:AIV, an area I expressed interest in getting involved in. A decent part of my running for adminship was wanting to help with processing WP:DYK queues, which are template-protected. In my election discussion there were no concerns raised about my professionalism, content creation or reviewing competency, which are the primary things needed with processing DYK queues. I do not meet some of the standard template editor guidelines (e.g. sandbox/significant template edits, etc), but I also do not plan on using the role outside of DYK queue processing. Thanks for your consideration. ~Darth StabroTalk • Contribs 16:46, 1 August 2025 (UTC)[reply]

Are there any active DYKers that you are working with often that could leave support here? — xaosflux Talk 19:14, 1 August 2025 (UTC)[reply]
I've seen Darth around at DYK but don't have the impression they're really one of the regulars. Looking over their contribution history I only see 33 hook promotions going back about 4 months (at least based on searching for PSHAW log messages). And looking through the WT:DYK archives, I'm seeing some consistent level of activity over the past 8 months, but not a huge volume compared to a few of the people that I would consider our major contributors to the behind-the-scenes DYK work, reinforcing my initial impression. Also, most of what I'm seeing (in an admittedly unscientific spot check) is routine participation in discussions; I haven't found any examples of complicated situations where they've had to carefully navigate contentious issues. In short, I'm not seeing any problems per-se, but I'm also not seeing the depth of experience and quality time in the trenches that an advanced permission like TE requires. We can certainly use more qualified hands at DYK, but I'd rather see Darth get more experience promoting hooks, managing the prep areas, and making tough decisions when nominators push hard for their own desired outcomes, before moving up to working on the queues. RoySmith (talk) 09:33, 6 August 2025 (UTC)[reply]
As someone who has worked with Darth Stabro in the past on DYK and is familiar with his work, I would support him getting the permission. He is a DYK regular and is familiar with the ins-and-outs of the project. Plus, we're short on hands, and more people being able to work with Queues is a plus in our eyes. Narutolovehinata5 (talk · contributions) 08:51, 6 August 2025 (UTC)[reply]
We do need more people to contribute to queueing, but Darth Stabro has so far promoted only 32 hooks, equal to three and a half Main Page sets. I'd prefer to see significantly more experience in prep sets, perhaps a hundred hooks promoted or more, to demonstrate "a need for the right". In RfA terms, NOTYET. ~~ AirshipJungleman29 (talk) 09:39, 6 August 2025 (UTC)[reply]
@RoySmith @AirshipJungleman29 Putting the question another way, do you see a reason why DeathStarbo should not get the rights? WP:TPEGRANT only requires working the sandbox of three template-protected pages and successfully proposing five significant edits to template-protected templates. I'm not at all involved with DYK, but 32 promotions sounds like more than equivalent to that. – SD0001 (talk) 10:31, 6 August 2025 (UTC)[reply]
Well yes, as I said above, I'd prefer that they should get more experience. You can do 32 promotions in ten minutes if you don't take care, but in queueing sets the highest priority is taking care. (You also, incidentally, need to be familiar with the entirety of WP:DYKCRIT, WP:DYKRI and WP:DYKAI, and I'm not sure you can do that by promoting three-and-a-half sets.) ~~ AirshipJungleman29 (talk) 10:48, 6 August 2025 (UTC)[reply]