|
|
(304 intermediate revisions by 19 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, March 25, 2015 ==
| + | Please '''do add your IRC nickname''' when adding a topic so that you could be called upon in the meeting. |
− | | |
− | * [SlickNik] Trove pulse update:
| |
− | ** https://etherpad.openstack.org/p/trove-pulse-update
| |
− | * [vgnbkr] Instance Storage for Replication
| |
− | ** https://etherpad.openstack.org/p/trove-replication-storage
| |
− | | |
− | == Trove Meeting, March 18, 2015 ==
| |
− | | |
− | * [SlickNik] Trove pulse update:
| |
− | ** https://etherpad.openstack.org/p/trove-pulse-update
| |
− | * [SlickNik] Openstack Feature Freeze this week for kilo-3:
| |
− | ** https://launchpad.net/trove/+milestone/kilo-3
| |
− | ** https://etherpad.openstack.org/p/TroveKilo3Blueprints
| |
− | * [SlickNik] Switch from oslo namespace packages to "oslo_" style modules
| |
− | ** https://review.openstack.org/#/c/150709/
| |
− | ** For context please see: http://lists.openstack.org/pipermail/openstack-dev/2015-March/059031.html
| |
− | *[peterstac] Come up with a strategy to deal with Mock()ing utility methods
| |
− | ** We have several patchsets that are mocking execute_with_timeout, which can cause unexpected behaviour.
| |
− | ** For context see: https://review.openstack.org/#/c/156486/ and https://review.openstack.org/#/c/138719/
| |
− | *[sushilkm] Different timeouts in configuration based per datastore
| |
− | **https://review.openstack.org/#/c/164640/
| |
− | <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]
| |
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.