Description

zware

opened on Sep 28, 2026

Issue body actions

Membership of the @python/buildbot-owners group has drifted out of date.

@python/organization-owners, please invite the following to the buildbot-owners team:

Username	Description
@stratakis	Owner of several cstratak-* workers, e.g. https://buildbot.python.org/#/workers/30
@kulikjak	Owner of kulikjak-solaris-sparcv9
@malvex	Owner of malvex-nixos-x86_64
@opsec	Owner of opsec-fbsd14 et al, three FreeBSD workers

I will also be adding the following existing org members:

Username	Description
@furkanonder	Owner of onder-riscv64

Similarly, I will also be removing folks who no longer operate a current worker, with many thanks to all for in most cases providing and/or administrating the only worker(s) for a platform for years at a time (and if anyone ever wants to host a new worker, please don't hesitate to reach out :)):

Username
@taleinat
@edelsohn
@embray
@koobs
@aixtools
@jkloth

Reacted by Furkan Onder, Stan Ulbrych and Jakub Kulík

Activity

1. koobs commented on Sep 28, 2026

   

   koobs

   on Sep 28, 2026

   More actions

   Here @zware 👋 if you need more FreeBSD builders, I have spare VM's (arm64 / amd64 ) I can provision on

   Reacted by Zachary Ware
2. encukou commented on Sep 28, 2026

   

   encukou

   on Sep 28, 2026

   Member

   More actions

   Hmm, are you sure? The group has write access to this repository.
   Nothing against the fine people mentioned here, but in general, anyone should be able to add a worker; shouldn't changing the config repo require some more trust?
3. hugovk commented on Sep 28, 2026

   

   hugovk

   on Sep 28, 2026

   Member

   More actions

   We have three buildbot teams:

   team	description	members
   Buildbot Config	"All the necessaries for running buildbot.python.org"	7
   Buildbot owners	"People who own workers for buildbot.python.org"	16
   buildbot.python.org	(no description)	2 people + above two teams

   "Buildbot owners" + "People who own workers for buildbot.python.org" matches @zware's updates, but perhaps that team doesn't need write for https://github.com/python/buildmaster-config, only the config team does?
4. zware commented on Sep 28, 2026

   

   zware

   on Sep 28, 2026

   MemberAuthor

   More actions

   With my worker owner hat on, I like having access to adjust the config on my own workers, and with my buildbot admin hat on I like owners being able to time both sides of updates to their own stuff to avoid downtime. Realistically, the buildmaster config is relatively low stakes and relatively recoverable in case of accidental damage, and I'm comfortable with worker owners having write there. It might be a good idea to require review from an admin (buildbot-config group), though?

   Sidenote: I also just realized in looking into this that python-core only had read while python-triage had triage on buildmaster-config, so I bumped python-core up to triage.
5. stratakis commented on Sep 28, 2026

   

   stratakis

   on Sep 28, 2026

   More actions

   Hmm not sure if it's a good idea to have write access honestly. We are talking about the buildmaster-config repo, right?

   The buildbot infra config AND each workers/builders configs live there.

   Obviously a worker owner shouldn't meddle with the infra design config.

   Now let's say I wanna fix up the parallel processes for my workers, I think that would be reasonable to do it myself. But e.g. enabling --with-dtrace and we start getting failures (as it happened), I will be able to block the CPython releases that rely on stable buildbots.

Issue actions