Difference between revisions of "Meetings/TroveMeeting"
< Meetings
(→Running The Meeting) |
(→Trove Meeting, August 31 2016) |
||
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, | + | == Trove Meeting, September 7 2016 == |
==== <big>Action items from last week's meeting</big>==== | ==== <big>Action items from last week's meeting</big>==== | ||
− | + | None | |
− | |||
==== <big>Trove pulse update</big>==== | ==== <big>Trove pulse update</big>==== | ||
Line 27: | Line 26: | ||
[https://docs.google.com/spreadsheets/d/1vJxNaoR3VVNS1Cpiz7U--1zyJRZ6ybMxzJoayrjdduo/edit?usp=sharing Pulse update] | [https://docs.google.com/spreadsheets/d/1vJxNaoR3VVNS1Cpiz7U--1zyJRZ6ybMxzJoayrjdduo/edit?usp=sharing Pulse update] | ||
− | [ | + | [Top 5 list] |
==== <big>Newton release schedule</big>==== | ==== <big>Newton release schedule</big>==== |
Revision as of 18:51, 31 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, September 7 2016
Action items from last week's meeting
None
Trove pulse update
[Top 5 list]
Newton release schedule
Open Discussion
Meeting Agenda History
Meeting Chat Logs
Running The Meeting
- To start the meeting, use
#startmeeting trove
- Send a courtesy ping to attendees peterstac johnma dougshelley66 pmalik vgnbkr mvandijk trevormc aliadil spilla songjian trevormc
- Use
#agenda https://wiki.openstack.org/wiki/Meetings/TroveMeeting
- Use
#topic
to mark each topic change. - Use
#link
to 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
,#action
or#link
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
#endmeeting