FYI: tomorrow much of our CI tests will not run due to a planned
Wikimedia Cloud reboot.
Sorry for the inconvenience.
----- Forwarded message from Andrew Bogott <abogott(a)wikimedia.org> -----
> Date: Tue, 27 Mar 2018 09:34:55 -0500
> From: Andrew Bogott <abogott(a)wikimedia.org>
> To: Cloud-announce(a)lists.wikimedia.org
> Subject: [Cloud] [Cloud-announce] Brief service interruption tomorrow 2018-03-28 at 15:00 UTC
> Reply-To: cloud(a)lists.wikimedia.org
> About 24 hours from now we're going to reboot a couple of servers in the
> cloud infrastructure to apply security updates.
> Few WMCS users (and, in particular, no tools users) should notice any
> interruption. Nonetheless, a few services will be down:
> - New instance creation will fail
> - CI tests will stop running
> - Horizon and Wikitech may display incorrect or missing information
> Apologies in advance for any inconvenience!
>  labservices1001 and labcontrol1001
> Wikimedia Cloud Services announce mailing list
> Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
> Wikimedia Cloud Services mailing list
> Cloud(a)lists.wikimedia.org (formerly labs-l(a)lists.wikimedia.org)
----- End forwarded message -----
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
Hope to see you there!
Michi (for WMDE’s tech team)
Michael F. Schönitzer
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.
Forwarding to Wikitech-l for the benefit of Wikitech-l subscribers who do
not subscribe to Wikimedia-l.
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ----------
From: Gregory Varnum <gvarnum(a)wikimedia.org>
Date: Fri, Mar 16, 2018 at 6:57 PM
Subject: [Wikimedia-l] Notification about problem identified with a recent
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
On 14 March and 15 March 2018, a CentralNotice banner appeared to some
logged-out users viewing English Wikipedia pages. The banner contained
data from those who visited a page with a banner. The banner was prepared
by the Wikimedia Foundation. The Foundation turned the banner off as soon
as we learned how the script was running, and its potential scope. We have
also removed all references to the code in question from CentralNotice on
The code utilized in this banner was based on an unused prototype created
by an outside vendor. Because the prototype was never enabled, the vendor’s
prototype code was not subjected to our standard quality assurance process.
However, we made the mistake of reusing the code for a different purpose,
and implementing it based on recommendations in documentation from Twitter
and Facebook to improve the appearance of shared links. At the time, our
understanding was that the platforms would only receive traffic data if the
user clicked on the link. Although this was true for Twitter, the Facebook
code operated differently.
We discovered the problematic link configurations during our ongoing
monitoring of live banners. The recommended code enhanced not only the
appearance of links, it also enhanced Facebook's ability to collect
information on people visiting non-Facebook sites. As soon as we realized
these banners were sharing information without even having to click the
link, we disabled them and began an investigation. Staff in multiple
departments are collaboratively reviewing the incident as well as
procedural and technical improvements to prevent future incidents.
While this sort of tracking is commonplace today across most of the
internet, it is not consistent with our policies. We are disappointed that
this type of hidden data collection is routinely recommended by major
platforms, without clearer disclosure.
These practices are why we all must regularly take routine steps to
maintain a secure computer and account. As the Wikimedia Foundation
continues to explore ways we can do that within Wikimedia's platform, we
encourage you to consider tools which block unwanted third-party scripts
like the one provided by Facebook.
We apologize for sending this late on a Friday (San Francisco time).
However, we wanted to provide this information as quickly as possible.
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
New messages to: Wikimedia-l(a)lists.wikimedia.org
TL;DR see <https://phabricator.wikimedia.org/T179461> for a proposed
I proposed in Phabricator a wile ago  that we adopt the term
"Wikimedia developer account" across our wikis and other documentation
for the LDAP-backed user accounts that are created using
These same sign-on credentials are used for:
* Phabricator (optionally)
* ssh-based "shell access" to Toolforge and Cloud VPS servers
* a variety of web services providing access to operational and
analytics data related to the Wikimedia services
There are plans  in various stages of progress to change things
about how developer accounts are created and managed. Breaking
assumptions in our documentation about the back-end storage system
(LDAP) and the front-end management interface (wikitech) will help
make these changes less disruptive. It also helps remove another
lingering "labs" reference that the Cloud Services rebranding efforts
have been trying to address.
This change probably has almost no impact on existing technical
community members. It is really just targeted at making things a bit
less confusing for newcomers.
If you have thoughts or concerns about this proposal, please describe
them on the Phabricator task . I'm proposing that on or about March
23rd (4 weeks from the date of this message) the comments on the task
will be evaluated for consensus and an approve/deny decision.
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Manager, Cloud Services Boise, ID USA
irc: bd808 v:415.839.6885 x6855
We are releasing the next version of the Parsoid deb and npm packages
(v0.9.0) later today. There is one significant change in this release
that might affect some VisualEditor installations. This version of
Parsoid wraps sections in <section> tags and bumps the HTML version to
1.6.1. However, VisualEditor installations older than Dec 12, 2017 are
not compatible with this section wrapped output.
In order to prevent silent failures, Parsoid will do a hard fail and
reject parse requests with a HTTP 406 when it receives a version string
smaller than 1.6.0 (which VE before Dec 12, 2017 would issue). VE will
then popup the following error: "Error loading data from server:
apierror-visualeditor-docserver-http: HTTP 406. Would you like to
retry?" Retries won't help in this scenario.
Knowing this, you have a couple of options:
* Not upgrade Parsoid. If you upgrade Parsoid without reading this
notice and later stumble on this (which we'll also add to the
Parsoid releases page), you have the option of downgrading your
Parsoid install by downloading an older deb package from
* If you choose to upgrade Parsoid and your VE installation is from
before Dec 12, 2017 (which is probably most of you), the recommended
solution is to upgrade your VisualEditor installation as well.
If for some reason you really really need to upgrade Parsoid but cannot
upgrade VisualEditor, contact us on IRC in #mediawiki-parsoid to ask us
how you can do that.
(on behalf of Parsoid developers).
I'm excited to announce that we've released OOUI v0.26.0 today. It
will be in MediaWiki core from 1.31.0-wmf.26, which will be deployed
to Wikimedia production in the regular train, starting on Tuesday 27
In this breaking release email I would like to begin with pointing out
two “normal” changes with visible user-interface amendments:
- The Design team at the Wikimedia Foundation has established new icon
guidelines over the course of recent months – resulting in a new set
which is part of this release. The set features improved universality,
consistency, neutrality, developer-friendliness and RTL language
- We took the chance of integrating those icons by also unifying
VisualEditor interface on same base size as all other Vector/OOUI
interfaces already had in place. While this leads to a minimal
increase of space (f.e. 2px in height) for the toolbar items, it
reduces and optimizes the interface in all existing OOUI-based
Special:Pages and extensions.
As there are seven breaking changes in this release, at least
nominally, please carefully consider if they affect your code:
* icons: Remove 'alignCentre', renamed in v0.24.2
* icons: Remove 'arrowLast', deprecated since v0.25.0
* icons: Remove 'bellOn', deprecated in v0.25.0
* icons: Remove 'quotesAdd', deprecated in v0.24.4
* icons: Remove 'redirect', renamed in v0.24.4
* indicators: Remove 'next' and 'previous', deprecated in v0.25.0
All six changes above have been deprecated and announced in former
versions. With this release we've removed them completely.
* WikimediaUI theme: Unify available variants across icon packs
This could affect 'wikimedia' pack users with icons set to
'progressive'. Due to branding guideline reasons we need to remove
this color variation We are not aware of any such use case in
production, nonetheless mark it breaking.
Please update your icon pack references accordingly in case you're
using one of those icons or variants.
Additional details on 12 new features, 53 code-level and accessibility
changes, 18 styling and interaction design amendments, and all
improvements since v0.25.0 are in the full changelog. If you have
any further queries or need help dealing with breaking changes, please
let me know.
As always, library documentation is available on mediawiki.org, and
there is comprehensive generated code-level documentation and
interactive demos hosted on doc.wikimedia.org.
 - https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
 - https://www.mediawiki.org/wiki/OOUI
 - https://doc.wikimedia.org/oojs-ui/master/
Senior UX Engineer
volker.e(a)wikimedia.org | @Volker_E