Wikitech-l October 2016

wikitech-l@lists.wikimedia.org

81 participants
88 discussions

Future of magic links / making ISBN linking easier
by Legoktm 21 Oct '16

21 Oct '16

Hi, In the RfC meeting for the Future of magic links RfC, it was agreed upon to disable magic links for the MW 1.28 release by default and begin the deprecation for Wikimedia sites. One of the subpoints was to provide migration tools and similar functionality. For RFC and PMID links, they were added to the default core interwiki map, and the Wikimedia one. But for ISBN, it points to the local wiki, so an interwiki link doesn't make sense. The two main proposals are: Virtual namespace ([[ISBN:0-7475-3269-9]]), which is similar to existing link syntax (double brackets), but is also a bit magical since there haven't been any new virtual namespaces since Special and Media in the initial version of MW. Parser function ({{#isbn:0-7475-3269-9}}), which is typically how new syntax/functions are added, but is farther away from traditional link syntax. I would appreciate comments on <https://phabricator.wikimedia.org/T148274> - I've written a patch for the virtual namespace as a POC, but writing one for the parser function if people prefer that, should be trivial. -- Legoktm

1 0

irc.wikimedia.org (kraz) reboot
by Daniel Zahn 21 Oct '16

21 Oct '16

Hi, this is to let you know that kraz, the server that runs irc.wikimedia.org had to be rebooted for a kernel upgrade. If you have IRC clients on that server (i know some use it for anti-vandal tools etc), and the clients don't auto-reconnect, please make them connect again now. (And ideally fix them so they automatically do it in the future). Thank you -- Daniel Zahn <dzahn(a)wikimedia.org> Operations Engineer

3 4

Disabled local uploads
by Danny B. 21 Oct '16

21 Oct '16

Hi, I've just noticed, that local uploads are completely disabled on projects which originally had them disabled for users, but allowed for admins and bureaucrats. Could somebody please point me to the relevant discussion about this topic as well as to relevant commits which are setting this behavior? Thank you in advance. Kind regards Danny B.

3 3

Looking for WikiDev Summit main topics and volunteers
by Quim Gil 20 Oct '16

20 Oct '16

Hi, this is a request from the organizers of the Wikimedia Developer Summit 2016 (San Francisco, January 9-11). We are looking for candidates to become main topics of the next Summit. Ideally complex topics with a high user impact (direct or indirect) and ramifications in multiple technical areas. Deciding a few main topics beforehand will help us inviting the people needing to be involved, especially non-WMF contributors requiring travel sponsorship. We are also looking for volunteers who want to get involved in the organization of the Summit, or want to provide feedback to improve our plans. If you have proposals for main topics and/or want to volunteer, please reply. Context: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2017 & https://lists.wikimedia.org/pipermail/wikitech-l/2016-September/086476.html -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

5 7

Public Event Streams (AKA RCStream replacement) question
by Andrew Otto 20 Oct '16

20 Oct '16

Hi all, We’ve been busy working on building a replacement for RCStream. This new service would expose recentchanges as a stream as usual, but also other types of event streams that we can make public. But we’re having a bit of an existential crisis! We had originally chosen to implement this using an up to date socket.io server, as RCStream also uses socket.io. We’re mostly finished with this, but now we are taking a step back and wondering if socket.io/websockets are the best technology to use to expose stream data these days. The alternative is to just use ‘streaming’ HTTP chunked transfer encoding. That is, the client makes a HTTP request for a stream, and the server declares that it will be sending back data indefinitely in the response body. Clients just read (and parse) events out of the HTTP response body. There is some event tooling built on top of this (namely SSE / EventSource), but the basic idea is a never ending streamed HTTP response body. So, I’m reaching out to to gather some input to help inform a decision. What will be easier for you users of RCStream in the future? Would you prefer to keep using socket.io (newer version), or would you prefer to work directly with HTTP? There seem to be good clients for socket.io and for SSE/EventSource in many languages. https://phabricator.wikimedia.org/T130651 has more context, but don’t worry about reading it; it is getting a little long. Feel free to chime in there or on this thread. Thanks! -Andrew Otto

8 15

2016-10-19 Scrum of Scrums meeting notes
by Grace Gellerman 19 Oct '16

19 Oct '16

https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-10-19 =2016-10-19= == Product == === Reading === ==== Android native app ==== * Current sprint ( https://phabricator.wikimedia.org/tag/mobile-app-android-sprint-93-neptuniu…) : * Start on Q2 goals for Wikidata descriptions * v2.4.160 released to production * Workaround to handle unexpected JSON service responses gracefully * CI screenshot regression testing * Next sprint (https://phabricator.wikimedia.org/project/view/2319/): * More Q2 goals for Wikidata descriptions ====Web==== * Current sprint: https://phabricator.wikimedia.org/project/view/2270/ - * Mainly tackling the tech debt - * Also working on moving the first paragraph in the lead section above the infobox - * Finished the work on prototype solutions to avoid FOUC (flash of unstyled content) on section collapsing: https://phabricator.wikimedia.org/T147338. We've demoed all 4 solutions to the team members. The next step is to decide on which solution we'll be using. * Next sprint: https://phabricator.wikimedia.org/project/view/2314/ - * Tech debt and hovercards instrumentation - ==== iOS native app ==== Current Board (5.3 is in Beta): https://phabricator.wikimedia.org/project/view/2220/ Since we last met: - * Feed based off of MCS (Mobile Content Service) and persisting to YapDatabase is complete & in beta - * "In the news" Notifications are complete and awaiting beta - * "In the news" in the explore feed is complete and awaiting beta Before we meet again: - * Adding alternate ToC (Table of Contents) style for UX research - * Notifications settings - * Bug fixes, crash fixes, converging to release of 5.3 No blockers ==== Mobile Content Service ==== Backlog: https://phabricator.wikimedia.org/tag/mobile-content-service/ Added more languages to 'In the news' feed portion. https://gerrit.wikimedia.org/r/#/c/315451/ Going to remove Chinese from it though due to an issue with language variant syntax and the inability to handle lang variantes in RB. https://phabricator.wikimedia.org/T147874 ==== Reading Infrastructure ==== * no blocking/blocked * ORES data in action API soon: https://phabricator.wikimedia.org/T143895 * OAuth approval workflow changes soon: https://phabricator.wikimedia.org/T103587#2621901 === Community Tech === * Sprint board: https://phabricator.wikimedia.org/tag/community-tech-sprint/ * No blockers * Not blocked * Since last week: * Did some more supporting work on Programs Dashboard * Local (wiki) ID and Global ID now populate in CentralAuth localuser table on new account attach * Did some work with NewPagesPatrol on enwiki - https://phabricator.wikimedia.org/T147225 * Work ongoing on maintenance script to backfill the columns for existing accounts: https://phabricator.wikimedia.org/T142503 * Work ongoing to modify Copypatrol (the plagiarism detection tool) to support more wikis https://phabricator.wikimedia.org/T145436 * Work ongoing on sending cookie with each block ticket - https://phabricator.wikimedia.org/T5233 * Upcoming: * Investigation for adding IP range support to Special:Contributions https://phabricator.wikimedia.org/T147664 * Preliminary work/investigation on throttling number of accounts created per browser: https://phabricator.wikimedia.org/T106930 === Discovery === * No blockers * Working on multiwiki indexes * Deploying BM25 for top 10 languages soon ( https://phabricator.wikimedia.org/T147008#2694395), languages like ja, zh and th still TODO * Added accent squashing for Russian/Cyrillic analyzer * Subphrase completion (completion inside phrase) enabled on mediawiki.org, wikitech and wikisources ==== Maps ==== * Launched snapshot service Is there any docs, demo, something to show to people ? ** Basic static service was described at https://github.com/kartotherian/kartotherian#static-map-images ** The new "overlay addition" to the static service added three params to specify which page and which map to draw over the image: domain=www.mediawiki.org title=Help:Extension:Kartographer groups=_925bf4f20f98fdda374476b902f702d080492748 * Discussing tabular data on Commons * If somebody has hive to Graphite setup, please talk to Yuri === Wikidata === * No blockers. * Working on a new parser function in addition to {{#property:…}}, as well as Lua support: https://phabricator.wikimedia.org/T142941 * Separate "Cognate" extension for automatic Wiktionary sitelinks pretty much done, in security review: https://phabricator.wikimedia.org/T145412 * We are going to celebrate Wikidata's fourth birthday on October 29: https://www.wikidata.org/wiki/Wikidata:Fourth_Birthday === Analytics === * Not blocking nor blocked * Update: * Recruiting fullstack dev: several tasks submitted and reviewed, some candidates passed to next steps. * Working on a KafkaSSE prototype (Kafka consumer to SSE) Kasocki's analog for SSE. * More work on removing Limn dashboards, only reportcard and ee-dashboards remaining. * Edit history reconstruction: good progress on productionization of the jobs for all wikis. * Troubleshooting varnish-kafka, causing false alarms in hadoop webrequest loading jobs. * Improved EventLogging monitoring and alarms. === Security === * Brian was out last week, but is back now * Security Reviews: * FileAnnotations (this week - done) * Google MT for Content Translation (this week) * Electron PDF-rendering service (next week) === Services === * Not blocking or blocked * Updates ** SCB is expanded to 4 machines per DC ** Node.js security update to 4.6.0 is live on SCB and RESTBase *** Please test and update your services that were not updated! ** Parsoid config deployment move to Scap3 ongoing === Technical Operations === * '''Blocked''' ** None * '''Blocking''' ** Noone * Updates ** SCB cluster capacity doubled today ** work ongoing on varnish 4 on text ** Jessie appserver reimaging ongoing, almost done ** API outage on Monday, root cause still unknown. https://phabricator.wikimedia.org/T148652 === ArchCom === * (RobLa can't be here; please follow links and comment) * https://phabricator.wikimedia.org/E323 - today's ArchCom meeting ** *T145472: Survey Cookies/Local Storage usage on Wikimedia sites* ** https://phabricator.wikimedia.org/T145472 == Fundraising Tech == * Got some help from Aaron Schultz on CN bug, would welcome more review from others familiar with MessageCache ** https://phabricator.wikimedia.org/T144952 * Brainstorming ways to monitor for recurrance of the issue * General stabilization and log-quieting tasks * Improving donor error messages

3 2

How to grow our technical community - Wikimedia Developer Summit
by Quim Gil 19 Oct '16

19 Oct '16

How to grow our technical community? This is a main topic at the upcoming Wikimedia Developer Summit (San Francisco, January 11-13, 2017). There is a call for participation open until the end of this month (October 31). Your proposals for discussions related to this main topic are welcome! There are some ideas about possible topics at https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/How_to_grow_… If you are interested in contributing to the discussions about How to grow our technical community, please join us at the Summit (the deadline to request travel sponsorship is next Monday, October 24). PLEASE ENCOURAGE OTHER PEOPLE to submit a proposal and/or join the Summit. This email will likely arrive to the core of the Wikimedia technical community, but the chances to arrive to the periphery and beyond are a lot smaller. We need your help! We want to discuss how to grow our technical community including the perspectives of those who haven't joined us yet. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

2 1

Commons problem on own MW install
by Bináris 19 Oct '16

19 Oct '16

Hi, I installed MW 1.23.15 on my laptop (running on a XAMPP). I have # InstantCommons allows wiki to use images from http://commons.wikimedia.org $wgUseInstantCommons = true; in LocalSettings.php. Content of my template is: [[Kép:Tick-green.png|20px]]<noinclude>[[Kategória:Sablonok]]</noinclude> where Kép is a legitimate alias for File in Hungarian I get a red 20px text and a tracking category for bad file instead of the image from Commons. The redlink goes to: http://localhost/w/index.php?title=Speci%C3%A1lis:Felt%C3%B6lt%C3%A9s&wpDes… (Special:Upload for those who can't fluently read urlencoded Hungarian) Thanks sfor the help. -- Bináris

5 5

Recently proposed patchsets by new contributors awaiting code review
by Andre Klapper 19 Oct '16

19 Oct '16

Your help is welcome to provide feedback (CR±1/2) and guidance: No *new* & unreviewed patches this week but: == mediawiki/extensions/LdapAuthentication: == since 2016-09-27 (3rd time listed here; it's 2 lines): Allow local user creation even if LDAP user creation is disabled https://gerrit.wikimedia.org/r/#/c/313019/ == pywikibot/core: == since 2016-09-25 (3rd time listed here): Checks the type of isbn and modifies accordingly https://gerrit.wikimedia.org/r/#/c/312726/ Thanks in advance for your reviews. Of last time's 3 listed patches, 1 got merged. Thanks to Hashar, Jonas and Thiemo! -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

1 0

Get your easy tasks for new contributors prepared! (It's GCI time again.)
by Andre Klapper 18 Oct '16

18 Oct '16

Google Code-in 2016 has been announced: A contest for 13-17 year old students. While we wait for Wikimedia to get accepted: Take those 10 minutes to find (or update) some Phabricator tasks in your project(s) that would take an experienced contributor 2-3 hours. * Do you have small, self-contained bugs you'd love to get fixed? * Does your documentation need improvements? * Does your user interface have small design issues? * Does your Outreachy/Summer of Code project welcome small tweaks? * Would you enjoy helping someone port your template to Lua? * Does your gadget use some deprecated API calls? * Do you have tasks in mind that welcome some research? We have nearly 600 open "easy" tasks listed: https://phabricator.wikimedia.org/maniphest/query/609oZQR8EpOH/#R Are the tasks in your area clear enough and still valid? And can you imagine helping a young person fix some of these tasks? * Add the project "Google-Code-in-2016" and a comment in Phabricator tasks that you would mentor those tasks. * Tasks are welcome in five areas: Code; Outreach/Research; Documentation/Training; Quality Assurance; User Interface. * Add yourself to the table of mentors on the wikipage. * Make sure the task description provides pointers to help the student. * "Beginner tasks" (e.g. "Set up Vagrant"?) also very very welcome! * "Generic" tasks also welcome (e.g. "Choose and fix 2 UI messages from the task list in https://phabricator.wikimedia.org/T40638 "). For complete info about Google Code-in, check https://www.mediawiki.org/wiki/Google_Code-in_2016#Mentors.27_corner Unsure about quality of contributions in GCI and effort? Please read https://lists.wikimedia.org/pipermail/multimedia/2015-January/001009.html Please ask if you have questions. Happy to help! See you in Google Code-in! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

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