Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(13 intermediate revisions by 2 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-dev mailing-list. '''We track current initiatives on the [[Technical_Committee_Tracker]].'''
''Status last updated: July 13, 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. Exceptionally, we may still call for a formal meeting. It generally happens on Tuesdays at 20:00 UTC on #openstack-meeting. The details and agenda will then be posted here.
* 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]
 
** Fix typo in vision document [https://review.openstack.org/482152]
 
** move the vision from reference to resolution [https://review.openstack.org/482686]
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115006.html
 
** Status: The whole patch chain now has majority support, will be merged on July 17 unless new objections are raised.
 
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 
** Status: Discussion in progress on latest revision. New patchset likely needed.
 
* ''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: 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: Initial discussion
 
 
 
 
 
'''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, just missing a few votes
 
 
 
 
 
'''Inclusion & Diversity'''
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
** Status: New revision posted. 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)''
 
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html''
 
** ''Status: ML created, "meta" SIG set up.''
 
** ''Next step: Meta SIG to reach out to existing WG to migrate them over''
 
 
 
 
 
'''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''
 
  
  

Revision as of 09:32, 22 September 2017


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-dev 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. Exceptionally, we may still call for a formal meeting. It generally happens on Tuesdays at 20:00 UTC on #openstack-meeting. The details and agenda will then be posted here.


Next Meeting

  • Date: tbd
  • Chair: tbd


Agenda

  • tbd


Apologies for Absence

  • tbd


Past meetings logs

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