Hey there! This is to let you know that phase I of the 2024 requests for adminship (RfA) review is now no longer accepting new proposals. Lots of proposals remain open for discussion, and the current round of review looks to be on a good track towards making significant progress towards improving RfA's structure and environment. I'd like to give my heartfelt thanks to everyone who has given us their idea for change to make RfA better, and the same to everyone who has given the necessary feedback to improve those ideas. The following proposals remain open for discussion:
Proposals 3 and 3b, initiated by Barkeep49 and Usedtobecool, respectively, provide for trials of discussion-only periods at RfA. The first would add three extra discussion-only days to the beginning, while the second would convert the first two days to discussion-only.
Proposal 5, initiated by SilkTork, provides for a trial of RfAs without threaded discussion in the voting sections.
Proposals 6c and 6d, initiated by BilledMammal, provide for allowing users to be selected as provisional admins for a limited time through various concrete selection criteria and smaller-scale vetting.
Proposal 7, initiated by Lee Vilenski, provides for the "General discussion" section being broken up with section headings.
Proposal 9b, initiated by Reaper Eternal, provides for the requirement that allegations of policy violation be substantiated with appropriate links to where the alleged misconduct occured.
Proposals 12c, 21, and 21b, initiated by City of Silver, Ritchie333, and HouseBlaster, respectively, provide for reducing the discretionary zone, which currently extends from 65% to 75%. The first would reduce it 65%–70%, the second would reduce it to 50%–66%, and the third would reduce it to 60%–70%.
Proposal 13, initiated by Novem Lingaue, provides for periodic, privately balloted admin elections.
Proposal 14, initiated by Kusma, provides for the creation of some minimum suffrage requirements to cast a vote.
Proposals 16 and 16c, initiated by Thebiguglyalien and Soni, respectively, provide for community-based admin desysop procedures. 16 would desysop where consensus is established in favor at the administrators' noticeboard; 16c would allow a petition to force reconfirmation.
Proposal 16e, initiated by BilledMammal, would extend the recall procedures of 16 to bureaucrats.
Proposal 17, initiated by SchroCat, provides for "on-call" admins and 'crats to monitor RfAs for decorum.
Proposal 25, initiated by Femke, provides for the requirement that nominees be extended-confirmed in addition to their nominators.
Proposal 27, initiated by WereSpielChequers, provides for the creation of a training course for admin hopefuls, as well as periodic retraining to keep admins from drifting out of sync with community norms.
To read proposals that were closed as unsuccessful, please see Wikipedia:Requests for adminship/2024 review/Phase I/Closed proposals. You are cordially invited once again to participate in the open discussions; when phase I ends, phase II will review the outcomes of trial proposals and refine the implementation details of other proposals. Another notification will be sent out when this phase begins, likely with the first successful close of a major proposal. Happy editing! theleekycauldron (talk • she/her), via:
You are receiving this message because you previously participated in the UCoC process.
This is a reminder that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) ends on May 9, 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.
Please share this message with members of your community so they can participate as well.
Hi there! Phase I of the Wikipedia:Requests for adminship/2024 review has concluded, with several impactful changes gaining community consensus and proceeding to various stages of implementation. Some proposals will be implemented in full outright; others will be discussed at phase II before being implemented; and still others will proceed on a trial basis before being brought to phase II. The following proposals have gained consensus:
I have a very clear notice that states you are not to edit my user page unless you are me. Do not edit the user pages of other editors. Thank you. 9t5 (talk) 12:31, 1 July 2024 (UTC)[reply]
Per WP:UOWN: pages in user space belong to the wider community. They are not a personal homepage, and do not belong to the user. They are part of Wikipedia, and exist to make collaboration among editors easier – making the collaboration easier includes avoiding polluting the maintenance categories, such as Wikipedia substituted templates.
Other popular issues on user pages to avoid:
misuse of HTML and wikitext causing so called lint errors
pollution of the category tree of User namespace templates due to copy-pasting of wikitext, which most often happens with userboxes.
Hey, I noticed you're an active editor, perhaps you can help me out. How can I have a template call a specific string from a given article using the start and end position number of the string (which I get using the findpagetext function)? JoeJShmo💌03:56, 26 July 2024 (UTC)[reply]
Say the Monkeys page has a 10 character string that is placed 150 characters - 160 characters from the start of the article. How can I call that line to my template? Say I wanted to use that line as a string in a function, how would I do that? JoeJShmo💌08:39, 26 July 2024 (UTC)[reply]
JoeJShmo, this is a strange thing to want to do in a Wikipedia article, that's why I asked for a clarification.
Sure, I'm happy to explain. I have a template for the lead of a specific kind of article that is written about every president of the U.S., and I want the template to automatically grab certain information from the main page of the president, such as the file for his signature and his years in office. I can get the position of these bits of information using the findinpage function, but I don't know how to actually call the information itself. JoeJShmo💌08:58, 26 July 2024 (UTC)[reply]
It's a template designed to work for every president. The point of the template is to automate the information and to avoid copy-pasting. I believe I'm to understand that you don't know how to implement my request, and that's fine. Thanks for the response, and for the wikidata info! JoeJShmo💌10:22, 26 July 2024 (UTC)[reply]
JoeJShmo, I do know, but I'm choosing not to tell you, because you shouldn't try to make such a template by parsing pages in the way you've described in the first message. If the template is needed on many pages, years can stored as data in a template or a Lua module.
Interesting. Can you explain why? Also, it isn't feasible to store all the information in the template, as every article needs different information to be parsed. JoeJShmo💌10:57, 26 July 2024 (UTC)[reply]
Because it's brittle and hard to maintain. There are more robust and maintainable alternatives.
I'm not sure its that brittle. I suppose it depends how you write it. The function I wrote checked for the signature using the signature parameter in the infobox. JoeJShmo💌20:55, 26 July 2024 (UTC)[reply]
Hey there, welcome to the 25th issue of the Wikipedia Scripts++ Newsletter, covering all our favorite new and updated user scripts since 1 March 2024. We've got a ton of wonderful editors taking back their pitchforks today. Don't worry, for they come in peace, to forcibly fix and extend existing scripts you use with sheer passion. There's so many, them forks have got what's basically their own column now! gift us with some rows before it's too late Aaron Liu (talk) 04:00, 1 August 2024 (UTC)[reply]
Got anything good? Tell us about your new, improved, old, or messed-up script here!
To a lesser extent, the same goes for PrimeHunter/Search sort. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
An easily configurable script to add a link to the #p-vector-user-menu-overflow portlet with a name, target, and icon. This one should be a relatively easier one. I would do it myself, but I'm too busy rotting away on Celeste (video game).
After the RIIJ update, Aaron Liu: Watchlyst Greybar Unsin has a dismiss button that allows you to mark an item as read in one click and cycle to the next Watchlist item.
Lordseriouspig/StatusChangerImproved is just like Enterprisey's script, except you select your status from a dropdown instead of cycling through them with a button. The WMF operates out of car-centric infrastructure anyway. Shame!
Aaron Liu has created Duplinks from Evad37/duplinks-alt; his fork adds a config variable to automatically highlight duplicate links on the loading of any page where the portlet link would've appeared.
Tired of staring at a bunch of filtering text and waiting for darn filter logs to load? Msz2001/AbuseFilter analyzer can parse abuse filters into a visual syntax tree and evaluate locally on-demand!
Polygnotus/DuplicateReferences finds references with the same link and displays the number of them along with a button to add the {{duplicated citations}} tag under the references section. Being lazy has never been easier!
fastest gun on the net Ponor/really-quick-block really quick add to contribution lists three buttons awesome