Jump to: navigation, search

Difference between revisions of "Meetings/TroveMeeting"

(Trove Meeting, Aug 5, 2015)
m (Update meeting agendas for Stein release)
 
(263 intermediate revisions by 16 users not shown)
Line 1: Line 1:
= Weekly Trove Team Meeting =
 
  
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt
+
== Weekly Trove Meeting ==
  
Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:
+
We have weekly team meetings on Wednesdays at 14:00 UTC in #openstack-meeting-alt.
  
==== Guidelines for Writing Clear Agenda Items ====
+
Previous meeting logs can be found here: http://eavesdrop.openstack.org/meetings/trove/
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.
 
  
 +
=== Meeting agendas ===
  
When referring to previous conversations or competing viewpoints, be sure to summarize them.
+
Meeting agendas is now maintained at: https://etherpad.openstack.org/p/trove-stein-meeting-agendas.
  
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.
+
Topics should be added to the agenda at least 24 hours before the meeting, as the team members could have time to prepare on it.
  
== Trove Meeting, Aug 5, 2015 ==
+
Please '''do add your IRC nickname''' when adding a topic so that you could be called upon in the meeting.
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
 
 
* [sushilkm] Datastore registration spec open questions, https://review.openstack.org/188072
 
** We talked a little about this in last week but want to bring this around to close on it.
 
** Question which need to be answered to move on this spec.
 
*** Should the api be simple CRUD operations on each object? (i.e. CRUD on datastores and versions separate) or make the API simplified where we really only care about the version when we update the image on an existing version or create a new version?
 
** Thoughts from SlickNik and cp16net were there on last weeks agenda too, https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Meeting.2C_July_29.2C_2015,
 
 
 
<br/>
 
[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]
 

Latest revision as of 13:44, 26 September 2018

Weekly Trove Meeting

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

Previous meeting logs can be found here: http://eavesdrop.openstack.org/meetings/trove/

Meeting agendas

Meeting agendas is now maintained at: https://etherpad.openstack.org/p/trove-stein-meeting-agendas.

Topics should be added to the agenda at least 24 hours before the meeting, as the team members could have time to prepare on it.

Please do add your IRC nickname when adding a topic so that you could be called upon in the meeting.