Change Iecc9751091285a5d3c amended resolution 2023-07-24, but left
a note in the original resolution that is far enough away from the
amended point to be confusing. So move it to a better location.
Also put the reference list into a line block so it displays
as intended.
These are formatting changes only; there's no change to the text.
Change-Id: Ide5068e20725cf46e3204c0fc3b2c84d99c8ba80
This patch proposes an amendment to the 2023-07-24 "Unmaintained status
replaces Extended Maintenance" resolution to allow an openstack-wide
group to handle Unmaintained branch changes across all projects by
default, though this can be overridden by individual projects.
Additionally, the original resolution file has been modified to
include a note that the amendment exists along with a link to it.
Change-Id: Iecc9751091285a5d3ca72c8d959136b33e274839
This resolution heavily revises [1] based on
feedback from the July 11, 2023 TC meeting.
1. EM is rename to Unmaintained.
2. Branch deletion and creation under unmaintained/.
3. New Gerrit group responsible for the branch.
4. Mention of TC maintaining a checklist and process.
[1]. https://review.opendev.org/c/openstack/governance/+/887966
Change-Id: I72ac1eab3c6b1b55b4f2bc017d5befaaee138f5f
Once the election are started it is difficult to change the list of
projects need election so any DPL or PTL model change request should
be merged before the election nomination start.
Change-Id: Ia1544d4541926c8f689e0e6f361b7057ed28b64d
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
This resolution is proposing that we rename the
Extended Maintenance SIG to the Stable Maintenance
SIG and empower project teams to further manage
their stable core team and policies.
Change-Id: I2e5dbc5132ec70ac2ffe6e088ba2f77db8f944c2
The TC-approved release was previously defined using a tag, but was
recently redefined to include all official deliverables. Rather than
continue using the tag index page to define it, clearly define it in
a formal TC resolution, making it easier to find.
Change-Id: I15deaf54fb7c1b390e68b065eeb801dcdbb99a94
Some projects have expressed an interest to function without a PTL.
This resolution defines how a project would work with the
responsibilities of the PTL role separated into liaison roles instead of
held by a single individual.
Change-Id: I183f616e66d13066cd91e2659e1e90f5d2798d69
Co-Authored-By: Jean-Philippe Evrard <jean-philippe@evrard.me>
One of the goals of the OpenDev effort is that it be applicable to
projects that are not OpenStack. While the OpenStack TC and goverance
has worked for us previously, we believe that officially splitting off
OpenDev gives it the freedom it needs to properly address user needs
beyond OpenStack.
Details on OpenDev's future plans can be found here:
http://lists.openstack.org/pipermail/openstack-infra/2019-December/006537.html
Co-Authored-By: Clark Boylan <clark.boylan@gmail.com>
Needed-By: https://review.opendev.org/703488
Change-Id: I512a000720d6402faa3e51551fe4e5841b1231ac
This is to:
1. Remove the dead cross-project specification-liaison team link
2. Fix the inaccurate support phases link.
Change-Id: Iefab661bbc2aff4118b7f21708bae5fda45b3f2f
The previous wording introduced unneccesary confusion about when the
goal would be set. Clarify that the goal is set at the beginning of a
release cycle as usual, and should be completed by the end of the
release cycle.
Also, avoid using the word 'support' to refer to which versions of
Python we run unit tests on.
Change-Id: I461ba0c0d4bc1e3d7e2b71ab614003733afdd4ea
Sphinx 1.5 and later allows a :reversed: parameter for :glob:
toctrees. Since we're presenting our resolution index in reverse
chronological order grouped by year, reversing the glob order keeps
the dates within each year consistently ordered as well. Yes, this
is probably me being OCD.
The SIGs governance resolution file was inconsistently named,
leading to it showing up outside the expected sort order. Rename the
file and add a permanent redirect from the old URL to the new one.
Related cleanup, the main index toctree was incorrectly marked as a
:glob: even though it didn't use any wildcard patterns so has been
corrected.
Change-Id: Ifbc6db87e41f01311b430080b97154d01708a2d4
We've been dealing with how to make appointed PTLs official and
documented in a rather ad hoc fashion: something different each
cycle.
This change provides a house rule which puts the responsibility
and the documentation in the combined hands of the appointed PTL
and the TC that appointed them and not election handling (where
it doesn't make sense since no election happened).
Change-Id: Idf78e00c59d10528a2b4950f8baa93c6731973ea
We have been operating SIGs for some time now with a very loose
governance model. We took this approach on purpose to give folks
space and opportunity to decide what they believed constituted
a SIG in hopes of learning how we can apply SIGs to our community
needs.
However at this point there is some confusion and concern regarding
SIG governance. Since SIGs explicitly do not sit below any existing
governance structure, there is no default solution to fall back on.
We need to define a clear way to address issues before any conflict
arises. As was the case elsewhere, we expect the mere existence of
a clear decision-making structure to prevent most conflicts from
happening.
This resolution proposes a minimal, simple governance model to
address such cases, introducing a SIGs admin group. The group
is initially formed of the Meta SIG co-leads: Melvin Hillsman
as UC representative and Thierry Carrez as TC representative.
The committees are of course free to choose new members whenever
they see fit.
A similar resolution was proposed to the User Committee, which
approved it:
http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-03-12-14.05.log.html#l-74
Change-Id: Ibc2336980739db38f64a42b8ba2adeacff000a13
Co-Authored-By: Melvin Hillsman <mrhillsman@gmail.com>
The typo was identified during voting, but did not want to ruin the
votes for this fix. So doing so in this follow up.
Change-Id: I9d4b9fc9f7b57155d7e4f5eba046ce1a0a5faded
We've talked about this for years, and talked some more at the
Rocky PTG. This adds a resolution to try and document / summarize
the outcomes of the Sydney summit and Rocky PTG.
Change-Id: I94b0421d8a489026300789b61b0293dd2e61726d
This provides an alternative to
I91315c3c42b8a329d1763f9de80aa3d0270ac044 to provide simplified
guidance on use of plugins for trademark tests. The coauthors below
represents the people who were activce in the creating and refining
these ideas.
Change-Id: I2e68c8e855e7c6c1e4f985f38a0a38de451407a3
Co-Authored-By: Graham Hayes <gr@ham.ie>
Co-Authored-By: Zane Bitter <zbitter@redhat.com>
Co-Authored-By: Andrea Frittoli <andrea.frittoli@gmail.com>
Co-Authored-By: Mark T. Voelker <mvoelker@vmware.com>
Co-Authored-By: Jim Rollenhagen <jim@jimrollenhagen.com>
Co-Authored-By: ricolin <rico.lin@easystack.cn>
Jay Faulkner