Based on comments that I received on Wikimedia-l, I would like to invite
people to a casual online meetup one hour before the monthly WMF Metrics
and Activities Meeting.
There will be no set agenda. You can come with questions or ideas that you
would like to discuss. Please be willing to listen to questions and ideas
from other Wikimedians.
I will host the meeting with the Zoom software. You can join with software
or by using your phone. If you join by phone then your phone number will be
visible to other participants.
The primary language of the meeting will be English, but if people would
like to communicate in diverse languages then that is okay too. We can
facilitate translation by text chat. Many Wikimedians, myself included, are
multilingual in varying degrees, so we might try to have live
Here is information about how to connect:
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/136978210
Or iPhone one-tap :
Dial (for higher quality, dial a number based on your current
Argentina: +54 341 512 2188
Australia: +61 (0) 2 8015 2088 or +61 (0) 8 7150 1149
Canada: +1 647 558 0588
Hong Kong, China: +852 5808 6088
France: +33 (0) 1 8288 0188 or +33 (0) 7 5678 4048
Germany: +49 (0) 30 3080 6188 or +49 (0) 30 5679 5800
Israel: +972 (0) 3 978 6688
Italy: +39 069 480 6488
Japan: +81 (0) 3 4578 1488 or +81 524 564 439
Mexico: +52 229 910 0061 or +52 554 161 4288
Spain: +34 84 368 5025 or +34 91 198 0188
Sweden: +46 (0) 7 6692 0434 or +46 (0) 8 4468 2488
Russia: +7 495 283 9788
United Kingdom: +44 (0) 20 3051 2874 or +44 (0) 20 3695 0088
US: +1 408 638 0986 or +1 646 558 8665
Meeting ID: 136 978 210
International numbers available: https://zoom.us/u/ekaPibJIy
The first "Wikimedia Café" meetup will be on 30 August 2018, at 17:00 UTC /
Let me emphasize that the environment won't be like this
so please don't feel intimated if you are nervous about public speaking.
(If a conversation feels to me like it is becoming uncivil or intimidating,
then I will ask the debaters to quiet themselves or to move to somewhere
else.) The meeting will generally have an environment that is more like this
I anticipate that few people will come, which is okay. I hope that if you
come then you will enjoy the environment and conversation.
Until next time,
( https://meta.wikimedia.org/wiki/User:Pine )
I've been meaning to document this for a while.
If you're finding yourself visiting Special:Export/Import often for the
purpose of MediaWiki development there is a much better way to get content
into your local wiki for testing purposes.
This short video explains how MobileFrontend extension provides tooling to
help you debug live on-wiki content via $wgMFContentProviderClass 
Hope it saves someone lots of time!
Senior Software Engineer
This survey will help the Release Engineering team measure developer
satisfaction and determine where to invest resources. The topics covered
will include the following:
* Local Development Environment
* Beta Cluster / Staging Environment
* Testing / CI
* Code Review
* Production Systems
* Development and Productivity Tools
* Developer Documentation
* General Feedback
We are soliciting feedback from all Wikimedia developers, including Staff,
3rd party contributors and volunteer developers. The survey will be open
for 2 weeks, closing on November 14th.
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
To participate in this survey, please start here:
One update regarding this.
We enabled using the new table for Special:Tags in several large wikis
which caused a massive improvement in the performance of the page. For
example loading Special:Tags on Wikidata used to take around a minute and
now it takes less than a second. English Wikipedia is down from ten seconds
to less than one and so on.
There is a lot of work needs to be done and maintenance scripts is being
ran to backpopulate the ct_tag_id column in change_tag table (If you want
to follow the progress, see https://phabricator.wikimedia.org/T193873) and
then we need start reading from the new table in mediawiki and finally we
can drop ct_tag column entirely. If you want to help in review, writing
code or anything, just let me know.
On Wed, 27 Jun 2018 at 15:15, Léa Lacroix <lea.lacroix(a)wikimedia.de> wrote:
> Hello all,
> Our team is refactoring some code around the change tags on Recent
> Changes. This can impact people using the database on ToolForge.
> Currently, the tags are stored in the table change_tag in the column
> In the next days, we will add a column ct_tag_id with a unique identifier
> for these tags. A new table change_tag_def that will store the tag id,
> the message, and more information like how many times this tag is used on
> the local wiki.
> On the long term, we plan to drop the column ct_tag since the tag will be
> identified with ct_tag_id.
> This change will happen on:
> - French Wikipedia: Monday July 2nd
> - All other wikis: from July 9th
> If there is any problem (trouble with saving edits, slow down of recent
> changes…) please create a subtask of T185355
> <https://phabricator.wikimedia.org/T185355> or contact Ladsgroup
> Léa Lacroix
> Project Manager Community Communication for Wikidata
> Wikimedia Deutschland e.V.
> Tempelhofer Ufer 23-24
> 10963 Berlin
> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
> unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt
> für Körperschaften I Berlin, Steuernummer 27/029/42207.
> Wikidata-tech mailing list
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
The Community Wishlist Survey is now open, and you can post proposals
for projects that you would like the Wikimedia Foundation's Community
Tech team to work on:
The Community Tech team builds features and makes changes that active
Wikimedia contributors want, and the Wishlist Survey sets the team's
agenda for the next year.
The Wishlist Survey starts with a two-week proposal period, when
contributors from all Wikimedia projects are invited to post, discuss
and improve proposals. After that, there's a two-week voting period,
when everyone can post support-votes on the proposals.
You can post technical proposals until 11 November.
You can vote on proposals from 16 November to 30 November.
The Community Tech team is responsible for addressing the top ten
wishes on the list. If they, after investigating it, find that
something isn't feasible, they need to explain why to the community.
The Wishlist can also be used by volunteer developers and other teams,
who want to find projects to work on that the community really wants.
-----BEGIN PGP SIGNED MESSAGE-----
In preparation for Wikimedia production switching to PHP 7.2, we need
to get CI running using 7.2 (and for the rest of the MediaWiki world
too!). But before we can do that, we'll need 7.1 to be passing first.
The following extensions are currently failing tests on 7.1:
* FileImporter: T206286
* Kartographer: T206293
* Wikibase: T205958
* WikibaseLexeme: T206100
* WikibaseMediaInfo: T206281
And one non-Wikimedia deployed extension:
* MultiMaps: T206291
Thank you to James F, Matma Rex and Umherirrender for already fixing
some other extensions that were failing.
I'd like to make 7.1 tests voting by the end of the week, and would
appreciate maintainers fixing their extensions before then. You can
currently trigger 7.1 tests to verify fixes by commenting "check
experimental" in Gerrit.
- -- Kunal / Legoktm
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> will be holding
office hours the first Wednesday of each month, starting next week. Come
ask us anything about Wikimedia search!
We’re particularly interested in:
* Opportunities for collaboration—internally or externally to the Wikimedia
* Challenges you have with on-wiki search, in any of the languages we
But we're happy to talk about anything search-related.
Details for our next meeting:
Date: Wednesday, November 7th, 2018
Time: 16:00 GMT / 08:00 PST / 11:00 EST / 17:00 CET
Google Meet link: https://meet.google.com/vyc-jvgq-dww
*N.B.:* Google Meet System Requirements
Hope to see you there!
Sr. Software Engineer, Search Platform
I'm sending this email to request your help with...
We don't want non-confirmed users to see links from semiprotected
Wikipedia articles to their corresponding Wikidata items. This is a
well-known source of vandalism (and bad press) that is seriously
affecting Wikidata and some Wikipedias.
As Lydia describes on T205783,
"When contentious topics show up in the news vandalism on the Wikipedia
articles related to it usually shows up pretty quickly. The article then
might be protected for some time in order to prevent more vandalism. A
pattern we are seeing now is that people then move over to Wikidata and
continue their vandalism there. (This might then in turn lead to
vandalism showing up in the article anyway if it uses the data.) This
especially happens when an infobox has "edit on Wikidata" links or
something similar. We need to find a way to make this attack vector less
of a problem."
We don't want to hide these links from everyone, just from non-confirmed
users. We could write CSS rules for certain user groups, but this can
bring undesired side effects like giving all users the possiblity of
hiding arbitrary content (e.g., vandalism) from other users who should
be able to see it.
We also have `mw.title.protectionLevels["edit"]` in Lua, but this option
is documented as "expensive" and I can't guess what its impact could be
if applied on a large scale.
Any action or suggestion on how to achieve this is more than welcome.
Thanks in advance!