#toolforge — Public Fediverse posts

🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: https://www.mediawiki.org/wiki/Special:MyLanguage/Developer_Satisfaction_Survey/2026

This year, 207 respondents from the Wikimedia developer community answered questions about:
:toolforge: #Wikimedia #Toolforge and Cloud VPS
:mediawiki: #MediaWiki code quality
🔌 Wikimedia API use
📜 #Documentation
🔬 Research
🛠️ Developer tools and processes

🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: https://www.mediawiki.org/wiki/Special:MyLanguage/Developer_Satisfaction_Survey/2026

This year, 207 respondents from the Wikimedia developer community answered questions about:
:toolforge: #Wikimedia #Toolforge and Cloud VPS
:mediawiki: #MediaWiki code quality
🔌 Wikimedia API use
📜 #Documentation
🔬 Research
🛠️ Developer tools and processes

🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: https://www.mediawiki.org/wiki/Special:MyLanguage/Developer_Satisfaction_Survey/2026

This year, 207 respondents from the Wikimedia developer community answered questions about:
:toolforge: #Wikimedia #Toolforge and Cloud VPS
:mediawiki: #MediaWiki code quality
🔌 Wikimedia API use
📜 #Documentation
🔬 Research
🛠️ Developer tools and processes

🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: https://www.mediawiki.org/wiki/Special:MyLanguage/Developer_Satisfaction_Survey/2026

This year, 207 respondents from the Wikimedia developer community answered questions about:
:toolforge: #Wikimedia #Toolforge and Cloud VPS
:mediawiki: #MediaWiki code quality
🔌 Wikimedia API use
📜 #Documentation
🔬 Research
🛠️ Developer tools and processes

🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: https://www.mediawiki.org/wiki/Special:MyLanguage/Developer_Satisfaction_Survey/2026

This year, 207 respondents from the Wikimedia developer community answered questions about:
:toolforge: #Wikimedia #Toolforge and Cloud VPS
:mediawiki: #MediaWiki code quality
🔌 Wikimedia API use
📜 #Documentation
🔬 Research
🛠️ Developer tools and processes

yesterday evening work with @EvoMRI on the @wdscholia instance on Toolforge. We noted that our main instance only shows half of the results, only @wikidata 'main' part. The 'scholarly' articles part are no longer there. That day has been pending.

We seem very close. I wrote up a status 3 weeks ago: https://chem-bla-ics.linkedchemistry.info/2025/12/31/rescuing-scholia-2-getting-close.html

For this week, plz use https://qlever.scholia.wiki/

We put a banner on the #toolforge instance

#openscience #wikidata #sparql #scholia

the 2025 Coolest Tool Awards are about to be revealed!! https://www.youtube.com/watch?v=Szjq7Emoqq0

#Wikimania #Wikimania2025 #Toolforge #CoolestToolAward

Celebration! The #wmhack25 was the occasion to onboard User:Arcstur as a maintainer of #EditGroups! I'm super grateful for him for already helping out with a big cleanup of the deployment process :)

#Wikidata #toolforge #wikitech

What are the plans around #redis usage in the #wikitech #toolforge, especially after the license change? Will we switch to a fork? Also, does it actually make sense to have a redis instance shared between many tools, when redis provides (AFAICT) no user isolation at all, meaning that the tools can overwrite each other's data (on top of potentially competing for resources like connections or memory)? The docs encourage prefixing keys, but it can't be enforced, right? https://wikitech.wikimedia.org/wiki/Help:Toolforge/Redis_for_Toolforge