Tue, Dec 5
None of the extensions had any composer dependencies that needed updating. The remaining outdated dependencies for WikibaseQualityConstraints are blocked for the same reason as for WikibaseLexeme: https://github.com/wikimedia/mediawiki-extensions-WikibaseLexeme/blob/master/README-dev.md#chore-dependency-updates
Everything that we can update has been updated.
Mon, Dec 4
There are no outdated composer dependencies.
We still have the literal copy "A description is not applicable for Multiple Languages." for the title= attribute of the - in the description cell for mul when viewing the legacy Termbox and the same copy for the aria-label= attribute when editing it. Should we adjust that as well?
As far as I can tell, the string dlc no longer exists in the cldr extension, so I think this is done indeed.
As far as I can tell, this task is "Done" by virtue of the root cause being identified: the Primary Sources gadget being broken. (see also T237925: Primary sources tool left without maintainers)
Fri, Dec 1
Thu, Nov 30
See https://wikidata.beta.wmflabs.org/wiki/Lexeme:L4563 for a prepared example.
@Tchanders Thank you so much for those details! This helps us a lot with planning the next steps better 🙏
Wed, Nov 29
Thank you! 🙏
I tried it out (check experimental) on a Wikibase change and it quickly failed with the following:
Tue, Nov 28
This is not great yet, but the list is a start. It contains things for us to work through and add tests as needed. Additional tests obviously will be needed/added for all the code we touch. This is list is more for the overall due diligence.
@Aklapper Please review the script that you're using to create these tasks. The pings via Phabricator accounts did not work. (At least I assume that was intended to be phabricator pings from the context.)
Then I misunderstood it moving forward. I'm sorry, my bad!
Not sure where to move this. We can pick it up again in the new year and click +2 on the change that drops the styles.
Oh, looking at the task description, I think we might have missed updating the copy of the onboarding popup. I'll quickly create a change for that too.
Mon, Nov 27
There is a whole bunch of API endpoints and Special Pages on the Wikidata side of things that do changes that currently cause an anon user's IP address to be logged and displayed. Many, but not all of them go through repo/includes/EditEntity/MediaWikiEditEntity.php and I guess WIP example: Create a temporary user from ApiSetClaim (I57075e88) outlines the fundamental work that will need to be done, eventually.
Fri, Nov 24
It would be better if the browser settings (Accept-Language) and/or geolocation would be considered.
On that Grafana panel, I wonder if we do not want to switch the axis for Forms and Lexemes. We have way more Forms than Lexemes. So Lexemes are by default almost invisible as are all the other Entities that are not Forms. Or maybe switch to a log y-axis?
What version of Wikibase are you running?
Side note: How come https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/WikibaseLexeme/+/605c2ed9bde1b624f76eab833f4c0e33c6640de0/resources/special/new-lexeme-dist/SpecialNewLexeme.cjs.js did not get picked up by the above search? This file is directly checked into the WikibaseLexeme directory as a normal file, and it contains the string compatConfig a bunch of times. 🤨
Ah interesting! I wasn't aware that mul existed there already since 2015/2016!
Wed, Nov 22
Tue, Nov 21
Those numbers look good! Now I'm expecting a sharp increase in Grafana for our panels about counting forms and senses.
Mon, Nov 20
Fri, Nov 17
Thu, Nov 16
Special:BadTitle/M123 would be also ok with me. For me, it would be not so much depending on the entity type, but rather that it should have some sensible "not found" response. Redirecting to the (missing) page of a non-exisitng entity is sensible. Showing a completely unrelated page just because its page-id happens to match the numeric part of the entity-id is not sensible to me.
There seems to be a problem with LibraryUpgrader, see: T345930: LibUp hasn't run since 5 June 2023. Should we somehow mention that in the respective section of the README as well?