Difference between revisions of "Meetings/TroveMeeting"
< Meetings
(→Trove Meeting, Dec 16, 2015) |
(→Trove Meeting, Dec 16, 2015) |
||
| 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, Jan 6, 2016 == |
* [cp16net] Trove pulse update | * [cp16net] Trove pulse update | ||
** http://bit.ly/1VQyg00 | ** http://bit.ly/1VQyg00 | ||
| − | * | + | * trove-dashboard reporting bugs/bp |
* Announcements | * Announcements | ||
* Open Discussion | * Open Discussion | ||
Revision as of 18:41, 5 January 2016
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, Jan 6, 2016
- [cp16net] Trove pulse update
- trove-dashboard reporting bugs/bp
- Announcements
- Open Discussion
