Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda Suggestions)
 
(136 intermediate revisions by 18 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
  
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/ . It meets weekly in an open meeting in the <code>#openstack-meeting</code> IRC channel on Freenode. See the [https://governance.openstack.org/tc/#how-to-propose-governance-changes governance website] for details on how to propose governance changes.
+
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/ .
  
=== Current proposals ===
+
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]].'''
''Status last updated: May 26, 2017''
 
  
'''Leadership'''
+
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.
* Technical Committee vision [https://review.openstack.org/453262] (gothicmindfood, johnthetubaguy, cdent, dtroyer)
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115006.html
 
** Status: Feedback was collected on draft review, ML and anonymous survey
 
** Next step: feedback needs to be distilled into actionable points (and split between cosmetic and significant changes).
 
* Introduce assert:supports-api-interoperability tag [https://review.openstack.org/418010] (mtreinish, sdague)
 
** Status: New revision posted May 22, might need another revision
 
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 
** Status: New revision needed
 
** Next step: johnthetubaguy to update it next week-ish
 
* Introduce Top 5 help wanted list [https://review.openstack.org/#/c/466684/] (ttx, dims)
 
** Status: Gathering initial feedback on proposal
 
* Etcd as a base service [https://review.openstack.org/467436] (dims)
 
** Status: Initial discussion on the review
 
 
 
 
 
'''New project teams'''
 
* Add Stackube project team [https://review.openstack.org/462460] (dims, ttx)
 
** Status: Frozen until the project is set up as a hosted project and openly collaborates there for some time
 
** Next step: Setting up openstack/stackube as an OpenStack-hosted project (dims to mentor them through the steps)
 
* Add Gluon project team [https://review.openstack.org/463069] (?)
 
** Status: Frozen while Gluon discusses further integration opportunities with Neutron
 
** Next step: This prospective team needs a TC sponsor/mentor to help them through the steps. Any volunteer ?
 
 
 
 
 
'''Simplification'''
 
* postgresql support in OpenStack -- two alternative solutions:
 
** Declare plainly the current state of Posgresql in OpenStack [https://review.openstack.org/427880] (sdague)
 
** Document lack of postgresql support [https://review.openstack.org/465589] (cdent)
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
 
** Status: No consensus yet, and energy is running low on pushing subsequent refinement patchsets
 
** Next step: Might need a sync discussion in a meeting to lean one way or the other
 
* ''Culling projects that are not going anywhere (ttx, ?)''
 
** ''Status: brainstorming''
 
 
 
 
 
'''Inclusion & Diversity'''
 
* How to propose changes: do not mention meetings [https://review.openstack.org/467255] (ttx)
 
** Status: Small doc catchup change. Voting in progress
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
** Status: New revision needed
 
** Next step: johnthetubaguy to update it
 
* Document voting process for `formal-vote` patches [https://review.openstack.org/463141] (flaper87)
 
** Status: New patchset posted on May 22, voting in progress (needs 66%)
 
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
 
** Status: New revision needed
 
** Next step: flaper87 to update it
 
* Office hours -- two patches:
 
** Introduce office hours [https://review.openstack.org/#/c/467256/] (ttx)
 
** Establish a #openstack-tc water cooler channel [https://review.openstack.org/#/c/467386/] (dims)
 
** Status: initial discussion on the reviews
 
* ''Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)''
 
** ''Status: brainstorming''
 
 
 
 
 
'''Other'''
 
* Support "Driver teams" [https://review.openstack.org/403826] [https://review.openstack.org/403829] [https://review.openstack.org/403836] [https://review.openstack.org/403839] (dhellmann)
 
** Status: Frozen while thingee works on driver discoverability
 
* networking-cisco project team addition [https://review.openstack.org/363709]  (thingee)
 
** Status: Blocked until driver teams are a thing
 
** Next step: thingee to reach out to networking-cisco folks to check how much discoverability solves their issue
 
* ''Policy on binary images publication (dhellmann)''
 
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116677.html''
 
** ''Status: to be proposed''
 
  
  
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* Date: tbd
+
* Date: July 2nd, 2020
* Chair: tbd
+
* Chair: Mohammed Naser
 
+
* Agenda to be published on the OpenStack-discuss mailing list before the meeting
 
 
==== Agenda ====
 
  
* tbd
+
==== Agenda Suggestions ====
  
 +
* Follow up on past action items
 +
* OpenStack Foundation OSU Intern Project (diablo_rojo)
 +
* W cycle goal selection start
 +
* Completion of retirement cleanup (gmann)
 +
** https://etherpad.opendev.org/p/tc-retirement-cleanup
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
* tbd
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 16:00, 26 June 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: July 2nd, 2020
  • Chair: Mohammed Naser
  • Agenda to be published on the OpenStack-discuss mailing list before the meeting

Agenda Suggestions

Apologies for Absence

Past meetings logs

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