Difference between revisions of "Meetings/TroveMeeting"
(→Trove Meeting, September 14 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, September | + | == Trove Meeting, September 21 2016 == |
==== <big>Action items from last week's meeting</big>==== | ==== <big>Action items from last week's meeting</big>==== | ||
Line 35: | Line 35: | ||
[http://releases.openstack.org/newton/schedule.html Release Schedule] | [http://releases.openstack.org/newton/schedule.html Release Schedule] | ||
− | Review changes that we would like to merge into | + | Review changes that we would like to merge into RC2. Only changes that have merged in master can be backported to Newton. Please tag all bugs with 'newton-rc-potential'. |
− | + | ==== <big>Open Discussion</big>==== | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | [https://review.openstack.org/#/c/372448/ Before we make pylint voting in master] | |
<br/> | <br/> |
Revision as of 16:29, 19 September 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 21 2016
Action items from last week's meeting
None
Trove pulse update
- If you have a change, or changes that you'd like to see merged for Newton, please do your part and do some reviews as well.
Newton release schedule
Review changes that we would like to merge into RC2. Only changes that have merged in master can be backported to Newton. Please tag all bugs with 'newton-rc-potential'.
Open Discussion
Before we make pylint voting in master
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 apsarshaik
- 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