Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2022.01. This bundle is compatible with '''MediaWiki 1.36''' or
above and requires '''PHP 7.3.19''' 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-2022.01.tar…
* sha256sum: 0cb434980b399f7bac42a92c9f171b6c9041cb998e3b2b0fcf16daf58c43fe61
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.01.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/postorius/lists/mediawiki-i18n.lists.wikimedia.…
* Report bugs to: https://phabricator.wikimedia.org/project/view/1464/
Release notes for each extension are below.
-- Kartik Mistry
== Highlights ==
* '''MLEB now requires MediaWiki 1.36 and PHP 7.3.19'''
== Babel, cldr, CleanChanges and LocalisationUpdate ==
* Localisation and maintenance updates.
== Translate ==
* Fix Special:PageMigration - Page search suggestion does not work
({{phab|T217726}})
* Fix UI issue: the page moves from bottom to top when new messages
are loaded in List tab ({{phab|T295655}}, {{gerrit|738587}})
* Migrate tables to an abstract schema ({{phab|T268576}}, {{gerrit|735613}})
* Improve UX on Special:AggregateGroups and add collapsibility ({{phab|T90511}})
* Feature: Special:Translate: Make the target language visible in the
translation UI ({{phab|T296987}}, {{gerrit|743383}})
* Feature: Special:Translate: Make the target language selector a bit
more prominent ({{phab|T296986}}, {{gerrit|743397}})
* Performance: Special:ActiveLanguages should not perform slow queries
if results are cached ({{phab|T285314}}, {{gerrit|747122}})
* Feature: Add a new Javascript hook,
<code>mw.translate.translationView.stateChange</code>, fired when the
state is updated ({{phab|T297129}}, {{gerrit|745997}})
* Remove unused Configure extension integration ({{gerrit|751382}})
* Feature: Add reason dropdown on PageTranslationDeletePage
({{phab|T153542}}, {{gerrit|754490}})
* Add filters to <code>meta=messagegroupstats</code> API
({{phab|T298736}}, {{gerrit|752000}})
* Allow exporting AggregateMessageGroups in offline format via CLI
({{phab|T299493}}, {{phab|T263268}}, {{gerrit|755356}})
=== Breaking changes ===
* Remove backward compatibility for MW <= 1.35 ({{phab|T298788}},
{{gerrit|752166}})
== UniversalLanguageSelector ==
* Remove backward compatibility for MW <= 1.35
* Localisation and maintenance updates.
=== Font updates ===
* Add Awami Nastaliq font ({{phab|T290510}}, {{gerrit|737206}})
* Update OpenDyslexic ({{gerrit|737207}})
* Update GentiumPlus font ({{phab|T298613}}, {{gerrit|737206}})
--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com
This is just a note to inform and/or remind you that the WMF has its own
internal cloud solution, Wikimedia Cloud VPS[0]. If you are considering
starting up a project on AWS, Google Cloud, or the like, please consider
using our internal, already-paid-for service.
We provide:
- Easy virtual machine creation and management[1]
- Persistent block storage[2]
- Self-serve provisioning of Mariadb and PostgreSQL database servers[3]
(and self-serve management of Mariadb user access)
- Automatic HTTPS/TLS termination for web endpoints[4]
- Other things!
Start experimenting today with a project request here:
https://phabricator.wikimedia.org/project/view/2875/
Q. Isn't WMCS only for community/volunteer projects?
A. Nope. Dozens of internal WMF projects are already hosted on Cloud
VPS. The advantage of using a community-focused platform is that when
the time comes to involve volunteers, contractors, or WMDE staff in your
work, you will find the path to access simple and straightforward.
Q. Is WMCS a safe place for my data and passwords?
A. Yes. If you want to store user PII on a Cloud VPS system then there
will need to be some official discussion, but that is true for any PII
hosted on any cloud platform.
Q. What is this going to cost me or my department?
A. WMCS provides free, unmetered resources to all projects related to
the WMF's mission and the Wikimedia community. If you have extremely
large resource needs (dozens of cores or terabytes of data) then there
may be some discussion about long-term cloud capacity but we don't have
a billing department and don't plan on ever having one.
Q. What kind of software can I host on Cloud VPS?
A. Any software with an OSI-approved license can be freely installed.
Q. I really need <specific feature that I know is available on AWS>. Do
you support that?
A. Maybe! Or even if we don't, we might be about to. Feel free to
respond to this ticket, or contact a member of the WMCS team via email,
slack, or IRC.
Q. Why would I use Cloud VPS when I already know how to use AWS?
A. There are so many reasons! Some of them are financial, ideological,
and legal, but the biggest reason is that we are here to help you. WMCS
staff and volunteers provide ongoing support for Cloud VPS via
phabricator and IRC, and we care about whether or not your project succeeds.
Thank you for reading!
[0] https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS
[1] https://wikitech.wikimedia.org/wiki/Help:Horizon_FAQ
[2] https://wikitech.wikimedia.org/wiki/Cinder
[3]
https://wikitech.wikimedia.org/wiki/Help:Adding_a_Database_to_a_Cloud_VPS_P…
[4]
https://wikitech.wikimedia.org/wiki/Help:Using_a_web_proxy_to_reach_Cloud_V…
🚂🌈Summary of 1.38.0-wmf.18 train deployment
This email is a summary of the Wikimedia production deployment of
1.38.0-wmf.18
- Conductor: Jeena Huneidi
- Backup Conductor: Mukunda Modell
- Blocker Task: T293959 <https://phabricator.wikimedia.org/T293959>
- Current Status <https://versions.toolforge.org>
🔢 According to our calculations
Sparklines comparing with the last 5 trains.
- 287 Patches ▆▇▁██
- 0 Rollbacks ▂▄▁█▁
- 0 Days of delay ▁▂▂█▁
- 13 Blockers ▄▃▁▃█
😻 Trainbow Love 🎉 Thanks to folks who reported or resolved blockers:
- Kosta Harlan
- Brennen Bearnes
- Tyler Cipriani
- Peter Pelberg
- Taavi Väänänen
- Umherirrender
- Zabe
- James D. Forrester
- Samuel
- Bartosz Dziewoński
- Jon Robson
- Gergő Tisza
--
Jeena Huneidi
Software Engineer, Release Engineering
Wikimedia Foundation
Hi,
excited to share that we've released OOUI v0.43.0 last Thursday.
It will rollout on the normal train tomorrow, Tuesday, 18 January 2022.
Highlights in this release since v0.42.0:
- MessageWidget features now a `showClose` option for the optional
closing notices et al.
- MenuSelectWidget highlights the first selectable option instead of the
visible one. Thanks to volunteer Func.
- Numerous icon additions and improvements are featured:
-- The only nominal breaking change is removal of the `destructive`
variant from 'close' icon. The 'close' icon shouldn't be used for removing
or deleting things for user-experience consistency, please revisit your
codebase and use 'trash' icon instead.
-- 'stopHand' icon was deprecated and renamed to 'hand' icon while being
aligned to the Design Style Guide's icon guidelines[0].
-- 'watchlist' icon was added. Thanks to Alex Hollender.
-- Large number of 'bold' and 'italic' icons for specific languages
were aligned to the guidelines. Thanks to new Design Systems team
peer, Bárbara Martínez Calvo.
I'm specifically excited about these changes as they emphasize our goal
to provide first-class experience for our diverse language communities.
With updated OOUI demos[1] and demos of future Vue.js-based[2] UI
toolkit Codex, you're now able to see and compare all per language
icons. Thanks to Roan Kattouw and Ed Sanders.
- Last, but not least, more than 20 different performance optimizations
across widgets were included in this release, thanks to Thiemo Kreuz
at current work focus by Wikimedia Deutschland.
One call for notice here, widgets don't feature default implicit
`aria-disabled="false"` any more to save bytes sent to client,
only when set dynamically.
There was one case of a template breakage written to check for
this –now missing attribute. Please carefully test if this might affect
your
code.–
You can find details on additional new features, code-level, styling
and interaction design amendments, and all improvements since v0.42.0
in the full changelog[4].
If you have any further queries or need help dealing with deprecating
changes, please let me know.
As always, interactive demos and library documentation is available
on mediawiki.org[5], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[6].
OOUI version: 0.43.0
MediaWiki version: 1.38.0-wmf.18[7]
Date of deployment to production: Regular train, starting Tuesday 18 January
[0] - https://design.wikimedia.org/style-guide/visual-style_icons.html
[1] -
https://doc.wikimedia.org/oojs-ui/master/demos/?page=icons&theme=wikimediau…
[2] - https://www.mediawiki.org/wiki/Vue.js
[3] - https://gerrit.wikimedia.org/g/oojs/ui/+/v0.43.0/History.md
[4] - https://www.mediawiki.org/wiki/OOUI
[5] - https://doc.wikimedia.org/oojs-ui/master/
[6] - https://wikitech.wikimedia.org/wiki/Deployments#Tuesday,_January_18
Best,
Volker