March 2015 - Foundation-board - lists.openinfra.dev

DefCore Report for 4/2 Board Meeting
by Rob Hirschfeld 01 Apr '15

01 Apr '15

* DefCore Board Report Meeting April 2, 2015 Rob Hirschfeld & Egle Sigler Co-Chairs 10 minute Limit * Short Status Update * No DefCore 2015.04 Guideline o Keystone expected for 2015.05 Guideline * DefCore 2015.03 has requests for Flagged Tests * Request for Feedback on 2015A Process Draft o starting community outreach process (need help) o interlock with TC 2015A DRAFT PROCESS Source: http://git.openstack.org/cgit/openstack/defcore/tree/process/2015A.rst We will take suggestions any way you want to give them; however, the prefered mechanism is to submit patches against Gerrit. Reposted for review: OpenStack DefCore Process 2015A Status: Draft Replaces: none 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 Summit S "solid" draft Community Advisory items selected DefCore +1 month S+1 self-testing Vendors +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. Process Definition The DefCore Guideline process has two primary phases: Draft and Review. During the Draft phase (A), the DefCore Committee is working with community leaders to update and score the components of the guideline. During the Review phase (B), general community and vendors have an opportunity to provide input and check the guidelines (C) against actual implementations. Review phase ends with Board approval of the draft guideline (D). This section provides specific rules and structure for each phase. 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.: 20015A.B2.2. This requirement may create numbering gaps in future iterations that will help indicate changes. Guidelines Draft Phase (A) Starting: S-3 A1. New Guidelines Start From Previous Guidelines 1. Receive DefCore Dedicated Section Guidelines 2. New Guidelines start from the previous Board approved document. 3. New Guidelines are given the preliminary name of the target year and .next. A2. Community Groups Tests into Capabilities 1. DefCore Committee coordinates community activities with the TC and PTLs to revise the capabilities based on current technical needs and functionality. 2. Groupings may change between iterations. 3. Tests must have unique identifiers that are durable across releases and grouping changes to be considered. 4. Tests must be under OpenStack governance. A3. PTLs Recommend Changes to Designated Sections A4. DefCore Committee identifies required capabilities 1. DefCore uses Board approved DefCore scoring criteria to evaluate capabilities. 2. DefCore needs Board approval to change scoring criteria. 3. Scoring criteria factor or weights cannot change after Draft is published. 4. DefCore identifies cut-off score for determining that a capability is required. 5. Capabilities will not be removed without being deprecated in the previous Guideline. 6. Capabilities will not be added without being advisory in the previous Guideline. A5. Foundation recommends OpenStack Components and OpenStack Platform Scope 1. Foundation recommends capabilities to include in each OpenStack Component. 2. Foundation recommends which Components are required for the OpenStack Platform. A6. Additional Capabilities and Tests 1. DefCore will work with the community to define new capabilities. 2. Test grouping for new capabilities will be included in the DefCore documents. 3. DefCore will publish a list of missing and gapped capabilities. A7. DefCore Committee creates recommendation for Draft. 1. DefCore Committee coordinates activities to create draft. 2. DefCore Committee may choose to ignore recommendations with documented justification. Guidelines Review Phase (B) Starting: Summit B1. All Reference Artifacts are reviewed via Gerrit 1. Draft Guideline 2. Designated sections 3. Test-Capability groupings 4. Flagged Test List 5. Capability Scoring criteria and weights 6. Not in Gerrit: Working materials (spreadsheets, etc) B2. Presentation of Draft Guidelines 1. DefCore will present Draft Guidelines to the Board for Review 2. DefCore will distribute Draft Guidelines to the community 3. Foundation provides Draft to vendors for review B3. Changes to Guideline made by Gerrit Review Process 1. Community discussion including vendors must go through Gerrit 2. All changes to draft must go through Gerrit process B4. For Gerrit reviews, DefCore CoChairs act as joint PTLs 1. Board committee members of DefCore serve as "core" reviewers (+2). 2. Requests for changes, must be submitted as patches by the requested party. 3. DefCore Committee members cannot proxy for community change requests. Community Review & Vendor Self-Test (C) Starting: S and continues past S+3 C1. Vendor Self-Tests 1. Vendors are responsible for executing these tests identified by the DefCore committee. 2. The Foundation may, but is not required to, provide tooling for running tests. 3. The Foundation may, but is not required to, define a required reporting format. 4. 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. 5. Self-test results cannot be used as proof of compliance. C2. Vendor submits results to Foundation for review 1. The Foundation determines the acceptable format for submissions. 2. The Foundation has final authority to determine if Vendor meets criteria. 3. The Foundation must provide a review of the results within 30 days. C3. Vendor Grievance Process 1. Vendors may raise concerns with specific tests to the DefCore committee. 2. The DefCore committee may choose to remove tests from a Guideline (known as flagging). 3. The DefCore committee must respond to vendor requests to flag tests within 30 days. 4. Vendors may not request flagging all tests in a capability. C4. Results of Vendor Self-Tests will be open 1. The Foundation will make the final results of approved vendors available to the community. 2. The Foundation will not publish incomplete or unapproved results. 3. Only "pass" results will be reported. Skipped and failed results will be omitted from the reports. 4. Reports will include individual test results, not just capability scoring. C5. API Usage Data Report 1. The Foundation will provide DefCore committee with an open report about API usage based on self-tests. 2. To the extent the data is available, capabilities beyond the DefCore list will be included in the report. Guideline Approval (D) Starting: S+3 D1. Board will review and approve DefCore Guideline from draft 1. Guidelines are set at the Platform, Component and Capability level only. 2. Text guideline document is authorative over the JSON representation. 3. DefCore will provide JSON representation for automated scoring 4. Guidelines only apply to the identified releases (a.k.a. release tags). D2. DefCore Committee has authority on test categorization 1. Can add flagged tests before and after Guideline approval. 2. Cannot change Test to Capability mappings after approval. 3. Maintains the test to capability mappings in the JSON representation. D3. Designated sections only enforced for projects with required capabilities 1. Designated sections may be defined for any project. 2. Designated sections applies to the release (a.k.a. release tags) identified in the Guideline. D4. Guidelines are named based on the date of Board approval 1. Naming pattern will be 4 digital year dot and 2 digit month. Functional Information Format: RestructuredTet Layout: 1.0 * -- Rob ____________________________ Rob Hirschfeld, 512-773-7522 I am in CENTRAL (-6) time http://robhirschfeld.com twitter: @zehicle, github: cloudedge & ravolt

