For Hackathon participants to add hacking projects, keep track of activities, and collaborate with others at the Wikimedia 2025 Hackathon (Istanbul, Turkey – May 2–4, 2025).
If you have an idea for a project you want to work on, or an existing project you'd like help with, please either create a new task, or add the Wikimedia-Hackathon-2025 project tag to an existing task!
Previous: Wikimedia-Hackathon-2024
I left some comments in the merge request for the service:
With this dataset, the scatterplot works with the implementation:
I loved participating in the games!
I also like the toolbox idea, but would additionally recommend to include all charts and tabular data files used in a given article in the respective info page (e.g. https://en.wikipedia.org/w/index.php?title=Ammonia&action=info ), where we already list Templates, Modules and Wikidata items used in the article. (Thanks to @Kallichore for bringing up this idea in https://de.wikipedia.org/wiki/Hilfe_Diskussion:Chart#Seiteninformationen )
Putting everything into some massive table is NOT an improvement.
@Nikerabbit I just invited the translatewiki.net GitHub account to the repo, can you try again please?
Error Output: ================ ERROR: Permission to wikimediabrasil/quickstatements3.git denied to translatewiki. fatal: Could not read from remote repository.
-rakkaus:#translatewiki- [l10n-bot] Imported 924 new messages or translations for quickstatements3.
I use this page daily in different languages and I am disappointed with the design change. The new look now rather degrades the UX compared to the old version. It's not a matter of habit, but of adding more time to open pages I use daily. Quick access has suffered for several reasons:
At the hackathon 2025 I improved on the part that mages an individual's family name to a Q-item. It should now also support family names with affixes, as is common in Dutch names.
Last year at the Hackathon I improved on the documentation somewhat by creating a README and linking to that from the landing page.
The way "described by source" works was also improved uppon at last year's hackathon, and had already gotten a toggle long before that.
The matching of family names can be further improved uppon, and adding a custom statement is a repeatedly requested feature.
Change #1148944 merged by jenkins-bot:
[mediawiki/extensions/PageAssessments@master] Lua: Rename attribute from projects to pageAssessments
Hi @Wangombe, message documentation in translations/qqq.json is now finished :D
Change #1148944 had a related patch set uploaded (by SD0001; author: SD0001):
[mediawiki/extensions/PageAssessments@master] Lua: Rename attribute from projects to pageAssessments
Change #1141032 merged by jenkins-bot:
[mediawiki/extensions/PageAssessments@master] Expose WikiProject associations to Lua
Change #1143787 merged by jenkins-bot:
[translatewiki@master] Add QuickStatements 3.0 to translatewiki.net
To summarize, this change makes things worse, not better. Please do not promote it.
@Novem_Linguae; Yes, I know it is trivial to add sorting to a tabular display. But note that I said "I would gladly give it up if it keeps other features from being implemented" Specifically, my idea of having hierarchical drill-down makes such simple sorting impossible. Since sorting adds such little value compared to the great value of a collapsible hierarchy, ditch the table. In the process, you make the list more compact, resolving one of @JAnD's concerns.
Sorting by name doesn’t seem to me particularly useful, particularly with the search capability. I would gladly give it up if it keeps other features from being implemented
There are two search fields, which is confusing in vector. In monobook is it better, but search field should be in left.
Not sure if this is the right place to leave feedback; if it is, it isn’t obvious; the "Add Actions" drop-down seems particularly confusing. I expected to see an "Add Comment" option but found done. Anyway, if this is not the place for my comments, please move them to the right place.
I would be supportive of using the toolbox in the top right. There are multiple things we could put in there. That being said, I would suggest we use an ellipses icon and open a menu for more clarity and better responsiveness, instead of using a list of icons that always show. In that menu, we could put the link to Wikidata, add the option to download as a CSV, toggle the patterns/symbols for accessibility. Would this be possible @Jdlrobson-WMF
Very nice. Any interest in adding a third column that displays the special page name in an unhidden way? So for example, Special:ListDuplicatedFiles instead of "List of files with duplicates". I think this would make the page more useful to developers.
Thanks for the recommendation @GPSLeo , I was following the logic of the Android Commons App, which sets the first language's caption to the filename. Updated the description: we can include a required filename field, required caption field, and an optional description field.