Difference between revisions of "Meetings/HeatAgenda"
< Meetings
| Line 19: | Line 19: | ||
** start running the integration tests | ** start running the integration tests | ||
** ask at next project meeting | ** ask at next project meeting | ||
| − | + | * What blueprints/major dev are outstanding (targeted for g2) | |
| − | + | * We should start focusing on bug fixing and testing | |
| + | * G2 blocking bugs | ||
* Open discussion | * Open discussion | ||
Revision as of 10:47, 4 December 2012
Weekly Heat (Orchestration) meeting
The heat Orchestration project team holds a meeting in #openstack-meeting:
- Wednesdays at 2000 UTC
Everyone is welcome.
The blueprints that are used as a basis for the heat project can be found at https://blueprints.launchpad.net/heat
Next meeting
- Wed Dec 5 at 2000 UTC
Agenda
- Apologies for absence
- shardy (at EMEA openstack day)
- Review last week's actions
- put heatclient in pypi
- make a bug to update the ubuntu tdls to install a recent version of boto
- start running the integration tests
- ask at next project meeting
- What blueprints/major dev are outstanding (targeted for g2)
- We should start focusing on bug fixing and testing
- G2 blocking bugs
- Open discussion
Previous meetings
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
- Prepare an outline for the meeting to speed things up (see http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html for an actual example)
