Crusty Blaa

On Oct 3rd, the OpenStack Foundation Board held a two hour conference call meeting which was open to anyone to join. The agenda was published in advance.

As usual, this my informal recollection of the meeting. It’s not an official record, etc. Jonathan published an official summary on the foundation mailing list.

Preliminaries

Our chairman, Alan Clark began the meeting by holding a roll call. If my count was correct, we had 21 of the 24 members of the board on the call, which is a pretty good turnout.

Alan introduced Chris Kemp as a replacement for Devin Carlen who had been representing Nebula and the Gold Members. Chris briefly explained that changes in his role at Nebula has left him more time for "strategic stuff" and is delighted to spend more time with the OpenStack community and join the board. He thanked everyone for their work in progressing the foundation to date.

Before getting down to business, we quickly voted to approve the minutes of the previous meeting.

Executive Director Report

Jonathan Bryce took the floor and gave a really excellent update on the Foundation's progress.

First off, he described the launch of the OpenStack Foundation Training Marketplace at LinuxCon in New Orleans. The site now has 12 companies listing training events at over 30 cities around the world and has seen over 10,000 unique visitors over the past 2 weeks. He reiterated how one of the Foundation's stated priorities for this year is to help training providers get the word out on their education programs and thereby expand the pool of people with OpenStack skills.

Next up, Jonathan gave an update on preparations for the OpenStack Summit in Hong Kong. Everything is coming together nicely and the finalized speaking agenda has now been posted. He explained that, while they had received some 250 submissions for the summit in Portland, there were over 600 submissions for Hong Kong and yet not many extra speaking slots. The track chairs had a tough job whittling down the submissions but he thinks the end result is an agenda packed with great sessions. Jonathan warned that, unlike previous summits, we have a hard limit on the number of attendees and the "full access" passes will sell out in the next week or so.

Eileen asked exactly how many full access passes were issued and Jonathan explained there are 2,000 but that there are many more passes for the general sessions and expo hall. Joseph asked for some insight into the demographics of the registered attendees and how it compares to previous summits. Jonathan felt that we would see a large number of attendees from the region and that, while some companies may have reduced their numbers travelling from further afield, there would still be plenty of representation from all of the companies we are used to seeing at summits.

The discussion then moved on to looking ahead to 2014 and a sneak peak of next year's budget. Jonathan explained how 2013 was a great year financially - particularly because the summits were larger than expected - and the Foundation goes into 2014 with a healthy budget surplus of over \$1M. We expect to continue to see large summits and this will lead to increased revenues and expenses. Jonathan expects the Foundation to continue to invest in technology and infrastructure over 2014. He described the Foundation funded projects in 2013 to improve the member database and tie it to the contributor agree process and an improved system for handling summit speaker submissions.

Rob Hirschfeld asked whether the Foundation had budgeted for certification testing infrastructure being proposed as part of the "what is core" discussion. Josh felt this it not be necessary for the Foundation to fund this, and there was a brief data tracking and authentication systems.

Jonathan continued by describing the rapid growth in Foundation staff during 2013, but that he expects ongoing staffing costs to have mostly levelled off for 2014. He went on to talk about how he sees the role of the Foundation over the next year to be around connecting different parts of the community, helping to gather data on users and deployments and sharing information with the world about new features in each release.

One Jonathan had finished, Lew Tucker congratulated Jonathan on the progress and asked whether a written summary could be prepared for board members so that we could help get the word out. Josh pointed out that we were soon due an annual report which would contain much of this information.

Josh then asked a question about the project budget for gold member fees and how many new members this assumed would be added in 2014. There was some confusion on the issue because gold member fees are based on the member's revenue, but the conclusion was that the addition of 4 new members was projected. This would bring the total number of gold members up to 20 out of a total possible 24 members.

Election Committee Report

Next up, Todd Moore delivered an excellent summary of the discussions and conclusions of the committee established to consider whether any changes were need for the individual and gold member director election systems and what those changes might be.

Todd's report - which will be published in full soon - described how we considered three separate questions. Firstly, whether and how concerns about the fairness of the individual member director election system (particularly the issue of large blocks of affiliated voters) should be addressed, secondly whether we should consider any rule changes around foundation employees eligibility for the individual member director election and, finally, whether the eligibility rules for the 2013 gold member director elections had been properly enforced.

