Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Next Meeting)
 
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
<!-- #acl [[ThierryCarrez]]:read,write,revert All:read -->
 
= Technical Committee =
 
  
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 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/ .
  
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]].
+
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]].'''
  
== Members ==
+
We hold office hours at [https://governance.openstack.org/tc/#office-hours various times] during the week on the [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ #openstack-tc] IRC channel. We meet formally [http://eavesdrop.openstack.org/#Technical_Committee_Meeting each week] in  #openstack-tc
  
{| border="1" cellpadding="2" cellspacing="0"
 
|<#eeeeee>| Name                 
 
|<#eeeeee>| Election   
 
|-
 
|  Russell Bryant (russellb)     
 
|  Directly-elected     
 
|-
 
|  Thierry Carrez (ttx)         
 
|  Directly-elected     
 
|-
 
|  John Dickinson (notmyname)   
 
|  Swift PTL           
 
|-
 
|  Anne Gentle (annegentle)     
 
|  Directly-elected     
 
|-
 
|  John Griffith (jgriffith)     
 
|  Cinder PTL           
 
|-
 
|  Joe Heck (heckj)             
 
|  Keystone PTL         
 
|-
 
|  Gabriel Hurley (gabrielhurley)
 
|  Horizon PTL         
 
|-
 
|  Vish Ishaya (vishy)           
 
|  Nova PTL             
 
|-
 
|  Mark McLoughlin (markmc)     
 
|  OpenStack-Common PTL
 
|-
 
|  Jay Pipes (jaypipes)         
 
|  Directly-elected     
 
|-
 
|  Monty Taylor (mordred)       
 
|  Directly-elected     
 
|-
 
|  Brian Waldon (bcwaldon)       
 
|  Glance PTL           
 
|-
 
|  Dan Wendlandt (danwent)       
 
|  Quantum PTL         
 
|}
 
  
== Mailing-list ==
+
=== Next Meeting ===
  
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.
+
* Date: Oct 28th, 2021
 +
* Time: 15.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting
 +
* Chair: Ghanshyam Mann
 +
* Agenda to be published on the OpenStack-discuss mailing list before the meeting
 +
* Location: #openstack-tc channel on OFTC
  
== Next meeting ==
+
==== Agenda Suggestions ====
  
First TC meeting will happen in-person during the OpenStack Summit in San Diego. Details will follow.
+
* Roll call
 +
* Follow up on past action items
 +
* Gate health check (dansmith/yoctozepto)
 +
** http://paste.openstack.org/show/jD6kAP9tHk7PZr2nhv8h/
 +
* Project Health checks framework
 +
** https://etherpad.opendev.org/p/health_check
 +
** https://review.opendev.org/c/openstack/governance/+/810037
 +
* Stable team process change
 +
** https://review.opendev.org/c/openstack/governance/+/810721
 +
* Technical Writing (doc) SIG need a chair and more maintainers
 +
** Current Chair (only maintainer in this SIG) Stephen Finucane will not continue it in the next cycle(Yoga)
 +
** http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025161.html
 +
* Open Reviews
 +
** https://review.opendev.org/q/projects:openstack/governance+is:open
  
=== Agenda ===
+
==== Apologies for Absence ====
* Selection of User committee representative
+
<Please write your name if you are not able to attend the meeting>
* Ceilometer [http://lists.openstack.org/pipermail/openstack-tc/2012-October/000016.html application for incubation]
+
*
  
== Presenting a motion before the TC ==
+
=== Past meetings logs ===
  
Motions need to be presented at least 4 business days before the next meeting scheduled time. They should be posted to openstack-tc@lists.openstack.org and CC-ed to openstack-dev@lists.openstack.org. Upon verification, the TC Chair will put the motion on the agenda for the next meeting.
+
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc
 +
 
 +
[[Category: meetings]]

Latest revision as of 15:29, 15 October 2021


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.

We hold office hours at various times during the week on the #openstack-tc IRC channel. We meet formally each week in #openstack-tc


Next Meeting

Agenda Suggestions

Apologies for Absence

<Please write your name if you are not able to attend the meeting>

Past meetings logs

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