Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Meeting)
(Agenda Suggestions)
 
(831 intermediate revisions by 41 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 [[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"
+
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
|- 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 ===
  
=== Exceptional meeting ===
+
* Date: Dec 2nd, 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: Video call on google meet: https://meet.google.com/uzo-tfkt-top
  
Exceptional meeting: Thursday August 14th, 19:00 UTC in #openstack-meeting-3
+
==== Agenda Suggestions ====
  
==== Agenda ====
+
* Roll call
* Our current pain points, and the need (or not) to limit the scope of the integrated release to get them under control
+
* Follow up on past action items
 
+
* Gate health check
(Potential follow-up meeting: Monday August 18th, 19:00 or 20:00 UTC)
+
** Fixing Zuul config error in OpenStack
 
+
*** https://etherpad.opendev.org/p/zuul-config-error-openstack
=== Meeting ===
+
* Updates on community-wide goal
 
+
** Selecting RBAC goal
Next meeting: Tuesday August 19th, 20:00 UTC
+
*** https://review.opendev.org/c/openstack/governance/+/818817
 
+
** Proposed community goal for FIPS compatibility and compliance
==== Agenda ====
+
*** https://review.opendev.org/c/openstack/governance/+/816587
 
+
* Yoga testing runtime: revert the drop of py3.6 ?
* tbd
+
** http://lists.openstack.org/pipermail/openstack-discuss/2021-November/026024.html
* Other governance changes
+
* Adjutant need PTLs and maintainers
** tbd
+
** http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025555.html
* Open discussion
+
* TC position on release cadence?
 
+
** http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684.html
 
+
* Open Reviews
==== Backlog ====
+
** https://review.opendev.org/q/projects:openstack/governance+is:open
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:
 
 
 
* A program for Rally [https://review.openstack.org/108502], final decision (before Sep 16)
 
* Propose Manila for Incubation [https://review.openstack.org/111149], final decision (before Sep 16)
 
* Graduation review: Ironic (before Sep 16)
 
* Graduation review: Marconi/Zaqar (before Sep 16)
 
* Graduation review: Barbican (before Sep 16)
 
* New nominee for User committee (pending name suggestions)
 
 
 
 
 
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 ====
 
+
<Please write your name if you are not able to attend the meeting>
* 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 ===
  
 
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 19:43, 30 November 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