OpenStack DefCore Committee is looking for community feedback about the proposed DefCore Process.
March has been a month for OpenStack DefCore milestones. At the March Board meeting, we approved the first official DefCore Guideline (called DefCore 2015.03) and we are poised to commit the first DefCore Process draft.
Once this initial commit is approved by the DefCore Committee (expected at DefCore Scale.8 Meeting 3/25 @ 9 PT), we’ll be ready for broader input by the community using the standard OpenStack Gerrit review process. If you are not comfortable with Gerrit, we’ll take your input anyway that you want to give it except via telepathy (we’ve already got a lot on our minds).
Note: We’re also looking for input on the 2015.next Guideline targeted for 2015.04,
The DefCore Process documents the rules (who, what, when and where) that will govern how we create the DefCore Guidelines. By design, it has to be detailed and specific without adding complexity and confusion. The why of DefCore is all that work we did on principles that shape the process.
This process reflects nearly a year of gestation starting from the June 2014 DefCore face-to-face. Once of the notable recent refinements was to organize material into time phases and to be more specific about who is responsible for specific actions.
DRAFT: OpenStack DefCore Process 2015A (reposted from OpenStack/DefCore)
This document describes the DefCore process required by the OpenStack bylaws and approved by the OpenStack Technical Committee and Board.
Expected Time line:
|Time Frame||Milestone||Activities||Lead By|
|-3 months||S-3||“preliminary” draft (from current)||DefCore|
|-2 months||S-2||ID new Capabilities||Community|
|-1 month||S-1||Score capabilities||DefCore|
|Advisory items selected||DefCore|
|+2 months||S+2||Test Flagging||DefCore|
|+3 months||S+3||Approve Guidance||Board|
Note: DefCore may accelerate the process to correct errors and omissions.