Wikitech-l February 2017

wikitech-l@lists.wikimedia.org

68 participants
72 discussions

SHA-1 hash officially broken
by Brion Vibber 26 Feb '17

26 Feb '17

Google security have announced that they have a working collision attack against the SHA-1 hash: https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html It's highly recommended to move to sha-256 where doable. Note that MediaWiki uses sha-1 in a number of places; in some such as revision hashes it's advisory for tools only, but in other places like deleted files (filearchive table) we use it for addressing, and should consider steps to mitigate attacks swapping in alternate files during deletion/undeletion. -- brion

5 8

Applications for WikiCite 2017 (Vienna, May 23-25, 2017) close in 5 days
by Dario Taraborelli 23 Feb '17

23 Feb '17

A reminder that applications to attend WikiCite 2017 <https://meta.wikimedia.org/wiki/WikiCite_2017> close on *February 27, 2017* . Please consider applying <https://docs.google.com/forms/d/e/1FAIpQLScWnCLfAt88cUWKSu_E-lU8m3te_r4P3ng…> if you work on sources and citations (or related tools) in Wikipedia, Wikidata, Wikisource or other Wikimedia projects. If there are other people in your network we should consider inviting to the event, please let us know. You can contact the organizing committee at: wikicite(a)wikimedia.org. Best, Dario -- on behalf of the organizers On Thu, Feb 9, 2017 at 3:44 PM, Dario Taraborelli < dtaraborelli(a)wikimedia.org> wrote: > Dear all, > > I am happy to announce that applications to attend WikiCite ‘17 officially open > today <https://goo.gl/forms/Kb9Wl6Xfw2EmFqEr2>. > > About the event > > WikiCite 2017 <https://meta.wikimedia.org/wiki/WikiCite_2017> is a 3-day > conference, summit and hack day to be hosted in Vienna, Austria, on May > 23-25, 2017. It expands on efforts started last year at WikiCite 2016 > <https://meta.wikimedia.org/wiki/WikiCite_2016/Report> to design a > central bibliographic repository, as well as tools and strategies to > improve information quality and verifiability in Wikimedia projects. > > Our goal is to bring together Wikimedia contributors, data modelers, > information and library science experts, software engineers, designers and > academic researchers who have experience working with Wikipedia's citations > and bibliographic data. > > WikiCite 2017 will be a venue to: > > - > > Day 1. (Conference) – present progress on existing work and > initiatives for citations and bibliographic data across Wikimedia projects > - > > Day 2. (Summit) – discuss technical, social, outreach and policy > directions > - > > Day 3. (Hack) – get together to build, based on new ideas and > applications > > > > More information on the event can be found here > <https://meta.wikimedia.org/wiki/WikiCite_2017>: > > How to apply > > Participation for this year's event is limited to 100 individuals. In > order to be considered for participation, please fill out the following > form <https://goo.gl/forms/Kb9Wl6Xfw2EmFqEr2> and provide us with some > information about yourself, your interests, and expected contribution. > PLEASE NOTE THIS IS NOT THE FINAL REGISTRATION FORM. Your application will > be reviewed and the organizing committee will extend an invitation by March > 10, 2017. This application form is to determine the best mix of > attendees. Not everyone who applies will receive an invitation, but there > will be a waitlist. > > Important dates > > > - > > February 9, 2017: applications open > - > > February 27, 2017: applications close, waitlist opens > - > > March 10, 2017: all final notifications of acceptance are issued, > waitlist processing begins > - > > March 31, 2017: attendee list is finalized > > > Travel support > > > Like last year, limited funding to cover travel costs of prospective > participants will be available. Requests for travel support should be > submitted via the application form > <https://goo.gl/forms/Kb9Wl6Xfw2EmFqEr2>. We will confirm by March 10, if > we can provide you with travel support. > > Contact > > For any question, you can contact the organizing committee via: > wikicite(a)wikimedia.org > > We look forward to seeing you in Vienna! > > The WikiCite 2017 organizing committee > > Dario Taraborelli > > Jonathan Dugan > > Lydia Pintscher > > Daniel Mietchen > > Cameron Neylon > > > > *Dario Taraborelli *Director, Head of Research, Wikimedia Foundation > wikimediafoundation.org • nitens.org • @readermeter > <http://twitter.com/readermeter> > -- *Dario Taraborelli *Director, Head of Research, Wikimedia Foundation wikimediafoundation.org • nitens.org • @readermeter <http://twitter.com/readermeter>

