Difference between revisions of "Meetings/TroveMeeting"
< Meetings
(→Weekly Trove Team Meeting) |
|||
| Line 1: | Line 1: | ||
= Weekly Trove Team Meeting = | = Weekly Trove Team Meeting = | ||
| − | |||
| − | |||
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt | We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt | ||
| Line 7: | 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 == | ||
An agenda item should have a clearly defined objective. | An agenda item should have a clearly defined objective. | ||
| Line 16: | Line 15: | ||
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 Apr. 30 == | ||
| + | * Open Items | ||
| + | ** Clarification on commit message style guidelines (slicknik): We've been having a lot of -1 reviews on commit message style and I wanted to clarify some of this so that we can reduce review churn caused by this. Goal: Have a clear understanding on when a commit message should be -1'ed. | ||
| + | |||
| + | <br /> | ||
Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove/2014/ | Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove/2014/ | ||
| − | + | <br /> | |
Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History | Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History | ||
| − | + | <br /><br /> | |
| − | + | <big>Note: BP Meetings now have their own wiki page at: https://wiki.openstack.org/wiki/Meetings/TroveBPMeeting</big> | |
| − | |||
| − | |||
| − | |||
Revision as of 21:58, 24 April 2014
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 Apr. 30
- Open Items
- Clarification on commit message style guidelines (slicknik): We've been having a lot of -1 reviews on commit message style and I wanted to clarify some of this so that we can reduce review churn caused by this. Goal: Have a clear understanding on when a commit message should be -1'ed.
Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove/2014/
Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History
Note: BP Meetings now have their own wiki page at: https://wiki.openstack.org/wiki/Meetings/TroveBPMeeting
