Open Stack

Rob,

Nice effort. I'm not sure of the distinction to be made between page 1 and page 2 but page 1 is quite a bit easier for me to follow.

Page 1 comments:

-        I think there should be only one arrow out of "Designated Sections document" which goes into "Defcore Recommends Core Capabilities." The document will go through the path to get two where the second arrow currently takes it. (Is that too confusing a statement?)

-        It seems that there may be a missing loop for inter release iteration of the definition to propose but "board approves core capabilities" should not be in this loop.

-        On the other hand, what happens if the board does not approve?

Thanks,

Will

From: Rob_Hirschfeld at Dell.com [mailto:Rob_Hirschfeld at Dell.com]
Sent: Thursday, June 26, 2014 11:18 PM
To: Defcore-committee at lists.openstack.org
Subject: [OpenStack-DefCore] Draft Process for Review

DefCore Committee,

I took the task of creating a DefCore process flow as an action item from our Face-to-Face meeting.  I've tried to capture all the steps and documents in as simple a way as possible.

Here's the draft of the process for your comments.  I'm hoping that to circulate it to the TC before our meeting next Tuesday.

Rob
______________________________
Rob Hirschfeld
Sr. Distinguished Cloud Solution Architect
Dell | Cloud Edge, Data Center Solutions
cell +1 512 909-7219 blog robhirschfeld.com, twitter @zehicle
Please note, I am based in the CENTRAL (-6) time zone

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20140627/943b80ad/attachment.html>