Wikitech-l March 2016

wikitech-l@lists.wikimedia.org

109 participants
102 discussions

Re: [Wikitech-l] [Engineering] Looking for more additions to SWAT (deploy) team
by Greg Grossmeier 02 Mar '16

02 Mar '16

<quote name="Max Semenik" date="2016-03-02" time="14:25:07 -0800"> > I could do it. CI that was making me sad previously is in a much better > shape now (thanks!) so I'm in. Sweet! Thanks Max! (moving logistics offthread...) -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |

1 0

Scrum of Scrums - 2016-03-02
by Greg Grossmeier 02 Mar '16

02 Mar '16

https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-03-02 = 2016-03-02 = == Technology == === Analytics === * '''Blocking''': ** Anyone working on Hadoop, due to encoding issue, reported on the list, leaves cluster unavailable probably until Monday March 7th. * '''Blocked''': ** (nobody we know) * '''Updates''': ** Some of our JVMs started with a non-UTF8 encoding causing page title extraction to create weird characters. We're fixing by backfilling data back to February 22nd. Due to this backfilling, the cluster will be busy and so we asked people to not use it until it's caught back up. Going forward we found an environment variable that will enforce the proper file.encoding. ** The Analytics Query Service (which hosts the pageview API) is fully split up from RESTBase, so we'll be able to add features and new endpoints more easily. ** Shifting to declaratively specifying which requests are pageviews, by setting a value in the X-Analytics header. If you're writing clients that generate what should be considered a "pageview", come talk to us. === Release Engineering === * '''Blocking''': ** Upcoming security patches to be deployed * '''Blocked''': ** Ops help: https://gerrit.wikimedia.org/r/#/c/272947/ * '''Updates''': ** Rolling out wmf.15 this week ** March 21st week of: no deploy week! === Research === * '''Blocking''': ** nothing that we know of * '''Blocked''': ** none reported * '''Updates''': ** Running a quicksurvey at a rate of 1:50 to learn about our readers. The survey will stop on 2016-03-07. It's tracked in https://phabricator.wikimedia.org/T125946 and all research documentations are in https://meta.wikimedia.org/wiki/Research:Characterizing_Wikipedia_Reader_Be… === Security === * '''Blocking''': ** none? * '''Blocked''': ** ??? * '''Updates''': ** Finishing review of horizon 2fa ** Lots of security patches to deploy ** sysop password policy, hash upgrades next week === Services === * '''Blocking''': ** possibly none * '''Blocked''': ** Ops: Change propagation deployment - https://phabricator.wikimedia.org/T128463 ** Ops: Varnish caching - https://phabricator.wikimedia.org/T127387 * '''Updates''': ** Caching enabled for most endpoints, watch out for titles with special characters ** API build-out: RB realted-pages endpoint - https://phabricator.wikimedia.org/T125983 ** EventBus: resource_change event - https://phabricator.wikimedia.org/T126687 ** RB cluster expansion continuing ** Cassandra - switching to 2.1.13, soon to 2.2.5 ** rate limiting soon coming to service-runner === Technical Operations === * '''Blocking''': ** research on ORES deployment in production * '''Blocked''': ** By none * '''Updates''': ** Be aware of https://phabricator.wikimedia.org/T124356 == Product == === Discovery === * '''Blocking''': ** none * '''Blocked''': ** Security Review of SVG sanitization node lib ** Security Review of PHP Schema validator lib ** Ops: Need to figure out the plan for maps hardware * '''Updates''': ** Portal stats updated ** Portal UI improvements in code review, will be released soon ** Upgrading ES to 1.7.5 ** Working on ES tuning & logging improvements ** WDQS upgraded to BG 2.0 successfully ** Releasing Kartographer next week to Wikivoyage === Reading === ==== Web ==== * PageImages to strip non-free images given results of analysis and conclusion that impact will be low https://phabricator.wikimedia.org/T125977#2056988 * Preparing to enable stored references on Japanese Wikipedia Dependencies: Ops, Jamie Crespo. Expect it to increase db storage but hopefully no performance impacts. https://phabricator.wikimedia.org/T126802 * Working on lazy loading references and images ==== Android ==== * '''Updates''': ** Working towards a new beta with support for user options. ==== iOS ==== ==== Mobile Content Service ==== * '''Updates''': Enabling to run the service on beta cluster (http vs https) https://phabricator.wikimedia.org/T113542 * '''Blocking''': Varnish not purging RESTBase URIs https://phabricator.wikimedia.org/T127370 ==== Reading Infrastructure ==== * SessionManager seems to be pretty solidly out there. We've been working with Performance to add in-process caching in some critical places, and preparing to set MW_NO_SESSIONS for the load.php entry point as mentioned last week. * AuthManager is coming! ** No longer blocking: Mobile apps: You should be able to start testing the API changes on https://authmanager.wmflabs.org/wiki/api.php now, the API classes should hopefully be stable at this point. ** We plan to have the core patches feature complete by March 15. *** The plan is to include a temporary feature flag, and to merge it to master with the flag disabled ASAP to make testing and updating extensions easier. *** Blocked: SECURITY: We could use security review on the AuthManager core bits as soon as possible. **** Main: https://gerrit.wikimedia.org/r/#/c/195297/ (I think you've mostly already reviewed this one, should be ready except for emailing of temporary passwords) **** API: https://gerrit.wikimedia.org/r/#/c/265201/ (Should be ready for review now, except for the new module for emailing of temporary passwords) **** UI: https://gerrit.wikimedia.org/r/#/c/240052/ (Still in progress) *** Help requested: SECURITY: Double-checking that any auth-related security changes in core aren't going to be lost would also be very helpful. ** Then we will start looking at WMF-deployed extensions that need updating (and send another email to wikitech-l). *** The current list of extensions that seem to need some sort of attention is the blockers of https://phabricator.wikimedia.org/T110282; look for access to $wgAuth, AuthPlugin, or a list of hooks that will eventually be posted on that bug. Most of these we'll probably fix ourselves, but help will be appreciated if anyone is interested. **** Stuff for https://phabricator.wikimedia.org/T68699 was already removed as part of SessionManager patch. Would be good to solve that problem somehow. ***** No it wasn't. See discussion on the bug. *** Help to be requested: Mobile: We'd really appreciate your help making sure that MobileFrontend functions if the AuthManager feature flag is enabled. We think the impact will mostly be in whatever you're injecting into the login and account creation pages. *** Help to be requested: Language: The Translate extension's TranslateSandbox class is creating and even trying to delete local users, which is scary and will likely need work. **** NL: That's by design ;) Not used in WMF but in translatewiki.net. Ping me on IRC or so. *** Help to be requested: Ops/Labs?: Bryan Davis is going to talk to Andrew Bogott and Alex Monk about collaborating on testing the changes we'll have to make to LdapAuthentication and OpenStackManager on the existing infrastructure you're using for testing your OpenStackManager changes. *** FYI: Security: At least CentralAuth, LdapAuthentication, and OATHAuth will likely want security reviews as those patches are written. ** Once all the extensions are fixed and tested, then we'll talk about scheduling the feature flag being turned on. === Editing === * Wikidata would appreciate thoughts on the Multi-Content Revisions RfC at https://phabricator.wikimedia.org/T107595 so that we don't break everyone's expectations of MediaWiki :-) ==== Collaboration ==== * '''Blocking''': ** External Store - Prep work for External Store on Beta is in progress. * '''Blocked''': ** No new blockers * '''Updates''': ** Following up on cross-wiki notifications, e.g. changing how human-readable names work. ** Most Flow board move issues are fixed, working on one remaining thing. ** Temporarily disabled thank you notification due to bug ==== Language ==== * '''Blocking''': Nothing * '''Blocked''': Nope * '''Updates''': ** Next week will be slow week ==== Multimedia ==== * '''Blocking''': N/A * '''Blocked''': N/A * '''Updates''': ** Potential issues with licensing in ImageTweaks, working on it ** Wikibase for Commons repository was requested, which is exciting ** Performance improvements to UploadWizard rolling out ==== Parsing ==== * '''Blocking''': Not that I know of – From Labs: https://phabricator.wikimedia.org/T128620 * '''Blocked''': None * '''Updates''': ** Templatedata-based serialization deployed last Wednesday *** Follow ups and bug fixes in progress ** Attribute parsing in tags now uses HTML5 parsing semantics ( https://phabricator.wikimedia.org/T108134 ) -- frwikisource needed a lot of fixes for <pages from= to= .. > style tags that editors fixed with a bot. *** Parsoid-side fix went out on Monday *** core-side fix will go out with wmf15 train ** Some progress on https://phabricator.wikimedia.org/T124356 -- Kunal's logging seems to have yielded results and he pushed a fix to the MobileFrontend extension. ** Work ongoing to set up prod wiki clones on labs vms -- more involved than it should be. Required for visual diff testing to test tweaks / changes to wikitext parsing / tidy replacement / etc. ==== VisualEditor ==== * '''Blocking''': ** None known. * '''Blocked''': ** Waiting on Design Research availability for user testing of Single Edit Tab integration * '''Updates''': ** Single Edit Tab live on group0 and Hungarian Wikipedia; next up, Polish Wikipedia, then English. ** OOUI on all pages: Initial proof-of-concept code https://gerrit.wikimedia.org/r/274328 being written. Deployment will not be next week, and will be in concert with Discovery and Performance teams. === Fundraising Tech === * No blockers * preparing real donor test of backup worldwide credit card processor * Working out final details of Latin American payment processing expansion * Steady stream of CiviCRM enhancements for us and upstream * More experiments in fraud monitoring and blocking * Adam Wight and Andrew Green return from a month of work on education program tools -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |

