Hello,
apologies for cross-posting!
I am writing to inform you that at Wikimedia Deutschland we have decided to
stop having weekly Technical Advice IRC Meetings (TAIM)[1] at
#wikimedia-tech after the final meeting on December 18th. In other words,
Technical Advice IRC Meetings will not continue in 2020.
We realized that the regular IRC meeting format has achieved the limits of
its reach, and it is time for us to think about other means to better
support as many volunteer developers as possible contributing to Wikimedia
software.
At WMDE we’ll be dedicating our efforts in 2020 to constantly improve
documentation of our products, including Wikidata and Wikibase, to allow
easier usage and contribution. Our engineering teams are also exploring new
possibilities to support volunteer developers in a more asynchronous way
than regular IRC meetings. If you have any suggestions for this, please let
us know on our talk page.[2]
On this point we would like to send the warmest thank you to all the people
who hosted TAIM meetings, all participants asking and answering questions,
and all supporters of TAIM over the years.
Have a great seasonal break and see you around in 2020!
On behalf of TAIM crew at WMDE
Johanna
[1] https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
[2] https://www.mediawiki.org/wiki/Talk:Technical_Advice_IRC_Meeting
--
Johanna Strodt
Project Manager for Community Communication / Technical Wishes Project
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
https://wikimedia.de
Hi All,
while going through OO.ui.confirm dialog documentation I got curious about
how to change the labels of the action buttons 'Ok' and 'Cancel' to show
different texts.
--
Eugene
Hello,
last couple of days we've released v0.36.0 & minor follow-up v0.36.1 to
ensure backwards compatibility. We caught the issue before rolling release
out. Version v0.36.1 will roll out on normal train next Tuesday.
Highlights in this release were
- Breaking change: Requiring PHP 7.2.9+, up from 5.6.99/HHVM in alignment
with recent MediaWiki core changes
- Deprecating change: Rename LookupElement's onLookupMenuItemChoose to
onLookupMenuChoose to follow naming scheme listeners – {Emitter}{Event}.
Thanks to Bartosz Dziewoński and Ed Sanders for quickly identifying and
fixing the backwards compatibility issue
- Amending and updating TextInput- and DropdownWidgets paddings minimally
to fully align with Design Style Guide's components templates[0].
You can find details on additional new features, code-level, styling and
interaction design amendments, and all
improvements since v0.35.0 in the full changelog[1].
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, interactive demos[2] and library documentation is available
on mediawiki.org[3], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[4].
OOUI version: 0.36.1
MediaWiki version: 1.35.0-wmf.11
Date of deployment to production: Regular train, starting Tuesday 17
December
[0]- https://design.wikimedia.org/style-guide/components/
[1]-
https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
<https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr>
[2]-
https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[3] - https://www.mediawiki.org/wiki/OOUI
[4] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
I made this RFC: https://phabricator.wikimedia.org/T240307
TL;DR: we'll have one interface per hook, and that interface will be
used for both calling and handling the hook.
It may seem like overkill, but on closer analysis, it actually seems
to work pretty nicely. There will be a place for doc comments,
arguments will be type-hinted, and smart code editors will be able to
show the hook documentation when you call or handle it.
The main open questions are:
* Where to put the many core interfaces: together or grouped by module?
* Should we split up the core HookRunner class by module? It contains
one line of boilerplate code per hook.
Existing hook handling classes in extensions can be converted to the
proposed system by:
* Changing all the handlers from static to non-static functions.
* Adding the necessary "implements" clause.
* Renaming any methods that do not already match the onHookName() pattern.
* Tweaking extension.json slightly.
I'm going on vacation soon, so I'll be aiming to move this to last
call early in the new year.
-- Tim Starling
Hi,
I've implemented two new diff themes in Gerrit's old UI. They are meant to
address the following two issues:
1. The default diff theme used in Gerrit places dark red and purple text on
a dark red background (in removed code). This can be hard to read.
Especially on a yellow-tinted monitor (e.g. Red shift, Night shift, Flux,
etc.).
2. The general use of green/red while readable, is hard to distinguish for
certain types of color-blindness.
== Theme 1: "elegant"
(Screenshot at https://phabricator.wikimedia.org/T232893)
This theme adopts the MediaWiki diff styles (yellow and blue). Which means:
* It only colours the background of the intra-line characters that were
added/changed/removed.
* The rest of the line uses a clean white background, thus providing full
colour contrast for all other syntax-highlighted code.
* The boundary of the added/removed blocks is indicated by a border (not by
absence of a background shade).
* The unchanged code lines are lightly shaded in grey (instead of the
default where these lesser important lines are given a bright white
background).
In other words, just like MediaWiki :)
== Theme 2: "eclipse"
(Screenshot at https://phabricator.wikimedia.org/T232893)
* The background greens and reds are lighter overall, stronger colour
contrast. The background reds have moved closer to orange, the greens have
moved closer toward cyan/blue.
Overall this theme is still very close to the default Gerrit theme, and
might be a good option if you've found the readability a concern but would
rather not make as much of a radical change (yet :D).
== How to change my diff theme?
>From any diff in Gerrit:
1. Click the gear icon in the top-right corner.
2. Select a Theme. (This provides a live preview!)
3. Press "Save" if you like it.
Alternatively, you can change it (without live preview) from the Settings
page:
https://gerrit.wikimedia.org/r/#/settings/diff-preferences
== What about the new UI?
The new UI already has better colour contrast in its diff styles, with
lighter background reds and greens by default.
Unfortunately the new UI has removed both the ability to theme the syntax
highlighting, as well as the ability to theme the diff colours on top of
that. Neither is changeable in the new UI currently.
For the time being I'm a hold out in the old UI as I'm unable to use review
dashboards in the new UI (until we upgrade to 2.16). Meanwhile this is
beneficial to myself and anyone else in a similar hold out.
-- Timo
Hi,
for HTML version see
https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-12-11
Željko
--
= 2019-12-11 =
== Callouts ==
* Release Engineering - December 23-January 3rd - No deploys (including
train), Holiday break
* Search Platform is blocked by Structured Data: Data dumps for SDC:
[[phab:T221917]]
== Product ==
=== iOS native app ===
* Updates:
**Working on interim bug fix release 6.5.1 [[phab:project/view/4414]]
**Development on 6.6 [[phab:project/view/4273]]
***Mobile-html
***more bug fixes
=== Android native app ===
* Updates:
**Suggested Edits V3 is in Production.
**Currently working on mobile-html. Work is 70% done.
***Started looking into Machine vision APIs
=== Web ===
* Updates:
** Summary: same as last week. Planning for desktop improvements and
tapering off of advanced mode.
** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project (Vector
/ DIP)]]:
*** Planning, research, and task creation
*** [[phab:T239248|<nowiki>Divide VectorTemplate into components</nowiki>]]
** Page previews (Popups):
*** [[phab:T236589|<nowiki>Page Previews Storybook not available on
doc.wikimedia.org and documentation a bit broken</nowiki>]]
** Mobile website (MinervaNeue / MobileFrontend):
*** [[Reading/Web/Advanced_mobile_contributions|Advanced mode]]:
**** [[phab:T232652|<nowiki>Add History to article toolbar for all
logged-in users</nowiki>]]
**** [[phab:T232594|<nowiki>Add article and discussion tabs to all
logged-in users on mobile</nowiki>]]
**** [[phab:T232653|<nowiki>Updates to user pages for all logged-in
users</nowiki>]]
**** [[phab:T230695|<nowiki>Render talk page as a tab (rather than a
modal)</nowiki>]]
*** Miscellaneous:
**** [[phab:T225213|<nowiki>Main Menu should work without JavaScript to be
more accessible and a better user experience</nowiki>]]
**** [[phab:T214045|<nowiki> Drawers should be removed from DOM after
close</nowiki>]]
**** [[phab:T239304|<nowiki>MinervaNeue: Desktop mode has invisible menu
button</nowiki>]]
**** [[phab:T238681|<nowiki>History icon not completely visible in smaller
screen devices</nowiki>]]
**** [[phab:T210808|<nowiki>Mark the MobileView API as deprecated</nowiki>]]
=== Product Infrastructure ===
* Updates:
** BUOD: Patch for EventLogging [[phab:T238544]]
** BUOD: Patch for error logging client [[phab:T235189]]
** Maps: investigated populate_admin error and deployed potential fix
[[phab:T240227]]
** Proton: Profiling continues with buster images for node
** MachineVIsion: Added no-JS fallback to Special:SuggestedTags
** MachineVision: Added frontend event logging to Special:SuggestedTags
** MachineVision: Updated suggestion query for performance
** MachineVision: Tweaked user approval/rejection vote validation behavior
** Push notifications: Researched approaches and software
=== Structured Data ===
* Blocking:
** dumps of MediaInfo items, see [[phab:T239905]]
** Search Platform - Data dumps for SDC: [[phab:T221917]]
* Updates:
** work continues on new input data types for statements on File page and UW
** tech talk today at 1800 UTC
=== Inuka ===
* Updates:
** Wikipedia KaiOS app: table of content [[phab:T234618]]
** Wikipedia KaiOS app: article links selection [[phab:T234625]]
=== UI Standardization ===
* Updates:
** OOUI v0.36.1 in preparation, with a hotfix for v0.36.0, which rollout we
stopped for reason of breaking backwards-compatibility in one case.
** Design Style Guide: Polishing base components in components section
== Technology ==
=== Fundraising Tech ===
* Updates:
** Have a pretty convincing explanation for apparent CentralNotice
impression inconsistencies (new campaign fallback feature changed reporting
of status codes)
** Fixing issues with new recurring donations features
** Optimizing donation imports from queue and from matching gifts
spreadsheets
=== Engineering Productivity ===
==== Release Engineering ====
* Blocking:
** Site Reliability Engineering - Requesting follow-up from Releng team
regarding Gerrit/Zuul Prometheus metrics [[gerrit:479139]]
* Updates:
** Train Health
*** Last week: 1.35.0-wmf.8 - [[phab:T233856]] - group1 + group2
*** This week: 1.35.0-wmf.10 - [[phab:T233858]]
*** Next week: 1.35.0-wmf.11 - [[phab:T233859]]
=== Scoring Platform ===
* Updates:
** Improvements to cawiki and euwiki deployed!
** Limits requests to 50 rev_ids per
** Model info now uses consistent ordering
** Advanced editquality support for Norwegian Wikipedia incoming --> Growth
** Built a machine-readable WikiProject taxonomy. See
https://github.com/halfak/wikitax
=== Search Platform ===
* Blocked by:
** Structured Data: Data dumps for SDC: [[phab:T221917]]
* Updates:
** "Wikidata Query Service Updater" should have 'bot' in the user agent to
indicate is a tool - [[phab:T238106]]
* Stuff no one else cares about:
** NullPointerException in wdqs-updater after last deployment
[[phab:T239131]]
=== Site Reliability Engineering ===
* Blocked by:
** Requesting follow-up from Releng team regarding Gerrit/Zuul Prometheus
metrics [[gerrit:479139]]
* Updates:
** Wrapping up goals/OKRs for the end of the quarter.
Hi Everyone,
It's time for Wikimedia Tech Talks 2019 Episode 11! This talk will take
place on *11 December 2019 at 6 PM UTC.*
Title: Structured Data on Commons
Speaker: Cormac Parle, Senior Software Engineer
Summary:
The talk will cover Structured Data on Commons:
- what structured is
- the structured data we store for a media file on commons
- where we store it
- how it helps with search
- the UI and the API calls we use to manipulate it
The link to the Youtube Livestream can be found here:
https://www.youtube.com/watch?v=U9LmFAkDnx0
During the live talk, you are invited to join the discussion on IRC at
#wikimedia-office
You can watch past Tech Talks here:
https://www.mediawiki.org/wiki/Tech_talks
If you are interested in giving your own tech talk, you can learn more
here:
https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Te…
Note: Please feel free to distribute this email to any lists that you feel
are appropriate!
Many kindnesses,
Sarah R. Rodlund
Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org
The 1.35.0-wmf.8 version of MediaWiki is blocked[0].
The train was tentatively unblocked on Friday. Details can be read
here:
* After deploy of 1.35.0-wmf.8 to group1, surge of "Cannot access the
database: Unknown error"
- https://phabricator.wikimedia.org/T239877
The new version can't proceed to group2 [1] until this (new) issue is
resolved:
* "PHP Notice: Undefined index: key" and similar in Cite.php and
ReferenceStack.php
- https://phabricator.wikimedia.org/T240248
If this issues is resolved, we will attempt to roll wmf.8 forward to all
wikis today, in order that wmf.10 can proceed as usual on Tuesday.
Thank you for your help with this issue!
-- Your frazzled train drudge
[0]. <https://phabricator.wikimedia.org/T233856>
[1]. <https://tools.wmflabs.org/versions/>
Hello everyone,
On Monday this week, we enabled Parsoid/PHP everywhere for all products
(Visual Editor, Mobile Content Service, Structured Discussions aka Flow,
Content Translation) but two (Wikitext Linter, Language Variant support).
Those last two were being supported by Parsoid/JS.
However, about 30 minutes back, we disabled database updates for wikitext
lints by turning off Parsoid/JS for the wikitext linter. You can read the
details in https://phabricator.wikimedia.org/T240057 but we took the
decision in order to help mitigate cluster load issues (
https://phabricator.wikimedia.org/T239983 if you have access to the phab
task ).
This is a temporary measure and we expect to be able to enable wikitext
linter updates something in the coming week (optimistically) assuming the
mediawiki train can roll out this week.
Not to bury the lede or anything (late on a Friday evening in the US
timezones), but we have now effectively switched over from Parsoid/JS to
Parsoid/PHP on the Wikimedia cluster. Once we have moved over language
variant support from Parsoid/JS to Parsoid/PHP and wrapped up any other
loose ends and tied a neat bow around it all, we'll be publishing a blog
post about the Parsoid/PHP porting and rollout process.
Subbu (on behalf of the Parsing team).