Jump to: navigation, search

Difference between revisions of "Meetings/MistralAgenda"

Line 3: Line 3:
 
== Next meetings ==
 
== Next meetings ==
  
July 11
+
July 18
  
 
== Agenda ==
 
== Agenda ==
Line 9: Line 9:
 
* Review action items
 
* Review action items
 
* Current status (progress, issues, roadblocks, further plans)
 
* Current status (progress, issues, roadblocks, further plans)
* Custom Actions API
+
* Actions API, the repos are prepared, now we need to decide:
** Name of the subproject with Actions API?
+
** Who will take what?
** OK to use mistral-extra to store OpenStack actions? What changes do we need in its structure?
+
** How to provide deprecation mechanism?
 +
** Is it feasible to squeeze into N-3?
 
* Open discussion
 
* Open discussion
  

Revision as of 06:40, 18 July 2016

We have IRC meetings on #openstack-meeting weekly on Mondays at 16:00 UTC.

Next meetings

July 18

Agenda

  • Review action items
  • Current status (progress, issues, roadblocks, further plans)
  • Actions API, the repos are prepared, now we need to decide:
    • Who will take what?
    • How to provide deprecation mechanism?
    • Is it feasible to squeeze into N-3?
  • Open discussion

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.

Previous meetings

http://eavesdrop.openstack.org/meetings/mistral/

Bug review meetings

http://eavesdrop.openstack.org/meetings/mistral_bug_review