|
|
| (100 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 10 ==
| + | 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 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>Reviews that can be merged</big> ===
| |
| − | | |
| − | The following reviews are awaiting approval and I'd like to merge them by end of week if there are no further negative comments.
| |
| − | | |
| − | [https://review.openstack.org/348088 Add "clean" command to redstack]
| |
| − | | |
| − | [https://review.openstack.org/345554 Remove discover from test-requirements]
| |
| − | | |
| − | [https://review.openstack.org/343827 Remove times.dbm file for each tox run]
| |
| − | | |
| − | [https://review.openstack.org/345655 MySQL do not retrieve Password in get user]
| |
| − | | |
| − | [https://review.openstack.org/345651 Define safe pid-file and socket paths in config]
| |
| − | | |
| − | [https://review.openstack.org/286317 Add log retrieval to Cassandra]
| |
| − | | |
| − | [https://review.openstack.org/343920 Use proper queries to update user properties]
| |
| − | | |
| − | [https://review.openstack.org/348087 Fix MySql replication start from incr backup]
| |
| − | | |
| − | === <big>Reviews that will be abandoned</big> ===
| |
| − | | |
| − | I plan to abandon the following reviews and unassign any bugs that are attached to them by end of the week if there are no updates.
| |
| − | | |
| − | [https://review.openstack.org/237184 Fixes the cluster issues]
| |
| − | | |
| − | [https://review.openstack.org/271781 Implement Couchdb Configuration Groups Implements : blueprint couchdb-configu...]
| |
| − | | |
| − | [https://review.openstack.org/199635 Fixes the detection of user with extra access]
| |
| − | | |
| − | [https://review.openstack.org/295274 Separate trove image build project based on libguestfs tools]
| |
| − | | |
| − | [https://review.openstack.org/288297 fix delete backup tenant_id error]
| |
| − | | |
| − | [https://review.openstack.org/208670 Update Management Console user and password]
| |
| − | | |
| − | [https://review.openstack.org/215775 Add support for extended_properties on cluster-create]
| |
| − | | |
| − | [https://review.openstack.org/308126 Create default datastore options]
| |
| − | | |
| − | [https://review.openstack.org/349624 test review stable/Mitaka, DO NOT MERGE]
| |
| − | === <big>Open Discussion</big>===
| |
| − | | |
| − | <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.
