Wikitech-l May 2017

wikitech-l@lists.wikimedia.org

82 participants
78 discussions

Tech Talk: A Gentle Introduction to Wikidata for Absolute Beginners [including non-techies!]
by Rachel Farrand 25 Jun '17

25 Jun '17

Please join for the following talk: *Tech Talk**:* A Gentle Introduction to Wikidata for Absolute Beginners [including non-techies!] *Presenter:* Asaf Bartov *Date:* February 09, 2017 *Time: *19:00 UTC <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+A+Ge…> Link to live YouTube stream <https://www.youtube.com/watch?v=eVrAx3AmUvA> *IRC channel for questions/discussion:* #wikimedia-office *Summary: *This talk will introduce you to the Wikimedia Movement's latest major wiki project: Wikidata. We will cover what Wikidata is, how to contribute, how to embed Wikidata into articles on other wikis, tools like the Wikidata Game, and how to query Wikidata (including SPARQL examples).

3 5

use of @inheritdoc
by Ryan Kaldari 24 Jun '17

24 Jun '17

A question that came up during Documentation Day was whether or not we should use the @inheritdoc convention for indicating that methods are documented in parent classes (rather than leaving them blank). Some arguments for using it include: * It can help code-sniffers and linters know that the documentation isn't missing. * It lets humans who are looking at the code know that they can find documentation elsewhere. * We are already using it. (It appears over 200 times in core JavaScript and about 40 times in core PHP. It's also used in at least 19 production extensions.) Some arguments for not using it: * It isn't necessary for generating docs at doc.wikimedia.org (Doxygen automatically inherits method docs if available). * It would require adding thousands of extra comment blocks to our code to implement it consistently. What are people's opinions on using it? Also, a quick note on usage. A lot of our existing usage looks like "* {@inheritdoc}". As explained at phpdoc.org, this usage is technically incorrect: "Currently some applications have DocBlocks containing just the {@inheritDoc} inline tag to indicate that their complete contents should be inherited. This usage breaks with the PHPDoc Standard as summaries cannot contain inline tags and inheritance is automatic; you do not need to define a special tag for it. However, it does make clear that an element has been explicitly documented (and thus not forgotten). As such we are working to include a new (normal) tag in the PHPDoc Standard @inheritDoc that will serve that purpose." Information about the use of @inheritdoc in JavaScript can be found at http://usejsdoc.org/tags-inheritdoc.html.

10 9

O'Reilly free books
by Amir Ladsgroup 23 Jun '17

23 Jun '17

O'Reilly just published some of their popular books for free, either as part of open access movement or some kind of marketing (or both). I find them useful to Wikimedia developers. It supports several types of e-books so you can read it in your kindle, etc.: * Performance, Operations, Release engineering: http://www.oreilly.com/webops-perf/free/ * Data, AI, Analytics: http://www.oreilly.com/data/free/ * Programming, architecture, Open source culture: http://www.oreilly.com/programming/free/ * Security: http://www.oreilly.com/security/free/ * Web platform, design: http://www.oreilly.com/web-platform/free/ This is a rather unusual type of email so I wasn't sure I was doing the right thing so I just sent it to wikitech-l. Please spread the word if you think it's okay or tell me if you think not. Thanks. Best

6 5

CREDIT showcase, Wednesday 7-June-2017
by Lani Goto 05 Jun '17

05 Jun '17

Hi! I'd like to welcome you to join us at the CREDIT showcase next week, Wednesday, 7-June-2017 at 1800 UTC / 1100 Pacific Time. We'd like to see your demos, whether they're rough works in progress or polished production material, or even just a telling of something you've been studying recently. For more information on the upcoming event, as well as recordings of previous events, please visit the following page: <http://goog_1968694156/> https://www.mediawiki.org/wiki/CREDIT_showcase And if you'd like to share the news about the upcoming CREDIT showcase, here's some suggested verbiage. Thanks! *Hi <FNAME>* *I hope all is well with you! I wanted to let you know about CREDIT, a monthly demo series that we’re running to showcaseopen source tech projects from Wikimedia’s Community, Reading, Editing, Discovery, Infrastructure and Technology teams. * *CREDIT is open to the public, and we welcome questions and discussion. The next CREDIT will be held on June 7th at 11am PT / 2pm ET / 18:00 UTC. * *There’s more info on MediaWiki, and on Etherpad, which is where we take notes and ask questions. You can also ask questions on IRC in the Freenode chatroom #wikimedia-office (web-based access here). Links to video will become available at these locations shortly before the event.* *Please feel free to pass this information along to any interested folks. Our projects tend to focus on areas that might be of interest to folks working across the open source tech community: language detection, numerical sort, large data visualizations, maps, and all sorts of other things.* *If you have any questions, please let me know! Thanks, and I hope to see you at CREDIT.* *YOURNAME* -- Lani Goto Project Assistant, Engineering Admin

