|
|
| (85 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, August 17 ==
| + | 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>====
| |
| − | | |
| − | * peterstac to propose changes to add non-voting jobs for mariadb, postgresql, pxc, and cassandra (amrith, 18:09:22)
| |
| − | * pmalik to work with infra to see if we can get different machines for gate (amrith, 18:16:00)
| |
| − | * peterstac to review py35 failure (amrith, 18:16:07)
| |
| − | | |
| − | ==== <big>Trove pulse update</big>====
| |
| − | | |
| − | * [https://docs.google.com/spreadsheets/d/1vJxNaoR3VVNS1Cpiz7U--1zyJRZ6ybMxzJoayrjdduo/edit#gid=1104331956 Pulse Update]<br />
| |
| − | | |
| − | * [https://gist.github.com/anonymous/1513fafa647403c9d8d494d2c42ac57f Top 5 list ]<br />
| |
| − | | |
| − | ==== <big>Newton release schedule</big>====
| |
| − | | |
| − | [http://releases.openstack.org/newton/schedule.html Release Schedule]
| |
| − | | |
| − | I will be marking a test client branch tomorrow, and once next week. The absolute deadline for all client changes is week R-5. After that, no new features, no bug fixes till AFTER Newton is cut. So it is important that ALL changes that must go into python-troveclient make it by Wednesday of week R-5. The release team wants clients tagged by Thursday.
| |
| − | | |
| − | ==== <big>Client reviews that need to be merged</big> ====
| |
| − | | |
| − | [peterstac] The following reviews are awaiting approval and/or review. We need to follow up on these quickly:
| |
| − | * [https://review.openstack.org/331813 331813 Expose Quota.update API]
| |
| − | * [https://review.openstack.org/348546 348546 Add --incremental flag to backup-create]
| |
| − | * [https://review.openstack.org/343927 343927 Add command to delete BUILD instances and clusters]
| |
| − | * [https://review.openstack.org/353230 353230 Display more flavor information in trove flavor-list command]
| |
| − | * [https://review.openstack.org/354507 354507 module-update with --all_datastores doesn't work]
| |
| − | * [https://review.openstack.org/348742 348742 Add support for module ordering on apply]
| |
| − | * [https://review.openstack.org/329160 329160 Implement scheduled backups]
| |
| − | | |
| − | ==== <big>Open Discussion</big>====
| |
| − | | |
| − | Get [https://review.openstack.org/#/c/356631/] merged for api docs.
| |
| − | | |
| − | <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>#agenda https://wiki.openstack.org/wiki/Meetings/TroveMeeting</nowiki></code>
| |
| − | * Use <code><nowiki>#topic</nowiki></code> to mark each topic change.
| |
| − | * Use <code><nowiki>#link</nowiki></code> to mark links.
| |
| − | * 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.
