Wikitech-l March 2016

wikitech-l@lists.wikimedia.org

109 participants
102 discussions

2016-03-30 Scrum of Scrums meeting notes
by Grace Gellerman 30 Mar '16

30 Mar '16

Process update starting next week: * If you'd like something you say to make it into the weekly Tech News, tag it with #technews https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-03-30 = *2016-03-30* = == Technology == === Analytics === * '''*Blocking'''*: none * '''*Blocked'''*: none * '''*Updates*'''*:* ** Unique Devices data released, pageviews data officially released, pagecounts-raw, pagecounts-all-sites deprecated, dumps.wikimedia.org/analytics has details ** Request Breakdown reports from Hadoop are ready, they replace the old Wikistats squid reports, some UI improvements coming shortly - === Architecture === * '''*Blocking'''*: ** ??? * '''*Blocked'''*: ** ??? * '''*Updates*'''*:* ** ??? === Performance === * '''*Blocking'''*: ** ??? * '''*Blocked'''*: ** ??? * '''*Updates*'''*:* ** ??? === Release Engineering === * '''*Blocking'''*: ** ??? * '''*Blocked'''*: ** ??? * '''*Updates*'''*:* ** scap 3.1 will be in production on Tuesday April 5th, now with large binary support! (via git-fat (what trebuchet used for feature parity)) ** Code freeze week of April 18th (DC switchover) === Research === * '''*Blocking'''*: ** none * '''*Blocked'''*: ** none * '''*Updates*'''*:* ** Deployed ORES swagger & v2 paths. Can now ask for feature lists and do feature injection when scoring. Announcement coming. === Security === * '''*Blocking'''*: ** ??? * '''*Blocked'''*: ** ??? * '''*Updates*'''*:* ** ??? === Services === * '''*Blocking'''*: ** / * '''*Blocked'''*: ** / * '''*Updates*'''*:* ** RESTBase *** Redirects for File: titles active only for the native moblie apps *** general availability blocked on VE - https://phabricator.wikimedia.org/T130757 *** bumped s-maxage for purged content to 1 week ** deployed the change-propagation service (via scap3) ** working on docs - https://www.mediawiki.org/wiki/Documentation/Services === Technical Operations === * '''*Blocking'''*: ** noone * '''*Blocked'''*: ** by noone * '''*Updates*'''*:* ** changeprop is live, worked with Marko from Services team ** working on ORES and scap3 integration with Amir == Product == === Community Tech === * '''*Blocking'''*: ** ??? * '''*Blocked'''*: ** ??? * '''*Updates*'''*:* ** ??? === Discovery === * '''*Blocking'''*: ** Not that we are aware of * '''*Blocked'''*: ** Quick Surveys:Not known to be blocked on anyone in SoS, but we might ask for help ** Existing: ops https://phabricator.wikimedia.org/T127014 and security https://phabricator.wikimedia.org/T127014 * '''*Updates*'''*:* ** We are experimenting publishing weekly status updates: https://www.mediawiki.org/wiki/Discovery/Status_updates === Editing === ==== Collaboration ==== * '''Blocking''': ** External store work * '''Blocked''': * '''Updates''': ** Working on support for Flow notifications being properly hidden on moderation ** Work on the Echo special page ==== Language ==== * '''*Blocking'''*: ** None * '''*Blocked'''*: ** None * '''*Updates*'''*:* ** Work on Parallel Corpora dump (will) need some time from Ops (Ariel), See: https://phabricator.wikimedia.org/T127793 ==== Multimedia ==== * '''*Blocking'''*: ** ??? * '''*Blocked'''*: ** ??? * '''*Updates*'''*:* ** ??? ==== Parsing ==== [ Subbu: I am feeling under the weather and will probably be napping / resting and won't show up for this SoS .. Scott might show up if he sees his email in time, but I've updated the etherpad in any case ] * '''*Blocking'''*: ** None * '''*Blocked'''*: ** None * '''*Updates*'''*:* ** VE team and CX teams already knows about the tasks I've filed against them for setting user-agent headers, accept headers. I've filed a ticket against Flow as well to set user-agent header in your request. Not urgent, but good to get it done sooner than later. ** Work ongoing to move data-mw out from an inlined attribute .. CX, VE, Flow: please start thinking about what this means and how you will process data-mw and html from separate api requests. The Parsoid and RESTBase side work will be done in 2-3 weeks time (which includes performance evaluation and impact of supporting old versions, etc.). We'll not turn this on in production (3-4 weeks away at least) without consulting with all affected clients, but the accept: header is your way of getting the old version till you are ready to switch, but we prefer that the switch not be delayed inordinately. I've already filed tickets against these projects, but this is just a heads up. ==== VisualEditor ==== * '''*Blocking'''*: ** ??? * '''*Blocked'''*: ** ??? * '''*Updates*'''*:* ** ??? === Fundraising Tech === * '''*Blocking'''*: ** None * '''*Blocked'''*: ** None * '''*Updates*'''*:* ** More DonationInterface refactoring ** Investigating ActiveMQ replacement options ** More work towards mass (reversible) contact de-duping in CiviCRM ** Scoping work to update PayPal integration === Reading === ==== Android ==== * '''*Updates*'''*:* ** Content Service is rolling out successfully. (25% of Android production app as of Monday evening) ==== iOS ===== * '''*Blocking'''*: ** None * '''*Blocked'''*: ** None * '''*Updates*'''*:* ** 5.0.1 Deployed last week ** 5.0.2 Being deployed this week (Just decided this on Monday - we received a call from Apple that there is an OS bug causing our app to crash and we needed to work around it) ==== Web ==== * Language switcher overlay being deployed ==== Reading Infrastructure ==== * Gather * AuthManager for 1.27 branch in progress (disabled switch for now) * Flow, able to tackle https://phabricator.wikimedia.org/T129397 ? * Wikidata, https://phabricator.wikimedia.org/T131176 ?

1 0

Reminder: CREDIT showcase Wednesday, 6-April-2016
by Adam Baso 30 Mar '16

30 Mar '16

Hello world - Reminder: the next CREDIT showcase will be 6-April-2016 at 1800 UTC (1100 SF). Looking forward to your demos! Please see the following links for information and to add your demo :) https://www.mediawiki.org/wiki/CREDIT_showcase https://etherpad.wikimedia.org/p/CREDIT -Adam

1 0

[IEG] Sharing of my Individual Engagement Grant application, please common on it
by DJAKN 30 Mar '16

30 Mar '16

Hello all, I'm prepared to participate in IEG and has an idea closely linked to the Accuracy Review Project raised by James Salsman. Here is a brief summary of my proposal: Out-of-date information and references are common in Wikipedia entries, especially in Chinese Wikipedia. Therefore, I would like to evaluate some existed solutions of identifying those out-of-date contents, and create a new bot to identify the information based on the results of testing. More detailed tests will be arranged after that by selected entries from Wikipedia and the cases that we compile. And here is the URL of the project the proposal: https://meta.wikimedia.org/wiki/Grants:IdeaLab/Searching_for_out-of-date_in… Because there is already relative discussion in this mailing list, please comment on the proposal in the discussion board of it at: https://meta.wikimedia.org/wiki/Grants_talk:IdeaLab/Searching_for_out-of-da… Li Linxuan

1 0

[BREAKING CHANGE] Legacy wikibits will no longer loaded by default on Wikimedia wikis and MediaWiki 1.27
by Krinkle 29 Mar '16

29 Mar '16

TL;DR: * Review site scripts to verify that no wikibits methods[1] are used. * If you find usage of wikibits, refactor the code to use newer methods instead, or add a dependency on the 'mediawiki.legacy.wikibits' module. Hi all, The deprecation and eventual removal of the legacy "wikibits" JavaScript module has been a long time coming. This announces another step in that direction. In 2011, wikibits was deprecated following the introduction of ResourceLoader in MediaWiki 1.17. To accommodate pre-ResourceLoader code that doesn't have a concept of dependencies, $wgIncludeLegacyJavaScript was created to allow existing sites (such as Wikimedia wikis) to load "mediawiki.legacy.wikibits" by default on all pages. While most code no longer uses wikibits, it remains set to this day. In 2013, we introduced mw.log.deprecate in MediaWiki 1.23 to help you detect any use of deprecated methods in the browser's developer console.[2] We have seen a big reduction in the use of such methods.[3] In 2015, we made significant performance improvements in MediaWiki 1.26, by running JavaScript asynchronously rather than blocking page rendering. To avoid breaking undeclared use of wikibits, we made an exception for wikibits and kept it as blocking other JavaScript modules on page views, re-purposing $wgIncludeLegacyJavaScript to mean "always load wikibits before other modules". Now, as the last step before removing wikibits from MediaWiki, it will first no longer load by default in MediaWiki 1.27. This change will roll out on Wikimedia wikis in April 2016. If you find usage of wikibits features without a dependency, please refactor this code to use the modern replacements[1], or add an explicit dependency as temporary stop-gap while figuring out how to refactor the code. Before re-factoring, please remember to first check whether the associated code is working. Many wikibits methods have become empty placeholders to avoid cascading failures. As such, blind updates may cause old or broken code that is currently invisible to re-activate itself. Removing dead code speeds up wikis for all users, and reduces the risk of things going wrong in future. For third-party wikis, this will ship in MediaWiki 1.27.0. If needed, you can alter LocalSettings.php and set $wgIncludeLegacyJavaScript to true. This will give you time to fix missing dependencies on wikibits. In MediaWiki 1.28, to be released in November 2016, the wikibits module will be removed entirely. -- Krinkle [1] https://www.mediawiki.org/wiki/ResourceLoader/Legacy_JavaScript [2] https://lists.wikimedia.org/pipermail/wikitech-l/2013-October/072776.html [3] https://grafana.wikimedia.org/dashboard/db/mw-js-deprecate?from=now-10M

5 7

Improving Wikimedia's Code Review process
by Andre Klapper 29 Mar '16

29 Mar '16

Hey everybody! At the Wikimedia Developer Summit there was a session about "Making Code Review not suck" [1]. The outcome are Phabricator (sub)tasks of the task "Define potential actions to reduce code review queues and waiting times" in https://phabricator.wikimedia.org/T101686 The following potential actions items have been identified: * https://phabricator.wikimedia.org/T129842 : Decide whether to have a "Code Review" committee / working group * https://phabricator.wikimedia.org/T129067 : Agree on and document a structured, standardized approach for reviewing code contributions * https://phabricator.wikimedia.org/T129068 : Improve code contribution guidelines for patch authors * https://phabricator.wikimedia.org/T128370 : Update ownership list on [[mw:Developers/Maintainers]] * https://phabricator.wikimedia.org/T128371 : Set up Code Review office hours * https://phabricator.wikimedia.org/T128372 : Document use of Owners in Phabricator and advertise it * https://phabricator.wikimedia.org/T115852 : Fix unclear maintenance responsibilities for some parts of MediaWiki core repository Discussion on each of those proposals is welcomed in the corresponding tasks! Thanks, andre [1] https://phabricator.wikimedia.org/T114419 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

7 6

Applications open for WikiCite (Berlin, May 25-26, 2016)
by Dario Taraborelli 29 Mar '16

29 Mar '16

Citations and references are the building blocks of Wikimedia projects. However, as of today, they are still treated as second-class citizens. Structured data bases such as Wikidata offer a unique opportunity <https://www.wikidata.org/wiki/Wikidata:WikiProject_Source_MetaData> to turn into reality over a decade of endeavors to build the sum of all citations and bibliographic metadata into a centralized repository. To coordinate upcoming work in this space, we're organizing a technical event in late May and opening up applications for prospective participants. *WikiCite 2016 <https://meta.wikimedia.org/wiki/WikiCite_2016>* is a hands-on event focused on designing data models and technology to *improve the coverage, quality, standards-compliance and machine-readability of citations and source metadata in Wikipedia, Wikidata and other Wikimedia projects*. Our goal, in particular, is to define a technical roadmap for building a repository of all Wikimedia references in Wikidata. We are bringing together Wikidatans, Wikipedians, software engineers, data modelers, and information and library science experts from organizations including *Crossref*, *Zotero*, *CSL*, *ContentMine*, *Google*, *Datacite*, *NISO*, *OCLC* and the *NIH*. We are also inviting academic researchers with experience working with Wikipedia's citations and bibliographic data. WikiCite will be hosted in *Berlin* on *May 25-26, 2016*. Participation to the event is capped at about 50 participants and we expect to have a number of open slots for applicants: - if you were pre-invited and have already filled in a form, you will receive a separate note from the organizers - if you have not been invited but you would like to participate, please fill in this application form <http://goo.gl/forms/Yv6rve2wCt> to give us some information about you and your interest and expected contribution to the event. Please help us pass this on to anyone who has done important technical work on Wikimedia references and citations. *Important dates* - *March 29, 2016*: applications open - *April 11, 2016*: applications close - *April 15, 2016*: notifications of acceptance are issued (if you applied for a travel grant, we'll be able to confirm by this date if we can cover the costs of your trip) For any question, you can contact the organizing committee: wikicite(a)wikimedia.org The organizers, Dario Taraborelli Jonathan Dugan Lydia Pintcher Daniel Mietchen Cameron Neylon *Dario Taraborelli *Head of Research, Wikimedia Foundation wikimediafoundation.org • nitens.org • @readermeter <http://twitter.com/readermeter>

1 0

How to make a good MediaWiki distribution?
by Robert Vogel 28 Mar '16

28 Mar '16

Hello everybody. I've opened up a task on phabricator (T130812) about the question of how to make a good MediaWiki distribution. And I'd like to ask anyone interested in this topic for thoughts, suggestions and advice. Your help is highly appreciated. Details can be found on the task page [1]. [1] https://phabricator.wikimedia.org/T130812 -- Robert Vogel

1 0

(no subject)
by イノウエナオキ 27 Mar '16

27 Mar '16

1 0

Wikitech two-factor authentication
by Chris Steipp 26 Mar '16

26 Mar '16

Hi all, tl,dr; if you enabled two-factor authentication on your wikitech.wikimedia.org account this past week (since 23 March, 22:03 UTC), the second factor may have been removed, and you should re-enable it. The long version: Several users in the past few days reported that they had 2FA required for their wikitech account, but had not enabled it. This was my fault-- we converted the database token format and didn't account for users who had previously clicked on the "enable two-factor authentication" but never finish the enabling process. These users (about 400, as best as we can tell) were unfortunately locked out of their accounts as a result, after we updated the token format. I've disabled 2FA for accounts that looked like they were affected by our update. Unfortunately, this may have disabled 2FA for users who recently enabled 2FA also. So if you enabled 2FA on your account this past week, you may need to re-enable it-- please login to wikitech and verify that 2FA is still enabled for you account. Apologies to everyone affected. Chris

1 0

Hackathon buddy familiar with page content type stuff needed
by Danny B. 25 Mar '16

25 Mar '16

Hello, we're looking for a buddy to help / guidance with page-content-type handling extension at Jerusalem Hackathon. If you are familiar with it, but not coming to the hackathon, please let me know as well. Feel free to reply to me directly to not pollute the list. Thanks for help. Kind regards Danny B. [[meta:User:Danny B.]]

3 2

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 March 2016