Jump to: navigation, search

Difference between revisions of "Meetings/MuranoAgenda"

(Next meetings)
(sjmc7 adding dashboard discussion items)
Line 14: Line 14:
 
i suggest to defer merge of this BP until we make sure that murano-ci is stable enough - at least two weeks without false negatives
 
i suggest to defer merge of this BP until we make sure that murano-ci is stable enough - at least two weeks without false negatives
 
* New BP for juno-3 - migrate to oslo.db
 
* New BP for juno-3 - migrate to oslo.db
 +
* [sjmc7] UI tweaks
 +
** Dashboard rename (we need this at least temporarily for a release this month). Brian has a patch to make it configurable in settings
 +
** Removing/hiding stats panel, at least for non-admins - our product manager thinks it's neat, but not something a user needs to see
 +
** Mark images - can do it via glance CLI so not urgent, but it needs to be more flexible (email thread, no conclusion). Wait for full discussion?
 +
** Moving to Projects panel?
 
* Open discussion
 
* Open discussion
  

Revision as of 16:58, 5 August 2014

We have meetings in #openstack-meeting-alt weekly on Tuesdays at 17:00 UTC.

Next meetings

  • July 29, 2014, 17:00 UTC (chaired by katyafervent)

Agenda

  • Action Items Review

katyafervent Extend the description of https://blueprints.launchpad.net/murano/+spec/murano-api-exception-handling

  • Juno-3 and release schedule
  1. link https://launchpad.net/murano/+milestone/juno-3
  2. link https://wiki.openstack.org/wiki/Juno_Release_Schedule

i suggest to defer merge of this BP until we make sure that murano-ci is stable enough - at least two weeks without false negatives

  • New BP for juno-3 - migrate to oslo.db
  • [sjmc7] UI tweaks
    • Dashboard rename (we need this at least temporarily for a release this month). Brian has a patch to make it configurable in settings
    • Removing/hiding stats panel, at least for non-admins - our product manager thinks it's neat, but not something a user needs to see
    • Mark images - can do it via glance CLI so not urgent, but it needs to be more flexible (email thread, no conclusion). Wait for full discussion?
    • Moving to Projects panel?
  • 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/murano/