1 0

Error when using OOjs UI/Windows/Message Dialogs
by Shanika Ediriweera 23 Feb '17

23 Feb '17

Hi, I am working on a phabricator task and I need to use OOjs UI/Windows/Message Dialogs ( https://www.mediawiki.org/wiki/OOjs_UI/Windows/Message_Dialogs) for a user warning. But TypeError: OO.ui.MessageDialog is not a constructor error occurs when I use: var messageDialog = new OO.ui.MessageDialog();TypeError: OO.ui.MessageDialog is not a constructor What might be the problem? Best Regards, Shanika Ediriweera Undergraduate Dept. of Computer Science & Eng. University of Moratuwa

2 5

Integrating Parsoid & RESTbase into a secure MediaWiki Install
by John P. New 22 Feb '17

22 Feb '17

Thanks to a couple of members of this list I was able to get Visual Editor working on my WikiMedia install. Now I would like to run the wiki under SSL. Of course, as soon as I do, my browser complains of mixed content from the RESTbase server and won't load VE at all. I am running MediaWiki 1.28 on a shared host, which means no access to node.js. So in order to run Parsoid and RESTbase I have installed both on my home server. As such, I have no way of getting a trusted SSL certificate for it; the most I could do is a self-signed certificate, which I am sure will cause as many browser complaints as the current mixed-content does. My question is, what is the likelihood of getting this configuration to work under SSL? John

3 4

www.wikipedia.org portal incident report 2017-02-22
by Jan Drewniak 22 Feb '17

22 Feb '17

Hello, There was a severe bug with the page www.wikipedia.org for about an hour today. Starting at about 6pm UTC and ending at 7:20 UTC, the text on that page was invisible. This was due to an improperly cached javascript file (which pointed to a 404). The URL of the file was purged and the page was fixed, but some steps will be taken to prevent this in the future. Full report is available at https://wikitech.wikimedia.org/wiki/Incident_documentation/20170222-www-por… but I'll paste it below anyway: ======== Summary ------------- At about 5pm UTC Feb. 22 the www.wikipedia.org page was severely broken for about an hour. The text on the page was invisible. This bug was caused by a javascript file being improperly cached and returning a 404. Timeline ----------- - A bug was filed at around 5:09pm UTC Feb.22 noting that the text on www.wikipedia.org is invisible. T158782 - We were made aware of this bug at about 5:40pm UTC - at 6:15pm UTC an attempt was made to rollback to the previous deploy. The deploy was visible on mwdebug1002 without error, but the error persisted in production. - at 6:20pm UTC we purged the URL of the specific javascript file, fixing the issue. Conclusions ----------------- - The wikipedia.org portal depends on a specific order of syncing followed by purging urls, which is fragile and needs some rethinking. - Errors in javascipt should not make the page unusable. Actionables --------------- Adding an entire list of asset URLs to purge (Task T158810) Preventing javascript from hiding page content indefinitetly (Task T158809) Use query params for cache-busting (Task T158808) ======== Jan Drewniak UX Engineer, Discovery Wikimedia Foundation

1 0

2017-02-22 Scrum of Scrums meeting notes
by Grace Gellerman 22 Feb '17

22 Feb '17

https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-02-22 == Call outs == *Community Tech: Need feedback on proposed table for range contributions https://phabricator.wikimedia.org/T156318 * Community Tech: Collation version numbering patch needs review https://gerrit.wikimedia.org/r/#/c/272419/ (blocks https://phabricator.wikimedia.org/T47611 ) * Services: RFC Discussion *REST API language variant support - * https://phabricator.wikimedia.org/T154190 * Language: Blocked on mysterious Qunit test failures: https://phabricator.wikimedia.org/T153038 (RelEng/Wikidata?)and schema changes review from DBA: https://phabricator.wikimedia.org/T146450 = 2017-02-22 = == Product == === Reading === ====Android==== * Last week: ** 2.5.189 beta released; production release is pending community feedback on Wikidata description editing ** Mapbox library upgrade in review ** Android Support Library upgraded * Next week (https://phabricator.wikimedia.org/project/view/2352/ ): ** Continue improving the offline experience ==== Web ==== * Current sprint: https://phabricator.wikimedia.org/tag/reading-web-sprint-92-%F0%9F%8D%9C/ * Last week: ** Page Previews: Use bundler to generate Page Previews JavaScript code - T156333 ** Create reading depth schema - T155639 * This week: ** Update related pages schema to allow for current A/B test - T157375 ** Page previews: use RESTBase in stage 0 wikis (italian, russian, greek, catalan, hebrew) - T158221 ** Deploy new mobile header to Catalan and Italian wikipedias - T156794 ** [Spike] Propose solutions for the issues identified with developing on MobileFrontend - T156263 ==== iOS native app ==== * Last Week ** Continued work on 5.4 https://phabricator.wikimedia.org/project/view/2326/ *** Location permission changes (friendlier prompt, users to opt-in instead of an intrusive pop-up) *** Closer evaluation of Mapbox & maps.wikimedia.org as tileserver *** Other bug fixes and enhancements * This week ** Continue work on 5.4 *** Finish location permission changes, add links to places map from Articles, Accessibility audit *** Other bug fixes and enhancements ====Reading Infrastructure==== * Mobile Content Service: Kanban Board: https://phabricator.wikimedia.org/project/view/2445/ ** Adding more tests for OnThisDay; removing French from it since not all dates produce a result ** Next: expanding TFA (today's featured article) to more languages using FeaturedFeed extension * working on TemplateStyles, ORES, MediaWiki logging ** TemplateStyles RfC: https://phabricator.wikimedia.org/T155813 - performance questions still open + waiting for community consultation to wrap up ==== Analytics ==== * Vetting wmf_last_access_global (project-wide unique devices) metric * Applying feedback received from community to Wikistats2.0 and finalizing visuals * Upgrade to CDH 5.10 to labs, went well, real production deploy scheduled for next tuesday 28th Feb * In progress: fixing a bug in AQS (Pageview API) related to the way dates are represented in the results ==== Community Tech ===== * Cookie blocks should go out this week https://phabricator.wikimedia.org/T158129 * Investigating global gadgets https://phabricator.wikimedia.org/T153332 * Some improvements to PageAssessments https://phabricator.wikimedia.org/T158245 https://phabricator.wikimedia.org/T154216 * Need feedback on proposed table for range contributions https://phabricator.wikimedia.org/T156318 === Discovery === * No blockers * A/B test for for sister wiki results finished, processing the results. * Working on ES5 upgrade & wikidata search * Working on annual plan & Collab Jam slides === Security=== Reviews: - 3D extension - Internal File Server - CollaborationKit - StopForumSpam === Services === * Blockers: None * Updates: ** DNS caching in service-runner by default *** https://phabricator.wikimedia.org/T158338 ** REST API 1.0 *** https://github.com/wikimedia/restbase/pull/764 ** *Language variant RFC* wrapping up right after this meeting *** https://phabricator.wikimedia.org/T122942 === Editing === ==== Language ==== * Current Sprint: https://phabricator.wikimedia.org/tag/language-2017_sprint_3/ * Compact Language Links deployed in 'svwiki'. * CX migration to OOJS continue. ==== Collaboration ==== * Blocked * Blocking * Updates ** New RecentChanges page - Bug fixes and refactoring ** Flow - Minor technical debt and upgrading pimple (should have no user impact) ** Will deploy an update ot the Flow export/import scripts that allow transwiki within the farm. We'll use this shortly (probably today) to transwiki a board fromMeta to MediaWiki.org == German Technical Wishlist == * TwoColConflict is officially in Beta, watching for feedback. * Working on FileImporter/Exporter to transfer files to Commons https://gerrit.wikimedia.org/r/#/projects/mediawiki/extensions/FileImporter… == Wikidata == * Same as last week, making good progress on Lexeme datatype for Wiktionary, as well as federation for Commons. * Will check if https://phabricator.wikimedia.org/T153038 is Wikidata related. ==== UI Standardization ==== * This week ** Work on the technical fundament of style guide (responsive layout, grid, navigation) * Updates ** General *** ContentTranslation: Сontribution's dropdown menu features non-standard layout. https://phabricator.wikimedia.org/T157217 *** Further work on: Replace abandoned colors in current WMF/Wikimedia products with WikimediaUI palette colors https://phabricator.wikimedia.org/T148708 ** OOjs UI: *** Figure out which parts of OOjs UI documentation should be improved, and where they should live - https://phabricator.wikimedia.org/T158494 *** Further improvements on form layouts in OOUI MW core forms for better user experience – https://phabricator.wikimedia.org/T136790 *** Align SelectfileInputWidget to color palette === Technical Operations === * '''Blocked''': ** None * '''Blocking''': ** None * Updates: ** Work continues on Ubuntu Precise deprecation, production and labs ** Budgeting Capex / Opex and annual plan ** Datacenter switchover ** Asia datacenter preparation === Release Engineering === * '''Blocked''': ** None * '''Blocking''': ** https://phabricator.wikimedia.org/T153038 === Fundraising Tech === * Hiring replacement for Casey, who's turning devops * More work on new PayPal integration: https://phabricator.wikimedia.org/T107372, https://phabricator.wikimedia.org/T153720 * Method to purge CentralNotice banners from caches: https://phabricator.wikimedia.org/T154954 * Investigating slow banner saves: https://phabricator.wikimedia.org/T158084 ** Andrew Green may ask ops for some help with both of the above ^^^ * More work resolving contact de-duplication conflicts in CiviCRM

1 0

(Belated) ArchCom meeting notes 2017-02-15
by Gabriel Wicke 21 Feb '17

21 Feb '17

Hi, here is a brief summary from last week's ArchCom meeting. Apologies for the delay. Internal discussions - Internal plans for cleaning up a provisional ArchCom charter. - How we manage the RfC board. RFC activity - Entering Final Comment Period: T122942: Support language variants in the REST API <https://phabricator.wikimedia.org/T122942> - Consensus has formed around using Accept-Language headers for now, leaving path prefixes as a future addition. - Based on the discussion on the task, the ArchCom will either make a decision or allow for more discussion in its meeting on Wednesday, February 22nd. - T66214: Define an official thumb API <https://phabricator.wikimedia.org/T66214>: Needs an update to the summary to reflect the recent discussion, should be ready for last call then. -- Gabriel Wicke Principal Engineer, Wikimedia Foundation

2 3

VisualEditor discards changes made in Wikitext editor
by John P. New 21 Feb '17

21 Feb '17

I've set up MW 1.28 with VE/parsoid and everything is working well However, when I edit in (any) wikitext editor and try to switch to VE, I am presented with a dialog with only 2 choices: "Cancel" or "Discard my changes and switch". Diving into the code I found I could change ve.init.MWVESwitchConfirmDialog.js (line 58) from modes: [ 'restbase' ] to modes: [ 'restbase', 'simple' ] that adds "Switch" to the dialog box, but when this option is chosen, any changes made in the wikitext editor are lost. Is this a mis-configuration on my part or is switching from edited wikitext to VE not supported? Do I need a RESTbase server to implement this functionality?

3 4

[T62399] Possible alert message to show
by Shanika Ediriweera 21 Feb '17

21 Feb '17

Hi, I am working on the task "When moving, warn if people try to move to Foo:Foo:Bar (repeated namespace)" - https://phabricator.wikimedia.org/T62399 . What would be a good alert message for the users when there is repeated namespace in title? Thank you. Best Regards, Shanika Ediriweera Undergraduate Dept. of Computer Science & Eng. University of Moratuwa

2 2

IRC: wm-bot logs temporary outage
by Petr Bena 19 Feb '17

19 Feb '17

Hi folks, Just letting you know that wm-bot logs will not be available for a day or two, reason is required migration to different OS as current OS is no longer accepted on wikimedia labs and all instances that are running it have to be terminated. If you want to track progress see https://phabricator.wikimedia.org/T157838 Bot is already up and running on new Debian instance and new logs are being collected, but the web server and web scripts are still not fully operational, we need to migrate about 3GB of text log files from IRC channels and also postgre DB which has similar size (not sure how to do that on-line, probably not even possible). Having say that, there may be some more outages because of postgre server switch, but they shouldn't be so much visible. Sorry for turbulences and thank you for your patience

1 0

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 February 2017