|
|
(211 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 20, 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
| |
− | * Trove Mid Cycle Meetup (Feb 9-11)
| |
− | ** https://etherpad.openstack.org/p/mitaka-trove-midcycle-rsvp
| |
− | * Python 3 support in Trove
| |
− | ** Several changes (5 in all) are now showing up for review as part of a project to include Python 3 support for Trove
| |
− | *** https://review.openstack.org/#/q/topic:bp/trove-python3
| |
− | ** I also see this page which indicates that Trove is one of the few projects not ready with Python 3
| |
− | *** https://wiki.openstack.org/wiki/Python3
| |
− | ** What is the intention relative to Python 3 in the Mitaka timeframe?
| |
− | *** There has been no cross-project spec on this, and Python 3 was a stretch goal for Mitaka (per conversations in Tokyo).
| |
− | *** Other projects have support for Python 3 but they aren't "done".
| |
− | ** Do we want it, these changes, and the voting CI in the Mitaka timeframe?
| |
− | ** Will a trove-specs spec be submitted? Is one needed or is this self-explanatory and one is not needed?
| |
− | ** I have asked the question in some of the reviews but got no answer so am asking it here at the trove meeting.
| |
− | * 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.