[Openstack-operators] [openstack-dev] [openstack-ansible] Mid Cycle Sprint
serverascode at gmail.com
Mon Dec 14 16:18:04 UTC 2015
FYI it looks like Ansible Fest London is Feb 18th.
On Thu, Dec 10, 2015 at 1:29 PM, Amy Marrich <Amy.Marrich at rackspace.com> wrote:
> 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:
> 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
> 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
> 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.
> 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
> 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
> Day 3: Small group / pair programming.
> Some topics/sprints that come to mind that we could explore/do are:
> - Install Guide Documentation Improvement 
> - Development Documentation Improvement (best practises, testing, how to
> develop a new role, etc)
> - Upgrade Framework 
> - Multi-OS Support 
>  https://etherpad.openstack.org/p/oa-install-docs
>  https://etherpad.openstack.org/p/openstack-ansible-upgrade-framework
>  https://etherpad.openstack.org/p/openstack-ansible-multi-os-support
> Jesse Pretorius
> IRC: odyssey4me
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-operators