Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

m (changed link to bylaws to go to openstack.org, added to Resources)
(Next Meeting: Prepared next meeting.)
 
(575 intermediate revisions by 28 users not shown)
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 [[http://www.openstack.org/legal/bylaws-of-the-openstack-foundation/|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"
+
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.
|- 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: 5 March 2020
 +
* Chair: evrardjp
 +
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
Next meeting: Tuesday September 30th, 20:00 UTC
+
==== Agenda Suggestions ====
  
==== Agenda ====
+
* Follow up on past action items
  
* Recommendation to Adopt DCO as CLA [https://review.openstack.org/120260]
+
* Ensuring ttx did report on the ML for the large scale sig
* Add a docs environment to the testing interface [https://review.openstack.org/119875]
+
* Report on tc/uc merge (ttx)
* Remove support for specific public cloud implementations from our code [https://review.openstack.org/122968]
+
* Ensuring the analysis of the survey was updated (jungleboyj)
* Other governance changes
+
* Report on telemetry after Rico's convo with the PTL (ricolin)
** Add tripleo-puppet-elements in programs.yaml [https://review.openstack.org/123826]
+
* 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)
** Add python-keystoneclient-federation to the Identity program [https://review.openstack.org/123786]
+
* report on the community goals for U and V, py2 drop (gmann)
** Add two new repos to infra program [https://review.openstack.org/124238]
+
* report on release naming (mugsie)
* Open discussion
+
* report on the ideas repo on the ML when ready (evrardjp)
** Layer #1 and the big tent
+
* volunteers to represent OpenStack at the OpenDev advisory board (evrardjp)
** Shelved discussions while we figure it out:
+
* Report on the OSF board initiatives (evrardjp)
*** Deeper dive into Swift "differences"
+
* Dropping side projects: using golden signals (ttx). ttx will list signals, and later projects matching those.
*** Kilo plan for Zaqar
 
** Need for TC meetings during TC election season (next two weeks) ?
 
*** Gap coverage plans final status
 
  
 
==== Backlog ====
 
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, or are just delayed while we process the earlier requests backlog:
 
 
* jeblair (proxy: mordred)
 
 
 
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]]
 
* [[Governance/TechnicalCommittee/Heat_Gap_Coverage|Heat gap coverage plan]]
 
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
* tbd
 
 
=== Presenting a motion before the TC ===
 
 
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 ===
 
=== Past meetings logs ===
Line 105: Line 37:
 
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:resources]]
+
[[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