Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Next Meeting)
 
(123 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: Jun 12, 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: Needs another patchset
 
** Next step: mtreinish to address dhellmann's comments
 
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 
** Status: New revision needed
 
** Next step: johnthetubaguy to update it next week-ish
 
* Top 5 wanted list (ttx, dims)
 
** Introduce Top 5 help wanted list [https://review.openstack.org/#/c/466684/]
 
** Add "Doc owners" to top-5 wanted list [https://review.openstack.org/469115]
 
** Status: Voting in progress
 
 
 
 
 
'''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 ?
 
* ''Add Blazar project team''
 
** ''Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/117844.html''
 
 
 
 
 
'''Simplification'''
 
* Document postgresql support in OpenStack -- two alternative solutions:
 
** Declare plainly the current state of MySQL in OpenStack [https://review.openstack.org/427880] (sdague, dirkm)
 
** 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: Dirk has integrated the latest feedback. Discussion in progress on that version
 
* ''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 posted, discussion in progress on that version.
 
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
 
** Status: New revision needed
 
** Next step: flaper87 to update it
 
* Office hours -- two patches:
 
* Follow-up precisions on office hours [https://review.openstack.org/470926] (ttx)
 
** Status: Voting in progress
 
* ''Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)''
 
** ''Status: brainstorming''
 
 
 
 
 
'''Goals'''
 
* Discovery alignment (two options):
 
** Add Queens goal to add collection links [https://review.openstack.org/468436]
 
** Add Queens Goal for full discovery alignment [https://review.openstack.org/468437]
 
** Status: Discussion in progress, some questions asked
 
* Policy and docs in code [https://review.openstack.org/469954]
 
** Status: This goal seems to be well accepted. The question is now more if that particular goal should be selected for Queens (rather than others)
 
* ''Migrate off paste''
 
** ''Status: Initial ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-May/117747.html''
 
* ''Continuing Python 3.5+ Support​''
 
** ''Status: Initial ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-May/117746.html''
 
 
 
 
 
'''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
 
* Guidelines for managing releases of binary artifacts [https://review.openstack.org/469265] (dhellmann)
 
** Status: Voting in progress
 
  
  
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* Date: tbd
+
* Date: June 4, 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
 
+
* Report on tc/uc merge (ttx)
* [add agenda items here]
+
* Report on the analysis of the 2019 survey (jungleboyj), and survey 2020.
* Open discussion
+
* 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)
 +
* Moving OpenDev discussion forward (clarkb)
 +
* Report on the OSF board initiatives (mnaser)
 +
* Refstack plans for 2020:06 (prmachan)
 +
* Technical Election Nomination Period Results (diablo_rojo)
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
* tbd
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 17:39, 28 May 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: June 4, 2020
  • Chair: Mohammed Naser
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
  • Report on tc/uc merge (ttx)
  • Report on the analysis of the 2019 survey (jungleboyj), and survey 2020.
  • 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)
  • Moving OpenDev discussion forward (clarkb)
  • Report on the OSF board initiatives (mnaser)
  • Refstack plans for 2020:06 (prmachan)
  • Technical Election Nomination Period Results (diablo_rojo)

Apologies for Absence

Past meetings logs

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