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
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
- add `codegenerator` repository used to generate OpenAPI specs from
service sources and client API bindings from the OpenAPI
- add `openapi` repository with documents describing OpenStack
flavouring of OpenAPI and Sphinx extension to render them similar to
os-api-ref
- slightly adapt the overall team mission to better match the reality
Depends-On: https://review.opendev.org/c/openstack/project-config/+/910580
Change-Id: I3513c3363eed62155291f2d9bf094bf07725df64
Below are the changes from previous cycle
testing runtime:
* Removing python 3.8 support because it is EOLing in oct 2024[1]
which means python 3.9 will be the minimum python version in
testing runtime.
* Add Python 3.12 as non voting testing.
* Remove Debian 11 from Additional testing support because 2024.2
is non-SLURP release and previous SLURP release 2024.1 supported
Debian 12 also which is what can be used as smooth upgrade to
future SLURP release 2025.1
* Removing Nodejs from runtime:
Nodejs is not a runtime requirement for Horizon instead it is
one of the test dependency. It does not fit as a runtime and can
be handle by Horizon team based.
* For better clarity, changed the 'Best Effort' section to
'Advance/Unstable Testing'. Adding Ubuntu 24.04 in that list.
[1] https://devguide.python.org/versions/
Change-Id: I77dbbf2413074ce0cddbfe6ac2f29d0ee1d71921
Murano project is not active as there is no response
from their maintainers/PTL on ML[1] or to the vmt on security
issue[2]. Also their gate is broken[3], while fixing the
python 3.11 job we found that their functional/tempest jobs
are broken.
The last change merged on master was 6 months ago which is
translation bot change. Project contribution stats:
./tools/project_stats_check.py -p murano
**************************************************
Start Project murano analysis...
Includes repositories: ['openstack/murano', 'openstack/murano-agent', 'openstack/murano-apps', 'openstack/murano-dashboard', 'openstack/murano-pkg-check', 'openstack/murano-specs', 'openstack/python-muranoclient', 'openstack/murano-tempest-plugin']
Start analysis branch master...
Validating Gerrit...
* There are 11 ready for review patches generated within 180 days
* There are 1 not reviewed patches generated within 180 days
* There are 2 merged patches generated within 180 days
* Unreviewed patch rate for patches generated within 180 days is 9.0 %
* Merged patch rate for patches generated within 180 days is 18.0 %
* Here's top 10 owner for patches generated within 180 days (Name/Account_ID: Percentage):
- OpenStack Release Bot : 36.36%
- Ghanshyam : 27.27%
- Alexandre Detiste : 9.09%
- Sam Morrison : 9.09%
- OpenStack Proposal Bot : 9.09%
- zhurong : 9.09%
[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/DFFI3SQ3344JWEXZBMO46THB5IR3DF6C/
[2] https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2024-02-12.log.html#t2024-02-12T08:08:47
[3] https://review.opendev.org/c/openstack/murano/+/904673
Change-Id: Idecbf676e328e0dc3aba2af69ec437a85d703dfa
Zuul