Revision as of 15:39, 2 March 2016

Weekly Trove Team Meeting

We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt

Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:

Guidelines for Writing Clear Agenda Items

An agenda item should have a clearly defined objective.

• [owner/author/interested-party] Good: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be a lack of consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.
• Bad: Discuss blueprint ‘xyz’
• Bad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.

When referring to previous conversations or competing viewpoints, be sure to summarize them.

Please make sure to include your own name in the first line of the agenda item, or the name of the person who will be presenting the subject/leading the discussion.

Trove Meeting, March 2, 2016

• [amrith] Trove pulse update
  • http://bit.ly/1VQyg00
• Announcements
  • [amrith] http://lists.openstack.org/pipermail/openstack-dev/2016-February/086362.html
  • Other announcements
• Health check on outstanding blueprints and features for Mitaka
  • [amrith] https://launchpad.net/trove/+milestone/mitaka-3
• Feature Freeze Exceptions
  • [amrith] The process for feature freeze exceptions is that by tomorrow (March 3rd) an email must be sent to the dev mailing list. If you have a BP/Project that will not merge before the m-3 deadline, we need to send out an email about an FFE. What is the list of FFE's that Trove requires for Mitaka? Typically the PTL would send this out so I'll work with Craig to get this sent out in time. I need the list.
• Open Discussion

Meeting Agenda History
Meeting Chat Logs

Running The Meeting

• To start the meeting, use #startmeeting trove
• Then, publish the link to the agenda for the meeting (this page).
• Use #topic to mark each topic change.
• You can find the near-full list of Meetbot commands here. Instructions for voting (which can be useful for a quick show of hands) live here.
• During the meeting, don't forget to liberally use #info, #agreed, #action or #link to make sure the critical discussion points will be highlighted in the meeting log. Attendees can use these Meetbot keywords as well.
• To end the meeting, use #endmeeting