openinfra/interop
Code Issues Proposed changes

Based on DefCore midcycle, use Scoring Criteria for Components

Browse Source 
This patch reflects the discussion at the midcycle where DefCore
committee felt that we could apply the existing criteria to
to components as long as we reflect that capabilities apply
more narrowly than components.

Change-Id: I9ac3aba72cf1789c1f88bb9ec38abf7aaa577349
This commit is contained in:
robhirschfeld 2015-07-29 15:21:47 -05:00 committed by Rob Hirschfeld
parent ac0520385f
commit d76ad93a6c
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/process/2015B.rst
View File

@ -112,6 +112,11 @@ A4. DefCore Committee identifies required capabilities
previous Guideline.
6. Capabilities will not be added without being advisory in the previous
Guideline.
7. For level of "widely deployed" adoption criteria, the size of the
pool being considered will match the scope of the community being
considered. Capabilities will be evaluated based on their use in their
component. Components will be evaluated based on their use in the
Platform.
A5. Foundation Staff recommends OpenStack Components and OpenStack Platform
Scope
@ -120,6 +125,9 @@ A5. Foundation Staff recommends OpenStack Components and OpenStack Platform
Component.
2. Foundation Staff recommends which Components are required for
the OpenStack Platform.
3. To support the Foundation recommendation, DefCore will apply the approved
scoring criteria to evaluate if a component should be included in the
platform (see A4).
A6. Additional Capabilities and Tests