Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

m
(Next Meeting)
 
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
  
The [[Governance/Foundation/TechnicalCommittee|OpenStack Technical Committee]] is one of the [[Governance|governing bodies]] of the OpenStack project. You can find more information about it, such as the list of its [http://governance.openstack.org current members] or its [http://governance.openstack.org/reference/charter.html governance charter], on the OpenStack governance website at http://governance.openstack.org . It meets weekly in an open meeting in the <code>#openstack-meeting</code> IRC channel on Freenode.
+
The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html 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 [http://git.openstack.org/cgit/openstack/governance 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 [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ #openstack-tc] IRC channel. We also meet formally [http://eavesdrop.openstack.org/#Technical_Committee_Meeting each week] in  #openstack-tc.  
  
  
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* November 3rd, 20:00 UTC
+
* Date:  2026 Jul 7                                                                                             
* Chair: Thierry Carrez (ttx)
+
* 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:
 +
** [https://webchat.oftc.net/?nick=&channels=%23openstack-tc&uio=d4 IRC (OFTC) - #openstack-tc]
  
  
 
==== Agenda ====
 
==== Agenda ====
  
* Add senlin project to big tent [https://review.openstack.org/235172]
+
* Roll call
* Freezer application to join the Big Tent [https://review.openstack.org/239668]
+
** courtesy-ping: gouthamr, noonedeadpunk, tonyb, frickler, spotz[m], dansmith, cardoe, mnasiadka, bauzas
* Added JavaScript to Common Testing Interface [https://review.openstack.org/232756]
+
* Last Week's Action Items
* Introduce assert:can-upgrade tag [https://review.openstack.org/239771] and assert:can-live-upgrade tag [https://review.openstack.org/239778]
+
* Writing the TC vision
* Open discussion
+
* (noonedeadpunk) Barbican UI situation
** Summit feedback
+
** Removed from releasing
** Reconsidering delayed project team applications
+
** Absent in our tracking/not present inactive project list, neither deprecated nor retired, no activity from maintainers
** Automating objective tag updates
+
** A new contributors are volunteering to revive the project, but are denied by current project leadership, because project considered as unmaintained by them
 
+
* A check on gate health
 
+
* TC Tracker, PTG Follow up
==== Backlog ====
+
** #link https://etherpad.opendev.org/p/tc-2026.2-tracker (Technical Committee activity tracker - 2026.2)
These items have been proposed, but are not put on the agenda just yet. Could be that they have not been discussed on openstack-dev for the time mandated by our charter yet, or are blocked for some other reason, or are just delayed while we process the earlier requests backlog:
+
** #link https://etherpad.opendev.org/p/apr2026-ptg-os-tc-summary
 
+
* Open Discussion and Reviews
* Add team:non-diverse-affiliation tag [https://review.openstack.org/218725]
+
** (stephenfin) Add cursive to oslo governance
 
+
*** #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/NCZQCAFU52BRXJ2YHUX6JQT27WHEPV4X/
 
+
*** This is currently maintained is the x namespace and is broken/blocking newer versions of cryptography. We should either move this into oslo (or another team like keystone) else remove use of it across the board.
Delayed project team applications:
+
*** Patches have been open for a while. Can we get a decision?
* Add new project Kosmos [https://review.openstack.org/223674] (no activity yet)
+
**** https://review.opendev.org/c/openstack/governance/+/990124
* Add Juju Charms for Ubuntu to OpenStack [https://review.openstack.org/224797] (no activity yet)
+
**** https://review.opendev.org/c/openstack/project-config/+/990122
* Adding Monasca to OpenStack [https://review.openstack.org/213183] (needs to adopt more of the OpenStack way, reconsider once Mitaka is started)
+
** (noonedeadpunk) Git 3.0 changes: https://git-scm.com/docs/BreakingChanges#_git_3_0
* Add new openstack kiloeyes repository [https://review.openstack.org/210175] (no activity yet)
+
*** switches default branch name from master to main for new repos.
* Add Fuel to OpenStack Projects [https://review.openstack.org/199232]  (needs more collaboration, reconsider once Mitaka is started)
+
*** switches sha-1 to sha-256 checksums, wonder if this can affect some projects, like releases and deployment tools.
* Add Compass to OpenStack Projects [https://review.openstack.org/196973]  (needs to adopt more of the OpenStack way, reconsider once Mitaka is started)
 
* WIP - Add Group Based Policy Project [https://review.openstack.org/161902]
 
 
 
 
 
==== Apologies for Absence ====
 
 
 
* tbd
 
 
 
 
 
=== Proposing discussion topics, motions or other governance changes before the TC ===
 
 
 
Motions need to be presented before Friday 0800 UTC to be added to the next Tuesday meeting agenda for discussion. They should either be posted as a proposed change to the [http://git.openstack.org/cgit/openstack/governance/ governance] repository (on review.openstack.org) or as a "[tc]" thread to openstack-dev@lists.openstack.org, with a pointer to that thread should be posted to openstack-tc@lists.openstack.org to make sure it gets the required attention from TC members. Upon verification, the TC Chair will put the motion on the agenda for the next meeting.
 
 
 
Before being finally voted on, motions will have to be presented as a [http://git.openstack.org/cgit/openstack/governance/ governance] change. As mandated by our charter, the vote on motions won't be closed until we spent a minimum of 4 business days of public discussions, to give a chance to our wider community to chime in on proposed changes.
 
 
 
Additions of code repositories to existing project teams, as well as other instances of governance repository housekeeping, do not constitute a "motion". Those will be approved a week after being proposed, if they have the required approvals (PTLs in the case of a repository addition) and no TC member -1 vote. A -1 vote will result in the proposed change to be reviewed at the next TC meeting.
 
  
 +
==== Absence ====
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===
  
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc
+
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.
  
 
[[Category: meetings]]
 
[[Category: meetings]]

Latest revision as of 06:20, 6 July 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


Agenda

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.