Jump to: navigation, search

Difference between revisions of "Meetings/TroveMeeting"

(→‎Trove Meeting, Jan 13, 2016)
(→‎Weekly Trove Team Meeting)
Line 20: Line 20:
 
* [cp16net] Trove pulse update
 
* [cp16net] Trove pulse update
 
** http://bit.ly/1VQyg00
 
** http://bit.ly/1VQyg00
−
* [peterstac] Use of TODO in the source code
+
* Trove Mid Cycle Meetup (Feb 9-11)
−
** 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.
+
** https://etherpad.openstack.org/p/mitaka-trove-midcycle-rsvp
−
* [amrith] Recent "Spam of Patches"
 
−
** See ML: http://openstack.markmail.org/thread/yx6hgouzu5wzrf5m
 
−
** The term "Spam of Patches" is not something I came up with
 
−
** These patches are taking a lot of bandwidth, from reviews, from the gate, and for merges that we really want to land into Mitaka
 
−
** How do we want to handle these from now to Mitaka release date?
 
−
* [amrith] HBase (again)
 
−
** Last week, I posted a message to the ML as promised
 
−
** See http://openstack.markmail.org/thread/yx6hgouzu5wzrf5m
 
−
** Later reposted with [sahara] in subject, http://openstack.markmail.org/thread/x5uirwolkknlorr3
 
−
** As expected, the feedback from several was that we should consider sahara for hbase full distributed mode
 
−
** Which we plan to do, anyway. But that's not for this phase.
 
−
** This phase is only standalone and pseudo-distributed, both of which are single node.
 
 
* Open Discussion
 
* Open Discussion
−
 
  
 
<br/>
 
<br/>

Revision as of 19:09, 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


Meeting Agenda History
Meeting Chat Logs

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/TroveMeeting&oldid=101120"