Difference between revisions of "Meetings/TechnicalCommittee"
< Meetings
(→Agenda) |
(→Agenda) |
||
| Line 22: | Line 22: | ||
* Roll call | * Roll call | ||
** courtesy-ping: gouthamr, noonedeadpunk, tonyb, frickler, spotz[m], dansmith, cardoe, mnasiadka, bauzas | ** courtesy-ping: gouthamr, noonedeadpunk, tonyb, frickler, spotz[m], dansmith, cardoe, mnasiadka, bauzas | ||
| − | * Last Week's | + | * Last Week's Action Items |
| − | |||
| − | |||
| − | |||
| − | |||
* Updates to PTI (stephenfin) | * Updates to PTI (stephenfin) | ||
** Main proposal is to adopt [https://peps.python.org/pep-0735/ PEP-735] dependency groups to capture our non-runtime dependencies (unit testing, linters, documentation, ...) as a step towards allowing us to move past requirements.txt files, which are pip-specific and largely being abandoned by upstream Python. See the pkg_resources removal and sqlalchemy 1.x->2.x for reasons why not investing in keeping up with the broader ecosystem is a bad idea. | ** Main proposal is to adopt [https://peps.python.org/pep-0735/ PEP-735] dependency groups to capture our non-runtime dependencies (unit testing, linters, documentation, ...) as a step towards allowing us to move past requirements.txt files, which are pip-specific and largely being abandoned by upstream Python. See the pkg_resources removal and sqlalchemy 1.x->2.x for reasons why not investing in keeping up with the broader ecosystem is a bad idea. | ||
| Line 34: | Line 30: | ||
*** An alternative would be to delete that doc and re-evaluate go(lang) support if anyone decides to use it in the future | *** An alternative would be to delete that doc and re-evaluate go(lang) support if anyone decides to use it in the future | ||
*** #link https://review.opendev.org/c/openstack/governance/+/988440 (openstack/governance change) | *** #link https://review.opendev.org/c/openstack/governance/+/988440 (openstack/governance change) | ||
| + | * Keeping release liaisons up to date (Duplicate info for DPL teams, inactive liaisons) | ||
| + | ** #link https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml | ||
| + | ** #link https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml | ||
| + | ** #link https://review.opendev.org/c/openstack/releases/+/984110 | ||
| + | ** #link https://review.opendev.org/c/openstack/governance/+/988780 | ||
| + | * A check on gate health | ||
| + | * TC Tracker, PTG Follow up | ||
| + | ** #link https://etherpad.opendev.org/p/tc-2026.2-tracker (Technical Committee activity tracker - 2026.2) | ||
| + | ** #link https://etherpad.opendev.org/p/apr2026-ptg-os-tc-summary | ||
* Open Discussion and Reviews | * Open Discussion and Reviews | ||
Revision as of 22:20, 18 May 2026
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.
Next Meeting
- Date: 2026 May 19
- Time: 1700 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting
- Chair: Goutham Pacha Ravi (gouthamr), Michał Nasiadka (mnasiadka)
- Agenda to be published on the OpenStack-discuss mailing list before the meeting
- Location:
Agenda
- Roll call
- courtesy-ping: gouthamr, noonedeadpunk, tonyb, frickler, spotz[m], dansmith, cardoe, mnasiadka, bauzas
- Last Week's Action Items
- Updates to PTI (stephenfin)
- Main proposal is to adopt PEP-735 dependency groups to capture our non-runtime dependencies (unit testing, linters, documentation, ...) as a step towards allowing us to move past requirements.txt files, which are pip-specific and largely being abandoned by upstream Python. See the pkg_resources removal and sqlalchemy 1.x->2.x for reasons why not investing in keeping up with the broader ecosystem is a bad idea.
- #link https://review.opendev.org/c/openstack/governance/+/988439/ (openstack/governance change)
- #link https://review.opendev.org/c/openstack/requirements/+/987879/ (openstack/requirements change)
- Secondary proposal to indicate that the golang PTI is massively out-of-date and needs work to be usable
- An alternative would be to delete that doc and re-evaluate go(lang) support if anyone decides to use it in the future
- #link https://review.opendev.org/c/openstack/governance/+/988440 (openstack/governance change)
- Main proposal is to adopt PEP-735 dependency groups to capture our non-runtime dependencies (unit testing, linters, documentation, ...) as a step towards allowing us to move past requirements.txt files, which are pip-specific and largely being abandoned by upstream Python. See the pkg_resources removal and sqlalchemy 1.x->2.x for reasons why not investing in keeping up with the broader ecosystem is a bad idea.
- Keeping release liaisons up to date (Duplicate info for DPL teams, inactive liaisons)
- #link https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml
- #link https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml
- #link https://review.opendev.org/c/openstack/releases/+/984110
- #link https://review.opendev.org/c/openstack/governance/+/988780
- A check on gate health
- TC Tracker, PTG Follow up
- #link https://etherpad.opendev.org/p/tc-2026.2-tracker (Technical Committee activity tracker - 2026.2)
- #link https://etherpad.opendev.org/p/apr2026-ptg-os-tc-summary
- Open Discussion and Reviews
Absence
Past meetings logs
Logs of past TC meetings can be accessed at http://eavesdrop.openstack.org/meetings/tc for IRC meetings and https://www.youtube.com/@openstack-tc for past video meetings.
