Hello Everyone,
You might know, TC has de-coupled the community-wide goals from the release cycle[1]. As per the new structure, community-wide goals are tied or have to be finished within the release cycle. Instead, it can have target dates which can be a particular cycle release date or multi-cycle or even in between a release cycle. Target dates will be selected by considering the amount of work needed and the community bandwidth. This will help to make sure the goal is ready to start and also continue working on the goal until work is completed. 'Secure RBAC' goal is one example of a new structure that has different milestones targeting the different set of work[2].
I think this will be helpful for PTLs and project teams to plan the active goals for their project.
Current Selected (Active) Goals: ------------------------------------- We have two Selected/Active goals. The project team can start/continue working on:
1. Migrate from oslo.rootwrap to oslo.privsep [3]. This is contouring from the previous cycle.
2. Consistent and Secure Default RBAC [4]. New design/implementation details are finalized now, please read those and for any queries, plan to attend the policy popup team biweekly meeting[5].
[1] https://review.opendev.org/c/openstack/governance/+/816387 [2] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rba... [3] https://governance.openstack.org/tc/goals/selected/migrate-to-privsep.html [4] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rba... [5] https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popup...
-gmann