Difference between revisions of "Meetings/TroveMeeting"
< Meetings
(→Reviews that can be merged) |
|||
| Line 17: | Line 17: | ||
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. | 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. | ||
| − | == Trove Meeting, August | + | == Trove Meeting, August 17 == |
==== <big>Action items from last week's meeting</big>==== | ==== <big>Action items from last week's meeting</big>==== | ||
| − | + | ACTION: peterstac to propose changes to add non-voting jobs for mariadb, postgresql, pxc, and cassandra (amrith, 18:09:22) | |
| − | + | ACTION: pmalik to work with infra to see if we can get different machines for gate (amrith, 18:16:00) | |
| − | + | ACTION: peterstac to review py35 failure (amrith, 18:16:07) | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==== <big>Trove pulse update</big>==== | ==== <big>Trove pulse update</big>==== | ||
| Line 35: | Line 30: | ||
* [https://gist.github.com/anonymous/be3d9dbd9a95da9574f4cf66fadd8cd6 Top 5 list ]<br /> | * [https://gist.github.com/anonymous/be3d9dbd9a95da9574f4cf66fadd8cd6 Top 5 list ]<br /> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==== <big>Open Discussion</big>==== | ==== <big>Open Discussion</big>==== | ||
Revision as of 14:36, 12 August 2016
Contents
Weekly Trove Team Meeting
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt
Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:
Guidelines for Writing Clear Agenda Items
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.
When referring to previous conversations or competing viewpoints, be sure to summarize them.
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.
Trove Meeting, August 17
Action items from last week's meeting
ACTION: peterstac to propose changes to add non-voting jobs for mariadb, postgresql, pxc, and cassandra (amrith, 18:09:22) ACTION: pmalik to work with infra to see if we can get different machines for gate (amrith, 18:16:00) ACTION: peterstac to review py35 failure (amrith, 18:16:07)
Trove pulse update
Open Discussion
Meeting Agenda History
Meeting Chat Logs
Running The Meeting
- To start the meeting, use
#startmeeting trove - Then, publish the link to the agenda for the meeting (this page).
- Use
#agenda https://wiki.openstack.org/wiki/Meetings/TroveMeeting - Use
#topicto mark each topic change. - Use
#linkto mark links. - You can find the near-full list of Meetbot commands here. Instructions for voting (which can be useful for a quick show of hands) live here.
- During the meeting, don't forget to liberally use
#info,#agreed,#actionor#linkto 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
#endmeeting
