The following are notes for reviewers on how to review changes for project-config. These notes are not exhaustive, they cover a few caveats that especially core reviewers should be aware of.
For changes to projects, there should be support by the project team that is affected. A couple of projects have listed infra liaisons at https://wiki.openstack.org/wiki/CrossProjectLiaisons#Infra . Changes should only merge when at least one of the infra liaisons has given a +1. For not-listed projects, there are no rules but it might be good to ask for review by PTL or cores of the repo depending on the change.
There should be no non-voting jobs in the gate queue. Voting jobs should be in both check and gate queues.
Check the following:
Check that publishing to docs.openstack.org or specs.openstack.org is only enabled for projects that are in the Big Tent (mentioned in governance repository). Similary, translation workflow is also only enabled for Big Tent projects.
In general, nodes are off-lined after a job run. Some special nodes are not off-lined and long-lived. Ensure for these nodes that any job running on them is handled in zuul/openstack_functions.py.
Current nodes that are long-lived are: proposal, release, signing, wheel-mirror-*