Greetings! I've written a brief blog that describes how Wikimedia uses
optional build steps as an enhancement to ResourceLoader and our
evolving pipeline. If you use ResourceLoader in your projects, you may
find it helpful:
https://phabricator.wikimedia.org/phame/post/view/206/all_code_is_built/
Thank you to the following reviewers for their great feedback: Jan
Drewniak, Santhosh Thottingal, Daniel Cipoletti, Joe Walsh, Bernd
Sitzmann, and Mónica Pinedo Bajo.
Stephen
The 1.36.0-wmf.1 version of MediaWiki is no longer blocked[0].
The new version is deployed to all groups[1]. Thanks to everyone who helped
unblock the train!
-- Your humble train trawler
[0]. https://phabricator.wikimedia.org/T257969
[1]. <https://versions.toolforge.org/>
--
Jeena Huneidi
Software Engineer, Release Engineering
Wikimedia Foundation
<tl;dr>: Make discourse-mediawiki.wmflabs.org read-only by end of
August. See and comment on https://phabricator.wikimedia.org/T247010
Hi everyone,
In January 2018, an experimental instance of the Q&A platform
"Discourse" was set up for developer support at
https://discourse-mediawiki.wmflabs.org .
See https://phabricator.wikimedia.org/T180854 .
Since its launch, the usage of this instance has declined:
https://phabricator.wikimedia.org/T247010#6270883
On average, there are two users who are engaged daily.
Other support venues which exist in parallel are much more active, such
as IRC, mailing lists, [[mw:Project:Support_desk]], [[meta:Tech]],
local technical village pumps, newsletters, Zulip for outreach
programs, or other third-party sites such as mwusers.org,
StackExchange.com, or Reddit.
Discontinuing the least frequented venue (which unfortunately is
Discourse though it seems to be a great communication platform) would
keep us from further fragmenting our conversations and efforts.
Planning, implementing, establishing and running a centralized
Wikimedia developer support venue on production infrastructure
(puppetization, data backups, uptime, etc) would require significant
technical and "social" capacity. If Discourse was to be further
evaluated, https://phabricator.wikimedia.org/T155678 and its subtasks
list part of the remaining needed work.
I propose to make discourse-mediawiki.wmflabs.org read-only by the end
of August 2020.
Please comment on https://phabricator.wikimedia.org/T247010 if you have
thoughts to share instead of replying to this message.
Because keeping conversations in one place. ;)
Thanks a lot!
andre
--
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2020.07. This bundle is compatible with MediaWiki 1.33 or above
and requires PHP 7.2 or above.
Next MLEB is expected to be released in 3 months. If there are very
important bug fixes, we will do an intermediate release. Please give
us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.07.tar…
* sha256sum: 7334f6c0f4e00a451d976c81024c955061cffc3466d8a03fd223733992d0a2d5
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.07.tar…
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Babel, CleanChanges and LocalisationUpdate ==
* Localisation and maintenance updates.
== cldr ==
* Update to cldr 37.
== Translate ==
* Fixes to moving and deletion of translatable pages.
([[phab:T168591|Phab:T168591]])
* Improved escape sequence handling for the Android XML file format.
([[phab:T192062|Phab:T192062]])
* Display a help message when editing a translatable page source.
([[phab:T192052|Phab:T192052]])
* Translations are now published instead of saved, for consistency
with rest of MediaWiki. ([[phab:T131132|Phab:T131132]])
* Updated Google Translate integration ([[phab:T33695|Phab:T33695]])
* Patrolling of edits to translation pages is allowed.
([[phab:T151172|Phab:T151172]])
* Message index should now be more robust and issues like "the message
does not correspond to any message group" when translating should no
longer occur. ([[phab:T221119|Phab:T221119]])
* Ensure plural keyword other is always present in exports for yaml
and json. ([[gerrit:c/mediawiki/extensions/Translate/+/603470|Gerrit
Patch]])
* Interface changes to message validator code. If you have custom
validators, you need to migrate them to a new interface.
([[gerrit:c/mediawiki/extensions/Translate/+/604400|Gerrit Patch]])
* Translatable pages can now prevent wrapping of outdated (and in
future untranslated) units by using <translate nowrap> syntax.<!--
unescape for email -->([[phab:T256625|Phab:T256625]])
* Slight changes to Special:PageTranslation interface.
([[gerrit:c/mediawiki/extensions/Translate/+/610073|Gerrit Patch]])
== UniversalLanguageSelector ==
* SkinTemplateOutputPageBeforeExec is deprecated, use SkinAfterPortlet
instead. ([[phab:T253178|phab:T253178]])
=== Input Methods ===
* Added Baoulé tilde keyboard.
--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com
The 1.36.0-wmf.1 version of MediaWiki is blocked[0].
The new version is deployed to group(s){0,1}[1], but can proceed no
further until these issues are resolved:
* RevisionAccessException when trying to import files with
FileImporter - https://phabricator.wikimedia.org/T258666
Once these issues are resolved train can resume. If these issues are
resolved on a Friday the train will resume Monday.
Thank you for your help resolving these issues!
-- Your humble train trawler
[0]. <https://phabricator.wikimedia.org/T257969>
[1]. <https://versions.toolforge.org/>
--
Jeena Huneidi
Software Engineer, Release Engineering
Wikimedia Foundation
Hi,
for HTML version see https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-07-22
Željko
--
= 2020-07-22 =
== Callouts ==
* Release Engineering
** [All] Review guidance at [[wikitech:Deployments/Covid-19]] and Code
Deployment Office Hour at 17:00UTC in #wikimedia-office
** "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:
** Update the wiki page instead of the etherpad page
(https://etherpad.wikimedia.org/p/Scrum-of-Scrums)
== Product ==
=== Web ===
* Updates:
** '''Summary''': deploying Desktop Improvements Project (DIP) to
select wikis, starting WVUI Vector integration and network client.
** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project
(Vector / DIP)]]:
*** [[phab:T177108|<nowiki>TypeError:
$.collapsibleTabs.getSettings(...) is undefined from Vector
skin</nowiki>]]
*** [[phab:T257518|<nowiki>[Bug] Max-Width Layout: Sidebar overlaps
footer when its height is longer than the content height</nowiki>]]
*** [[phab:T255727|<nowiki>Make collapsible sidebar persistent for
logged-in users</nowiki>]]
*** [[phab:T254851|<nowiki>Current checkbox hack doesn't provide
<Enter> or <Space> as toggle action</nowiki>]]
*** [[phab:T254228|<nowiki>Deploy new version of vector skin to all
wikis as a user preference</nowiki>]]
*** [[phab:T254227|<nowiki>Switch test wikis to new version of vector
by default</nowiki>]]
*** [[phab:T253842|<nowiki>Fix the printable versions of modern
Vector</nowiki>]]
*** [[phab:T249363|<nowiki>Move the existing search to the header in
preparation for Vue.js search development</nowiki>]]
*** [[phab:T246420|<nowiki>Limit content width, and refine alignment &
styling of relevant elements</nowiki>]]
*** [[phab:T167956|<nowiki>Deprecate and remove printable version
mode</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:T237036|<nowiki>ext.uls.interface should set targets and
explicitly not target the Minerva skin</nowiki>]]
*** [[phab:T235712|<nowiki>Fix the most common "Module not loadable on
target mobile" warnings (Oct 2019)</nowiki>]]
*** [[phab:T257953|<nowiki>[Technical debt payoff] Drop
MFSpecialCaseMainPage, from MobileFrontend</nowiki>]]
*** [[phab:T254287|<nowiki>Final warning: Mobile main page special
casing will be disabled July </nowiki>]]
*** [[phab:T240622|<nowiki>[Technical debt payoff] Remove
InlineDiffFormatter and InlineDifferenceEngine from
MobileFrontend</nowiki>]]
*** [[phab:T32405|<nowiki>[EPIC] MobileFrontend extension should stop
special-casing main page</nowiki>]]
** Standardization
*** [[phab:T232903|<nowiki>Standardise `.mw-infobox` by relying on
`.warningbox`</nowiki>]]
** Portals
*** [[phab:T128546|<nowiki>[Recurring Task] Update Wikipedia and
sister projects portals statistics</nowiki>]]
** QuickSurveys
*** [[phab:T246977|<nowiki>Run baseline quicksurvey on test wikis</nowiki>]]
** Miscellaneous
*** [[phab:T138401|<nowiki>Replace jsduck with JSDoc3 across all
Wikimedia code bases</nowiki>]]
=== Structured Data ===
* Updates:
** working on adding schema.org licensing data to article pages
** ongoing work on mediasearch
== Technology ==
=== Fundraising Tech ===
* Updates:
** Investigating American Express card failures in India
** Fixing how we set up one-time card donations to make them possible
to convert to monthly recurring
** Refining sync process for employer matching gift policies
** Investigating seemingly unintended duplicate donations
** Updating custom CiviCRM report used to track fraud.
=== Engineering Productivity ===
==== Release Engineering ====
* Updates:
** [All] Deployments/Covid-19 [[wikitech:Deployments/Covid-19]]
** Train Health
*** Last week: 1.35.0-wmf.41 - [[phab:T256669]]
*** This week: 1.36.0-wmf.1 - [[phab:T257969]]
*** Next week: 1.36.0-wmf.2 - [[phab:T257970]]
=== Site Reliability Engineering ===
* Updates:
** mobileapps traffic is being migrated to kubernetes.
Hi Everyone,
It's time for Wikimedia Tech Talks 2020 Episode 5! *This talk will take
place next Wednesday on 22 July 2020 at 17:00 UTC.*
*Title:* Beyond Wikipedia - Knowledge that even a computer can understand
*Speaker*: Zbyszko Papierski, Senior Software Engineer
<https://wikimediafoundation.org/profile/zbyszko-papierski/>
*Summary:* Everybody knows what Wikipedia is, right? This magnificent
source of knowledge has been helping countless people with their everyday
lives for nearly two decades. Whether you want to know how to calculate the
circumference of the circle, whether hyenas are pack animals or what really
happened to the Ottoman Empire - Wikipedia’s got your back.
Well, unless you happen to be a computer.
One issue with Wikipedia is that knowledge there isn’t very well
structured. There are links to other pages, sure - but unless you actually
understand the text, you won’t understand what the link actually is. This
is, of course, a field day for AI/ML experts - and there are a lot of
people already scavenging Wikipedia for any meaningful relations.
Fortunately, this is not the only way.
Enter Wikidata - Wikipedia’s younger sister. Wikidata is also a source of
knowledge curated and provided by a community of volunteers but presented
in a relational graph format. Structuring the knowledge has huge
ramifications - it not only makes it easier to digest by software but also
allows you to infer new knowledge.
There are different ways for developers to interact with Wikidata, but
we’ll focus on Wikidata Query Service - a service my team is responsible
for. It provides a queryable interface - using an RDF graph language called
SPARQL (not to be confused with a hundred other things in IT with “spark”
in the name).
Let’s do some discovery!
*The link to the Youtube Livestream can be found here: *
https://www.youtube.com/watch?v=jNNy8ALGjaE
During the live talk, you are invited to join the discussion on IRC at
#wikimedia-office
You can browse 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: This is a public talk. Feel free to distribute through appropriate
email and social channels!
Kindly,
Sarah R. Rodlund
Senior Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org