Jump to: navigation, search

Difference between revisions of "Meetings/TroveMeeting"

(Agenda for February 11 2015)
m (Agenda for February 11 2015)
Line 15: Line 15:
 
When referring to previous conversations or competing viewpoints, be sure to summarize them.
 
When referring to previous conversations or competing viewpoints, be sure to summarize them.
  
== Agenda for February 11 2015 ==
+
== Agenda for February 18 2015 ==
  
* Review https://review.openstack.org/#/c/150709/, OSLO Namespace change [amrith]
+
* Trove pulse update:
** At mid-cycle I took an action item to follow up on this with #openstack-oslo. Here is the update. This change is not mandatory for Kilo, it will likely be mandatory for "L" release. The change as proposed is low-risk but incomplete. It should include a hacking rule as proposed in Neutron.
+
** https://etherpad.openstack.org/p/trove-pulse-update
** Discussion: Do we want to reconsider mid-cycle conversation and merge this change for Kilo?
+
* Trove related presentations/talks in the Liberty Summit -- Please Vote!
 +
** https://etherpad.openstack.org/p/liberty-summit-trove-talks
 +
* Trove Liberty Mid Cycle Sprint -- Initial planning
 +
** http://doodle.com/candscrt36hg38a7
  
* Review https://review.openstack.org/#/c/154119/ datastore and strategy classification [amrith]
+
<br/>
** This was discussed at mid-cycle and I took the action item to push a blueprint. In normal course, this would get reviewed as part of the spec review and action taken based on that. However there is an urgency to get this process accepted and implemented for the Kilo cycle so I am raising this for consideration at the meeting.
+
[https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History_.282015.29 Meeting Agenda History]
 +
<br/>
 +
[http://eavesdrop.openstack.org/meetings/trove/2015 Meeting Chat Logs]

Revision as of 10:45, 18 February 2015

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.

  • 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.

Agenda for February 18 2015


Meeting Agenda History
Meeting Chat Logs