Portal:Toolforge/Admin/Monthly meeting/2026-05-26

Attendees

Bryan Davis (bd808) Filippo Giunchedi Arthur Puthin  Seyram Komla Sapaty Francesco Negri Andrew Bogott Belinda Liviero Taavi Väänänen

Notes

• buildpacks upgrades
  • T380127 “Heroku 24” is still open and should be closed (after checking the leftover items)
  • “Heroku 26” stack was released last week, we should use it for builds with “--use-latest-versions”
  • T424362 “Define update process” is open for comments, we can wait for David to be back before taking any decisions
• Toolforge membership requests: should we revisit the process?
  • We're getting more and more AI-generated requests and it's difficult to evaluate if they're in good faith
  • Would it be easier to evaluate code instead of generic LLM-generated text requests?
    • Maybe it would be just as difficult
  • Asking how their tool would benefit the movement is usually a good question
  • We could implement template replies or dropdowns with possible reasons
  • More broadly, we are trying to prevent “incorrect” usages of Toolforge and our infrastructure. E.g. we could try to identify people who are using Toolforge to bypass rate limits.
  • Toolforge bad users are similar to PAWS bad users, where we currently have no barrier at entry, but we block users after they misbehave.
  • For monitoring after-the-fact we need more tools, the current “disable tool” function is not enough. We don’t have a list of “recently created tools”, there is no way of doing systematic monitoring.
  • We can look at this at the product level with some support from Chris Ciufo.
  • People now have more ways of generating bad tools, we should adapt our policies too.
  • We should expose to users the resources they are consuming, sometimes they ask for more CPU when they are not even consuming the ones they already have. Can we expose this via a dashboard?
• Standard items:
  • k8s upgrade workgroup progress
  • T194332 Push to deploy beta
    • Work is ongoing in the required subtask T348755 and its subtasks
  • Sustainability score
• User-discoverable tools to show memory/cpu utilization vs requested vs limits (e.g. T427204)
• Are toolschecker checks still relevant or are they covered by other checks? Context is T328502
  • Looking at https://logstash.wikimedia.org/goto/911d557b057d7e9091e8594aad244321 it seems that we could just drop toolschecker
  • The Toolforge etcd check is something we want to port to Prometheus