1 1

Question re what-links-here
by Aran 02 Jun '17

02 Jun '17

Hello, I have some wikis which have had some of their content changed programmatically due to the code in a parser-function being changed. In the wikis that are MediaWiki 1.27, the links in the what-links-here didn't update after I ran the refreshLinks maintenance script. The ones that are 1.28's in the same situation the links updated fine after running the script... is this a known issue? is there any way I can update the links in the 1.27's without upgrading the wiki? Thanks, Aran

4 9

Congratulations to accepted candidates for Google Summer of Code 2017 & Outreachy Round 14
by Srishti Sethi 02 Jun '17

02 Jun '17

Hello, Please join me in welcoming Wikimedia's accepted candidates for Google Summer of Code 2017 and Outreachy Round 14! Google Summer of Code 2017 1. Alexander Jones, Texas, United States, Implement Thanks support in Pywikibot <https://phabricator.wikimedia.org/T161426> - John Mark Vandenberg 2. Amrit Sreekumar, Kerela, India, Improvements to ProofreadPage Extension and Wikisource <https://phabricator.wikimedia.org/T161111> - Yann Forget, Tpt 3. Feroz Ahmad, New Delhi, India, Add a "hierarchy" type to the Cargo extension <https://phabricator.wikimedia.org/T161609> - Yaron Koren, Nischayn22 4. Harjot Singh Bhatia, New Delhi, India, Adding Data storage feature and upgrading Quiz extension <https://phabricator.wikimedia.org/T160257> - Marielle Volz, Sam Reed 5. Harsh Shah, India, Build a similar to @NYPLEmoji bot for Commons images - Dereckson, Ariel 6. Keerthana S, India, Automatic editing suggestions and feedbacks for articles in Wiki Ed Dashboard <https://phabricator.wikimedia.org/T160840> - Sage Ross, Jonathan Morgan 7. Sejal Khatri, India, Provide enhanced usability for Wikimedia Programs & Events Dashboard managed by Wiki Education foundation < https://phabricator.wikimedia.org/T161929> - Sage Ross, Jonathan Morgan 8. Siddhartha Sarkar, India, Single Image Batch Upload < https://phabricator.wikimedia.org/T161670> - Basvb Outreachy Round 14 1. Ela Opper, Tel Aviv, Israel, "Remind me of this article in X days" MediaWiki notification <https://phabricator.wikimedia.org/T161823> - Matthew Flaschen and Moriel Schottlender 2. Medha Bansal, New Delhi, India, WikiEduDashboard: Allow Programs & Events Dashboard to make automatic edits on connected wikis < https://phabricator.wikimedia.org/T161568>- Jonathan Morgan, Sage Ross 3. Sonali Gupta, Rajasthan, India, Document process for creating new Zotero translator and getting it live in production < https://phabricator.wikimedia.org/T161191> - Marielle Volz We would like to encourage accepted candidates to introduce themselves on this thread, share with us where they are coming from and give a brief overview of the project they will be working on. We’re so proud of the contributions they have made so far to our community, and we look forward to having a wonderful time working with them over the summer! Also, a huge shout-out to the project mentors for their enthusiasm and commitment! Thank you to Sumit and Anna for coordinating this round along with me! Best, Srishti -- Srishti Sethi Developer Advocate Technical Collaboration team Wikimedia Foundation https://www.mediawiki.org/wiki/User:SSethi_(WMF)

8 7

Arch Comm evolution plan needs your feedback
by Victoria Coleman 02 Jun '17

02 Jun '17

