Difference between revisions of "Meetings/TroveMeeting"
< Meetings
Doug Shelley (talk | contribs) |
|||
| Line 5: | Line 5: | ||
Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind: | 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 == | + | ==== Guidelines for Writing Clear Agenda Items ==== |
An agenda item should have a clearly defined objective. | An agenda item should have a clearly defined objective. | ||
| Line 14: | Line 14: | ||
When referring to previous conversations or competing viewpoints, be sure to summarize them. | When referring to previous conversations or competing viewpoints, be sure to summarize them. | ||
| − | |||
| − | |||
| − | == Agenda for | + | == Agenda for February 11 2015 == |
| − | * Review # | + | * Review https://review.openstack.org/#/c/150709/, OSLO Namespace change [amrith] |
| + | ** At mid-cycle I took an action item to follow up on this with #openstack-oslo. Here is the update. This change is not mandatory for Kilo, it will likely be mandatory for "L" release. The change as proposed is low-risk but incomplete. It should include a hacking rule as proposed in Neutron. Do we want to reconsider mid-cycle conversation and merge this change for Kilo? | ||
Revision as of 15:52, 9 February 2015
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.
- 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.
Agenda for February 11 2015
- Review https://review.openstack.org/#/c/150709/, OSLO Namespace change [amrith]
- At mid-cycle I took an action item to follow up on this with #openstack-oslo. Here is the update. This change is not mandatory for Kilo, it will likely be mandatory for "L" release. The change as proposed is low-risk but incomplete. It should include a hacking rule as proposed in Neutron. Do we want to reconsider mid-cycle conversation and merge this change for Kilo?