1 0

Fwd: [Ops] Minor Phab instability
by Legoktm 02 Mar '16

02 Mar '16

-------- Forwarded Message -------- Subject: [Ops] Minor Phab instability Date: Wed, 2 Mar 2016 19:55:13 +0000 From: Chad Horohoe <chorohoe(a)wikimedia.org> To: Operations Engineers <ops(a)lists.wikimedia.org>, Development and Operations engineers (WMF only) <engineering(a)lists.wikimedia.org> Hi all, As you may have noticed lately, there's been a bit of a problem with Phabricator--mostly of the sort where it complains about not being able to connect to the m3 database. This is known, and is unfortunately a one time migration cost associated with getting the remaining Gerrit repositories indexed in Phabricator. The work should be done by the end of the week, and I'm trying to batch it as small as possible to try and limit disruption. Thanks for bearing with me! -Chad

1 0

dataset1001 (dumps.wikimedia.org) maintenance window March 2 1-4pm UTC
by Ariel Glenn WMF 02 Mar '16

02 Mar '16

Dataset1001, the host which serves dumps and other datasets to the public, as well as providing access to various datasets directly on stats100x, will be unavailable tomorrow for an upgrade to jessie. While I don't expect to need nearly 3 hours for the upgrade, better safe than sorry. In the meantime all files will be accessible via ms1001.wikimedia.org via the web, and all dumps and page view files from our mirrors as well. Thanks for your understanding. Ariel Glenn

