There are updates to the OpenInfra Foundation bylaws that
cleans up some of the old special-case text for the OpenStack
project. Some of the changes in bylaws are important to the
OpenStack governance (for example, diversity requirement) so
we are moving those changes in the OpenStack TC charter.
OpenInfra Board has approved the bylaws changes as sent in
the below email attachment:
- https://lists.openinfra.dev/archives/list/foundation@lists.openinfra.dev/thread/6FBOOK7WVBRHYOBQPTF2T2CNJOO7XMSQ/
- https://board.openinfra.dev/meetings/2023-12-05
That attachment shows the bylaws changes and what needs to be
moved to OpenStack TC charter or to the Openinfra Project
Confirmation Guidelines.
This commit update the OpenStack TC charter for the required
changes in the bylaws.
Change-Id: Iaff919fc99b8270bc7562a61ea73c5304a0f4acf
As discussed in PTG[1], TC agreed to extend the PTL
and TC election nomination as well as the voting
period to 2 weeks. Accordingly, clearify and change the
deadline of elections.
[1] https://etherpad.opendev.org/p/tc-2023-1-ptg#L495
Change-Id: Ic126e2891270b986a22badfd8d2fcb701124082f
Foundation bylaws mention the "ATC" term and during
the merging of UC to TC we changed it to "AC". Adding a line
stating that both are the same term and that way we will comply
with the bylaws also
- https://openinfra.dev/legal/openstack-technical-committee-member-policy
Change-Id: Icd7efda1d7a49c6ddb1b7f4ac9687e7e6b231a84
As discussed in PTG, we will try the DPL model first for
the leaderless projects or if PTL assignment is needed in between
of the cycle.
- https://etherpad.opendev.org/p/tc-zed-ptg#L109
Change-Id: Ie65553720247b585be94d53811a2ade20353f9cc
We don't use openstack-dev mailing list since some time. This patch
changes it to point to openstack-discuss which is currently used and
active mailing list.
Change-Id: Ic559a67ec661d896d9b266a916cfc10a318d23ce
We had situation in past where we stuck to change the charter
becasue of vacant seat because total number of TC members were
not present to pass the motion.
These type of situation should not hold the TC work and we should
count current number of TC members as complete TC to continue work
on motion, charter etc.
Change-Id: I25c2894a7beb48968edb222cc7ff859fbd392154
This proposes to replace the ATC terminology with AC (Active
Contributor). This makes it clear that ACs are not just people with
technical project contributions. Those contributions are the easiest
way to build the initial list, and automatically qualify a person, but
harder-to-quantify contributions still qualify and we have a procedure
for doing so.
Change-Id: I8ac41cbab493be6a8d58b21234717524edfa70e7
let's add election schedule exceptions reference page in
TC charter so that we can follow the exception
process in future.
Change-Id: I9a7574a71ebdb7a64958e026767016e497e8ff43
The charter currently mandates that after a motion receives sufficient
votes to pass, it must stay open for further comments and voting for a
minimum of 3 calendar days. This is in addition to motions needing to
stay open for a minimum of 7 calendar days.
This grace period is a bit impractical to enforce, and in some cases
just delays decisions and creates frustration. This change removes it
from the charter, and advise to apply common sense instead. If the
chair senses that there are concerns that are still unvoiced, a delay
should be applied. If all else fails, it's easy enough to revert a
change if someone disagrees after the fact, using our 'rollback'
house rule[1].
[1] https://governance.openstack.org/tc/reference/house-rules.html
Change-Id: Ib3e12511a8d551ac4fcc76cec79f14b46a704ce0
This change propose two changes in charter:
1. Revise the TC election dates + Clarify the TC terms.
2. Add election required for the vacancy if there
are no candidates available to fill the vacant seats when needed.
Change-Id: I599d84d2b75681449f357c316480772621a069ec
Over 2020 elections, gradually reduce the TC to 9 members by
renewing two less seats than you normally should.
A 9-member TC would strike the right balance between diversity of ideas
(for good representation of the community) and number of available
stewards.
Change-Id: I484f286553c9db061b613dace39e7995e1cf9a24
Update the :repo: shorthand role to use opendev instead of cgit links
in project team pages.
Make sure that the other content under the reference/ directory is
updated to use :repo: instead of cgit links (except the one in
pti/javascript.rst which should really point to the NPM package).
Change-Id: I1009ba2a0f8d0fd1dab26f05241903b71c63e4fb
Add the gerrit topic tag to use when applying each house rule to a patch.
Change-Id: Ia8c2ae26fc7e60f7bc3f03fb4898cf91de36773d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We've had a couple projects go through changes in leadership, for
which we do have a couple formalities, but they weren't written down.
This commit updates the charter to include the items that need to be
taken care of if a PTL steps down and appoints another individual to
the role.
Change-Id: Ie162d3c66abc698bf31e7224530869a836e111e9
Now that we are resuming meetings, update the charter section that
documents what we agreed to do. Include text encouraging folks not to
wait for meetings to raise topics.
Change-Id: I2de10118262fd91e0c83f9af5b8f203b65dccdff
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We currently make no provision for the chair to be able to delegate or
otherwise share their responsibilities. This change defines a new vice
chair role to give us a way to designate someone to act in a
supporting role for the active chair and to take over in the chair's
absence so that business does not need to halt when the chair is
unavailable.
Change-Id: I3e520eb0d900bc3d0552afbb5bcb9fd13fd0d09c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The existing 3 weeks prior to summit target for TC elections can be
problematic for travel planning for candidates who might only go to
summit if they win their election, or might plan a different length
of trip depending on their role(s) in the community. This change
makes the target for the election to be six weeks prior to summit
to ease that planning.
In addition to helping with travel concerns, it also means that any
newly elected TC members will be more involved in planning for the
forum at the summit.
If approved this change would go in effect for the second election
in 2018. The first election of 2018 is already scheduled.
Change-Id: Ie1a7d9bae28864fb7413d8df2daa67abc5c70778
A while ago it was decided[0] that motions, before being
merged/approved, should be discussed and voted on during the Technical
Committee meetings. This worked well back in the days but it's not
necessary anymore. This was carried over even though we now have an
asynchronous voting system and it was never properly documented or
re-evaluated.
This patch documents how formal-vote patches are voted on and eventually
approved.
[0] http://lists.openstack.org/pipermail/openstack-dev/2013-August/013339.html
Change-Id: Ie84bacb9038d82bdfb518724a8e6fb726f5a0316
Since voting now happens asynchronously, it's not necessary to proxy
voting through other TC members.
Change-Id: I77c036fa49468c80ffff687ab4de86d95c031d84
With the Design Summit functions being split between the OpenStack
Summit and the Project Teams Gathering, the current wording in the
TC charter around election (which uses "Design Summit" and "Summit"
interchangeably) is no longer valid.
This change clarifies the situation by:
* keeping PTL elections near to development cycle boundaries
(but defining the timeframe relative to release rather than
relative to an event)
* keeping TC elections on a 6-month spring/fall cadence,
organizing them relative to the OpenStack Summit dates
The change is compatible with the language around TC elections
present in the OpenStack Foundation bylaws (esp. Appendix 4),
which mentions 6-month and one-year periods but does not attach
TC elections to events or cycles. This change therefore should
not require any change on the bylaws side.
While it tries to minimize impact, the net result of the change
is that TC elections are now separate from PTL elections (rather
than run just the week after).
This change also adds some flexibility in vote organization, by:
* using "on or before" language to allow election officials to
work around holidays
* removing language around nomination periods (potentially allowing
for the addition of "campaign days" between nomination and vote)
* lowering the minimum required amount of voting days to 4 business
days (potentially allowing the vote to be organized within a week
rather than forcing it to overlap with a weekend)
Change-Id: I5900f9b4a10cbdb09609516d0b04f29b4fe7eb88
We have a data file containing the extra ATCs for all projects, but the
list is not published in an easily readable format. Add the list of
extra ATCs to the project pages.
Change-Id: I8e8c5ca9b24d4c58f3813924c93dece12b20d397
Move from a program-driven project structure (which prevented
competition and innovation) to a project-based structure. Introduce
new simple objective requirements for future OpenStack projects.
Remove incubation process (keeping old incubation/integration
requirements doc around as a reference until it's converted into a set
of representative tags).
This change is heavily based on a previous proposal by Doug Hellmann
(see https://review.openstack.org/#/c/131422/1)
Change-Id: Ida9f60d8cbd0dcf48669b82e619fc4016ee0bcb7
Create index pages with toctree entries to load the existing
documents so they are all linked together.
Add titles to some of the documents that did not have them to
make them work with sphinx.
Change-Id: I0d44cfe1a75ab7df07e0efc989eb7cf161d9bf78
This converts 2 of the reference documents to rst, and fixes the
tox.ini so that tox -e docs creates a pretty html version of these
documents. While the publish target location has still not been
sorted this moves the ball forward in generating nicer output
for the documents.
The incubation-integration-requirements document was intentionally
left out, because it's much more active, and we should decide this
is the right approach before we impose the merge conflicts on
everyone in flight.
Change-Id: I2fefdb5efe196cdbda4555141b09e7e771e20bdd
Ghanshyam Mann