May 2018 - Wikitech-l - lists.wikimedia.org

Database dumps
by Byrial Jensen 17 Apr '25

17 Apr '25

Until some weeks ago http://dumps.wikimedia.org/backup-index.html used to show 4 dumps in progress at the same time. That meant that new database dumps normally was available within about 3 weeks for all databases except for enwiki and maybe dewiki where the dump process due to size took longer time. However the 4 dumps processes at one time become 3 some weeks ago. And after massive failures at June 4, only one dump has been in progress at the same time. So at the current speed it will take several months to come thru all dumps. Is it possible to speed up the process again using several dump processes at the same time? Thank you, Byrial

3 2

User-Agent:
by Domas Mituzas 17 Apr '25

17 Apr '25

Hi! from now on specific per-bot/per-software/per-client User-Agent header is mandatory for contacting Wikimedia sites. Domas

19 61

Acquiring list of templates including external links
by Takashi OTA 17 Apr '25

17 Apr '25

Hoi, This is an inquiry from my friend in academia, researching about Wikipedia. He would like to know whether there's a way to acquire a list of templates including external links. Here are some examples including external links. https://ja.wikipedia.org/wiki/Template:JOI/doc https://ja.wikipedia.org/wiki/Template:Twitter/doc Such links are stored in externallinks.sql.gz, in an expanded form. When you want to check increase/decrease of linked domains in chronological order through edit history, you have to check pages-meta-history1.xml etc. In a such case, traditional links and links by templates are mixed, Therefore, the latter ones (links by templates) should be expanded to traditional link forms. Sorry if what I am saying does not make sense. Thanks in advance, --Takashi Ota [[U:Takot]]

13 24

EBNF grammar project status?
by Steve Bennett 01 Apr '25

01 Apr '25