Hi everyone, I wanted to bring to everyone’s attention the plan for evolving the WMF Architecture Committee. We are clarifying and broadening the scope and mandate of the Committee and renaming it to the Wikimedia Technical Committee (T-Comm for short). We are excited to share the plan with you! We have published the draft charter at https://www.mediawiki.org/wiki/Architecture_committee/Charter <https://www.mediawiki.org/wiki/Architecture_committee/Charter> and would appreciate your review and feedback over the next couple weeks. Looking forward to the discussion on the talk page! Victoria ( on behalf of the Arch Comm membership) Victoria Coleman Wikimedia Foundation 149 New Montgomery Street San Francisco, CA 94105 +1-650-703-8112 vcoleman(a)wikimedia.org

2 1

Join my Reddit AMA about Wikipedia and ethical, transparent AI
by Aaron Halfaker 02 Jun '17

02 Jun '17

Hey everybody, TL;DR: I wanted to let you know about an upcoming experimental Reddit AMA ("ask me anything") chat we have planned. It will focus on artificial intelligence on Wikipedia and how we're working to counteract vandalism while also making life better for newcomers. We plan to hold this chat on June 1st at 21:00 UTC/14:00 PST in the /r/iAMA subreddit[1]. I'd love to answer any questions you have about these topics questions, and I'll send a follow-up email to this thread shortly before the AMA begins. ---- For those who don't know who I am, I create artificial intelligences[2] that support the volunteers who edit Wikipedia[3]. I've been fascinated by the ways that crowds of volunteers build massive, high quality information resources like Wikipedia for over ten years. For more background, I research and then design technologies that make it easier to spot vandalism in Wikipedia—which helps support the hundreds of thousands of editors who make productive contributions. I also think a lot about the dynamics between communities and new users—and ways to make communities inviting and welcoming to both long-time community members and newcomers who may not be aware of community norms. For a quick sampling of my work, check out my most impactful research paper about Wikipedia[3], some recent coverage of my work from *Wired*[4], or check out the master list of my projects on my WMF staff user page[5], the documentation for the technology team I run[9], or the home page for Wikimedia Research[8]. This AMA, which I'm doing with with the Foundation's Communications department, is somewhat of an experiment. The intended audience for this chat is people who might not currently be a part of our community but have questions about the way we work—as well as potential research collaborators who might want to work with our data or tools. Many may be familiar with Wikipedia but not the work we do as a community behind the scenes. I'll be talking about the work I'm doing with the ethics of AI and how we think about artificial intelligence on Wikipedia, and ways we’re working to counteract vandalism on the world’s largest crowdsourced source of knowledge—like the ORES extension[6], which you may have seen highlighting possibly problematic edits on your watchlist and in RecentChanges. I’d love for you to join this chat and ask questions. If you do not or prefer not to use Reddit, we will also be taking questions on ORES' MediaWiki talk page[7] and posting answers to both threads. 1. https://www.reddit.com/r/IAmA/ 2. https://en.wikipedia.org/wiki/Artificial_intelligence 2. https://www.mediawiki.org/wiki/ORES 3. http://www-users.cs.umn.edu/~halfak/publications/The_Rise_and_Decline/halfa… 4. https://www.wired.com/2015/12/wikipedia-is-using-ai-to-expand-the-ranks-of-… 5. https://en.wikipedia.org/wiki/User:Halfak_(WMF) 6. https://www.mediawiki.org/wiki/Extension:ORES 7. https://www.mediawiki.org/wiki/Talk:ORES 8. https://www.mediawiki.org/wiki/Wikimedia_Research 9. https://www.mediawiki.org/wiki/Wikimedia_Scoring_Platform_team -Aaron Principal Research Scientist @ WMF User:EpochFail / User:Halfak (WMF)

2 2

Reading monthly update for May 2017
by Chris Koerner 01 Jun '17

01 Jun '17

