|
|
(290 intermediate revisions by 18 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, May 26, 2015 ==
| + | Please '''do add your IRC nickname''' when adding a topic so that you could be called upon in the meeting. |
− | | |
− | * [SlickNik] Trove pulse update:
| |
− | ** https://etherpad.openstack.org/p/trove-pulse-update
| |
− | * [amrith] Do we need all these new hacking rules?
| |
− | ** Changes have been proposed for inclusion of the following hacking rules [copied from commit message without validation]. E128, E265, E713, H238, E111, E122, E123, E128, E251, E265, E713, H105, H306, H404. (four changes, 3 in trove, one in trove-client)
| |
− | ** When some hacking rule changes were proposed the last time (https://review.openstack.org/#/c/104616/ for example) the discussion at the Trove meeting was two-fold. First, that we didn't want to add all of these new hacking rules as they had limited upside. The second was that we'd consider reviewing them as a group before accepting changes. I'd like the group to consider all of these changes before we all spend time reviewing them. I would also like to have the ones for trove consolidated into one change to reduce the merge issues.
| |
− | ** Personally, I find many of these hacking rules to have minimal benefit (if any). But I would rather we discuss them as a group before we all spend cycles reviewing them and then deciding (correctly) not to incorporate them as we have done in the past.
| |
− | | |
− | <br/>
| |
− | [https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History_.282015.29 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.