What's the status of the project to create a grammar for Wikitext in EBNF? There are two pages: http://meta.wikimedia.org/wiki/Wikitext_Metasyntax http://www.mediawiki.org/wiki/Markup_spec Nothing seems to have happened since January this year. Also the comments on the latter page seem to indicate a lack of clear goal: is this just a fun project, is it to improve the existing parser, or is it to facilititate a new parser? It's obviously a lot of work, so it needs to be of clear benefit. Brion requested the grammar IIRC (and there's a comment to that effect at http://bugzilla.wikimedia.org/show_bug.cgi?id=7 ), so I'm wondering what became of it. Is there still a goal of replacing the parser? Or is there some alternative plan? Steve

26 217

Missing Section Headings
by Marc Riddell 13 Sep '24

13 Sep '24

Hello, I have been a WP editor since 2006. I hope you can help me. For some reason I no longer have Section Heading titles showing in the Articles. This is true of all Headings including the one that carries the Article subject's name. When there is a Table of Contents, it appears fine and, when I click on a particular Section, it goes to that Section, but all that is there is a straight line separating the Sections. There is also no button to edit a Section. If I edit the page and remove the "== ==" markers from the Section Titles, the Title then shows up, but not as a Section Heading. Also, I don't have any Date separators on my Want List. This started 2 days ago. Any thoughts? Thanks, Marc Riddell [[User:Michael David]]

10 11

How to make commits from mirrored Wikimedia repos show up on your GitHub profile
by Bartosz Dziewoński 27 Jun '24

27 Jun '24

I know it has been annoying a couple of people other than me, so now that I've learned how to make it work I'll share the knowledge here. tl;dr: Star the repositories. No, seriously. (And yes, you need to star each extension repo separately.) (Is there a place on mw.org to put this tidbit on?) ------- Forwarded message ------- From: "Brian Levine" <support(a)github.com> (GitHub Staff) To: matma.rex(a)gmail.com Cc: Subject: Re: Commits in mirrored repositories not showing up on my profile Date: Tue, 09 Jul 2013 06:47:19 +0200 Hi Bartosz In order to link your commits to your GitHub account, you need to have some association with the repository other than authoring the commit. Usually, having push access gives you that connection. In this case, you don't have push permission, so we don't link you to the commit. The easy solution here is for you to star the repository. If you star it - along with the other repositories that are giving you this problem - we'll see that you're connected to the repository and you'll get contribution credit for those commits. Cheers Brian -- Matma Rex

3 3

Research FAQ gets a facelift
by Dario Taraborelli 25 Jun '24

25 Jun '24

We just released a new version of Research:FAQ on Meta [1], significantly expanded and updated, to make our processes at WMF more transparent and to meet an explicit FDC request to clarify the role and responsibilities of individual teams involved in research across the organization. The previous version – written from the perspective of the (now inactive) Research:Committee, and mostly obsolete since the release of WMF's open access policy [2] – can still be found here [3]. Comments and bold edits to the new version of the document are welcome. For any question or concern, you can drop me a line or ping my username on-wiki. Thanks, Dario [1] https://meta.wikimedia.org/wiki/Research:FAQ [2] https://wikimediafoundation.org/wiki/Open_access_policy [3] https://meta.wikimedia.org/w/index.php?title=Research:FAQ&oldid=15176953 *Dario Taraborelli *Head of Research, Wikimedia Foundation wikimediafoundation.org • nitens.org • @readermeter <http://twitter.com/readermeter>

2 1

bluejeans
by Jeremy Baron 22 Feb '23

22 Feb '23

Hi, On Tue, Mar 1, 2016 at 3:36 PM, David Strine <dstrine(a)wikimedia.org> wrote: > We will be holding this brownbag in 25 minutes. The Bluejeans link has > changed: > > https://bluejeans.com/396234560 I'm not familiar with bluejeans and maybe have missed a transition because I wasn't paying enough attention. is this some kind of experiment? have all meetings transitioned to this service? anyway, my immediate question at the moment is how do you join without sharing your microphone and camera? am I correct thinking that this is an entirely proprietary stack that's neither gratis nor libre and has no on-premise (not cloud) hosting option? are we paying for this? -Jeremy

9 16

New DB_REPLICA constant; DB_SLAVE deprecated
by Aaron Schulz 04 Jul '20

04 Jul '20

As of 950cf6016c, the mediawiki/core repo was updated to use DB_REPLICA instead of DB_SLAVE, with the old constant left as an alias. This is part of a string of commits that cleaned up the mixed use of "replica" and "slave" by sticking to the former. Extensions have not been mass converted. Please use the new constant in any new code. The word "replica" is a bit more indicative of a broader range of DB setups*, is used by a range of large companies**, and is more neutral in connotations. Drupal and Django made similar updates (even replacing the word "master"): * https://www.drupal.org/node/2275877 * https://github.com/django/django/pull/2692/files & https://github.com/django/django/commit/beec05686ccc3bee8461f9a5a02c607a023… I don't plan on doing anything to DB_MASTER, since it seems fine by itself, like "master copy", "master tape" or "master key". This is analogous to a master RDBMs database. Even multi-master RDBMs systems tend to have a stronger consistency than classic RDBMs slave servers, and present themselves as one logical "master" or "authoritative" copy. Even in it's personified form, a "master" database can readily be thought of as analogous to "controller", "governer", "ruler", lead "officer", or such.** * clusters using two-phase commit, galera using certification-based replication, multi-master circular replication, ect... ** https://en.wikipedia.org/wiki/Master/slave_(technology)#Appropriateness_of_… *** http://www.merriam-webster.com/dictionary/master?utm_campaign=sd&utm_medium… -- -Aaron

4 3

Life hack: Working with production content in your local wiki
by Jon Robson 13 Dec '18

13 Dec '18

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 [1] https://youtu.be/uRQzjN0hBlY Hope it saves someone lots of time! [1] https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/blob/maste… -- Jon Robson Senior Software Engineer

1 1

Roadmap for CX?
by Strainu 06 Sep '18

06 Sep '18

Following the recent outage, we've had a new series of complaints about the lack of improvements in CX, especially related to server-side activities like saving/publishing pages. Now, I know the team is involved in a long-term effort to merge the editor with the VE, but is there an end in sight for that effort? Can I tell people who ask "look, 6 more months then we'll have a much better translation tool"? Is there a publicly available roadmap for this project and more generally, for CX? Thanks, Strainu

5 8

MediaWiki and OpenID Connect
by Adam Sobieski 11 Jul '18

11 Jul '18

Wikitech-l, Greetings. I would like to describe an exciting scenario possible with OpenID Connect. In the scenario, after choosing to verify their name on their Wikipedia account, a user logs onto Wikipedia and uses OpenID Connect to link their Wikipedia account to multiple verified accounts, for example their Facebook and LinkedIn accounts. At the end of the process, we can envision the user obtaining a checkmark next to their full name on Wikipedia, their real name and a verification icon appearing next to their edits and on their user page. There might even be, per user settings, hyperlinks to their Facebook and LinkedIn pages on their Wikipedia user page. With such features, we can envision allowing groups of users or admins to determine that certain articles require a verified account to edit. Presently, OpenID Connect functionality is available for MediaWiki as an extension. I would like to see the OpenID Connect functionality under discussion expanded to support scenarios including aforementioned and also integrated into MediaWiki. Thank you. I hope that the above ideas are also interesting to you in the Wikitech-l community. Best regards, Adam Sobieski http://www.phoster.com/contents/

9 17

Your feedback requested - Beta Cluster Survey...
by Jean-Rene Branaa 15 Jun '18

15 Jun '18

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

1 1

[nominations needed] Wikimedia Technical Conference
by Deborah Tankersley 08 Jun '18

08 Jun '18

*Hello,We recently announced the new Wikimedia Technical Conference (TechConf) during the closing session of the Barcelona Hackathon on May 20, 2018. We are sending this email to give an update on the planning and organization, and to also let everyone know how the nomination process will work for those interested in attending. The Wikimedia Technical Conference will take place in Portland, OR, USA on October 22-25, 2018. And, as mentioned in previous emails [1][2] and on the wiki page [3], this conference will be focused on the cross-departmental program called Platform Evolution. We will be providing more information and context as we go along in the process.For this conference, we are looking for diverse stakeholders, perspectives, and experiences that will help us to make informed decisions for the future evolution of the platform. We need people who can create and architect solutions, as well as those who actually make decisions on funding and prioritization for the projects.Later this week, we will send out a form to provide more detailed information on the nomination process and how to nominate people (or it can be yourself) to attend this conference, along with the skills, experiences, and/or backgrounds that we are looking for. Due to the time needed for visa application and other constraints, the deadline for nominations will be June 8th. Please make sure that you don’t miss the deadline!If you have any questions, please post them on the talk page [4][1] https://lists.wikimedia.org/pipermail/mediawiki-l/2018-April/047367.html <https://lists.wikimedia.org/pipermail/mediawiki-l/2018-April/047367.html> [2] https://lists.wikimedia.org/pipermail/wikitech-l/2018-April/089738.html <https://lists.wikimedia.org/pipermail/wikitech-l/2018-April/089738.html> [3] https://mediawiki.org/wiki/Wikimedia_Technical_Conference/2018 <https://mediawiki.org/wiki/Wikimedia_Technical_Conference/2018> [4] https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018 <https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018> * *Cheers from the Program Committee:* *Kate, Corey, Joaquin, Greg, Birgit and TheDJ* -- deb tankersley Program Manager, Engineering Wikimedia Foundation

5 5

New feature deployed: Finding text changes in moved paragraphs in diffs
by Birgit Müller 06 Jun '18

06 Jun '18

Hi all, over the past 1,5 years WMDE’s Technical Wishes team was working on a major improvement of wikidiff2 [1] - the engine behind the wikitext diff view. The major outcome of our improvements got deployed to most wikis just now: It is now easier to find moved paragraphs and text changes inside them. [2] Why we worked on this: The idea for the project arose from the wishlist of the German-speaking communities: Show text changes in moved paragraphs. Before we worked on this, moved paragraphs were shown in the diff as a deleted paragraph and then as an added paragraph. This meant that you had to parse visually through the paragraphs to find any potential changes - a fact that vandals liked to make use of. [3] Desktop version, mobile version The desktop version of the feature already got deployed to Mediawiki.org and deWP in December 2017. After further improvements of the diff algorithm, the change could now get deployed to most wikis. The languages unified Han, Thai and Japanese that don’t use spaces as delimiters will follow soon. The mobile version is in the making and will follow in the next weeks. The backend work has been done by the WMDE team, the WMF’s mobile team is taking care of the design work for the user interface of the mobile version. Improving the algorithm of wikidiff2: More than a new feature The work that has been done goes further than the original wish: First of all, we not only highlighted text changes within a moved paragraph, but also made it easier to find moved paragraphs in the first place: Clickable arrows allow to follow the move of the paragraph. Second, we generally improved the diff algorithm: For example, we could find an old bug in the diff engine: Sometimes two paragraphs which are not related at all were considered a changed paragraph. The bug fix was already deployed in October 2017. [4] If you are interested in learning more about the work that has been done, we're going to publish the lessons learned by the dev team within the next days (so stay tuned :-) !. Thank you! We would like to thank everyone who supported us in the work around wikidiff2: People from different wikis looked into diffs and gave us valuable feedback. Moritz Mühlenhoff supported us by updating the library, and deploying it. Tim Starling and Max Semenik supported us with code review and consultation during the Vienna Hackathon. The Desktop and Mobile Web team is going to add a user friendly design to the mobile version. Your advice, feedback and support is much appreciated :-) Further feedback is very welcome! Birgit (for the technical wishes team) [1] Extension manual: https://www.mediawiki.org/wiki/Extension:Wikidiff2 [2] Deployment ticket: https://phabricator.wikimedia.org/T195375 [3] Main project page on meta: https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Show_text_changes_whe… [4] Patch on gerrit for the bug fix: https://gerrit.wikimedia.org/r/#/c/356582/ -- Birgit Müller Community Communications Manager Software Development and Engineering 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.

2 2

+2 nomination for Jakob in mediawiki/*
by Addshore 05 Jun '18

05 Jun '18

Hi, I've filed <*https://phabricator.wikimedia.org/T195220 <https://phabricator.wikimedia.org/T195220>*>, nominating Jakob for +2 in mediawiki/ repos. -- Addshore

2 1

TechCom Radar 2018-05-30
by Kate Chapman 04 Jun '18

04 Jun '18

Hi All, Here are the minutes from this week's TechCom meeting: * TechCom will be announcing a call for nominations to expand the committee next week * Discussion and community input on MediaWiki Platform Architecture Principles Document continues: <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/MediaWiki_Plat…> * Public IRC Discussion of RFC next week 2018-06-06 in the #wikimedia-office channel at 2pm PST(22:00 UTC, 23:00 CET): Use ar_page_id to determine the parent IDs for undeleted revisions <https://phabricator.wikimedia.org/T193690> You can also find our meeting minutes at <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes> See also the TechCom RFC board <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. -- Kate Chapman TechCom Facilitator (Contractor)

6 9

Planet Wikimedia using new software "rawdog"
by Daniel Zahn 03 Jun '18

03 Jun '18

Hi, this is an announcement to let you know that the service ($lang). planet.wikimedia.org, an RSS feed aggregator for all Wikimedia related blogs, has switched software. You can find the English version at https://en.planet.wikimedia.org/ Other existing languages are listed on https://wikitech.wikimedia.org/wiki/Planet.wikimedia.org#Which_languages_ex… ? Today we moved away from planet-venus and to a newer package called "rawdog" that does the same thing as before, fetching a bunch of RSS feed and combining them into a single page and feed. The reason is that planet-venus has been dropped in Debian stable (stretch) because it was unmaintained, so we had to find an alternative to be able to upgrade the underlying servers to a current OS version. If you never heard of planet, here you can find more info: https://wikitech.wikimedia.org/wiki/Planet.wikimedia.org If you already use it but just subscribe to the "feed of feeds" then nothing should change for you. (Though note that we support RSS 2.0 but not a separate Atom feed anymore. We are redirecting the old atom.xml URL to the new (and old) URL rss20.xml.) If you already use it and look at the web UI, enjoy the new theme that Paladox imported from KDE to make it look about 150% better than before. (thanks to him for that theming work!) We also applied patches to make it look more like our former planet for a smooth transition. A "wmf1" package has been built and uploaded at https://apt.wikimedia.org/wikimedia/pool/main/r/rawdog/ If you want to know more about "rawdog": https://offog.org/code/rawdog/ https://packages.debian.org/stretch/rawdog If you want to add your blog feed, feel free to upload changes or just drop me a mail. Bugs can be reported here: https://phabricator.wikimedia.org/project/view/413/ Tickets are: https://phabricator.wikimedia.org/T180498 , https://phabricator.wikimedia.org/T168490 Cheers, Daniel -- Daniel Zahn <dzahn(a)wikimedia.org> Operations Engineer

6 13

wgEmergencyContact - noc@wikipedia.org
by Martin Urbanec 01 Jun '18

01 Jun '18

Hello, is it intended to have *noc(a)wikipedia.org <noc(a)wikipedia.org>* in wgEmergencyContact in CommonSettings.php? Martin

4 4

change to output file numbering of big wikis
by Ariel Glenn WMF 31 May '18

31 May '18

TL;DR: Scripts that reply on xml files numbered 1 through 4 should be updated to check for 1 through 6. Explanation: A number of wikis have stubs and page content files generated 4 parts at a time, with the appropriate number added to the filename. I'm going to be increasing that thi month to 6. The reason for the increase is that near the end of the run there are usually just a few big wikis taking their time at completing. If they run with 6 processes at once, they'll finish up a bit sooner. If you have scripts that rely on the number 4, just increase it to 6 and you're done. This will go into effect for the June 1 run and all runs afterwards. Thanks!

1 0

[MediaWiki-announce] 1.31.0-rc.2
by Chad Horohoe 30 May '18

30 May '18

Hi, I'd like to announce the immediate availability of MediaWiki 1.31.0-rc.2, the second release candidate for 1.31.x. Links at the end of the e-mail. The tag has been signed and pushed to Git. This is not a final release and should not be used for production websites. There are several major outstanding bugs on the workboard. As always, please do try out the release candidate in a test environment. It's how we find bugs that didn't surface in initial development :-) You'll likely notice that I went from rc.0 to rc.2 with this announcement. This was not an oversight. While rc.1 was tagged, signed, and built as a tarball, prior to announcing it I noticed the version number still referred to rc.0. Rather than confuse people, I decided to move forward with an rc.2. There's only a two commit difference between the tags. If using the patch files, you'll want to do it stepwise, moving from rc.0 to rc.1 then on to rc.2. There have also been schema changes since rc.0, so you will need to run update.php. Full release notes: https://phabricator.wikimedia.org/diffusion/MW/browse/REL1_31/RELEASE-NOTES… https://www.mediawiki.org/wiki/Release_notes/1.31 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.0-rc.2.tar.gz https://releases.wikimedia.org/mediawiki/1.31/mediawiki-core-1.31.0-rc.2.ta… https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.0-rc.2.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.0-rc.2.tar.gz.… https://releases.wikimedia.org/mediawiki/1.31/mediawiki-core-1.31.0-rc.2.ta… https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.0-rc.2.patch.g… Public keys: https://www.mediawiki.org/keys/keys.html -- Chad Horohoe _______________________________________________ MediaWiki announcements mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce

1 0

New Filters on Watchlist to graduate out of beta soon
by Joe Matazzoni 30 May '18

30 May '18

Collaboration team [1] is announcing plans to graduate the New Filters for Edit Review [2] out of beta on Watchlist by late June or early July. After launch, this suite of improved edit-search tools will be standard on all wikis. Individuals who prefer the existing Watchlist interface will be able to opt out by means of a new preference. The New Filters introduce an easier yet more powerful filtering interface [3] to Watchlist as well as a whole list of filters and other tools that make reviewing edits more efficient, including live page updating [4], user-defined highlighting [5], the ability to create special-purpose filter sets and save them for re-use [6] and (on wikis with ORES enabled [7]) predictive filters powered by machine learning [8]. If you’re not familiar with the New Filters, please give them a try on Watchlist by activating the New Filters beta feature. In particular, it would be very helpful if you could test the new functionality with your local gadgets and configurations. The documentation pages [9] provide guidance on how to use the many new tools you’ll discover. Over 70,000 people have activated the New Filters beta, which has been in testing on Watchlist for more than eight months. We feel confident that the features are stable and effective, but if you have thoughts about these tools or the beta graduation, please let us know on the project talk page [10]. In particular, tell us if you know of a special incompatibility or other issue that makes the New Filters problematic on your wiki. We’ll examine the blocker and may delay release on your wiki until the issue can be addressed. [1] https://www.mediawiki.org/wiki/Collaboration <https://www.mediawiki.org/wiki/Collaboration> [2] https://www.mediawiki.org/wiki/Edit_Review_Improvements/New_filters_for_edi… <https://www.mediawiki.org/wiki/Edit_Review_Improvements/New_filters_for_edi…> [3] https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit… <https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit…> [4] https://www.mediawiki.org/wiki/Edit_Review_Improvements/New_filters_for_edi… <https://www.mediawiki.org/wiki/Edit_Review_Improvements/New_filters_for_edi…> [5] https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit… <https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit…> [6] https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit… <https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit…> [7] https://www.mediawiki.org/wiki/ORES <https://www.mediawiki.org/wiki/ORES> [8] https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit… <https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit…> [9] https://www.mediawiki.org/wiki/Help:New_filters_for_edit_review/Quick_tour <https://www.mediawiki.org/wiki/Help:New_filters_for_edit_review/Quick_tour>[10] https://www.mediawiki.org/wiki/Talk:Edit_Review_Improvements/New_filters_fo… <https://www.mediawiki.org/wiki/Talk:Edit_Review_Improvements/New_filters_fo…> _____________________ Joe Matazzoni Product Manager, Collaboration Wikimedia Foundation, San Francisco "Imagine a world in which every single human being can freely share in the sum of all knowledge."

1 0

2018-05-30 Scrum of Scrums meeting notes
by Grace Gellerman 30 May '18

30 May '18

https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-05-30 =2018-05-30= == Callouts == * From last week, all WIndows NT operating systems are under the "Windows" os family in analytics metrics * Security: Security review for Wikidata queries data release proposal https://phabricator.wikimedia.org/T190875 == Audiences == === Readers === ==== iOS native app ==== * Blocked by: * Blocking: * Updates: ** Continuing work on tech debt release, 5.8.2 ( https://phabricator.wikimedia.org/project/view/3358/ ) ** Starting work on next major release, 5.9 ( https://phabricator.wikimedia.org/project/view/3238/ ) ==== Android native app ==== * Blocked by: * Blocking: * Updates: * Released maintenance update to production (improvements to reading list syncing / fix no-such-project errors) * Finalizing multilingual features based on user testing at Hackathon -- on track for release in ~1 week. ==== Readers Web ==== * Blocked by: * Blocking: * Updates: *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra ==== Readers Infrastructure ==== * No updates this week. *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra **[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of client apps by coalescing and moving more logic to the server]] ***Reading Infra depends on Parsing, Services ===== Maps ===== * Blocked by: * Blocking: * Updates: ==== Multimedia ==== * Blocked by: * Blocking: * Updates: ** Looking into OOUI migration for Wikibase per discussions at the hackathon/elsewhere ** UploadWizard work for multilingual captions pretty much complete ** Indexing wikibase statements (searchable via haswbstatement:XXXX), work continues on quantities *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 3.1]] Prepare for launch of the first Structured Data on Commons feature (multilingual file captions) ***SDC depends on Multimedia,SRE, WMDE, Search Platform, MediaWiki Platform, Research ** [[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 2.1]] Integrate structured file captions into search *** SDC depends on Search Platform, Multimedia **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Structured_Data#Segment_4:_Programs|Segment 4, Outcome 2]]: Develop a better understanding of existing needs for Structured Commons- T171252 ***Research depends on Multimedia === Contributors === ==== Community Tech ==== * Blocked by: * Blocking: * Updates: ** Working on PageTriage improvements ==== Anti-Harassment Tools ==== * Blocked by: * Blocking: * Updates: ** Working on Blocking Tools ==== Editing ==== * Blocked by: * Blocking: * Updates: ** None ==== Parsing ==== * Blocked by: * Blocking: * Updates: ** Tidy -> RemexHtml: final switch planned for June 27th / July 11th *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]] Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team *** Parsing depends on MediaWiki Platform, Services **[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of client apps by coalescing and moving more logic to the server]] Increase code sharing of client apps by coalescing and moving more logic to the server. *** Reading Infra depends on Parsing, Services ** [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better data|Outcome 2: Objective 1]]: Revision storage scaling *** Services depends on SRE, Parsing ==== Collaboration ==== * Blocked by: * Blocking: * Updates: ** Patches to solve most of Echo's multi-DC incompatibilities now awaiting review https://phabricator.wikimedia.org/T164860 ** Deleted Echo's rspec tests to unbreak CI ==== Language ==== * Blocked by: * Blocking: * Updates: *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.1]] Improve and consolidate our unified editing platform so that it's great on all devices ***Language depends on Editing === Audiences Design === ==== UI Standardization ==== * Blocked by: * Blocking: * Updates: ** OOUI – v0.27.1 released yesterday: https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v… *** 1 deprecation in this release. Additionally 9 style amendments, 9 code & 2 accessibility improvement. Among those **** Toolbar: Add a required 'name' property to toolgroup configs; deprecating change (Ed Sanders) **** Clarify and align TabSelectWidget focus (Volker E.) https://phabricator.wikimedia.org/T194863 **** Allow dropdown menus to be larger than their handles (Ed Sanders) https://phabricator.wikimedia.org/T195257 ** Continuing work on Design Style Guide, this week starting 'Resources' page with all repo resources ** Continuing work on a minor UI/UX issues in AdvancedSearch with WMDE team == Technology == === Analytics === * Blocked by: * Blocking: * Updates: ** Updated user agent string parsing regexes in eventlogging and refinery ** Migrated zookeeper to new hardware ** Migrating druid to debian stretch, should be finished this week ** Revision score now available in eventstreams === Cloud Services === * Blocked by: * Blocking: * Updates: === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** Working on getting Ingenico Connect API campaign ready. ** Still working on backend pipeline for CentralNotice EventLogging stats ** Working on a Donor Deletion tool for Civi in response to GDPR === MediaWiki Platform === * Blocked by: * Blocking: * Updates: * MCR: ** ar_rev_id deduplication is merged and maintenance script has been run ** API "templated parameters" patch was merged * TemplateStyles: ** Implemented a feature request. ** An enwiki RFC about enabling it as soon as Remex is enabled there is passing. * MediaWiki core master now requires PHP 7.0 or HHVM * MediaWiki-CodeSniffer 19.0.0 and 20.0.0 released, to allow for safe PHP 7 features to be used * Bug triage and fixes for MassMessage and GlobalUserPage * Finished development of "CoverMe": https://tools.wmflabs.org/coverme/ ( https://blog.legoktm.com/2018/05/29/introducing-coverme-find-the-most-calle…) * Deployed postgres in CI, filed T195807 for failures * Work towards PSR-4 in MediaWiki core, including enabling PSR-4 autoloader for more directories, and implementing a structure test to validate PSR-4 compliance * Hackathon projects: ** MySQL client wrapper to replace "sql" shell script: https://gerrit.wikimedia.org/r/#/c/434188/ ** Refactor API parameter validation: https://gerrit.wikimedia.org/r/q/topic:%2522bug%252FT142080-api-param-valid… ** Script to import Phabricator task information into a wiki: https://gerrit.wikimedia.org/r/#/c/433919/ * The usual code review and bug work *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]] Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team ***Parsing depends on MediaWiki Platform, Services *** Planning underway for next FY Platform Evolution program **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research *** MCR capabilities in active development ** [[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 1.1]] Assist with deploying MultiContent Revisions on Commons [[phab:T174022|T174022]] Implement multi-content revisions, [[phab:T174023|T174023]] Implement MCR storage layer, [[phab:T174045|T174045]] DB schema migration for MCR, [[phab:T174044|T174044]] Deploy MCR storage layer, [[phab:T174043|T174043]]Deploy Multi-Content Revisions ***SDC depends on MediaWiki Platform, WMDE *** MCR capabilities in active development === Performance === * Blocked by: * Blocking: Readers Web (review of CitationUsage) - will be done this week * Updates: ** performance perception survey live on several wikis ** Trialing mobile performance testing on SauceLabs device lab ** More fixes to ChronologyProtector ** Still pulling jQuery deps out of base javascript modules ** Bunch of resourceloader bug fixes ** mcrouter expected to be ready in prod this week, will test on testwiki next week === Release Engineering === * Blocking ** * Blocked ** * Updates ** Train status: https://phabricator.wikimedia.org/T191051 ** 1.32.0-wmf.5 got held up last week by an incident that happened during the scheduled Thursday train deployment window. *** https://wikitech.wikimedia.org/wiki/Incident_documentation/20180524-wikidata *** We should be back on track this week, wmf.5 is clear of blockers and wmf.6 should be rolling out as usual *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra === Research === * Blocked by: Performance: https://gerrit.wikimedia.org/r/#/c/432534/ * Blocking: None * Updates: ** Deploying the gapfinder-tools app and gathering section mappings. ** Have been gathering synonym mappings. ** Analyzed the first incoming labels from WikiLabels citations campaign *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Structured_Data#Segment_4:_Programs|Segment 4, Outcome 2]]: Develop a better understanding of existing needs for Structured Commons- [[phab:T171252|T171252]] ***Research depends on Multimedia === Scoring Platform === * Blocked by: * Blocking: * Updates: === Search Platform === * Blocked by: Security: https://phabricator.wikimedia.org/T190875 * Blocking: * Updates: ** Wikidata reindexed and now external ID and string properties can be searched for with haswbstatement keyword ** Deep category search enabled on all wikis except private ones: https://phabricator.wikimedia.org/T194260 ** all: keyword enabled on all wikis: https://phabricator.wikimedia.org/T165110 ** Exploring ideas for applying NLP to search: https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Potential_Applicatio… ** Looking into fixing regex highlighting that does not time out as expected: https://phabricator.wikimedia.org/T195491 ** Working on query parsing refactoring: https://phabricator.wikimedia.org/T185108 ** Working on Polish analyzer: https://phabricator.wikimedia.org/T186046 ** Working on fulltext search for Lexemes *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|*Objective 2.1]] Integrate structured file captions into search *** SDC depends on Search Platform, Multimedia === Security === * Blocked by: * Blocking: * Updates: *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]]: Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team ***Parsing depends on MediaWiki Platform, Services === Services === * Blocked by: ** Parsing on language variants transformation support ** Echo on non JSON-serializable job https://phabricator.wikimedia.org/T192945 ** Who knows who's resonsible for GWToolset extension? It has non-json-serializable job https://phabricator.wikimedia.org/T192946 * Blocking: none? * Updates: ** Kafka queue enabled for all jobs everywhere except some exceptions and cirrus search ** revision-score event exposed via event streams *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of client apps by coalescing and moving more logic to the server.]] ***Reading Infra/Parsing, Services **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]] Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team ***Parsing depends on MediaWiki Platform, Services [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better data|Outcome 2: Objective 1]]: Revision storage scaling *** Services depends on SRE, Parsing === Site Reliability Engineering === * Blocked by: ** Collaboration for flow, T172025 * Blocking: ** None * Updates: ** Had a wikidata outage https://wikitech.wikimedia.org/wiki/Incident_documentation/20180524-wikidata ** row C move+upgrade went quite well ** mcrouter to be deployed this week *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better data|Outcome 2: Objective 1]]: Revision storage scaling *** Services depends on SRE, Parsing == Wikidata == * Blocked by: * Blocking: * Updates: *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 1.1]] Assist with deploying MultiContent Revisions on Commons [[phab:T174022|T174022]] Implement multi-content revisions, [[phab:T174023|T174023]] Implement MCR storage layer, [[phab:T174045|T174045]] DB schema migration for MCR, [[phab:T174044|T174044]] Deploy MCR storage layer, [[phab:T174043|T174043]]Deploy Multi-Content Revisions ***SDC depends on MediaWiki Platform, WMDE == German Technical Wishlist == * Blocked by: * Blocking: * Updates: == SoS Meeting Bookkeeping == * Updates:

1 0

Machine-utilizable Crowdsourced Lexicons
by Adam Sobieski 30 May '18

30 May '18

INTRODUCTION Machine-utilizable lexicons can enhance a great number of speech and natural language technologies. Scientists, engineers and technologists – linguists, computational linguists and artificial intelligence researchers – eagerly await the advancement of machine lexicons which include rich, structured metadata and machine-utilizable definitions. Wiktionary, a collaborative project to produce a free-content multilingual dictionary, aims to describe all words of all languages using definitions and descriptions. The Wiktionary project, brought online in 2002, includes 139 spoken languages and American sign language [1]. This letter hopes to inspire exploration into and discussion regarding machine wiktionaries, machine-utilizable crowdsourced lexicons, and services which could exist at https://machine.wiktionary.org/ . LEXICON EDITIONING The premise of editioning is that one version of the resource can be more or less frozen, e.g. a 2018 edition, while wiki editors collaboratively work on a next version, e.g. a 2019 edition. Editioning can provide stability for complex software engineering scenarios utilizing an online resource. Some software engineering teams, however, may choose to utilize fresh dumps or data exports of the freshest edition. SEMANTIC WEB A machine-utilizable lexicon could include a semantic model of its contents and a SPARQL endpoint. MACHINE-UTILIZABLE DEFINITIONS Machine-utilizable definitions, available in a number of knowledge representation formats, can be granular, detailed and nuanced. There exist a large number of use cases for machine-utilizable definitions. One use case is providing natural language processing components with the capabilities to semantically interpret natural language, to utilize automated reasoning to disambiguate lexemes, phrases and sentences in contexts. Some contend that the best output after a natural language processing component processes a portion of natural language is each possible interpretation, perhaps weighted via statistics. In this way, (1) natural language processing components could process ambiguous language, (2) other components, e.g. automated reasoning components, could narrow sets of hypotheses utilizing dialogue contexts, (3) other components, e.g. automated reasoning components, could narrow sets of hypotheses utilizing knowledgebase content, and (4) mixed-initiative dialogue systems could also ask users questions to narrow sets of hypotheses. Such disambiguation and interpretation would utilize machine-utilizable definitions of senses of lexemes. CONJUGATION, DECLENSION AND THE URL-BASED SPECIFICATION OF LEXEMES AND LEXICAL PHRASES A grammatical category [2] is a property of items within the grammar of a language; it has a number of possible values, sometimes called grammemes, which are normally mutually exclusive within a given category. Verb conjugation, for example, may be affected by the grammatical categories of: person, number, gender, tense, aspect, mood, voice, case, possession, definiteness, politeness, causativity, clusivity, interrogativity, transitivity, valency, polarity, telicity, volition, mirativity, evidentiality, animacy, associativity, pluractionality, reciprocity, agreement, polypersonal agreement, incorporation, noun class, noun classifiers, and verb classifiers in some languages [3]. By combining the grammatical categories from each and every language together, we can precisely specify a conjugation or declension. For example, the URL: https://machine.wiktionary.org/wiki/lookup.php?edition=2018&language=en-US&… includes an edition, a language of a lemma, a lemma, a lexical category, and conjugates (with ellipses) the verb in a language-independent manner. We can further specify, via URL query string, the semantic sense of a grammatical element: https://machine.wiktionary.org/wiki/lookup.php?edition=2018&language=en-US&… Specifying a grammatical item fully in a URL query string, as indicated in the previous examples, could result in a redirection to another URL. That is, the URL: https://machine.wiktionary.org/wiki/lookup.php?edition=2018&language=en-US&… could redirect to: https://machine.wiktionary.org/wiki/index.php?edition=2018&id=12345678 or to: https://machine.wiktionary.org/wiki/2018/12345678/ and the URL with a specified semantic sense: https://machine.wiktionary.org/wiki/lookup.php?edition=2018&language=en-US&… could redirect to: https://machine.wiktionary.org/wiki/index.php?edition=2018&id=12345678&sens… or to: https://machine.wiktionary.org/wiki/2018/12345678/4/ The URL https://machine.wiktionary.org/wiki/2018/12345678/ is intended to indicate a conjugation or declension with one or more meanings or senses. The URL https://machine.wiktionary.org/wiki/2018/12345678/4/ is intended to indicate a specific sense or definition of a conjugation or declension. A feature from having URL’s for both conjugations or declensions and for specific meanings or senses is that HTTP request headers can specify languages and content types of the output desired for a particular URL. The provided examples intended to indicate that each complete, language-independent conjugation or declension can have an ID number as opposed to each headword or lemma. Instead of one ID number for all variations of “fly”, there is one ID number for “flew”, another for “have flown”, another for “flying”, and one for each conjugation or declension. Reasons for indexing the conjugations and declensions instead of traditional headwords or lemmas include that, at least for some knowledge representation formats, the formal semantics of the definitions vary per conjugation or declension. CONCLUSION This letter broached machine wiktionaries and some of the services which could exist at https://machine.wiktionary.org/ . It is my hope that this letter indicated a few of the many exciting topics with regard to machine-utilizable crowdsourced lexicons. REFERENCES [1] https://en.wiktionary.org/wiki/Index:All_languages#List_of_languages [2] https://en.wikipedia.org/wiki/Grammatical_category [3] https://en.wikipedia.org/wiki/Grammatical_conjugation [4] https://en.wikipedia.org/wiki/List_of_HTTP_header_fields#Request_fields

2 1

Wednesday: Technical Advice IRC Meeting
by Michael Schönitzer 29 May '18

29 May '18

Sorry for cross-posting! Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 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.

1 0

postgres support in CI
by Antoine Musso 29 May '18

29 May '18

Hello, Thanks to Kunal Mehta, CI now supports running MediaWiki tests using the Postgres database! It has been requested since 2012 ( T39602 ) and finally came to fruition. Unsurprisingly, a few tests are failing and require some assistance. Anyone is welcome to help on that front. See T195807 for a list. Please celebrate Kunal! [T39602] Jenkins: Set up PHPUnit testing on PostgreSQL backend https://phabricator.wikimedia.org/T39602 [T195807] Fix failing MediaWiki core tests on Postgres database backend https://phabricator.wikimedia.org/T195807 -- Antoine "hashar" Musso

1 0

Adding a page creation log to MediaWiki
by Ryan Kaldari 28 May '18

28 May '18

One of the projects that I worked on during the Hackathon was resolving the 11-year old request to add a page creation log to MediaWiki ( https://phabricator.wikimedia.org/T12331). Up til now, we've logged page deletions and page moves, but not page creations. Having such a log is important for two reasons: * Currently, it is difficult for non-administrators to identify abusive spammer/PR accounts since much of the paper trail of their work is hidden by page deletions. * Currently, it is difficult to get data/metrics about page creation since the page table doesn't include information about when an article was created (or by whom) and the revision and recentchanges tables don't include deleted revisions. The patch to add this logging still needs to be reviewed/merged and any assistance with that would be greatly appreciated: https://gerrit.wikimedia.org/r/#/c/399897/ The feature has been put behind a feature flag so that any wikis worried about logging blot (i.e. Wikidata) can keep it disabled.

1 0

Re: [Wikitech-l] Wikitech-l Digest, Vol 178, Issue 36
by oldrik sobgui 27 May '18

27 May '18

Q Le 22 mai 2018 13:01, <wikitech-l-request(a)lists.wikimedia.org> a écrit : > Send Wikitech-l mailing list submissions to > wikitech-l(a)lists.wikimedia.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > or, via email, send a message with subject or body 'help' to > wikitech-l-request(a)lists.wikimedia.org > > You can reach the person managing the list at > wikitech-l-owner(a)lists.wikimedia.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Wikitech-l digest..." > > > Today's Topics: > > 1. TechCom Radar 2018-05-19 (Kate Chapman) > 2. [nominations needed] Wikimedia Technical Conference > (Deborah Tankersley) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 21 May 2018 13:42:49 -0700 > From: Kate Chapman <kate(a)cascadiatm.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: [Wikitech-l] TechCom Radar 2018-05-19 > Message-ID: <a56da236-11a4-6898-9102-a171a15882b8(a)cascadiatm.com> > Content-Type: text/plain; charset=utf-8 > > Hi All, > > Here are the minutes from this week's TechCom meeting: > > TechCom held a public meeting at the Hackathon in Barcelona. These > minutes are the result of that meeting. > > * Detailed Meeting Notes: > <https://etherpad.wikimedia.org/p/wmhack2018-techcom> > > * No public IRC RFC meeting on 2018-05-23 > > * No internal TechCom meeting on 2018-05-23 > > * There is a request for feedback on the future of extension management > (not an official TechCom RFC yet, but is being monitored) > <https://www.mediawiki.org/wiki/Requests_for_comment/ > Extension_management_feedback> > > * Held a public discussion of TechCom’s Platform Architecture Principles > <https://www.mediawiki.org/wiki/Wikimedia_Technical_ > Committee/MediaWiki_Platform_Architecture_Principles> > Notes: > <https://www.mediawiki.org/wiki/Wikimedia_Technical_ > Committee/MediaWiki_Platform_Architecture_Principles/Hackathon_Notes_2018> > > * TechCom-RFC Inbox was empty so no new RFCs were triaged: > <https://phabricator.wikimedia.org/tag/techcom-rfc/> > > You can also find our meeting minutes at > <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes> > > See also the TechCom RFC board > <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. > > -- > Kate Chapman > TechCom Facilitator (Contractor) > > > > > ------------------------------ > > Message: 2 > Date: Tue, 22 May 2018 00:47:53 +0200 > From: Deborah Tankersley <dtankersley(a)wikimedia.org> > To: wikitech-l <wikitech-l(a)lists.wikimedia.org>, A public mailing > list about Wikimedia Search and Discovery projects > <discovery(a)lists.wikimedia.org> > Subject: [Wikitech-l] [nominations needed] Wikimedia Technical > Conference > Message-ID: > <CABo2faawcr0soHZn4ju5xThQPD2dog+rypLYG3mMm9fAGfK4og@mail. > gmail.com> > Content-Type: text/plain; charset="UTF-8" > > *Hello,We recently announced the new Wikimedia Technical Conference > (TechConf) during the closing session of the Barcelona Hackathon on May 20, > 2018. We are sending this email to give an update on the planning and > organization, and to also let everyone know how the nomination process will > work for those interested in attending. The Wikimedia Technical Conference > will take place in Portland, OR, USA on October 22-25, 2018. And, as > mentioned in previous emails [1][2] and on the wiki page [3], this > conference will be focused on the cross-departmental program called > Platform Evolution. We will be providing more information and context as we > go along in the process.For this conference, we are looking for diverse > stakeholders, perspectives, and experiences that will help us to make > informed decisions for the future evolution of the platform. We need people > who can create and architect solutions, as well as those who actually make > decisions on funding and prioritization for the projects.Later this week, > we will send out a form to provide more detailed information on the > nomination process and how to nominate people (or it can be yourself) to > attend this conference, along with the skills, experiences, and/or > backgrounds that we are looking for. Due to the time needed for visa > application and other constraints, the deadline for nominations will be > June 8th. Please make sure that you don’t miss the deadline!If you have any > questions, please post them on the talk page [4][1] > https://lists.wikimedia.org/pipermail/mediawiki-l/2018-April/047367.html > <https://lists.wikimedia.org/pipermail/mediawiki-l/2018-April/047367.html> > [2] https://lists.wikimedia.org/pipermail/wikitech-l/2018- > April/089738.html > <https://lists.wikimedia.org/pipermail/wikitech-l/2018-April/089738.html> > [3] https://mediawiki.org/wiki/Wikimedia_Technical_Conference/2018 > <https://mediawiki.org/wiki/Wikimedia_Technical_Conference/2018> [4] > https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018 > <https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018> > * > > *Cheers from the Program Committee:* > *Kate, Corey, Joaquin, Greg, Birgit and TheDJ* > > -- > > deb tankersley > > Program Manager, Engineering > > Wikimedia Foundation > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > ------------------------------ > > End of Wikitech-l Digest, Vol 178, Issue 36 > ******************************************* >

1 0

Kio faras vin feliĉa ĉi-semajne? / What's making you happy this week? (Week of 27 May 2018)
by Pine W 27 May '18

27 May '18

The Wikidata development team released to production the first version of Wikidata support of lexicographical data: https://lists.wikimedia.org/ pipermail/wikidata/2018-May/012090.html. A large issue of *The Signpost* was published with several thought-provoking pieces: https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2018-05-24. Multilingual captions will be an early feature of structured data on Commons. A request for feedback is here: https://commons.wikimedia.org/ wiki/Commons:Structured_data/Get_involved/Feedback_requests/Multilingual_ Captions_and_MediaInfo What's making you happy this week? You are welcome to comment in any language. Pine ( https://meta.wikimedia.org/wiki/User:Pine )

1 0

Announcing the Wikimedia Foundation's Technical Engagement team
by Victoria Coleman 26 May '18

26 May '18

Hello everyone, to better serve the technical communities that build free and open source software for the movement as well as the communities who use Wikimedia's APIs to interact with our projects, the Wikimedia Foundation is making some structural changes. The Technical Engagement team is a new team in the Technology department of the Wikimedia Foundation reporting to the Foundation's Chief Technology Officer (CTO), Victoria Coleman. This new team has two sub-teams: the Wikimedia Cloud Services team and the Technical Advocacy team. Bryan Davis will manage the Technical Engagement teams. He will also lead the hiring process for a new Developer Advocacy Manager position, which will take over some of the management duties. The Wikimedia Cloud Services team will continue to focus on maintaining the Wikimedia Cloud VPS infrastructure as a service <https://en.wikipedia.org/wiki/Cloud_computing#Infrastructure_as_a_service_.…> platform, the Toolforge platform as a service <https://en.wikipedia.org/wiki/Platform_as_a_service> project, and additional supporting technologies used in the Cloud Services environment such as the Wiki Replica databases and the hosting infrastructure for dumps.wikimedia.org <https://dumps.wikimedia.org/>. The existing team of Andrew Bogott, Arturo Borrero Gonzalez, Brooke Storm, and Chase Pettet will be joined by James Hare in the role of Product Manager. The team is also hiring for a fifth Operations Engineer and for a part-time technical support contractor. The Technical Advocacy team will focus on creating improved documentation for Wikimedia APIs and services as well as providing support for technical contributors and API consumers. The new team is being formed by moving the Foundation's Developer Relations team to the Technology department, with the exception of Rachel Farrand who will remain in Community Engagement in close collaboration with other event organizers. Andre Klapper and Srishti Sethi are both taking the role of Developer Advocate in the new team. A developer advocate is someone whose primary responsibility is to make it easy for developers to use a platform. Typically they do this by producing example software, tutorials, and other documentation explaining how to use the platform's products and services. Sarah R. Rodlund will also be joining the team as a Technical Writer. Technical writing has many subspecialties. Sarah will be focusing on improving our existing documentation by helping create a style guide and editing existing documentation to fit with that guide. She will also be supporting volunteers who are interested in practicing their technical writing skills on Wikimedia documentation. The team will be hiring for a Developer Advocacy Manager role in July. This new person will help round out the skills of the team and will take the lead in developing their programs. The Technical Engagement team will work with other teams inside the Wikimedia Foundation as well as groups at affiliate organizations and the larger Wikimedia volunteer community to provide technical outreach services and support. We hope to continue to grow the number of people involved in our programs until we can confidently say that we are providing the best help possible to the hundreds of volunteer developers, designers, technical writers, and end users of the Wikimedia movement's APIs and services. We will continue to be involved in existing programs to attract and support new technical contributors like the Wikimedia Hackathons, Outreachy, and Google Summer of Code. We also hope to find new ways to connect with new and existing technical contributors as we support the Wikimedia movement's 2030 strategic direction and the shared goals of knowledge as a service and knowledge equity. Very excited to be getting started down the path of strengthening our developer advocacy program! Best wishes, Victoria Coleman Chief Technology Officer Wikimedia Foundation 1 Montgomery Street, Suite 1600 San Francisco, CA 94104 +1-650-703-8112 vcoleman(a)wikimedia.org

3 2

MediaWiki-CodeSniffer 19.0.0 and 20.0.0 released
by Kunal Mehta 25 May '18

25 May '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello! With MediaWiki core now requiring PHP 7.0 or HHVM as the minimum version, CodeSniffer will now also require the same, and targets those versions as the minimum for the code it will be checking starting with version 20.0.0. 19.0.0 contains new sniffs and bug fixes, and is the last version to support PHP 5.5 and 5.6. I will have libraryupgrader upgrade all repositories directly to 20.0.0. If you want to continue to support older PHP versions in your project, upgrade your project to use 19.0.0 directly. libraryupgrader will skip projects using that version, since it means you explicitly want to support older PHP versions. Here's the changelog for 19.0.0: * Add break and continue to ParenthesesAroundKeywordSniff (Umherirrender ) * Check if the default of null is in the type list of @param (Umherirrender) * Do not enforce name for traits with phpunit annotations (Umherirrender ) * Don't allow 'iterable' type hint (Kunal Mehta) * Prevent usage of nullable and void type hints (Kunal Mehta) * Prohibit PHP's vanilla execution (Max Semenik) * Reorganize PHP 7.0 compatibility sniffs into a category (Kunal Mehta) And for 20.0.0: * Require PHP 7 or HHVM to run (Kunal Mehta) * Document why we still need to keep ScalarTypeHintUsageSniff (Kunal Mehta) * Drop PHP7UnicodeSyntaxSniff sniff (Kunal Mehta) - -- Legoktm -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlsHy48ACgkQUvyOe+23 /KICmA/+OCzvr49gSu8VeB4+dQZR2qHp25rdShszsmsqr6iXKeObxUahLM0TcgtO 3x/TNCuT2uGnXrwVhzfqIglj0xs85niRx11tvCAm1rFPCMZKW8k1usA/s7nI5yQ4 3vnlkyZxhTKL+4VG0U0v2aMcQh8h+WhLyGqFZ9BW9CxzjZpxXuNJ/mP7KJtqaCZp EH/23gzf/fez1szV6ZIeh42Bv11HRxZBGpiJGnh7Vs5xKmwzfhUZQsvKBq5vBit0 +snbt+c4QpqZ9hEsa5vFqYQKDRj6EybuFlTLRmPYXScfm0udm+6h5EqCfuz2QdUB n88Cc/FApsgtUlve0LsOalpU/ePvEd3TPb33LU1mc/+bhBZs4j1E5mHlgmI28pWA 1UxuK8V5KP63ZcaWQsemU7vQ4wnS0PyPF+gabDxLmJNtW929AZe52mZxKq7lBO4K rUdqHoGZylmIM/etM5LLnEpZ2rNPL9+S+JAtFV/kke60F6VLVFgfDMIVH3phvj7t HrO2J+jq5eRQ8C4K1zvMXpyz1+vBtxma1yBsZMcrZZOlMaxoTjczWoLro3izBqs4 6BIZD4koEdtOJhcsz1GgnyaF6jGpWESirjwf9zRoruoZfGMrozEpvrk4SRiuHVoF PqBs9bSUJ+IjrzQZD4dtdBEcb1m6sZ6UlQhxJ+8TQ3ChnHIGM5I= =jP1N -----END PGP SIGNATURE-----

1 0

MediaWiki core master now requires PHP 7.0 or HHVM
by Kunal Mehta 25 May '18

25 May '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, MediaWiki core's master branch now requires a minimum of PHP 7.0 or HHVM[1], as decided upon in the RfC. CI has been updated no longer run PHP 5.5 tests. There are already quite a few patches[2] to remove code that isn't necessary now, or start using new features :) But out of caution, we're waiting until after next week's Wikimedia train deploy before merging those to ensure it doesn't need to be reverted for any reason. It's important to remember that while nearly all of the new PHP 7.0 features can now be used, they still need to be supported in HHVM (with hhvm.php7.all disabled). Notably, this means that scalar type hints cannot be used. PHPCS should prevent those features from being used (more on that in a separate email). Thanks to everyone who made this finally happen, especially the Wikimedia Operations team :) - -- Legoktm [1] https://gerrit.wikimedia.org/r/#/c/405216/ [2] https://gerrit.wikimedia.org/r/#/q/topic:new-php -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlsHydgACgkQUvyOe+23 /KJvEBAAj3ljVLOuSQitaB+6xakUTlZZpkcjRLyrbJ8KbfxyycB94pzlZ4fRdqHY nBnrokrawqQqgVEai9hq7nfVngWYH2eC11dhIXrpj2oklxswVaOxxwhPF92SJ9IP cuDawz9v6sqgMKDnQmHmTkpNmsWzez4d7LZMPW6UHKSGBl48ZZc5ZiTYlFyBKeLB BY5CNHY41flx21Z+BTQBQ2+tZ/Fm2kv6tAgI9gj8wpS5lviq1bhO+AH2/7qEcpjm LHZTcvrxHgctgU8XbEWXeGbNKK9/JUyuHApiDcgSXi81qGRHgaUytmYunXNQmsP8 51GzpGBL8R7YVP6uPFeYEcEJgvFAFa+xyeGHjDtTNniUj5co3eVixWvD668jCFc9 Lfd4O73vNMQluksNw81DEZQ5Pt+MMhA1DMqmAw+rwRYVdunfbumhh1uze03nJuCj Pk386sJkXVmawbc8PV9U8tnUoNIY+ngdzjl0ivOGwlxRpt30Usv0XxiA2i1R9IUU +BNGETmgpRg9i7cA4yqYGeOUeiYQhh4PHQeKIURp0M7BHChYsRCUqg6+blSNRqf4 TXpwIzAZ7Y3DjCxJLmn2zF1wHu5qSF20Af+hCf6A3WzYrnULGe2UtAk2BdOpJJ7h zgtG/lLuQPHCXxAfrP8gkVtfkTL+LGD1ZZm+AGlpDWYNNnB5pqE= =Xzun -----END PGP SIGNATURE-----

1 0

Today: Technical Advice IRC Meeting
by Michael Schönitzer 23 May '18

23 May '18

Sorry for cross-posting! Reminder: Technical Advice IRC meeting again **today, Wednesday 3-4 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.

1 0

TechCom Radar 2018-05-19
by Kate Chapman 21 May '18

21 May '18

Hi All, Here are the minutes from this week's TechCom meeting: TechCom held a public meeting at the Hackathon in Barcelona. These minutes are the result of that meeting. * Detailed Meeting Notes: <https://etherpad.wikimedia.org/p/wmhack2018-techcom> * No public IRC RFC meeting on 2018-05-23 * No internal TechCom meeting on 2018-05-23 * There is a request for feedback on the future of extension management (not an official TechCom RFC yet, but is being monitored) <https://www.mediawiki.org/wiki/Requests_for_comment/Extension_management_fe…> * Held a public discussion of TechCom’s Platform Architecture Principles <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/MediaWiki_Plat…> Notes: <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/MediaWiki_Plat…> * TechCom-RFC Inbox was empty so no new RFCs were triaged: <https://phabricator.wikimedia.org/tag/techcom-rfc/> You can also find our meeting minutes at <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes> See also the TechCom RFC board <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. -- Kate Chapman TechCom Facilitator (Contractor)

1 0

Wiki Dialogue Systems
by Adam Sobieski 21 May '18

21 May '18

INTRODUCTION Some technical topics are broached toward the crowdsourcing of dialogue system content and behavior. COLLABORATIVE AUTHORING The content and behavior of a dialogue system can be represented in a number of ways. Firstly, the content and behavior of a dialogue system can be represented in programming language source code files. Collaborative authoring, in this case, is a matter of integrated development environments and source code repositories, version control systems. Secondly, some or all of the content and behavior of a dialogue system can be separated from the source code files as data stored in some data format or in a database. Collaborative authoring, in this case, could require custom software tools. Thirdly, a number of services, cognitive services, can encapsulate the content and behavior of a dialogue system. Collaborative authoring, in this case, could require utilization of such services or related user interfaces. Fourthly, the content and behavior of a dialogue system can be represented as a set of interrelated, URL-addressable, editable pages. Servers can provide content for a number of different content types, for example hypertext for content authors and other formats for dialogue system user agents. Server-side scripting can be utilized to generate pages and generated pages can contain client-side scripting. Fifthly, the content and behavior of a dialogue system can be represented as a set of interrelated, URL-addressable, editable diagrams. Sixthly, the content and behavior of a dialogue system can be represented in transcript form. Transcript-based user interfaces may resemble instant messaging applications, scrollable sequences of speech bubbles, with speech bubbles coming from the left and right sides, such that users can edit the content in dialogue systems’ speech bubbles. Users could opt to view more than plain text in speech bubbles. There could also be vertical, colored bands in one or both margins, visually indicating discourse behaviors, moves, objectives or plans which span one or multiple utterances. COLLABORATIVE DEBUGGING Debugging dialogue systems is an important topic. Debugging scenarios include switching from interactions with dialogue systems to authoring processes such that dialogue context data is preserved. NATURAL LANGUAGE GENERATION AND UNDERSTANDING Natural language generation can produce editable structured documents from the data stored in databases and knowledgebases. Generated content can contain, beyond natural language, data and program logic to facilitate the processing of constrained or unconstrained edits. Edits to generated content can result in changes to stored data. COMPUTER-AIDED WRITING Computer-aided writing can convenience content authors and assure quality. Software can, generally speaking, provide users with information, warnings and errors with regard to tentative edits. Software can support users including with regard to their spelling, grammar, word selection, readability, text coherence and cohesion. Software can measure the neutral point of view of natural language. Software can also process tentative edits with regard to their logical consistency with respect to data stored in databases and knowledgebases. WIKI DIALOGUE SYSTEMS Exploration into the collaborative authoring and debugging of dialogue systems could result in new wiki technologies. Wiki dialogue systems could resemble spoken language dialogue systems with transcript-based user interfaces, users able to easily switch between dialogue-based interactions and the editing of dialogue system content and behavior. Best regards, Adam Sobieski http://www.phoster.com/contents/

1 0

[mediawiki/core CR request] Translate special pages into Gorontalo
by Martin Urbanec 20 May '18

20 May '18

Hello all, I'd like to request CR+2 of https://gerrit.wikimedia.org/r/#/c/428915/, which is translating special pages into Gorontalo. Thanks in advance, Martin

1 0

Download a wiki?
by Bart Humphries 20 May '18

20 May '18

We have a very old wiki which has basically never been updated for the past decade and which was proving stubbornly resistant to updating several years ago. And now the owner of the server has drifted away, but we do still have control over the domain name itself. The best way that we can think of to update everything is to scrape all of the pages/file, add them to a brand new updated wiki on a new server, then point the domain to that new server. Yes, user accounts will be broken, but we feel that this is the most feasible solution unless someone else has another idea. However, there's a lot of pages on meritbadge.org -- which is the wiki I'm talking about. Any suggestions for how to automate this scraping process? I can scrape the HTML off every page, but what I really want is to get the wikitext off of every page. Bart Humphries bart.humphries(a)gmail.com (909)529-BART(2278)

4 4

⠠⠺⠓⠁⠞⠄⠎ ⠍⠁⠅⠊⠝⠛ ⠽⠕⠥ ⠓⠁⠏⠏⠽ ⠞⠓⠊⠎ ⠺⠑⠑⠅⠦ / What's making you happy this week? (Week of 20 May 2018)
by Pine W 20 May '18

20 May '18

*Between the Brackets* Yaron Koren produced a 30 minute digest of previous episodes of this podcast. Much of the episode will be understandable by people who are not developers but are familiar with how MediaWiki works. I enjoyed listening to this: https://betweenthebrackets.libsyn.com/episode-8-btb-digest-1 *WMF awards of Project Grants and Rapid Grants* * Nine Rapid Grants, with maximum amounts of $2000 each, were awarded to promote readership: https://blog.wikimedia.org/2018/05/16/rapid-grants-awarded/ * Eleven Project Grants, totaling $354,654, were awarded for diverse projects: https://lists.wikimedia.org/pipermail/wikimedia-l/2018-May/090291.html. There will be a Project Showcase video meeting on June 14. *Reports from Wikimedia Conference 2018 participants* I especially appreciated this detailed report from Peaceray and Joe Mabel which mentions a wide range of subjects including Structured Data on Commons, Learning Days, possible ways to incorporate more diverse citations into Wikipedia, lightning talks, libraries and partnerships, and general thoughts about the conference: https://meta.wikimedia.org/wiki/Cascadia_Wikimedians/2018_Wikimedia_Confere…. Conference reports are currently available in English, Thai, French, Ukrainian, Latvian, German, and Polish: https://meta.wikimedia.org/wiki/Wikimedia_Conference_2018/Further_reports. *Report from the Wikimedia Conference 2018 Strategy Track* Significant good-faith effort appears to be invested in the strategy process: https://meta.wikimedia.org/wiki/Wikimedia_Conference_2018/Documentation/Mov… What's making you happy this week? You are welcome to comment in any language. Pine ( https://meta.wikimedia.org/wiki/User:Pine )

1 0

PHPUnit 6+ on older versions of MW
by Jeroen De Dauw 17 May '18

17 May '18

Hey, I updated one of my extensions to use PHPUnit 6+ and am having troubles getting the tests to run with older versions of MediaWiki. In particular, I'd like my tests to run with MW 1.27. I suspect this is somehow possible and has already been done in other extensions. Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software Crafter | Speaker | Student | Strategist | Contributor to Wikimedia and Open Source ~=[,,_,,]:3

2 3

Provide input on the future direction of MediaWiki's extension management system
by Kunal Mehta 17 May '18

17 May '18

Hi everyone, As part of the MediaWiki Platform Team's goal to develop a roadmap for MediaWiki, we want to solicit input on the future direction of MediaWiki's extension management system. One of MediaWiki's greatest strengths is the diverse extension ecosystem. But navigating that ecosystem and managing those extensions can be difficult and cumbersome. Please provide input on what features you'd like to see at: <https://www.mediawiki.org/wiki/Requests_for_comment/Extension_management_fe…>. You can suggest a specific feature, or endorse and comment on other people's proposals. I've put down a few proposal to help start the discussion, but I'm sure that everyone has plenty more :-). The goal will be to collate the input provided there, and use it to plan future development work on improving extension management. If you know other people who use MediaWiki and have valuable opinions, please let them know about the RfC. Thanks, Kunal / Legoktm

1 0

2018-05-16 Scrum of Scrums meeting notes
by Grace Gellerman 16 May '18

16 May '18

https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-05-16 =2018-05-16= == Callouts == * Fundraising campaigns https://meta.wikimedia.org/wiki/CentralNotice/Calendar * Readers Web, Performance: Help reviewing the CitationUsage schema instrumentation: https://gerrit.wikimedia.org/r/#/c/432534/. * Modern Event Platform -- Analytics starting interviewing user, anyone interested should reach Andrew Otto ( https://phabricator.wikimedia.org/T185233) == Audiences == === Readers === ==== iOS native app ==== * Blocked by: * Blocking: * Updates: **5.8.1 released; small bug fixes + Wikidata magic word override ( https://phabricator.wikimedia.org/project/view/3339/ ) **Continuing work on tech debt release, 5.8.2 ( https://phabricator.wikimedia.org/project/view/3358/ ) ==== Android native app ==== * Blocked by: * Blocking: * Updates: ** ==== Readers Web ==== * Blocked by: * Blocking: * Updates: **Working with Services on Proton (Chromium PDF rendering backend service) instrumentation https://phabricator.wikimedia.org/T189307 **Page issues A/B testing framework in progress https://phabricator.wikimedia.org/T193584 **Team is at offsite + hackathon so not much else going on **Full stack engineer backfill hiring continues **Minor Popups refactoring *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra ==== Readers Infrastructure ==== * Blocked by: ** RelEng on https://gerrit.wikimedia.org/r/#/c/432310/ * Blocking: * Updates: ** Closed out most follow-up work for Short description magic word. ** Reading list browser extensions (Chrome/FF/Safari) coming soon. *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra **[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of client apps by coalescing and moving more logic to the server]] ***Reading Infra depends on Parsing, Services ===== Maps ===== * Blocked by: * Blocking: * Updates: ** ==== Multimedia ==== * Updates ** Hackathon prep impacting some throughput ** OOUI work on WikibaseMediaInfo elements to start soon; UploadWizard license selection getting OOUI makeover as well ** Search indexing hitting some snags - discussion ongoing *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 3.1]] Prepare for launch of the first Structured Data on Commons feature (multilingual file captions) ***SDC depends on Multimedia,SRE, WMDE, Search Platform, MediaWiki Platform, Research ** [[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 2.1]] Integrate structured file captions into search *** SDC depends on Search Platform, Multimedia **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Structured_Data#Segment_4:_Programs|Segment 4, Outcome 2]]: Develop a better understanding of existing needs for Structured Commons- T171252 ***Research depends on Multimedia === Contributors === ==== Community Tech ==== * Blocked by: * Blocking: * Updates: ** GlobalPreferences live on test wikis, will be slowly rolling it out further ** Investigating how to integrate PageTriage with ORES and some external copyvio detection service ==== Anti-Harassment Tools ==== * Blocked by: * Blocking: * Updates: ** ==== Editing ==== * Blocked by: * Blocking: ** Updates: ** ==== Parsing ==== * Blocked by: * Blocking: * Updates: *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]] Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team *** Parsing depends on MediaWiki Platform, Services **[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of client apps by coalescing and moving more logic to the server]] Increase code sharing of client apps by coalescing and moving more logic to the server. *** Reading Infra depends on Parsing, Services ** [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better data|Outcome 2: Objective 1]]: Revision storage scaling *** Services depends on SRE, Parsing ==== Collaboration ==== * Blocked by: * Blocking: * Updates: ** ==== Language ==== * Blocked by: Core Platform to take a look at: https://phabricator.wikimedia.org/T151116 - Abuse filters set to warn users require two captchas * Blocking: None * Updates: ** ContentTranslation Version 2 work continue. ** Most of team members will be at Hackathon, so slow week. *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.1]] Improve and consolidate our unified editing platform so that it's great on all devices ***Language depends on Editing === Audiences Design === * Blocked by: * Blocking: * Updates: ** ==== UI Standardization ==== * Blocked by: * Blocking: * Updates: ** == Technology == === Analytics === * Blocked by: * Blocking: * Updates: ** Modern Event Platform -- We're starting interviewing user, anyone interested should reach Andrew Otto ( https://phabricator.wikimedia.org/T185233) ** We have a replacement for pivot called Turnilo (exact same but opensource) - https://turnilo.wikimedia.org - We'll soon redirect pivot URLs to turnilo ** Geoeditors available in Hive and Druid - https://wikitech.wikimedia.org/wiki/Analytics/Data_Lake/Edits/Geoeditors - Dashboard in Superset (wikitech account + ping to analytics needed) ** virtualpageview_hourly (aggregation of pageviews and page-previews) are available in hive and druid ** Testing of Druid 0.11 is done, some changes in how we handle streaming data to be done before rolling out ** Burrow (Kafka monitoring tool) has been upgrade to version 1.1 === Cloud Services === * Blocked by: * Blocking: * Updates: ** === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** === MediaWiki Platform === * Blocked by: * Blocking: * Updates: ** *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]] Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team ***Parsing depends on MediaWiki Platform, Services **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research ** [[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 1.1]] Assist with deploying MultiContent Revisions on Commons [[phab:T174022|T174022]] Implement multi-content revisions, [[phab:T174023|T174023]] Implement MCR storage layer, [[phab:T174045|T174045]] DB schema migration for MCR, [[phab:T174044|T174044]] Deploy MCR storage layer, [[phab:T174043|T174043]]Deploy Multi-Content Revisions ***SDC depends on MediaWiki Platform, WMDE === Performance === * Blocked by: ** * Blocking: ** * Updates: ** === Release Engineering === * Blocked by: * Blocking: * Updates: ** Most of the team are in Barcelona this week for the Wikimedia hackathon as well as a team offsite. Ping twentyafterfour in #wikimedia-releng if you need assistance. *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra === Research === * Blocked by: None (just waiting for some reviews on schema instrumentation code) * Blocking: None * Updates: ** Finished up the first version of the CitationUsage schema instrumentation. https://gerrit.wikimedia.org/r/#/c/432534/ ** Working on improving the recommendation API algorithm. https://phabricator.wikimedia.org/T190774 *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Structured_Data#Segment_4:_Programs|Segment 4, Outcome 2]]: Develop a better understanding of existing needs for Structured Commons- [[phab:T171252|T171252]] ***Research depends on Multimedia === Scoring Platform === * Blocked by: * Blocking: * Updates: === Search Platform === * Blocked by: * Blocking: * Updates: ** *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|*Objective 2.1]] Integrate structured file captions into search *** SDC depends on Search Platform, Multimedia === Security === * Blocked by: * Blocking: * Updates: ** *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]]: Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team ***Parsing depends on MediaWiki Platform, Services === Services === * Blocked by: * Blocking: * Updates: ** *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of client apps by coalescing and moving more logic to the server.]] ***Reading Infra/Parsing, Services **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]] Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team ***Parsing depends on MediaWiki Platform, Services [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better data|Outcome 2: Objective 1]]: Revision storage scaling *** Services depends on SRE, Parsing === Site Reliability Engineering === * Blocked by: Collaboration on Flow dumps, T172025 * Blocking: None * Updates: ** Various SREs will be at the hackathon ** Addressing a mailing list subscription spam attack. For now it's a whack a mole game, will probably implement some captcha on registration ** Moving forward with mcrouter deployment for multi-dc https://phabricator.wikimedia.org/T192370 ** Debmonitor passed reviews, pending deployment https://phabricator.wikimedia.org/T191298 ** Looking at AES128-SHA usage from toolforge bots ** Proton deployment passed beta by services, proceeding with production deployment ** *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption. Proton deployment passed beta by services, proceeding with production deployment *** Reading Web depends on SRE, RelEng, Reading Infra **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better data|Outcome 2: Objective 1]]: Revision storage scaling *** Services depends on SRE, Parsing == Wikidata == * Blocked by: * Blocking: * Updates: ** *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 1.1]] Assist with deploying MultiContent Revisions on Commons [[phab:T174022|T174022]] Implement multi-content revisions, [[phab:T174023|T174023]] Implement MCR storage layer, [[phab:T174045|T174045]] DB schema migration for MCR, [[phab:T174044|T174044]] Deploy MCR storage layer, [[phab:T174043|T174043]]Deploy Multi-Content Revisions ***SDC depends on MediaWiki Platform, WMDE == German Technical Wishlist == * Blocked by: * Blocking: * Updates: ** == SoS Meeting Bookkeeping == * Updates: **

1 0

Recent Account hijacking activities
by John Bennett 16 May '18

16 May '18

*On 8 May 2018, account hijacking activities were discovered on Wikiviajes - Spanish Wikivoyage (es.wikivoyage.org <http://es.wikivoyage.org>). It was identified by community stewards and communicated to the Trust and Safety, Legal, and Security teams who responded to the event. At this time the event is still under investigation and we are unable to share more about what is being done without risking additional hijacking of accounts. However, we feel it is important to share what details we can and inform the community of what happened. Similar to past security incidents, we continue to encourage everyone to take some routine steps to maintain a secure computer and account - including regularly changing your passwords, actively running antivirus software on your systems, and keeping your system software up to date. The Wikimedia Foundation's Security team and others are investigating this incident as well as potential improvements to prevent future incidents. We are also working with our colleagues in other departments to develop plans for how to best share future status updates on each of these incidents. However, we are currently focused on resolving the issues identified. If you have any questions, please contact the Trust and Safety team (ca{{(a)}}wikimedia.org <http://wikimedia.org>). John BennettDirector of Security, Wikimedia Foundation*

3 2

Upcoming WMCS network outages: Tuesday May 15th
by Andrew Bogott 16 May '18

16 May '18

As part of some long-deferred routine maintenance, we need to update (and, in one case, physically move) the network servers that handle all traffic between WMCS instances. During each change, all WMCS network traffic (including network access to all tools and VMs) will be interrupted for several minutes. The first outage will be: Tuesday, May 15 at 13:00 UTC The second outage will be three hours later: Tuesday, May 15 16:00 UTC In each case outages should last no more than ten to fifteen minutes. More details about this move can be found at https://phabricator.wikimedia.org/T193579 . -Andrew

1 7

Wednesday: Technical Advice IRC Meeting
by Michael Schönitzer 15 May '18

15 May '18

Sorry for cross-posting! Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 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.

1 0

Audiences Q3 FY1718 Quarterly Check-In slides & notes
by Megan Neisler 15 May '18

15 May '18

*Hi Wikitech-l,Slide decks and notes from the recent FY1718 Q3 Audiences Quarterly Check-Ins are posted as follows:Audiences 1 (Contributors):slides <https://commons.wikimedia.org/wiki/File:WMF_Contributors_Team_May_2018_Quar…>& notes <https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/Quarterly_…>Audiences 2 (Readers, Technical Program Management, Product Design Strategy, and Wikidata): slides <https://commons.wikimedia.org/wiki/File:WMF_Reading,_PM,_Design_Research,_W…>& notes <https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/Quarterly_…>These and other links are also posted on the quarterly checkin page <https://meta.wikimedia.org/w/index.php?title=Wikimedia_Foundation_Annual_Pl…> .Thanks,Megan* -- Megan Neisler Senior Project Coordinator - Audiences & Technology Wikimedia Foundation

1 0

(no subject)
by Liza Rustanto 15 May '18

15 May '18

-- Liza Rustanto

1 0

GSoC 2018 Introduction: Hagar Shilo
by Hagar Shilo 14 May '18

14 May '18

Hi All, My name is Hagar Shilo. I'm a web developer and a student at Tel Aviv University, Israel. This summer I will be working on a user search menu and user filters for Wikipedia's "Recent changes" section. Here is the workplan: https://phabricator.wikimedia.org/T190714 My mentors are Moriel and Roan. I am looking forward to becoming a Wikimedia developer and an open source contributor. Cheers, Hagar

8 11

Nini kinakufanya uwe na furaha wiki hii? / What's making you happy this week? (Week of 13 May 2018)
by Pine W 13 May '18

13 May '18

>From the WMF Blog: * "The stories behind this year’s award-winning photographs from Wiki Loves Africa": https://blog.wikimedia.org/2018/05/07/wiki-loves-africa-winners/ * "Here’s everything we published from the design, development, and data process for the page previews feature": https://blog.wikimedia.org/2018/05/09/page-previews-documentation/ * "Exploring offline access to Wikipedia: WikiFundi, an editing tool for remote schools": https://blog.wikimedia.org/2018/05/10/offline-access-wikipedia-wikifundi/ >From email lists: * The This Month in GLAM newsletter for April 2018: https://lists.wikimedia.org/pipermail/wikimedia-l/2018-May/090225.html * "AdvancedSearch beta feature available on all wikis": https://lists.wikimedia.org/pipermail/wikitech-l/2018-May/089950.html, from the WMDE Technical Wishes team * Two announcements about maps: https://lists.wikimedia.org/pipermail/wikitech-l/2018-May/089878.html and https://lists.wikimedia.org/pipermail/wikitech-l/2018-May/089964.html What's making you happy this week? You are welcome to comment in any language. Pine ( https://meta.wikimedia.org/wiki/User:Pine )

1 0

Should your language change it’s map language fallbacks?
by Joe Matazzoni 11 May '18

11 May '18

Since we launched map internationalization earlier this week [1], a number of users have asked about the map language-fallback schemes and how communities can change their fallbacks (e.g., this exchange [2]). I added a post today [3] to the Map Improvements project page that goes into detail about language fallbacks. It explains how to request a change and gives an example of why some less widely translated languages, at least, might want to consider adding to their fallbacks. I’m sure there are many angles on this question we haven’t considered. If you have thoughts or questions, please share them on the project talk page [4]. We’re listening. [1] https://www.mediawiki.org/wiki/Map_improvements_2018#May_9,_2018:_Map_inter… <https://www.mediawiki.org/wiki/Map_improvements_2018#May_9,_2018:_Map_inter…> [2] https://www.mediawiki.org/wiki/Topic:Ubzgfi8j4bdsqe9p <https://www.mediawiki.org/wiki/Topic:Ubzgfi8j4bdsqe9p> [3] https://www.mediawiki.org/wiki/Map_improvements_2018#May_11,_2018:_Should_y… <https://www.mediawiki.org/wiki/Map_improvements_2018#May_11,_2018:_Should_y…>? [4] https://www.mediawiki.org/wiki/Talk:Map_improvements_2018 <https://www.mediawiki.org/wiki/Talk:Map_improvements_2018> _____________________ Joe Matazzoni Product Manager, Collaboration Wikimedia Foundation, San Francisco "Imagine a world in which every single human being can freely share in the sum of all knowledge."

1 0

Discovery Weekly Update for the week starting 2018-05-07
by Chris Koerner 11 May '18

11 May '18

Привет! Another update from the Search Platform team for the week starting 2018-05-07 **Programming note:** Due to the upcoming Wikimedia Hackathon and some (personal) holiday time, the next update will be the week of 2018-05-28. Until then, and as always, feedback and questions are welcome. == Highlights== * Map internationalization launched everywhere, and embedded maps (mapframe) are now live on 276 Wikipedias [0] * ''"Hello, my name is _____"'' is an in-depth blog post by Trey that was published earlier this week where he details the irony that searching for names is not always as straightforward as you might think. [1] == Discussions == === Search === * Erik updated a script that was populating lots of 500 errors in the logs [2] * Erik also did a lot of research to evaluate impact of adding ~2700 new shards to production cluster (there is a pdf attached to the last comment in the ticket that contains more information) [3] There is a follow-up ticket as well for the next steps [4] * Trey worked on the analysis config for the new Slovak stemmer that was deployed this week—but the plugin still needs to be deployed and the wikis re-indexed. [5] * Stas and others worked on looking up entities by external identifiers - the work is done for now, but it needs a re-index to be fully ready [6] * David worked on externalizing the parsing logic from SimpleKeywordFeature and FullTextQueryStringQueryBuilder and it was pushed into production in April 2018 [7] == Other Noteworthy Stuff == * Trey's most recent updates to transliteration on the Crimean Tatar Wikipedia are live; after a year of part-time 10% project work, the transliteration infrastructure for Crimean Tatar is done and the accuracy is in the high 90% range. [8] == Did you know? == * The English word “dove”, as the past tense of “dive”, is one of the rare cases where a conjugation has become more irregular over time. The verb “dive” picked up the strong conjugation [9] by analogy with other strong verbs, particularly “drive/drove”. [10] Going in the more typical direction of regularization, Swedish strong verbs slowly lost some of their distinctive plural forms. [11] The change started in the 16th century, and was still in progress as late as the 1940s. From the search perspective, regular forms are easier to deal with—so, way to go Swedish! [0] https://lists.wikimedia.org/pipermail/wikitech-l/2018-May/089964.html [1] https://blog.wikimedia.org/2018/05/08/searching-for-names-is-not-always-str… [2] https://phabricator.wikimedia.org/T179266 [3] https://phabricator.wikimedia.org/T192972 [4] https://phabricator.wikimedia.org/T193654 [5] https://phabricator.wikimedia.org/T191544 [6] https://phabricator.wikimedia.org/T99899 [7] https://phabricator.wikimedia.org/T188530 [8] https://phabricator.wikimedia.org/T188321 [9] https://en.wikipedia.org/wiki/Germanic_strong_verb [10] https://en.wiktionary.org/wiki/dove#Etymology_2 [11] https://en.wikipedia.org/wiki/Swedish_grammar#Historical_plural_forms --- Subscribe to receive on-wiki (or opt-in email) notifications of the Discovery weekly update. https://www.mediawiki.org/wiki/Newsletter:Discovery_Weekly The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as "Easy" or "Volunteer needed" in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R Yours, Chris Koerner Community Liaison Wikimedia Foundation

1 0

Deactivating hyperlink by CSS
by יגאל חיטרון 11 May '18

11 May '18

Hello. Is there a way to deactivate a hyperlink using CSS? I tried pointer-events: none, but wiki does not recognize it. Thank you. Igal (User:Ikhitron)

5 6

TechCom Radar 2018-05-09
by Kate Chapman 11 May '18

11 May '18

Hi All, Here are the minutes from this week's TechCom meeting: * Public IRC Meeting occurred on: Come up with a strategy for handling interface changes <https://phabricator.wikimedia.org/T193613> Notes: <https://phabricator.wikimedia.org/T193613#4195628> * No Public IRC RFC Meeting next week. * Discussed and decided not to continue discussion within TechCom, because the standard is not currently relevant: Investigate making MediaWiki\ServiceContainer compatible with PSR-11 <https://phabricator.wikimedia.org/T193722> * Discussed RFC and will put forth an additional proposal: RFC: Use ar_page_id to determine the parent IDs for undeleted revisions <https://phabricator.wikimedia.org/T193690> You can also find our meeting minutes at <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes> See also the TechCom RFC board <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. -- Kate Chapman TechCom Facilitator (Contractor)

1 0

Map internationalization launched everywhere, AND embedded maps now live on 276 Wikipedias
by Joe Matazzoni 10 May '18

10 May '18

As of today, interactive (Kartographer) maps no longer display in the language of the territory mapped; instead, you’ll read them in the content language of the wiki where they appear—or in the language their authors specify (subject to availability of multilingual data). In addition, mapframe, the feature that automatically embeds dynamic maps right on a wiki page, is now live on most Wikipedias that lacked the feature. (Not included in the mapframe launch are nine Wikipedias [1] that use the stricter version of Flagged Revisions). If you you’re new to mapframe, this Kartographer help page [2] shows how to get started putting dynamic maps on your pages. If you’d like to read more about map internationalization: this Special Update [3] explains the feature and its limiations; this post [4] and this one [5] describe the uses of the new parameter, lang=”xx”, which lets you specify a map’s language. And here are some example maps [6] to illustrate the new capabilities. These features could not have been created without the generous programming contributions and advice of our many map-loving volunteers, including Yurik, Framawiki, Naveenpf, TheDJ, Milu92, Astirlin, Evad37, Pigsonthewing, Mike Peel, Eran Roz, Gareth and Abbe98. My apologies to anyone I’ve missed. The Map Improvements 2018 [7] project wraps up at the end of June, so please give internationalized maps and mapframe a try soon and give us your feedback on the project talk page [8]. We’re listening. [1] https://phabricator.wikimedia.org/T191583 [2] https://www.mediawiki.org/wiki/Help:Extension:Kartographer [3] https://www.mediawiki.org/wiki/Map_improvements_2018#April_18,_2018,_Specia… [4] https://www.mediawiki.org/wiki/Map_improvements_2018#April_25,_2018,_You_ca… [5] https://www.mediawiki.org/wiki/Map_improvements_2018#April_26,_2018:_OSM_na… [6] https://test2.wikipedia.org/wiki/Map_internationalization_examples [7] https://www.mediawiki.org/wiki/Map_improvements_2018 [8] https://www.mediawiki.org/wiki/Talk:Map_improvements_2018 _____________________ Joe Matazzoni Product Manager, Collaboration Wikimedia Foundation, San Francisco "Imagine a world in which every single human being can freely share in the sum of all knowledge."

8 7

OOUI v0.27.0 release (breaking change)
by Volker E. 09 May '18

09 May '18

Hello everyone, We've released OOUI version 0.27.0 last evening. It will be in MediaWiki core from 1.32.0-wmf.3, which will be deployed to Wikimedia production in the regular train, starting on Tuesday 16 May. As there are five breaking changes in this release, at least nominally, please carefully consider if they affect your code. Breaking changes since last release: * GroupElement: Remove getItem(s)FromData (Prateek Saxena) We rename a number of getters when asking for one of 0+ items for consistency reasons. This and the following two changes are all on this topic. * MultiSelectWidget: Remove getSelectedItems and getSelectedItemsData (Prateek Saxena) * SelectWidget: Remove getSelectedItem (Prateek Saxena) * TagItemWidget: Replace 'disabled' items with 'fixed' (Moriel Schottlender) For consistency of behavior and separation of UX concerns, we don't allow for individual tag items in a TagMultiselectWidget to be individually disabled. Instead, allow defining 'fixed' values that cannot be removed. We are not aware of any instance of the TagMultiselectWidget featuring 'disabled' items, nevertheless marking it as breaking change. * indicators: Remove 'alert', deprecated in v0.25.2 (James D. Forrester) 'alert' indicator has been deprecated a while ago and is unused in all known implementations, therefore we've removed it completely. Deprecations since last release: * icons: Deprecate 'editing-citation' icons from 'content' (Volker E.) We've added an explicit 'editing-citation' icon pack, that helps us standardize citation icons. Therefore we have moved existing related icons to its own pack. * icons: Rename 'settings' to 'pageSettings' (Volker E.) Clarify intended usage of icon by renaming it. Please update your icon pack references accordingly in case you're using one of those icons. New features, icons and highlights in this release: * An infusable PHP NumberInputWidget was implemented by volunteer mainframe98. * icons: 'editing-citation' pack was added (Volker E.) * ProcessDialog: Fix footer height when actions or dialog size changes (Bartosz Dziewoński) Additional details on 45 code-level and accessibility changes, 34 styling and interaction design amendments, and all improvements since v0.26.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]. Thanks to all contributors involved, especially volunteers mainframe98 and Daimona Eaytoy! Best, Volker [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/ -- Senior User Experience Engineer Wikimedia Foundation volker.e(a)wikimedia.org | @Volker_E

2 1

2018-05-09 Scrum of Scrums meeting note
by Grace Gellerman 09 May '18

09 May '18

https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-05-09 = 2018-05-09 = == Callouts == *UI Standardization: OOUI – v0.27.0 breaking change release https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v… As there are 5 breaking changes & 2 deprecations in this release, at least nominally, please carefully consider if they affect your code. *RelEng: Please review my patch! https://gerrit.wikimedia.org/r/#/c/415886/ <3 -mdh (RI) == Audiences == === Readers === ==== iOS native app ==== * Blocked by: * Blocking: * Updates: ==== Android native app ==== * Blocked by: * Blocking: * Updates: ** Nearly ready with Multilingual prototype for user-testing at the Hackathon. ==== Readers Web ==== * Blocked by: **Ruby to JS Cucumber refactor needs help from the RelEng team: https://phabricator.wikimedia.org/T190710 **Proton instrumentation needs help from the Services team: https://phabricator.wikimedia.org/T189307 ***We need help setting up the test environment (send production traffic to new server to find out how it performs); let's discuss in the Thursday sync! * Blocking: * Updates: **Merged refactoring jQuery collapsible elements to use CSS instead of JavaScript https://phabricator.wikimedia.org/T42812 **Merged miscellaneous watchstar bug fixes wrapping up https://phabricator.wikimedia.org/T191454 **Working with anti-harassment team for improvements to messaging for blocked users https://phabricator.wikimedia.org/T165535 **Miscellanous post-page previews en/dewiki launch clean up https://phabricator.wikimedia.org/T192622 **Some rather involved improvements to long infobox presentation and inlined article thumbnails https://phabricator.wikimedia.org/T189688 **Miscellaneous MobileFrontend and Popups refactors **Proton (Chromium rendering service) instrumentation in progress https://phabricator.wikimedia.org/T189307 **Reviewing applicants for full stack engineer backfill **Continuing on improving the page issues experience https://phabricator.wikimedia.org/T159262 *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra ==== Readers Infrastructure ==== * Blocked by: * Blocking: * Updates: ** Updated mobile-sections, summary, and action=mobileview to take overridden local short descriptions into account (also provide the source where the description came from: local or central wiki; the first two endpoints are already deployed, the action=mobileview is riding the train this week) ** Added announcement for production Android app to point to a survey about reading list sync, running for one week since Tuesday. ** Add to Reading List browser extensions awaiting legal review *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of client apps by coalescing and moving more logic to the server]] ***Reading Infra depends on Parsing, Services ===== Maps ===== * Blocked by: * Blocking: * Updates: ==== Multimedia ==== * Blocked by: * Blocking: * Updates: ** Working on frontend changes for MediaInfo (changing forms to OOUI) ** Added instrumentation to UploadWizard via EventLogging ** Continuing work on search indexing of properties and qualifiers ** Discussion in progress about what parts of MCR need to be completed for initial SDoC launch with multi-lingual file captions === Contributors === ==== Community Tech ==== * Blocked by: * Blocking: * Updates: ==== Anti-Harassment Tools ==== * Blocked by: * Blocking: * Updates: ==== Editing ==== * Blocked by: * Blocking: * Updates: ==== Parsing ==== * Blocked by: * Blocking: * Updates: ==== Collaboration ==== * Blocked by: * Blocking: * Updates: ** Internationalized maps are live ** <mapframe> live on almost all Wikipedias (waiting for a Parsoid restart before we announce) ==== Language ==== * Blocked by: https://phabricator.wikimedia.org/T151116 - Abuse filters set to warn users require two captchas - affecting CX. * Blocking: None * Updates: ** ContentTranslation version 2 work continue. === Audiences Design === * Blocked by: * Blocking: * Updates: ==== UI Standardization ==== * Blocked by: * Blocking: * Updates: ** OOUI – v0.27.0 breaking change release: https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v… *** 5 breaking changes & 2 deprecations in this release! Additionally 7 style changes, 4 code & 3 accessibility improvements. Among those **** Infusable PHP NumberInputWidget is now added and part of core (mainframe98) **** ProcessDialog: Fix footer height when actions or dialog size changes (Bartosz Dziewoński) **** icons: Add 'editing-citation' pack (Volker E.) **** SelectFileWidget: Use `<label>` for select ButtonElement (Volker E.) ** Continued work on Design Style Guide == Technology == === Analytics === * Blocked by: * Blocking: * Updates: **Kafka upgrade on main Kafka cluster (tier 1) **Upgrading druid to 0.11 and running into trouble, testing in labs. **Working on geoeditors (the improved geowiki data - #editors per country). **Work continues to update UA Parser. **Recruiting for SRE, Audiences and data analysts team. **Surfacing virtual pageviews in aggregated form in Hive and in Druid/pivot. **switching on EL sanitization in Hive, not yet deleting data, just creating another sanitized copy. === Cloud Services === * Blocked by: * Blocking: * Updates: === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** CiviCRM *** another version upgrade - https://phabricator.wikimedia.org/T194210 *** imports for new bitcoin processor - https://phabricator.wikimedia.org/T192953 *** fixes for audit file processing (refunds to recurring payments) - https://phabricator.wikimedia.org/T190098 *** recurring charge processing for main CC processor's new API - https://phabricator.wikimedia.org/T170973 ** CentralNotice *** Still working out mechanics of new banner impression / EventLogging backend pipeline - https://phabricator.wikimedia.org/T186048 *** CSP on banner previews breaking some workflows, investigating whether those should stay broken - https://phabricator.wikimedia.org/T193332 ** DonationInterface *** squashing last blocker bug for public-facing trial of main CC processor's new API - https://phabricator.wikimedia.org/T190871 === MediaWiki Platform === * Blocked by: * Blocking: * Updates: === Performance === * Blocked by: None * Blocking:None * Updates: ** Continuing to migrate our tools, making good progress there. ** Evaluating several different mobile testing services, hoping to find one that allows us to do regular testing but haven't yet done so. ** Beginning to do performance testing on Android phones (mobile site, not app) ** Had an issue with NavTiming extension that resulted in some data collection being dropped. Fixed at the end of last week. ** Beginning some ResourceLoader refactoring to reduce overhead. Related, looking in to deferring jQuery until somewhat later in the page load process. ** Blocked the train last week, had to roll back a change to DBTransactionError ** Refactoring varnish log processing for better reusability ** Planning an offsite for June === Release Engineering === * Blocked by: * Blocking: * Updates: === Research === * Blocked by: None * Blocking: None * Updates: ** Started implementing the CitationUsage schema instrumentation: https://phabricator.wikimedia.org/T191086 ** Started identifying areas of improvement for the recommendation API: https://phabricator.wikimedia.org/T190774 === Scoring Platform === * Blocked by: * Blocking: * Updates: === Search Platform === * Blocked by: * Blocking: * Updates: ** Trey published a blog post about names & search: https://blog.wikimedia.org/2018/05/08/searching-for-names-is-not-always-str… ** Wikidata indexing for more properties enabled, pending reindex: https://phabricator.wikimedia.org/T163642 ** More wikis get deepcategory search enabled soon (~next week): https://phabricator.wikimedia.org/T194139 ** Working on Polish analyzer: https://phabricator.wikimedia.org/T186046 ** Working on using Serbian analyzer for more languages: https://phabricator.wikimedia.org/T192395 ** Working on improving sharding of Elastic cluster: https://phabricator.wikimedia.org/T192972 ** Working on query parsing refactoring: https://phabricator.wikimedia.org/T185108 === Security === * Blocked by: * Blocking: * Updates: === Services === * Blocked by: none * Blocking: PDF service * Updates: ** Kafka 1.1 🎉 Cheers to Analytics ** A lot of RESTBase patches are getting deployed ** A big thank for everyone who reached to us regarding the jobs callout from last week === Site Reliability Engineering === * Blocked by: * Blocking: * Updates: == Wikidata == * Blocked by: ** nodejs selenium tests to be stable and voting on ci they still fail most of the time due to issues that are in mediawiki core or other extensions and generally seem super flaky ** Enhanced recent changes don't format external usernames well in contributors summary https://gerrit.wikimedia.org/r/#/c/428712/ (Any objections?) * Blocking: * Updates: ** Normalize change tag schema - https://phabricator.wikimedia.org/T185355 ** 2 weeks until Lexeme is live. == German Technical Wishlist == * Blocked by: ** UCA category collation got declined because of …? https://phabricator.wikimedia.org/T128806 * Blocking: * Updates: ** AdvancedSearch is enabled as a Beta feature on all wikis: https://phabricator.wikimedia.org/T193182 ** Finalizing deepcategory search integration in AdvancedSearch: https://phabricator.wikimedia.org/T194256 ** Fixed a OOUI bug in IE10+: https://phabricator.wikimedia.org/T191287 ** Raised test coverage of FileImporter to over 60%: https://doc.wikimedia.org/cover-extensions/FileImporter/ ** Working on a core fix needed for FileImporter: https://phabricator.wikimedia.org/T193621 ** Looking forward to the Hackathon == SoS Meeting Bookkeeping == * Updates:

2 1

Structured Data on Commons at the Wikimedia Hackathon in Barcelona
by Sandra Fauconnier 09 May '18

09 May '18

Hi all! Several members of the Structured Data on Commons team will be at the Wikimedia Hackathon in Barcelona next week. Join us there! We will do an introduction and Q&A session, a session focused on GLAM projects, and you are warmly welcomed to join us at the dedicated Structured Commons corner/table(s) we'll have on location. Come and have a chat! More info here: https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2018/Structured_Commons - please add your username to the list of participants if you're interested. All the best! Sandra - on behalf of the team :-)

1 0

[mailman question] Adding whole domain to ban_list
by Martin Urbanec 09 May '18

09 May '18

Hello, I'm trying to ban @aol.com for signing up to wikimediacz-l. This is a member-only list for Wikimedia Czech Republic members and as aol.com is pretty unfrequent in Czechia, I don't expect any problems (and if there will be some, members of the list are added by a list administrator). There is a big sign-up spam, so that's the reason why I decided to issue the block. If there is a way how to enforce manual adding by a list administrator, I'll be happy, but helping how to add whole aol.com to ban_list will be useful. I tried to add "^.*(a)aol.com$" (a regex) to the ban_list variable, but this apparently do not help, still some aol addresses are able to sign up. Thank you in advance for any help. Martin

3 2

Update on page issues on mobile web
by Chris Koerner 08 May '18

08 May '18

Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. [0] Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues. So far, we have drafted a proposal on the design and implementation of the project. [1] We were also able to run user testing on the proposed designs. [2] The tests so far have positive results. Here is a quick summary of what we learned: * The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode. * Page issues make sense to readers and they understand how they work * Readers care about page issues and consider them important * Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. [1] Please leave feedback on the talk page. [3] [0] https://www.mediawiki.org/wiki/Reading/Web/Team [1] https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues [2] https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues/Rese… [3] https://www.mediawiki.org/wiki/Talk:Reading/Web/Projects/Mobile_Page_Issues Yours, Chris Koerner Community Liaison Wikimedia Foundation

1 0

AdvancedSearch beta feature available on all wikis
by Birgit Müller 08 May '18

08 May '18

(cross-post) Dear all, we are really happy to announce that the new AdvancedSearch interface got deployed as a beta feature to all wikis just now. [1] The search has great options to perform advanced queries e.g. by using keywords like "hastemplate" or "intitle", but often even experienced editors don't know about it - this is what we found out in a workshop series on advanced searches in 2016 and this is why we have built the AdvancedSearch extension. [2] AdvancedSearch enhances Special:Search through an advanced parameters form. It serves as an interface for some of the search options that the Wikimedia Foundation's search team has been implemented over the past years. The way the interface works, users don't have to know the syntax behind each search field, but they can learn about it if they want to. *From small beta to full beta* The feature already has been a beta feature on deWP, arWP, huWP, faWP and mediawiki.org for more than 5 months. During this "small beta phase" (= base version with a set of features, deployed to a few wikis, both ltr and rtl wikis) support for more search options got added (searches in categories and sub categories, searches for content in a specific language in wikis that have the translate extension enabled, searches for subpages of a page), the way how to select and configure namespaces got improved and several bugs were fixed. Everyone is invited to test the now full beta feature! If you want to give us feedback or if you find a bug, please use the main feedback page (or file a ticket in phabricator): https://www.mediawiki.org/wiki/Help_talk:Extension:AdvancedSearch If you want to learn more about the project, the functional scope of the AdvancedSearch extension and the usage, please see * the help page: https://www.mediawiki.org/wiki/Help:AdvancedSearch *the main project page: https://meta.wikimedia.org/ wiki/WMDE_Technical_Wishes/AdvancedSearch * the list of supported search options: https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/AdvancedSearch/Functi… *Thanks, thanks, thanks :-)*A huge thanks to everyone who has tested the feature and gave feedback over the last 5 months and to everyone who has translated software messages and announcements - this is much appreciated! And a huge thanks to the WMF's search team who has done all the backend work and has built great options for advanced search queries that now can be accessed through the AdvancedSearch interface. It was and is great to work with you :-) Looking forward to more testing and feedback to further improve the feature, Thanks a lot, Birgit (for WMDE's Technical Wishes team) [1] https://phabricator.wikimedia.org/T193182 <https://phabricator.wikimedia.org/T180147>(Deployment ticket) [2] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/AdvancedSearch /Workshop <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/AdvancedSearch> -- Birgit Müller Community Communications Manager Software Development and Engineering 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.

1 0

Wednesday: Technical Advice IRC Meeting
by Michael Schönitzer 08 May '18

08 May '18

Sorry for cross-posting! Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 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.

1 0

Apa yang membuat anda gembira minggu ini? / What's making you happy this week? (Week of 6 May 2018)
by Pine W 08 May '18

08 May '18

I was happy to read about the new features in the latest release of the Wikimedia Commons app for Android. My understanding is the app is developed and maintained by community members with funding from WMF and GSoC in addition to volunteer time. Also, I was happy to see GSoC participants introducing themselves and their projects on Wikitech-l. I am grateful to the WMF staff who are listening and responding civilly to the questions and comments on MediaWiki regarding the page previews feature. The project plan appears to have been designed thoughtfully. Finally, I liked reading portions of English Wikipedia's article about CubeSats. What's making you happy this week? You are welcome to comment in any language. Pine ( https://meta.wikimedia.org/wiki/User:Pine )

2 1

Gerrit newcomer bot
by Srishti Sethi 08 May '18

08 May '18

*Hello all,A quick update related to Gerrit -- you will notice a small change on patches uploaded by new developers. There is a bot now which is adding a reviewer (as "Welcome, new contributor!") and a welcome message in a comment to a patch submitted by a new developer. You would also be able to query patches of new developers by typing in the search term: `ownerin: newcomers` (only applicable to new patches).Learn more about the bot, and file an issue here: https://github.com/srish/gerrit-newcomer-bot <https://github.com/srish/gerrit-newcomer-bot>OR comment on the related Phab task: https://phabricator.wikimedia.org/T192046 <https://phabricator.wikimedia.org/T192046>Thanks,Srishti * -- Srishti Sethi Developer Advocate Technical Collaboration team Wikimedia Foundation https://www.mediawiki.org/wiki/User:SSethi_(WMF)

5 4

2018-05-02 Scrum of Scrums meeting notes
by Grace Gellerman 08 May '18

08 May '18

https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-05-02 ==2018-05-02 == == Callouts == * Fundraising campaigns https://meta.wikimedia.org/wiki/CentralNotice/Calendar - next up: Netherlands 2018-04-10through 2018-05-08 * Services: If someone maintains/knows JobQueue Job code that posts jobs cross-wiki, please tell us. * Language -> Platform: Need help in https://phabricator.wikimedia.org/T193008(MediaWiki\MediaWikiServices::rese… doesn't reset database connection state) * If you have a WMF service that uses WDQS, please document at https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Usage and consider whether it should be using internal cluster or public endpoint. * Research: If you speak English, French, or Spanish, you're welcome to label some unsourced statements at http://labels.wmflabs.org. Look for the "Labeling Unsourced Statements" (or its equivalent in other languages) campaign. * Research: If you speak two languages from the list of Arabic, English, Spanish, Japanese, French, and Russian, you're also welcome to help us with mapping section titles. https://docs.google.com/spreadsheets/d/1KjUiMERifNvoqxaXYo3aymjELHrIkyX9wgC… * Research: We would love to hear about a robust way of sending out user talk page messages across wikis, not just enwiki. == Audiences == === Readers === ==== iOS native app ==== * Blocked by: * Blocking: * Updates: **Point release should be code complete this week; mostly small bug fixes + Wikidata magic word override (https://phabricator.wikimedia.org/T191347) ==== Android native app ==== * Blocked by: * Blocking: * Updates: **Working on multilingual extensions. Planning to complete before Hackathon, and perform user testing there. ==== Readers Web ==== * Blocked by: * Blocking: * Updates: **Some rather involved improvements to infobox alignment https://phabricator.wikimedia.org/T189688 **Refactoring jQuery collapsible elements to use CSS instead of JavaScript https://phabricator.wikimedia.org/T42812 **Improvements, bug fixes, and analyses to page previews; better RTL support https://phabricator.wikimedia.org/T192928 https://phabricator.wikimedia.org/T190831 https://phabricator.wikimedia.org/T193058 https://phabricator.wikimedia.org/T192773 https://phabricator.wikimedia.org/T188734 https://phabricator.wikimedia.org/T193053 **Miscellaneous watchstar bug fixes wrapping up https://phabricator.wikimedia.org/T191454 **Reviewing applicants for full stack engineer backfill **Page issues instrumentation planning https://phabricator.wikimedia.org/T191532 **Little slow this week due to holidays and vacations **Ongoing minor improvements to MobileFrontend and MinervaNeue *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra ==== Readers Infrastructure ==== * Blocked by: * Blocking: * Updates: ** Updated summary output to use the correct description if it was overridden. Same for mobile-sections plus also added the description_source so the apps can see where the description came from. (deployed as of Monday, going to roll out to pages as they are edited) ** ReadingLists response times went up 10x, might be related to ChronologyProtector change (there is a fix, thanks Performance!) https://phabricator.wikimedia.org/T193417 *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra **[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of client apps by coalescing and moving more logic to the server]] ***Reading Infra depends on Parsing, Services ===== Maps ===== * Blocked by: * Blocking: * Updates: ** ==== Multimedia ==== * Updates ** Continuing work on prototype for file-page integration for MediaInfo ** Search work progressing well - moving on from properties to qualifiers ** Still considering instrumentation possibilities *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 3.1]] Prepare for launch of the first Structured Data on Commons feature (multilingual file captions) ***SDC depends on Multimedia,SRE, WMDE, Search Platform, MediaWiki Platform, Research ** [[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 2.1]] Integrate structured file captions into search *** SDC depends on Search Platform, Multimedia **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Structured_Data#Segment_4:_Programs|Segment 4, Outcome 2]]: Develop a better understanding of existing needs for Structured Commons- T171252 ***Research depends on Multimedia === Contributors === ==== Community Tech ==== * Blocked by: * Blocking: * Updates: ** Starting a new project, AFC improvement ==== Anti-Harassment Tools ==== * Blocked by: * Blocking: * Updates: ** ==== Editing ==== * Blocked by: * Blocking: ** Updates: ** ==== Parsing ==== * Blocked by: Operations on https://phabricator.wikimedia.org/T193414 -- Production Debian stretch servers are running a different version of Tidy compared to Debian Jessie servers * Blocking: * Updates: ** *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]] Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team *** Parsing depends on MediaWiki Platform, Services **** Work Ongoing. (1) Tidy will be gone by end of quarter, and in touch with Platform team about it (2) Language variants work is apace. Services & Parsing are yet to meet to work about API spec for what Services wants Parsing to implement. **[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of client apps by coalescing and moving more logic to the server]] Increase code sharing of client apps by coalescing and moving more logic to the server. *** Reading Infra depends on Parsing, Services **** Not aware of anything that Parsing needs to do (unless it is language variants, which is already being addressed as part of our own goal above). [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better data|Outcome 2: Objective 1]]: Revision storage scaling *** Services depends on SRE, Parsing **** Services, Parsing, Editing need to meet and resolve if data-mw blob separation is happening this quarter or not. ==== Collaboration ==== * Blocked by: * Blocking: * Updates: ** ==== Language ==== * Blocked by: See callouts * Blocking: None * Updates: ** ContentTranslation Version 2 work continue. *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.1]] Improve and consolidate our unified editing platform so that it's great on all devices ***Language depends on Editing === Audiences Design === * Blocked by: * Blocking: * Updates: ** ==== UI Standardization ==== * Blocked by: * Blocking: * Updates: ** == Technology == === Analytics === * Blocked by: * Blocking: * Updates: ** Druid has been upgraded to 0.10 (on the road to 0.11, allowing to move to java8 and therefore stretch instead of jessie) ** http://pivot.wikimedia.org is having problems for some datasources (banner-impressions) - We ask people to start using Superset ( superset.wikimedia.org - wikitech account + ping to analytics needed) ** Geowiki (editors per country) is now named GeoEditors. Data has been vetted against old data (see https://wikitech.wikimedia.org */wiki/Analytics/Systems/GeoEditors) ** Mirror Maker still has issues. We are upgrading jumbo to Kafka 1.1 before rolling it to the main cluster, with ops collaboration ** EventBus logs are pushed to logstash ** On the way to upgrade ua-parser, the library we use to classify user agents ** Dashiki can now pivot data (example of configuration change: https://meta.wikimedia.org/w/index.php?title=Config%3ADashiki%3AInterlangua…, example of dashboard using it: https://language-reportcard.wmflabs.org/interlanguage/#desktop) === Cloud Services === * Blocked by: * Blocking: * Updates: ** === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** Infrastructure for transition to EventLogging for data on FR cluster ** Fixing up some errors in the donations queue ** Setting up BitPay ** Ongoing fixes and improvements in existing systems: CiviCRM, Ingenico, Grafana dashboard === MediaWiki Platform === * Blocked by: * Blocking: * Updates: ** MCR *** Task wrangling *** Working to resolve architectural disagreements *** Migration script to populate the new MCR tables is done, waiting for MCR people to review. *** ar_text/ar_flags removal is blocked on Cloud Services: https://phabricator.wikimedia.org/T189141 *** Wrote a maintenance script to deduplicate ar_rev_id, needs review: https://gerrit.wikimedia.org/r/q/topic:%2522bug%252FT193180-cleanup-archive… *** API updates for query modules are in Gerrit: https://gerrit.wikimedia.org/r/#/c/413223/ *** Started working on the API "templated parameters" patch again. Almost ready to put it in Gerrit. Described in https://phabricator.wikimedia.org/T174032#3990488. ** MediaWiki 1.31 blocker work ** Usual code review and bug work *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]] Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team ***Parsing depends on MediaWiki Platform, Services **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research ** [[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 1.1]] Assist with deploying MultiContent Revisions on Commons [[phab:T174022|T174022]] Implement multi-content revisions, [[phab:T174023|T174023]] Implement MCR storage layer, [[phab:T174045|T174045]] DB schema migration for MCR, [[phab:T174044|T174044]] Deploy MCR storage layer, [[phab:T174043|T174043]]Deploy Multi-Content Revisions ***SDC depends on MediaWiki Platform, WMDE === Performance === * Blocked by: ** * Blocking: ** * Updates: ** === Release Engineering === * Blocked by: none * Blocking: none? * Updates: ** Announcing Quibble! https://phabricator.wikimedia.org/phame/post/view/99/introducing_quibble/ ** MediaWiki core and extensions 1.32.0-wmf.2 going out this week [ https://phabricator.wikimedia.org/T191048 blocker task] if you spot blockers ** New Scap Release coming Soon™ *** git-lfs updates for ORES *** better canary stuff for MediaWiki deploys *Quarterly goal dependency update: ** no updates **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra === Research === * Blocked by: None * Blocking: None * Updates: ** Sending out invitations to multilingual Wikipedia users and asking their help in mapping article section titles into different languages (ar, en, es, fr, ja, ru). Would love to hear if anyone knows about a robust way of sending talk page messages across wikis, not just enwiki. You're welcome to contribute too: https://docs.google.com/spreadsheets/d/1KjUiMERifNvoqxaXYo3aymjELHrIkyX9wgC… ** Running a Wikilabels campaign for unsourced statements (en, fr, it). So far we have 25 independent annotators and more than 300 labels. Your contributions are also welcome: http://labels.wmflabs.org *Quarterly goal dependency update: Jonathan is driving these initiatives. **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Structured_Data#Segment_4:_Programs|Segment 4, Outcome 2]]: Develop a better understanding of existing needs for Structured Commons- [[phab:T171252|T171252]] ***Research depends on Multimedia === Scoring Platform === * Blocked by: None * Blocking: None * Updates: **git-lfs is almost finished **wp10 data is available on beta cluster and will go to prod soon === Search Platform === * Blocked by: * Blocking: * Updates: ** WDQS internal cluster is up and serving traffic. ** Fixed error in negating keywords: https://phabricator.wikimedia.org/T193208 ** Working on Polish analyzer: https://phabricator.wikimedia.org/T186046 ** Evaluating feature generation by `query_explorer` functionality of LTR plugin: https://phabricator.wikimedia.org/T187148 ** Working on improving sharding of Elastic cluster: https://phabricator.wikimedia.org/T192972 ** Working on query parsing refactoring: https://phabricator.wikimedia.org/T185108 ** Working on indexing more statements in Wikidata: https://phabricator.wikimedia.org/T99899 ** WDQS GUI auto-build working, thanks again RelEng! *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|*Objective 2.1]] Integrate structured file captions into search *** SDC depends on Search Platform, Multimedia === Security === * Blocked by: * Blocking: * Updates: ** *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]]: Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team ***Parsing depends on MediaWiki Platform, Services === Services === * Blocked by: none * Blocking: none * Updates: ** RESTBase storage clenups ongoing ** Job Queue migration continues *** The job type config must be global for all the jobs that are posted cross-wiki, so our normal switchover process doesnt work for them. We've identifie most of cases, but we need help if someone knows a job we might have missed. *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Readers|Increase code sharing of client apps by coalescing and moving more logic to the server.]] ***Reading Infra/Parsing, Services **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Product#Program_3:_Increase_device_support_for_editing|Goal 3.6]] Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team ***Parsing depends on MediaWiki Platform, Services [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better data|Outcome 2: Objective 1]]: Revision storage scaling *** Services depends on SRE, Parsing === Site Reliability Engineering === * Blocked by: * Blocking: * Updates: ** *Quarterly goal dependency update: **[[metawiki:Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Product#Program_2:_Better_Encyclopedia|Outcome 1, Objective 4]]: Continue improving the ways that users can download articles of interest for later consumption *** Reading Web depends on SRE, RelEng, Reading Infra **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research [[Wikimedia Technology/Goals/2017-18 Q4#Program 7. Smart tools for better data|Outcome 2: Objective 1]]: Revision storage scaling *** Services depends on SRE, Parsing == Wikidata == * Blocked by: ** MediaWiki core's selenium tests flaky when run as part of mwext-mw-selenium-node-composer-jessie job - https://phabricator.wikimedia.org/T191537 **CI infrastructure Issues *** What level of service is expected, what to do when the service level "drops" too much? *** What amount of contribution can/should be expected from our team, how much can/should we get involved? * Blocking: * Updates: **Release of Lexeme is still on schedule - May 23rd. ** *Quarterly goal dependency update: **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Prepare for launch of the first Structured Data on Commons feature]] (multilingual file captions) ***SDC depends on Multimedia/,SRE, WMDE, Search Platform, MediaWiki Platform, Research **[[Wikimedia Audiences/2017-18 Q4 Goals#Programs|Objective 1.1]] Assist with deploying MultiContent Revisions on Commons [[phab:T174022|T174022]] Implement multi-content revisions, [[phab:T174023|T174023]] Implement MCR storage layer, [[phab:T174045|T174045]] DB schema migration for MCR, [[phab:T174044|T174044]] Deploy MCR storage layer, [[phab:T174043|T174043]]Deploy Multi-Content Revisions ***SDC depends on MediaWiki Platform, WMDE == German Technical Wishlist == * Blocked by: * Blocking: * Updates: ** == SoS Meeting Bookkeeping == * Updates: **

6 5

Introducing Quibble, a test runner for MediaWiki
by Antoine Musso 08 May '18

08 May '18

Hello, Running all tests for MediaWiki and matching what CI/Jenkins is running has been a constant challenge for everyone, myself included. Today I am introducing Quibble, a python script that clone MediaWiki, set it up and run test commands. It is a follow up to the Vienna Hackathon in 2017. We had a lot of discussion to make the CI jobs reproducible on a local machine and to unify the logic at a single place. Today, I have added a few jobs to mediawiki/core. An immediate advantage is that they run in Docker containers and will start running as soon as an execution slot is available. That will be faster than the old jobs (suffixed with -jessie) that had to wait for a virtual machine to be made available. A second advantage, is one can exactly reproduce the build on a local computer and even hack code for a fix up. The setup guide is available from the source repository (integration/quibble.git): https://gerrit.wikimedia.org/r/plugins/gitiles/integration/quibble/ The minimal example would be: git clone https://gerrit.wikimedia.org/r/p/integration/quibble cd quibble python3 -m pip install -e . quibble A few more details are available in this post on the QA list: https://lists.wikimedia.org/pipermail/qa/2018-April/002699.html Please give it a try and send issues, support requests to Phabricator: https://phabricator.wikimedia.org/tag/quibble/ Next week I will polish up support for MediaWiki extensions and skins and eventually Quibble will take over most of the CI jobs running for MediaWiki related projects. -- Antoine "hashar" Musso

5 10

Discovery Weekly Update for the week starting 2018-04-30
by Chris Koerner 07 May '18

07 May '18

Hello friends, A short and simple update this week from the Search Platform team. As always, feedback and questions welcome. == Highlights== * Maps update: mapframe was installed on English Wikipedia [0] === Search === * Trey has created a Slovak Elasticsearch Plugin/Analysis Chain using a Slovak Stemming Algorithm and is moving ahead with adding an Elasticsearch plugin for it. [1] [0] https://www.mediawiki.org/wiki/Topic:Uca6loi6wxwy4rvg [1] https://phabricator.wikimedia.org/T190815] --- Subscribe to receive on-wiki (or opt-in email) notifications of the Discovery weekly update. https://www.mediawiki.org/wiki/Newsletter:Discovery_Weekly The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as "Easy" or "Volunteer needed" in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R Yours, Chris Koerner Community Liaison Wikimedia Foundation

1 0

IRC Meeting for RFC "Come up with a strategy for handling interface changes"
by Kate Chapman 07 May '18

07 May '18

Hi All, We ended up scheduling this a little late so it didn't go out on the TechCom Radar. There is a IRC meeting on 2018-05-09 at 2pm PST(22:00 UTC, 23:00 CET) on #wikimedia-office channel for RFC: Come up with a strategy for handling interface changes <https://phabricator.wikimedia.org/T193613> Thanks, -Kate -- Kate Chapman TechCom Facilitator (Contractor)

1 0

Introduction : Ujjwal Agrawal ( GSoC 2018 )
by Ujjwal Agrawal 07 May '18

07 May '18

Hello Everyone! I am Ujjwal Agrawal, third-year B.Tech. Undergraduate at Indian Institue of Technology (ISM), Dhanbad, and I've been selected for GSoC 2018. I have a keen interest in Android App development and I will be implementing a feature to browse/search the Wikimedia Commons Repository from Commons App <https://phabricator.wikimedia.org/T188597 <https://phabricator.wikimedia.org/T189788#4153895>>, as a part of my intern program. I’d like to thank my mentors Nicolas Raoul and Neslihan for giving me this wonderful opportunity! Regards Ujjwal Agrawal

1 0

Adding a category to json page
by יגאל חיטרון 07 May '18

07 May '18

Hello. Is there a way to add a category to json contentmodel page? Thank you. Igal (User:IKhitron)

2 2

GSoC 2018 Introduction: Prssanna Desai
by prssanna desai 06 May '18

06 May '18

Greetings, I'm Prssanna Desai, an undergraduate student from NMIMS University, Mumbai, India and I've been selected for GSoC '18. *My Project:* *Improve Data Explorer for query.wikidata.org <http://query.wikidata.org>* The project consists of making usability improvements to the Explorer Dialog and the Graph Explorer of WDQS. You can read my full proposal here: https://phabricator.wikimedia.org/T189669 I’d like to thank my mentors Jonas Kress, Stas Malyshev and Lucas Werkmeister for giving me this wonderful opportunity! Regards, Prssanna Desai

3 2

TechCom Radar 2018-05-02
by Kate Chapman 04 May '18

04 May '18

Hi All, Here are the minutes from this week's TechCom meeting: * Public IRC Meeting on Colorable SVG <https://phabricator.wikimedia.org/T106240> occured minutes available here: <https://tools.wmflabs.org/meetbot/wikimedia-office/2018/wikimedia-office.20…> * RFC Approved Tracking dependencies for multiple Content objects per page (MCR) <https://phabricator.wikimedia.org/T190063> * Discussed reviewing development policies and then using RFC process to update: <https://phabricator.wikimedia.org/T190379> You can also find our meeting minutes at <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes> See also the TechCom RFC board <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. -- Kate Chapman TechCom Facilitator (Contractor)

1 0

Thank you for participating in the global Wikimedia survey!
by Edward Galvez 03 May '18

03 May '18

Hello everyone, I would like to share my deepest gratitude for everyone who responded to the Wikimedia Communities and Contributors Survey. The survey has already closed for this year. The quality of the results has improved because more people responded. We heard from over 200 people who work in volunteer developer spaces like Phabricator, IRC, Mediawiki, mailing lists, and many others, which is a solid increase from last year. We are working on analyzing the data already and hope to have something published on meta in a couple months. Be sure to watch Community Engagement Insights <https://meta.wikimedia.org/wiki/Community_Engagement_Insights> for when we publish the reports. We will also message those individuals who signed up on the thank you page or sent us an email to receive updates about the report. Feel free to reach out to me directly at egalvez[at] wikimedia.org or at my talk page on meta <https://meta.wikimedia.org/wiki/User:EGalvez_(WMF)>. Thank you again to everyone for sharing your opinions with us! -- Edward Galvez Evaluation Strategist, Surveys Learning & Evaluation Community Engagement Wikimedia Foundation

1 0

Scribunto localization/code review request
by Martin Urbanec 03 May '18

03 May '18

Hello all, can somebody with +2 on Scribunto please review&merge https://gerrit.wikimedia.org/r/403603 for https://phabricator.wikimedia.org/T184512? Thanks! Martin

1 0

Τι σας κάνει ευτυχισμένη αυτήν την εβδομάδα? / What's making you happy this week? (Week of 22 April 2018)
by Pine W 03 May '18

03 May '18

*"To be, or not to be"* A phrase from Shakespeare's *Hamlet <https://en.wikipedia.org/wiki/Hamlet> *is "To be, or not to be, that is the question"*.* Chris Koerner from WMF Discovery published some interesting information about the verb "to be", and how on-wiki search deals with it, in this issue <https://lists.wikimedia.org/pipermail/discovery/2018-April/001652.html> of the *Discovery Weekly Update*: "The English verb "to be" is kind of weird—the infinitive "be" and participles "being, been" start with "b-", while the preterite forms "was, were" start with "w-", and the present forms "am, is, are" start with vowels. The conjugations originally come from three or four different verbs! Why "three or four"? Wiktionary disagrees with itself a bit, listing four on the etymology of "is" [5] and three on the etymology of "be". [6] The conflation goes back at least to Proto-Germanic, [7] so German is similarly weird. [8] Dutch has a greatly simplified paradigm, but still shows some trace of the multiple sources. [9] Other languages, including ASL, Arabic, Bengali, Hawaiian, Hebrew, Indonesian, Japanese, Russian, Turkish, and Ukrainian at least partly avoid this mess by having a zero copula. [10] For search on-wiki, we deal with this problem in part with stemming [11] and stop words. [12] "[5] https://en.wiktionary.org/wiki/is#Etymology_1 [6] https://en.wiktionary.org/wiki/be#Etymology [7] https://en.wikipedia.org/wiki/Proto-Germanic_language [8] https://en.wiktionary.org/wiki/sein#Conjugation [9] https://en.wiktionary.org/wiki/zijn#Inflection [10] https://en.wikipedia.org/wiki/Zero_copula [11] https://en.wikipedia.org/wiki/Stemming [12] https://en.wikipedia.org/wiki/Stop_words" *Legal case ends well for Greek Wikipedia administrator*From the Wikimedia Blog: https://blog.wikimedia.org/2018/04/18/greece-legal-case-ended/ *Photos from the 2018 Wikimedia Conference in Germany* Some photos of the 2018 Wikimedia Conference are available on Commons <https://commons.wikimedia.org/wiki/Category:Wikimedia_Conference_2018>. Here are a few: * https://commons.wikimedia.org/wiki/File:Wikimedia_ Conference_2018,_Group_photo.jpg * https://commons.wikimedia.org/wiki/File:Wikimedia_ Conference_2018_by_ZUFAr_01.jpg * https://commons.wikimedia.org/wiki/File:WMCON18_Sweets_Table_1.jpg * https://commons.wikimedia.org/wiki/File:WMCON18_by_Rehman_-_Posters_(2).jpg * https://commons.wikimedia.org/wiki/File:Wikimedia_Conference_2018_%E2%80%93… What's making you happy this week? You are welcome to comment in any language. Pine ( https://meta.wikimedia.org/wiki/User:Pine )

3 4

[MediaWiki-announce] MediaWiki 1.31.0-rc.0 now available
by Chad Horohoe 02 May '18

02 May '18

Hi, I'd like to announce the immediate availability of MediaWiki 1.31.0-rc.0, the first release candidate for 1.31.x. Links at the end of the e-mail. The tag has been signed and pushed to Git. This is not a final release and should not be used for production websites. There's several major outstanding bugs on the workboard. As always please do try out the release candidate in a test environment. It's how we find bugs that didn't surface in initial development :) Full release notes: https://phabricator.wikimedia.org/diffusion/MW/browse/REL1_31/RELEASE-NOTES… https://www.mediawiki.org/wiki/Release_notes/1.31 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.0-rc.0.tar.gz Core only, no extensions: https://releases.wikimedia.org/mediawiki/1.31/mediawiki-core-1.31.0-rc.0.ta… GPG signatures: https://releases.wikimedia.org/mediawiki/1.31/mediawiki-core-1.31.0-rc.0.ta… https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.0-rc.0.tar.gz.… Public keys: https://www.mediawiki.org/keys/keys.html -- Chad Horohoe _______________________________________________ MediaWiki announcements mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce

1 0

Scoring platform status update
by Adam Wight 02 May '18

02 May '18

We've summarized our technical work over the last three months, please see the blog post for details: https://phabricator.wikimedia.org/phame/post/view/104/status_update_may_2_2… Our novel, collaborative auditing system "judgment and dialogue engine" (JADE) is deployed to the beta cluster and is now available for tool developers to explore and integrate with. Read more here, https://mediawiki.org/wiki/JADE A dynamically updated table of ORES support is now available for anyone tracking our progress: https://tools.wmflabs.org/ores-support-checklist/ Regards, Adam

1 0

Code review for T15673
by Eran Rosenthal 02 May '18

02 May '18

Hi, A long standing issue with references that it doesn't natively support direction which is widely requested feature in RTL wikis. Can someone with +2 permissions please review the gerrit item in https://gerrit.wikimedia.org/r/#/c/7738/ ? Thanks, Eran

1 1

Re: [Wikitech-l] Commons app - version 2.7 release
by Josephine Lim 02 May '18

02 May '18

Hi Daniel, Happy to hear that you like the new features! :) Re: 2FA logins, that is an interesting question! However, it is not one that is unique to our app, for if you log in to your 2FA-enabled Wikimedia account on your mobile phone's browser, both factors can also be on the same mobile device. ;) Perhaps someone more well-versed in security/authentication than I am could be better placed to answer that question. Point noted re: the CCs, thanks! Best regards, Josephine On 2 May 2018 at 06:10, <wikitech-l-request(a)lists.wikimedia.org> wrote: > > > Message: 3 > Date: Tue, 1 May 2018 13:10:15 -0700 > From: Daniel Zahn <dzahn(a)wikimedia.org> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Commons app - version 2.7 release > Message-ID: > <CAERT87qNE20Yh7NNX5u_nCeiuy7Hqy6GHfd=xm1Cwym2Jtjqbw > @mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > > - New "Nearby places that need pictures" UI with direct uploads (and > associated category suggestions) - > > Woohoo. That's exactly what i was always missing and was so great about the > old WikiLovesMonuments app. > > Thank you very much! > > > Enabled two-factor authentication login > > Also very nice, just wondering what the second factor is on mobile, since > usually that's a mobile app as well. Does that still make it 2 factors? > > P.S. Crossposting to multiple mailing lists at once with CC: can be tricky, > maybe better send a separate mail to each. > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > ------------------------------ > > End of Wikitech-l Digest, Vol 178, Issue 2 > ****************************************** >

