project-config/gerrit
Jay Faulkner dd6c0bcd91 Proposed new Ironic core structure
Ironic is considering a two-tier structure, separating permission to
approve/workflow patches from the ability to core-review vote.

The final state is intended to be:
- All existing active ironic-cores go into ironic-approvers
- ironic-approvers goes into ironic-reviewers
- anyone approved later can get added to ironic-reviewers

In terms of permissions, the desired state is:
- ironic-approvers are the only team that can approve patches for
  landing
- ironic-reviewers are allowed to core review and do most other core
  activities except the final workflow to land code

As a transition, I'm leaving the ironic-core group in the ACLs. Once
the new group is created, populated, and working, we can rename the
old one to reflect its disuse.

I've also, as a result of auditing the core groups for other Ironic
projects and seeing some of them out of date, am unifying more
ironic-related projects into the same ACL configuration. The now
disused old core groups for those projects will also be renamed to
reflect their disuse when completed.

Change-Id: I7fea059274ffd8635e426e82882a3076527464eb
2024-10-15 15:16:32 -07:00
..
acls Proposed new Ironic core structure 2024-10-15 15:16:32 -07:00
notify_impact.yaml Reorganizes project-config 2014-09-25 11:41:04 -04:00
projects.yaml Proposed new Ironic core structure 2024-10-15 15:16:32 -07:00