Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

m (Added the opendev advisory board volunteer search.)
 
(833 intermediate revisions by 35 users not shown)
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 on the first Thursday of each month in #openstack-tc at 1400 UTC.
  
{| border="1" cellpadding="2" cellspacing="0"
 
|<#eeeeee>| Name                 
 
|<#eeeeee>| Election     
 
|-
 
|  Russell Bryant (russellb)     
 
|  Directly-elected       
 
|-
 
|  Thierry Carrez (ttx)         
 
|  Chair, 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: 6 February 2020
 +
* Chair: ricolin
 +
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
== Meeting ==
+
==== Agenda Suggestions ====
  
Next meeting: February 12, 2013
+
* Follow up on past action items
 +
** Report on large scale sig (ttx)
 +
*** review AP January: post a summary of large scale sig's meeting on the ML this week
 +
*** report to see if momentum is still there
 +
** Report on tc/uc merge (ttx)
 +
*** report on the investigations and discussions with UC
 +
** report on the post for the analysis of the survey (jungleboyj)
 +
*** review AP January on updating the patch
 +
** Report on the convo Telemetry (ricolin)
 +
*** where are we now?
 +
** Report on multi-arch SIG (ricolin)
 +
** report on infra liaison and static hosting (mnaser)
 +
*** check if there is progress / follow up
 +
** report on stable branch policy work (mnaser)
 +
*** review AP january: mnaser to push an update to distill what happened on the ML in terms of stable branch policy
 +
** report on the oslo metrics project (mnaser jroll)
 +
*** has code appeared since last convo, any update from the spec from LINE, any update of the large scale SIG?
 +
** report on the community goals for U and V, py2 drop (gmann)
 +
** report on release naming (mugsie)
 +
*** Victoria Announced (sorry forgot to say it at last meeting)
 +
*** W progress?
 +
** report on the ideas repo (evrardjp)
 +
** charter change (evrardjp)
 +
** ricolin: (in March 2020): Report on whether SIG guidelines worked.
 +
** volunteers to represent OpenStack at the OpenDev advisory board (evrardjp)
  
=== Agenda ===
+
* addendums
  
* Special Motion: [http://lists.openstack.org/pipermail/openstack-dev/2013-February/005421.html incubation process evolution]
+
==== Apologies for Absence ====
* End-of-cycle graduation review
 
*# "Why we think we're ready" statements from Ceilometer and Heat (nijaba, sdake)
 
*# Report on release cycle alignment progress (ttx)
 
*# Technical stability and architecture maturity assessment
 
*# Scope complementarity
 
  
== 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
  
== Past meetings logs ==
+
[[Category: meetings]]
 
 
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc
 

Latest revision as of 19:11, 17 January 2020


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 on the first Thursday of each month in #openstack-tc at 1400 UTC.


Next Meeting

  • Date: 6 February 2020
  • Chair: ricolin
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
    • Report on large scale sig (ttx)
      • review AP January: post a summary of large scale sig's meeting on the ML this week
      • report to see if momentum is still there
    • Report on tc/uc merge (ttx)
      • report on the investigations and discussions with UC
    • report on the post for the analysis of the survey (jungleboyj)
      • review AP January on updating the patch
    • Report on the convo Telemetry (ricolin)
      • where are we now?
    • Report on multi-arch SIG (ricolin)
    • report on infra liaison and static hosting (mnaser)
      • check if there is progress / follow up
    • report on stable branch policy work (mnaser)
      • review AP january: mnaser to push an update to distill what happened on the ML in terms of stable branch policy
    • report on the oslo metrics project (mnaser jroll)
      • has code appeared since last convo, any update from the spec from LINE, any update of the large scale SIG?
    • report on the community goals for U and V, py2 drop (gmann)
    • report on release naming (mugsie)
      • Victoria Announced (sorry forgot to say it at last meeting)
      • W progress?
    • report on the ideas repo (evrardjp)
    • charter change (evrardjp)
    • ricolin: (in March 2020): Report on whether SIG guidelines worked.
    • volunteers to represent OpenStack at the OpenDev advisory board (evrardjp)
  • addendums

Apologies for Absence

Past meetings logs

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