Hi,
for HTML version see https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-06-24
Željko
--
= 2020-06-24 =
== Callouts ==
* SRE DBAs:
** m1-master failover, etherpad will have minor issues on Thursday Jun 25th
* Release Engineering
** [All] Review guidance at [[wikitech:Deployments/Covid-19]] and Code
Deployment Office Hour at 17:00UTC in #wikimedia-office
** Gerrit upgrade on Saturday, 27th of June
<https://lists.wikimedia.org/pipermail/wikitech-l/2020-June/093526.html>
** "scap sync" will be renamed to "scap sync-world" in the next
release. If you use "scap sync" non-interactively, please add a note
to: [[phab:T250302]] (and also, explain why you're using it)
** scap sync now has option --canary-wait-time; [[phab:T217924]]
== SoS Meeting Bookkeeping ==
* Updates:
** looking for somebody to facilitate on 2020-07-01
== Product ==
=== iOS native app ===
* Updates:
** Bug fix 6.6.1 to be released this week [[phab:project/view/4574]]
** Early development and research on new experiments for 6.7
[[phab:project/view/4661]]
=== Android native app ===
* Updates:
** Completed new user contribution screen, to be deployed to Beta this week.
** Design refresh of explore feed cards and the main screen.
=== Web ===
* Updates:
** '''Summary''': sidebar instrumentation and content width limiting
for Desktop Improvements Project (DIP), component baseline taskout for
Vue.js search.
** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project
(Vector / DIP)]]:
*** [[phab:T255574|<nowiki>Watchlist star gone on Vector</nowiki>]]
*** [[phab:T237036|<nowiki>ext.uls.interface should set targets and
explicitly not target the Minerva skin</nowiki>]]
*** [[phab:T254546|<nowiki>Language portlet no longer at the bottom of
sidebar</nowiki>]]
*** [[phab:T253938|<nowiki>Future proof addPortletLink</nowiki>]]
*** [[phab:T250282|<nowiki>Build sidebar instrumentation</nowiki>]]
*** [[phab:T246419|<nowiki>Build collapsible sidebar and sidebar
button </nowiki>]]
*** [[phab:T60137|<nowiki>Deprecate the
SkinTemplateOutputPageBeforeExec hook</nowiki>]]
*** [[phab:T252774|<nowiki>Checkbox and mediawiki.toc.styles styles
should be merged into a single ResourceLoader module</nowiki>]]
*** [[phab:T251212|<nowiki>[Dev] Drop VectorTemplate usage in Vector</nowiki>]]
*** [[phab:T244392|Vue.js search case study]]:
**** See [[Reading/Web/Desktop Improvements/Vue.js case study/Status
log|weekly status updates]].
** Mobile website (MinervaNeue / MobileFrontend):
*** [[phab:T235712|<nowiki>Fix the most common "Module not loadable on
target mobile" warnings (Oct 2019)</nowiki>]]
*** [[phab:T255630|<nowiki>Sorry toast doesn't show for mobile editor
on pages you can't edit (Uncaught TypeError: m.show is not a function,
Uncaught TypeError: Cannot read property 'show' of
undefined)</nowiki>]]
*** [[phab:T240622|<nowiki>[Technical debt payoff] Remove
InlineDiffFormatter and InlineDifferenceEngine from
MobileFrontend</nowiki>]]
** Standardization
*** [[phab:T255717|<nowiki>Scope and use of mediawiki.skinning's
'elements.less' file</nowiki>]]
*** [[phab:T255229|<nowiki>Align mediawiki.ui/variables.less variables
to CSS variable naming scheme</nowiki>]]
*** [[phab:T255225|<nowiki>Replace non-standard color palette .new
color with Red50 `#d33`</nowiki>]]
*** [[phab:T66477|<nowiki>Vector: Use semantic HTML5 elements where
applicable</nowiki>]]
** Miscellaneous
*** [[phab:T255814|<nowiki>Latest version of SkinBlueSpiceCalumma is
not compatible with current version of Chameleon</nowiki>]]
*** [[phab:T255299|<nowiki>Some images appear when Show Images is
disabled</nowiki>]]
*** [[phab:T253045|<nowiki>TypeError: self.hide is not a function. (In
'self.hide()', 'self.hide' is undefined)</nowiki>]]
=== Structured Data ===
* Updates:
** mediasearch design work, vue prototype work and backend changes
== Technology ==
=== Fundraising Tech ===
* Updates:
** More work on employer matching gifts: [[phab:T249924]], [[phab:T251201]]
** CentralNotice subnational targeting and banner templates going out
on train this week [[phab:T255476]]
** Improving efficiency of data export to bulk mail provider [[phab:T253152]]
** Tweaking config of card entry forms to avoid confusion [[phab:T254032]]
** Monitoring converted recurring donations now that a month has
passed, ready to convert the rest from our main card processor's old
API to their new API [[phab:T256181]]
** Adding a redirect feature to hide banners now that many browsers
don't allow pixels to set cookies: [[phab:T251780]]
=== Engineering Productivity ===
==== Release Engineering ====
* Updates:
** scap sync now has option --canary-wait-time; [[phab:T217924]]
** [All] Deployments/Covid-19 [[wikitech:Deployments/Covid-19]]
** Train Health
*** Last week: 1.35.0-wmf.37 - [[phab:T254174]]
*** This week: 1.35.0-wmf.38 - [[phab:T254175]]
*** Next week: 1.35.0-wmf.39 - [[phab:T254176]]
=== Site Reliability Engineering ===
* Updates:
** Working on actionables for the sessionstore incident
** m1-master failover, etherpad will have minor issues on Thursday Jun 25th
** Working on moving switching proton traffic to kubernetes
As per the MediaWiki version lifecycle [1], I would like to announce the
formal end of life (EOL) of MediaWiki 1.33 as of next week, Tuesday June
30, 2020.
This means that MediaWiki 1.33 will no longer receive maintenance or
security backports (barring an unforseen issues with the 1.33.4 release
today). It is therefore strongly discouraged that you continue to use it.
It is recommended to upgrade to MediaWiki 1.34 (due to become EOL in
November 2020). The current Long Term Support (LTS) version of MediaWiki,
MediaWiki 1.31, is however older (and downgrading is not supported. The
delayed next LTS (MediaWiki 1.35) is currently due to be released in early
August 2020, and will be supported until at least June 2023.
MediaWiki 1.34 bumps the required PHP version from 7.0 in 1.33 (which is
unsupported upstream), to PHP 7.2.9 or later.
Thanks!
Sam Reed
[1] https://www.mediawiki.org/wiki/Version_lifecycle
// sorry for cross-posting
Hello,
A lot of heated discussion occur on talk pages – thus, edit conflicts
happen on talk pages a lot. To be able to solve these more effectively, the
Technical Wishes team at Wikimedia Germany is designing an additional user
interface for this situation. This interface is shown to you when you write
on a discussion page and another person writes a discussion post in the
same line and saves it before you do. With this additional editing conflict
interface you can adjust the order of the comments and edit your comment.
If you'd like to know more about this feature, please visit the project
page [1].
This interface is created as a result of the Technical Wishes survey [2] in
2015, in which the German Wikipedia community wished for a simpler way to
resolve edit conflicts. For regular edit conflicts on article pages, the two
column conflict user interface was created, which has been available as a
beta feature since November 2018. The plan is to make this additional
interface for talk pages available in a few months.
We are inviting everyone to have a look at the planned feature and let us
know what you think on our central feedback page [3]! -- For the Technical
Wishes Team: Max Klemm
[1]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Edit_Conflicts#Edit_c…
[2]
https://de.wikipedia.org/wiki/Wikipedia:Umfragen/Technische_W%C3%BCnsche_20…
[3] https://www.mediawiki.org/wiki/Help_talk:Two_Column_Edit_Conflict_View
--
Max Klemm
Working Student Community Communication for Technical Wishes
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0https://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.
Apologies for cross-posting
Over the last year, the DBpedia core team has consolidated great amount
of technology around DBpedia. This tutorial is targeted for developers
(in particular of DBpedia Chapters) that wish to learn how to replicate
local infrastructure such as loading and hosting an own SPARQL endpoint.
A core focus will also be the new DBpedia Stack, which contains several
dockerized applications that are automatically loading data from the
databus. The tutorial will cover the following topics:
- Using Databus collections (Download)
- Creating customized Databus collections
- Uploading data to the Databus
- Using collections in Databus-ready Docker applications
- Creating dockerized applications for the DBpedia Stack
The first tutorial will be held on July 1st, 2020 at 9:00-10:00 am
CEST.The tutorial will be repeated once more at a later time.
# Quick Facts
- Web URL:https://wiki.dbpedia.org/tutorials/1st-dbpedia-stack-tutorial
- When: July 1st, 2020 9:00-10:00 am CEST
- Where: The tutorial will be organized online. Registration is required
though.
- Databus: https://databus.dbpedia.org/
# Registration
Attending the DBpedia Stack tutorial is free. Registration is required
though. After the registration for the event, you will receive an email
with more instructions. Please register here to be part of the meeting:
https://docs.google.com/forms/d/e/1FAIpQLSfI3x5YE6bYmxTM57001MBfy5_1EjyjUV5…
# Program
- Please check the schedule for the upcoming DBpedia Stack Tutorial
here: https://wiki.dbpedia.org/tutorials/1st-dbpedia-stack-tutorial
# Organisation
- Milan Dojchinovski, AKSW/KILT, DBpedia Association
- Jan Forberg, AKSW/KILT, DBpedia Association
- Sebastian Hellmann, AKSW/KILT, DBpedia Association
We are looking forward to meeting you online!
With kind regards,
The DBpedia Team
Hi all,
Tomorrow we will be issuing a security and maintenance release to all
supported branches of MediaWiki.
The new releases will be:
- 1.34.2
- 1.33.4
- 1.31.8
This will resolve one minor issue in MediaWiki core, and also includes some
fixes previously committed to git, including minor security and hardening
patches along with bug fixes included for maintenance reasons.
We've noted that these issues are minor, and as such you don't need to
apply them as quickly as with other security releases, if you're unable to
do so. We therefore decided to continue with getting the security (and
maintenance) release out for this quarter as planned, even with the global
situation as is.
We will make the fixes available in these respective release branches, and
also master. Tarballs will be available for the above mentioned point
releases as well.
A summary of some of the security fixes that have gone into non-bundled
MediaWiki extensions will also follow.
As per the MediaWiki Version lifecycle [1], June 2020 is the scheduled EOL
date for the REL1_33. 1.33.4 will therefore be the final release of the
MediaWiki 1.33 branch, barring any unforeseen issues.
[1] https://www.mediawiki.org/wiki/Version_lifecycle
Thanks!
Sam
Hello,
We will be switching over m1 database primary master (
https://phabricator.wikimedia.org/T254556#6247415) , which holds the
etherpad database.
This means that on Thursday 25th at 08:00AM UTC Etherpad will be on
read-only for a few seconds.
Communication will happen on #wikimedia-operations IRC channel.
Sorry for the inconveniences.
Manuel.
Hello all,
This is a reminder that the "Writing Wikidata queries" workshop is coming
up! It will take place this Sunday, June 21st at 9 am IST on the Zoom
platform:
https://wikimedia.zoom.us/j/99498586419
More details of the workshop are here:
https://meta.wikimedia.org/wiki/SWT_Indic_Workshop_Series_2020/Workshops#Wr…
.
Remember to bring a computer with you as hands-on activities will be a part
of this workshop.
We look forward to your participation! :)
Cheers,
SWT Indic Workshop Series Team
Hi,
in my first attempt at jumping into improving a mediawiki extension, I am failing at a very basic step.
I want to make the extension configurable and followed this advice:
[ https://www.mediawiki.org/wiki/Manual:Configuration_for_developers | https://www.mediawiki.org/wiki/Manual:Configuration_for_developers ]
this is my extension.json I added:
"config": {
"ShariffServices": {
"value": "["twitter","facebook","pinterest"]",
"description": "configuration of available services"
}
},
"ConfigRegistry": {
"Shariff": "GlobalVarConfig::newInstance"
},
now in the baisc PHP file of the extension, I am trying
use MediaWiki\MediaWikiServices;
$config = MediaWikiServices::getInstance()->getConfigFactory()->makeConfig( 'Shariff' );
$services = $config->get ('Services');
but the last line leads to
[XtqcaewKU0Q3UCukKmZO9AAAABM] /index.php?title=Main_Page Error from line 3061 of ../includes/parser/Parser.php: Call to a member function matchStartAndRemove() on null
Backtrace:
#0 ..includes/parser/Preprocessor_DOM.php(1277): Parser->braceSubstitution(array, PPFrame_DOM)
#1 ../includes/parser/Parser.php(2942): PPFrame_DOM->expand(DOMElement, integer)
#2 ../includes/parser/Parser.php(701): Parser->replaceVariables(string, PPFrame_DOM)
#3 ../includes/parser/Parser.php(4717): Parser->preprocess(string, Title, ParserOptions)
#4 ../includes/cache/MessageCache.php(1089): Parser->transformMsg(string, ParserOptions, Title)
#5 ../includes/Message.php(1273): MessageCache->transform(string, boolean, LanguageEn, Title)
#6 ../includes/Message.php(874): Message->transformText(string)
#7 ../includes/Message.php(934): Message->toString(string)
#8 ../includes/OutputPage.php(902): Message->text()
#9 /../includes/OutputPage.php(949): OutputPage->setHTMLTitle(Message)
#10 ../includes/OutputPage.php(2424): OutputPage->setPageTitle(string)
#11 /../includes/exception/MWExceptionRenderer.php(128): OutputPage->prepareErrorPage(string)
#12 ../includes/exception/MWExceptionRenderer.php(54): MWExceptionRenderer::reportHTML(ConfigException)
#13 ../includes/exception/MWExceptionHandler.php(75): MWExceptionRenderer::output(ConfigException, integer)
#14 ../includes/exception/MWExceptionHandler.php(149): MWExceptionHandler::report(ConfigException)
#15 ../includes/MediaWiki.php(551): MWExceptionHandler::handleException(ConfigException)
#16 ../index.php(42): MediaWiki->run()
#17 {main}
What am I doing wrong?
As far is I understand it, using DefaultSettings.php is outdated, we should be using extension.json. But I can't get it to work.
Can anybody point me to a simple extension that uses this mechanism correctly?
so long,
Bernhard