The last topic was easily dispensed with - Todd and the committee worked with the foundation staff to verify that all eligibility rules (i.e. eligibility as a candidate and eligibility to vote) had been properly enforced.

The first topic proved to be substantially more contentious. The pros and cons of changing to an STV based election system or tweaking the rules of the current system to halve (from 8 to 4) the number of votes which you could allocate to a single candidate were explained in great detail. Todd explained how the committee felt that changes were not necessarily warranted but that it would be wise to seriously consider the option of the "max 4 votes per candidate" tweak.

A motion was proposed to not fundamentally change the voting system and was almost voted for until it became apparent that Monty wanted to speak but was unable to come off mute. Once that was sorted out, Monty stated that the cumulative system was utterly broken and that block voting did, in fact, influence the outcome of the election. He felt strongly that a change to STV was needed. The debate then took off in earnest with many well put points made by various members. I explained how I agreed fully with Monty but that I was convinced by the "it's working reasonably well; this doesn't warrant a the disruption of a bylaws change" but that we needed to be alert to any renewed concern from members after the next election. In the end the vote was passed with no abstentions and Monty voting against.

The discussion then moved on to the question of the "only 4 votes per candidate" tweak. Much of the discussion hinged on whether this tweak required a bylaws change. The election committee and Jonathan felt that it was compatible with the "cumulative voting system" language in in section 3.9a of the bylaws but legal counsel for the foundation (Mark Radcliffe) disagreed strongly and felt "cumulative voting" was "binary in the eyes of the law". Since the committee had suggested this tweak on the understanding that it was easy to implement, the idea was dropped.

Next, we discussed the second issue - the question of foundation employees on the board. The committee did not have a consensus recommendation on this but Todd did summarize the different viewpoints and arguments. One approach proposed that the executive director would be granted a new, automatic seat on the board and (because there is a limit of two members per organization), only one additional foundation employee could be elected to the board rather than the current limit of two employees. There was lots of debate and I felt Jonathan's input was particularly interesting - that he did not see the need for an automatic executive director seat and he had reservations about restricting employees from being directors since they could bring invaluable and passionate input, should the electorate choose to elect them. In the end, it was felt there was not sufficient cause to warrant a disruptive bylaws change and the motion was withdrawn.

So, in summary, there will be no election system changes proposed to the electorate during this cycle. However, the board again re-stated the importance that all members adhere to the community code of conduct which states:

Respect the election process. Members should not attempt to manipulate election results. Open debate is welcome, but vote trading, ballot stuffing and other forms of abuse are not acceptable.

Finally, the committee took an action item from the board to analyze the results of the next election and provide the board with a report on the potential effect of any of the options proposed.

Wrapping Up

Because of the lengthy debate on the election system, we had run out of time and the rest of the agenda had to be postponed until the in person board meeting in Hong Kong.

Edits

• Changed from "legal counsel for the board" to "legal counsel for the foundation". Thanks to Richard Fontana for the correction.
• Included a reference to the code of comment. Thanks to Rob Esker for his question.

On Aug 6th, the OpenStack Foundation Board held a two hour conference call meeting which was open to anyone to join. The agenda was published in advance.

As usual, this my informal recollection of the meeting. It's not an official record, etc. Jonathan published an official summary on the foundation mailing list.

Preliminaries

Alan Clark chaired the meeting and spent the first few minutes reviewing the agenda and holding the roll call. We had more than 50% of the board members, and so had sufficient quorum.

We then reviewed the minutes of the previous meeting and approved them by vote. Todd, Troy, Nick, Devin and Jim all abstained because they weren't present at that meeting.

Patent Cooperation

Next up was a follow-on from the patent cooperation discussion at our previous meeting.

The Legal Affairs Committee had previously proposed three options that we make no change, that we implement a Google-style patent pledge or that we introduce an OIN-style cross licensing agreement.

Keith Bergelt, CEO of the Open Invention Network, attended the meeting and gave a presentation describing the OIN and how it could play a key role in OpenStack's strategy to create an environment of patent non-aggression around OpenStack. Keith has been actively working with the Legal Affairs Committee to develop a fourth proposal for the board which would make the best possible use of the OIN.

