In TC house rule, we introduced the project-updates topic so that
we can speed up the process for updates (including addition or retirement
of repository) in existing projects. But this was not meant for the
retirement of complete project. Any retirement of complete project
or a new project application are the big change in OpenStack umbrella
and should require the detailed discussion. That is why it should fall
under formal-vote topic.
For retiring the projct, we have been using the mixed topic where
sometime we use formal-vote and sometime project-updates.
Clarfiy the same in our house rule doc also.
Change-Id: I591c92fb84b5ca22905cf703be3c27f690899513
The last stable branch of networking-ovn, stable/train, was already
retired[1] and the project no longer has any active stable branches,
so can be formally retired.
[1] https://review.opendev.org/c/openstack/releases/+/865967
Change-Id: I0f3e1fda9080b3a433783ae2c423f82f638a5457
This repo was deprecated in xena after devstack grew the ability to self
bootstrap CI environments using ansible. We want to drop this repo as it
is no longer necessary and it will help clear the path for Ubuntu Xenial
cleanup in the CI system.
Depends-On: https://review.opendev.org/c/openstack/devstack-gate/+/919626
Change-Id: I232939fc9c7ba13aea85c9c179d4517eb4ba33d5
During bylaw updates to move the OpenStack TC specific rules
to TC charter, Appendix 4 has been removed from Bylaw and most of
the content written there was moved to TC charter.
Removing its reference also.
- https://openinfra.dev/legal/bylaws
Change-Id: I23d0c1dc0096b5270fec16eb5078300d2eb36501
When we have the leaderless project, we should also check the
project activity and if any project is not up to date to their
basic activies then TC should discuss it to mark Inactive.
Ref: This was discussed in previous PTG (2023.2 vPTG):
- https://etherpad.opendev.org/p/tc-2024.1-tracker#L7
Change-Id: I7bcdb6051b6504b4155df06b263ae9bd9bf11b05
We introduced the DPL model in 2020 and many projects tried and
continued this leadership model. One thing that lacked or did not
work out is the monitoring of liaisons activeness. We relied on
the project team liaisons to be active and if they are not or
they cannot serve in that role anymore, they modify the same
in project.yaml. Also, TC members are to keep monitoring the liaison's
status at regular intervals. But none of these things helped and
there were cases that liaisons were not active and so was the project.
To have an easy monitoring policy, this change proposes a TC liaison
as a required liaison for the DPL projects who will monitor the
project activities as well as reset the DPL model and liaison status.
This way we can explicitly know if DPL liaisons are active and if any
project would like to continue the DPL model they need to opt-in every
cycle.
Change-Id: I915e55f8e6175185658cb60d369b3f649e964db0
Distributed project leadership model details are written
in resolution only
- https://governance.openstack.org/tc/resolutions/20200803-distributed-project-leadership.html
but many times we need to gradually develop/amend this model for
example, in vPTG we discussed adding a monitoring policy for
DPL liaisons
- https://etherpad.opendev.org/p/apr2024-ptg-os-tc#L297
It is not easy to amend resolution for such changes and all the amendment
will be distributed in different resolutions which will make it hard to
have the latest policy/document at single place.
The content of the resolution is not changed in the new reference doc and
any further amendment will be done later.
Change-Id: I5518308b6d3f9e83547c43c30fe00b2f1972fdb5
Currently we try to monitor and move the inactive project to
Inactive state before milestone-2 which is deadline from the
release team. But there are chances that either TC detect the
inactive projects late or project can become inactive
after milestone-2. In that case, TC needs to discussion it
in details and considering all risk take decision. Modifying
the process doc to explicitly cover this case just in case
if we see project not fixing security bug or other critical
issue in project after m-2.
- https://etherpad.opendev.org/p/apr2024-ptg-os-tc#L303
Change-Id: I0c3908c93bc12db1fb8ef0d2c433352a83e49554
The repository is to contain the code
of the OSH plugin for Helm CLI tool.
Helm allows users install plugins from git
repos but it assumes cloning the whole git
repo to the user's machine which is not
desirable.
This repo will contain only a small portion
of the OSH code which provides some convenience
to users when they deploy Openstack using
OSH charts.
Depends-On: I1ec3e19c0dd8c83382e803525dd0b9612cfa75f8
Change-Id: Ib4b5e3baa22f87a19b3f75952eb8b587acd8283b
I felt deeply motivated to learn this role and our
collective governance processes. I'm very thankful for
the encouragement that I received to try it and learn
it best.
Change-Id: I683064e311e7e9f9d6e19a8474d21f355b006b79
Also clear out existing TC roles and prepare for nominations.
Depends-On: If6c157efebc58d1fbe32a61a64f209b4102ac5c8
Change-Id: If655aa9adc22a8d49e5672890342e1f4d6e99c40
