Difference between revisions of "Meetings/TechnicalCommittee"

Revision as of 21:43, 1 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 2
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: Video on Zoom (https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09)

Agenda Suggestions

Roll call
Follow up on past action items
- noonedeadpunk to propose a patch to reference that makes the recommendation for downstream packagers to use the version name rather than codename.
- 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 send an email on ML asking project/release team to hold dropping the py38 until we get the pti change merged
Gate health check
2023.2 cycle Leaderless projects
- https://etherpad.opendev.org/p/2023.2-leaderless
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
  - https://etherpad.opendev.org/p/recheck-weekly-summary
Open Reviews
- https://review.opendev.org/q/projects:openstack/governance+is:open

Absence

Past meetings logs

Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc

@@ Line 20: / Line 20: @@
 * Roll call
 * Follow up on past action items
+** noonedeadpunk to propose a patch to reference that makes the recommendation for downstream packagers to use the version name rather than codename.
+** 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 send an email on ML asking project/release team to hold dropping the py38 until we get the pti change merged
 * Gate health check
 * 2023.2 cycle Leaderless projects