Keith described how the OIN was formed 8 years ago by IBM, NEC, Novell, Philips, Red Hat and Sony to ensure "freedom of action, freedom to operate" around Linux. It has some 560 member companies who sign up to a broad cross-licensing agreement whereby any patents they hold which read on Linux is licensed to all other member companies.

The patents which are covered by the OIN agreement are those which read on the software packages listed in the OIN's Linux System Definition. Over time, this definition has grown to include the likes of Android, WebOS and, more recently, OpenStack. The OIN views OpenStack has one of the most import projects after Linux and feels that including OpenStack in its defintiion is an obvious step.

That OpenStack is included in the OIN system definition means that there are already 560 licensees committed to non-aggression around OpenStack. Keith feels that this goes a long way to achieving the OpenStack Foundation's goals in this area and that we should seek to make the most effective use of the existence of this agreement rather than reinvent the wheel.

Keith proposes a more formalized relationship with the Foundation, that members would be encouraged to join the OIN, that we'd do joint press releases and that there would be an ongoing direct relationship with the TC to ensure the system definition is regularly updated to include all OpenStack projects.

Legal Affairs Committee

Van Lindberg was up next to provde an update from the Legal Affairs Committee but this turned out to be a continuation of the previous discussion on patent cooperation.

Van summed up this fourth proposal succinctly - that OpenStack members get behind the OIN. He went on to describe how a difficulty with this approach is that some members of OpenStack will never be members of the OIN because the OIN fundamentally see those companies as a threat to Linux. He didn't name these companies.

So, the question becomes how we can ensure the ability of those OpenStack members who aren't members of the OIN to join a patent cooperation initiative specifically around OpenStack.

