Below are some recent highlights from the wikiverse.
Here is a Phabractor ticket regarding the showcase from Wikimedia Hackathon
2018 in Barcelona: https://phabricator.wikimedia.org/T195219
Here is the Wikidata report from the May 2018 issue of *This Month in GLAM*:
https://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2018/Contents/Wikid…
What's making you happy this week? You are welcome to comment in any
language.
On a personal note: this week I am planning to take a few days offline. If
someone else would start a "What makes you happy this week?" thread during
next weekend, I would be grateful.
Have a good week ahead.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
Hey,
In the past couple of days, the committee has been asked about whether the
CODE_OF_CONDUCT.md should exist in mediawiki extension and skins repos[1].
We had a meeting and the resolution is output of that meeting. [2] Feel
free to comment and give us feedback about it on its talk page :)
[1]: https://phabricator.wikimedia.org/T165540
[2]:
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Tenure_April2018/R…
Sincerely,
Amir on behalf of the Code of conduct committee
Hello together,
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
stated at
https://www.mediawiki.org/wiki/Manual:Extension_registration#Requirements_(…
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"
https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/250060/33/includes/regi….
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[0].
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[1].
Please help us improve the Beta Cluster by filling out this quick survey:
https://goo.gl/forms/XgIxXiSi1G5eVHbp2
This survey will be open until June 15th, 2018.
Thanks!
Jean-René Branaa
Wikimedia Foundation - Technology
[0] https://www.mediawiki.org/wiki/Beta_Cluster
[1]
https://wikimediafoundation.org/wiki/Beta_Cluster_Survey_Privacy_Statement
Hi everyone,
I am a Ujjwal, contributor from Commons Android App team. As a part of my
internship project, I was working on search images feature in Commons app
in Phase 1 of my Internship (GSoC 2018). I am attaching a prodDebug APK for
the same. Feel free to create an issue regarding any bugs or feature
request that you have at our GitHub repository
<https://github.com/commons-app/apps-android-commons/>.
APK Link:
https://drive.google.com/file/d/1THe_I3PRixktLQcOSMMvzymLhHN6_ERq/view?usp=…
Thanks
Ujjwal Agrawal
Hello all!
Several patches related to multi-content[1] revisions landed on master today.
The big ones are:
* https://gerrit.wikimedia.org/r/c/mediawiki/core/+/405015
* https://gerrit.wikimedia.org/r/c/mediawiki/core/+/406595
* https://gerrit.wikimedia.org/r/c/mediawiki/core/+/416465
These patches *should* by themselves not change any behavior. All new features
are still disabled, new database tables are not used yet.
We plan to have these on testwiki for more than a week before they go live with
the train in the week of the 25th. We made a plan with releng for this[2].
Deployment to testwiki (group0) will probably happen tonight.
Until then, the new code can already be tested on the beta cluster. We did
extensive manual testing beforehand on a dedicated vps. Test logs are available
at [3].
If you find any problems, please file tickets on phabricator and tag them with
the #Multi-Content-Revisions project.
Overall progress of the MCR storage layer deployment ins tracked on phabricator
[4]. Next steps will be to further refactor the code that is now in the
(intermediate/internal) DerivedPageDataUpdater class, and to change core code to
use the new interfaces. We will also look into providing alternatives to several
of the hook points triggered during page edits.
Cheers,
Daniel
[1] https://www.mediawiki.org/wiki/Requests_for_comment/Multi-Content_Revisions
[2] https://phabricator.wikimedia.org/T196585
[3]
https://www.mediawiki.org/wiki/User:Daniel_Kinzler_(WMDE)/MCR-StorageLayerT…
[4] https://phabricator.wikimedia.org/T174044
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
\o/\o/ff
Hello everyone,
That time is finally upon us. [1]
On 6 July 2017, we made an announcement [2] 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. [3]
A year later, as announced and planned, on 5 July 2018, the last 100 or
so wikis [6] will have Tidy replaced to complete this transition. [3]
If you are an editor of one of these last remaining wikis, we have a
query [4] 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 [3] or leave a message on mediawiki.org. [5]
Thanks,
Subbu.
[1] https://www.mediawiki.org/wiki/Parsing/Replacing_Tidy
[2]
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2017-July/001625…
[3] https://phabricator.wikimedia.org/T175706
[4] https://quarry.wmflabs.org/query/27652
[5] https://www.mediawiki.org/wiki/Talk:Parsing/Replacing_Tidy
[6] List of wikis that will get Tidy replaced on 5 July 2018:
Wikipedias
----------
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
Wiktionaries
------------
bg eo eu fr io ka lt mn ru th uz wa
Wikibooks
---------
en fr
Wikisources
-----------
ar en fa fr he ru sa sl sr sourceswiki
Others
------
commons incubator
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
tools?
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.[0]
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,[1] as well as a proposed data model for describing tools.[2] 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 [1] and [2] 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.
Best regards,
James Hare
[0] https://tools.wmflabs.org/hay/directory/
[1] https://meta.wikimedia.org/wiki/Toolhub
[2] https://meta.wikimedia.org/wiki/Toolhub/Data_model
----
James Hare
Associate Product Manager
Wikimedia Foundation
https://wikimediafoundation.org
Dear all,
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 [2].
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 [1].
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
larger group.
TechCom members are expected to be available at least 4 hours per week for
committee work. This includes meetings, administrative work, and technical work
[1], and also taking care of the RFC process [4]. 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 [3]. 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.
Daniel Kinzler,
Chair of the Wikimedia Technical Committee
[1] https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Charter
[2]
https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Call_for_Nomin…
[3] https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee
[4] https://www.mediawiki.org/wiki/Requests_for_comment/Process
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.