As announced in April[0], we are replacing Selenium tests written in Ruby
with tests in Node.js. Now is the last responsible moment to make the move.
There will be two more reminders, in September and October. In the
meantime, only critical problems will be resolved in the Ruby stack. After
October we will no longer maintain it. You can follow task T139740[1] for
more information. Extensive documentation is available at mediawiki.org[2].
If you need help with the migration, I am available for pairing and code
review (zfilipin in Gerrit, zeljkof in #wikimedia-releng).
Željko Filipin
--
0: https://lists.wikimedia.org/pipermail/wikitech-l/2017-April/087888.html
1: https://phabricator.wikimedia.org/T139740
2: https://www.mediawiki.org/wiki/Selenium/Node.js
TL;DR:
MediaWiki core is upgrading its version of QUnit from 1.x to 2.x.
This means extensions or skins with QUnit tests must now be compatible
with 2.x.
See https://phabricator.wikimedia.org/T170515 and
https://qunitjs.com/upgrade-guide-2.x/.
Hi all,
### Deprecated API
In 2014, QUnit started to overhaul its API, to be more robust and better
support async workflows. The most notable change was the removal of global
and static functions, in favour of more contextual methods.
The first part of this released in 1.15, and more was gradually introduced
in later releases. The vast majority of our codebases are already using the
new interfaces. In fact, the vast majority of our QUnit tests were written
after 2014 and never used the old interfaces in the first place.
For a short list of removed functions, see
https://phabricator.wikimedia.org/T170515.
If you find a QUnit Jenkins job for a MediaWiki extension or skin repo
starts failing, it is most likely due to this. Look for errors such as
"QUnit.start undefined", "test.callback is not a function",
"QUnit.asyncTest is undefined", and "QUnit.push is undefined",
There are also some methods that have been deprecated over the past few
years. These still work in QUnit 2. Please take a moment to familiarise
yourself with the renamed methods and new methods. Doing so will avoid
confusion when reading new code that uses them.
See https://qunitjs.com/upgrade-guide-2.x/.
### New features
The 'setup' and 'teardown' module hooks are now called 'beforeEach' and
'afterEach'. The old names still work, but the new names clarify that these
hooks are run for each QUnit.test().
QUnit 2.0 also adds new 'before' and 'after' hooks, which run only once per
module. This is somewhat analogous to use of setUpBeforeClass() in PHPUnit.
Since QUnit 1.16, QUnit.test() supports returning a Promise from the test
callback. This automatically attaches an assert.async() handler and waits
for the promise to complete. It also asserts that the Promise will be
resolved, and fails the test if rejected. This helps avoid a common pitfal
where a test could timeout when forgetting to attach a promise.fail()
handler.
## Upgrade
The version used on Special:JavaScriptTest has already been upgraded. –
https://gerrit.wikimedia.org/r/365757.
The copy used for command-line usage (grunt-karma) and Jenkins will be
upgraded by https://gerrit.wikimedia.org/r/367838
-- Timo
Hello,
This was something that came up during "The Big Open" at Wikimania, when
Katherine Maher talked with Ryan Merkley (CEO of Creative Commons) and
Mark Surman (ED of Mozilla Foundation). One of the themes mentioned was
that our projects need to work together and support each other.
In that vein, I'm interested in what people think about promoting
Firefox to users who are using legacy browsers that we don't support at
Grade A (or some other criteria). As part of the "drop IE8 on XP"
project[1] we're already promoting Firefox as the alternative option. I
was imagining it could be a small and unobtrusive bubble
notification[2], similar to those that Google pushes Chrome on people with.
If users use modern browsers, they're going to have better security
support, and most likely a better experience browsing Wikimedia sites
too. We'd be improving the web by reducing legacy browsers, and allowing
us to move forward with newer technology sooner (ideally).
And we'd be supporting a project that is ideologically aligned with us:
Mozilla.
Thoughts, opinions?
[1] https://phabricator.wikimedia.org/T147199
[2] https://www.mediawiki.org/wiki/Bubble_notifications
Thanks,
-- Legoktm
Hello,
Today, we discovered a major regression in Wikilabels. We've patched the
issue and made an emergency deployment. We also deleted some labels that
were saved while the system was compromised.
Here is the details of of what happened:
https://phabricator.wikimedia.org/phame/post/view/69/wikilabels_incident_re…
We're very sorry for this inconvenience,
Yours truly
--
Amir Sarabadani Tafreshi
Software Engineer (contractor)
-------------------------------------
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
http://wikimedia.de
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.
https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-08-30
= 2017-08-30 =
== Callouts ==
* Selenium Ruby framework deprecation at the end of October
** Announcement:
https://lists.wikimedia.org/pipermail/wikitech-l/2017-August/088653.html12:…
* trebuchet is to scheduled be removed at quarter's end. It's effectively
replaced by scap. Salt (the foundation upon trebuchet is built) will be
removed too. https://phabricator.wikimedia.org/T164780
* IE8-on-XP support being dropped. https://phabricator.wikimedia.org/T163251
* Ganglia is being moved behind LDAP authentication for security reasons
plus deprecation https://gerrit.wikimedia.org/r/#/c/374320/
* eqiad frack refresh preparation in progress, temptative transition
scheduled for Sept. 20th. https://phabricator.wikimedia.org/T174218
* Would like somebody from Ops who knows dumps to review:
https://gerrit.wikimedia.org/r/#/c/373354/
== Audiences ==
=== Readers ===
==== Multimedia ====
* 3D work continuing as usual - have some deploy bumps to pave over
* Onboarding 1 engineer and 1 PM, will take up some of our productivity
==== iOS ====
* Blocked by: none
* Blocking: none
* Updates:
** Working on 5.6.1 with minor bug fixes (
https://phabricator.wikimedia.org/project/view/2898/ ), goes to public beta
this week
** Next up is 5.6.7 ( https://phabricator.wikimedia.org/project/view/2899/
)
==== Discovery ====
* Blocked by: none
* Blocking: none
* Updates:
** Running search result thumbnails AB test this/next week
====Reading Infrastructure ====
* adding article concatenation support to Collection extension
=== Contributors ===
==== Global Collaboration ====
===== Language =====
* No Blocker/Blocking.
* CX-VE work continue.
* Preparing for cxserver deployment (with lots of changes/improvements!)
* New MT service in review: Matxin.
===== Collaboration =====
* Updates:
** ChangesList filters
*** RCFilters: Minimize saved query before comparison
({{phabricator|T174193}})
*** WLFilters: set default values ({{phabricator|T171134}})
*** RCFilters: Adjust highlight for seen/unseen states in Watchlist
({{phabricator|T171235}})
*** WLFilters: Fix seen/unseen filters ({{phabricator|T171127}})
*** RCFilters: Enable 'View newest' ({{phabricator|T163426}})
*** RCFilters: Hide saved queries from anonymous users
({{phabricator|T173992}})
*** WLFilters: avoid querying the DB when filters are in conflict
({{phabricator|T171132}})
*** Various bug fixes
* Blockers
** Resolved a Flow issue that was blocking dumps ({{phabricator|T172025}})
=== Community Tech ===
* Post-deployment fixes to LoginNotify and CodeMirror
* Working on GlobalPreferences and ArticleCreationWorkflow
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
=== Fundraising Tech ===
* No blocker/blocking
* Trying to optimize things for December (db writes, fs access, etc)
* More work on handling donations where the user returns with no session
cookies
* More work on main CC processor - new API and audit file format
=== MediaWiki Platform ===
* Blocked by:
* Blocking:
* Updates:
=== Performance ===
* Blocked by:
* Blocking:
* Updates:
=== Release Engineering ===
* Blocked by: none
* Blocking: none
* Updates:
** Selenium Ruby framework deprecation announce:
https://lists.wikimedia.org/pipermail/wikitech-l/2017-August/088653.html 1
2:31:12
*** End of October deprecation date.
** Team kanban:
https://phabricator.wikimedia.org/project/board/2769/query/rAdBKbHGnFVu/
=== Research ===
* Blocked by:
* Blocking:
* Updates:
=== Scoring Platform ===
* Blocked by:
** Bit of ops support to help us diagnose file handle starvation during
stress testing. https://phabricator.wikimedia.org/T174402.
https://phabricator.wikimedia.org/T169246
* Blocking:
** Moving our service over to a new, dedicated cluster.
* Updates:
** Thresholds feature is announced and ready for testing,
https://phabricator.wikimedia.org/phame/post/view/68/more_better_model_info…
** Over the next few weeks, we're finalizing a schema for commenting on or
judging almost any wiki artifact:
https://etherpad.wikimedia.org/p/meta_ores_schema
** Working to formally identify our stakeholders.
https://www.mediawiki.org/wiki/ORES/Stakeholders
=== Search Platform ===
* Blocked by: none
* Blocking: none
* Updates:
** Continuing work on ML-assisted ranking
** A/B tests for interleaved results and human-graded relevancy concluded,
analyzing results next
** Fixed issue with punctuation and Chinses language (T172653)
** Categories to RDF code merged, need review for
https://gerrit.wikimedia.org/r/#/c/373354/ from somebody who knows dumps
** WDQS logs now go to logstash
** Sent inquiry to wiki communities about extending the list of namespaces
searched by default (https://phabricator.wikimedia.org/T170473)
* Analyzed some unexpected behavior of searchin Japanese:
https://phabricator.wikimedia.org/T173650
=== Security ===
* Blocked by: None
* Blocking: None
* Updates:
* Completed auditing tables which are being replicated to labs for
consistency with privacy policy
* Reviews:
** Adhoc review of CentralNotice
** vue.js
** ArticleCreationWorkflow
=== Services ===
* Blocked by: none
* Blocking: none
* Updates:
** Came back from an offsite
** Rolling out job event production to all wikis today
** Continuing to set up the new Cassandra 3 cluster
** Will be very slowly preparing for node.js upgrade, so will soon create
some tasks for service owners to access the complexity of it
=== Technical Operations ===
* Blocked by: none
* Blocking: none
* Updates:
** trebuchet is to scheduled be removed at quarter's end. It's effectively
replaced by scap. Salt (the foundation upon trebuchet is built) will be
removed too.
** IE8-on-XP support being dropped.
https://phabricator.wikimedia.org/T163251
** Ganglia is being moved behind LDAP authentication for security reasons
** eqiad frack refresh preparation in progress, tentative transition
scheduled for Sept. 20th. https://phabricator.wikimedia.org/T174218
== Wikidata ==
* Blocked by:
* Blocking:
* Updates:
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
Wiki articles can be printed by most modern web browsers.The design and
layout of printed articles by the web browser is controlled via a special
print style sheet. This is similar to, but not the same as, the "Download
as PDF" feature, which recently saw a similar update.
Our current print styles have issues printing tables that are common on
many articles. They also do not contain any reference to the Wikipedia
brand. The Readers team at the Wikimedia Foundation plans to update these
print styles with some improvements.
* Book-like styling similar to our current book (PDF) rendering option
* New layout of article content to reduce paper usage. This can potentially
reduce the number of pages printed by 20 to 25%.
* Clear printing of tables and infoboxes
* Better headings
* Project-specific branding
We are planning on deploying these styles in August 2017. For a comparison
of the old print styles and the new, please visit the project page on
MediaWiki.org. Comments and feedback can be left on the talk page there.
https://www.mediawiki.org/wiki/Reading/Web/Projects/Print_Styles#Desktop_Pr…
Yours,
Chris Koerner
Community Liaison
Wikimedia Foundation
Hello -
I'm writing today to let you know that we're cancelling the recurring
CREDIT showcase (https://www.mediawiki.org/wiki/CREDIT_showcase). Turnout
has been relatively low for a while, and it requires a fair amount of setup
each month.
Going forward, we'll return to the previous approach, which was having
individual teams sharing demo videos on their own. Please be on the lookout
for such demos along the way on wikitech-l.
In closing, I'd like to thank everyone who's participated in CREDIT in the
past. I've appreciated all of the hard work that goes into planning these
events and the neat things you've all shared along the way.
Thank you.
-Adam