|
|
| (119 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, July 5 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
| |
| − | | |
| − | * Trove pulse update
| |
| − | ** [http://bit.ly/1VQyg00 Pulse update]
| |
| − | ** [https://gist.github.com/amrith/c76d4af85922728d5fdebcdbe77e3559 Top 5 list ]
| |
| − | | |
| − | * Call for topics for mid-cycle
| |
| − | ** Remember that it will be a Virtual Midcycle.
| |
| − | ** Etherpad: https://etherpad.openstack.org/p/newton-trove-midcycle
| |
| − | | |
| − | * Announcements
| |
| − | | |
| − | ** Next week is the N-2 milestone
| |
| − | *** '''All specs for Newton must be approved by the end of the week.'''
| |
| − | | |
| − | ** I will be cutting beta release for Trove on master and mitaka branches (I don't think anything significant went into liberty branch)
| |
| − | | |
| − | * Specs that are up for review
| |
| − | | |
| − | ** The following three specs appear ready to merge. If there are no objections, I will approve these three by midweek next week.
| |
| − | | |
| − | #[https://review.openstack.org/#/c/332885 332885] Quota Update
| |
| − | #[https://review.openstack.org/#/c/329510 329510] Scheduled Backup Specification
| |
| − | #[https://review.openstack.org/#/c/327355 327355] Add configuration group management for DB2
| |
| − | | |
| − | * Proposal for review
| |
| − | | |
| − | * Newton Project Updates
| |
| − | | |
| − | * 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.
