Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Next Meeting: Prepared next meeting.)
 
(92 intermediate revisions by 14 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: August 8th, 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.
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 
** Status: Voting in progress, still missing a couple of votes
 
 
 
 
 
'''New project teams'''
 
* Add Stackube project team [https://review.openstack.org/462460]
 
** 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: waiting a few months to see how the integration goes (ttx to mentor them through the steps)
 
* Add Glare project team [https://review.openstack.org/479285]
 
** Status: Discussion in progress, decision likely to be made after Pike releases
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119442.html
 
* Add Blazar project team [https://review.openstack.org/482860]
 
** Status: Discussion in progress, decision likely to be made after Pike releases
 
 
 
 
 
'''Inclusion & Diversity'''
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
** Status: Discussion in progress on latest revision, another patchset likely needed
 
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
 
** Status: Needs a new patchset to incorporate feedback (or abandon since it's been implemented already)
 
** Next step: flaper87 to update this proposal
 
* ''Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)''
 
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html''
 
** ''Status: ML created, "meta" SIG set up, initial discussions being held''
 
** ''Next step: Meta SIG to reach out to existing WG to migrate them over''
 
 
 
 
 
'''Other'''
 
* Allow teams to use their channel for meetings [https://review.openstack.org/485117] (flaper87)
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html
 
** Status: Open discussion, some revisions expected
 
* Support "Driver teams" [https://review.openstack.org/403836] [https://review.openstack.org/403839]
 
** 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
 
* ''How to deal with confusion around "hosted" projects (ttx)''
 
** ''Initial ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118368.html''
 
** ''Subsequent ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/119043.html''
 
** ''Status: Brainstorming''
 
  
  
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* Date: tbd
+
* Date: 5 March 2020
* Chair: tbd
+
* Chair: evrardjp
 +
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
 +
==== Agenda Suggestions ====
  
==== Agenda ====
+
* Follow up on past action items
  
* tbd
+
* 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 ====
 
==== Apologies for Absence ====
 
* tbd
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

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