1 0

Suggestions about OpenStack Diversity?
by Rob Hirschfeld 31 Mar '15

31 Mar '15

OpenStack Community, The Board has been discussing how to encourage diversity (all types from gender and region to commercial and technical) and also work to improve transparency of Board processes. If you have ideas for us to consider, please feel free to reply to this thread. If you think that we're doing OK (or not) on this, please let us know that too. Thanks, -- Rob ____________________________ Rob Hirschfeld, 512-773-7522 I am in CENTRAL (-6) time http://robhirschfeld.com twitter: @zehicle, github: cloudedge & ravolt

4 7

April 2 OpenStack Board meeting call for agenda items; Board packet materials due by Monday March 30th.
by Alan Clark 31 Mar '15

31 Mar '15

The next OpenStack board meeting will be held on April 2nd at 12noon - 2pm pacific. Committee Chairs and Directors please send me items you would like on the agenda. I need the materials for the board packet by EOB Monday March 30th so that I may post and distribute the materials to the board prior to the meeting. (Please tell me if materials need to be marked confidential.) I've started drafting the agenda[1]. Expecting topics from several committees, it's going to be a very full agenda. We will also be holding an Executive Session during the meeting. Thanks, AlanClark [1] https://wiki.openstack.org/wiki/Governance/Foundation/2Apr2015BoardMeeting#…

12 18

Transparency Committee meeting
by Steve Hallett 31 Mar '15

31 Mar '15

