atom feed9 messages in net.launchpad.lists.openstackRe: [Openstack] User Friendly Develop...
FromSent OnAttachments
Lloyd DewolfJul 26, 2012 2:33 pm 
Thierry CarrezJul 27, 2012 1:49 am 
Lloyd DewolfJul 27, 2012 9:59 am 
Mark CollierJul 27, 2012 10:17 am 
Vishvananda IshayaJul 27, 2012 10:38 am 
Tim BellJul 27, 2012 10:56 am 
Ryan LaneJul 27, 2012 11:17 am 
Stefano MaffulliJul 27, 2012 12:43 pm 
Atul JhaJul 27, 2012 2:19 pm 
Subject:Re: [Openstack] User Friendly Development -was- Fwd: [nova] [cinder] Nova-volume vs. Cinder in Folsom
From:Lloyd Dewolf (lloy@gmail.com)
Date:Jul 27, 2012 9:59:46 am
List:net.launchpad.lists.openstack

On Fri, Jul 27, 2012 at 1:48 AM, Thierry Carrez <thie@openstack.org> wrote:

Lloyd Dewolf wrote:

In my fantasies for the Grizzly release it would start something like:

A. Grizzly Summit

B. From the summit the Tech Committee & PTL have community consensus on the overarching goal for the release and the projects' goals. Articulated online in user friendly manner.

C. Webinar / OpenStack User Groups get a presentation on the release goals, and channels for input and participation.

D. About the half way point in release schedule, development adjusts the online communication to reflect reality, presents an update, and again channels for input and participation.

How do things work today? I haven't found much in the wiki.

Currently we publicly track and adjust release goals through the series blueprints in Launchpad (for example: https://blueprints.launchpad.net/quantum/folsom for Quantum). You can see a combined view for all Folsom at: http://wiki.openstack.org/releasestatus/ . The plan is initially seeded by the PTLs after the design summit, then continuously adjusted to reflect reality (with a status update every week at the Project & Release status meeting).

These public plans can then be used by anyone who wants to present them in webinars or user group meetups, and anyone is free to comment on them and provide input.

Very cool. I'll sync up with the crew right after the Grizzly design summit to see if we can make this accessibly through communication to the user base.

Anyone else interested in collaborating on driving this experiment?

Thank you,