1 2

Everything is a wiki page
by Federico Leva (Nemo) 02 Mar '16

02 Mar '16

I started https://www.mediawiki.org/wiki/Everything_is_a_wiki_page This is a very simple concept which, however, I find is often neglected. Some extension developers are conscious about what they do, but there is a lot of needless self-inflicted pain that we could do without. Nemo

2 1

[x-post] Reminder: WMF Language Office Hour today i.e. March 2nd 2016 (Wednesday) at 1400 UTC
by Runa Bhattacharjee 02 Mar '16

02 Mar '16

[x-posted announcement] Hello, A reminder that the online office hour hosted by the Wikimedia Language team is scheduled for later today at 1400 UTC. You can join the hangout or watch the session from: https://plus.google.com/u/0/events/cbn4a2gubl4m6au3jv0gllh5t0k Please note, due to the limitation of Google Hangouts there are few seats available. So do let us know on the event page, if you would like to participate on the hangout. We will also be on the IRC channel #wikimedia-office to take questions. Please see below for the event details, local time and original announcement. Thanks Runa == Details == # Event: Wikimedia Language team's office hour session # When: March 2nd, 2016 (Wednesday) at 14:00 UTC (check local time http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160302T1400) # Where: https://plus.google.com/u/0/events/cbn4a2gubl4m6au3jv0gllh5t0k and on IRC #wikimedia-office (Freenode) # Agenda: Content Translation updates and Q & A ---------- Forwarded message ---------- From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org> Date: Thu, Feb 25, 2016 at 6:12 PM Subject: WMF Language team office hour and online meeting on March 2nd 2016 (Wednesday) at 1400 UTC To: MediaWiki internationalisation <mediawiki-i18n(a)lists.wikimedia.org>, Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>, "Wikimedia & GLAM collaboration [Public]" <glam(a)lists.wikimedia.org> [x-posted announcement] Hello, The next online office hour session of the Wikimedia Language team is scheduled for next Wednesday, March 2nd 2016 at 14:00 UTC. This session is going to be an online discussion over Google Hangouts/Youtube with a simultaneous IRC conversation. Due to the limitation of Google Hangouts, only a limited number of participation slots are available. Hence, do please let us know (on the event page <https://plus.google.com/u/0/events/cbn4a2gubl4m6au3jv0gllh5t0k>) if you would like to join in the Hangout. The IRC channel #wikimedia-office and the Q&A channel for the youtube broadcast will be open for interactions during the session. Our last online round-table session was held in November 2015. You can watch the recording here: https://www.youtube.com/watch?v=eYWZ6C4N93Y Please read below for the event details, including local time and do let us know if you have any questions. Thank you Runa == Details == # Event: Wikimedia Language team's office hour session # When: March 2nd, 2016 (Wednesday) at 14:00 UTC (check local time http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160302T1400) # Where: https://plus.google.com/u/0/events/cbn4a2gubl4m6au3jv0gllh5t0k and on IRC #wikimedia-office (Freenode) # Agenda: Content Translation updates and Q & A -- Language Engineering Manager Outreach and QA Coordinator Wikimedia Foundation -- Language Engineering Manager Outreach and QA Coordinator Wikimedia Foundation

