[openstack-dev] [openstack-ansible] Mid Cycle Sprint

Amy Marrich Amy.Marrich at rackspace.com
Thu Dec 10 20:29:52 UTC 2015


I'd be game to join in if it's in San Antonio. While I'd love to go to London I don't think I'd make.

Like Major I'd like to see some doc work.

Amy Marrich
________________________________
From: Jesse Pretorius <jesse.pretorius at gmail.com>
Sent: Wednesday, December 9, 2015 6:45:56 AM
To: openstack-dev at lists.openstack.org; openstack-operators at lists.openstack.org
Subject: [openstack-dev] [openstack-ansible] Mid Cycle Sprint

Hi everyone,

At the Mitaka design summit in Tokyo we had some corridor discussions about doing a mid-cycle meetup for the purpose of continuing some design discussions and doing some specific sprint work.

***
I'd like indications of who would like to attend and what locations/dates/topics/sprints would be of interest to you.
***

For guidance/background I've put some notes together below:

Location
--------
We have contributors, deployers and downstream consumers across the globe so picking a venue is difficult. Rackspace have facilities in the UK (Hayes, West London) and in the US (San Antonio) and are happy for us to make use of them.

Dates
-----
Most of the mid-cycles for upstream OpenStack projects are being held in January. The Operators mid-cycle is on February 15-16.

As I feel that it's important that we're all as involved as possible in these events, I would suggest that we schedule ours after the Operators mid-cycle.

It strikes me that it may be useful to do our mid-cycle immediately after the Ops mid-cycle, and do it in the UK. This may help to optimise travel for many of us.

Format
------
The format of the summit is really for us to choose, but typically they're formatted along the lines of something like this:

Day 1: Big group discussions similar in format to sessions at the design summit.

Day 2: Collaborative code reviews, usually performed on a projector, where the goal is to merge things that day (if a review needs more than a single iteration, we skip it. If a review needs small revisions, we do them on the spot).

Day 3: Small group / pair programming.

Topics
------
Some topics/sprints that come to mind that we could explore/do are:
 - Install Guide Documentation Improvement [1]
 - Development Documentation Improvement (best practises, testing, how to develop a new role, etc)
 - Upgrade Framework [2]
 - Multi-OS Support [3]

[1] https://etherpad.openstack.org/p/oa-install-docs
[2] https://etherpad.openstack.org/p/openstack-ansible-upgrade-framework
[3] https://etherpad.openstack.org/p/openstack-ansible-multi-os-support

--
Jesse Pretorius
IRC: odyssey4me
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151210/7192ff95/attachment.html>


More information about the OpenStack-dev mailing list