Difference between revisions of "Meetings/MistralAgenda"
< Meetings
| Line 3: | Line 3: | ||
== Next meetings == | == Next meetings == | ||
| − | October | + | October 28 |
== Agenda == | == Agenda == | ||
| − | * | + | * Review last week's action items |
| − | * Discuss | + | * Discuss some advanced use cases |
| − | * Discuss | + | * Discuss what is left on documentation (use cases, DSL, API) |
| − | + | * Start discussing development plans | |
| − | * | ||
== Checklist for the meeting organizer == | == Checklist for the meeting organizer == | ||
| Line 21: | Line 20: | ||
== Previous meetings == | == Previous meetings == | ||
| + | *2013-10-21 [http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-10-21-16.00.html summary] | [http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-10-21-16.00.log.html log] | ||
Revision as of 05:18, 28 October 2013
We have IRC meetings on #openstack-meeting weekly on Mondays at 16:00 UTC.
Next meetings
October 28
Agenda
- Review last week's action items
- Discuss some advanced use cases
- Discuss what is left on documentation (use cases, DSL, API)
- Start discussing development plans
Checklist for the meeting organizer
- Publish the agenda 24h in advance.
- 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.
- Record decisions and commitments; review in the next meeting.