Van first described how OpenStack LLC (the Rackspace owned entity which held OpenStack's before the Foundation was formed) actually joined the OIN some time ago because of concerns about the "CPTN transaction". The OpenStack Foundation could quite easily take over this agreement and, by virtue of the fact that the OpenStack Foundation is in some sense the entity licensing the OpenStack software to everyone, the benefits of the OIN cross-license would flow to all OpenStack users.

For OIN non-members, the Foundation could create a separate, limited license agreement whereby the OpenStack related patents held by such licensors would be licensed to the Foundation and the benefits of that agreement would also flow to all OpenStack users.

Van went on to talk a little about patent trolls (a subject close to his heart), how this is a serious issue for OpenStack and how, even now, there is a troll going after Rackspace and HP over a number issues including some related to OpenStack. Van feels that the OIN does not actually protect against the threat of trolls very well, because (somewhat obviously) such trolls would not be members of the OIN.

Van raised again (this has been discussed before) the idea of a patent indemnity program whereby OpenStack members (or even just the Foundation) would contribute to a fund which could be used for the legal defence (not any settlements themselves) of any OpenStack members threatened by patent trolls for the use of OpenStack. Van feels that patent trolls often go after some weaker companies, obtain a small settlement because that company feels it's cheaper to settle than to defend and that settlement sets a problematic precedent that the troll can then build upon. An indemnity program would encourage members to fight patent trolls and avoid precedents being established which would set the entire community up for trouble.

Eileen made the point that the OIN was created because the GPL lacks a patent license. We're not in the same position, since OpenStack is licensed under the Apache License which includes a broad patent license. She raised concerns about the idea of an indemnity program, how it's scope could turn out to be very large and expensive and disagreed that trolls always go after the smaller players.

The conclusion was ... no decisions today, more dialogue needed.

OpenStack Training

Next up, Jonathan revisited the topic of how the Foundation can encourage and regularize the market forming around OpenStack training.

This topic was also covered in the June meeting and Jonathan felt there was good support for some of the proposals but board members had concerns and questions about other aspects. Since then, Jonathan has been talking to several board members including Brian Stevens and Boris Renski and feels he can provide some clarifications and updates. The Foundation would like to move forward with two proposals - a training licensing program and a baseline certification test.

The training licensing program would replace the use by training providers of the Built For OpenStack mark. This will allow the Foundation to have a closer relationship with training providers and help raise awareness about the availability of OpenStack training. There is broad support for this proposal
and the Foundation have a draft agreement ready to circulate to training providers.

The baseline certification test proposal was the proposal that has required more discussion but it is better understood now. The idea is that the Foundation would define a common baseline set of training which all licensed OpenStack providers must include and certify against, but that the Foundation also fully expects providers to expand upon this content greatly and compete on the unique aspects of their training.

The vast majority of what would be included in this baseline training is already covered by all training courses out there. The Foundation would not seek to force content and topics on training providers but would instead seek to add new content when it sees that training providers are already covering these new topics. It is expected that the Foundation staff and others it engages will take 6-9 months to prepare this program.

Jonathan feels a baseline OpenStack certification would ensure that there is OpenStack training which globally available, not cost-prohibitive for students in regions all around the world and provides a target for people who want to become knowledge around OpenStack.

The board moved to support the Foundation staff in its efforts to create a baseline certification testing program for OpenStack. The motion was passed unanimously.

User Committee Update

Tim Bell took the floor next to raise an issue the User Committee has been discussing in recent times.

The committee currently consists of Tim, Ryan Lane and JC Martin. While the committee is doing a great job, they feel that their limited numbers (and their limited time) is constraining their ability to achieve some of their goals.

The obvious solution is to add more members to the committee, but there's a catch. Committee members sign an NDA and have access to some sensitive data about OpenStack deployments which are obtained through surveys with the understanding that the information is confidential. Adding significantly more members could compromise the confidence that survey responders would have in the confidentiality of their responses.

Tim has been talking with Tom Fifield about what role Tom could take (as a Foundation staff member) on the committee in order to help out, without Tom having to sign the NDA and gain access to the confidential survey results. The idea is that Tom can take on some of the responsibility to act as a go-between who ensures that issues which are identified by the committee are raised as appropriate with the developer community.

In a similar vein, the committee is exploring the idea of a structure whereby only the "core" committee members need to sign the NDA and there would be sub-groups of the committee who can get involved without gaining direct access to the survey results.

What is Core

Rob Hirschfeld gave a quick update on the "what is core" discussions he is
leading. The discussion was initially limited to the board, more recently
broadened to include the TC and Rob now plans to broaden it to include the
wider community.

Rob mentioned a flowchart he has prepared to describe some of the proposed process. He also discussed how the initial position on requiring "plugins" has evolved into talk of designating some parts of projects as "required implementations" and allowing other parts to have "alternate implementations".

Other Updates

Todd and Rob met with the Foundation's legal team to discuss what changes to the Individual Directors election process would be allowed under Delaware law. He will present some thoughts on this at the next board meeting.

Simon has been working with Mark Collier and Heidi Bretz to ensure that companies who have expressed an interest in applying to be a Gold Member are aware of the board's revised expectations around new members. Simon and the membership committee still plan on re-drafting the wiki page describing the criteria for new members.

Alan mentioned that the Compensation Committee completed a mid-year review of Jonathan's goals for the year and concluded things are very much on track. Full details were posted to the foundation-board mailing list.

The next board meeting is scheduled for October 3rd at 9am PST. There will also be an all day board meeting in Hong Kong on November 4th.

OpenStack has an awful lot of developers writing Python code and many of us wouldn't consider ourselves true "pythonistas". This means we wind up having a bunch of interesting discussions about e.g. EABL vs LBYL.

A particular bugbear of mine is exception handling. I'm convinced that very, very few developers think hard about their error handling strategy and that the problem is even more serious with exception based languages.

So, I really like getting into error handling discussions. This morning, we have a great one - how to do exception chaining in Python, and whether that's even something you want to do.

On June 27, the OpenStack Foundation Board of Directors met for two hours via conference call. As usual, the agenda was published in advance and the meeting was open to anyone who wanted to observe the proceedings.

These notes are my perspective of the meeting. Jonathan Bryce published an official summary and official minutes will be posted in due course.

Roll Call and Meeting Confidentiality Policy

As you can imagine, a conference call with 20-30 attendees takes a while to get going. We began with a roll call and, after perhaps 15 minutes, were ready to get started.

First item on the agenda was a review of our meeting confidentiality policy. Directors agree to refrain from commenting on the meeting proceedings until Jonathan posts his summary. The only official record of the meeting is Jonathan's summary and the official minutes. Anything discussed during executive session is confidential. Nothing new here.

Amendment to our Certificate of Incorporation

Next up was a motion to approve a relatively minor amendment to the foundation's certificate of incorporation.

The details of the amendment is fairly obscure, but essentially the Foundation is applying for U.S. 501(c) status which means it will be a tax-exempt, non-profit organization. There are various different organization types, but the
two most relevant are 501(c)(3) and 501(c)(6). OpenStack is filing for 501(c)(6) status.

Jonathan explained that, while preparing for this filing, it was noted that the original certificate of incorporation only allows (on winding up of the foundation) the foundation's assets to be transferred to a 501(c)(3) organization. This amendment simply allows for the possibility of transferring assets to 501(c)(6) organizations.

There was some brief discussion clarifying exactly which status we were filing for and the motion was passed unanimously.

Transparency Policy

Next up, Lauren Sell explained the context for a formal transparency policy document which had been circulated to the board members and would require further discussion before being approved.

Lauren reminded us that at our meeting in April, the Transparency Working Group presented the principles for a transparency policy. Lauren had since worked with legal counsel to draft a more formal policy based on those original principles.

The main question Lauren felt needed to be cleared up was the issue of document management. The board has (and will continue to have) documents which must remain confidential. At our April meeting we had agreed that the OpenStack Infrastructure team would investigate hosting an OwnCloud instance which would act as our document store. While this was still on the team's to-do list, it had not been prioritized over other work.

I suggested that, in the team time, we create a new mailing list for the the board (e.g. foundation-directors?) which would be open to everyone for read-only subscription and we would use the current mailing list to share confidential documents. Once the document management system is in place, we could then shut down the private foundation-board mailing list.

Rather than discuss in any great detail, it was agreed the Lauren would start a discussion on the foundation mailing list.

Summits & Marketing

Next up, Mark Collier and Lauren gave us an update on the Marketing front and how summit planning is progressing.

Lauren first talked through some excellent slides with a tonne of details about the Icehouse Design Summit in Hong Kong from Nov 5-8, 2013. This is the first time that the summit will be held at an "international venue" (an amusing term if you're not U.S. based :) and we again expect record attendance.

Included in Lauren's slides were some really helpful maps and aerial shots showing the venue, the geography of Hong Kong and the location of the recommended hotels. The venue is located near the airport which is a 25 minute train journey from down town Hong Kong. There are a couple of hotels adjacent to the venue and most of the other recommended hotels are down town. The foundation staff have worked hard to come up with a good range of hotel options, including hotels with a rate of under \$150 per night.

In terms of travel advice, it was noted that visitors must have a passport valid for at least one month after their planned stay and that flights from SFO to HKG are currently averaging between \$1000 and \$1400. Jonathan recommends that people book their flights early, because fares will increase very significantly closer to the event. Lauren also pointed out that it's sensible to make hotel books now, since the hotels closest to the venue are already selling out.

Lauren then talked through the planned format for the summit, which has been heavily influenced by feedback received through the survey results from the previous summit.

This time around there will be two types of passes. A more affordable limited access pass will give access to the expo hall, general sessions and a single track of breakout sessions on Tuesday and Wednesday. The hope is that this will help control the numbers at the breakout sessions, but also make the event more accessible to folks who just want to come along for the first time and learn about OpenStack.

The primary language of the event will be English, but there will be simultaneous translation into Mandarin in the main hall.

The call for sponsors is already open and we have 21 sponsors to date. The headline sponsorship sold out in an astonishing 7 minutes.

For the first time, there will be a travel support program designed to ensure that lack funding won't prevent key technical contributors from attending the event. Details of this will be announced very soon. We had a brief discussion about how this program should be run and it was pointed out that we could learn from similar programs for PyCon and UDS.

In terms of learnings from the previous summit, some of the things the team will be working hard to improve is the quality of network connectivity, the size breakout rooms and the variety of beverages and snacks.

It was noted that feedback from ATCs who completed the survey was 2.5:1 in favour of keeping the design summit collocated with the conference. In Hong Kong, the design summit rooms will be well separate from the breakout session rooms, ATC status will be properly indicated on name badges and it will be much more clear on the schedule which sessions are part of the design summit and which are breakout sessions.

After some interesting discussion about the plans for Hong Kong, Lauren gave a brief overview of how plans are proceeding for the 2014 summits. The spring summit is planned for the week of May 14 with Atlanta and Chicago under consideration. The autumn/fall summit will be one of the first two weeks of November with Paris and Berlin currently under consideration. Decisions on the venues for both these summits are expected to be made soon.

Finally, Lauren ran through some updates on the progress of the marketing community more generally. Version 1 of the OpenStack marketing portal has been made available. The mailing list is gaining new subscribers all the time. The monthly meetings are also seeing growing numbers attending.

Patent Cooperation Proposal

Next on the agenda was a presentation from several members of the Legal Affairs Committee on the three options they recommend the foundation should consider for increased cooperation on patent sharing or cross-licensing between foundation members.

Frankly, I don't really have the energy to try and summarise these proposals in great detail, so this is short ... however, this is certainly a complex and important topic.

The Apache License v2.0 has a patent provision which means you grant a license to any of your patents which are infringed upon by any contributions you make. If any licensee of the software claims that the software infringes on their patent, then they lose any patent rights granted to them under the license.

Two options were presented to the board for how we might encourage further sharing of patents related to OpenStack between the companies involved. The idea is that we could put OpenStack in a better defensive position by sharing a wider range of applicable patents.

The first option proposed was to closely copy Google's Open Patent Non-Assertion Pledge. The idea is that companies involved in OpenStack would pledge to not assert specific sets of relevant patents against OpenStack users.

The alternative option proposed was the adoption of an OIN-style patent cross-licensing scheme. The primary difference of this scheme is that an actual patent license is granted to users, rather than just a non-assertion pledge.

The slides outlining these options will be posed to the foundation wiki page. It is hoped the board will be in a position to come to a decision on this in November.

Closing Topics

Alice King is stepping down from her role on the Legal Affairs Committee, so the board voted to approve a motion to appoint Van Lindberg to the committee.

Rob Hirschfeld gave an update on his work to bring about a productive discussion on the question of "what is core?". Rob has held a couple of meetings with other board members and drafted six position statements which he hopes will drive the discussion towards a consensus-based decision. Rob wishes the board to come to a good level of consensus on these position statements before opening the discussion up to the rest of the community.

Finally, there was a brief discussion about training and how members of the User Committee are actively working on training materials.

Last Thursday, on May 30, the OpenStack Foundation Board met over the phone for two hours to discuss a number of topics. The date for the meeting was set well in advance, the call was open to anyone who cared to listen in and agenda was posted in advance to our wiki page.

Below is my summary of our discussions. The official summary was posted earlier by Jonathan Bryce.

For this meeting, Lew Tucker acted as chairman in place of Alan Clark.

Training

The first big topic on the agenda was an update from Mark Collier on the Foundation's work-in-progress plans for official OpenStack training and certification programs.

The idea is that, with the huge interest globally in OpenStack, we're hearing consistently that there is a shortage of people with OpenStack expertise and training. The Foundation would like to address this in a way that adds new Openstack experts, grows our community and establishes a base knowledge set that everyone is united around.

The OpenStack ecosystem is already ramping up its training offerings and classes are available today from a number of companies all over the world. The Foundation wants to encourage this and help accelerate the availability of training.

Crucially, the Foundation proposes to introduce a new trademark program which would require all OpenStack training and credentialling providers to include a base set of training material and tests which would be developed by the Foundation itself. The hope is that we would protect the OpenStack brand by ensuring that all official training courses would have the same basic content and quality levels.

This proposal of a new trademark program triggered a significant amount of debate which continued on over email after the call. On the call, Jim Curry and Boris Renski kicked off the discussion by expressing similar concerns about whether the trademark program would actually hinder the growth of training offerings in the ecosystem. Jonathan clarified that intent isn't to prevent training programs from competing with additional content, but rather to ensure all programs have a common baseline. Others like Nick Barcet and Todd Moore chimed in with the view that OpenStack really needs this and Nick drew an analogy with Linux Professional Institute certification.

After much discussion, the conclusion was that the topic needed further discussion before any concrete steps could be taken. Mark Collier closed out the topic by making the point that the "Built for OpenStack" trademark was currently being used for OpenStack training and this would continue until an alternative plan was put in place.

Expect to see plenty more discussion about this soon on the foundation mailing list!

Next Board Meeting

We had some discussion about when our next meeting should be held and, based on the availability of board members, it looks like it will be held on Thursday, June 27 between 9am and 11am Pacific time.

Gold Member Committee

Next up, Simon Anderson discussed a new committee that we agreed to set up at our previous meeting - the Prospective Gold Member Committee.

The idea with this committee is that when companies approach the Foundation and express an interest in becoming a Gold Member, the Committee will work with the Foundation staff and the prospective member to ensure their application is properly prepared before it comes before the board.

The committee will essentially act as a mentor for prospective new members and help them understand what is expected of Gold Members. The hope is that this will result in applicants being better prepared than we've seen previously.

One concern expressed by Lauren Sell and others is that the committee shouldn't become a vetting committee. The committee doesn't have the mandate to turn away unsuitable candidates. If a candidate chooses to ignore the committee's advice and mentorship, they should still be able to have their application heard by the board even this ultimately means the application is likely to be received unfavourably by the board. This point was accepted and everyone was in agreement on the mandate for the committee.

The members of the committee will be Simon Anderson, Devin Carlen, Rob Hirschfeld, Joseph George, Sean Roberts and Nick Barcet.

Update from the Executive Director

Next, Jonathan gave the board a quick update.

Jonathan talked about his attending a number of OpenStack events internationally recently and how there is still tremendous opportunity to grow the OpenStack community and engage new people. He also talked about how he met with a number of significant OpenStack users and hopes to be able to use their stories to illustrate the truly global nature of the OpenStack user community.

He also talked about the success of the OpenStack Summit in Portland and how we had 2600 attendees compared to the 1300 attendees six months previously. Feedback on the summit has been overwhelmingly positive with the most common negative comments related to the Wi-Fi network and how some of the breakout sessions were massively over-subscribed. The Foundation will continue to invest significantly in networking infrastructure at the conference and there is work underway to restructure some of the room layouts at the upcoming Summit in Hong Kong based on the feedback from Portland.

Jonathan also talked about how our financials are in good shape. We had a surplus from the Portland Summit which will allow us to make the Hong Kong Summit a kick-ass event. The Foundation is also well advanced in completing its first audit and we expect to see fully audited financials for 2012 published in August. Apparently this will be a good milestone in our progress towards non-profit status.

Role of Core

After Jonathan's update, board members had an opportunity to briefly raise topics of interest.

First of those was Rob Hirschfeld who wants to bring together a group of board members to discuss the what "Core" project status means and should mean in future.

Rob talked about how he feels that the issue of whether core projects need a plugin architecture will be the key to unlocking the discussion and making progress.

Working With Standards Bodies

Randy Bias mentioned that he had been approached by someone from the IEEE who talked about the possibility of the IEEE working together with OpenStack on interoperability and standardization issues. Randy was mostly just passing on the message but also made the point that we can probably use the the experience of other bodies to help us ensure interoperability between OpenStack clouds.

Joshua McKenty quickly took a firm and contrary view to Randy's - that standardization bodies are typically pretty ineffective and would actually slow down our progress on OpenStack interoperability.

The discussion concluded with general agreement that while individuals are welcome to talk to and learn from whoever they wish as part of their efforts to help make progress on OpenStack interoperability. Josh also agreed to provide the board with an update on his work on refstack.

Meeting Summaries The final brief topic was a joy indeed. As [had already been discussed on the mailing list](http://lists.openstack.org/pipermail/foundation/2013-May/001419.html), Josh felt that [my previous meeting summary](http://blogs.gnome.org/markmc/2013/05/25/april-14th-openstack-foundation-board-meeting/) breached a policy agreed by the board (before my joining) that directors would make no public comment board meetings until after Jonathan had published an official summary of the meeting. Josh also felt that my reference to the agenda of the executive session had breached the confidentiality of the session. Jonathan and I repeated the point that Jonathan had not gotten around to doing an official summary in a reasonable time and explicitly given me the go-ahead to post my summary. In some follow-up emails, I also made the point that - in this case - we actually made no effort to keep the agenda of the executive session private during the public part of the meeting so it was completely appropriate to mention it in my summary.