Hello, Welcome to the first in a reoccurring monthly update from the Reading department at the Wikimedia foundation. Here we'll provide a quick summary of things that are currently being worked on. An archive of past activity can be found on Mediawiki.org. Feedback and questions are welcome. == Web == === New print styles for the mobile web === Based on the findings of the New Readers team, we learned that users are increasingly getting information online, and then sharing or consuming it offline. In terms of mobile devices, this often means taking screenshots of useful information, or saving the article as a PDF to read later on their phones. Our older print styles did not account for reading on mobile devices - they focused on paper printing. We will update our print styles for mobile devices to account for offline consumption, making them easier to read and navigate, as well as accounting for missing crucial information such as article title and branding.[0] === Moving the lead section before the infobox on the mobile web === Over the past few quarters, we've been focusing on the top of the article experience on the mobile website. One of the identified issues was that, for articles which contained an infobox, users were exposed to the infobox content prior to having an overview of the subject of the article itself. To improve on this issue, we've moved the lead section of each article so that it appears before the infobox on mobile, allowing readers to have access to the main content of the page earlier. This change is now live on all projects. Before, [0] After [1] === Completing related pages deployment === Since March 30, 2017, we have been running a test on enwiki on the related pages feature. Over the past month, we collected data and analyzed the performance of the feature.[2] Based on the results, we completed the deployment of the feature on mobile English Wikipedia. == New Readers == * The New Readers team is deep in beginning pilots to address the barriers that were identified as highest priority through deep research in 2016.[3] You can see deeper, cross-team updates at m:New Readers/Updates. [4] * For Reading, we're supporting the Android and Web teams in developing deeper support for readers who have internet sometimes, but want access to some content when they're offline or don't want to spend the data to read. To see a summary of that work, check out m:New Readers/Offline.[5] == Multimedia == * In addition to bugfixes and maintenance, the team has been evaluating the pre-release version of 3D model file support and collecting feedback via the Commons Village Pump.[6] During the forthcoming month the team will be prioritizing and working on 3D tasks in anticipation of a future launch.[7] == Other Noteworthy Stuff == * Following April's Q3 quarterly check-in, we examined core readership metrics for the same timespan in a followup presentation.[8] [9] [0] https://www.mediawiki.org/wiki/Reading/Web/Projects/Print_Styles#Mobile_Pri… [1] https://www.mediawiki.org/wiki/File:Mobile_website,_older_version_of_infobo… [2] https://www.mediawiki.org/wiki/File:Lead_paragraph_before_infobox_example_-… [3] https://www.mediawiki.org/wiki/Reading/Web/Projects/Related_pages#Metrics_a… [4] https://meta.wikimedia.org/wiki/New_Readers/Findings [5] https://meta.wikimedia.org/wiki/New_Readers/Updates [6] https://meta.wikimedia.org/wiki/New_Readers/Offline [7] https://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2017/05#Pre… [8] https://phabricator.wikimedia.org/tag/3d/ [9] https://www.mediawiki.org/wiki/File:Reading,_Comm_Tech_%26_TPG_Quarterly_Ch… [10] https://commons.wikimedia.org/wiki/File:Wikimedia_Foundation_Reading_metric… --- 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 - Discovery Wikimedia Foundation

1 0

2017-05-31 Scrum of Scrums meeting notes
by Grace Gellerman 31 May '17

31 May '17

