Difference between revisions of "Meetings/TroveMeeting"
< Meetings
(→Trove Meeting, Jan 6, 2016) |
|||
| Line 24: | Line 24: | ||
* Open Discussion | * Open Discussion | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<br/> | <br/> | ||
Revision as of 04:57, 13 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 13, 2016
- [cp16net] Trove pulse update
- (link to be posted shortly)
- [peterstac] Use of TODO in the source code
- I've noticed that we have a tendency to use the *TODO* marker in the code to remind ourselves of things that need to be done (usually out of scope of the current changeset). While this is admirable, I believe that entering a bug in launchpad is a better solution. I'd like to see how others feel about this.
- Open Discussion
