September 2019 - Foundation-board

board meerting in Shanghai
by Arkady.Kanevsky＠dell.com 27 Sep '19

27 Sep '19

Dell Customer Communication - Confidential DO we have a scheduled board meeting in Shanghai? I would expect it will be Sunday Nov 3 prior to the summit. Need to arrange travel so people can attend in person. Thanks, Arkady

2 1

Upcoming Interop guideline and the future of OpenStack Interop Guidelines
by Egle Sigler 20 Sep '19

20 Sep '19

Foundation Board, Thank you for approving the latest interop guideline during the last board meeting. As I mentioned during the last board meeting, we are going to start scoring the next guideline to be approved during the November board meeting and we are looking for volunteers to join the Interop Working Group. The current process for creating the next guideline requires talking to the project PTLs and other members of the community to determine if there are any significant changes to the projects, determining which tempest tests are associated with these changes, and scoring the changes based on interop core criteria [1]. After the scoring is complete, we discuss the results in an IRC meeting and submit patches for updating the guidelines. If you can help and would like to learn more about the process, please let me know! During Shanghai board meeting I would like to have a discussion with the board about the future of the interop program. With help from the community and some very dedicated people that included Chris Hoge (secretary of Interop WG, OpenStack Foundation) and Mark Voelker (co-chair of Interop WG, VMware) I have co-chaired Interop Working Group for almost 5 years. During this time the Interop guidelines have become stable, with fewer and fewer changes made in each new guideline. I think that if the board wants to continue with the guidelines as-is, with twice a year updates (or more if needed), we will need new volunteers to co-chair Interop WG and help drive the program. Another option would be to simplify the trademark program so that it doesn’t require so many volunteer hours. If it relied more on contractual assertions and less on formal technical checks requiring updated guidelines, it could be directly handled by the foundation. In addition to the guideline maintenance and updates, there is the work involved in running and maintaining RefStack. RefStack is used to validate and submit the results, and needs constant maintenance and updates as well. A more contractual interop program would not require an overhead of maintaining an additional project. I believe that Interop guidelines are instrumental in maintaining OpenStack interoperability, however, I also believe that we need to make the program easy to maintain and abide by. As such, I would like to hand over the program as-is to new volunteers from the board, or simplify the program down to a contract that can be directly managed by the foundation.. After this next guideline, the board will need to decide what path the interop guidelines should take. Current process is strict and requires a lot of volunteer hours. While the program was being created and growing, we had a lot of community involvement. Once the guidelines became stable, we had less and less participation. As of last week, Chris Hoge, a key member of the Interop Working Group, no longer works for the Foundation and we will no longer be able to count on him doing a lot of the heavy lifting when it comes to guideline changes. [1] https://github.com/openstack/interop/blob/master/doc/source/process/CoreCri… Thank you, Egle Sigler

2 1

Passing the Red Hat baton to Daniel Becker
by Mark McLoughlin 11 Sep '19

11 Sep '19

Hi all Some months ago I transitioned within Red Hat from a management role back to an individual contributor role and lately I'm not so directly involved with Red Hat's day-to-day OpenStack operations. These past years on the board have been quite a ride, and I'm very grateful for the opportunity to work with you all. I remain a big advocate of the OpenStack, and so I'm very happy to be passing the baton as Red Hat's representative on the board to my good friend and close colleague, Daniel Becker. As director of our OpenStack engineering organization, Daniel is obviously very close to Red Hat's OpenStack concerns, and has a particular interest in the health of the developer community since he is directly responsible for the majority of Red Hat's contributors. Daniel will join today's board meeting in my place. Please give him a warm welcome, and keep in touch! Thanks, Mark.

3 2

Director Diversity - Item for Board meeting
by Jonathan Bryce 06 Sep '19

06 Sep '19

Hi everyone, One of our 2019 directors, Sean McGinnis, recently switched employment to Dell. As most of you know, the Bylaws have a clause in Article 4.17(a) that ensures diversity of representation by limiting the number of directors that can be affiliated with a single corporate entity to two (the “Director Diversity Requirement”). We already had two directors from Dell on the Board (Arkady Kanevsky and Prakash Ramchandran), so Sean’s new affiliation brings that total over the limit. Article 4.17(d) of the Bylaws states “If a director who is an individual becomes Affiliated during his or her term and such Affiliation violates the Director Diversity Requirement, such individual shall resign as a director.” However, 4.17(e) says "A violation of the Director Diversity Requirement may be waived by a vote of two thirds of the Board of Directors (not including the directors who are Affiliated).” Sean has requested that the Board vote on a motion to waive the violation under 4.17(e). In the case of this Board vote, Arkady, Prakash and Sean would abstain from voting and the remaining directors could vote to waive or not waive the violation for the remainder of the 2019 term. Alan will add this item to the agenda, so I wanted to send out some brief background on the issue and the relevant sections from the Bylaws ahead of the meeting. If you have any questions, feel free to pass them along, Jonathan

1 0