A governance/deliverable consistency check revealed that independent
deliverable whitebox-tempest-plugin is defined in the releases repository
(and regularly released) despite being marked release-management:none
in the governance repository.
This fixes this inconsistency to make sure whitebox-tempest-plugin is
included in all release management processes.
Change-Id: I4d4a6ce7992af9c79711279424aa5cf39e35fb58
In the 2024.2 election cycle, the polling period
was three weeks. We noticed a small uptick in
the voting numbers:
- 2025.1: (21.4% voter) Voting period was three weeks
284 authorized voters, votes cast: 61
- 2024.2 (19.1% voter) Voting period was two weeks
298 authorized voters, votes cast: 57
- 2024.1: (16.5% voter) Voting period was two weeks
309 authorized voters, Actual votes cast: 51
While the reason for this uptick cannot solely be
attributed to the change in window, the TC expressed
their preference that the extended voting period
did not hurt. It is allowed for this voting
period to overlap with the week set aside for
TC campaigning - any early voters have the ability
to change their minds and their votes before
polling ends.
Change-Id: I45e12ce715708eb67449dc73db8cffcf3cc70234
In order to unify approach on handling Apache Web server deployment
and configuration team come up with idea to produce a separate role
for that as we have failed with finding existing one which would meet
our intended "pluggable" design.
Based on that a new repo/project is needed as we intend to make
resulting role not opinionated and re-usable outside of OSA scope.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/935693
Change-Id: I2da92910e2897da10283bb93fcb6309c70d09d6e
kuryr-kubernetes and kuryr-tempest-plugin are not active and
also proposed for the retirement
- https://review.opendev.org/c/openstack/governance/+/922507
But the retirement is on hold due to dependency on Tacker. Marking
them as Inactive until we retire them.
Change-Id: Iad39d648f46917ae8abd268cbaf715421b8245af
Also clear out existing TC roles and prepare for nominations.
Depends-On: Id5847c7c37d556b11932dae542f4aaeb699cf7ec
Change-Id: I7760c815d032c7aaff9956588b6ce5c1fb7b4750
As per the testing runtime for 2025.1 cycle, we need to start testing
ubuntu Noble. To implement that, this propose to select this
migration activity as one of the community-wide goal.
Also, fix some typos from:
- https://review.opendev.org/c/openstack/governance/+/928078
Change-Id: I488f322681cc46a2118bfe60262eaec67d47d13d
Projects aren't "Python projects" or "JavaScript projects" but
rather "projects with Python components" and "projects with
JavaScript components." A project might have deliverables with
repositories containing implementations of things in different
languages, or may even have multiple programming languages
represented within a single deliverable repository. Make it more
clear that language-specific PTI guidance is to be followed based on
the languages which are present, rather than implying that projects
are shoe-horned into one specific language.
Change-Id: I77b0b0c889d49f028dd595ed14d8095f450486d6
The sunbeam-charms mono-repo now replaces all individual charm
repositories - remove from the Sunbeam project.
Update validate-legacy.py to deal with repositories which don't
use a default branch of 'master'.
Change-Id: Id5e72114e73a765285c99a21e23c4d6eaa3c15ea
Largely unmaintained and no adoption.
Retire repositories and remove from the OpenStack Charms
project.
Change-Id: I9bba818c86f8b44a9ce7346f7948fb611eb9d414
Depends-On: I5c84630cc9dbd9d67303ff65bbfb4d1677e30d12
Depends-On: I428861f408d57599b9717726b3f6a4a35493e230
Below are the changes from previous cycle
testing runtime:
* Adding Ubuntu 24.04 version which is the latest LTS
* Keeping Ubuntu 22.04 as additional testing because this was
supported in previous SLURP release 2024.1
* Adding python 3.12 as mandatory testing
Change-Id: I8bd10369b929fd6352b91743d2c0393b8452791d
I think monasca is a good project and would like to make it to be more stable.
As a single developer without support from a company, I need more time to do that.
That is the reason I create this merge request.
Change-Id: I893d0d717a8862636d456904aa7d1acd96e53471
