Wikitech-l February 2017

wikitech-l@lists.wikimedia.org

68 participants
77 discussions

CREDIT showcase Wednesday 1-March-2017
by Adam Baso 01 Mar '17

01 Mar '17

Hi! I'd like to welcome you to join us at the CREDIT showcase next week, Wednesday, 1-March-2017 at 1900 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: 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! -Adam *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 showcase open 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 March 1st at 11am PT / 2pm ET / 19:00 UTC. * *There’s more info on MediaWiki <https://www.mediawiki.org/wiki/CREDIT_showcase>, and on Etherpad <https://etherpad.wikimedia.org/p/CREDIT>, 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 <https://webchat.freenode.net/?channels=%23wikimedia-office>). 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*

1 1

Discovery Weekly Update for the week starting 2017-02-13
by Chris Koerner 28 Feb '17

28 Feb '17

Howdy, A few updates this week from across the Discovery department. == Highlights == *Annual Plan "Collab Jam" took place in the SF offices this week, where lots of conversations were had on how teams within the Foundation can work together in the next fiscal year to do cool things. * ICU Folding is now effective on all English, French, Hebrew and Greek wikis. [1] ** Note: please consider asking for this feature if you would like to enable it on a particular language. == Discussions == === Search === * The new contentmodel search keyword is now operational on commons. [0] * ICU Folding is now effective on all English, French, Hebrew and Greek wikis. [1] ** Note: please consider asking for this feature if you would like to enable it on a particular language. === Portal === * Had an issue with a bad caching of an error message which resulted in text not being displayed on the wikipedia.org page for a very short time. This will be fixed with a patch. [2] * Article statistics were updated for wikipedia.org, wikiquote.org and wikiversity.org [3] === Wikidata Query Service === * Upgraded to Blazegraph 2.1.5 RC, several bugs fixed. * POST is now enabled for WDQS queries. * Started nomination process for federation endpoints. [4] [0] https://phabricator.wikimedia.org/T156371 [1] https://phabricator.wikimedia.org/T155515 [2] https://phabricator.wikimedia.org/T158782 [3] https://phabricator.wikimedia.org/T128546 [4] https://www.wikidata.org/wiki/Wikidata:SPARQL_federation_input ---- The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as "Easy" or "Volunteer needed" in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R Yours, Chris Koerner Community Liaison - Discovery Wikimedia Foundation

1 0

OOJS-UI: label/data mechanism in "OO.ui.ComboBoxInputWidget"
by Robert Vogel 28 Feb '17

28 Feb '17

Hi everybody! I'm working on some OOJS-UI components for an extension and I've stumbled across something: The "OO.ui.ComboBoxInputWidget" allows to set an array of "OO.ui.MenuOptionWidget" objects in its "menu.items" config field. Such an item can have a "label" and a "data" field. The "data" field can be of type "object" [1]. Now, if I use a "data" field of type "object" the value of the "OO.ui.ComboBoxInputWidget" will be "[Object object]", as it tries to cast the "data" value to a string when a user selects an option item. So it looks like "OO.ui.ComboBoxInputWidget" allows only "data" of type "string" in its options. Is that correct? That would also mean that there is no "label/data" mechanism of the input field itself. If I've got the following options [ { label: "Rot", data: "red" }, { label: "Gelb", data: "yellow" }, { label: "Grün", data: "green" } ] and the user selects the option with label "Gelb" the input field shows "yellow", not "Gelb". Did I miss something? Is it possible to show a "label" to the user but retrieve the "data" (object) when calling "getValue" on such a field? [1] https://doc.wikimedia.org/oojs-ui/master/js/#!/api/OO.ui.MenuOptionWidget-c… -- Robert

2 3

Community Wishlist Survey – languages and spreading the word
by Johan Jönsson 27 Feb '17

27 Feb '17

