Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

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.
+
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.
  
 +
=== Current proposals ===
 +
''Status last updated: May 17, 2017''
  
−
=== Next Meeting ===
+
'''Leadership'''
 +
* Technical Committee vision [https://review.openstack.org/453262] (gothicmindfood, johnthetubaguy, cdent, dtroyer)
 +
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115006.html
 +
** Status: Feedback was collected on draft review, ML and anonymous survey
 +
** Next step: feedback needs to be distilled into actionable points (and split between cosmetic and significant changes).
 +
* Introduce assert:supports-api-compatibility tag [https://review.openstack.org/418010] (mtreinish, sdague)
 +
** Status: Dependency was approved. New revision needed.
 +
** Next step: sdague to follow up with mtreinish to see if he will push it to the end
 +
* Add tag assert:never-breaks-compat [https://review.openstack.org/446561] (mordred)
 +
** Status: New revision needed
 +
** Next step: ttx to follow up with mordred to see if he will push it to the end
 +
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 +
** Status: New revision needed
 +
** Next step: johnthetubaguy to update it next week-ish
 +
 
 +
 
 +
'''New project teams'''
 +
* Add Stackube project team [https://review.openstack.org/462460] (ttx)
 +
** Status: Under discussion in the review.
 +
* Add Gluon project team [https://review.openstack.org/463069] (?)
 +
** Status: Under discussion in the review. Needs a sponsor to help it through.
 +
 
 +
 
 +
'''Simplification'''
 +
* Deprecate postgresql in OpenStack [https://review.openstack.org/427880] (sdague)
 +
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
 +
** Status: Discussion / voting on the review (no consensus yet)
  
−
* May 16th, 20:00 UTC
 
−
* Chair: Thierry Carrez (ttx)
 
  
 +
'''Inclusion & Diversity'''
 +
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 +
** Status: New revision needed
 +
** Next step: johnthetubaguy to update it
 +
* Stop requiring public IRC meetings [https://review.openstack.org/462077] (johnthetubaguy)
 +
** Status: Voting in progress. Could use being separated from parent change
 +
* Document voting process for `formal-vote` patches [https://review.openstack.org/463141] (flaper87)
 +
** Status: Majority support reached on May 16, about to be approved
 +
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
 +
** Status: New revision needed
 +
** Next step: flaper87 to update it
  
−
==== Agenda ====
 
  
−
* Boston feedback and immediate action items
+
'''Queens goals'''
−
* Post-Forum next steps for...
+
* Add Queens goal split out tempest plugins [https://review.openstack.org/369749] (mtreinish)
−
** Draft technical committee vision for public feedback [https://review.openstack.org/453262] (now that feedback was collected)
+
** Status: Majority support reached on May 16, about to be approved
−
** Introduce assert:supports-api-compatibility [https://review.openstack.org/418010] (now that [https://review.openstack.org/#/c/421846] is approved)
 
−
** deprecate postgresql in OpenStack [https://review.openstack.org/427880] (following forum session)
 
−
** Describe what upstream support means [https://review.openstack.org/440601] (following forum session)
 
−
* Change the target for this goal to uWSGI not Apache mod_wsgi [https://review.openstack.org/460951]
 
−
* Moving away from weekly meetings
 
−
** Stop requiring public IRC meetings [https://review.openstack.org/462077]
 
−
** Remove the proxying section from charter [https://review.openstack.org/463140]
 
−
** Document voting process for `formal-vote` patches [https://review.openstack.org/463141]
 
−
** Drop Technical Committee meetings [https://review.openstack.org/459848]
 
−
* Open discussion
 
  
  
−
==== Backlog ====
+
'''Other'''
−
These items have been proposed, but are not put on the agenda just yet. Could be that they have not been discussed on openstack-dev for the time mandated by our charter yet, or are blocked for some other reason, or are just delayed while we process the earlier requests backlog:
+
* Fix comment about design summits [https://review.openstack.org/454070] (jhesketh, ttx)
 +
** Status: New revision needed
 +
** Next step: ttx to follow up with jhesketh to see if he will push it to the end, and to adopt it if not
 +
* 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
  
−
* Driver teams options & Adding networking-cisco back into the Big Tent [https://review.openstack.org/363709] [https://review.openstack.org/403826] [https://review.openstack.org/403829] [https://review.openstack.org/403836] [https://review.openstack.org/403839] (thingee to get in touch with networking-cisco folks)
 
−
* Add Queens goal split out tempest plugins [https://review.openstack.org/369749] (work in progress)
 
−
* Add tag assert:never-breaks-compat [https://review.openstack.org/446561] (work in progress)
 
−
* Fix comment about design summits [https://review.openstack.org/454070] (waiting for new revision)
 
−
* Add project openstack/stackube. [https://review.openstack.org/462460] (iterating on review)
 
−
* Add Project Gluon to OpenStack Big-Tent [https://review.openstack.org/463069] (iterating on review)
 
−
* TC to have approve authority on maintenance-mode projects [https://review.openstack.org/460963] (waiting for email thread)
 
  
 +
=== Next Meeting ===
  
−
==== Apologies for Absence ====
+
* Date: tbd
 +
* Chair: tbd
  
−
* tbd
 
  
 +
==== Agenda ====
  
−
=== Proposing discussion topics, motions or other governance changes before the TC ===
+
* tbd
  
−
Motions need to be presented before Friday 0800 UTC to be added to the next Tuesday meeting agenda for discussion. They should either be posted as a proposed change to the [http://git.openstack.org/cgit/openstack/governance/ governance] repository (on review.openstack.org) or as a "[tc]" thread to openstack-dev@lists.openstack.org, with a pointer to that thread should be posted to openstack-tc@lists.openstack.org to make sure it gets the required attention from TC members. Upon verification, the TC Chair will put the motion on the agenda for the next meeting.
 
  
−
Before being finally voted on, motions will have to be presented as a [http://git.openstack.org/cgit/openstack/governance/ governance] change. As mandated by our charter, the vote on motions won't be closed until we spent a minimum of 4 business days of public discussions, to give a chance to our wider community to chime in on proposed changes.
+
==== Apologies for Absence ====
  
−
Additions of code repositories to existing project teams, as well as other instances of governance repository housekeeping, do not constitute a "motion". Those will be approved a week after being proposed, if they have the required approvals (PTLs in the case of a repository addition) and no TC member -1 vote. A -1 vote will result in the proposed change to be reviewed at the next TC meeting.
+
* tbd
  
  

Revision as of 09:35, 17 May 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/ . It meets weekly in an open meeting in the #openstack-meeting IRC channel on Freenode. See the governance website for details on how to propose governance changes.

Current proposals

Status last updated: May 17, 2017

Leadership

  • Technical Committee vision [1] (gothicmindfood, johnthetubaguy, cdent, dtroyer)
  • Introduce assert:supports-api-compatibility tag [2] (mtreinish, sdague)
    • Status: Dependency was approved. New revision needed.
    • Next step: sdague to follow up with mtreinish to see if he will push it to the end
  • Add tag assert:never-breaks-compat [3] (mordred)
    • Status: New revision needed
    • Next step: ttx to follow up with mordred to see if he will push it to the end
  • Describe what upstream support means [4] (johnthetubaguy)
    • Status: New revision needed
    • Next step: johnthetubaguy to update it next week-ish


New project teams

  • Add Stackube project team [5] (ttx)
    • Status: Under discussion in the review.
  • Add Gluon project team [6] (?)
    • Status: Under discussion in the review. Needs a sponsor to help it through.


Simplification


Inclusion & Diversity

  • Decisions should be globally inclusive [8] (johnthetubaguy)
    • Status: New revision needed
    • Next step: johnthetubaguy to update it
  • Stop requiring public IRC meetings [9] (johnthetubaguy)
    • Status: Voting in progress. Could use being separated from parent change
  • Document voting process for `formal-vote` patches [10] (flaper87)
    • Status: Majority support reached on May 16, about to be approved
  • Drop Technical Committee meetings [11] (flaper87)
    • Status: New revision needed
    • Next step: flaper87 to update it


Queens goals

  • Add Queens goal split out tempest plugins [12] (mtreinish)
    • Status: Majority support reached on May 16, about to be approved


Other

  • Fix comment about design summits [13] (jhesketh, ttx)
    • Status: New revision needed
    • Next step: ttx to follow up with jhesketh to see if he will push it to the end, and to adopt it if not
  • Support "Driver teams" [14] [15] [16] [17] (dhellmann)
    • Status: Frozen while thingee works on driver discoverability
  • networking-cisco project team addition [18] (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


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

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/TechnicalCommittee&oldid=154110"