So... where is the resulting list of candidate maintainers? 🤔

Since this is marked as resolved, where are the candidate tools that were identified?

Did the resolution of this task produce any public artifact that could be shared here?

Heads-up: I added a new MR (https://gitlab.wikimedia.org/toolforge-repos/wikinewsie/-/merge_requests/23) to fix an overflow issue in small screens with the language selector @Chimaifeanyi29 introduced earlier.

I've submitted a fix for this in https://gitlab.wikimedia.org/toolforge-repos/wikinewsie/-/merge_requests/19. I started with a simple JPEG-only filename check, which was already pretty effective, but then went down a rabbit hole to implement a more robust validation, so that e.g. movie or game posters (like those for Resident Evil (2026 film) and Mario Kart Tour - Wikipedia would continue to get the backdrop. It took me the whole weekend, but I'm pretty happy with how this turned out, and ended up improving a bunch of other aspects as well (e.g. the display of transparent logos and icons in the dark mode, and the application of the backdrop also in the article modal).

It seems to me that the main issue is with images that have a transparent background, right?

Also for completeness' sake, I'd be curious to know what kinds of edge cases IPA fails to support. AFAIK IPA has various levels of precision, starting with the phonetic vs. phonemic transcription modes (aka [...] vs. /.../) and the former supposedly is able to capture significantly more detail than the latter. So is the limitation inherent to the syntax (source format) level, or does it lay at the ability of TTS engines to correctly represent such nuances?

Implemented in https://gitlab.wikimedia.org/toolforge-repos/wikinewsie/-/merge_requests/5 (I'm creating this task retroactively, for tracking purposes).

I've submitted https://gitlab.wikimedia.org/toolforge-repos/wikinewsie/-/merge_requests/8 which provides an alternative solution to this: instead of moving the image hoping that the cropping doesn't remove useful information, the full image is shown, with a blurred background derived from the image itself (a common pattern in modern web design) to fill the container without requiring cropping in the first place.

I've submitted https://gitlab.wikimedia.org/toolforge-repos/wikinewsie/-/merge_requests/8 which provides an alternative solution to this: instead of moving the image hoping that the cropping doesn't remove useful information, the full image is shown, with a blurred background derived from the image itself (a common pattern in modern web design) to fill the container without requiring cropping in the first place.

This sounds very useful but I'm not sure a fixed list would be the best approach. For example, that split of European regions isn't particularly interesting to me — I'd much rather have news related to the EU, for instance, or the Iberian peninsula, or Portugal specifically, or even a particular region or city within.

From the slides:

Sharing some CSS-related resources in my to-read/to-watch list, which may be useful:

Hmm, good question — I don't know. I just thought I'd mention it because it wasn't referred previously. :)

Wouldn't patch demo also be an option to test this?

Having Spanish as the second fallback in the chain, after Portuguese, sounds reasonable indeed, and would be strictly an improvement over the current situation (i.e. it would not override any instances where Galician is currently falling back to Portuguese).

I'm going to try to ask a couple Galician speakers (native and otherwise) to chime in.

@Catrope great news! How can one follow that change to get notified when it happens?

@BCornwall you had emailed geral@wikimedia.pt (which is an alias to the Wikimedia-PT-internal mailing list -- wikimedia-pt-internal@lists.wikimedia.org) on 7 Aug, and @Alchimista replied to that email the next day, which is why I didn't comment here. However, he replied directly to the list and didn't cc you, so you may not have received the response. I'll ping him directly to comment here for the record.

For those who attended the session and/or are interested in this, please follow the conversation at task T371264, which is about development of the tool itself.

I also invite anyone interested to create issues/feature requests in the project repository's issue tracker. I've already added a bunch: https://github.com/waldyrious/bookform/issues

Update on the current status: For the moment the tool is already live and semi-functional. There are a few critical missing tasks for it to be a minimal MVP, namely the ability to actually connect the items with each other, and the ability to check Wikidata for potentially existing items, to avoid duplicates. Once those are done, we can close this task, since at that point the tool will indeed be usable.

For future reference, I'm copying below the text about this project that was added to the Etherpad of the closing ceremony showcase:

Thank you, @Olea! Reach out to us afterwards during the hackathon if you'd like to discuss this topic further :)

Would it make sense to also update https://www.mediawiki.org/wiki/Manual:Ajax? I'm thinking especially the "Limitations" section. I know it's marked as outdated already, but perhaps the banner at the top could link to the appropriate page with up-to-date info.

Thanks for the update, @Pcoombe. Indeed, even though strictly speaking the WMF logo was not moved to the footer, it was removed from the Projects grid, so I agree that the spirit of this issue has been addressed. Kudos to @Ladsgroup for implementing these changes!

In T246901#10529126, @OpenDEM wrote:

Date would be Sunday 16.02.2025 at 16:00 UTC.

Ah, awesome! Yeah, that worked now :D → https://test.wikipedia.org/w/index.php?title=M3api-examples_guestbook&diff=prev&oldid=643177

@LucasWerkmeister should others be able to use it as well? I tried the following, without success:

Shouldn't the new members be added (or add themselves) to the Toolforge-standards-committee project?

For the record, I have emailed @KFrancis my details, got the NDA document from her and have signed it. Is there a confirmation step needed, of should I request my addition to the WMF-NDA project now?

Thanks for the follow-up, @bd808! Is there someone we should ping for that request? The instructions are not clear in that respect.

I've done most of the work during the Wikimania Hackathon, and deployed a working version to http://waldyrious.net/wikispeed. I will mark this as finished once I clean up the code and iron out a couple minor bugs.

Thanks for the suggestion! I probably should have added more details to the ticket description. I know about Cradle, but it doesn't work for what I need because for books you need to create multiple items at once (for convenience): one for the work, one for the edition, and possibly more for the author, publisher, etc.

Apologies, I somehow missed the notification of the previous comments. Adding relevant links:

I perfectly understand, @apaskulin! Although I was enthusiastic about the chance to contribute to wrap up this long overdue content migration/unification, I must admit I'm also slightly relieved that this work will still happen without me having to figure out how to make the timelines work out! ^^

Hey there! I was deliberately conservative in my time availability estimate (and therefore also the budget) because I didn't want to overcommit and sacrifice my family life due to combining this with my full-time job. I am reasonably confident that the amount of time I have planned to use should be sufficient to complete the project, including some restructuring of the pages on Meta, but I would be able to expand the time dedication if it turns out to be necessary (I can also take a couple months off on a leave from my day job, if it turns out to be appropriate). Such decisions would depend on a deeper initial assessment of the workload, as well as the recommendations from the people who have prepared the project, and certainly know more about the necessary commitment than I do! :)

Thanks for the edits to this bug, @Bugreporter2! I agree with your reasoning, but I think it helps to mention the existing redirect notices as an example of what is being sought and prior art for a similar feature. I've edited the description to re-add some of this context.

Quoting my comment from T35943, for convenience:

The PR has been merged and deployed to https://ws-export-test.wmcloud.org. Thanks, @Samwilson!

Submitted github:wikimedia/ws-export#472 to fix this.

Thanks for sharing! After seeing the document I realized this was about the layout and design of administration/configuration interfaces in various online platforms, not necessarily MediaWiki wikis. Perhaps this could be made clear in the task description.

Thanks both for the updates! @He7d3r, please clarify your position: do you think the exceptions justify treating pt-BR differently and keeping this issue about pt-PT only? Or is your opinion that, precisely because they are exceptions, the default should be plural zero and thus this issue should refer to both pt-PT and pt-BR?

In T151008#2808957, @He7d3r wrote:

However, searching for specific examples of phrases containing "zero <something>", I got these statistics in the same corpus:

Also, can the summary be published somewhere accessible to the community?

I'm not exactly sure how the "MediaWiki testimonials" page is specifically relevant to a comparative review of the Community configuration feature, but either way, I thought I'd point our the following list of on-wiki configuration extensions: https://mediawiki.org/wiki/Extension:Config

Update: Gerrit patch 804770 has been merged during Wikimedia-Hackathon-2023, following validation done via Patch Demo. Many thanks to @Amire80!

Update: Gerrit patch 133222 has been merged during Wikimedia-Hackathon-2023! Many thanks to @Tgr and @Urbanecm!

FYI, there's a discussion currently ongoing at https://commons.wikimedia.org/wiki/Commons:Village_pump/Proposals#Enable_textured_3D_files_on_Commons.