To join etherpad discussion: https://etherpad.openstack.org/p/Transparency_Committee_Meeting_(Mar_31,_20… Meeting information Topic: Transparency Committee Date: Tuesday, March 31, 2015 Time: 7:00 pm, Pacific Daylight Time (San Francisco, GMT-07:00) Meeting Number: 593 747 373 Meeting Password: 1951 To start or join the online meeting Go to https://symantecmeetingcenter.webex.com/symantecmeetingcenter/j.php?MTID=m2… Teleconference information Provide your phone number when you join the meeting to receive a call back. Alternatively, you can call: Call-in toll-free number (Premiere): 1-877-805-0966 (US) Call-in number (Premiere): 1-719-867-4947 (US) Show global numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=7233209291&num=1877-8… Host Access code: 310 116 1103 Participant Access code: 723 320 9291 For assistance 1. Go to https://symantecmeetingcenter.webex.com/symantecmeetingcenter/mc 2. On the left navigation bar, click “Support”. To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://symantecmeetingcenter.webex.com/symantecmeetingcenter/j.php?MTID=m1… To check whether you have the appropriate players installed for UCF (Universal Communications Format) rich media files, go to https://symantecmeetingcenter.webex.com/symantecmeetingcenter/systemdiagnos…. http://www.webex.com We’ve got to start meeting like this™ CCM:+17198674947x3101161103# IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. You should inform all meeting attendees prior to recording if you intend to record the meeting. Please note that any such recordings may be subject to discovery in the event of litigation.

1 0

Transparency Committee meeting
by Steve Hallett 31 Mar '15

31 Mar '15

To: Transparency list Cc: Foundation Board list The transparency committee has not had a chance to meet since Mar Board meeting. We have some open actions items from Mar meeting, and prior to Apr Board meeting. I am unclear as to definitive current committee member list, therefore am cc:ing entire board, foundation board list, as well as transparency committee list. I apologize for late notice, and the scheduling conflict, but did want to find a timezone that would support global participants. (Meeting invite to follow separately) [X] OpenStack Transparency Committee Mar 31 Agenda rough outline * Chair status * Committee member status * Report Card: o How are we doing relative to stated goals and commitments? * Top-of-mind issues for discussion o Open items from Mar 3 Board meeting * Recommendations and read-out to Board for Apr 2 Board meeting * Set date/time for next committee meeting To join etherpad discussion: https://etherpad.openstack.org/p/Transparency_Committee_Meeting_(Mar_31,_20… [X] Transparency Policy http://www.openstack.org/legal/transparency-policy/ Committee page: https://wiki.openstack.org/wiki/Governance/Foundation/TransparencyCommittee [X] WIP >From Kavit's Mar 1 email to Board for Agenda items: Transparency 1. Set usage rules for sending email to the confidential Board list (done) 2. Ensure community feedback in the decision making process for those rules (wip) 3. Regular reports from the transparency committee (wip) >From Jonathan's post Mar 3 NYC Board meeting email: "Finally, the Board wrapped up with an hour-long discussion about transparency and diversity. Discussion points included implementing better mailing list procedures, potential changes to the Transparency Policy and how Board Members can better engage with and support all of our global communities. Sean Roberts is picking up the Transparency Committee work, which will convene in the next few weeks to follow up on the discussion with more concrete recommendations and actions on that front. Also, Robert Esker started a thread on this list to discuss potential updates to the Transparency Policy." In process edits to Transparency Policy https://docs.google.com/document/d/1FeSSw1r3imd6B-Wf2oj5VcwekhNF-jtv5upNh1P…<https://docs.google.com/document/d/1FeSSw1r3imd6B-Wf2oj5VcwekhNF-jtv5upNh1P…> [X] Thoughts (and questions) on Transparency: What * Decision Making * Spending * Vendor Influence * Community Participation * Why contributions are accepted or rejected * ... Who is accountable to whom? * Foundation * Board * TC * Members * ... [X] Separate item if time: (Not sure whether to keep within Transparency committee) Diversity & Inclusion 1. Establishment of a diversity committee, with a remit to ensure diversity at the board, Foundation staff and project contributor levels 2. Regular reports on diversity released bi-annually 3. Expert review of the bylaws for other discriminatory content a. Extend Travel Support for individual directors. Prohibitively expensive for unsponsored individual directors. Only one trip presently with 4 x F2F per annum b. (example 2 - Affiliation criteria is non inclusive. Proposal to change $ amount to a % of the income earned) 4. The foundation must have a published diversity and inclusion policy that covers the Foundation employees AND its actions with respect to the community. The board needs to set the direction for the Foundation to follow and the Foundation executive should have these goals included in their performance criteria.

