Difference between revisions of "Meetings/TroveMeeting"
< Meetings
(→Trove Meeting, July 5 2016) |
(→Trove Meeting, July 5 2016) |
||
Line 17: | Line 17: | ||
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. | 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, July | + | == Trove Meeting, July 12 2016 == |
* Action items from last week's meeting | * Action items from last week's meeting | ||
+ | |||
+ | ** [amrith] review logstash to see how the redis scenario tests perform | ||
+ | ** [amrith] revisit https://review.openstack.org/#/c/237710/ and figure out some way to get the code merged even if it is disabled but available for debugging? | ||
+ | ** [amrith] review what kind(s) of machines we get in the gate and see if we can get some more beefy horses ... | ||
+ | |||
* Trove pulse update | * Trove pulse update | ||
Line 31: | Line 36: | ||
* Announcements | * Announcements | ||
− | ** | + | ** [http://openstack.markmail.org/thread/jsrgvut4nf5243pt Project mascots] |
+ | *** Please post your ideas in [https://etherpad.openstack.org/p/trove-mascot etherpad] | ||
+ | *** We will have a vote at next meeting, July 19th and send to the foundation on that day | ||
+ | |||
+ | ** This week is the N-2 milestone | ||
*** '''All specs for Newton must be approved by the end of the week.''' | *** '''All specs for Newton must be approved by the end of the week.''' | ||
− | + | *** N-2 milestone for releases have been met | |
− | ** | ||
* Specs that are up for review | * Specs that are up for review | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
* Proposal for review | * Proposal for review | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
* Newton Project Updates | * Newton Project Updates |
Revision as of 18:52, 11 July 2016
Contents
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, July 12 2016
- Action items from last week's meeting
- [amrith] review logstash to see how the redis scenario tests perform
- [amrith] revisit https://review.openstack.org/#/c/237710/ and figure out some way to get the code merged even if it is disabled but available for debugging?
- [amrith] review what kind(s) of machines we get in the gate and see if we can get some more beefy horses ...
- Trove pulse update
- Call for topics for mid-cycle
- Remember that it will be a Virtual Midcycle.
- Etherpad: https://etherpad.openstack.org/p/newton-trove-midcycle
- Announcements
- Project mascots
- Please post your ideas in etherpad
- We will have a vote at next meeting, July 19th and send to the foundation on that day
- Project mascots
- This week is the N-2 milestone
- All specs for Newton must be approved by the end of the week.
- N-2 milestone for releases have been met
- This week is the N-2 milestone
- Specs that are up for review
- Proposal for review
- Newton Project Updates
- Open Discussion
Meeting Agenda History
Meeting Chat Logs
Running The Meeting
- To start the meeting, use
#startmeeting trove
- Then, publish the link to the agenda for the meeting (this page).
- Use
#topic
to mark each topic change. - You can find the near-full list of Meetbot commands here. Instructions for voting (which can be useful for a quick show of hands) live here.
- During the meeting, don't forget to liberally use
#info
,#agreed
,#action
or#link
to make sure the critical discussion points will be highlighted in the meeting log. Attendees can use these Meetbot keywords as well. - To end the meeting, use
#endmeeting