Hi Wikitech,
I've been catching up on the recent achievements regarding Parsoid/PHP,
well done!
With WMF sites being migrated, of course non-WMF sites start to creep into
the picture. As I'm involved in running one of those, I'm curious to know
if and how you are going to support this upgrade? I've read about Linter
and ParserMigration but I'm not clear on how they fit into the picture.
I'm asking specifically because we are running some custom extensions which
will probably break with the advent of Parsoid/PHP.
At present we are running MW 1.33 on PHP 7.0, but we are not using VE.
It would be fine if we as a maintenance team have to invest some (or even
considerable) time and effort but I would like to know the size of the
endeavour beforehand...
Thanks, best,
LF
2019 was a great year for Wikimedia Technical Talks
<https://www.mediawiki.org/wiki/Wikimedia_Technical_Talks>! We are looking
forward to a new year and a new line-up of speakers starting in February
2020!
If you have an idea for a Tech Talk (or know someone who does) -- please
propose a talk
<https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?title=Proposa…>!
We'll discuss your idea with you, and if it's a good fit, we'll get you on
this year's schedule.❤📆❤
- If you are saying to yourself, *"UGH! NO WAY! I HATE PUBLIC
SPEAKING!!!!"* 😐 You are not alone! Many people have a fear of public
speaking <https://en.wikipedia.org/wiki/Public_speaking#Glossophobia>.
One of the best ways to get past it is through practice!
- If you are thinking,* "An hour is way too long to talk to a faceless
audience!!!" 😬 *You are probably right! An hour is a long time to
listen, too! Let's come up with a length and format that will work for you!
- If you are thinking, *"I have an idea for a talk, but I don't have the
time!!!"* ⏰ No problem! We can schedule your talk for a few months from
now!
- If you are thinking, *"Ideas? I have no ideas!"* 💡Take a look at some
past tech talks
<https://www.mediawiki.org/wiki/Wikimedia_Technical_Talks#2019_Technical_Tal…>
for inspiration!
Tech talks are a great way to share your work, refine your ideas for other
professional venues (conferences, papers, etc), and be more visible in the
Wikimedia technical community! 👓 Hope you'll join us this coming year as a
speaker or a viewer!
Please feel free to forward this email to appropriate lists.
Kindly,
Sarah R. Rodlund
Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org
tl;dr if the timing of the weekly MediaWiki branch cut affects you, please
join the discussion on T242446[1]
Soon we will switch on full automation of the mediawiki branch cut! 🎉
In so doing we will switch from using the make-wmf-branch script in
release/make-wmf-branch. Instead we will use release/make-release/branch.py
and the associated config will now live at
release/make-release/settings.yaml. The documentation on wiki has been
updated to reflect the change with instructions about how to set up and use
branch.py.
There is more to this change than just using a different script, however.
In order to turn on full automation we need to decide on when to run the
branch cut. The current practice is to do it at approximately noon pacific
on Tuesdays. We could move this to an earlier time but I think we should
have a larger discussion about the timing of the branch cut and how that
affects various teams and workflows.
If the timing of the branch cut affects your team, your feedback is
requested on the task at [1]
[1] https://phabricator.wikimedia.org/T242446
Read on Phabricator at https://phabricator.wikimedia.org/phame/post/view/179
-------
How’d we do in our strive for operational excellence in November and
December? Read on to find out!
## 📊 Month in numbers
* 0 documented incidents in November, 5 incidents in December. [1]
* 17 new Wikimedia-prod-error reports. [2]
* 23 Wikimedia-prod-error reports closed. [3]
* 190 currently open Wikimedia-prod-error reports in total. [4]
November had zero reported incidents. Prior to this, the last month with no
documented incidents was December 2017. To read about past incidents and
unresolved actionables; check <
https://wikitech.wikimedia.org/wiki/Incident_documentation#2019>.
Explore Wikimedia incident graphs (interactive) at <
https://codepen.io/Krinkle/full/wbYMZK>.
-------
## *️⃣ Many dots, do not a query make!
David Causse investigated a flood of exceptions from SpecialSearch […].
Read the story at <https://phabricator.wikimedia.org/phame/post/view/179>.
-------
## 📉 Outstanding reports
Take a look at the workboard and look for tasks that might need your help.
The workboard lists error reports, grouped by the month in which they were
first observed.
→ https://phabricator.wikimedia.org/tag/wikimedia-production-error/
Breakdown of recent months (past two weeks not included):
* March: 3 of 10 reports left. (unchanged). ⚠️
* April: Three reports closed, 6 of 14 left.
* May: (All clear!)
* June: Three reports closed. 6 of 11 left (unchanged). ⚠️
* July: One report closed, 12 of 18 left.
* August: Two reports closed, 4 of 14 left.
* September: One report closed, with 9 of 12 left.
* October: Four reports closed, 8 of 12 left.
* November: 5 new reports survived the month of November.
* December: 9 new reports survived the month of December.
-------
# 🎉 Thanks!
Thank you to everyone who helped by reporting, investigating, or resolving
problems in Wikimedia production.
Until next time,
– Timo Tijhof
-------
Footnotes:
[1] Incidents. –
https://wikitech.wikimedia.org/wiki/Incident_documentation#2019
[2] Tasks created. –
https://phabricator.wikimedia.org/maniphest/query/AFDaPqjd5PTe/#R
[3] Tasks closed. –
https://phabricator.wikimedia.org/maniphest/query/YkIxmhRvEZ8R/#R
[4] Open tasks. –
https://phabricator.wikimedia.org/maniphest/query/47MGY8BUDvRD/#R
Hello everyone,
In 2015 Wikimedia Germany published the Service Catgraph[1], a graph
database of the categories of Wikipedias, as well as Deepcat[2] a gadget
for Wikipedia users to search for articles in a category, including
recursive subcategories, in the search page of Mediawiki.
Since 2018 this functionality is built in the search engine of Wikipedia as
well as into the Advanced Search GUI.
Wikimedia will therefore sunset Catgraph as well as Deepcat. We plan to
shut down the service end of January. Catgraph also powered other tools
such as Catcycle[3] and Article List Generator[4], these will also stop
working. If your wiki has deepcat enabled as a gadget or in your globar.js,
or you have it in your common.js you should remove it and use the newer,
built in 'deepcategory'.
Documentation for the new search-keyword can be found here:
https://www.mediawiki.org/wiki/Help:CirrusSearch/de?uselang=de#Deepcategory
Documentation for the new Graph-Database is available here:
https://www.mediawiki.org/wiki/Wikidata_Query_Service/Categories
Cheers,
Michael for the project Technical Wishes at Wikimedia Germany
[1]: https://wikitech.wikimedia.org/wiki/Nova_Resource:Catgraph
[2]: https://de.wikipedia.org/wiki/Hilfe:Suche/Deepcat
[3]: http://tools.wmflabs.org/render-tests/catcycle-dev/catcycle.py
[4]: https://tools.wmflabs.org/render/stools/alg?uilang=en
--
*M. F. Schönitzer*
Community Communication
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
https://wikimedia.de
Unsere Vision ist eine Welt, in der alle Menschen am Wissen der Menschheit
teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
https://spenden.wikimedia.de
Imagine a world in which every single human being can freely share in the
sum of all knowledge. Help us to achieve our vision!
https://spenden.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/029/42207.
Hi,
for HTML version see
https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-01-08
Željko
--
= 2020-01-08 =
== Callouts ==
* Release Engineering
** January 27th-31st - No deploys at all (including train), All-Hands
** Need some help (from CPT? Maybe?) looking at jobqueue on beta cluster
which is evidently running slowly: [[phab:T241448]]
* SRE:
** The eqiad kubernetes cluster will be reinitialized on Tuesday Jan 14th
2020. The duration is expected to be up to 4 hours during EU morning. All
requests will have been routed beforehand to codfw to avoid causing issues
to users. Please refrain from trying to deploy to that cluster during that
time period.
** OKRs in final drafts, reach out if your team requires SRE involvement
== Product ==
=== Editing ===
* Updates:
** Preparing to release v1.0 of DiscussionTools to target wikis to discuss
=== Growth ===
* Updates:
** Main focus is on releasing the first version of topic matching for
suggested edits module. Initial release utilizing morelike targeted for
before All Hands.
=== Android native app ===
* Updates:
**Preparing for a minor release with some bug fixes and improved language
variant support. The release candidate is currently in Beta :
https://play.google.com/store/apps/details?id=org.wikipedia.beta
**Mobile-html integration is 70% complete. The Android O board with the
rest of the work will be the next major release: [[phab:project/view/4318]]
=== Web ===
* Updates:
** Summary: digging into desktop improvements (DIP).
** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project (Vector
/ DIP)]]:
*** [[phab:T232140|<nowiki>Separate out logo handling into square image
logos and long text/wordmark banner logos</nowiki>]]
*** [[phab:T240062|<nowiki>Extract components from VectorTemplate to
Mustache files</nowiki>]]
*** [[phab:T239248|<nowiki>[EPIC] Divide VectorTemplate into
components</nowiki>]]
*** [[phab:T117279|<nowiki>[EPIC] Core should provide inline diffs as well
as side by side (Move InlineDifferenceEngine into core / remove
MobileDiff)</nowiki>]]
*** [[phab:T237561|<nowiki>[SPIKE 10hrs] Investigate how skin suboptions
can be presented in Special:Preferences</nowiki>]]
** Mobile website (MinervaNeue / MobileFrontend):
*** [[Reading/Web/Advanced_mobile_contributions|Advanced mode]]:
**** [[phab:T240644|<nowiki>Regression: Label is visible on Logout button
for logged in users on all wikis (non-AMC) and contribution icon on user
page</nowiki>]]
**** [[phab:T238364|<nowiki>[Bug] Simplified Talk Page Does Not Support
Sections With Non-ascii Characters/Several ascii characters aren't
supported either</nowiki>]]
**** [[phab:T236328|<nowiki>Username should be on its own line (Recent
changes & Watchlist)</nowiki>]]
*** Miscellaneous:
**** [[phab:T237050|<nowiki>The `site` and `site.styles` module should be
explicitly disabled on mobile rather than abuse the targets
system</nowiki>]]
**** [[phab:T214647|<nowiki>[EPIC] Re-define the contract for displaying
drawers and overlays in MobileFrontend</nowiki>]]
**** [[phab:T241179|<nowiki>Remove Special:MobileMenu</nowiki>]]
**** [[phab:T240502|<nowiki>Raw HTML in MobileFrontend</nowiki>]]
**** [[phab:T234570|<nowiki>Tech debt: Drop Browser.supportsAnimations
method</nowiki>]]
**** [[phab:T214049|<nowiki>Technical: Every Drawer has a shield for
catching clicks</nowiki>]]
**** [[phab:T198265|<nowiki>Special:MobileOptions is empty for third
parties and when beta is disabled and this is confusing</nowiki>]]
**** [[phab:T171000|<nowiki>[EPIC] Minerva works independently of
MobileFrontend</nowiki>]]
**** [[phab:T206069|<nowiki>Transition MobileFrontend Gruntfile.js tasks to
NPM scripts</nowiki>]]
**** [[phab:T140045|<nowiki>Respect
$wgAllowSiteCSSOnRestrictedPages</nowiki>]]
=== Product Infrastructure ===
* Blocked by:
** SRE on buster nodejs10 images for proton. Will resume work this week
=== Structured Data ===
* Blocking:
** Search Platform: Data dumps for SDC: [[phab:T221917]]
=== Inuka ===
* Updates:
** KaiOS app: read article in another language [[phab:T234628]]
** KaiOS app: loading experience [[phab:T240888]]
** KaiOS app: navigate to previous article [[phab:T241423]]
** KaiOS app: offline mode indicator
== Technology ==
=== Fundraising Tech ===
* Updates:
** CiviCRM
*** Updating Civi version to latest
*** More improvements to contact de-duplication
** Payments-wiki
*** Implementing iDEAL and recurring card payments via our backup processor
=== Core Platform ===
* Blocked by:
** RelEng on Quibble [[phab:T236680]]
** Security OAuth 2.0 review [[phab:T239940]]
* Blocking:
** Search Platform: MW Job consumers sometimes pause for several minutes
[[phab:T224425]]
** RelEng: [[phab:T241448]]
* Updates:
** New session storage to roll out to production -> Redis cluster going away
=== Engineering Productivity ===
==== Release Engineering ====
* Blocked by:
** SRE ServiceOps: Rolling out PHP 7.2.26 to CI is blocked on creating a
PHP 7.2.2.6 package [[phab:T241224]]
** CP: [[phab:T241448]]
* Blocking:
** Core Platform: Quibble [[phab:T236680]]
* Updates:
** Train Health
*** week of Dec 16th: 1.35.0-wmf.11 - [[phab:T233859]]
*** This week: 1.35.0-wmf.14 - [[phab:T233862]]; now on group0. New logspam
is quiet so far
*** Next week: 1.35.0-wmf.15 - [[phab:T233863]]
*** January 27th-31st - No deploys at all (including train), All-Hands
=== Research ===
* Blocked by:
** SRE on recommendation API migration. Will reach out soon.
=== Scoring Platform ===
* Updates:
*** New draft topic model coming (New taxonomy --> Better labels --> Better
fitness) (FYI: Growth)
*** New revscoring version 2.6.3 -- better info formatting. Expanded
support for vectors.
*** Jade API on Beta
https://en.wikipedia.beta.wmflabs.org/w/api.php?action=help&modules=jadepro…
**** + updates to Jade API docs [[Extension:Jade/API]]
=== Search Platform ===
* Blocked by:
** Structured Data: Data dumps for SDC: [[phab:T221917]]
** Core: MW Job consumers sometimes pause for several minutes
[[phab:T224425]]
* Updates:
** Re-import OSM data at eqiad and codfw to temporarily fix current OSM
replication issues (including reducing replication interval, which might
fix the issue long term) - [[phab:T239728]]
** Migrate and redeploy discovery platform analytics jobs with kerberos
integration - [[phab:T241011]]
=== Security ===
* Blocking:
** Core Platform: OAuth 2.0 review [[phab:T239940]]
=== Site Reliability Engineering ===
* Blocking:
** Research on recommdendation-api migration to kubernetes. Working on it
** Product infrastructure on creating a buster nodejs image. Working on it
** Release Engineering - ServiceOps: Rolling out PHP 7.2.26 to CI is
blocked on creating a PHP 7.2.2.6 package [[phab:T241224]]
* Updates:
** The eqiad kubernetes cluster will be reinitialized on Tuesday Jan 14th
2020. The duration is expected to be up to 4 hours during EU morning. All
requests will have been routed beforehand to codfw to avoid causing issues
to users. Please refrain from trying to deploy to that cluster during that
time period.
** OKRs in final drafts, reach out if your team requires SRE involvement
All,
I've released a new version of Quibble just today, version 0.0.40.
This has a few changes, most notable further improvements to support the
work on testing Core Platform team's new RESTful API.
The full change log is available at
https://doc.wikimedia.org/quibble/changelog.html
Thank you to Clara Andrew-Wani, Andrew Wight, and Timo Tijhof for their
patches.
I will be updating CI jobs to use this progressively over the next few days.
Yours,
--
*James D. Forrester* (he/him <http://pronoun.is/he> or they/themself
<http://pronoun.is/they/.../themself>)
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello. I'd like to improve in our wiki {{efn}} / {{notelist}} so it will be
as in enwiki. I mean, if I use it now, I got that
text1{{efn|name=ref1|text2}}text3{{efn|name=ref1}}text4
==refs==
{{notelist}}
creates
text1[a]text3[a]text4
refs
a ^ *1.0 1.1* text2
while in enwiki there is
text1[a]text3[a]text4
refs
a ^ *a b* text2
Could you explain me, please, how can I set the format of reference group
multiple used reference? Thank you.
Igal (User:IKhitron)
Apologies for cross-posting
====
SEMANTiCS - 16th International Conference on Semantic Systems, September
7 - 10, 2020
Amsterdam, The Netherlands
https://2020-eu.semantics.cc/
====
= Important Dates (specific track dates are given below)
* Abstract Submission Deadline: April 18, 2020 (11:59 pm, Hawaiitime)
* Paper Submission Deadline: April 25, 2020
(11:59pm,Hawaii time)
* Notification of Acceptance: June 08, 2020 (11:59
pm,Hawaii time)
* Camera-Ready Paper: July 06, 2020
(11:59pm, Hawaii time)
= Read a detailed description of all available calls online:
https://2020-eu.semantics.cc/calls
= Submission via Easychair on
https://easychair.org/my/conference?conf=sem20eu#
Proceedings of SEMANTiCS 2020 EU are planned to be published by Springer
LNCS & CEUR. All proceedings will be made available open access.
SEMANTiCS 2020 EU particularly welcomes submissions on the following key
topics:
* Web Semantics & Linked (Open) Data
* Enterprise Knowledge Graphs, Graph Data Management and Deep Semantics
* Machine Learning & Deep Learning Techniques
* Semantic Information Management & Knowledge Integration
* Terminology, Thesaurus & Ontology Management
* Data Mining and Knowledge Discovery
* Reasoning, Rules and Policies
* Natural Language Processing
* Data Quality Management and Assurance
* Explainable Artificial Intelligence
* Semantics in Data Science
* Trust, Data Privacy, and Security with Semantic Technologies
* Economics of Data, Data Services and Data Ecosystems
-------
* Special Sub-Topic: Digital Humanities and Cultural Heritage
* Special Sub-Topic: LegalTech
* Special Sub-Topic: Blockchain and Semantics
We especially encourage contributions that illustrate the applicability
of the topics mentioned above for industrial purposes and/or illustrate
the business relevance of their contribution for specific industries.
We invite contributions to the following tracks:
= Read a detailed description of all available calls online:
https://2020-eu.semantics.cc/calls
== Research and Innovation Track ==
The Research and Innovation track at SEMANTiCS welcomes papers on novel
scientific research and/or innovations relevant to the topics of the
conference. Submissions must be original and must not have been
submitted for publication elsewhere. Papers must follow the guidelines
given in the author instructions, including references and optional
appendices. Each submission will be reviewed by several PC members who
will judge it based on its innovativeness, appropriateness, and impact
of results in terms of effectiveness at solving real problems.
= Important Dates:
* Abstract Submission Deadline: April 18, 2020 (11:59 pm, Hawaii
time)
* Paper Submission Deadline: April 25, 2020 (11:59 pm,
Hawaii time)
* Notification of Acceptance: June 08, 2020 (11:59 pm,
Hawaii time)
* Camera-Ready Paper: July 06, 2020 (11:59
pm, Hawaii time)
Author instructions: Reviews will be carried out in a single-blind mode.
Long papers should have a maximum length of 15 pages and short papers of
6 pages. Submissions should follow the guidelines of the Springer LNCS
format. The detailed Call for Research and Innovation papers is
available here: https://2020-eu.semantics.cc/calls
== Posters and Demos Track ==
The Posters and Demonstrations Track invites innovative work in
progress, late-breaking research and innovation results, and smaller
contributions in all fields related to the Semantic Web and Linked Data
in a broader sense. These include submissions on innovative applications
with impact on end users, such as demos of solutions that users may test
or that are yet in the conceptual phase but are worth discussing, and
also applications or pieces of code that may attract developers and
potential research or business partners.
= Important Dates:
* Paper Submission Deadline: June 22, 2020 (11:59 pm,
Hawaii time)
* Notification of Acceptance: July 22, 2020 (11:59 pm,
Hawaii time)
* Camera-Ready Paper: August 01, 2020 (11:59
pm, Hawaii time)
Author instructions: Proceedings are planned to be published via CEUR
Workshop Proceedings and should follow the guidelines of the Springer
LNCS format. The detailed Call for Poster and Demos papers is available
online.
== Industry and Use Case Track ==
Focusing strongly on industry needs and ground breaking technology
trends SEMANTICS invites presentations on enterprise solutions that deal
with semantic processing of data and/or information. A special focus of
Semantics 2019 will be on the convergence of machine learning techniques
and knowledge graphs. Additional topics of interest are Enterprise
Knowledge Graphs, Semantic AI & Machine Learning, Enterprise Data
Integration, Linked Data & Data Publishing, Semantic Search,
Recommendation Services, Thesaurus and/or Ontology Management, Text
Mining, Data Mining and any related fields. All submissions should have
a strong focus on real-world applications beyond the prototypical stage
and demonstrate the power of semantic systems!
= Important Dates:
* Paper Submission Deadline: May 25, 2020 (11:59
pm,Hawaii time)
* Notification of Acceptance: June 15, 2020 (11:59 pm,
Hawaii time)
* Camera-Ready Presentation: August 24, 2020 (11:59
pm, Hawaii time)
Submit your presentations here:
http://2020-eu.semantics.cc/submission-industry-presentations
== Workshops and Tutorials ==
Workshops and Tutorials at SEMANTiCS 2018 allow your organisation or
project to advance and promote your topics and gain increased
visibility. The workshops and tutorials will provide a forum for
presenting widely recognised contributions and findings to a diverse and
knowledgeable community. Furthermore, the event can be used as a
dissemination activity in the scope of large research projects or as a
closed format for research and commercial project consortia meetings.
= Important Dates for Workshops:
* Proposals WS Deadline: March 23, 2020 (11:59 pm,
Hawaii time)
* Notification of Acceptance: April 20, 2020 (11:59 pm,
Hawaii time)
= Important Dates for Tutorials (and other meetings, e.g. seminars,
show-cases, etc., without call for papers):
* Proposals Tutorial Deadline: May 11, 2020 (11:59 pm,
Hawaii time)
* Notification of Acceptance: June 01, 2020 (11:59
pm, Hawaii time)
== Special Calls ==
Special calls or sub-topics are dedicated towards specific topics that
are of special interest to the SEMANTiCS community. In case we receive a
sufficient amount of high quality submissions these topics will become
special tracks within the conference program. For 2020 SEMANTiCS
Amsterdam encourages submissions to the following sub-topics:
* Special Sub-Topic: Digital Humanities and Cultural Heritage
* Special Sub-Topic: LegalTech
* Special Sub-Topic: Blockchain and Semantics
Each sub-topic is managed by a distinct committee and encourages
submissions from the scientific or industrial domain. Scientific
submissions will undergo a thorough review process and will be published
in the conference proceedings in case of acceptance. Industrial
submissions will be evaluated and selected according to the quality
criteria of the industry track. We are looking forward to your submissions!
= Read a detailed description of all available calls online:
https://2020-eu.semantics.cc/calls