I tried to update a dead link under MediaWiki-Vagrant#Authoring roles and got directed here. Perhaps links to the Puppet website should be whitelisted? Or is there some other procedure for adding Puppet links I'm unaware of?
Agreed that puppet links should be exempted from that abuse filter. I've made the edit, and for what it's worth you've now made enough edits to MediaWiki.org that further attempts to add links or modify links should succeed.
A vote in SecurePoll from 7 to 21 March 2022 is scheduled as part of the ratification process for the Universal Code of Conduct (UCoC) Enforcement guidelines. Eligible voters are invited to answer a poll question and share comments. Read voter information and eligibility details. During the poll, voters will be asked if they support the enforcement of the Universal Code of Conduct based on the proposed guidelines.
There are events scheduled to learn more and discuss:
A community panel recorded on 18 February 2022 shares perspectives from small- and medium-sized community participants.
The Movement Strategy and Governance (MSG) team is hosting Conversation Hours on 4 March 2022 at 15:00 UTC. Please sign-up to interact with the project team and the drafting committee about the updated enforcement guidelines and the ratification process. See the Conversation Hour summaries for notes from 4 February 2022 and 25 February 2022.
You can comment on Meta-wiki talk pages in any language. You may also contact either team by email: msgwikimedia.org or ucocprojectwikimedia.org
Sincerely,
Movement Strategy and Governance
Wikimedia Foundation
Hello. I am new to MediaWiki. I cant't edit the page above because Clump decided to protect that page. Will you temporarily unprotect it for 1 hour please? Thank you if you help me! --Fragguni9989 (talk) 02:14, 25 February 2022 (UTC)
I am writing to provide an update on the improvements to the MediaWiki maintenance script documentation on mediawiki.org, as well as to ask you to fill out a survey that will help us to understand these improvements better.
Project Pralekhan is a documentation project under which MediaWiki's maintenance script documentation is being improved. Under this project, I have documented 134 scripts so far. Apart from this, the main landing page for maintenance scripts has been improved with a sidebar for easier navigation.
If you are a developer or admin involved in running and maintaining a MediaWiki site, we kindly ask you to respond to this survey by 3 March 2022 (UTC):
Your response is highly appreciated. Your input plays a key role in the analysis and recommendations to ensure more improvements to MediaWiki maintenance scripts.
I have translated 11 strings of total 15 strings of Template:Bundled to Finnish. Page Template:Bundled/fi still doesn't exist, despite the first translations made by me on 5 February and the display title string have also been translated since 5 Feb. Why doesn't it still exist?
The issue is that <translate> tags are used inside JSON content (templatedata), which is not safe. You can avoid issues with <translate nowrap>, but that isn't fully safe either.
I've added all the existing translations to templatedata directly. I haven't marked the page for translation yet in case someone wants to double-check (since marking for translation would delete the units). But otherwise it should fix the problem once it gets marked for translation.
We should find other instances of translate tags inside templatedata, and be sure the relevant people adding those tags are aware of the problem. cc @Wladek92, @Shirayuki
Would it be a good idea to write a Lua module than converts translations from the form the Translate extension produces to the form TemplateData expects?
If I'm not mistaken, such module would require to fetch individual translations from all languages the page has been translated to. That would be one expensive call per language per unit, where we have one unit per parameter and one for the template alone. This can quickly escalate to the current limit of costly calls, which is 500.
I haven't marked the page for translation yet in case someone wants to double-check (since marking for translation would delete the units).
The unit pages themselves aren’t automatically deleted, e.g. Translations:Template:Bundled/11/fi still exists, so reverting the edits would restore the translations (although as far as I remember, fuzzy state is lost when the unit is removed and later re-added).
That would be one expensive call per language per unit, where we have one unit per parameter and one for the template alone.
Somewhat silly, but I think template transclusion doesn’t count to that limit (there are other limits on template transclusion, though). So going through all languages, trying to transclude the translations and catching the exception if it doesn’t exist could actually work without reaching the limit. (Although it could make sense to go through the languages, check with #ifexist’s Lua equivalent if the template itself (not a translation unit) exists in that language, and going through only the translation units that may realistically exist. This way we go over 300 languages only once, the rest of the loops go over only the existing few or few dozen languages.)
A policy regarding the removal of "advanced permissions" (administrator, bureaucrat, interface administrator, etc.) was adopted by global community consensus in 2013.
While this wiki was initially excluded, this community decided in August 2020 to explicitly opt-in. Accordingly, the stewards are reviewing the activity of the accounts with advanced permissions based on the admin activity review policy.
We have determined that the following users meet the inactivity criteria (no edits and no logged actions for more than 2 years):
These users will receive a notification soon in their talk pages, asking them to start a community discussion if they want to retain some or all of their current advanced permissions. If the users do not respond, then their advanced permissions will be removed by the stewards without further notice after one month of the notification.
Please let us know at the stewards' noticeboard on Meta-Wiki if you have any questions or concerns.
Greetings from Wiki Loves Folklore International Team,
We are pleased to inform you that Wiki Loves Folklore an international photographic contest on Wikimedia Commons has been extended till the 15th of March 2022. The scope of the contest is focused on folk culture of different regions on categories, such as, but not limited to, folk festivals, folk dances, folk music, folk activities, etc.
We would like to have your immense participation in the photographic contest to document your local Folk culture on Wikipedia. You can also help with the translation of project pages and share a word in your local language.
Hello. I wanted to give you an update about the Desktop Improvements project, which the Wikimedia Foundation Web team has been working on for the past few years.
The goals of the project are to make the interface more welcoming and comfortable for readers and useful for advanced users. The project consists of a series of feature improvements which make it easier to read and learn, navigate within the page, search, switch between languages, use article tabs and the user menu, and more.
The improvements are already visible by default for readers and editors on 24 wikis, including Wikipedias in French, Portuguese, and Persian.
User menu - focused on making the navigation more intuitive by visually highlighting the structure of user links and their purpose.
Sticky header - focused on allowing access to important functionality (logging in/out, history, talk pages, etc.) without requiring people to scroll to the top of the page.
For a full list of the features the project includes, please visit our project page. We also invite you to our Updates page.
The features deployed already and the table of contents that's currently under development
If you think this would be good as a default for all readers and editors of this wiki, feel free to start a conversation with the community and contact me.
On wikis where the changes are visible by default for all, logged-in users can always opt-out to the Legacy Vector. There is an easily accessible link in the sidebar of the new Vector.