I'm currently working on upgrading some wikis to Mediawiki 1.31, and
I've been reading the manual on extension dependencies. It is clearly
that skins can be required with the key "skins", however looking at git
and the change in gerrit, the key is actually implemented as "skin"
The change in itself is inconsistent, as it adds both documentation and
actual code which are not compatible to each other.
I've been wondering if it is just the documentation being wrong or the
key being typo'd ever since 1.29, considering the extensions dependency
key is inplural I'd tend to think the key is typo'd ever since 1.29.
Question would then be how to resolve this. The best way would probably
be to deprecate the "skin" key and implement "skins" as a key, and
remove "skin" with the next major release (1.32), as I don't think the
actual behaviour should be changed mid-release.
Alex "FO-nTTaX" Winkler
Head of Liquipedia Development
https://liquipedia.net/ - https://www.teamliquid.com/
The Wikimedia Foundation Technology department is seeking feedback
regarding your current and future use of the Beta Cluster.
The anonymized results of this survey will be used by the Wikimedia
Foundation Technology department to inform future decisions.
This survey will be conducted via a third-party service, which may subject
it to additional terms. For more information on privacy and data-handling,
see the survey privacy statement.
Please help us improve the Beta Cluster by filling out this quick survey:
This survey will be open until June 15th, 2018.
Wikimedia Foundation - Technology
That time is finally upon us. 
On 6 July 2017, we made an announcement  about our plans to replace
Tidy with RemexHtml on the Wikimedia cluster.
Over the last year, we have progressively replaced Tidy on about 800
wikis in a phased manner. 
A year later, as announced and planned, on 5 July 2018, the last 100 or
so wikis  will have Tidy replaced to complete this transition. 
If you are an editor of one of these last remaining wikis, we have a
query  which gives you counts of linter issues in the main namespace
that might need fixing.
Many thanks to all the hundreds of editors on all the wikis who have
been fixing markup on pages and templates. You have enabled us to do
this much-required upgrade of a key part of our core technical platform
with the minimum of disruption to readers.
If you have any questions or concerns, please leave a comment on the
relevant Phabricator ticket  or leave a message on mediawiki.org. 
 List of wikis that will get Tidy replaced on 5 July 2018:
af an ar as ast av az azb ba be bn bpy ce ckb cy
da diq el en eo es eu fr fy gd gu hak hi hr hu hy
id ja ka kk kn koi kv lrc lv mg mk ml mr ms myv nah nn
oc pam pl pnb pt ro roa_rup sd sh simple sl sr su sw
ta te tg th tr tt ug uk ur vi xmf yi yo zh zh_min_nan zh_yue
bg eo eu fr io ka lt mn ru th uz wa
ar en fa fr he ru sa sl sr sourceswiki
Hello everyone, sorry for cross-posting.
What does your participation on the Wikimedia projects look like? Do you
edit articles? Upload files? Patrol vandalism? Translate articles?
Translate interface messages? Do you organize people, online or offline? Do
you train new editors, or new trainers? Do you write code?
There are many different ways to contribute to Wikimedia – more than you
would expect just from reading Wikipedia articles. With many kinds of
contributions there are many tools you can use, most of which have been
developed by our volunteer community. But do you know how to find these
Since January the Wikimedia Cloud Services team at the Wikimedia Foundation
has been meeting with contributors, organizers, and tool developers to
learn more about the role tools play in our communities' work. We have also
been researching existing methods for organizing lists of tools – at least
14 of them, including popular tool catalogs like Hay's Tool Directory.
With this research, we hope to figure out how best to put the right tools
in front of the right people.
For this, we need your help. We have a page on Meta summarizing our current
work, as well as a proposed data model for describing tools. Consider
what work you currently do, whether you contribute content, code,
organizing support, what have you – and ask: if there was a tool you needed
to complete a certain task, would you know where to look? How would you
look for it? Please look over  and  and let us know what you think.
Feedback is welcome in any language. If you would like to get in touch
privately, you are also welcome to email me at jhare(a)wikimedia.org.
Associate Product Manager
We, the Wikimedia Technical Committee (TechCom), are looking for two new members
to broaden the committee’s area of expertise. If you can think of anyone
(including yourself) who may be a good addition to TechCom, please read on, here
or on the wiki .
TechCom is the guardian of the integrity, consistency, stability, and
performance of all software supporting the Wikimedia projects. It acts as the
senior advisor and the convergence point of all decisions related to technical
work that is strategic, cross-cutting, and/or hard to undo .
Traditionally, TechCom members have mainly been experts for MediaWiki core. We
have been slowly growing the committee to get a broader perspective, and now
want to try harder to cover our blind spots by starting this nomination process.
Some areas of expertise that we hope new members would bring to the table
include: internationalization, deployment and releases, mobiles apps, security,
performance, and analytics. We are also interested in expertise in areas at the
fringes of TechCom’s scope, such as privacy, interaction design, and bug wrangling.
Of course, we will not be able to cover all these areas perfectly with the
addition of just two people and we will likely expand the size of the committee
further in the future. For now however, we want to be careful to not to grow the
committee too quickly, so that we have time to adjust existing processes to a
TechCom members are expected to be available at least 4 hours per week for
committee work. This includes meetings, administrative work, and technical work
, and also taking care of the RFC process . As we evolve the committee to
become more proactive, we also expect to spend more time drafting and discussing
guidelines and policies.
You can find the list of current members on the TechCom page . If you would
like to join, or want to nominate somebody else, please send an email to
<techcom(a)wikimedia.org> by June 18 with “Nomination for <name>” in the subject
line. The email should contain an overview of the nominee’s skill set and
experience as well as a short pitch explaining why this person would be a good
addition to TechCom.
Nominations are now open until June 18, 2018; and we will review the submissions
and vet the potential new members over the following weeks. We hope that we can
announce new members before the end of July.
Chair of the Wikimedia Technical Committee
Principal Platform Engineer
Gesellschaft zur Förderung Freien Wissens e.V.