|
|
| Line 15: |
Line 15: |
| | When referring to previous conversations or competing viewpoints, be sure to summarize them. | | When referring to previous conversations or competing viewpoints, be sure to summarize them. |
| | | | |
| − | == Agenda for Apr. 30 == | + | == Agenda for May 7 == |
| − | * Establish policy for disk image builder elements for datastores [mat-lowery]
| |
| − | ** Do we require elements for both Ubuntu and Fedora when a Gerrit change introduces a new datastore or version?
| |
| − | *** Cassandra and Couchbase are examples of datastores that don't currently have Fedora elements. https://review.openstack.org/77461 and https://review.openstack.org/79413 are examples of Gerrit changes that have been -1ed because of lack of Fedora elements.
| |
| − | *** Isn't one working element better than none? If both are required, is that inviting lower quality on the other element the user is required to code but never uses?
| |
| − | *** Are Fedora elements tested in an automated way as the Ubuntu elements are? Reasoning: Yes they were submitted with the Gerrit change, but do they work?
| |
| − | *** Is the policy that Trove requires both Fedora and Ubuntu support for each manager on day one? There is already a lack of parity across datastore managers--not all can do backup and restore (but ultimately I assume they will). Why can't Trove take distro support piecemeal just like it does the datastore operations?
| |
| − | *** [[User:Mat-lowery|mat-lowery]] ([[User talk:Mat-lowery|talk]]) Wed Apr 30 19:17:28 UTC 2014
| |
| − | **** Result: <SlickNik> Let's table this for now.
| |
| − | ** What about Package Install vs. Tarball Install vs. Source Install? Is there a requirement on how the bits are laid down?
| |
| − | *** If packages are required, what are the acceptable sources? (Example: Redis currently uses a PPA.)
| |
| − | *** Does the decision here have repercussions on datastore upgrades?
| |
| − | *** [[User:Mat-lowery|mat-lowery]] ([[User talk:Mat-lowery|talk]]) Wed Apr 30 19:17:28 UTC 2014
| |
| − | **** Result: <SlickNik> So allow [PPAs]. But let's make a best effort to follow this order: distro package, project maintainer PPA, some random PPA.
| |
| − | * Open Items
| |
| − | ** Clarification on commit message style guidelines (slicknik): We've been having a lot of -1 reviews on commit message style and I wanted to clarify some of this so that we can reduce review churn caused by this. Goal: Have a clear understanding on when a commit message should be -1'ed.
| |
| | | | |
| | <br /> | | <br /> |
Revision as of 09:58, 1 May 2014
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.
- 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.
Agenda for May 7
Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove/2014/
Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History
Note: BP Meetings now have their own wiki page at: https://wiki.openstack.org/wiki/Meetings/TroveBPMeeting