Hi everyone, At the Dev Summit a few weeks ago, there was a number of discussions about the Community Wishlist Survey and how to make it available to Wikimedia editors. In order to make it easier to give us constructive criticism or copy our process, I've tried to write down what we did, why, solutions and problems we're aware of and what we plan to do next time: https://meta.wikimedia.org/wiki/Community_Tech/Wishlist_Survey_outreach //Johan Jönsson --

1 0

Fwd: EventStreams launch and RCStream deprecation
by Andrew Otto 27 Feb '17

27 Feb '17

Hi everyone! Wikimedia is releasing a new service: EventStreams <https://wikitech.wikimedia.org/wiki/EventStreams>[1]. This service allows us to publish arbitrary streams of JSON event data to the public. (Psssst: we’re looking for cool new uses <https://www.mediawiki.org/wiki/EventStreams/Blog_-_Call_For_Entries>[2] to put on an upcoming blog post.) Initially, the only stream available will be good ol’ RecentChanges <https://www.mediawiki.org/wiki/Manual:RCFeed>. This event stream overlaps functionality already provided by irc.wikimedia.org and RCStream <https://wikitech.wikimedia.org/wiki/RCStream>. However, this new service has advantages over these (now deprecated) services. 1. We can expose more than just RecentChanges. 2. Events are delivered over streaming HTTP (chunked transfer) instead of IRC or socket.io. This requires less client side code and fewer special routing cases on the server side. 3. Streams can be resumed from the past. By using EventSource, a disconnected client will automatically resume the stream from where it left off, as long as it resumes within one week. In the future, we would like to allow users to specify historical timestamps from which they would like to begin consuming, if this proves safe and tractable. I did say deprecated! Okay okay, we may never be able to fully deprecate irc.wikimedia.org. It’s used by too many (probably sentient by now) bots out there. We do plan to obsolete RCStream, and to turn it off in a reasonable amount of time. The deadline iiiiiis July 7th, 2017. All services that rely on RCStream should migrate to the HTTP based EventStreams service by this date. We are committed to assisting you in this transition, so let us know how we can help. Unfortunately, unlike RCStream, EventStreams does not have server side event filtering (e.g. by wiki) quite yet. How and if this should be done is still under discussion <https://phabricator.wikimedia.org/T152731>. The RecentChanges data you are used to remains the same, and is available at https://stream.wikimedia.org/v2/stream/recentchange. However, we may have something different for you, if you find it useful. We have been internally producing new Mediawiki specific events <https://github.com/wikimedia/mediawiki-event-schemas/tree/master/jsonschema…> [3] for a while now, and could expose these via EventStreams as well. Take a look at these events, and tell us what you think. Would you find them useful? How would you like to subscribe to them? Individually as separate streams, or would you like to be able to compose multiple event types into a single stream via an API? These things are all possible. I asked for a lot of feedback in the above paragraphs. Let’s try and centralize this discussion over on the mediawiki.org EventStreams talk page <https://www.mediawiki.org/wiki/Talk:EventStreams>[4]. In summary, the questions are: - What RCStream clients do you maintain, and how can we help you migrate to EventStreams? <https://www.mediawiki.org/wiki/Topic:Tkjkee2j684hkwc9> - Is server side filtering, by wiki or arbitrary event field, useful to you? <https://www.mediawiki.org/wiki/Topic:Tkjkabtyakpm967t> - Would you like to consume streams other than RecentChanges? <https://www.mediawiki.org/wiki/Topic:Tkjk4ezxb4u01a61> (Currently available events are described the event-schemas repository <https://github.com/wikimedia/mediawiki-event-schemas/tree/master/jsonschema…> .) Thanks! - Andrew Otto [1] https://wikitech.wikimedia.org/wiki/EventStreams [2] https://www.mediawiki.org/wiki/EventStreams/Blog_-_Call_For_Entries [3] https://github.com/wikimedia/mediawiki-event-schemas/tree/master/jsonschema… [4] https://www.mediawiki.org/wiki/Talk:EventStreams

4 4

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

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