Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

 
(101 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: July 7, 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 (johnthetubaguy, cdent, dtroyer)
 
** Initial draft for public feedback [https://review.openstack.org/453262]
 
** Subsequent patch 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: Discussion still in progress, mostly on the most appropriate level of details.
 
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 
** Status: Discussion in progress. New patchset likely needed.
 
* Remove remaining 'big tent' references [https://review.openstack.org/480500] (ttx)
 
** Status: Voting in progress
 
* ''Resurrect SWG''
 
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/119068.html''
 
** ''Status: In a meetingless group, someone needs to actively lead the group and post updates''
 
** ''Next step: johnthetubaguy to resurrect the group, set up reporting and grow new members / leaders from there''
 
 
 
 
 
'''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: Initial discussion
 
* ''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, cdent)
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
 
** Status: Voting in progress
 
 
 
 
 
'''Inclusion & Diversity'''
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
** Status: Discussion in progress. Might be better expressed as a principle and a project-team-guide chapter
 
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
 
** Status: New revision needed
 
** Next step: flaper87 to update it
 
* ''Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)''
 
** ''Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html''
 
 
 
 
 
'''Queens Goals'''
 
* Need for project-management by Goal champions to ensure smoother delivery, see thread at [http://lists.openstack.org/pipermail/openstack-dev/2017-June/118808.html]
 
* Goal selection
 
** We'll probably only pick 2, currently leading the pack are:
 
*** Split Tempest plugins (already approved)
 
*** Policy and docs in code [https://review.openstack.org/469954]
 
** Other proposals
 
*** 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]
 
*** Migrate off paste [http://lists.openstack.org/pipermail/openstack-dev/2017-May/117747.html]
 
**** This one is considered a bit vague, lacking a practical success story in one project
 
*** Continuing Python 3.5+ Support​ [http://lists.openstack.org/pipermail/openstack-dev/2017-May/117746.html]
 
**** We should wait for Pike goal completion before "extending" this one
 
* Follow-ups
 
** Clean up boilerplate code in policy docs goal [https://review.openstack.org/475882]
 
 
 
 
 
'''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
 
* ''Allow teams to use their channel for meetings (flaper87)''
 
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html''
 
** ''Status: Brainstorming''
 
* ''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: July 11th (to be confirmed)
+
* Date: 5 March 2020
* Chair: ttx
+
* Chair: evrardjp
 
+
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
==== Agenda ====
+
==== Agenda Suggestions ====
  
* TC 2019 vision next step
+
* Follow up on past action items
* Final selection of Queens goals
+
* Report on tc/uc merge (ttx)
* Open discussion
+
** Options proposed at http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012806.html
 +
* 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 (ttx)
 +
** Draft for guidelines at https://review.opendev.org/#/c/707421/
  
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
+
* ttx (vacation)
* tbd
 
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 10:57, 25 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
  • 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 (ttx)


Apologies for Absence

  • ttx (vacation)

Past meetings logs

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