Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Next Meeting)
 
(86 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 1st, 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
 
  
  
'''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
 
** 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
 
  
 +
* Date: 16 January 2020
 +
* Chair: evrardjp
 +
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
'''Inclusion & Diversity'''
+
==== Agenda Suggestions ====
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
** Status: Discussion in progress on latest revision
 
* 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''
 
  
 +
* Follow up on past action items
 +
** ricolin: (in March 2020): Report on whether guidelines worked.
 +
** ttx: Report on large scale sig -- how does this fly and how are the action items.
 +
** mnaser: report on infra liaison and static hosting
 +
** ttx: report about the vision reflection update, that should be started in January
 +
** jungleboyj: report on the blog post for the analysis of the survey
 +
** ttx (report in Feb 2020): Report on tc/uc merge
 +
** mnaser: report on stable branch policy work.
  
'''Other'''
+
* New initiatives and/or report on previous initiatives
* Allow teams to use their channel for meetings [https://review.openstack.org/485117] (flaper87)
+
** gmann report on the community goals for U and V, py2 drop, and goal select process schedule.
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html
+
*** anyone to help gmann?
** Status: Open discussion
+
** ...
* Support "Driver teams" [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
 
* ''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 ===
+
* addendums
 
 
* Date: tbd
 
* Chair: tbd
 
 
 
 
 
==== Agenda ====
 
 
 
* tbd
 
 
 
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
* tbd
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 15:37, 5 December 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: 16 January 2020
  • Chair: evrardjp
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
    • ricolin: (in March 2020): Report on whether guidelines worked.
    • ttx: Report on large scale sig -- how does this fly and how are the action items.
    • mnaser: report on infra liaison and static hosting
    • ttx: report about the vision reflection update, that should be started in January
    • jungleboyj: report on the blog post for the analysis of the survey
    • ttx (report in Feb 2020): Report on tc/uc merge
    • mnaser: report on stable branch policy work.
  • New initiatives and/or report on previous initiatives
    • gmann report on the community goals for U and V, py2 drop, and goal select process schedule.
      • anyone to help gmann?
    • ...


  • addendums

Apologies for Absence

Past meetings logs

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