Difference between revisions of "Meetings/TroveMeeting"
< Meetings
(→Other reviews that look to be ready to merge) |
(→Weekly Trove Team Meeting) |
||
| 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 31 2016 == |
==== <big>Action items from last week's meeting</big>==== | ==== <big>Action items from last week's meeting</big>==== | ||
| − | + | * get new non-voting jobs to pass | |
| − | * | + | * ApsarShaik to follow up with mistral on bug/1607788 |
| − | * | ||
| − | |||
| − | |||
==== <big>Trove pulse update</big>==== | ==== <big>Trove pulse update</big>==== | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==== <big>Newton release schedule</big>==== | ==== <big>Newton release schedule</big>==== | ||
| Line 38: | Line 29: | ||
[http://releases.openstack.org/newton/schedule.html Release Schedule] | [http://releases.openstack.org/newton/schedule.html Release Schedule] | ||
| − | ==== <big> | + | ==== <big>Feature reviews that need to be merged</big> ==== |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==== <big>Other reviews that look to be ready to merge</big> ==== | ==== <big>Other reviews that look to be ready to merge</big> ==== | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==== <big>Open Discussion</big>==== | ==== <big>Open Discussion</big>==== | ||
Revision as of 19:42, 24 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 31 2016
Action items from last week's meeting
- get new non-voting jobs to pass
- ApsarShaik to follow up with mistral on bug/1607788
Trove pulse update
Newton release schedule
Feature reviews that need to be merged
Other reviews that look to be ready to merge
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
