|
|
| (215 intermediate revisions by 14 users not shown) |
| Line 1: |
Line 1: |
| − | = Weekly Trove Team Meeting =
| |
| | | | |
| − | We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt
| + | == Weekly Trove Meeting == |
| | | | |
| − | Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:
| + | We have weekly team meetings on Wednesdays at 14:00 UTC in #openstack-meeting-alt. |
| | | | |
| − | ==== Guidelines for Writing Clear Agenda Items ====
| + | Previous meeting logs can be found here: http://eavesdrop.openstack.org/meetings/trove/ |
| − | 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.
| |
| | | | |
| | + | === Meeting agendas === |
| | | | |
| − | When referring to previous conversations or competing viewpoints, be sure to summarize them.
| + | Meeting agendas is now maintained at: https://etherpad.openstack.org/p/trove-stein-meeting-agendas. |
| | | | |
| − | 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.
| + | Topics should be added to the agenda at least 24 hours before the meeting, as the team members could have time to prepare on it. |
| | | | |
| − | == Trove Meeting, Jan 13, 2016 ==
| + | Please '''do add your IRC nickname''' when adding a topic so that you could be called upon in the meeting. |
| − | * [cp16net] Trove pulse update
| |
| − | ** http://bit.ly/1VQyg00
| |
| − | * [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.
| |
| − | * [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
| |
| − | | |
| − | | |
| − | <br/>
| |
| − | [https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory Meeting Agenda History]
| |
| − | <br/>
| |
| − | [http://eavesdrop.openstack.org/meetings/trove/2015 Meeting Chat Logs]
| |
We have weekly team meetings on Wednesdays at 14:00 UTC in #openstack-meeting-alt.
Topics should be added to the agenda at least 24 hours before the meeting, as the team members could have time to prepare on it.
