Meetings/TroveMeeting

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 16, 2016

• Action items from last week's meeting
  • [amrith] figure out who has to send FFE acceptances
• Trove pulse update
  • http://bit.ly/1VQyg00 [1]
• Announcements
  • http://releases.openstack.org/mitaka/schedule.html
  • [amrith] Cross project Quotas library/project
    • see [2]
    • see [3]
  • [amrith] Take a look at [4]
    • Was proposed by Flavio. I'm not sure it addresses the things that we've discussed in the past. But worth taking a look at and posting your thoughts on the things you'd like in the project-wide dashboard.
  • Other announcements
• Health check on outstanding blueprints and features for Mitaka
  • https://review.openstack.org/#/q/starredby:amrith+status:open [5]
  • [amrith] The change(s) for module management [6] that went into python-troveclient will be in 2.2.0. But 2.2.0 won't be available in Mitaka as the request was after the hard freeze for the client. So we'll have to resubmit the request to tag 2.2.0 [7] against Newton and upper-constraints.txt [8] will only be bumped for Newton. For Newton, let's remember that the client hard freeze is a hard freeze and is not extended by an FFE.
• Summit planning
  • Propose sessions at https://etherpad.openstack.org/p/trove-newton-proposed-sessions [9]
  • Conference room allocations announced (Trove: 3fb, 6wr, cm:half) [10]
• 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