I am writing to you to let you know the voting period for the Universal Code of Conduct Coordinating Committee (U4C) is open now through 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! I've been doing a lot of work lately on gadgets, and I find myself wanting to create documentation pages for specific gadgets. I created ProveIt and MiniEdit already, but would like to create several more which are currently redirects (OWIDPopup, Vivarium, Formicarium, ExcerptTreeDownloadPDF, InlineSearch), and more. I could create them and categorize them and be done, but I'm thinking it would be neater to have a "Gadget" namespace or pseudo-namespace, similar to "Extension" and "Skin". What do you think? Are pseudo-namespaces frowned upon? Can a proper "Gadget" namespace be defined? Would it create a problem if the "Gadget" and "Gadget definition" namespaces of Extension:Gadgets ever get enabled in MediaWiki.org? Thanks!
The use case for these namespaces (Gadgets 2.0) has not gone away, and is still actively being worked on. But, the latest version of MediaWiki no longer requires custom namespaces to implement them, we have content models instead. Which means if/when Gadgets 2.0 gets completed and deployed to mediawiki.org (which I hope it does!), it will not clash with these documentation pages.
In February earlier this year, I have updated the Gadgets extension to completely remove these namespace definitions, thus making it clear that is no longer reserved in any way.
Thanks a lot for the pointer. I was already wondering who may be permitted to change the interwiki. I just added the request at m:Talk:Interwiki_map#usemod as a service for you to work on once you have the required permissions.
I tried to fix a broken link on this page Professional development and consulting at an external link that goes to Yaron Koren's Working with Mediawiki book but it returned an error, please how do i fix it?
Thanks @Wladek92, i have already begun doing that, thankfully the documentations are quite detailed, but i would appreciate some help fixing this...if you have pointers i would be happy if you can share
I can't translate "Developers wanting to install MediaWiki locally to have an environment for development of MediaWiki core or extensions should also read How to become a MediaWiki hacker for further instructions." from the Download page. What should I do?
Hi there, I've been trying to implement namespace-removal for {{Ll}}'s translated link names. You can see a problem at User:Aaron Liu/sandbox. The first line produces a blank, while the second line, which is just the first line's both cases substituted, produces its stuff correctly. What's wrong here?
Yes, due to improper conversion when the UI language differs from the language to convert to in certain cases such as Special:Permalink/5860177. Other reasons include the desire for translation units to be independent of each other.
Category:Pages using deprecated NoteTA template claims that {{NoteTA}} is deprecated and to use {{LC zh}} instead. But the latter requires repetitively adding conversions for the same thing, while the former replaces every instance while being able to include common conversions.
@Winston Sung Pardon the ping, but do you know why it's deprecated?
The tracking category was added to Module:NoteTA, with only the comment "Add tracking category", by 122.100.88.89(talk·contribs) on February 25, and the same IP then created the category a few minutes later, without comment.
@122.100.88.89: can you explain the reasoning for this unilateral and undiscussed (as far as I can see) deprecation?
@Aaron Liu: It is because NoteTA would mess up translation memories, so to ensure the translation memory can provide correct results with proper language conversion, always specify the translation for different variants.
Oh wait, the translation memory means the one on the right, doesn't it? Would it still be messed up if every page used NoteTA?
Edit: Thanks Winston for confirming the former. But does being messed up mean it displays improperly or wouldn't convert like the original page? In the latter case, would using NoteTA on these pages too solve that?
Would it still be messed up if every page used NoteTA?
The problem would still exist:
NoteTA being place on one of the translation unit on a page, causing page-dependent NoteTA template transclusions showing up in different translation units' translation suggestions.
NoteTA cannot always placed in the first translation unit of a page due to different types of translation units (e.g., syntaxhighlight, template parameters like the Localized_link template).
Translators ignore the one-to-multi conversion and use the translation suggestion with broken language conversion result.
NoteTA template being used in templates causing duplicated page status indicator
The Main Page has been migrated to LC zh, but here's a brief explaination:
Conversion-zh use UI-language-only detection and output respective variant contents.
If users view the template (usually by clicking the "other language" link) while there are inconsistency between the output language (UI language, the 'en' when not logged in would output 'zh-hans') and the variant language ('zh-Hant-TW' / 'zh-tw'), it will give out incorrect conversion results (e.g., '信息' vs. '資訊').
At this case, you can neither add NoteTA (as it will become many directly-exposed '-{H' tags) nor using native syntax (same reason).
As you can see, most of them were to ensure all translation units having consistency, always giving correct conversion results independently (instead of relying on other translation units with NoteTA).
Could Module:Used by/data.json be adjusted to include the RealMe extension in the Miraheze portion? I have tried to do it myself, but I am filtered by "Operator873's Filter". This was confirmed by a Miraheze engineer in their Discord. Unfortunately, I am unable to link to that discussion without being filtered. ~~~~
This year, the term of 4 (four) Community- and Affiliate-selected Trustees on the Wikimedia Foundation Board of Trustees will come to an end [1]. The Board invites the whole movement to participate in this year’s selection process and vote to fill those seats.
The Elections Committee will oversee this process with support from Foundation staff [2]. The Board Governance Committee created a Board Selection Working Group from Trustees who cannot be candidates in the 2024 community- and affiliate-selected trustee selection process composed of Dariusz Jemielniak, Nataliia Tymkiv, Esra'a Al Shafei, Kathy Collins, and Shani Evenstein Sigalov [3]. The group is tasked with providing Board oversight for the 2024 trustee selection process, and for keeping the Board informed. More details on the roles of the Elections Committee, Board, and staff are here [4].
Here are the key planned dates:
May 2024: Call for candidates and call for questions
June 2024: Affiliates vote to shortlist 12 candidates (no shortlisting if 15 or less candidates apply) [5]
June-August 2024: Campaign period
End of August / beginning of September 2024: Two-week community voting period
October–November 2024: Background check of selected candidates
Board's Meeting in December 2024: New trustees seated
Learn more about the 2024 selection process - including the detailed timeline, the candidacy process, the campaign rules, and the voter eligibility criteria - on this Meta-wiki page, and make your plan.
Election Volunteers
Another way to be involved with the 2024 selection process is to be an Election Volunteer. Election Volunteers are a bridge between the Elections Committee and their respective community. They help ensure their community is represented and mobilize them to vote. Learn more about the program and how to join on this Meta-wiki page.
Best regards,
Dariusz Jemielniak (Governance Committee Chair, Board Selection Working Group)
[5] Even though the ideal number is 12 candidates for 4 open seats, the shortlisting process will be triggered if there are more than 15 candidates because the 1-3 candidates that are removed might feel ostracized and it would be a lot of work for affiliates to carry out the shortlisting process to only eliminate 1-3 candidates from the candidate list.