1 0

Fwd: [opensource-107] Seattle to host the 2016 OpenStreetMap State of the Map US Conference
by Pine W 02 Mar '16

02 Mar '16

(Cross-posting) For Wikimedia folks who are interested in possible collaborations with OSM, now seems like a good time to start thinking about possible presentations. Staff from the Wikimedia Foundation, and/or Wikimedia volunteers from around the US outside of the Seattle area, may want to start thinking about travel plans. For Wikimedia volunteers outside of Cascadia Wikimedians territory, you might consider applying for WMF Travel and Participation Support grants [1]. If you're inside of Cascadia Wikimedians territory and would like to attend the conference, we may have funds in our budget that can support your attendance. Contact me off-list for details. Regards, Pine [1] https://meta.wikimedia.org/wiki/Grants:TPS ---------- Forwarded message ---------- From: Clifford Snow <clifford(a)snowandsnow.us> Date: Tue, Mar 1, 2016 at 5:18 PM Subject: [opensource-107] Seattle to host the 2016 OpenStreetMap State of the Map US Conference To: opensource-107-announce(a)meetup.com I am excited to announce that Seattle was chosen to host the OpenStreetMap 2016 State of the Map US Conference. The conference will take place July 23-25 on SeattleU's campus. We chose SeattleU for their low cost, proximity to Seattle and access to public transit. The food trucks near by didn't hurt either. We are looking for help! Let us know if you want to help. Request for presentation proposals should be coming fairly soon. Start thinking about what you want to present or teach. The formal announcement can be found at: https://openstreetmap.us/2016/02/sotmus-2016/ Clifford

