Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda Suggestions)
 
(94 intermediate revisions by 16 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: September 5th, 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.
* Add "Reduce Development Complexity" to top-5 [https://review.openstack.org/496404] (cdent)
 
** Status: Open discussion
 
* ''Adding infra to the top 5 help wanted list (fungi)''
 
** ''Next step: fungi to raise discussion / submit a proposal''
 
 
 
 
 
'''New project teams'''
 
* Masakari - Instances High Availability Service [https://review.openstack.org/500118]
 
** Status: Open discussion
 
* Add Stackube project team [https://review.openstack.org/462460]
 
** Status: Project was set up, ready for review again. Dims mentoring.
 
* Add Glare project team [https://review.openstack.org/479285]
 
** Status: Ready for review again. Team will meet with TC at the PTG.
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119442.html
 
* Add Blazar project team [https://review.openstack.org/482860]
 
** Status: Ready for review again. Team will meet with TC at the PTG.
 
* Add Gluon project team [https://review.openstack.org/463069]
 
** Status: Frozen while Gluon discusses further integration opportunities with Neutron
 
** Next step: Meet with the TC at the PTG to discuss recent progress in Neutron integration
 
 
 
 
 
'''Inclusion & Diversity'''
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
** Status: Discussion in progress on latest revision. Is likely to be transformed into guidance in the Project Team Guide
 
* ''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, first workgroups to be migrated''
 
** ''Next step: Migrate volunteer WGs''
 
 
 
 
 
'''Other'''
 
* Be explicit about supported database versions [https://review.openstack.org/493932] (mordred)
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-August/121144.html
 
** Status: Open discussion
 
* 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: 2 April 2020
* Chair: tbd
+
* Chair: ?
 +
* 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)
* tbd
+
* 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 ====
 
==== Apologies for Absence ====
 
* tbd
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 21:30, 1 April 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: 2 April 2020
  • Chair: ?
  • 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