Difference between revisions of "Meetings/TechnicalCommittee"
| Line 6: | Line 6: | ||
=== Next Meeting === | === Next Meeting === | ||
| − | * | + | * April 5th, 20:00 UTC |
* Chair: Thierry Carrez (ttx) | * Chair: Thierry Carrez (ttx) | ||
==== Agenda ==== | ==== Agenda ==== | ||
| + | (Last meeting for the mitaka TC membership) | ||
| − | * | + | * Update Newton new PTL's [https://review.openstack.org/298228] |
| − | * | + | * Mention in project requirements about ptl election [https://review.openstack.org/295609] |
| − | * | + | * Change mission statement by recent change [https://review.openstack.org/292610] |
| − | * | + | * Retire the kite/python-kiteclient projects [https://review.openstack.org/297803] |
| − | + | * Separating cross-project specs and guidelines [http://lists.openstack.org/pipermail/openstack-dev/2016-March/090156.html ML Discussion] & [https://review.openstack.org/#/c/296571/ Review] | |
| − | + | * More tbd | |
| − | * | + | * Cross-project workshops at the Austin summit (sdague) |
| − | + | * Video design summit moderator advice (ttx) | |
| − | |||
| − | |||
| − | ** | ||
* Open discussion | * Open discussion | ||
| Line 30: | Line 28: | ||
* Call out GPL style licenses in testing/validation. [https://review.openstack.org/293140] (pending an update) | * Call out GPL style licenses in testing/validation. [https://review.openstack.org/293140] (pending an update) | ||
| − | * | + | * type:packaging and type:deployment tags (pending iterations on the reviews) |
| − | * | + | ** Introduce type:deployment tag [https://review.openstack.org/295528] |
| − | * | + | ** Introduce a type:packaging tag [https://review.openstack.org/295971] |
| − | * Add type:deployment to release:cycle_with_miestones [https://review.openstack.org/298278] | + | ** Modify asserts for upgrades to include deployment [https://review.openstack.org/295529] |
| + | ** Add type:deployment to release:cycle_with_miestones [https://review.openstack.org/298278] | ||
| + | |||
==== Apologies for Absence ==== | ==== Apologies for Absence ==== | ||
Revision as of 09:09, 30 March 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 5th, 20:00 UTC
- Chair: Thierry Carrez (ttx)
Agenda
(Last meeting for the mitaka TC membership)
- Update Newton new PTL's [1]
- Mention in project requirements about ptl election [2]
- Change mission statement by recent change [3]
- Retire the kite/python-kiteclient projects [4]
- Separating cross-project specs and guidelines ML Discussion & Review
- More tbd
- Cross-project workshops at the Austin summit (sdague)
- Video design summit moderator advice (ttx)
- Open discussion
Backlog
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. [5] (pending an update)
- type:packaging and type:deployment tags (pending iterations on the reviews)
Apologies for Absence
- tbd
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