2 2

Code Stewardship Reviews - Q3 Update and Q4 Request for Feedback...
by Jean-Rene Branaa 02 May '18

02 May '18

Hello All, We're kicking off another round of Code Stewardship reviews for the quarter. Please take a look and share your thoughts through the Feedback Solicitation talk pages[1]. Below you'll also find a brief update for the Q3 Code Stewardship Review activities. Q4 Code Stewardship Reviews The dicussion window for this quarter's stewardship review candidates is opening today (May 1st) and will remain open until the 21st of May. As a brief reminder, the Code Stewardship Review process[0] has been put in place to help us discuss and plan a course of action for code, extensions, and services that are deployed in Wikimedia Foundation's production environment and are currently un/under funded. We are soliciting your feedback for the following items during this review cycle: * Geodata Extension[2] * LiquidThreads Extension[3] * Zotero Translation Server[4] * TranslationNotifications Extension[5] * FlaggedRecs Extension[6] Once the feedback window is closed, we will review the feedback and if needed, prioritize those items to be reviewed further during this quarter's review cycle. Q3 Code Stewardship Reviews We wanted to provide a quick update on the Code Stewardship Reviews from last quarter. Below is a list of those items we reviewed last quarter and a brief status for each of them. * TimedMediaHandler[7]: Code Steward identified - Readers Engineering. Preliminary plan in place. * IRC RecentChanges Feed[8]: Code Steward identified - Analytics. * RelatedSites[9]: Code Steward identified - CommTech. Plan is to sunset extention. Details to follow. * AbuseFilter[10]: Code Steward identified - Platform Team. Team will be as responsive as possible with current resourcing levels. Code Stewardship for this extension will be included in future resource plans. Although not included in the complete review process, UrlShortener [11] did end up finding a steward once being submitted as a review candidate. This past quarter was our first attempt at using this review process. We were successfully able to address four areas of concern. Assigning Code Stewards as well as laying out some initial plans for moving forward. Although good progress was made this quarter, there are some challenges ahead. Simply assigning a Code Steward doesn't necessarily translate into the gaps getting fully addressed. To that end, we'll be working with the Code Stewards to help identify ongoing gaps. Over time we will look to fill those gaps through the Foundation's annual planning and community engagement. The process wasn't without it's challenges, one of which was the concern that all items being reviewed were being considered for sunsetting. After clarifying some of this in our process definition[0], it seems most of these concerns have been addressed. As always, if there's any additional feedback on the process, please don't hesitate to contact Greg Grossmeier or I. Cheers, Jean-Rene Branaa Release Engineering Wikimedia Foundation [0] https://www.mediawiki.org/wiki/Code_stewardship_reviews [1] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitati… [2] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitati… [3] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitati… [4] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitati… [5] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitati… [6] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitati… [7] https://phabricator.wikimedia.org/T185551 [8] https://phabricator.wikimedia.org/T185319 [9] https://phabricator.wikimedia.org/T185206 [10] https://phabricator.wikimedia.org/T185154 [11] https://phabricator.wikimedia.org/T187052

