On Tue, Mar 1, 2016 at 3:36 PM, David Strine <dstrine(a)wikimedia.org> wrote:
> We will be holding this brownbag in 25 minutes. The Bluejeans link has
I'm not familiar with bluejeans and maybe have missed a transition
because I wasn't paying enough attention. is this some kind of
experiment? have all meetings transitioned to this service?
anyway, my immediate question at the moment is how do you join without
sharing your microphone and camera?
am I correct thinking that this is an entirely proprietary stack
that's neither gratis nor libre and has no on-premise (not cloud)
hosting option? are we paying for this?
I've been meaning to document this for a while.
If you're finding yourself visiting Special:Export/Import often for the
purpose of MediaWiki development there is a much better way to get content
into your local wiki for testing purposes.
This short video explains how MobileFrontend extension provides tooling to
help you debug live on-wiki content via $wgMFContentProviderClass 
Hope it saves someone lots of time!
Senior Software Engineer
In the next couple weeks I'm planning to start switching our video
transcode output from WebM VP8/Vorbis to the newer WebM VP9/Opus profile,
which saves us about 38% on file size and bandwidth while retaining the
This will not affect what kinds of files you upload; only the scaled
transcoded output files used for playback will change. All modern browsers
that support VP8 support VP9 as well, and our player shim for Safari and IE
will continue to work.
All the details:
Comments and questions welcome!
Following the recent outage, we've had a new series of complaints
about the lack of improvements in CX, especially related to
server-side activities like saving/publishing pages.
Now, I know the team is involved in a long-term effort to merge the
editor with the VE, but is there an end in sight for that effort? Can
I tell people who ask "look, 6 more months then we'll have a much
better translation tool"?
Is there a publicly available roadmap for this project and more
generally, for CX?
Since June 27th, any CI job running 'npm install' might suffer from a 10
minutes extra delay.
Somehow when requesting package informations from the NpmJS CDN
(CloudFlare), the connection holds for ten minutes. npm just idles
waiting for a reply. Then eventually it shows:
npm ERR! registry error parsing json
npm then retry and process as usual.
The json error is due to a CloudFlare HTML page stating:
The page could not be rendered due to a temporary fault.
The impact is any Jenkins job using npm have a high chance of taking 10
more minutes to build. That notably impacts MediaWiki core and all its
A few minutes ago, I have made a change to run npm with --loglevel=info
which would give some hints about what it is doing by causing npm to
emit more informations in the console. (verbose would be way too much
I have filled a bug to npm: https://github.com/npm/npm/issues/21101
Our task: https://phabricator.wikimedia.org/T198348
I have no idea how to mitigate the issue :-(
Antoine "hashar" Musso
a quick reminder: The deadline for nominations for the Wikimedia Technical
Conference (Portland, USA, October 22-25, 2018) is tomorrow, *Thursday June
14, 2018. *So if you are a volunteer (or staff member) and think you (or
the person you nominate) might be able to provide valuable feedback for the
program, please use this form: https://goo.gl/forms/MKF682BE1OVI0pe63 to
nominate yourself or someone else.
You can find more information on the nomination process in the FAQ:
If you haven't heard about the conference at all by now, please see:
https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2018 for more
Questions are very welcome on the talk page there:
Thanks to everyone who already has taken the time to nominate someone -
your support is much appreciated :-)
The Wikimedia Technical Conference Team
2018-06-02 1:36 GMT+02:00 Rachel Farrand <rfarrand(a)wikimedia.org>:
> As per the email below we are now opening up the nomination process for the
> Wikimedia Technical Conference (WMTechConf), to be held in Portland, OR,
> USA on October 22-25, 2018.
> *Please fill out the survey using this link to nominate yourself or someone
> else to attend: *https://goo.gl/forms/MKF682BE1OVI0pe63 This nomination
> form will remain open between June 1 and June 14, 2018.
> This survey is conducted via a third-party service, which may make it
> subject to additional terms. For more information on privacy and
> data-handling, see this survey privacy statement: https://
> *If you have any questions, please post them on the event's talk page
> The Wikimedia Technical Conference Team
> On Mon, May 21, 2018 at 3:47 PM, Deborah Tankersley <
> dtankersley(a)wikimedia.org> wrote:
> > *Hello,We recently announced the new Wikimedia Technical Conference
> > (TechConf) during the closing session of the Barcelona Hackathon on May
> > 2018. We are sending this email to give an update on the planning and
> > organization, and to also let everyone know how the nomination process
> > work for those interested in attending. The Wikimedia Technical
> > will take place in Portland, OR, USA on October 22-25, 2018. And, as
> > mentioned in previous emails  and on the wiki page , this
> > conference will be focused on the cross-departmental program called
> > Platform Evolution. We will be providing more information and context as
> > go along in the process.For this conference, we are looking for diverse
> > stakeholders, perspectives, and experiences that will help us to make
> > informed decisions for the future evolution of the platform. We need
> > who can create and architect solutions, as well as those who actually
> > decisions on funding and prioritization for the projects.Later this week,
> > we will send out a form to provide more detailed information on the
> > nomination process and how to nominate people (or it can be yourself) to
> > attend this conference, along with the skills, experiences, and/or
> > backgrounds that we are looking for. Due to the time needed for visa
> > application and other constraints, the deadline for nominations will be
> > June 8th. Please make sure that you don’t miss the deadline!If you have
> > questions, please post them on the talk page 
> > https://lists.wikimedia.org/pipermail/mediawiki-l/2018-April/047367.html
> > <https://lists.wikimedia.org/pipermail/mediawiki-l/2018-
> >  https://lists.wikimedia.org/pipermail/wikitech-l/2018-
> > April/089738.html
> > <https://lists.wikimedia.org/pipermail/wikitech-l/2018-April/089738.html
> >  https://mediawiki.org/wiki/Wikimedia_Technical_Conference/2018
> > <https://mediawiki.org/wiki/Wikimedia_Technical_Conference/2018> 
> > https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018
> > <https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018
> > *
> > *Cheers from the Program Committee:*
> > *Kate, Corey, Joaquin, Greg, Birgit and TheDJ*
> > --
> > deb tankersley
> > Program Manager, Engineering
> > Wikimedia Foundation
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> Rachel Farrand
> Events Program Manager
> Technical Collaboration Team
> Wikimedia Foundation
> Wikitech-l mailing list
Community Communications Manager
Software Development and Engineering
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Greetings. I would like to describe an exciting scenario possible with OpenID Connect.
In the scenario, after choosing to verify their name on their Wikipedia account, a user logs onto Wikipedia and uses OpenID Connect to link their Wikipedia account to multiple verified accounts, for example their Facebook and LinkedIn accounts. At the end of the process, we can envision the user obtaining a checkmark next to their full name on Wikipedia, their real name and a verification icon appearing next to their edits and on their user page. There might even be, per user settings, hyperlinks to their Facebook and LinkedIn pages on their Wikipedia user page. With such features, we can envision allowing groups of users or admins to determine that certain articles require a verified account to edit.
Presently, OpenID Connect functionality is available for MediaWiki as an extension. I would like to see the OpenID Connect functionality under discussion expanded to support scenarios including aforementioned and also integrated into MediaWiki.
Thank you. I hope that the above ideas are also interesting to you in the Wikitech-l community.