Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Next Meeting: Prepared next meeting.)
 
(844 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: 5 March 2020
 +
* Chair: evrardjp
 +
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
== Meeting ==
+
==== Agenda Suggestions ====
  
Next meeting: February 5, 2013
+
* Follow up on past action items
  
=== Agenda ===
+
* Ensuring ttx did report on the ML for the large scale sig
 +
* Report on tc/uc merge (ttx)
 +
* Ensuring the analysis of the survey was updated (jungleboyj)
 +
* Report on telemetry after Rico's convo with the PTL (ricolin)
 +
* report on stable branch policy work: mnaser to push an update to distill what happened on the ML in terms of stable branch policy (mnaser)
 +
* report on the community goals for U and V, py2 drop (gmann)
 +
* report on release naming (mugsie)
 +
* report on the ideas repo on the ML when ready (evrardjp)
 +
* volunteers to represent OpenStack at the OpenDev advisory board (evrardjp)
 +
* Report on the OSF board initiatives (evrardjp)
 +
* Dropping side projects: using golden signals (ttx). ttx will list signals, and later projects matching those.
  
* Update on the "Future of Incubation / core" joint committee
 
** Incubation [http://lists.openstack.org/pipermail/openstack-tc/2013-January/000113.html process update]
 
** Schedule for end of cycle graduation review
 
* Schedule for Spring 2013 PTL/TC elections
 
  
== Presenting a motion before the TC ==
+
==== Apologies for Absence ====
  
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.
+
=== 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
+
[[Category: meetings]]

Latest revision as of 15:15, 6 February 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: 5 March 2020
  • Chair: evrardjp
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
  • Ensuring ttx did report on the ML for the large scale sig
  • Report on tc/uc merge (ttx)
  • Ensuring the analysis of the survey was updated (jungleboyj)
  • Report on telemetry after Rico's convo with the PTL (ricolin)
  • report on stable branch policy work: mnaser to push an update to distill what happened on the ML in terms of stable branch policy (mnaser)
  • report on the community goals for U and V, py2 drop (gmann)
  • report on release naming (mugsie)
  • report on the ideas repo on the ML when ready (evrardjp)
  • volunteers to represent OpenStack at the OpenDev advisory board (evrardjp)
  • Report on the OSF board initiatives (evrardjp)
  • Dropping side projects: using golden signals (ttx). ttx will list signals, and later projects matching those.


Apologies for Absence

Past meetings logs

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