Revision as of 13:12, 3 August 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, August 10

Meeting on August 3 canceled

Action items from last week's meeting

[amrith] review what kind(s) of machines we get in the gate and see if we can get some more beefy horses ...

Ongoing, we can adjust flavors in our test scripts

Trove pulse update

Pulse Update

Top 5 list

Announcements

N-3 milestone

We met of N-3 milestone is the next milestone.

Specs that are up for review

Proposal for review

Newton Project Updates

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

@@ Line 17: / Line 17: @@
 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, July 20 2016 ==
+== Trove Meeting, August 10 ==
+=== <big>Meeting on August 3 canceled</big> ===
 === <big>Action items from last week's meeting</big>===
-[amrith] review logstash to see how the redis scenario tests perform
-* Sent the results to Petr and Peter<br />
-[amrith] revisit https://review.openstack.org/#/c/237710/ and figure out some way to get the code merged even if it is disabled but available for debugging?<br />
-* It is up and available for review<br />
 [amrith] review what kind(s) of machines we get in the gate and see if we can get some more beefy horses ...
@@ Line 39: / Line 32: @@
 * [https://gist.github.com/amrith/76f199be5d736349a6e807c15c7e24ee Top 5 list ]<br />
-=== <big>Next week: mid-cycle</big>===
-Remember that it will be a Virtual Midcycle.<br />
-Etherpad: https://etherpad.openstack.org/p/newton-trove-midcycle<br />
-I will make an agenda by later this week. I asked Masaki-san and Kengo-san if they would be able to attend and it turns out that next week is not good for them so they'll see the re-runs.<br />
@@ Line 55: / Line 37: @@
-[http://openstack.markmail.org/thread/jsrgvut4nf5243pt Project mascots]<br />
+=== <big>N-3 milestone</big>===
-Based on the ideas in the etherpad, I did a quick doodle poll of the people who are active in the project over the past 180 days. The results are in:
-# Stingray (4)
+We met of N-3 milestone is the next milestone.<br />
-# Clam with a pearl in it (3)
-# Koala Bear (1)
-# Whale (1)
-# Sea Dragon (1)
-# Salmonella (0)
-I will send the 1 and 2 of these to the foundation after the meeting today.<br />
-Links:
-Mascot ideas [https://etherpad.openstack.org/p/trove-mascot etherpad]
-=== <big>N-2 milestone</big>===
-We met of N-2 milestone and specs have been approved. We will have no more specs in Newton. Mariam, I've removed my -2 on [https://review.openstack.org/#/c/329524/ Create Ocata Specs Directory]. Would you please approve.<br />
-I have also cut b2 releases for Trove, Client and Dashboard. No b2 release was made for trove-image-builder and it will likely not have an N release deliverable at this point. I will work on it for Ocata.
 === <big>Specs that are up for review</big>===
@@ Line 84: / Line 46: @@
 === <big>Proposal for review</big>===
-* https://review.openstack.org/#/c/286317/ (already got several +2 but always had to be rebased)
-* https://review.openstack.org/#/c/321838/ (scenario tests only)
-* https://review.openstack.org/#/c/342312/ (scenario tests only)
 === <big>Newton Project Updates</big>===
@@ Line 92: / Line 51: @@
 === <big>Open Discussion</big>===
-* We will have to do something about https://review.openstack.org/#/c/316381/

Difference between revisions of "Meetings/TroveMeeting"