Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Jun 20 status update)
(Apologies for Absence)
 
(96 intermediate revisions by 15 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 20, 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 (gothicmindfood, johnthetubaguy, cdent, dtroyer)
 
** Initial draft for public feedback [https://review.openstack.org/453262]
 
** New version integrating feedback and editing for style [https://review.openstack.org/473620]
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115006.html
 
** Status: New draft produced integrating some of the feedback. Discussion in progress on that version
 
* Introduce assert:supports-api-interoperability tag [https://review.openstack.org/418010] (mtreinish, cdent)
 
** Status: Voting in progress
 
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 
** Status: New revision needed
 
** Next step: johnthetubaguy to update it
 
* Top 5 wanted list (ttx, dims)
 
** Introduce Top 5 help wanted list [https://review.openstack.org/#/c/466684/]
 
*** Status: Majority reached on Jun 19, to be approved Jun 22
 
** Add "Doc owners" to top-5 wanted list [https://review.openstack.org/469115]
 
*** Status: Majority reached on Jun 20, to be approved Jun 23
 
** Add "Glance Contributors " to top-5 wanted list [https://review.openstack.org/474604]
 
*** 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'''
 
* Declare plainly the current state of PostgreSQL in OpenStack [https://review.openstack.org/427880] (sdague, dirkm)
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
 
** Status: Still under discussion. Could use a minor formatting revision
 
* ''Culling Fuel (ttx)''
 
** ''Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/118367.html''
 
 
 
 
 
'''Inclusion & Diversity'''
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
** Status: Open discussion
 
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
 
** Status: New revision needed
 
** Next step: flaper87 to update it
 
* ''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: Open discussion
 
* 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, still missing a couple votes
 
* Remove "meritocracy" from the opens [https://review.openstack.org/473510]
 
** Status: Voting in progress
 
  
  
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* Date: June 20, 20:00 on #openstack-meeting
+
* Date: 10 October 2019
* Chair: ttx (or thingee if ttx is late)
+
* Chair: asettle
 +
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
 +
==== Agenda Suggestions ====
  
==== Agenda ====
+
* Follow up on past action items
 
+
** ricolin: Follow up with SIG chairs about guidelines https://etherpad.openstack.org/p/SIGs-guideline
* Review proposed Pike goals and come up with a proposed selection
+
** ttx: contact interested parties in a new 'large scale' sig (help with mnaser, jroll reaching out to verizon media)
* Open discussion
+
** Release Naming - Results of the TC poll - Next action
  
 +
* New initiatives and/or report on previous initiatives
 +
** Help gmann on the community goals following our new goal process.
 +
*** It includes 1. Ussuri goal proposals update 2. Plan for V cycle goal discussion 3. One more TC member to Volunteer
 +
** mugsie: to sync with dhellmann or release-team to find the code for the proposal bot
 +
** jroll - ttx: Feedback from the forum selection committee -- Follow up on https://etherpad.openstack.org/p/PVG-TC-brainstorming -- Final accepted list?
 +
** mnaser: sync up with swift team on python3 migration
 +
* addendums
 +
** define goal select process schedule
 +
*** This is different discussion to select goals. We need to make sure we can have a schedule for cycles to follow. So we know when exactly to ask for goal idea, ask for champion, start +1 cycle goal select process, and start +2 cycle select process.
 +
** Maintain issue with Telemetery
 +
** overall review for TC summit and PTG plans
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
  
* smcginnis, dims are traveling and might have a hard time joining
+
evrardjp - Travelling
* ttx might be late joining
 
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 12:35, 28 October 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: 10 October 2019
  • Chair: asettle
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
    • ricolin: Follow up with SIG chairs about guidelines https://etherpad.openstack.org/p/SIGs-guideline
    • ttx: contact interested parties in a new 'large scale' sig (help with mnaser, jroll reaching out to verizon media)
    • Release Naming - Results of the TC poll - Next action
  • New initiatives and/or report on previous initiatives
    • Help gmann on the community goals following our new goal process.
      • It includes 1. Ussuri goal proposals update 2. Plan for V cycle goal discussion 3. One more TC member to Volunteer
    • mugsie: to sync with dhellmann or release-team to find the code for the proposal bot
    • jroll - ttx: Feedback from the forum selection committee -- Follow up on https://etherpad.openstack.org/p/PVG-TC-brainstorming -- Final accepted list?
    • mnaser: sync up with swift team on python3 migration
  • addendums
    • define goal select process schedule
      • This is different discussion to select goals. We need to make sure we can have a schedule for cycles to follow. So we know when exactly to ask for goal idea, ask for champion, start +1 cycle goal select process, and start +2 cycle select process.
    • Maintain issue with Telemetery
    • overall review for TC summit and PTG plans

Apologies for Absence

evrardjp - Travelling

Past meetings logs

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