In order to improve browser testing tools, release engineering team has
created browser testing user satisfaction survey:
It should take you up to 5 minutes. Most of the questions have simple 5
level linear scale. There are 5 sections, and the last question in each
section will be free form text field, so you can leave comments on anything
we forgot to ask.
For details about the survey, feel free to take a look at phabricator task:
I would like to draw your attention to ticket
This ticket highlights some issues with the way sections, headers and the
TOC are handled in the parser in combination with tag extensions and parser
Basically the problem is that the TOC is created before strip markers are
substituted, which prevents some sections from showing up in the TOC.
This issue is limiting the usefulness of such constructs, so I am very
interested to spend some time on it with people well-versed in the parser
code and in particular the formatHeadings function.
Of course, there are plenty more details I could give but before flooding
wikitech-l with those I thought I'd poll for the interest in addressing
this. Maybe the next step could be some chat over IRC or another medium?
Thanks in advance,
This is an inquiry from my friend in academia, researching about Wikipedia.
He would like to know whether there's a way to acquire a list of templates
including external links. Here are some examples including external links.
Such links are stored in externallinks.sql.gz, in an expanded form.
When you want to check increase/decrease of linked domains in chronological
order through edit history, you have to check pages-meta-history1.xml etc.
In a such case, traditional links and links by templates are mixed,
Therefore, the latter ones (links by templates) should be expanded to
traditional link forms.
Sorry if what I am saying does not make sense.
Thanks in advance,
--Takashi Ota [[U:Takot]]
tl;dr: WMF Continuous Integration will have downtime on Tuesday August
2nd starting at about 16:00 UTC due to a WMF Labs infrastructure
upgrade. Don't expect Jenkins to report test failure/passing on your
changes during this time.
Apologies for the disruption,
Greg on behalf of the Release Engineering team
----- Forwarded message from Andrew Bogott <abogott(a)wikimedia.org> -----
> Date: Mon, 25 Jul 2016 11:57:15 -0500
> From: Andrew Bogott <abogott(a)wikimedia.org>
> To: labs-announce(a)lists.wikimedia.org, Release Engineering <releng(a)lists.wikimedia.org>, Operations Engineers <ops(a)lists.wikimedia.org>
> Subject: [RelEng] Labs Openstack upgrade next Tuesday, 2016-08-02, 16:00 UTC
> Reply-To: andrewbogott(a)gmail.com
> I'm going to upgrade our Openstack install from version 'Kilo' to
> version 'Liberty' next Tuesday. I've scheduled a 3-hour window for the
> process, although noticeable service interruptions should be shorter.
> Here's what to expect:
> - Tools services and existing Labs uses should be unaffected apart from
> brief ( < 1 minute) interruptions in network service.
> - Continuous Integration tests (Jenkins, Zuul, etc.) will be disabled for
> most of the upgrade window.
> - Creation/Deletion of new instances will be disabled for most of the
> - Wikitech and Horizon may error out occasionally and/or display
> inconsistent information. Users may need to refresh their web logins after
> the upgrade.
> Apart from fixing a few seldom-seen bugs, this upgrade shouldn't result in
> noticeable changes for Labs users. It will lay the groundwork for an
> upcoming Horizon upgrade, but that will be announced in a future email.
> RelEng mailing list
----- End forwarded message -----
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |