Difference between revisions of "Meetings/HeatAgenda"
< Meetings
(→Weekly Heat (Orchestration) meeting) |
(→Agenda (2014-08-06 1200 UTC)) |
||
Line 14: | Line 14: | ||
* Review action items from last meeting | * Review action items from last meeting | ||
* Adding items to the agenda | * Adding items to the agenda | ||
+ | * Keeping up to date on the Heat mid-cycle meet-up | ||
* Critical issues sync | * Critical issues sync | ||
Revision as of 12:11, 6 August 2014
Contents
Weekly Heat (Orchestration) meeting
The heat Orchestration project (see also wiki) team holds a meeting in #openstack-meeting
at alternating times:
Our first 1200 UTC meeting is Wednesday 28th May, 2014.
Everyone is welcome.
The blueprints that are used as a basis for the heat project can be found at https://blueprints.launchpad.net/heat
Agenda (2014-08-06 1200 UTC)
- Review action items from last meeting
- Adding items to the agenda
- Keeping up to date on the Heat mid-cycle meet-up
- Critical issues sync
Agenda (2014-07-30 2000 UTC)
- Review action items from last meeting
- Adding items to the agenda
- Spec approval criteria - (suggest we *can* approve after 3 * +2)
- Heat Gap Coverage plan
- Scaling group member health maintenance
- Using rally for Heat benchmark and quotas patches
- Critical issues sync
Agenda (2014-07-23 1200 UTC)
- Review action items from last meeting
- Adding items to the agenda
- Critical issues sync
Agenda (2014-07-16 2000 UTC)
- Review action items from last meeting
- Adding items to the agenda
- Juno-2 release
- Juno-2 blueprints
- Gap analysis
- Stevedore for resource plugins
- Critical issues sync
Meeting minutes
Meeting organizers
- Publish the agenda 24h in advance
- Mail the agenda to the list and invite participants
- Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
- Use http://meetbot.debian.net/Manual.html to get an automatic summary
- Mail the automatic summary as a reply to the invitation