Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda)
 
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. It is an elected group that represents the contributors to the project, and has oversight on all technical matters.
 
  
The Technical Committee is formally defined in the [[Governance/Foundation/Bylaws|OpenStack Foundation bylaws]] (in particular article 4.1(b), article 4.13 and Appendix 4) and further refined in the [[Governance/Foundation/TechnicalCommittee|Technical Committee charter]].
+
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/ .
  
=== Members ===
+
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]].'''
  
{| border="1" cellpadding="2" cellspacing="0"
+
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.  The first meeting of the month is usually a video meeting; connection information will be posted below when that's the case.
|- bgcolor=#eeeeee
 
| Name                 
 
| End of term   
 
|-
 
| James E. Blair (jeblair)         
 
|  April 2015 
 
|-
 
|  Russell Bryant (russellb)     
 
|  October 2014
 
|-
 
| Thierry Carrez (ttx)         
 
|  April 2015
 
|-
 
|  Sean Dague (sdague)     
 
|  October 2014
 
|-
 
|  Anne Gentle (annegentle)     
 
|  October 2014
 
|-
 
|  Doug Hellmann (dhellmann)     
 
|  October 2014
 
|-
 
|  Vish Ishaya (vishy)           
 
|  April 2015
 
|-
 
|  Mark McClain (markmcclain)     
 
|  April 2015
 
|-
 
|  Mark McLoughlin (markmc)     
 
|  October 2014
 
|-
 
|  Jay Pipes (jaypipes)       
 
|  April 2015
 
|-
 
|  Michael Still (mikal)       
 
|  April 2015
 
|-
 
|  Monty Taylor (mordred)       
 
|  October 2014
 
|-
 
|  Devananda van der Veen (devananda)
 
|  April 2015
 
|}
 
  
=== Mailing-list ===
 
  
The [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc openstack-tc mailing-list] is used for communication within the Technical Committee. Posting is moderated for non-members.
+
=== Next Meeting ===
  
=== Meeting ===
+
* Date:  2024 May 7
 
+
* Time: 18.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting
Next meeting: Tuesday July 8th, 20:00 UTC
+
* Chair: Goutham Pacha Ravi (gouthamr)
 +
* Agenda to be published on the OpenStack-discuss mailing list before the meeting
 +
* Location: IRC + Video
 +
** Video (Zoom) Meeting: https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09
 +
** IRC (OFTC): #openstack-tc
  
 
==== Agenda ====
 
==== Agenda ====
  
* Core Capabilities TC scoring
+
* Roll call
** Current version of DefCore capability scoring [https://review.openstack.org/100721]
+
* DPL model improvement proposals and TC Liaisons
** Propose scores for DefCore capabilities [https://review.openstack.org/100722]
+
** #link https://review.opendev.org/c/openstack/governance/+/916822 (Move DPL model into doc)
* Election behavior guidelines
+
** #link https://review.opendev.org/c/openstack/governance/+/916833 (Add DPL model & liaison reset policy)
** A resolution on standards of behavior during elections [https://review.openstack.org/100445]
+
** #link https://review.opendev.org/c/openstack/governance/+/917516 (TC liaisons for requirements, release management and ; freezer is the fourth)
** Adds a resolution addressing expected election behaviour [https://review.openstack.org/98675]
+
* Next steps on PyPi Maintainers cleanup
* Other governance changes
+
** #link https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup (Notes on PyPi maintainership of OpenStack packages)
** Modify Images mission to fit Artifact Repository [https://review.openstack.org/98002]
+
* 2024.2 TC Tracker
** Add translation support requirement [https://review.openstack.org/97872]
+
** #link https://etherpad.opendev.org/p/tc-2024.2-tracker (Technical Committee activity tracker)
** Resolution requesting designated sections from projects [https://review.openstack.org/100675]
+
* Ongoing business
* Housekeeping changes
+
** Gate Health updates
** Rename security-guide to security-doc [https://review.openstack.org/104295]
+
* Open Discussion and Reviews
** Add docs-specs repo to Documentation program [https://review.openstack.org/104293]
 
** add keystonemiddleware to keystone projects [https://review.openstack.org/102305]
 
** Adding Horizon mission statement [https://review.openstack.org/102050]
 
* Open discussion
 
  
==== Backlog ====
+
==== Absence ====
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 bylaws yet, or are blocked for some other reason:
+
*
  
* Integrated projects and new requirements: Gap analysis for Swift
+
=== Past meetings logs ===
* Integrated projects and new requirements: Gap analysis for Heat
 
 
 
 
 
At every milestone we should review progress on the incubation/integration gap coverage plans:
 
* [[Governance/TechnicalCommittee/Neutron_Gap_Coverage|Neutron gap coverage plan]]
 
* [[Governance/TechnicalCommittee/Trove_Gap_Coverage|Trove gap coverage plan]]
 
* [[Governance/TechnicalCommittee/Ceilometer_Gap_Coverage|Ceilometer gap coverage plan]]
 
* [[Governance/TechnicalCommittee/Horizon_Gap_Coverage|Horizon gap coverage plan]]
 
* [[Governance/TechnicalCommittee/Glance_Gap_Coverage|Glance gap coverage plan]]
 
 
 
==== Apologies for Absence ====
 
 
 
* tbd
 
  
=== Presenting a motion before the 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 video meetings.
 
 
Motions need to be presented at least 4 business days before the next meeting scheduled time. They should be posted to openstack-dev@lists.openstack.org, then 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.
 
 
 
Note that before being voted on, motions must now be presented as a [http://git.openstack.org/cgit/openstack/governance/ governance] change.
 
 
 
=== Past meetings logs ===
 
  
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc
+
[[Category: meetings]]

Latest revision as of 23:22, 1 May 2024


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

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 video meetings.