Due to decision for resetting DPL model each cycle, I'm opting-in for
the DPL model for Freezer project for the next cycle as well.
Change-Id: I521eaeef9eecf549fbf376c05ddaef3a15ca34c6
First round of follow up.
This patch only fix typos from comments made on:
https://review.opendev.org/c/openstack/governance/+/902585
This patch also reword a title to make it less ambiguous.
Other kind of comments will be addressed later.
Change-Id: Ida1b2b71b1be72f99af7870b1251ce123a4f8274
As the last emerging project has transitioned to active, make the list
of emerging projects say "None" instead of just being non-existent.
Change-Id: I262da09b760495b6bb9a4a5d542726b97b443edd
This was discussed during the TC session in the vPTG in April 2024 that
we should raise the bar for an inactive projects to become again active
official OpenStack projects.
This patch updates the emerging technology and inactive projects
document to require from inactive projects that they need to meet all
the requirements to be active for at least one full cycle and only then
in next cycle such project can be considered by the TC to be active
again.
Change-Id: Ie16888099f1ed938b7753808984c7368ea2300a6
Fix vague language around what
TC's git repositories contain; and
fix references to the
OpenInfra Board of Directors, and
the now-dissolved User Committee
Change-Id: I15c34541d16c432b41e4db52e73569a81ceeb889
There are multiple organizations that my be reigniting interest in
watcher recently. Since it is passing tests, has good coverage, and
seems to still work, we are moving it to DPL with liaisons that are
present to give some more time for evaluation and contributors to
show up.
Change-Id: Ifd8418dc68f7447a208fbf0073b481ecf7504fb3
Sometimes, the project need more time to become active, and TC
can discuss their extension to stay Inactive. Adding the project
Inactive state extension in the timeline section (basically
"entered" to "entered or extended"). It means extension cycle
will be considered as the latest cycle for the Inactive project
timeline/next step.
Freezer project became inactive in 2024.1 cycle, and the
new maintainers took over the project maintenance. They
are working on making project active but need more time.
This proposes the extension for this project to stay inactive
for this cycle.
Change-Id: I7a5b3cab1323a20225b929e2002dabec3eebdce6
We need to generate a timezone aware "now" time
the proper way since the utcnow() method was
deprecated in python 3.12.
[1] https://blog.ganssle.io/articles/2019/11/utcnow.html
Change-Id: Ic91dbd3d0fb0bab5725d09fd8d658baaefed8440
When docs moved back under projects several docs repos were
put under the TC where they have not counted towards AC
status
governance update
Change-Id: I1e64844b79fe1a6c9e792f421299575bfaf18464
Last year, we moved the TC affiliation diversity requirement from
the Board bylaw to the TC charter, but we did not define the rules
to handle a violation of the diversity requirement.
During the 2024.2 TC election, we encountered a situation where the
diversity requirement was violated[1]. Due to the lack of defined
rules in the TC charter, we were unable to effectively resolve the
situation, resulting in an undesirable outcome.
As discussed at the PTG[2], we need to define some rules in the
charter to better handle such situations in the future. To keep it
simple, the proposal here is to select another affiliation member
(who does not violate the affiliation diversity) based on their
ranking in the election voting. This rule is align with the Board
diversity requirement voilation rules[3].
[1] https://governance.openstack.org/tc/resolutions/20240322-adjudication-of-2024.2-tc-election.html
[2] https://etherpad.opendev.org/p/apr2024-ptg-os-tc#L219
[3] https://openinfra.dev/legal/bylaws (Section 4.15 Director Diversity)
Change-Id: I1857cd95991abaad7fcdd7657d88eff7f44631ab
Doing this is useful since we lack
human-readable web pages to point to
when answering the question:
"What repositories are under
OpenStack TC's governance charter?"
Change-Id: I5672a7f0ce3de32d8fc0577fee8354552d2962ce
As there was no candidate for OpenStack Charms PTL in the
2024.2 election, I hereby volunteer to take up this role.
Change-Id: Ic7d3a5fc4c93d19f490064ae29a2920f58bf23e8
As per new policy, TC liaison is mandatory for all DPL
model projects, this change adds the same in its
implementation. Also, assigning the same for existing
DPL projects. All new request to the DPL model should have
TC liaions as required.
Change-Id: Ib6067a45002bad0d2ee658de96ebe79aa86e223a