1 0

Proposal: Add security researchers to CREDITS file & [[Special:Version/credits]]
by Brian Wolff 01 May '18

01 May '18

Hi everyone, Currently we only credit people who report security vulnerabilities at https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Thanks (which basically nobody reads or knows exists) and sometimes in the commit message and release announcements. Given such people are instrumental in keeping MediaWiki secure, I think we should also credit them in the CREDITS file. I propose adding another section to the file - "Vulnerability Reporters", listing the names of everyone who has reported a security vulnerability in either MediaWiki or a bundled extension. Thoughts? -- Brian

4 3

Commons app - version 2.7 release
by Josephine Lim 01 May '18

01 May '18

Hi all, We've just released version 2.7 of the Commons Android app ! \o/ The new version is available for download on the Google Play Store[1] as well as F-Droid[2]. This update includes several new features: - New "Nearby places that need pictures" UI with direct uploads (and associated category suggestions) - Two-factor authentication login - Notifications activity to display Commons user talk messages - Real-time location tracking in Nearby - Improvements to UI of navigation drawer, tutorial, media details view, login and settings - Option to nominate picture for deletion in media details view We are also thrilled to be mentoring two new contributors for this year's GSoC - Tanvi Dadu and Ujjwal Agrawal. :) Thank you all for your support and encouragement thus far! More details and screenshots can be found in my blog post[3]. Feedback, bug reports, and suggestions are always welcome on our GitHub page[4]. Best regards, Josephine (project maintainer) [1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons [2]: https://f-droid.org/repository/browse/?fdid=fr.free.nrw.commons [3]: https://cookiesandcodeblog.wordpress.com/2018/04/21/commons-app-version-2-7… [4]: https://github.com/commons-app/apps-android-commons/issues

4 5

Re: [Wikitech-l] Commons app - version 2.7 release
by Josephine Lim 01 May '18

01 May '18

Hi zppix e, We have been wanting to release an iOS app, but it depends entirely on whether we are able to get an iOS developer on board, either as a volunteer or paid (if we are able to obtain additional funding). The current team is unfortunately all Android developers. Do you know anyone who might be interested? :) Best regards, Josephine On Tue, 1 May 2018, 21:19 , <wikitech-l-request(a)lists.wikimedia.org> wrote: > Send Wikitech-l mailing list submissions to > wikitech-l(a)lists.wikimedia.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > or, via email, send a message with subject or body 'help' to > wikitech-l-request(a)lists.wikimedia.org > > You can reach the person managing the list at > wikitech-l-owner(a)lists.wikimedia.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Wikitech-l digest..." > > > Today's Topics: > > 1. Discovery Weekly Update for the week starting 2018-04-16 > (Chris Koerner) > 2. Readers Monthly update for April 2018 (Chris Koerner) > 3. Phabricator monthly statistics - 2018-04 > (communitymetrics(a)wikimedia.org) > 4. Mapframe maps now work on English Wikipedia (Joe Matazzoni) > 5. Commons app - version 2.7 release (Josephine Lim) 6. Re: Commons app - version 2.7 release (Josephine Lim) > 7. Re: Commons app - version 2.7 release (zppix e) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 30 Apr 2018 15:09:22 -0500 > From: Chris Koerner <ckoerner(a)wikimedia.org> > To: A public mailing list about Wikimedia Search and Discovery > projects <discovery(a)lists.wikimedia.org>, > wikitech-l(a)lists.wikimedia.org > Subject: [Wikitech-l] Discovery Weekly Update for the week starting > 2018-04-16 > Message-ID: > < > CAKW0rmHSj20YQ8XCVu10NxQm1M8SoDf0OJ7a_HyxD8Rt27E0FQ(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Here is another update from the Search Platform team. This one > includes the week of 2018-04-16 and 2018-04-23 > > As always, feedback and questions welcome. > > == Highlights== > * The Search team is looking for a volunteer to help with this easy > ticket: T192458 Enable search result ranking in MySQL full text > search. [0] > > == Discussions == > > === Search === > * Serbian-language wikis have been updated with a new language > analyzer for search that does some stemming (so that related forms of > a word can find each other) and handles the transliteration between > the Serbian Cyrillic and Latin alphabets, which are both used in > Serbian. [1] > *...and work on the plugin and re-indexing the wikis to allow the new > Serbian alphabets to be used is also done [2] [3] [4] > * Stas fixed some bugs for deep category search [5] [6] > * Completion search for Lexemes merged [7] > * Fixed some indexing errors [8] > * Cirrus profile management has been updated to provide a standard way > to override profile content [9] > * Fixed issues with ElasticSearch latency alerts on ~15 wikis that had > the issue [10] > > > [0] https://phabricator.wikimedia.org/T192458 > [1] https://en.wikipedia.org/wiki/Serbian_language#Writing_system > [2] https://phabricator.wikimedia.org/T189239 > [3] https://phabricator.wikimedia.org/T183015 > [4] https://phabricator.wikimedia.org/T189265 > [5] https://phabricator.wikimedia.org/T192270 > [6] https://phabricator.wikimedia.org/T188350 > [7] https://phabricator.wikimedia.org/T190970 > [8] https://phabricator.wikimedia.org/T192609 > [9] https://phabricator.wikimedia.org/T191876 > [10] https://phabricator.wikimedia.org/T191236 > > --- > > Subscribe to receive on-wiki (or opt-in email) notifications of the > Discovery weekly update. > > https://www.mediawiki.org/wiki/Newsletter:Discovery_Weekly > > The archive of all past updates can be found on MediaWiki.org: > > https://www.mediawiki.org/wiki/Discovery/Status_updates > > Interested in getting involved? See tasks marked as "Easy" or > "Volunteer needed" in Phabricator. > > [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R > [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R > > Yours, > Chris Koerner > Community Liaison > Wikimedia Foundation > > > > ------------------------------ > > Message: 2 > Date: Mon, 30 Apr 2018 15:54:57 -0500 > From: Chris Koerner <ckoerner(a)wikimedia.org> > To: wikitech-l(a)lists.wikimedia.org, mobile-l > <mobile-l(a)lists.wikimedia.org> > Subject: [Wikitech-l] Readers Monthly update for April 2018 > Message-ID: > <CAKW0rmFcTx00= > bxRnW+eOMdrUqFzQrxZJmF99g6NV7Gb7PuJYA(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hello again, > This is the monthly update from the Readers team at the Wikimedia > Foundation for April 2018. > > As always, feedback and questions are welcome. > > ==Highlights== > * Synced Reading Lists are now available on both Android and iOS. [0] > > === Apps=== > * ''Android -'' Synced reading lists are now available on Android! [1] > [2] This has been one of the most consistently requested app > features, and the team is delighted to be able to bring it to you. A > browser extension is in the works to allow you to add articles to your > reading lists from the web. We'll announce in the app when it's ready. > * ''iOS'' - Guess what? When we said syncing we meant across platforms > too! iOS also released syncing reading lists, brining folders, search > and sort to our Saved pages, and letting you sync across to Android. > [3] > > === Web === > * Page Previews were enabled by default for logged-out users on > English and German Wikipedia. [4] The feature is now deployed to all > Wikipedia projects for logged-out users. Logged-in users can enable > the feature in their Preferences. [5] [6] [7] [8] > > === New Readers === > * New Reader updates can be found at Meta. [9] > > [0] https://www.mediawiki.org/wiki/Wikimedia_Apps/Synced_Reading_Lists > [1] https://play.google.com/store/apps/details?id=org.wikipedia&hl=en_GB > [2] https://releases.wikimedia.org/mobile/android/wikipedia/stable/ > [3] https://itunes.apple.com/app/wikipedia/id324715238 > [4] https://www.mediawiki.org/wiki/Page_Previews > [5] https://www.mediawiki.org/wiki/Page_Previews > [6] > https://blog.wikimedia.org/2018/04/18/how-we-designed-page-previews-for-wik… > [7] > https://blog.wikimedia.org/2018/04/20/why-it-took-a-long-time-to-build-that… > [8] > https://phabricator.wikimedia.org/phame/post/view/93/extension_popups_page_… > [9] https://meta.wikimedia.org/wiki/New_Readers/Updates > > --- > > Subscribe to receive theses updates as on-wiki notifications or opt-in > email. > > https://www.mediawiki.org/wiki/Newsletter:Readers_Monthly > > The archive of all past updates can be found on MediaWiki.org: > > https://www.mediawiki.org/wiki/Reading/Status_updates > > > Yours, > Chris Koerner > Community Liaison > Wikimedia Foundation > > > > ------------------------------ > > Message: 3 > Date: Tue, 01 May 2018 00:00:27 +0000 > From: communitymetrics(a)wikimedia.org > To: wikitech-l(a)lists.wikimedia.org > Subject: [Wikitech-l] Phabricator monthly statistics - 2018-04 > Message-ID: <5ae7ae1b.EJXBgUMah/DBKYY/%communitymetrics(a)wikimedia.org> > Content-Type: text/plain; charset=us-ascii > > > Hi Community Metrics team, > > This is your automatic monthly Phabricator statistics mail. > > Accounts created in (2018-04): 292 > Active Maniphest users (any activity) in (2018-04): 914 > Task authors in (2018-04): 502 > Users who have closed tasks in (2018-04): 269 > > Projects which had at least one task moved from one column to another on > their workboard in (2018-04): 285 > > Tasks created in (2018-04): 2292 > Tasks closed in (2018-04): 1949 > Open and stalled tasks in total: 38191 > > Median age in days of open tasks by priority: > > Unbreak now: 17 > Needs Triage: 396 > High: 663 > Normal: 928 > Low: 1186 > Lowest: 1141 > > (How long tasks have been open, not how long they have had that priority) > > Active Differential users (any activity) in (2018-04): 22 > > TODO: Numbers which refer to closed tasks might not be correct, as > described in https://phabricator.wikimedia.org/T1003 . > > Yours sincerely, > Fab Rick Aytor > > (via community_metrics.sh on phab1001 at Tue May 1 00:00:27 UTC 2018) > > > > ------------------------------ > > Message: 4 > Date: Mon, 30 Apr 2018 19:38:36 -0700 > From: Joe Matazzoni <jmatazzoni(a)wikimedia.org> > To: wikitech-l(a)lists.wikimedia.org, Map integration > <maps-l(a)lists.wikimedia.org> > Subject: [Wikitech-l] Mapframe maps now work on English Wikipedia > Message-ID: <2F63F912-6E3C-4B87-8FFD-AAD0EBD7DE80(a)wikimedia.org> > Content-Type: text/plain; charset=utf-8 > > English Wikipedians can now use the mapframe function to embed maps right > on a page. (Here’s an example, showing the location of this year’s > Wikimania conference. [1]). Mapframe was requested by the English community > via RfC last year [2] and the request was reconfirmed this spring [3]. If > you you’re new to mapframe, this Kartographer help page [4] shows how to > use it. > > Expect more significant new features in the coming weeks, with the > implementation of the long-awaited map internationalization features [5]. > After internationalization, maps will display in the content language of > the wiki they’re published on. Until then, they will continue to display in > the language of the territory mapped. (You can experiment with > internationalized maps on testwiki now—here’s a page of examples. [6]) > > These features are brought to you as part of the Map Improvements 2018 > project [7]. Please try mapframe out on English Wikipedia and let us know > what you think on the project talk page [8]. We’re listening. > > [1] > https://en.wikipedia.org/wiki/User:JMatazzoni_(WMF)/maptest?action=edit#Loc… > < > https://en.wikipedia.org/wiki/User:JMatazzoni_(WMF)/maptest?action=edit#Loc… > > > [2] > https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_15… > < > https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_15… > >? > [3] > https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_16… > < > https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_16… > > > [4] https://www.mediawiki.org/wiki/Help:Extension:Kartographer < > https://www.mediawiki.org/wiki/Help:Extension:Kartographer> > [5] > https://www.mediawiki.org/wiki/Map_improvements_2018#April_18,_2018,_Specia… > < > https://www.mediawiki.org/wiki/Map_improvements_2018#April_18,_2018,_Specia… > > > [6] https://test2.wikipedia.org/wiki/Map_internationalization_examples < > https://test2.wikipedia.org/wiki/Map_internationalization_examples> > [7] https://www.mediawiki.org/wiki/Map_improvements_2018 < > https://www.mediawiki.org/wiki/Map_improvements_2018>[8] > https://www.mediawiki.org/wiki/Talk:Map_improvements_2018 < > https://www.mediawiki.org/wiki/Talk:Map_improvements_2018> > _____________________ > > Joe Matazzoni > Product Manager, Collaboration > Wikimedia Foundation, San Francisco > > > "Imagine a world in which every single human being can freely share in the > sum of all knowledge." > > > > > > > ------------------------------ > > Message: 5 > Date: Tue, 1 May 2018 19:17:04 +1000 > From: Josephine Lim <josephinelim86(a)gmail.com> > To: wikitech-l(a)lists.wikimedia.org, commons-l(a)lists.wikimedia.org, > wikivoyage-l(a)lists.wikimedia.org, mobile-l > <mobile-l(a)lists.wikimedia.org> > Subject: [Wikitech-l] Commons app - version 2.7 release > Message-ID: > <CANezgv= > Pu9v+t6+6i9Sjep7YtU0+pkRp6235JRqSj6375RvCQw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi all, > > We've just released version 2.7 of the Commons Android app ! \o/ The new > version is available for download on the Google Play Store[1] as well as > F-Droid[2]. > > This update includes several new features: > > - New "Nearby places that need pictures" UI with direct uploads (and > associated category suggestions) - Two-factor authentication login - > Notifications activity to display Commons user talk messages - Real-time > location tracking in Nearby - Improvements to UI of navigation drawer, > tutorial, media details view, login and settings - Option to nominate > picture for deletion in media details view > > We are also thrilled to be mentoring two new contributors for this year's > GSoC - Tanvi Dadu and Ujjwal Agrawal. :) > > Thank you all for your support and encouragement thus far! More details and > screenshots can be found in my blog post[3]. Feedback, bug reports, and > suggestions are always welcome on our GitHub page[4]. > > > Best regards, > Josephine (project maintainer) > > [1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons > [2]: https://f-droid.org/repository/browse/?fdid=fr.free.nrw.commons > [3]: > > https://cookiesandcodeblog.wordpress.com/2018/04/21/commons-app-version-2-7… > [4]: https://github.com/commons-app/apps-android-commons/issues > > > ------------------------------ > > Message: 6 > Date: Tue, 1 May 2018 19:25:00 +1000 > From: Josephine Lim <josephinelim86(a)gmail.com> > To: wikitech-l(a)lists.wikimedia.org, commons-l(a)lists.wikimedia.org, > wikivoyage-l(a)lists.wikimedia.org, mobile-l > <mobile-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Commons app - version 2.7 release > Message-ID: > < > CANezgvnJEA31-HFzm9VUijLfN4NKdYAynoveOSpu1EZ1RJvdXA(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Sorry about the lack of formatting - I am not sure why that happened. :( To > rephrase, the new features are: > > * New "Nearby places that need pictures" UI with direct uploads (and > associated category suggestions) > * Enabled two-factor authentication login > * Enabled viewing of Commons user talk messages > * Real-time location tracking in Nearby > * Improvements to UI of navigation drawer, tutorial, media details view, > login and settings > * Option to nominate picture for deletion in media details view > > Best regards, > Josephine > > On 1 May 2018 at 19:17, Josephine Lim <josephinelim86(a)gmail.com> wrote: > > > Hi all, > > > > We've just released version 2.7 of the Commons Android app ! \o/ The new > > version is available for download on the Google Play Store[1] as well as > > F-Droid[2]. > > > > This update includes several new features: > > > > - New "Nearby places that need pictures" UI with direct uploads (and > > associated category suggestions) - Two-factor authentication login - > > Notifications activity to display Commons user talk messages - Real-time > > location tracking in Nearby - Improvements to UI of navigation drawer, > > tutorial, media details view, login and settings - Option to nominate > > picture for deletion in media details view > > > > We are also thrilled to be mentoring two new contributors for this year's > > GSoC - Tanvi Dadu and Ujjwal Agrawal. :) > > > > Thank you all for your support and encouragement thus far! More details > > and screenshots can be found in my blog post[3]. Feedback, bug reports, > and > > suggestions are always welcome on our GitHub page[4]. > > > > > > Best regards, > > Josephine (project maintainer) > > > > [1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons > > [2]: https://f-droid.org/repository/browse/?fdid=fr.free.nrw.commons > > [3]: https://cookiesandcodeblog.wordpress.com/2018/04/21/commons-app- > > version-2-7-beta-release/ > > [4]: https://github.com/commons-app/apps-android-commons/issues > > > > > > > > > > > ------------------------------ > > Message: 7 > Date: Tue, 1 May 2018 06:19:08 -0500 > From: zppix e <megadev44s.mail(a)gmail.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] Commons app - version 2.7 release > Message-ID: > <CAL_JNvp0w4ZkuY+J4Q3DaJX8DBHARASE= > C-wvXS18Ws4EX8LZA(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Is there a plan to release to iOS? > > Thanks, > Zppix > Volunteer Developer for WMF > Volunteer Support for Mozilla > www.enwp.org/User:Zppix > > > On Tue, May 1, 2018 at 4:25 AM, Josephine Lim <josephinelim86(a)gmail.com> > wrote: > > > Sorry about the lack of formatting - I am not sure why that happened. :( > To > > rephrase, the new features are: > > > > * New "Nearby places that need pictures" UI with direct uploads (and > > associated category suggestions) > > * Enabled two-factor authentication login > > * Enabled viewing of Commons user talk messages > > * Real-time location tracking in Nearby > > * Improvements to UI of navigation drawer, tutorial, media details view, > > login and settings > > * Option to nominate picture for deletion in media details view > > > > Best regards, > > Josephine > > > > On 1 May 2018 at 19:17, Josephine Lim <josephinelim86(a)gmail.com> wrote: > > > > > Hi all, > > > > > > We've just released version 2.7 of the Commons Android app ! \o/ The > new > > > version is available for download on the Google Play Store[1] as well > as > > > F-Droid[2]. > > > > > > This update includes several new features: > > > > > > - New "Nearby places that need pictures" UI with direct uploads (and > > > associated category suggestions) - Two-factor authentication login - > > > Notifications activity to display Commons user talk messages - > Real-time > > > location tracking in Nearby - Improvements to UI of navigation drawer, > > > tutorial, media details view, login and settings - Option to nominate > > > picture for deletion in media details view > > > > > > We are also thrilled to be mentoring two new contributors for this > year's > > > GSoC - Tanvi Dadu and Ujjwal Agrawal. :) > > > > > > Thank you all for your support and encouragement thus far! More details > > > and screenshots can be found in my blog post[3]. Feedback, bug reports, > > and > > > suggestions are always welcome on our GitHub page[4]. > > > > > > > > > Best regards, > > > Josephine (project maintainer) > > > > > > [1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons > > > [2]: https://f-droid.org/repository/browse/?fdid=fr.free.nrw.commons > > > [3]: https://cookiesandcodeblog.wordpress.com/2018/04/21/commons-app- > > > version-2-7-beta-release/ > > > [4]: https://github.com/commons-app/apps-android-commons/issues > > > > > > > > > > > > > > _______________________________________________ > > Wikitech-l mailing list > > Wikitech-l(a)lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > ------------------------------ > > End of Wikitech-l Digest, Vol 178, Issue 1 > ****************************************** >

