Apologies in advance for a possibly ranty email.
I'm again seeing some major Toolforge developments happening with major
decisions being made in private. A few examples:
* Infrastructure IaC/OpenTofu migration (with an intern assigned to it)
popping out of nowhere to implementation tasks
https://phabricator.wikimedia.org/T390056 with no public/formal
discussion whether we want to replace the current tooling with that.
* UI project starting an "investigation" task
(https://phabricator.wikimedia.org/T383146) with a clear bias towards a
specific solution, based on unspecific "previous discussions", which
were then hidden from the description when I asked for documents
relating those to be made public.
* The Toolforge CLI consolidation project apparently has switched
implementation languages compared to the last decision request,
apparently based on "a team decision" that was apparently made "a few
months" ago but never communicated anywhere as far as I can tell:
https://phabricator.wikimedia.org/T356262#10722410
First, could we please again stop doing major decisions in private?
Second, is there something in our processes or workflows that we could
improve so that things wouldn't always immediately start going more
hidden and private every time I stop paying close attention to this?
Taavi
Hi there,
the tofu-infra project gained support for managing quotas, see
https://phabricator.wikimedia.org/T371391
Openstack quotas can now be established in several ways:
* traditionally via the wmcs-openstack CLI
* using the cookbook to manage quotas
* using tofu-infra
If a quota is set via tofu-infra, it will override all the others, as far as I
understand how they work.
If a quota is not set via tofu-infra, then whatever quota was already
established should be in action.
I have not back-filled, nor have plans to do so, previous quotas into tofu-infra.
regards.