|
|
| (366 intermediate revisions by 22 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.
| |
| − |
| |
| − | * 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. |
| | | | |
| − | == Agenda for Oct 22nd ==
| + | 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. |
| − | * [SlickNik] Discuss trove design summit sessions in the etherpad
| |
| − | ** https://etherpad.openstack.org/p/kilo-trove-summit-topics
| |
| − | * [amcrn] Ask folks to review https://wiki.openstack.org/wiki/Bugs#Importance and (re-)categorize bugs accordingly.
| |
| − | * [amrith and AJaeger] AJaeger started working on https://review.openstack.org/#/c/129624/. This same issue was debated in https://review.openstack.org/#/c/104616/ and after some deliberation we eventually didn't take the change. My recollection is that this was discussed at the mid-cycle in Cambridge as part of the conversations that led to https://review.openstack.org/#/c/115778/ and we decided that we wouldn't take H301. Maybe that was a decision for the Juno cycle only; I don't recall. After speaking with AJaeger, I've put this on the agenda for this meeting because I would like to make sure that we're in favor of this change now before he spends much more time on it, and the attendant fixes to H302 and H304 which produce numerous failures.
| |
| − | * [robertmyers and schang] Discuss guestagent refactoring progress.
| |
| − | ** https://review.openstack.org/#/c/119425/ passed and ready for review, but gate seems to be broken.
| |
| − | ** Prepare for other guestagent merges. Discuss status of other in-flight commits.
| |
| | | | |
| − | <br /><br />
| + | Please '''do add your IRC nickname''' when adding a topic so that you could be called upon in the meeting. |
| − | Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove/2014/
| |
| − | <br />
| |
| − | Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History
| |
| − | <br /><br />
| |
| − | <big>Note: BP Meetings now have their own wiki page at: https://wiki.openstack.org/wiki/Meetings/TroveBPMeeting</big>
| |
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.
