Meetings/TroveMeeting

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 May 7

• How do Gerrit changes get approved? [mat-lowery]
  • Goal: To clarify the Gerrit change approval process used by Trove core (for the benefit of core and non-core).
    • Core potentially benefits by establishing a process that all core follows (and possibly swap best practices).
      • What if all core used a prioritized queue such as ReviewDay? If you're not using a prioritized queue, how do you prevent starvation?
    • Non-core potentially benefits by making the process transparent and setting expectations.
      • "Hey core, please review <change>" is inefficient and unfair. The priority (such as that calculated by ReviewDay) should be the sole indicator of review/approval priority.
  • Goal: To reduce the time from submittal to approval and prevent Gerrit change starvation.
    • My first-ever Trove submittal is over three months old. Why is that?
    • Establish Gerrit "etiquette."
      • No leaving -1s and then disappearing. A reviewer that leaves a -1 has an obligation to respond to follow up questions.
      • No leaving -1s for nice-to-haves. That's what 0 is for.
      • No leaving -1s for questions about why something was done. Again, use a 0.
      • No leaving -1s for something minor when there are five +1s.
      • Leaving a -1 has the potential to cause the author to "reset the counter" (because he has to submit a new revision) on age-influenced priorities (such as ReviewDay). Think hard before you leave that -1.
  • More details on the mailing list.

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