In Zed cycle, we started collecting the operators feedback
- https://etherpad.opendev.org/p/BER-2022-OPS-SRBAC
- https://etherpad.opendev.org/p/rbac-operator-feedback
and based on that we changed the direction for RBAC goal:
1. Finish delivering project personas. This is to introduce the member
and reader roles to operate things within their project. By default,
any other project role like foo will not be allowed to do anything
in the project.
2. Change in scope implementation. Services with project resources
(except Ironic as they have user using the system scope) that have
already implemented scope (or have yet to) should make all policy
rules set scope_types=['project'].
Discussion reference for policy popup team
- https://etherpad.opendev.org/p/rbac-zed-ptg#L171
Change-Id: If7b052149df3f37f2173e6719c8c6d0d81787cc7
As part of our discussion from the latest PTG, as well as several
prior, one of the goals for the project was to retire any of the
unused repositories under the openstack-helm umbrella.
This change seeks to retire the openstack-helm-deployments repo
since it has not been maintained and the use-case that it was
originally created for is no longer being actively pursued.
Depends-on: https://review.opendev.org/c/openstack/openstack-helm-deployments/+/847410
Change-Id: Idb63ff8e74427d2b2adab5f003441fb0f6b218b1
At the October 2021 PTG and April 2022 PTG we discussed the need to for
something like "technical preview" state for the e.g. new OpenStack
projects which don't meet all requirements for being official OpenStack
project (see Skyline for example).
This patch adds framework for such projects. It's called "emerging
technology" state which can be set for new projects.
It also defines "inactive" state for the existing, not well maintained
projects.
Change-Id: I32a07f8bb46723f36c1bf846644b6aa768778a4f
Foundation bylaws mention the "ATC" term and during
the merging of UC to TC we changed it to "AC". Adding a line
stating that both are the same term and that way we will comply
with the bylaws also
- https://openinfra.dev/legal/openstack-technical-committee-member-policy
Change-Id: Icd7efda1d7a49c6ddb1b7f4ac9687e7e6b231a84
The security-analysis repo is slated for retirement by the Security
SIG. This change removes the security-analysis repository from the
list that is currently maintained by the Security SIG.
https://lists.openstack.org/pipermail/openstack-discuss/2022-June/028816.html
Change-Id: I1d59c3534d9982c97f451cfc8ee711a44e71a6ef
Adding infra contributors opportunities in upstream investment
(copy from previous year) which still need help.
Change-Id: I7fe371b5844f1524d02bb911763957658e9afedd
Recently we discussed with Release Management team some possible
improvements in the project governance. Summary of that discussion can
be found in [1].
This patch updates potential triggers to consider project to be dropped
in the dropping-projects document to reflect those improvements
mentioned in [1].
[1] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028418.html
Change-Id: I3c9bb37be8ab9ab5282377169de906db2bf5b7fc
Validate on Zuul builds and Gerrit.
This is needed for project stats check. Please check etherpad for more
detail discussion or output example [1].
Run project_stats_check.py with no arguments will run on all projects
defined in `reference/projects.yaml`.
If you wish to run for specific project or branch. Run like:
`project_stats_check.py -p heat,sahara -b master,stable/xena`
[1] https://etherpad.opendev.org/p/health_check
Change-Id: I84c3a4898a74c26746fd66d046a80b8936a608e9
With the outcome of the legal check, it is not clear to us
that tick tock words are ok to use for our new release
cadence arrangement and in what form.
In TC, we decided to use a different name and 'SLURP'
is the choice of the majority[1]
Let's update our resolution document to reflect the new name
and I am adding a "communication" section to explain that how
we will use "SLURP" in our documentation.
[1] https://meetings.opendev.org/meetings/tc/2022/tc.2022-05-12-15.00.log.html#l-191
Change-Id: If82240c1f62842314b48caa4694280c0be147919
As discussed in PTG, we will try the DPL model first for
the leaderless projects or if PTL assignment is needed in between
of the cycle.
- https://etherpad.opendev.org/p/tc-zed-ptg#L109
Change-Id: Ie65553720247b585be94d53811a2ade20353f9cc
As of our discussions from the last PTG, as well as several
prior, one of the goals for the openstack-helm project is to
retire any of the unused repositories under the openstack-helm
projects umbrella.
This change seeks to retire the openstack-helm-docs repo since
it hasn't been maintained and all the documentation lives within
the openstack-helm repo itself.
Depends-on: https://review.opendev.org/c/openstack/openstack-helm-docs/+/839429
Change-Id: Id6d8333c35d27d42c4ac3661971f6c5396b0aa1f
Keystone is already moved to PTL model and we do not
need the DPL model Liaisons now. This commit removes
those.
Change-Id: Ie01acc49e3a3882b7f9b0f1ebb2dd157ece8f1c3
TC is more connected with project teams with the
weekly meeting and PTG TC+Leadership interaction sessions.
Also, TC liaisons did not work the way we expected it. In Zed
PTG, we decided to remove it.
- https://etherpad.opendev.org/p/tc-zed-ptg
Change-Id: I08702b015245df35d40e08fa08a3269cc6bb1cac