1 0

Re: [Foundation Board] April 2 OpenStack Board meeting call for agenda items; Board packet materials due by Monday March 30th.
by Rob Hirschfeld 26 Mar '15

26 Mar '15

Alan, DefCore has updates on process draft and possible action to approve 2015.04 Guideline. 10 minutes max. Rob On Mar 25, 2015 5:53 PM, Alan Clark <aclark(a)suse.com> wrote: > > The next OpenStack board meeting will be held on April 2nd at 12noon - 2pm pacific. > > Committee Chairs and Directors please send me items you would like on the agenda. I need the materials for the board packet by EOB Monday March 30th so that I may post and distribute the materials to the board prior to the meeting. (Please tell me if materials need to be marked confidential.) > > I've started drafting the agenda[1]. Expecting topics from several committees, it's going to be a very full agenda. We will also be holding an Executive Session during the meeting. > > Thanks, > AlanClark > > > > > > [1] https://wiki.openstack.org/wiki/Governance/Foundation/2Apr2015BoardMeeting#… > > > > > > > > _______________________________________________ > Foundation-board mailing list > Foundation-board(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board

1 0

Notes for March 3 Board discussion
by Mark Collier 24 Mar '15

24 Mar '15

Hi everyone, In the March 3 board meeting we took some time to break off into groups to discuss emerging market opportunities: NFV/IoT, Containers, and Public & Hybrid Clouds. Additionally, given the importance of the new product management working group, there was a group focused on that. After the teams met they came back and shared their thoughts on the opportunities for OpenStack, which I attempted to summarize in the attached slides. The primary goal of the exercise was to raise awareness of the rapidly changing market landscape, while identfying potential areas to focus on going forward. One of the biggest takeaways was that there are many other communities and organizations working on adjacent technologies that we can better collaborate with, both at our summits and by working more directly in other forums. I look forward to working with everyone to ensure OpenStack is an integral part of these exciting emerging markets! Mark

3 2

promoting the newly open Foundation-Board list
by Rob Hirschfeld 24 Mar '15

24 Mar '15

All, It occurs to me that we still need to advertise that the list is now available for community subscribers. Here's my tweet about it: https://twitter.com/zehicle/status/580120314241163264 And a short link to the list http://bit.ly/1CKP subscription page. -- Rob ____________________________ Rob Hirschfeld, 512-773-7522 I am in CENTRAL (-6) time http://robhirschfeld.com twitter: @zehicle, github: cloudedge & ravolt

1 0

This list is now publicly accessible
by Jonathan Bryce 21 Mar '15

21 Mar '15

Hi everyone, As mentioned on Wednesday, we made the switch to turn this list public yesterday. Any emails sent here going forward will be publicly visible in the archives: http://lists.openstack.org/pipermail/foundation-board/ Mark McLoughlin managed to send an email at the exact time we were moving the archives, so his message ended up in both lists. Well played, Mark! = ) For any confidential information, use the mailing list at foundation-board-confidential(a)lists.openstack.org. I’m happy that we’ve been able to implement this now as laid out in the the Transparency Policy. Since we have achieved the desired configuration, emails sent to the confidential mailing list are automatically considered Confidential Information under the Transparency Policy and should not be forwarded outside of the membership of that list without the consent of the person sending the original email. If you feel that information sent to the confidential list should be publicly available, first ask the original sender if they are willing to repost to this or some other public list. If you and the original sender disagree about whether or not the information should be made public, escalate to the Chairperson of the Board and Executive Director. If there is still disagreement, it may be brought before the Board as a whole. I hope that with this new list configuration we won’t have issues in this area, but in any case, none of us should act unilaterally in making confidential information public. Thanks again to the infra team for helping with the set up. Let me know if you have any questions, Jonathan

2 1