Difference between revisions of "Governance/Foundation/24Jan2017BoardMinutes"
Alan Clark (talk | contribs) (Created page with "The official minutes will be posted here once they are approved by the Board of Directors. Until they are approved, we have posted the meeting summary provided by the Executiv...") |
Alan Clark (talk | contribs) |
||
Line 1: | Line 1: | ||
− | + | <div style="text-align:center;">MINUTES OF A TELEPHONIC MEETING OF</div> | |
− | " | + | <div style="text-align:center;">THE BOARD OF DIRECTORS OF</div> |
− | |||
− | + | <div style="text-align:center;">OPENSTACK FOUNDATION</div> | |
− | + | <div style="text-align:center;">January 24, 20171:04 pm PST</div> | |
− | + | The following are the minutes of a telephonic meeting of the Board of Directors (the Board) of OpenStack Foundation, a Delaware corporation (the Foundation) at the above time pursuant to notice duly given to all directors. The following directors were present by phone for all or part of the meeting: | |
− | + | <div style="margin-left:1in;margin-right:0in;">Alan Clark</div> | |
− | + | <div style="margin-left:1in;margin-right:0in;">Allison RandalAnni Lai</div> | |
− | + | <div style="margin-left:1in;margin-right:0in;">Boris Renski</div> | |
− | + | ||
+ | <div style="margin-left:1in;margin-right:0in;">Brad Topol</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Brian Stein </div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">ChangBo Guo</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Chris Price</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Egle Sigler</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Junwei Liu</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Kavit MunshiKenji Kaneshige</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Joseph Wang</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Lew Tucker </div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Mark Baker</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Mark McLoughlin</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Rob Esker</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Russell Bryant</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Shane Wang</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Steven Dake</div> | ||
+ | |||
+ | <div style="margin-left:1in;margin-right:0in;">Tim Bell</div> | ||
+ | |||
+ | |||
+ | Also present for some or all of the meeting was Mark Collier, Jonathan Bryce and Lauren Sell of the OpenStack Foundation, Mark Radcliffe of DLA Piper and certain members of the community. Mr. Clark called the meeting to order and provided an overview of the agenda. He also served as Chairman. Mr. Radcliffe served as Secretary of the meeting and recorded the minutes. | ||
+ | |||
+ | <u>Welcome from the Chairman.</u> | ||
+ | |||
+ | Mr. Clark welcomed the new Board members and thanked the departing Board members for their service. Mr. Clark reminded the Board members that certain Company policies applied to them, including, in particular, the Code of Conduct, Community Code of Conduct and Antitrust Compliance Policy. He urged the Board members to review these policies. </u> | ||
+ | |||
+ | <u>Approval of Board Minutes.</u> | ||
+ | |||
+ | <div style="margin-left:0in;margin-right:0in;">Mr. Clark presented the minutes from the December 6, 2016. After a discussion, upon a motion duly made and seconded the following resolution was unanimously approved by the Board (the following members abstained because they were not present at the meeting: Steven Dake, Brian Stein, Chris Parker and Russell Bryant):</div> | ||
+ | |||
+ | <div style="margin-left:0in;margin-right:0in;">RESOLVED, that minutes of the Board meeting on December 6, 2016 attached as <u>Exhibit A</u> is approved.</div> | ||
+ | |||
+ | |||
+ | <u>2017 Strategy Implementation.</u> | ||
+ | |||
+ | Messrs. Bryce and Collier and Ms. Sells provided a more detailed discussion of the implementation of the Foundation’s 2017 strategy. A Board discussion followed. | ||
+ | |||
+ | <u>Compensation Timeline</u> | ||
+ | |||
+ | Mr. Clark discussed the timeline for discussing compensation issues. | ||
+ | |||
+ | <u>Report of Interop Working Group and Approval of Updated Guidelines.</u> | ||
+ | |||
+ | Ms. Sigler provided a report on the activities of the Interop Working Group. Ms. Sigler discussed the 2017.1 Guidelines attached as <u>Exhibit B</u>. Ms. Sigler discussed the 2017A Process Document attached as <u>Exhibit C</u>. A Board discussion followed. Upon motion duly made and seconded, the Board unanimously adopted the following resolution: | ||
+ | |||
+ | RESOLVED, that the Board approves the revised guidelines designated 2017.01 Guidelines for the OpenStack releases set forth in the 2017.01 Guidelines. | ||
+ | |||
+ | FURTHER RESOLVED, that the Board approves the revised 2017A Process Document. | ||
+ | |||
+ | <u>Strategy Discussion</u> | ||
+ | |||
+ | Ms. Randall provided an update on the discussion of the strategy of the Foundation being considered by the Board. A Board discussion followed. | ||
+ | |||
+ | |||
+ | <div style="margin-left:0in;margin-right:0in;"></div> | ||
+ | |||
+ | <div style="margin-left:0in;margin-right:0in;"></div> | ||
+ | |||
+ | <div style="margin-left:0in;margin-right:0in;"></div> | ||
+ | |||
+ | <div style="margin-left:0in;margin-right:0in;">There being no further business before the Board and upon motion duly made and seconded, the meeting was then adjourned at 3:00 pm PST.</div> | ||
+ | |||
+ | |||
+ | {| style="border-spacing:0;width:6.5in;" | ||
+ | |- style="background-color:#ffffff;border:none;padding-top:0in;padding-bottom:0in;padding-left:0.0799in;padding-right:0.0799in;" | ||
+ | || | ||
+ | || | ||
+ | || Respectfully submitted, | ||
+ | |||
+ | |||
+ | Mark Radcliffe | ||
+ | |||
+ | Secretary of the Meeting | ||
+ | |- style="background-color:#ffffff;border:none;padding-top:0in;padding-bottom:0in;padding-left:0.0799in;padding-right:0.0799in;" | ||
+ | || APPROVED: | ||
+ | |||
+ | |||
+ | Alan Clark | ||
+ | |||
+ | Chairman of the Meeting | ||
+ | |||
+ | |||
+ | |||
+ | || | ||
+ | || | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <div style="text-align:center;"><u>Exhibit A</u></div> | ||
+ | |||
+ | <div style="text-align:center;"><u>[ https://wiki.openstack.org/wiki/Governance/Foundation/6Dec2016BoardMinutes December 6, 2016 Board Minutes]</u></div> | ||
+ | |||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"><u>Exhibit B</u></div> | ||
+ | |||
+ | <div style="text-align:center;"><u>[https://review.openstack.org/#/c/424408/ 2017.01 Guidelines]</u></div> | ||
+ | |||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"></div> | ||
+ | |||
+ | <div style="text-align:center;"><u>Exhibit C</u></div> | ||
+ | |||
+ | <div style="text-align:center;"><u>2017A Process Document</u></div> | ||
+ | |||
+ | |||
+ | OpenStack Interop Working Group Process 2017A | ||
+ | |||
+ | |||
+ | {| style="border-spacing:0;width:1.9063in;" | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | align=center style="color:#333333;" | '''Status:''' | ||
+ | | style="color:#333333;" | Draft | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | align=center style="color:#333333;" | '''Replaces:''' | ||
+ | | style="color:#333333;" | 2016A | ||
+ | |- | ||
+ | |} | ||
+ | <div style="color:#333333;">This document describes the Interop Working Group's working process required by the OpenStack bylaws and approved by the OpenStack Technical Committee and Board.</div> | ||
+ | |||
+ | Expected Time Line: | ||
+ | |||
+ | |||
+ | {| style="border-spacing:0;width:6.5in;" | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | align=center style="color:#333333;" | '''Time Frame''' | ||
+ | | align=center style="color:#333333;" | '''Milestone''' | ||
+ | | align=center style="color:#333333;" | '''Activities''' | ||
+ | | align=center style="color:#333333;" | '''Lead By''' | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | style="color:#333333;" | -3 months | ||
+ | | style="color:#333333;" | S-3 | ||
+ | | style="color:#333333;" | Draft status | ||
+ | | style="color:#333333;" | Interop WG | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | style="color:#333333;" | -2 months | ||
+ | | style="color:#333333;" | S-2 | ||
+ | | style="color:#333333;" | ID new Capabilities | ||
+ | | style="color:#333333;" | Community | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | style="color:#333333;" | -1 month | ||
+ | | style="color:#333333;" | S-1 | ||
+ | | style="color:#333333;" | Score Capabilities | ||
+ | | style="color:#333333;" | Interop WG | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | style="color:#333333;" | Summit | ||
+ | | style="color:#333333;" | S | ||
+ | | style="color:#333333;" | Review status | ||
+ | | style="color:#333333;" | Community | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | style="color:#333333;" | Advisory/Deprecated items selected | ||
+ | | style="color:#333333;" | Interop WG | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | style="color:#333333;" | +1 month | ||
+ | | style="color:#333333;" | S+1 | ||
+ | | style="color:#333333;" | Self-testing | ||
+ | | style="color:#333333;" | Vendors | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | style="color:#333333;" | +2 months | ||
+ | | style="color:#333333;" | S+2 | ||
+ | | style="color:#333333;" | Test Flagging | ||
+ | | style="color:#333333;" | Interop WG | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | style="color:#333333;" | +3 months | ||
+ | | style="color:#333333;" | S+3 | ||
+ | | style="color:#333333;" | Approve Guidance | ||
+ | | style="color:#333333;" | Board | ||
+ | |- | ||
+ | |} | ||
+ | <div style="color:#333333;">Note: The Interop Working Group may accelerate the process to correct errors and omissions.</div> | ||
+ | |||
+ | Process Definition | ||
+ | |||
+ | <div style="color:#333333;">The Guideline process has two primary phases: Draft and Review. During the Draft phase (A), the Interop Working Group is working with community leaders to update and score the components of the Guideline. During the Review phase (B), the general community and vendors have an opportunity to provide input and check the Guidelines (C) against actual implementations. The Review phase ends with Board approval of the draft Guideline (D).</div> | ||
+ | |||
+ | <div style="color:#333333;">This section provides specific rules and structure for each phase.</div> | ||
+ | |||
+ | <div style="color:#333333;">NOTE: To ensure continuity of discussion, process components defined below must _not_ reuse numbers in future revisions. The numbering pattern follows draft, section and sub-item numbering, e.g.: 2015A.B2.2. This requirement may create numbering gaps in future iterations that will help indicate changes.</div> | ||
+ | |||
+ | Guidelines Draft Phase (A) | ||
+ | |||
+ | <div style="color:#333333;">Starting: S-3</div> | ||
+ | |||
+ | <div style="color:#333333;">A1. New Guidelines Start From Previous Guidelines</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">New Guidelines start from the previous Board approved document.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">New Guidelines are given the preliminary name of "next.json".</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">A2. Community Groups Tests into Capabilities</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group coordinates community activities with the Technical Leadership to revise the capabilities based on current technical needs and functionality.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Capabilities must correspond to projects which are part of the "TC-approved release" as designated by the TC (see bylaws of the Foundation, section 4.1(b)(iii)).</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Groupings may change between iterations.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Tests must have unique identifiers that are durable across releases and changes in grouping.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Tests must be under OpenStack Technical Committee governance.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group will provide the test groupings in JSON format for scoring.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group will provide a human-readable summary of the Guideline generated from the JSON version.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">'''''A3. Interop Working Group Collects Recommendations for'''''</div> | ||
+ | |||
+ | <div style="color:#777777;">Designated Sections</div># <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Designated Sections will not be removed without being deprecated in the previous Guideline.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Designated Sections will not be added without being advisory in the previous Guideline.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Designated Sections will not be added or be made advisory unless the corresponding code base is designated as part of the "TC-approved release" by the Technical Committee (see bylaws of the Foundation, section 4.1(b)(iii)).</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Technical leadership may, but is not required to, assist the Interop Working Group with defining advisory Designated Sections for projects that have advisory or required Capabilities.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Designated Sections may be sufficiently defined for Guidelines using general descriptions.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">The Interop Working Group will present A3.4 descriptions to the Board for approval.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Technical leadership may, but is not required to, provide more specific details describing the Designated Sections for a project.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Designated Sections will be included in the JSON Guideline.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">A4. Interop Working Group identifies required capabilities</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group uses Board approved scoring criteria to evaluate Capabilities.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group needs Board approval to change scoring criteria.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Scoring criteria factors or weights cannot change after Draft is published.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group identifies a cut-off score for determining that a Capability is required.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Capabilities will not be removed without being deprecated in the previous Guideline.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Capabilities will not be added without being advisory in the previous Guideline.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">For the "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.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">'''''A5. Foundation Staff recommends OpenStack Components and OpenStack Platform'''''</div> | ||
+ | |||
+ | <div style="color:#777777;">Scope</div># <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Foundation Staff recommends Capabilities to include in each OpenStack Component.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Foundation Staff recommends which Components are required for the OpenStack Powered Platform.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">To support the Foundation recommendation, the Interop Working Group will apply the approved scoring criteria to evaluate if a component should be included in the Platform (see A4).</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">A6. Additional Capabilities and Tests</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group will work with the community to define new Capabilities.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Test grouping for new Capabilities will be included in the Interop Working Group documents.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group will publish a list of missing Capabilities and Capabilities with inadequate test coverage.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">A7. The Interop Working Group creates recommendation for Draft.</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interoper Working Group coordinates activities to create the Guideline draft.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group may choose to ignore recommendations with documented justification.</div> | ||
+ | |||
+ | |||
+ | |||
+ | Guidelines Review Phase (B) | ||
+ | |||
+ | <div style="color:#333333;">Starting: Summit</div> | ||
+ | |||
+ | <div style="color:#333333;">B1. All Reference Artifacts are reviewed via Gerrit</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Draft Guideline</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Designated sections</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Test-Capability groupings</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Flagged Test List</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Capability Scoring criteria and weights</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">May not be in Gerrit: Working materials (spreadsheets, etc)</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">B2. Presentation of Draft Guidelines for Review</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group will present Draft Guidelines to the Board for review.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group will distribute Draft Guidelines to the community for review.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Foundation Staff will provide Draft Guidelines to vendors for review.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">A link to the Gerrit document must be provided with the review materials.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">B3. Changes to Guideline made by Gerrit Review Process</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Community discussion including vendors must go through Gerrit.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">All changes to draft must go through Gerrit process.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group will proxy for users who do not participate in the Gerrit process with attribution.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">'''''B4. For Gerrit reviews, Interop Working Group Co-Chairs act as'''''</div> | ||
+ | |||
+ | <div style="color:#777777;">Joint PTLs</div># <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Interop Working Group Co-Chairs serve as "core" reviewers (+2).</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Requests for changes must be submitted as patches by the requesting party.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Interop Working Group members may proxy change requests as long as the requesting party is explicitly acknowledged.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">One Interop Working Group Co-Chair must be Board member.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">One Interop Working Group Co-Chair will be elected by the Interop Working Group. Election quorum is composed of attendees present during the election meeting.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Additional core reviewers (+2) can be appointed by Co-Chairs.</div> | ||
+ | # <div style="color:#333333;margin-left:0.5in;margin-right:0in;">Election meetings must be posted at least one meeting prior.</div> | ||
+ | |||
+ | |||
+ | |||
+ | Community Review & Vendor Self-Test (C) | ||
+ | |||
+ | <div style="color:#333333;">Starting: S and continues past S+3</div> | ||
+ | |||
+ | <div style="color:#333333;">C1. Vendor Self-Tests</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Vendors are responsible for executing tests identified by the Interop Working Group.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Foundation may, but is not required to, provide tooling for running tests.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Foundation may, but is not required to, define a required reporting format.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Self-test results may be published by Vendors in advance of Foundation review, but must be clearly labeled as "Unofficial Results - Not Yet Accepted By The OpenStack Foundation".</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Vendors who publish self-tests MUST provide them in the same format that would be submitted to the OpenStack Foundation but MAY provide additional formats if they choose to do so.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Self-test results cannot be used as proof of compliance.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">C2. Vendor submits results to Foundation for review</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Foundation determines the acceptable format for submissions.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Foundation has final authority to determine if Vendor meets criteria.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Foundation will provide a review of the results within 30 days.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">C3. Vendor Grievance Process</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Vendors may raise concerns with specific tests to the Interop Working Group.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group may choose to remove tests from a Guideline (known as flagging).</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group will acknowledge vendor requests to flag tests within 30 days.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">C4. Results of Vendor Self-Tests will be open</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Foundation will make the final results of approved vendors available to the community.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Foundation will not publish incomplete or unapproved results.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Only "pass" results will be reported. Skipped and failed results will be omitted from the reports.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Reports will include individual test results, not just Capability scoring.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Vendors are required to submit a description of the system and configuration used to achieve the results.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Foundation may require vendors to submit specific details of the configuration and may also require use of a specific format for reporting.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">C5. API Usage Data Report</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Foundation will provide Interop Working Group with an open report about API usage based on self-tests.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">To the extent the data is available, Capabilities beyond the Interoperability Guideline list will be included in the report.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">C6. Only Two Approved Guidelines at a time:</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Vendors seeking Foundation validation are limited to using the two latest approved Guidelines.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Since past validations are respected, older Guidelines will be maintained as superseded for historical reference.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Guideline status progresses as follows:</div> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | {| style="border-spacing:0;width:6.2604in;" | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | align=center style="color:#777777;" | '''draft:''' | ||
+ | | style="color:#777777;" | initial work, pre-summit (S-3) discussion material | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | align=center style="color:#777777;" | '''review:''' | ||
+ | | style="color:#777777;" | as presented at summit (S) for community review | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | align=center style="color:#777777;" | '''approved:''' | ||
+ | | style="color:#777777;" | board approved, one of the two official guidelines | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | align=center style="color:#777777;" | '''superseded:''' | ||
+ | | style="color:#777777;" | board approved, now superseded by two latest guidelines | ||
+ | |- | ||
+ | |} | ||
+ | Guideline Approval (D) | ||
+ | |||
+ | <div style="color:#333333;">Starting: S+3</div> | ||
+ | |||
+ | <div style="color:#333333;">D1. Board will review and approve Interoperability Guidelines from draft</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Guidelines are set at the Platform, Component and Capability level only.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group will submit the human-readable summary of Capabilities (see section A2[6]) to the Board for approval.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">By voting to approve the summary, the Board delegates responsibility for maintaining test groupings to the Interop Working Group subject to the limitations described in section D2.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Guidelines only apply to the identified releases (a.k.a. release tags).</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">D2. Interop Working Group has authority on test categorization</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group can add flagged tests before and after Guideline approval.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group cannot add additional Tests to Capability mappings after approval.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">The Interop Working Group maintains the test to Capability mappings in the JSON representation.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">D3. Designated Sections only enforced for projects with required Capabilities</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Designated Sections may be defined for any project.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Designated Sections apply to the releases (a.k.a. release tags) identified in the Guideline.</div> | ||
+ | # <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Designated Sections will be included in the JSON Capabilities file to ensure a single source of identification.</div> | ||
+ | |||
+ | |||
+ | |||
+ | <div style="color:#333333;">D4. Guidelines are named based on the date of Board approval</div># <div style="color:#777777;margin-left:0.5in;margin-right:0in;">Naming pattern will be: 4-digit year, dot (period), and 2-digit month.</div> | ||
+ | |||
+ | |||
+ | |||
+ | Functional Information | ||
+ | |||
+ | |||
+ | {| style="border-spacing:0;width:2.5938in;" | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | align=center style="color:#333333;" | '''Format:''' | ||
+ | | style="color:#333333;" | RestructuredText | ||
+ | |- style="border:0.75pt solid #dddddd;padding-top:0.0694in;padding-bottom:0.0694in;padding-left:0.1389in;padding-right:0.1389in;" | ||
+ | | align=center style="color:#333333;" | '''Layout:''' | ||
+ | | style="color:#333333;" | 1.0 | ||
+ | |- | ||
+ | |} |
Latest revision as of 17:17, 20 March 2017
The following are the minutes of a telephonic meeting of the Board of Directors (the Board) of OpenStack Foundation, a Delaware corporation (the Foundation) at the above time pursuant to notice duly given to all directors. The following directors were present by phone for all or part of the meeting:
Also present for some or all of the meeting was Mark Collier, Jonathan Bryce and Lauren Sell of the OpenStack Foundation, Mark Radcliffe of DLA Piper and certain members of the community. Mr. Clark called the meeting to order and provided an overview of the agenda. He also served as Chairman. Mr. Radcliffe served as Secretary of the meeting and recorded the minutes.
Welcome from the Chairman.
Mr. Clark welcomed the new Board members and thanked the departing Board members for their service. Mr. Clark reminded the Board members that certain Company policies applied to them, including, in particular, the Code of Conduct, Community Code of Conduct and Antitrust Compliance Policy. He urged the Board members to review these policies. </u>
Approval of Board Minutes.
2017 Strategy Implementation.
Messrs. Bryce and Collier and Ms. Sells provided a more detailed discussion of the implementation of the Foundation’s 2017 strategy. A Board discussion followed.
Compensation Timeline
Mr. Clark discussed the timeline for discussing compensation issues.
Report of Interop Working Group and Approval of Updated Guidelines.
Ms. Sigler provided a report on the activities of the Interop Working Group. Ms. Sigler discussed the 2017.1 Guidelines attached as Exhibit B. Ms. Sigler discussed the 2017A Process Document attached as Exhibit C. A Board discussion followed. Upon motion duly made and seconded, the Board unanimously adopted the following resolution:
RESOLVED, that the Board approves the revised guidelines designated 2017.01 Guidelines for the OpenStack releases set forth in the 2017.01 Guidelines.
FURTHER RESOLVED, that the Board approves the revised 2017A Process Document.
Strategy Discussion
Ms. Randall provided an update on the discussion of the strategy of the Foundation being considered by the Board. A Board discussion followed.
Respectfully submitted,
Secretary of the Meeting | ||
APPROVED:
Chairman of the Meeting
|
OpenStack Interop Working Group Process 2017A
Status: | Draft |
Replaces: | 2016A |
Expected Time Line:
Time Frame | Milestone | Activities | Lead By |
-3 months | S-3 | Draft status | Interop WG |
-2 months | S-2 | ID new Capabilities | Community |
-1 month | S-1 | Score Capabilities | Interop WG |
Summit | S | Review status | Community |
Advisory/Deprecated items selected | Interop WG | ||
+1 month | S+1 | Self-testing | Vendors |
+2 months | S+2 | Test Flagging | Interop WG |
+3 months | S+3 | Approve Guidance | Board |
Process Definition
Guidelines Draft Phase (A)
- New Guidelines are given the preliminary name of "next.json".
- Capabilities must correspond to projects which are part of the "TC-approved release" as designated by the TC (see bylaws of the Foundation, section 4.1(b)(iii)).
- Groupings may change between iterations.
- Tests must have unique identifiers that are durable across releases and changes in grouping.
- Tests must be under OpenStack Technical Committee governance.
- The Interop Working Group will provide the test groupings in JSON format for scoring.
- The Interop Working Group will provide a human-readable summary of the Guideline generated from the JSON version.
- Designated Sections will not be added without being advisory in the previous Guideline.
- Designated Sections will not be added or be made advisory unless the corresponding code base is designated as part of the "TC-approved release" by the Technical Committee (see bylaws of the Foundation, section 4.1(b)(iii)).
- Technical leadership may, but is not required to, assist the Interop Working Group with defining advisory Designated Sections for projects that have advisory or required Capabilities.
- Designated Sections may be sufficiently defined for Guidelines using general descriptions.
- The Interop Working Group will present A3.4 descriptions to the Board for approval.
- Technical leadership may, but is not required to, provide more specific details describing the Designated Sections for a project.
- Designated Sections will be included in the JSON Guideline.
- The Interop Working Group needs Board approval to change scoring criteria.
- Scoring criteria factors or weights cannot change after Draft is published.
- The Interop Working Group identifies a cut-off score for determining that a Capability is required.
- Capabilities will not be removed without being deprecated in the previous Guideline.
- Capabilities will not be added without being advisory in the previous Guideline.
- For the "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.
- Foundation Staff recommends which Components are required for the OpenStack Powered Platform.
- To support the Foundation recommendation, the Interop Working Group will apply the approved scoring criteria to evaluate if a component should be included in the Platform (see A4).
- Test grouping for new Capabilities will be included in the Interop Working Group documents.
- The Interop Working Group will publish a list of missing Capabilities and Capabilities with inadequate test coverage.
- The Interop Working Group may choose to ignore recommendations with documented justification.
Guidelines Review Phase (B)
- Designated sections
- Test-Capability groupings
- Flagged Test List
- Capability Scoring criteria and weights
- May not be in Gerrit: Working materials (spreadsheets, etc)
- The Interop Working Group will distribute Draft Guidelines to the community for review.
- Foundation Staff will provide Draft Guidelines to vendors for review.
- A link to the Gerrit document must be provided with the review materials.
- All changes to draft must go through Gerrit process.
- The Interop Working Group will proxy for users who do not participate in the Gerrit process with attribution.
- Requests for changes must be submitted as patches by the requesting party.
- Interop Working Group members may proxy change requests as long as the requesting party is explicitly acknowledged.
- One Interop Working Group Co-Chair must be Board member.
- One Interop Working Group Co-Chair will be elected by the Interop Working Group. Election quorum is composed of attendees present during the election meeting.
- Additional core reviewers (+2) can be appointed by Co-Chairs.
- Election meetings must be posted at least one meeting prior.
Community Review & Vendor Self-Test (C)
- The Foundation may, but is not required to, provide tooling for running tests.
- The Foundation may, but is not required to, define a required reporting format.
- Self-test results may be published by Vendors in advance of Foundation review, but must be clearly labeled as "Unofficial Results - Not Yet Accepted By The OpenStack Foundation".
- Vendors who publish self-tests MUST provide them in the same format that would be submitted to the OpenStack Foundation but MAY provide additional formats if they choose to do so.
- Self-test results cannot be used as proof of compliance.
- The Foundation has final authority to determine if Vendor meets criteria.
- The Foundation will provide a review of the results within 30 days.
- The Interop Working Group may choose to remove tests from a Guideline (known as flagging).
- The Interop Working Group will acknowledge vendor requests to flag tests within 30 days.
- The Foundation will not publish incomplete or unapproved results.
- Only "pass" results will be reported. Skipped and failed results will be omitted from the reports.
- Reports will include individual test results, not just Capability scoring.
- Vendors are required to submit a description of the system and configuration used to achieve the results.
- The Foundation may require vendors to submit specific details of the configuration and may also require use of a specific format for reporting.
- To the extent the data is available, Capabilities beyond the Interoperability Guideline list will be included in the report.
- Since past validations are respected, older Guidelines will be maintained as superseded for historical reference.
- Guideline status progresses as follows:
draft: | initial work, pre-summit (S-3) discussion material |
review: | as presented at summit (S) for community review |
approved: | board approved, one of the two official guidelines |
superseded: | board approved, now superseded by two latest guidelines |
Guideline Approval (D)
- The Interop Working Group will submit the human-readable summary of Capabilities (see section A2[6]) to the Board for approval.
- By voting to approve the summary, the Board delegates responsibility for maintaining test groupings to the Interop Working Group subject to the limitations described in section D2.
- Guidelines only apply to the identified releases (a.k.a. release tags).
- The Interop Working Group cannot add additional Tests to Capability mappings after approval.
- The Interop Working Group maintains the test to Capability mappings in the JSON representation.
- Designated Sections apply to the releases (a.k.a. release tags) identified in the Guideline.
- Designated Sections will be included in the JSON Capabilities file to ensure a single source of identification.
Functional Information
Format: | RestructuredText |
Layout: | 1.0 |