|
|
| (105 intermediate revisions by 9 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, July 20 2016 ==
| + | Please '''do add your IRC nickname''' when adding a topic so that you could be called upon in the meeting. |
| − | | |
| − | === <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 ...
| |
| − | * Ongoing, we can adjust flavors in our test scripts<br />
| |
| − | | |
| − | | |
| − | === <big>Trove pulse update</big>===
| |
| − | | |
| − | * [https://docs.google.com/spreadsheets/d/1vJxNaoR3VVNS1Cpiz7U--1zyJRZ6ybMxzJoayrjdduo/edit#gid=1104331956 Pulse Update]<br />
| |
| − | | |
| − | * [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 />
| |
| − | | |
| − | | |
| − | === <big>Announcements</big>===
| |
| − | | |
| − | | |
| − | [http://openstack.markmail.org/thread/jsrgvut4nf5243pt Project mascots]<br />
| |
| − | | |
| − | | |
| − | 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)
| |
| − | # 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>===
| |
| − | | |
| − | | |
| − | === <big>Proposal for review</big>===
| |
| − | | |
| − | | |
| − | === <big>Newton Project Updates</big>===
| |
| − | | |
| − | | |
| − | === <big>Open Discussion</big>===
| |
| − | | |
| − | * We will have to do something about https://review.openstack.org/#/c/316381/
| |
| − | | |
| − | | |
| − | | |
| − | <br/>
| |
| − | [https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory Meeting Agenda History]
| |
| − | <br/>
| |
| − | [http://eavesdrop.openstack.org/meetings/trove/2016 Meeting Chat Logs]
| |
| − | | |
| − | ==Running The Meeting==
| |
| − | * To start the meeting, use <code><nowiki>#startmeeting trove</nowiki></code>
| |
| − | * Then, publish the link to the agenda for the meeting (this page).
| |
| − | * Use <code><nowiki>#topic</nowiki></code> to mark each topic change.
| |
| − | * You can find the near-full list of Meetbot commands [https://wiki.debian.org/MeetBot here]. Instructions for voting (which can be useful for a quick show of hands) live [http://docs.openstack.org/infra/system-config/irc.html#voting here].
| |
| − | * During the meeting, don't forget to liberally use <code><nowiki>#info</nowiki></code>, <code><nowiki>#agreed</nowiki></code>, <code><nowiki>#action</nowiki></code> or <code><nowiki>#link</nowiki></code> 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 <code><nowiki>#endmeeting</nowiki></code>
| |
We have weekly team meetings on Wednesdays at 14:00 UTC in #openstack-meeting-alt.
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.
