Hello all,
The next language community meeting is coming up in a few weeks - *February
21st, 12:00 pm UTC*.
If you're interested, you can sign up on this wiki page: <
https://www.mediawiki.org/w/index.php?title=Wikimedia_Language_engineering/…
>.
This meeting is for individuals involved in creating content or managing
technical aspects across different language communities. This will be a
participant-driven meeting, where we collectively discuss specific
technical issues related to language wikis and work together to find
possible solutions. This could involve anything from fixing a broken
template on the Kurdish wiki to brainstorming ideas for growing content on
the Tulu Wiktionary, currently in the Wikimedia Incubator, or celebrating
the creation of Fon Wikipedia, to using MinT for content translation.
Feel free to add any *technical updates* related to your project or ideas
for *problem-solving* discussion that you would like to share during the
meeting to the notes document here: <
https://etherpad.wikimedia.org/p/language-community-meeting-february-2024>.
If you need interpretation support from English to another language, please
let us know by sending an email to ssethi(a)wikimedia.org.
Looking forward to your participation!
Cheers,
Jon, Mary & Srishti
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi,
I query special pages through API (concretely Special:UnconnectedPages),
and I noticed that main namespace articles are yielded first.
It seems that pages are ordered by namespace numbers.
Is it a guaranteed behaviour?
(If so, I can break from the loop at te first page not in 0 namespace which
would be nice.)
--
Bináris
Hello everyone,
I am glad to inform you that as part of our initial experimentations with
Parsoid Read Views, Parsoid is turned on as the default read views renderer
in Wikitech for DiscussionTools. Here's the rationale
<https://www.mediawiki.org/wiki/Parsoid/Parser_Unification/Confidence_Framew…>
behind our confidence to roll-out this experimental feature and collect
feedback.
This is an opportunity to experiment the changes confidently before we
start rolling out more wikis.
If this disrupts your workflow, don’t worry you can still opt out through a
user preference or turn Parsoid off on the page you’re navigating in
the Tools submenu.
To report bugs and issues, please look at our known issues
<https://www.mediawiki.org/wiki/Parsoid/Parser_Unification/Known_Issues>
documentation
and if you found a new bug please create a phab ticket and tag the Content
Transform Team in Phabricator
<https://phabricator.wikimedia.org/project/view/5846> or send us a message
in our slack channel #content-transform-team.
More relevant info about our roll-out strategy can be found on this wiki
page
<https://m.mediawiki.org/wiki/Parsoid/Parser_Unification/Confidence_Framework>
.
Best regards,
Mateus
Hi all,
Today when playing around Wikipedia iOS app I'm surprised to find out that the Chinese language variant support is still somewhat broken. There is no zh-cn variant available, only zh-hans (displayed as "Simplified Chinese"). I haven't touched the Android app for a while, but in my last review it mistakenly includes zh-hans and zh-hant variants.
As I mentioned in https://phabricator.wikimedia.org/T305319, the correct list of variants the app should include should be: zh-cn, zh-sg, zh-my, zh-tw, zh-mo, zh-hk. Other zh variants have incomplete conversion, thus should be excluded.
I hope somebody at the relevant team could reach out to me and discuss possible solutions. If you don't understand the reason to do this I can give a detailed explanation. I believe this task should not be triaged as "Low" because it has negative impacts on Chinese readers.
Best regards,
Diskdance
Hello,
Recently I'm researching Parsoid's design as MW is migrating to Parsoid. I found out that due to its single-pass tokenizing design, templates are not handled textually as the legacy parser does.
This is good as the HTML now have information about which template they are transcluded from. However, https://www.mediawiki.org/wiki/Parsoid/limitations says "We have since decided to use the PHP preprocessor for template expansions, which side-steps these issues by reverting to the traditional textual preprocessor pass". Is this still true now?
Best regards,
Diskdance
Hi all,
OOUI v0.49.0 was released yesterday. It will be rolled out in MediaWiki via the deployment train starting on Tuesday, 13 February 2024.
There are several breaking changes in this release. Please check your code carefully and make the suggested updates as necessary.
- SearchInputWidget, TextInputWidget: getSaneType() has been changed to getValidType() to reflect more inclusive language. Please check your code to make sure you're using the updated method name.
- SelectWidget: getItemMatcher() no longer supports the value of `true` for the mode argument, which has been deprecated since v0.30.4. Use `'exact'` instead.
- WindowManager: The alias toggleAriaIsolation(), deprecated since v0.44.1, has been removed. Use toggleIsolation() instead.
Other changes include:
- JavaScript documentation has been migrated from JSDuck to JSDoc3.
- The Less variable @line-height-base, deprecated since v0.42.0, has been removed. Use @line-height-label instead.
You can find a full list of changes in the changelog[1].
As always, interactive demos[2] and code-level documentation[3] are available on doc.wikimedia.org, along with library documentation[4] on mediawiki.org.
[1] - https://gerrit.wikimedia.org/g/oojs/ui/+/v0.49.0/History.md
[2] - https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[3] - https://doc.wikimedia.org/oojs-ui/master/js
[4] - https://www.mediawiki.org/wiki/OOUI
Happy UI-ing,Anne
--
Anne Tomasevich (she/her)
Staff Software Engineer, Design System
Wikimedia Foundation
I'm updating some blubberised repos that a colleague of mine created some
time ago and I'm not sure what base images from the Docker registry
<https://docker-registry.wikimedia.org/> are the best to use.
For instance, one repo uses docker-registry.wikimedia.org/wikimedia-buster
as base image in .pipeline/blubber.yaml. I thought I'd update to Bookworm
as the newest stable Debian release, but there is no image
"wikimedia-bookworm", only "bookworm". I'd like to know what's different in
the the ones with the wikimedia- prefix.
There are also several different ones for Python, e.g. "python3",
"python3-buster" and "python3-build-buster".
Is there documentation somewhere or links to repos where I can see what
Docker or Blubber files were used to create them?
*Sebastian Berlin*
Utvecklare/*Developer*
Wikimedia Sverige (WMSE)
E-post/*E-Mail*: sebastian.berlin(a)wikimedia.se
Telefon/*Phone*: (+46) 0707 - 92 03 84
The 1.42.0-wmf.18 version of MediaWiki is blocked[0].
The new version is currently deployed to group1[1], and can proceed no
further until these issues are resolved:
* Revision endpoint: InvalidArgumentException: ParserOutput does not
have a render ID
- https://phabricator.wikimedia.org/T356368
* TypeError: Argument 1 passed to
MediaWiki\Parser\Sanitizer::encodeAttribute() must be of the type
string, null given, called in
/srv/mediawiki/php-1.42.0-wmf.18/includes/xml/Xml.php on line 81
- https://phabricator.wikimedia.org/T357668
The second issue blew up after a rollback for the first issue, so we're
currently in a much-less-than-optimal state.
Once these issues are resolved train can resume.
Thank you for any help!
-- Your not entirely placid train operator
[0]. https://phabricator.wikimedia.org/T354436
[1]. https://versions.toolforge.org/
Hello,
Starting on Wednesday(14th February), selected tools will stop running on
Grid Engine.
The tools will be stopped from running but the code and data will not be
deleted.
If you want your tool to be re-enabled, please reach out to the cloud
admins on the mailing list or on the tool's migration ticket.
Those who have reached out to ask for extension are not affected by this.
Here's a reminder of the timeline we are following[0]
[0]:
https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation#…
--
Seyram Komla Sapaty
Developer Advocate
Wikimedia Cloud Services
The 1.42.0-wmf.17 version of MediaWiki is blocked[0].
The new version is currently deployed to group0[1], but can proceed no
further until this issue is resolved:
* T356895 - [wmf.17 - testwiki] Impact module: Temporary delay in
getting your information
- https://phabricator.wikimedia.org/T356895
Once this issue is resolved train can resume.
Thank you for any help!
-- Your downright placid train operator
[0]. https://phabricator.wikimedia.org/T354435
[1]. https://versions.toolforge.org/