1 0

RfC: Notifications in core
by Legoktm 02 Mar '16

02 Mar '16

Hi, I've written an RfC about moving most of the Echo extension code into MediaWiki core: <https://www.mediawiki.org/wiki/Requests_for_comment/Notifications_in_core>. RobLa has written a summary of it on the Phab task: <https://phabricator.wikimedia.org/T128351>. Feedback is appreciated. :) -- Legoktm

2 1

Re: [Wikitech-l] [Analytics] Please provide feedback on suggested improvements to the Code of Conduct
by Matthew Flaschen 02 Mar '16

02 Mar '16

See discussion at https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Seems_to_be_a_lot… . Matt On 02/23/2016 09:37 PM, reguyla(a)gmail.com wrote: > I notice you mention in a lot of places that people should contact an > administrator. What if the person they are complaining about is an > admin? Because I have seen admins violate several of these rules of > conduct and it's rare for anything to be donecabout it. > > > Reguyla > > > Sent from my T-Mobile 4G LTE device > > > ------ Original message------ > > *From: *Matthew Flaschen > > *Date: *Tue, Feb 23, 2016 8:45 PM > > *To: *Wikitech List;Engineering List;Design List;Wiki Research > List;Analytics Public List;hackathonorganizers(a)lists.wikimedia.org > <mailto:;hackathonorganizers@lists.wikimedia.org>; > > *Subject:*[Analytics] Please provide feedback on suggested improvements > to the Code of Conduct > > > Thanks to everyone who’s helped work on the Code of Conduct sofar.Pe <http://far.Pe>ople have brought up issues they feel were missed when working on "Unacceptable behavior" (https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Unacceptable_behavior ) and "Report a problem" (https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Report_a_problem ). Consultants have also suggested changes in these samesections.Th <http://sections.Th>ese are important sections, so please take a look at the proposed changes (https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Suggested_changes). I apologize that this feedback arrived later than planned, but I think this will create a better document.If you prefer to give your opinion privately, feedback via e-mail is welcome at conduct-discussion(a)wikimedia.org.Thanks <mailto: conduct-discussion(a)wikimedia.org.Thanks>,Matt Flaschen_______________________________________________Analytics mailing listAnalytics(a)lists.wikimedia.orghtt <mai lto: listAnalytics(a)lists.wikimedia.orghtt>ps://lists.wikimedia.org/mailman/listinfo/analytics <http://lists.wikimedia.org/mailman/listinfo/analytics> >

1 0

ArchCom RFC triage on Wednesday 2016-03-02?
by Rob Lanphier 01 Mar '16

01 Mar '16

Hi folks, An ArchCom RFC triage (per <https://phabricator.wikimedia.org/T125865>) was penciled in for this past RFC meeting (<https://phabricator.wikimedia.org/E144>), but I was out for jury duty and wasn't able to make the push for this or facilitate it if we stuck with my hasty plan. I'm done now, and would be happy to accommodate assuming everyone is available and up for helping out with a triage for this coming meeting on Wednesday 2016-03-02 (<https://phabricator.wikimedia.org/E146>) The point of the triage would be to try to ensure that more RFCs have assigned shepherds on ArchCom. That, in turn, would hopefully make it more likely for an RFC to make it through the process more quickly. Instead of having to ask all of ArchCom status about a particular RFC, there would be a single ArchCom owner to check in with. Any RFC that doesn't have a shepherd is not likely to move through the process. There are always going to be several RFCs that don't have shepherds. Just submitting an RFC doesn't guarantee that an ArchCom member will think your RFC is important. Life is hard that way. Make your case! Note also: shepherd != slave. Even when an RFC has a shepherd, there's no guarantee that the RFC is a high priority for the shepherd. Certainly, the shepherd's credibility as a worthy ArchCom member is potentially damaged by foot dragging, but don't bank on being able to dump blame on the shepherd if your RFC isn't going fast enough for your taste. Thoughts? Rob

2 1

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