Difference between revisions of "Meetings/TechnicalCommittee"
(→Absence) |
m |
||
| Line 10: | Line 10: | ||
=== Next Meeting === | === Next Meeting === | ||
| − | * Date: 2023 May | + | * Date: 2023 May 9 |
* Time: 18.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting | * Time: 18.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting | ||
* Chair: Kristi Nikolla | * Chair: Kristi Nikolla | ||
* Agenda to be published on the OpenStack-discuss mailing list before the meeting | * Agenda to be published on the OpenStack-discuss mailing list before the meeting | ||
| − | * Location: | + | * Location: #openstack-tc on OFTC IRC |
==== Agenda Suggestions ==== | ==== Agenda Suggestions ==== | ||
| Line 20: | Line 20: | ||
* Roll call | * Roll call | ||
* Follow up on past action items | * Follow up on past action items | ||
| − | |||
** noonedeadpunk write the words for "The Smith Plan(tm)" (the script of the movie about changing PTI and saving the world from the dangers of getting rid of py38) | ** noonedeadpunk write the words for "The Smith Plan(tm)" (the script of the movie about changing PTI and saving the world from the dangers of getting rid of py38) | ||
| − | ** gmann | + | ** gmann to propose reverts for patches that bumped Python requires to 3.9 and add a voting job that depends on all those |
* Gate health check | * Gate health check | ||
| − | |||
| − | |||
* Broken docs due to inconsistent release naming | * Broken docs due to inconsistent release naming | ||
* Schedule of removing support for Python versions by libraries - how it should align with coordinated releases (tooz case) | * Schedule of removing support for Python versions by libraries - how it should align with coordinated releases (tooz case) | ||
| Line 36: | Line 33: | ||
==== Absence ==== | ==== Absence ==== | ||
| − | + | ||
=== Past meetings logs === | === Past meetings logs === | ||
Revision as of 15:16, 8 May 2023
The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. You can find more information about it, such as the list of its current members or its governance charter, on the OpenStack TC governance website at https://governance.openstack.org/tc/ .
In order to include as many people as possible in the discussion, the Technical Committee relies on asynchronous communications as much as possible. We propose and vote on changes through the openstack/governance repository. Large-impact changes are discussed on the openstack-discuss mailing-list. We track current initiatives on the Technical_Committee_Tracker.
Although we don't hold office hours, you can find various members of the TC at various times throughout the week in the #openstack-tc IRC channel. We also meet formally each week in #openstack-tc. The first meeting of the month is usually a video meeting; connection information will be posted below when that's the case.
Next Meeting
- Date: 2023 May 9
- Time: 18.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting
- Chair: Kristi Nikolla
- Agenda to be published on the OpenStack-discuss mailing list before the meeting
- Location: #openstack-tc on OFTC IRC
Agenda Suggestions
- Roll call
- Follow up on past action items
- noonedeadpunk write the words for "The Smith Plan(tm)" (the script of the movie about changing PTI and saving the world from the dangers of getting rid of py38)
- gmann to propose reverts for patches that bumped Python requires to 3.9 and add a voting job that depends on all those
- Gate health check
- Broken docs due to inconsistent release naming
- Schedule of removing support for Python versions by libraries - how it should align with coordinated releases (tooz case)
- Recurring tasks check
- Bare 'recheck' state
- Open Reviews
Absence
Past meetings logs
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc
