Hi, I just proposed a session for the Wikimania Hackathon next week:
Creation of a Program Committee for Wikimedia developer events
All the details are in the task. I am mentioning this here to promote the
session among those of you joining the hackathon in Montreal next week, but
most importantly to encourage feedback and discussion before the session
and by anyone anywhere. Preferably in the task itself, to avoid
Engineering Community Manager @ Wikimedia Foundation
Hey, yesterday the patch implementing human-readable section IDs  was
merged (thanks, Tim!). The new feature has already been enabled on beta
cluster and you can try it yourselves, e.g. on  - some pages might still
have old HTML cached though and require a null edit to update.
What's next? We can probably flip it on testwiki after Wikimania, but
further deployments depend on Reading Web, Apps and Parsoid teams. We,
however, can already encourage editors to check it out in staging.
Unanswered question: do we really need to percent-encode the IDs? There is
extensive discussion of that in the aforementioned task, concluding that
percent-encoding is probably more "correct". However, not escaping it gives
much better browser compatibility (close to 100%). We can change this at
any time because no links will be broken due to the way browsers handle
What's the impact for end users? When the commit above goes live, there
will be no user-visible changes, and almost no HTML changes at all (only
some interface IDs/classes generated from MediaWiki messages might slightly
change, but no links will be broken). When we migrate we will initially
enable new IDs as a fallback. After 1 month, the new IDs will become
default while old ones will be used as a fallback. This way, old links will
continue to work, and we have no plans to disable the fallbacks in the
What's the impact for developers? Sanitizer::escapeId() has been
deprecated, all code should migrate
to escapeIdForAttribute(), escapeIdForLink()
or escapeIdForExternalInterwiki(). Warning: unlike escapeId(), these
functions' output is not guaranteed to be HTML-safe so it must be escaped.
Our security guidelines say that everything should be HTML-safe anyway, so
even escapeId() should be properly escaped. The same deprecation happened
Max Semenik ([[User:MaxSem]])
I haven't tried this, but it sounds like translators and Language
Engineering folks might be interested.
---------- Forwarded message ----------
From: Alex Brollo <alex.brollo(a)gmail.com>
Date: Tue, Aug 1, 2017 at 12:10 AM
Subject: [Wikisource-l] An it.source gadget to manage diacritics
To: wikisource list <wikisource-l(a)lists.wikimedia.org>
Just to let it known, some it.source contributors are using a comfortable
gadget to manage diacritics - it can delete, replace or add a pretty large
list of diacritical marks to any character with a single click.
It uses .normalize() string method, so decomposing-recomposing (when
possible) unicode characters and allowing to manage diacritics alone
indipendently from base ascii character.
Perhaps is this gadget "rediscovering the wheel"....? Anyway, the code is
Wikisource-l mailing list
Due to today's train deployment more than doubling the error rate seen in
fatalmonitor, I have rolled-back group 1 wikis to wmf.11. I've submitted
an UBN task T172320  detailing the error, which appears to be fallout
from issues in Wikibase first noticed two weeks ago.
I expect that this will be easily resolved once someone familiar with the
issue has had a chance to look into it and the train should be back on
track in time for tomorrow's deployment.
Next week is Wikimania (yay!), for those of you who weren't aware.
Due to having good non-Wikimania coverage in both Release Engineering
and Operations we will, however, be doing the normal MediaWiki train
that week along with SWAT and (if needed) service deploys.
Please don't merge risky things thinking that you have an extra week
to make them less risky.
Release Team Manager
For patrolling work, ORES usually has two levels of support:
- For basic support we usually provide a model that is called 'reverted'
and has less accuracy. It also risks perpetuating editor biases due to the
lack of differentiation between reasons that a change may have been
- For advanced support, we require manual labeling of a large sample of
edits, but then we can provide two more models: 'damaging' and 'goodfaith'.
ORES review tool can only be enabled on wikis where advanced support is
available and most other tools prefer the 'damaging' over the basic
'reverted' model as well.
So, for performance and capacity reasons we think it makes sense to remove
'reverted' models from the ORES service when 'damaging' model is made
available. However, we also want to be careful about making sure this
change doesn't disrupt the work of tool developers that make use of the
If you do, please voice your concerns now. If there is no objection within
the next two weeks, we'll begin the process of removing the 'reverted'
model for wikis that have the 'damaging' model available.
Related phabricator card: https://phabricator.wikimedia.org/T171059
Amir Sarabadani Tafreshi
Software Engineer (contractor)
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
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.
This is an email about Tech News. Partly to introduce or explain what
it is to those who might be unfamiliar with it, or have seen it but
don't know it well. Partly to ask if there's anything we could do
better. If you know all there’s to know, there’s a request for
feedback towards the bottom of this email.
ABOUT TECH NEWS
a) What is Tech News?
Tech News is a newsletter for reaching out with technical updates to
the general Wikimedia editor communities, to make sure they can keep
track of what's happening. It's typically distributed in 15–20
languages, reaching roughly 90 community pages (Village Pumps etc) and
some 600 individual subscribers, in addition to those who read it on
Meta, see it included in the Signpost or get it in their email inbox.
b) How is Tech News written?
Simplification is key. Technical news for non-technical readers.
Should be easy to translate as well as be written with en-1 and en-2
readers in mind. A couple of sentence per item, then a link to a Phab
task, wiki page or email if they need more information. Too long and
we put an unreasonable burden on the translators.
c) I've done something technical. The communities should know. How do I add it?
* There's a "user-notice" tag in Phabricator. Add it to the task
together with a simple 1–3 sentence explanation of what this is and
how it affects editors. Don't worry about polish, we'll take care of
* You can add it yourself!
https://meta.wikimedia.org/wiki/Tech/News/Next will take you to the
relevant issue. Remember to link to a relevant Phab task, wiki page or
* You can always write on https://meta.wikimedia.org/wiki/Talk:Tech/News
d) When is it distributed?
Weekly, each Monday afternoon/evening UTC. The deadlines for additions
are several days prior to that to give the translators time to do
for when to add things to have them included in the next newsletter.
e) What is Tech News not?
* A general Wikimedia newsletter. Everything in the Wikimedia world is
at most one step removed from being technical. This doesn't mean Tech
News is the best place. Typical items are new or upcoming features or
potential breaking changes.
* The way to reach the Wikimedia technical community. If you want to
reach Wikimedia developers, an email to wikitech-l is usually better
than an item in Tech News. Tech News is a way to keep Wikimedia
contributors up-to-date with technical changes.
* A way to talk about all the important things that happen in the
background. They're often awesome and we should talk more about them,
but if they don't affect how contributors interact with the sites,
then this is not the place.
* A place for updates about one wiki. If it's just relevant for
English or German Wikipedia, you should update English or German
Wikipedia, not the entire Wikimedia community. Exceptions to this rule
are Commons and Wikidata, because they're used by so many other
HOW CAN WE MAKE TECH NEWS BETTER?
Are there ways we could make Tech News better at spreading information
about technical updates that are relevant for Wikimedia contributors?
Something we do that's unnecessary? Things we're often missing? Things
we fail to explain? Anything we're particularly good at and should
keep doing? Tell us – on the list, on
https://meta.wikimedia.org/wiki/Talk:Tech/News, or privately (:
And, specifically – are there other places (wiki pages etc) where this
information should be available? Anything we could do to make this
easier for you?
= *2017-08-02* =
== Callouts ==
*** Android App: We are investigating user reports of reading list pages
saved for offline not functioning correctly; trying to reproduce issues.
*** WikiData: Wikidiff2 patches about moved paragraphs need review:
***Tech Ops: Still ongoing issues with pdfrender getting stuck
*** Scoring Platform: Large file support in git: subscribe to this task if
you might have similar requirements!
== Audiences ==
=== Readers ===
==== Web ====
Starting work on new page summary API
Desktop print styles
==== iOS native app ====
* Blocked by: none
* Blocking: none
* Updates: 5.6.0 (Reading themes, on this day) final bug fixes & polish,
submit to App Store on Friday 8/4
==== Android native app ====
* *Blocked by:* n/a
* Blocking: n/a
** Cookie release work is all in QA/design review –
*** We are investigating user reports of reading list pages saved for
offline not functioning correctly; trying to reproduce issues. Want to
nail this down before the release.
** Offline compilations MVP client-side work is nearly complete –
*** Work on file generation and storage is underway (
** One engineer is newly hired, one more offer still to be made; PM search
is in progress
==== Reading Infrastructure ====
* Blocked by:
** Extracting structured reference lists (JSON).
** Fixing pronunciation parsing.
** Gergo on vacation until Wikimania
==== Discovery (maps) ====
* Blocked by: none
* Blocking: none
* Deploying mapframe/maplink to four more wikis that the community has
* Progressing with reloading test server
== Community tech ==
* Human-readable sections merged, wikitech-l announcement today
* CodeMirror and LoginNotify hopefully deploying soon
* Started work on GlobalPreferences and ArticleCreationWorkflow
Not blocking and not blocked
=== Contributors ===
==== Global Collaboration ====
===== Language =====
* No blockers.
* Niklas looking at, T170591. See:
** cxserver's adaption changes merged; deploy pending.
** CX-VE work continue.
===== Collaboration =====
*** Filter duplicates when filtering for multiple tags
** RCFilters: Improve loading animation
*** Make 'related links' collapsible
*** Create a sticky preference for days/limit groups
*** Allow setting a new query as default
*** Ability to page through the results in the new UI
*** Some bug fixes
** Flow dumps - https://phabricator.wikimedia.org/T172025
==== Parsing ====
* Language Converter support code in Parsoid was deployed y'day -- the
second part of rendering a page in the desired language variant is the next
part in development
* Going to be publishing weekly linter count change stats on wiki --
** Weekly plug :-) if you are an editor on a wiki, please help fix these
high-priority linter issues on your home wiki.
==== UI Standardization ====
** OOjs UI: v0.22.4 released, among changes:
*** (continued from last week): Further aligning OOjs UI with WikimediaUI
**** WikimediaUI theme: Directly use the Less values from WikimediaUI Base
(James D. Forrester)
*** Accessibility FieldsetLayout: Use `<legend>` now that Chrome 55 bug is
less important (James D. Forrester)
*** Apex theme: Introduced focus states on all widgets as accessibility/UX
*** WikimediaUI theme: Work around a Firefox rendering bug for checkboxes
and radios (Bartosz Dziewoński)
== Wikidata ==
* Further improvements on the Query Service UI:
* Preparing for Wikimania: cleaning up Lexeme demo data, widgets, and
== German Technical Wishlist ==
* Blocked by:
** Waiting for C++ reviews of the wikidiff2 patches for changes in moved
*** the plan is to get at least +1s and then poke Tim
=== Search Platform ===
* Blocked by: none
* Blocking: none
** Continuing work on ML-assisted ranking
** Working on A/B test with interleaving search results (
** Vietnamese analyzer will be re-evaluated after upstream bugfixes (
** Archive search enabled everywhere (
https://phabricator.wikimedia.org/T163235 ), needs bugfix (
** Wikidata prefix search with Elastic testing continues, some feedback
received & processing (test: http://elastic-wikidata.wmflabs.org/wb.html,
** Trey published docs for tools used to analyze language analysers:
=== Services ===
* Blockers: none
** Will truncate stored HTML soon to free up space for Cassandra 3 migration
*** No disruptions for VE
*** A bit elevated latencies for some time
** Testing new data model in the RESTBase-dev cluster. Please ignore alerts
** Recommendation service API going public tomorrow
** Low team availability next week due to Debconf
=== Technical Operations ===
* Blocked by:
** Flow dumps speedup still blocked on revision content retrieval issue,
** Still ongoing issues with pdfrender getting stuck
** Wikidata and dewiki read only for 1hour+
=== Fundraising Tech ===
* CentralNotice: working on clone campaign feature, fixed a couple little
* Working on generic script to clear up stranded payments
* Loading ever more mailing data into Civi from our 3rd party bulk mailer
* Continuing work on API update for our main credit card processor
* Also updating our audit parser for the same processor
=== Scoring Platform ===
* Blocked by:
**Note git-fat is still a long-term blocker, and some solutions are being
* Blocking others:
**Mention that we're trying to resolve our blocker to using the new ORES
server cluster, by doing stress tests to estimate capacity. When we're
done, the celery workers will be moved off of SCB nodes
**Revscoring 2.0 is coming -- going break ORES "model_info" JSON structure
& add new functionality
***Will be deployed on labs before in prod, so code can be updated and
***Announcement coming -- probably during Wikimania
***"Thresholds" is something Roan knows about
=== Security ===
** Kartography extension
** review of tables replicated to sanitarium
I'd like to welcome you to join us at the CREDIT showcase next week,
Wednesday, 2-August-2017 at 1800 UTC / 1100 Pacific Time. We'd like to see
your demos, whether they're rough works in progress or polished production
material, or even just a telling of something you've been studying
recently. For more information on the upcoming event, as well as recordings
of previous events, please visit the following page:
And if you'd like to share the news about the upcoming CREDIT showcase,
here's some suggested verbiage. Thanks!
*I hope all is well with you! I wanted to let you know about CREDIT, a
monthly demo series that we’re running to showcaseopen source tech projects
from Wikimedia’s Community, Reading, Editing, Discovery, Infrastructure and
Technology teams. *
*CREDIT is open to the public, and we welcome questions and discussion. The
next CREDIT will be held on August 2nd at 11am PT / 2pm ET / 18:00 UTC. *
*There’s more info on MediaWiki, and on Etherpad, which is where we take
notes and ask questions. You can also ask questions on IRC in the Freenode
chatroom #wikimedia-office (web-based access here). Links to video will
become available at these locations shortly before the event.*
*Please feel free to pass this information along to any interested folks.
Our projects tend to focus on areas that might be of interest to folks
working across the open source tech community: language detection,
numerical sort, large data visualizations, maps, and all sorts of other
*If you have any questions, please let me know! Thanks, and I hope to see
you at CREDIT.*
Project Assistant, Engineering Admin