Hello,
I'm pleased to announced that Contributors team has released OOUI
0.25.0 last evening. It will be in MediaWiki core from 1.31.0-wmf.17,
which will be deployed to Wikimedia production in the regular train,
starting on Tuesday 18 January. As there are six breaking changes in
this release, at least nominally, please carefully consider if they
affect your code.
Breaking changes since last release:
* Drop the `constructive` flag entirely (James D. Forrester)
We've identified that we are providing a better experience with a
smaller number of different button types in our use cases and after
outreaching, testing and consolidating from it's starting patch Feb
2016 we finally get rid of the last remainders of this button flag
with this release.
* Remove `BookletLayout#getClosestPage` (James D. Forrester)
We rename a number of getters when asking for one of 0+ items for
consistency reasons.
This and the following three changes are all around this topic.
* SelectWidget: Remove `getFirstSelectableItem` (Prateek Saxena)
* SelectWidget: Remove `getHighlightedItem` (Prateek Saxena)
* SelectWidget: Remove `getRelativeSelectableItem` (Prateek Saxena)
* icons: Drop 'watchlist', deprecated in v0.23.1 (James D. Forrester)
'watchlist' icon was unused and we had no further plans to start using
it, therefore removed it completely.
Deprecations since last release:
* GroupElement: Rename getItem(s)FromData to findItem(s)FromData
(Prateek Saxena)
Similar to the breaking changes above, this and the following two
changes are for naming consistency reasons.
* MultiSelectWidget: Rename getters (Prateek Saxena)
* SelectWidget: Rename `getSelectedItem` to `findSelectedItem` (Prateek Saxena)
* icons: Flag indicators 'previous' & 'next' as to be removed (Volker E.)
In our quest to make OOUI core leaner, we've identified that those indicators
originally planned for a certain use case, never came into use.
You can still reference similar 'previous' & 'next' from 'movement' pack.
* icons: Rename 'arrowLast' to 'arrowPrevious' (James D. Forrester)
We're also renaming 'arrowLast' for consistency reasons to 'arrowPrevious'.
* icons: Remove 'eye'/'eyeClosed' icons (Volker E.)
We want to use 'alerts' pack more deliberately in major products and
moved 'eye'/'eyeClosed' out. They were deprecated in v0.23.0 in 'alerts'.
Use icons from 'accessibility' pack instead.
Please update your icon pack references accordingly in case you're
using one of those icons.
A personal highlight of this release is that with the various SVG
markup optimizations in this together with removal of pre Opera v15
special treatment in last minor release we've accomplished to bring
down the icons from ~180 KB to ~120 KB before or 1.8 KB of after
gzipped critical rendering CSS.
Additional details on 11 new features, 42 code-level and accessibility
changes, 18 styling and interaction design amendments, and all
improvements since v0.24.0 are in the full changelog[0]. If you have
any further queries or need help dealing with breaking changes, please
let me know.
As always, library documentation is available on mediawiki.org[1], and
there is some comprehensive generated code-level documentation and
interactive demos hosted on doc.wikimedia.org[2].
[0] - https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
[1] - https://www.mediawiki.org/wiki/OOUI
[2] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
--
Senior UX Engineer, Contributors
Wikimedia Foundation
volker.e(a)wikimedia.org | @Volker_E
https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-01-10
== Callouts ==
* Search PF would like somebody from performance/MediaWiki team to look at:
https://phabricator.wikimedia.org/T183101we’ve got some fails on
LinksUpdate which blocked search index update which makes Wikidata items
invisible in search (~50 items)
** [Perf] We've been looking at it, but we haven't identified a cause for
this issue yet.
** [SP] I guess we will just watch out for it and hope it was an one-time
thing.
* [Perf] Trying to compile a list of everything running in Prod that
*requires* Zend PHP5. Currently only aware of the XML dump job (has syntax
errors in output if run under HHVM). Anything else, please reach out to
Ian (email: imarlier@, irc: marlier)
* Reminder: Whitelist your EventLogging schema if you want data older than
90 days to be retained, talk to the Analytics team if you're not sure what
this means
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by: none
* Blocking: none
* Updates:
**Continuing work on 5.8 - synced reading lists
==== Android native app ====
* Blocked by: Patch to unblock DELETE endpoints in varnish:
https://gerrit.wikimedia.org/r/402433 DONE!
* Blocking: none
* Updates:
** Completed work to integrate with the new Reading List service!
Continuing to test and measure performance.
==== Reading Infrastructure ====
* Blocked by: ops on https://gerrit.wikimedia.org/r/#/c/402433/ <= this is
already merged since 2018-01-09
* Blocking: none
* Updates:
** working on request batching in reading list service
** continuing work on WP0 piracy
** Summary endpoint switchover from TextExtracts to PCS implementation
planned for Wednesday
** wrapping up media and references endpoints
** metadata and CSS endpoints to follow
==== Web ====
* Wrapping up a rework of the mobile web beta/settings page.
* Nothing new to report with regards to challenges/deliverables
==== Maps ====
* Blocked by: Services team
* Blocking: None
* Updates
** Everyone is back from vacation
** Several issues waiting on service team
==== Multimedia ====
* Nothing to report
=== Contributors ===
==== Parsing ====
* Sole update: Approaching additional wikis for replacing Tidy on those
wikis on Jan 31st.
==== Global Collaboration ====
* Blocked: Security on https://phabricator.wikimedia.org/T144467
* Blocking: Ops on Flow dumps. Matt's back from sabbatical but has been
sick off and on over the last week
=== Community Tech ===
* Investigating new year's proposals
* Will file for security/performance/DBA review for GlobalPreferences today
==== UI Standardization ====
** OOUI v0.25.0 released
https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
*** 6 breaking and 5 deprecating changes, and 16 UI related improvements,
among those
**** Drop the `constructive` flag entirely
**** Remove `BookletLayout#getClosestPage`
Also we significantly reduced SVG file size for our interface elements by
up to 21% with fine-tuned markup optimizations.
* Ongoing:
** OOUI & based products:
*** icons: Unify, refine and align to WikimediaUI Style Guide
https://phabricator.wikimedia.org/T177432 – first patches in:
https://gerrit.wikimedia.org/r/#/c/402757/
** More optimizations/size savings for RL embedded SVGs as data URIs
== Technology ==
== Technical Operations ==
* Blocking:
** None
* Blocked:
** Global Collaboration on Flow. https://phabricator.wikimedia.org/T172025
* Updates
** s5 => s8 migration for wikidata completed successfully. Feel free to
reach out to DBAs for followup questions and/or details
** meltdown/spectre week, ops busy with the mitigations, do expect some
slower response times
** This is a big hardware refresh quarter. Work is already decided and
prioritized, but please do provide input when/if requested ASAP. Thanks
=== Release Engineering ===
* Blocking
** None?
* Blocked
** ops: zuul package update (blocks gerrit upgrade)
** ops: node-tunnel-agent package update (blocks moving node testing to
docker in ci)
* Updates
** 2 weeks of normal MediaWiki deploys (this and next) followed by 2 weeks
of no MediaWiki but SWATs as needed (DevSummit/All Hands followed by RelEng
team offsite)
** Currently building nightlies of Mediawiki on the new “releases” (aka
non-CI) Jenkins host. Working with Security on best way to handle security
patches (which is the goal, to ensure security patches stay cleanly
applicable).
=== Performance ===
* Blocking: None
* Blocked: None
* Updates
** As noted above, we've been investigating LinksUpdate failures, haven't
been able to identify a cause at this point, haven't been able to reproduce.
** Fixes to Thumbor implementation happening as issues are reported (no
major ones at this point)
** Published the first in a series of blog posts detailing how we measure
performance:
https://phabricator.wikimedia.org/phame/post/view/83/measuring_wikipedia_pa…
** Trying to get a list of everything running in Prod that *requires* PHP5
(Zend) -- only thing that I know of for sure is the XML dump job.
=== Security ===
* No updates
* Sam and Brian are traveling this week
* Darian's last day is January 15th
=== Fundraising Tech ===
* Blocking: None
* Blocked: None
* Updates:
** Upstreaming stuff to Civi
** Making our Amazon Pay SDK fork support TCP proxy
** Re-starting work on new API for our main credit card processor
** Stats projects:
*** Andrew Green's druid banner impressions lib:
https://github.com/AndrewGreen/centralnotice_analytics
*** Jack Gleeson's stats collector:
https://github.com/jackgleeson/stats-collector
*** More consideration of how the get banner stats to payments in realtime
(talking with Analytics)
*** Also need to talk with analytics about preserving aggregated banner
stats for December
=== Scoring Platform ===
* Blocking: no
* Blocked: no
* Updates
** We added Extension:ORES to in-house code coverage reporting :D
*** https://doc.wikimedia.org/cover-extensions/ORES/index.html
*** https://scrutinizer-ci.com/g/wikimedia/mediawiki-extensions-ORES/
=== Analytics ===
* https://superset.wikimedia.org You can now create dashboards on top of
druid data, no automatic user creation. Created users for PMs and analysts,
let us know if you want a user. Perf to be seen.
* Clickstream data now public. Research community has access to the paths
readers follow through the site (aggreggated counts, not per user)
* Eventlogging purging on master box almost done.
* Working on wikistats UI bugs and small features to make project selection
more friendly, once the UI tweaks are done we will leave this work on
backburner until next year.
* Work on new set of APIs to return pageviews per country continues.
Privacy study of this data:
https://wikitech.wikimedia.org/wiki/Analytics/AQS/Pageviews/Pageviews_by_co…
* Meeting with Asaf for our next big project: geowiki (editors per country,
quite sensitive data)
** Mostly quiet (holidays)
=== Search Platform ===
* Blocked by: none
* Blocking: none
* Updates:
* Improving LTR training mechanisms (
https://phabricator.wikimedia.org/T184547)
* Working on fixes for completion suggester & redirects namespaces (
https://phabricator.wikimedia.org/T115756)
* Investigating ElasticSearch phonetic search (
https://phabricator.wikimedia.org/T182708)
* Working on refactoring search profiles to make them more config-like
https://phabricator.wikimedia.org/T183279
* Processing feedback for Wikidata fulltext & prefix search rankings
* Running test for machine-learning ranking on Hebrew wiki (
https://phabricator.wikimedia.org/T182616)
* Discussing publishing data from WDQS query logs (
https://phabricator.wikimedia.org/T143819)
== Wikidata ==
* Gaining speed after the holidays.
* Working on Lexeme continues, now working on diffs:
https://phabricator.wikimedia.org/T182424
* Working on Quality Constraint integration continues, 1.0 rollout planned
for Q1.
* Preparing for Developer Summit.
* Planning collaboration with Multimedia (MediaInfo) as well as Search for
Q1.
== MediaWiki Platform==
* Blocked by: Wikibase on https://phabricator.wikimedia.org/T183019
* Blocking: N/A
* Updates:
* Tim: Spectre/Meltdown review
* Multi-Content Revisions:
** Actor table: 380669 needs code review
** Working on https://phabricator.wikimedia.org/T36925 and
https://phabricator.wikimedia.org/T182678
** Comment table:
***Schema changes are almost done. Then we can start trying to use it.
** cleanupUsersWithNoId:
*** enwiki finished
*** Hopefully dewiki and wikidatawiki can be run this week
* ExternalStore de-PHP-serialization: Patch done before vacation. But Jaime
raised some interesting discussion on
https://phabricator.wikimedia.org/T183419 that may determine how we go
about updating ExternalStore
* Code coverage:
** Added a bunch of @covers tags in core, we also validate them pre-merge
now (see giant spike in
https://tools.wmflabs.org/coverage/mediawiki/chart.png )
** Implemented coverage reports for extensions (
https://phabricator.wikimedia.org/T71685,
https://doc.wikimedia.org/cover-extensions/ ), still in a beta period, will
announce as ready for usage end of this or next week once
https://phabricator.wikimedia.org/T182749 is implemented and documented
** Brainstorming/working on proof of concept for pre-merge coverage reports
that don't take hours to generate
* Audiences Technology Working Group planning
* Developer Summit planning
== SoS meeting ==
* ggellerman has ongoing conflicts, looking for another facilitator every
other week
* Check in on goals here, talk about cross-team dependencies in this
meeting, rather than waiting until the end of each quarter.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
Nemo generated a list of the top +2'ers for MediaWiki core and
MediaWiki extensions in 2017:
<http://federico.kapsi.fi/crstats/2017-merges.txt>
Thank you very much for all of the code review that you do :-) Special
shout out to Timo with 365 +2's in MediaWiki core - one for every day
of the year!
- ----
Inspired by that, for 2018, my goal will be to review one MediaWiki
patch by a volunteer for each day I'm working. And if I can't find a
patch to review, I'll find an abandoned looking patch by a volunteer,
and fix it up to a merge-able state. I encourage others to take on
this pledge too!
- -- Legoktm
-----BEGIN PGP SIGNATURE-----
iQJLBAEBCgA1FiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlpTFhsXHGxlZ29rdG1A
bWVtYmVyLmZzZi5vcmcACgkQUvyOe+23/KLLQg//TRCgSwkRlrGprcYcYJnDlAU3
FfEzgH6j0CEKKSzNnMmkoi75B8QMyCh2UH9VSbjPHCU7AY6ElO1NhGZ/r7fhZLbb
otDYCi7b684K/nGFzw2MlBd4IhERJ6K69jGnzbPOrxeDGnsN8lggsRW/dSM8YYtq
zNCzqQ5ZSHPomCNW9oKiA8xXTS+wddD+++HOLdlTlqiyiyJIhvFuAvtrdXlatLWb
o758HtCaRhI6cegqO7UIhcvtB0rN8AtIqOD/3qoNZKQkcIhCUxQrtKvwCJpyoCTG
p3J/I5aDt6LPVwpRyXLqVYy7h+d+MCiC/pfDdPVJ6D5XT9CiagVnqMSsc/Q5BoF5
VElh47NPAydRRGgprSI6+MpnitSEebUR3kLPWTUlKEp9iLKgGvPWgK64GGgYH1ww
8I4KCWC/HxNPV2ZUCTOFcIhG5bEO0fYSgpydfUJRLjJM/ZO+27bHl6bcBUBrimaG
z7iMVOCziA0nJYdvbdyHWm/xB/wA6IW4LFkqRz+OnP9f4Ntsi3ikdNof6BELROBk
efshfqyZ/N3CWtD2+rQaO6BzdCOIKea1xGG9XbYCaVTCmPDJEe7yq0+yVnDPq+Dh
7WRWrVqdJS5BqJ0MD16u6Q94OVNn+IoEBmP9tnHmZA2PW4KyPjlQWOFU7WpGtkJE
7oRLuvF9iOxA+ThHsE4=
=A7ZA
-----END PGP SIGNATURE-----
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting: https://www.mediawiki
.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
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/681/51985.
Work has begun to upgrade the base distribution for MediaWiki-Vagrant
to Debian Stretch [0]. The Wikimedia production cluster is preparing
for a similar upgrade [1] which will in part allow the Wikimedia wikis
to migrate to PHP 7 [2].
== What's new in the stretch-migration branch? ==
* Debian Stretch (Debian 9) base image
* Default PHP runtime is Zend PHP 7.0 (HHVM available via role)
* Database is MariaDB 10.1
* Provisioning via Puppet 4
Setting up a basic wiki (no roles enabled) seems to work pretty well.
Additional roles need testing and may require updated Puppet manifests
(Puppet syntax updates, erb syntax updates, package name changes,
additional packages). Help is needed to test roles, file bugs, and
submit patches. With some help I think we can be ready to switch to
Stretch as the default base image in early/mid January.
== Testing the Stretch base image and Puppet profiles ==
Its recommended to test with a fresh MediaWiki-Vagrant checkout so if
things go badly you can easily switch back to your original install
and keep working.
$ git clone --recursive
https://gerrit.wikimedia.org/r/mediawiki/vagrant mwv-stretch
$ cd mwv-stretch
$ git checkout stretch-migration
$ ./setup.sh
$ vagrant up
You can run `vagrant roles list -e -1` to get a nice list of the roles
you have enabled on your normal Trusty VM install to copy over to your
Stretch testing VM. This one-liner liner might even do it for you:
$ cd mwv-stretch
$ vagrant roles enable $(cd ../vagrant; vagrant roles list -e -1)
$ vagrant provision
[0]: https://phabricator.wikimedia.org/T181353
[1]: https://phabricator.wikimedia.org/T174431
[2]: https://phabricator.wikimedia.org/T176370
Bryan
--
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Manager, Cloud Services Boise, ID USA
irc: bd808 v:415.839.6885 x6855
(The HTML version of this announcement can be found at
https://discourse-mediawiki.wmflabs.org/t/welcome-to-wikimedia-developer-su…
)
https://discourse-mediawiki.wmflabs.org/
Wikimedia Developer Support offers a support channel for all developers
working with MediaWiki or other Wikimedia related technologies: APIs,
extensions, skins, gadgets, templates, bots, tools, apps, data sets… If you
need help with a technical problem, just ask.
This website is based on Discourse. If you have questions about how to use
it, check https://www.mediawiki.org/wiki/Discourse/Help
Your feedback about this website is very important! Bug reports, feature
requests and other suggestions are very welcomed.
IMPORTANT
Wikimedia Developer Support is a pilot project running on a test
instance. This is not the final deployment. More about this project at
https://www.mediawiki.org/wiki/Discourse
* Although the migration of users and content to the production server is
theoretically possible, at this point it is not guaranteed (T184461).
* The authentication system for this test instance is not what will be used
if this project makes it to production.
* If you have a Wikimedia account, use the same email when registering
here. This is how your username and content will remain yours if/when
Wikimedia single sign-on is implemented (T124691).
* Do not reuse your “real” passwords when creating an account in this test
instance.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Awesome, thanks for making it happen and the update!
Cheers
Lydia
On Jan 9, 2018 07:56, "Manuel Arostegui" <marostegui(a)wikimedia.org> wrote:
On Tue, Jan 9, 2018 at 6:50 AM, Manuel Arostegui <marostegui(a)wikimedia.org>
wrote:
> Hello,
>
> We are starting in 10 minutes
>
> On Wed, Jan 3, 2018 at 10:36 AM, Manuel Arostegui <
> marostegui(a)wikimedia.org> wrote:
>
>> Hello everyone
>>
>> Happy new year!
>>
>> This is a reminder.
>>
>> Next Tuesday 9th January at 6:00AM UTC we will have a read only time on
>> s5 for 30 minutes (https://phabricator.wikimedia.org/T181645 ), to
>> proceed and split wikidata onto its own hardware and make the new s8 shard
>> live (https://phabricator.wikimedia.org/T177208).
>>
>> Amir and Katie have kindly agreed to help us with testing and any
>> possible troubleshooting from the code side.
>>
>> Communication and coordination will happen on #wikimedia-operations if
>> anyone else is around and willing to provide another pair of eyes, that
>> would be, of course, much appreciated!
>>
>> Thanks
>> Jaime, Manuel
>>
>>
>>
>>
>>
>>
Hello,
The failover to split s5 and s8 was done successfully (https://phabricator.
wikimedia.org/T177208#3885585)
So now dewiki lives on s5 (not changed) and wikidata has its own set of
servers in a new shard called s8.
Thanks everyone who helped out!
Jaime,Manuel
On Tue, Jan 9, 2018 at 6:50 AM, Manuel Arostegui <marostegui(a)wikimedia.org>
wrote:
> Hello,
>
> We are starting in 10 minutes
>
> On Wed, Jan 3, 2018 at 10:36 AM, Manuel Arostegui <
> marostegui(a)wikimedia.org> wrote:
>
>> Hello everyone
>>
>> Happy new year!
>>
>> This is a reminder.
>>
>> Next Tuesday 9th January at 6:00AM UTC we will have a read only time on
>> s5 for 30 minutes (https://phabricator.wikimedia.org/T181645 ), to
>> proceed and split wikidata onto its own hardware and make the new s8 shard
>> live (https://phabricator.wikimedia.org/T177208).
>>
>> Amir and Katie have kindly agreed to help us with testing and any
>> possible troubleshooting from the code side.
>>
>> Communication and coordination will happen on #wikimedia-operations if
>> anyone else is around and willing to provide another pair of eyes, that
>> would be, of course, much appreciated!
>>
>> Thanks
>> Jaime, Manuel
>>
>>
>>
>>
>>
>>
Hello,
The failover to split s5 and s8 was done successfully (
https://phabricator.wikimedia.org/T177208#3885585)
So now dewiki lives on s5 (not changed) and wikidata has its own set of
servers in a new shard called s8.
Thanks everyone who helped out!
Jaime,Manuel
Forwarding to Wikitech-l and MediaWiki-l for the benefit of technical
people who may be interested in this subject and not subscribed to the
general WikimediaAnnounce-l.
As has been the case for awhile, WikimediaAnnounce-l is not automatically
forwarding to Wikimedia-l, so I'm forwarding this email manually to that
list also.
Have a good weekend.
Pine <https://en.wikipedia.org/wiki/User:CatherineMunro/Bright_Places>
---------- Forwarded message ----------
From: Markus Glaser <glaser(a)hallowelt.com>
Date: Mon, Dec 18, 2017 at 2:36 AM
Subject: [Wikimedia Announcements] Annual report 2017 for MediaWiki
Stakeholders' Group
To: "wikimediaannounce-l(a)lists.wikimedia.org" <wikimediaannounce-l@lists.
wikimedia.org>
Hello,
here is the annual report of the MediaWiki Stakeholders' Group:
https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_
Group/Annual_Report_2017
Best,
Markus Glaser
_______________________________________________
Please note: all replies sent to this mailing list will be immediately
directed to Wikimedia-l, the public mailing list of the Wikimedia
community. For more information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
_______________________________________________
WikimediaAnnounce-l mailing list
WikimediaAnnounce-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimediaannounce-l
Hello,
test2wiki [0] used to be a group0 wiki, meaning it used to get new
deployments at Tuesday of every week, at the same time that other test
wikis get deployments.
Recently, a major bug in Wikibase was introduced by yours truly [1]. It
happened when changes in Wikibase repo (aka Wikidata) transmitted to a
Wikibase client (aka all other wikis) while repo has the newer version of
mediawiki than the client. Any changes to the way repo transmits changes to
client must stay backward compatible for at least a minor release (=one
week). As you might guess, sometimes it's hard to test these cases.
The decision to prevent such problems in the future was to have one of our
test client wikis (that is connected to test.wikidata.org) kept back for
deployments for one day so we can have a test repo-client connection with
different mediawiki versions. You can read more in about reasoning in the
phabricator task: [2]
So starting from his week, test2wiki will get new releases a day later (in
Wednesdays).
[0]: https://test2.wikipedia.org/wiki/Main_Page
[1]: https://phabricator.wikimedia.org/T182243
[2]: https://phabricator.wikimedia.org/T182326
Best
--
Amir Sarabadani
Software Engineer
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
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.
