Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Apologies for Absence)
Line 40: Line 40:
* dhellmann 5 Apr and 12 Apr
* dhellmann 5 Apr and 12 Apr
* johnthetubaguy 12 Apr
=== Proposing discussion topics, motions or other governance changes before the TC ===
=== Proposing discussion topics, motions or other governance changes before the TC ===

Revision as of 09:15, 8 April 2016

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 governance website at http://governance.openstack.org . It meets weekly in an open meeting in the #openstack-meeting IRC channel on Freenode.

Next Meeting

  • April 12th, 20:00 UTC
  • Chair: Thierry Carrez (ttx)


(First meeting for the Newton TC membership)

  • Welcome Newton TC members
    • Update member roster [1], -tc ML rights (in progress) and Gerrit rights (done)
    • Select chair [2] (please propose alternate candidates with similar patches)
    • Confirmation of change approval rules & agenda buildup process
    • Austin reminders: Joint Board/TC meeting (Sunday 2:30pm) and Dinner with the BoD, UC, Gold Member Reps and Foundation Staff (Saturday 7pm)
  • Propose topics for Joint board / TC meeting agenda
  • Tidy of item 5 of the vulnerability:managed tag [3]
  • Cross-project workshops at the Austin summit (sdague)
  • Video design summit moderator advice (ttx)
  • Open discussion
    • What would you like to achieve during the coming 6 months ?


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:

  • Call out GPL style licenses in testing/validation. [4] (pending an update)
  • type:packaging and type:deployment tags (pending iterations on the reviews)
    • Introduce type:deployment tag [5]
    • Introduce a type:packaging tag [6]
    • Modify asserts for upgrades to include deployment [7]
    • Add type:deployment to release:cycle_with_miestones [8]

Apologies for Absence

  • dhellmann 5 Apr and 12 Apr
  • johnthetubaguy 12 Apr

Proposing discussion topics, motions or other governance changes before the TC

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 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 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.

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.

Past meetings logs

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