I recently discovered that the OOUI library, when an input is declared as
"required" (i.e., mandatory), accomplishes this by adding the "required"
parameter to the input, which is an HTML parameter that's part of HTML5.
When "required" is specified, the browser checks the input when the form
gets submitted, and, if it's blank, displays an error message and prevents
It's certainly convenient to be able to use HTML's "required", but I see
some weaknesses with this approach, compared to a built-in MediaWiki
- There is less i18n support. Some browsers have quite impressive language
support - Google Chrome seems to support around 150 languages - but none
have the comprehensiveness of MediaWiki.
- The error message is displayed in the language of the user's browser
settings, rather than in the language they have for the wiki. (Why the two
would be different, I don't know, but it's possible.)
- The display of the error message does not match the OOUI look-and-feel.
Any thoughts about all of these? Was the use of "required" a conscious
decision, or just a matter of convenience?
WikiWorks · MediaWiki Consulting · http://wikiworks.com
my skin uses the global parser in order to render some parts of the
navigation bar via templates (Parser::recursivePreprocess). This works
fine on all normal pages (and even some special ones like
Special:Version), but not on special pages like Special:AllPages.
Some debugging revealed that on Special:AllPages the global parser
object (\MediaWiki\MediaWikiServices::getInstance()->getParser()) is not
properly initialized. Member variables like mOptions and mTitle are null
which results in tons of NPEs.
Any idea why that is? Is that a bug or am I mis-using the parser?
We are having a little trouble with HitCounters and deprecated warnings.
We use extensions and skins from the GitHub mirror to easily pull in
changes on the REL1_36 branch. Tracking a branch like REL1_36 is a lot
easier than manually downloading a zip file with a non-relevant name,
like v4.3.5.zip (especially with 30+ extensions and skins).
HitCounter is stale. The author, @WikiForMen, said he updated the
extension to fix the warnings (see the Talk page). It appears the
changes have not trickled into the GitHub repo. Confer,
Would it be possible to update the HitCounters repo, please?
Thanks in advance.
The 2021 Board of Trustees election is coming soon. Candidates from the
community are needed to fill the available seats.
The Wikimedia Foundation Board of Trustees oversees the Wikimedia
Foundation's operations. Community trustees and appointed trustees make up
the Board of Trustees. Each trustee serves a three-year term. The Wikimedia
community has the opportunity to vote for community trustees.
Wikimedia contributors will vote to fill four seats on the Board in 2021.
This is an opportunity to improve the Board's representation, diversity,
and expertise as a team.
For potential candidates:
- *Traits:* Wikimedia is a global movement and seeks candidates from the
broader community. Candidates should think about what experiences and
perspectives they will bring to the Board. Ideal candidates align with the
Wikimedia mission and are thoughtful, respectful, and community-oriented.
The Board would like to find perspectives and voices that are
under-represented and essential for our movement. They should bring what
Wikimedia needs from a new Trustee.
- *Commitment: *Trustees serve a three-year term and can serve up to
three consecutive terms. The time commitment is about 150 hours per year,
excluding travel. This time is not evenly spread throughout the year. The
time is concentrated around meetings. The expectation is that Trustees
serve on at least one of the Board’s committees.
- *Requirements*: English is the language of business for the Board.
Candidates need a basic understanding of English, but support and training
are part of onboarding. Candidate applications will be translated into
several languages to reach a broad audience of voters.
- *Apply*: Candidates from all projects and communities who meet the
needs of Wikimedia Trustee are welcome. If you know someone who could be a
good trustee, encourage them to run for election. Candidates can find
information and submit their nomination on the Apply to be a Candidate page.
- *Resources*: A toolkit has been developed for community members who
are considering submitting their candidacy for the Wikimedia Foundation
Board of Trustees, and who want to better understand what to expect and how
to prepare for the role.
Thank you for your support,
The Wikimedia Foundation Board of Trustees
Krishna Chaitanya Velaga (he/him)
Board Governance Facilitator, Wikimedia Foundation
The committee has finished selecting new members and the new committee
candidates are (In alphabetical order):
- Amir Sarabadani
- Kunal Mehta
- Martin Urbanec
- Tony Thomas
And auxiliary members will be (Also in alphabetical order):
- Ariel Glenn
- Effie Mouzeli
- Nuria Ruiz
You can read more about the members in the mediawiki.org page
The changes compared to last term are:
- Kunal Mehta is joining the main CoC committee
- Ariel Glenn is coming back to auxiliary committee
- Effie Mouzeli is joining auxiliary committee for the first time
- Tonina Zhelyazkova is leaving the committee
- Matanya and Tpt are leaving the auxiliary committee
- I won't run for the chair this year.
This is not the final structure. According to the CoC
the current committee publishes the new members and calls for public
feedback for *six weeks* and after that, the current committee might apply
changes to the structure based on public feedback.
Please let the committee know if you have any concern regarding the members
and its structure until *26 May 2021* and after that, the new committee
will be in effect and will serve for a year.
Amir, On behalf of the Code of Conduct committee
There will be a MediaWiki Stakeholders' Group  meeting this Friday
(04JUN) at 15:30-16:30 GMT / 08:30-09:30 PDT / 11:30-12:30 EDT /
17:30-18:30 CET / 15:30-16:30 UTC. Meeting information is linked at .
Topics of discussion will be:
1) MediaWiki News
* What's new in MediaWiki
* Phabricator EOL
* MW 1.36 release
2) MWStake Membership Discussion
* Eric-Jan from Wikibase Solutions will discuss the benefits of joining
3) Welcome Adam Shoreland (Addshore) to the MWStake Board
4) Kubernetes Workshop tool
Feel free to come and listen, ask some questions, or add a topic to the