Difference between revisions of "Meetings/Swift"
< Meetings
| Line 2: | Line 2: | ||
Meeting Logs: http://eavesdrop.openstack.org/meetings/swift/2015/ | Meeting Logs: http://eavesdrop.openstack.org/meetings/swift/2015/ | ||
| − | '''Agenda: July | + | '''Agenda: July 15, 2015 2100 UTC''' |
* Hackathon reminder (https://www.eventbrite.com/e/swift-hackathon-tickets-17308818141) | * Hackathon reminder (https://www.eventbrite.com/e/swift-hackathon-tickets-17308818141) | ||
Revision as of 23:29, 7 July 2015
Meeting Time: Every Wednesday at 21:00 UTC in #openstack-meeting Meeting Logs: http://eavesdrop.openstack.org/meetings/swift/2015/
Agenda: July 15, 2015 2100 UTC
- Hackathon reminder (https://www.eventbrite.com/e/swift-hackathon-tickets-17308818141)
- Python3 work: https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:master+topic:py3,n,z
- Option 1: Do what we're currently doing. big patches, hard to review, little immediate payoff
- Option 2: Patch one module at a time and blacklist non-ported modules in the gate jobs. smaller pieces of work, measurable progress, still will take a while
- Option 3: Freeze the world, port everything, done. painful up front, but done all at once
- updates from ongoing work
- encryption, EC work, hummingbird?
- notification middleware [cschwede]
- Hot Bugs [notmyname]
- EC bugs
- https://bugs.launchpad.net/swift/+bugs?field.tag=ec (needs triage)
- swiftclient bugs
- https://goo.gl/uO4b7l ("new" bugs that need to be looked at)
- EC bugs
- Specs that are open and should land? [notmyname]
- Container Sync performance. [eranrom]
When adding an item, please include your IRC nickname with it.
