Jump to content

Portal:Toolforge/Admin/Monthly meeting/2024-11-05

From Wikitech

Attendees

  • Arturo Borrero
  • Bryan Davis
  • David Caro
  • Francesco Negri
  • Sarai Sanchez
  • Seyram Komla Sapaty
  • Slavina Stefanova

Agenda

  • k8s upgrade workgroup progress
  • KR/hypothesis progress
  • Toolforge standard committee

Notes

k8s upgrade workgroup progress

Upgraded to 1.28 yesterday, quite smooth Some nodes had a small issue where the cookbook tries to evacuate the node, but is unable to, though deleting the pods manually worked (all user tools, 2 deployments 1 cronjob)

There was an issue (T378976) where a tool was not able to start, that might be related to NFS, the user restarted the webservice and worked (probably in a different worker?), keep an eye for any node having stuck processes

Next is 1.29, Francesco and Arturo, will probably not get to it before the end-of-year PTO but will start working on it

Toolsdb mariadb upgrade has priority, so that might take the time instead

Missing the webservice deploy for the latest code - will happen tomorrow

KR/hypothesis progress

6.3.5 components-api

Have working token auth in local dev. Deploy to toolsbeta next

Want to generate a async client library from the OpenAPI spec to use in the components-api service

Will create a limited components-api client (command line), mainly to be able to write functional tests easily

6.3.7 Sustainability score

Delivery of sustainability score pushed to Q3

6.3.6 hypothesis

Looking for pain points in user journeys.

Need to gather and incorporate user feedback. Thinking about QuickSurveys as a possible tool to gather information. Need to find out if that can be enabled on Wikitech.

Looking at some 3rd party platforms like fly.io and Heroku to see how they do things

Evaluate creating high-level designs representing UI-based workflows

Toolforge Standard Committee

8 folks went through the process and they’re all set up on the existing mailing list (we kicked out previous members).

How do we avoid being in the same situation where after 7 years we have to start the committee over from scratch? Some discussions are ongoing.

Committee members have started looking through the Phabricator backlog and closing some old tasks.

A difference from before: there is a tool named “toolforge-standards-committee” and everyone in the committee is a co-maintainer for that tool. If there is an abandoned tool, the “toolforge-standards-committee” tool can be added as a co-maintainer for the abandoned tool.

Should we invite the members of the committee to this monthly meeting?

David to draft an invite with some info about the meeting

Bryan can deliver the invite via the committee's mailing list