Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

 
(162 intermediate revisions by 19 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 17, 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 [http://eavesdrop.openstack.org/#Technical_Committee_Meeting each week] in  #openstack-tc
* 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-compatibility tag [https://review.openstack.org/418010] (mtreinish, sdague)
 
** Status: Dependency was approved. New revision needed.
 
** Next step: sdague to follow up with mtreinish to see if he will push it to the end
 
* Add tag assert:never-breaks-compat [https://review.openstack.org/446561] (mordred)
 
** Status: New revision needed
 
** Next step: ttx to follow up with mordred to see if he will push it to the end
 
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 
** Status: New revision needed
 
** Next step: johnthetubaguy to update it next week-ish
 
* ''Publish official "help wanted" list (ttx, dims)''
 
** ''Status: to be proposed''
 
 
 
 
 
'''New project teams'''
 
* Add Stackube project team [https://review.openstack.org/462460] (dims, ttx)
 
** Status: Under discussion in the review. Needs to be set up as a hosted project before a final decision can be made.
 
* Add Gluon project team [https://review.openstack.org/463069] (?)
 
** Status: Under discussion in the review. Some answers missing. Needs a sponsor to help it through.
 
 
 
 
 
'''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: Discussion / refining exact wording (no consensus yet)
 
* ''Culling projects that are not going anywhere (ttx, ?)''
 
** ''Status: brainstorming''
 
 
 
 
 
'''Inclusion & Diversity'''
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
** Status: New revision needed
 
** Next step: johnthetubaguy to update it
 
* Stop requiring public IRC meetings [https://review.openstack.org/462077] (johnthetubaguy)
 
** Status: Voting in progress. Could use being separated from parent change
 
* Document voting process for `formal-vote` patches [https://review.openstack.org/463141] (flaper87)
 
** Status: Discussion still in progress, probably needs another patchset
 
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
 
** Status: New revision needed
 
** Next step: flaper87 to update it
 
* ''Setting up TC discussion channel and defining office hours (dims, ttx)''
 
** ''Status: to be proposed''
 
* ''Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)''
 
** ''Status: brainstorming''
 
 
 
 
 
'''Queens goals'''
 
* Add Queens goal split out tempest plugins [https://review.openstack.org/369749] (mtreinish)
 
** Status: New patchset posted on May 17. Voting in progress.
 
 
 
 
 
'''Other'''
 
* Fix comment about design summits [https://review.openstack.org/454070] (jhesketh, ttx)
 
** Status: New patchset posted on May 18. Voting in progress
 
* 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: December 03, 2020
* Chair: tbd
+
* Chair: Mohammed Naser
 +
* Agenda to be published on the OpenStack-discuss mailing list before the meeting
  
 +
==== Agenda Suggestions ====
  
==== Agenda ====
+
* Follow up on past action items
 
+
* OpenStack User-facing APIs and CLIs (belmoreira)
* tbd
+
* W cycle goal selection start
 
+
* Retirement for Leaderless projects (gmann)
 +
* Audit and clean-up tags (gmann)
 +
** Remove assert_supports-zero-downtime-upgrade tag
 +
*** https://review.opendev.org/c/openstack/governance/+/761975
 +
** Doc clarification 'supports-api-interoperability' tag
 +
*** https://review.opendev.org/c/openstack/governance/+/760562
 +
* Open Reviews
 +
** Dashboard link: shorturl.at/duyA4
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
* tbd
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 14:10, 4 December 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 each week in #openstack-tc


Next Meeting

  • Date: December 03, 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