https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-05-31 *= 2017-05-31 =* contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering == Call outs:== * Security: status of TemplateStyles security review? (—from Reading eng.) **its almost done. will be done end of this week at latest --bawolff * Analytics: EventLogging purging script will be deployed before end of Q4. Reminder: Default purging strategy for new schemas since July 2016 is full purge after 90 days. If you want new schemas sinc that date not to be fully purged after 90 days, please contact Analytics as soon as possible. * RelEng: If you've committed something recently that may affect performance, you maybe did affect performance: please check :) - https://phabricator.wikimedia.org/T166345 === Reading === ==== iOS ==== * Last week ** 5.5 - https://phabricator.wikimedia.org/project/view/2602/ *** Places search updates: https://phabricator.wikimedia.org/T159733 *** Update `Top Read` feed design: https://phabricator.wikimedia.org/T165510 *** Places accessibility: https://phabricator.wikimedia.org/T159733 *** Other bug fixes & enhancements * This week ** 5.5 - https://phabricator.wikimedia.org/project/view/2602/ *** Feature freeze, finish any remaining bug fixes & design tweaks *** Regression testing ==== Android ==== * Bug identified last week causing stale content on the German WP main page. Thanks to Arlo and the Parsoid crew for the quick fix. * Beta release planned for late this week (for real). Finishing up final tasks now. * Next release will finalize the UI components for readling list syncing. * New engineer hiring process is underway. (The new eng will replace Stephen who is moving to Reading Web.) * Current release board: https://phabricator.wikimedia.org/project/view/2352/ * Next release board: https://phabricator.wikimedia.org/project/view/2763/ ==== Multimedia ==== * Ongoing: Media Viewer improvements, bringing it in line with standards that didn't exist when it was written * Soon: 3D extension prioritization and fixes * Current work is largely stalled due to hiring process ==== Web ==== * Commencing work on Electron PDF. (cc Ops) * Clearing out backlog - with a focus on #wikimedia-log-errors (cc RelEngs) ==== Reading Infrastructure ==== * compiling Page Content Service Data Inventory for HTML endpoint ==== Wikidata ==== * attended Wikicite (after the hackathon) * Wikidata build is broken due to CI - it runs composer update. need someone to review jenkins-config change to add the ability to do composer install instead: ** https://gerrit.wikimedia.org/r/#/c/354522/ * discussed at hackathon to move away from having the Wikidata build entirely and put our libraries into mediawiki-vendor ==== Services ==== * Blockers: none * Updates: ** Getting ready to test automatic RESTBase blacklisting ==== Security ==== * Reviews: ** psy/psysh use on WMF servers ** Verification of whitelisted.yaml / graylisted.yaml === Editing === ==== Language ==== * No blockers. Not blocking. * CX new change in wmf3: User can now choose article publish destination in a better manner. ==== Parsing ==== * Waiting on the wmf2 train to roll out fully for some followup work / updates. * Linter patch to cache linter counts is still in review, but close to being merged. Once that gets in, and it rolls out, we will be able to re-enable linter on large wikis * https://gerrit.wikimedia.org/r/#/c/72053/ introduces a piglatin language variant for easier testing of language variant code. Needs reviews. Bartosz might already be on it. ==== Collaboration ==== * Continued work on namespace and tag filters for RCFilters * Followup and bug fixes on the new notification blacklist feature (now in Beta Cluster) * Working on tag validation for AbuseFilter ==== Analytics ==== * We found the issue in global unique devices count per top domain (*. wikipedia.org), fixed it and data looks good after vetting, will be productionized in short. * Ongoing: Webrequest Tagging (portal, pageviewAPI, etc.) * Making progress on Wikistats2 front-end (stats.wikimedia.org replacement) * CRing and testing EL purging script, we plan to deploy it before the end of the quarter. Reminder: Default purging strategy for new schemas since July 2016 is full purge after 90 days. ==== UI Standardization ==== * This week: ** Preparing urgent v0.23.0 with OOjs v2.1.0 dependency, bug fixes and further improvements around Promise-methods feat WindowManager ** Continuos work on style guide build process, semi-automated SVG export * Updates: ** OOjs UI: *** v0.22.0 released with 2 accessibility and several other (UI) improvements, among those **** Rename the 'MediaWiki' theme to 'WikimediaUI' for clarity on development focus **** WindowManager: Add `WindowInstance` - a Promise-based lifecycle object (Timo Tijhof) and follow **** Frameless button sizing equal framed ones is in **** Passing ARIA tests from 13 up to 18 **** OOjs UI demos now with strengthened mobile experience, clearer sectioning and in-demo widget code for copy & paster === Discovery === Meeting conflict, probably can't attend. * No blockers, continuing the work from previous one === Fundraising Tech === * Civi / mailhouse integration * Dead session debugging * Fraud filter fixes * Moving all DonationInterface queue code into library * Preparing to move DonationInterface configuration code into library * CentralNotice new features ready to deploy === RelEng === * Blocked ** MW 1.29 Release blocked on the tasks in: https://phabricator.wikimedia.org/project/view/2400/ *** Lots to do with JobQueue and the Database * Updates ** WARNING: Ops will be removing Salt near the end of next quarter, that means no more Trebuchet as well. See https://phabricator.wikimedia.org/T129290#3245438 for a list of things still needing migration to scap3. ** wmf.2 train issues, if you've committed something recently that may affect performance, you maybe did affect performance: please check :) - https://phabricator.wikimedia.org/T166345

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 2017