1 0

Mapframe maps now work on English Wikipedia
by Joe Matazzoni 01 May '18

01 May '18

English Wikipedians can now use the mapframe function to embed maps right on a page. (Here’s an example, showing the location of this year’s Wikimania conference. [1]). Mapframe was requested by the English community via RfC last year [2] and the request was reconfirmed this spring [3]. If you you’re new to mapframe, this Kartographer help page [4] shows how to use it. Expect more significant new features in the coming weeks, with the implementation of the long-awaited map internationalization features [5]. After internationalization, maps will display in the content language of the wiki they’re published on. Until then, they will continue to display in the language of the territory mapped. (You can experiment with internationalized maps on testwiki now—here’s a page of examples. [6]) These features are brought to you as part of the Map Improvements 2018 project [7]. Please try mapframe out on English Wikipedia and let us know what you think on the project talk page [8]. We’re listening. [1] https://en.wikipedia.org/wiki/User:JMatazzoni_(WMF)/maptest?action=edit#Loc… <https://en.wikipedia.org/wiki/User:JMatazzoni_(WMF)/maptest?action=edit#Loc…> [2] https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_15… <https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_15…>? [3] https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_16… <https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_16…> [4] https://www.mediawiki.org/wiki/Help:Extension:Kartographer <https://www.mediawiki.org/wiki/Help:Extension:Kartographer> [5] https://www.mediawiki.org/wiki/Map_improvements_2018#April_18,_2018,_Specia… <https://www.mediawiki.org/wiki/Map_improvements_2018#April_18,_2018,_Specia…> [6] https://test2.wikipedia.org/wiki/Map_internationalization_examples <https://test2.wikipedia.org/wiki/Map_internationalization_examples> [7] https://www.mediawiki.org/wiki/Map_improvements_2018 <https://www.mediawiki.org/wiki/Map_improvements_2018>[8] https://www.mediawiki.org/wiki/Talk:Map_improvements_2018 <https://www.mediawiki.org/wiki/Talk:Map_improvements_2018> _____________________ Joe Matazzoni Product Manager, Collaboration Wikimedia Foundation, San Francisco "Imagine a world in which every single human being can freely share in the sum of all knowledge."

1 0

Phabricator monthly statistics - 2018-04
by communitymetrics＠wikimedia.org 01 May '18

01 May '18

Hi Community Metrics team, This is your automatic monthly Phabricator statistics mail. Accounts created in (2018-04): 292 Active Maniphest users (any activity) in (2018-04): 914 Task authors in (2018-04): 502 Users who have closed tasks in (2018-04): 269 Projects which had at least one task moved from one column to another on their workboard in (2018-04): 285 Tasks created in (2018-04): 2292 Tasks closed in (2018-04): 1949 Open and stalled tasks in total: 38191 Median age in days of open tasks by priority: Unbreak now: 17 Needs Triage: 396 High: 663 Normal: 928 Low: 1186 Lowest: 1141 (How long tasks have been open, not how long they have had that priority) Active Differential users (any activity) in (2018-04): 22 TODO: Numbers which refer to closed tasks might not be correct, as described in https://phabricator.wikimedia.org/T1003 . Yours sincerely, Fab Rick Aytor (via community_metrics.sh on phab1001 at Tue May 1 00:00:27 UTC 2018)

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l May 2018