|
|
(187 intermediate revisions by 12 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 16, 2016 ==
| + | Please '''do add your IRC nickname''' when adding a topic so that you could be called upon in the meeting. |
− | | |
− | * Action items from last week's meeting
| |
− | ** [amrith] figure out who has to send FFE acceptances
| |
− | * Trove pulse update
| |
− | ** http://bit.ly/1VQyg00 [http://bit.ly/1VQyg00]
| |
− | * Announcements
| |
− | ** http://releases.openstack.org/mitaka/schedule.html
| |
− | ** [amrith] Cross project Quotas library/project
| |
− | *** see [http://lists.openstack.org/pipermail/openstack-dev/2016-March/089453.html]
| |
− | *** see [https://review.openstack.org/#/c/284454/]
| |
− | ** Other announcements
| |
− | * Health check on outstanding blueprints and features for Mitaka
| |
− | ** https://review.openstack.org/#/q/starredby:amrith+status:open [https://review.openstack.org/#/q/starredby:amrith+status:open]
| |
− | * [amrith] Take a look at [https://review.openstack.org/#/c/292451/]
| |
− | ** Was proposed by Flavio. I'm not sure it addresses the things that we've discussed in the past. But worth taking a look at and posting your thoughts on the things you'd like in the project-wide dashboard.
| |
− | * Summit planning
| |
− | ** Propose sessions at https://etherpad.openstack.org/p/trove-newton-proposed-sessions [https://etherpad.openstack.org/p/trove-newton-proposed-sessions]
| |
− | ** Conference room allocations announced (Trove: 3fb, 6wr, cm:half) [http://markmail.org/message/avbqqzwhog36tme2]
| |
− | * Open Discussion
| |
− | | |
− | <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.