Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Next Meeting)
(47 intermediate revisions by 9 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 11th, 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: Majority reached, to be approved on Aug 15th unless new objections are raised
 
  
  
'''New project teams'''
+
=== Next Meeting ===
* 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
+
* Date: 11 Jul 2019
** Next step: Setting up openstack/stackube as an OpenStack-hosted project (dims to mentor them through the steps)
+
* Chair: ttx (and mugsie on gifs)
* Add Gluon project team [https://review.openstack.org/463069]
+
* Agenda to be published on the openstack-discuss mailing list before the meeting
** 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)
+
==== Agenda Suggestions ====
* 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
 
  
 +
* Follow up on past action items
  
'''Inclusion & Diversity'''
+
** Health check changes: asettle to update community (done), fungi to update wiki (done), mugise to update yaml file with liasons and mnaser to update the tooling
* 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''
 
  
 +
** Help-most-needed list: AlanClark and zaneb to update investment opportunities document
  
'''Other'''
+
  [0] https://etherpad.openstack.org/p/2019-upstream-investment-opportunities-refactor
* Amend leaderless program resolution timeframe [https://review.openstack.org/492578] (persia)
+
  [1] https://review.opendev.org/#/c/657447/
** Status: Voting in progress
 
* 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: New patchset posted, discussion in progress
 
* 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''
 
  
 +
** Goal selection: lbragstad to prune the community-goals etherpad
 +
 
 +
  [2] https://etherpad.openstack.org/p/community-goals
  
=== Next Meeting ===
+
** Pop-up teams: ttx to define pop-up teams
 +
 
 +
  [3] https://review.opendev.org/#/c/661356/
 +
  [4] https://review.opendev.org/#/c/661983/5
 +
 
 +
** SIG governance: tc-members to review goal, popup, and SIG project etherpad
 +
 +
    [5] https://etherpad.openstack.org/p/explain-team-formate-differentiate
  
* Date: tbd
+
** Review PTL Guide: asettle ttx ricolin to sync up and review the PTL section of the project teams guide to improve the PTL experience
* Chair: tbd
+
 
 +
  [6] https://review.opendev.org/#/c/665699/
  
 +
* Active initiatives
  
==== Agenda ====
+
** Python 3: mnaser to sync up with swift team on python3 migration and mugsie to sync with dhellmann or release-team to find the code for the proposal bot
  
* tbd
+
** Forum follow-up: ttx to organise Milestone 2 forum meeting with tc-members
  
 +
* Summary meeting minutes from 6 June
 +
 
 +
  [7] http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-06-06-14.00.txt
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
  
* tbd
+
asettle - on vacay
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Revision as of 13:56, 19 June 2019


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: 11 Jul 2019
  • Chair: ttx (and mugsie on gifs)
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
    • Health check changes: asettle to update community (done), fungi to update wiki (done), mugise to update yaml file with liasons and mnaser to update the tooling
    • Help-most-needed list: AlanClark and zaneb to update investment opportunities document
  [0] https://etherpad.openstack.org/p/2019-upstream-investment-opportunities-refactor
  [1] https://review.opendev.org/#/c/657447/
    • Goal selection: lbragstad to prune the community-goals etherpad
  [2] https://etherpad.openstack.org/p/community-goals
    • Pop-up teams: ttx to define pop-up teams
  [3] https://review.opendev.org/#/c/661356/
  [4] https://review.opendev.org/#/c/661983/5
    • SIG governance: tc-members to review goal, popup, and SIG project etherpad
   [5] https://etherpad.openstack.org/p/explain-team-formate-differentiate
    • Review PTL Guide: asettle ttx ricolin to sync up and review the PTL section of the project teams guide to improve the PTL experience
  [6] https://review.opendev.org/#/c/665699/
  • Active initiatives
    • Python 3: mnaser to sync up with swift team on python3 migration and mugsie to sync with dhellmann or release-team to find the code for the proposal bot
    • Forum follow-up: ttx to organise Milestone 2 forum meeting with tc-members
  • Summary meeting minutes from 6 June
 [7] http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-06-06-14.00.txt

Apologies for Absence

asettle - on vacay

Past meetings logs

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