 Thanks for joining everyone. I think we're going to get started in just another minute or so. Good everyone's homes. I'm not showing much. I've been on meetings since 5 a.m. so you guys don't need to see my face. Awesome. I think we can go ahead and get started. Like I said, we'll be recording this so if you miss anything, if you'd like to follow up, please let me know. And I believe everyone's in my screen. Yep, awesome. During the meeting, if you have any questions that will be bouncing between speakers, but feel free to drop them in the chat or just interrupt whoever's talking and we can answer questions as we go. And of course, if there's any follow up questions, we can answer them afterwards. So I will go ahead and present. And first I'm going to go ahead and kick it off to Jonathan and Mark to just kick off the meeting and then we'll go ahead and start with the project updates. All right. Can you hear me okay Allison? Yeah. Great. Well, this is Mark, like probably all of you. I'm coming to you live from my home. So I just want to say thank you all for joining this community meeting. You know, we're all kind of dealing with a lot right now, a lot of change, a lot of people out there struggling with everything going on. But, you know, I believe very strongly in this community we've come together many times in when we face challenges and I think, you know, we're in a very challenging time right now with community members all over the world that are being impacted by what's going on. But I think we are able to work really well together as a community. You know, we have, we're very lucky I think in that as open source communities, we have been working together online remotely kind of for years, for the 10 years of OpenStack. We've, you know, we've worked together remotely all over the world and obviously we're in a position now where we're unfortunately not going to be able to get together in person, all of us in June for what we were planning to do for Vancouver and we'll be talking about the, how the event plans are changing and Erin and her team will go into that later. But I am really confident that we have the right community spirit and the right ability to kind of reach out and help each other and all the ways we have for 10 years in the OpenStack community and all the other communities within the OSF now and so just excited to be able to help each other whenever we can and I'll go ahead and turn it back. Back over to Erin to go through some of the, or I should say Allison to go through some of the updates this morning. So thank you all for joining. Thanks Mark. Yeah, so this morning we're going to kick off with the OpenStack Foundation project updates. Kick first with OpenStack and then we'll turn it over to the events team from the OpenStack Foundation. Just give us an update on all the different events that we're planning and how that impacts the broader community. So first I'm going to hand it over to Kendall Nelson for OpenStack. Hello everyone. So, as far as project updates go for OpenStack, we're currently developing the usury release. Our two main community goals that were selected were project specific contributor and PTL documentation and also dropping PI 27 support. I don't know if you have a text. I have a mail from the bekommen. Sorry, all of that. Maybe it was accidental on me. Keep going. Okay, okay. So, as far as the project specific contributor and PTL documentation goes we have until the end of the release to continue working on this, the actual details of implementation were decided a little later than we would have liked but there are a number of projects completed and more patches continue to go out day by day. So I'm confident that we can get this accomplished. Basically the goal is just that there are a lot of different aspects of how to contribute to a number of projects and there are a lot of common things but there are also a lot of project specific best practices and that sort of thing and we wanted to make sure that it was easier for contributors to get involved and in order to do that we need those details written down somewhere. So that's what that goal is all about. As for dropping PI 27 support. We obviously have been on Python three for a while and we don't need to support PI 27 anymore. So, at this point all of the open stack services have dropped PI 27 and the like current phase that is under development is working on updating all of the Tempest plugins to drop PI 27. There are a couple Python clients left that need to drop it and at that point we'll be able to start pushing required changes on the deployment projects. Though not all of those need everything implemented and some of them are already done so this goal should also be completed by the end of the release. Next week we have the final release for non client libraries next week is milestone three and that with that comes feature freeze. So, at that point, most of the new features that will be looking for in the upcoming release will be settled and we will start focusing on testing for the rest of the cycle. Also, we have the cycle highlight deadline next week so we should be able to start promoting the things that will be new shiny fun things with the next release. The last thing as far as project updates goes is we've been talking internally at least a little bit about a like cheers to the release since we won't be able to get together in June to celebrate it. So, at some point in the next week or two here I will send an email to the discuss mailing list to kind of brainstorm and plan that out. Another thing that's currently going on in community updates that I will touch on is the TC and PTL elections on Tuesday the nomination period closed, and we have candidates for all but 16 of the projects for PTL. So we have 16 projects that we are looking for a different solution, whether we decide that they will still have a candidate or maybe be turned into a SIG or something like that. If you're interested in that discussion, let me know and I can direct you to that. And as for the TC election we have, I think it's six candidates and we have five seats or seven candidates and five seats. I'd have to double check those numbers but at this point we're in a campaigning period for the next week and then next Tuesday is when we'll actually start polling for the election to find out who are new TC members will be. And that is all. Awesome. Yeah, so another community update so we are doing a runs on OpenStack campaign and you're around in like mid 2016 we kicked this off to just show the versatility of OpenStack and how many different industries it's worked on. So we're reviving this campaign and we definitely want to make it community wide. So one of the big pieces to where people can participate is taking the user survey. The TC actually just published a great series of findings from the questions that they asked in the user survey so we'll be putting that up on super user soon, but it really helps you know bridge that feedback gap between the operators and the developer. So if you or your customers or your internal teams are running OpenStack, please, please take the survey. You'll see many more emails from me about it probably, but we definitely appreciate you taking the time to do it as it does help guide some of the future releases. And with that we're also trying something new this time where you can submit your case study pretty easily or have your customers do it as well. It's a form staff that's like five or six questions. So it doesn't take too long and it's actually pretty easy to kind of cycle it through approvals that way as well. So if you'd like to submit your case study please reach out to me and we'll also be circulating that link with the recording as well. The next big thing is this is 2020. So it's the 10th anniversary for the OpenStack project. So we have been talking internally about some big ideas to celebrate the community's progress and the project's progress over the last decade. So we will be sharing more information probably in the next week on the OpenStack Discuss mailing list on how your company can get involved or how you as an individual can get involved. And last week, I think it was last week, it all kind of blends together now. Sunny shared a survey on the mailing list where you can talk about your top 10 favorite things or summit cities or things like that from the last 10 years. So if you've been around the community for a long time or even if you're new please take the survey it's really interesting to get everyone's different perspectives and kind of see how OpenStack has shaped their life from last 10 to last 10 years to maybe just the last year to And with that, I will pass it to Matt McEwen for the airship update. Hey, thank you very much. Hopefully you can all hear me. Ashley and I wanted to give you a quick status on what we've been up to an airship. The first thing is our airship to development, which is where the majority of our new development is happening on our two dot oh release. We've been really well. We are still finishing up our alpha milestone and plan to get that out the door this month and what our alpha milestone is going to be is going to be a an end to end demonstration of the sort of a provisioning workflow of, you know, from soup to nuts driven remotely by the the new clients for airship to But leaving out leaving out the workload deployment on top of it as part of that we've done a lot of good work in parallel on on the work workload deployment and life cycle management as well. But that will be wrapped up as part of the beta release, which will follow. We also had a meet up a couple of days ago. It was PTG style meet up and it was it logically took took the place of a face to face meet up that we were planning to have at coupon, which we did not. You know the pros and cons of that it would have been nice to see folks face to face but we did have some much higher participation, since it was a remote meeting. It was full day really good. It was one of the nice things about it is that a focus of airship to do is to make it smaller and to work with other communities that are that are working on similar things. So, many of the folks in the airship community have have sort of gone and focused on different projects other projects like customize and metal cubes and cluster API and things like that. And getting together for this gave us an opportunity to all kind of catch up on what we've all been working on and what the status of these different projects are in addition to the kind of the airship proper projects the airship based projects like airship cuddle and armada and the the new airship UI. So that was that was really good. It also featured updates from the airship working committee and technical committee and a feedback session at the end. So it was really good from a community standpoint as well. Next airship has added a formal vulnerability management process. This is largely inspired by open stacks. Well, well oiled vulnerability management process. And it has a small group of individuals who receive the security bugs that had been submitted. And then a, you know, process to remediate that and then release that we, we were lucky enough to have a trial run of our vulnerability management process already shortly after was introduced it turned out to be a false alarm so that was good. But it helped us, you know, make sure that in a in that false alarm context, all the gears returning. And then that's also a good segue because we've integrated that into our GitHub issues that we've been focusing on recently. We've adopted GitHub issues for our sort of story tracking type things and this was largely driven by the fact that, like I mentioned, we're collaborating with a lot of and driving work and contributing to a lot of other projects, most of which also use GitHub issues. So, keeping our scope in GitHub issues allows us to cross reference those really easily. Sort of that coupled with the fact that no one in the airship community in hindsight really fell in love with Jira. So this doesn't this doesn't change our, you know, where does our source code live and how do we do our, you know, our Garrett workflow, one bit, except that we are, we've introduced GitHub issues. We can commit tags into our commit messages and then those feed off of the the GitHub mirror that we have of our open dev repositories. And with that, I'll hand it off to Ashley. Thanks Matt. Yeah, so those are kind of the airship project updates and I wanted to just give a couple of notes around some major community updates on the airship side. So airship has its own slack workspace now, which is exciting. It mirrors to the same IRC channel that we've been using at a free note at airship it. And so it's the same content you can just use whichever platform you prefer now that makes working across communities a little bit easier for some people. So you can join that at airship it.org slash slack. And then we also have a user survey coming soon. And so some of you all might be familiar with the open stack user survey, and this will be very similar. We are currently brainstorming some ideas for specific questions that the airship community and the developers are interested in asking users as well as potential users so look for that that will be going around on the mailing list. We're basically looking for feedback and an etherpad at this point and then we'll be passing around sort of an alpha of the user survey soon. And with that I'll give it back to Allison. Awesome. Thanks Ashley. Thanks Matt. Next we're going to Cata containers and I'll pass it to Sunny. Awesome. Thank you Allison. Hi everyone this is Sunny from The Foundation. So for the Cata containers recent updates the community has just released the latest stable 1.9.6 and 1.10.2 releases. And the community just created 2.0 deaf branches in Cata containers CIM test repos as a basis of running Cata 2.0 feature development. And the development cycle will, the 2.0 development cycle will happen along the side with the next 1.12.0 release. And Cata containers 2.0 release involves some huge changes like repository consolidation, agent simplification, image pooling inside sandbox and so on. So the community has been discussing and working on how to plan things out on those. And I also include a link at the bottom bullet point I will also send you the chat in a little bit. All the 2.0 features are tracked by the GitHub project and you can find that in there. And for the community update last but not least if you are using Cata containers please take the Cata user survey and provide anonymous feedback to the community. And that's it. I'll hand back to Alison. Thanks Sunny. Next is Starling X from Ildiko. Hi, it's Ildiko also from the Foundation. I hope everyone can hear me and apologies I don't have my video on cameras freak me out. So, you know, I'm isolating. So as for the starting X update. For those of you who are a little less familiar with the project, it's a fully integrated open source platform optimized for edge and IOT use cases. The latest stable release is 3.0 and the community is being very actively working on the 4.0 release. The planned or target release date is during the second half of June. Currently we have the milestone 2 deadline happening this week. There are a couple of things that are already merged. So things like Cata container support, for example, is already available in starting X and will come out with the 4.0 release. The community is very actively focusing on items like stability and manageability security type of type of items and also looking into improving and increasing test coverage on all levels. So not just unit and functional testing but looking into sanity robustness testing as well. Hopefully in the future we will be able to do some performance testing as well as for the larger ongoing work items for the 4.0 release. The upgrade support when it comes to upgrading from 3.0 to 4.0 is something that the community is actively working on to finalize, especially with edge environment. It's really important to be able to go through smooth upgrades for the platform. So it's a high priority item for the community. There are also some, let's say, more exotic feature development activities ongoing like increasing FPGA support and adding some enhancements to the project. So they are looking into security related items like certificate management. So they are looking into further support and enhancements in that area as well. This project also has a user survey. We just have this trend ongoing right now. So the community would be really eager to learn from either of you or if you know anyone who is testing, evaluating the project, please look into the user survey. It's a really short one. So we really just would like to get an idea of what people are doing with the project or if anyone needs help, you can also mark that in the user survey. And I will reach out to you and see how I can help you getting started with either testing activities or getting involved in the community. And I believe that's all for starting Excel. Back to Allison. All right. And last but not least is Zool. So I think I'm passing this off to Clark. Yes. So hello, morning. I'm Clark. I'm one of the Zool maintainers. I also happened to be a foundation staff member. So, quite a bit has happened with Zool since last time you've had an update from us. One of the first things you might notice is that we've reorganized the documentation how it's laid out and organized. So that it's easier for you to find what you need. Specifically, we've created tutorials, how to guides, and then more in-depth reference documents, as well as higher level explanation docs. And the idea there is, you know, if you know you want to set up a Zool, you go straight to the how to guide. If you're trying to find some specific behavior in your Zool system, you go to the reference and so on. So the idea is to make it more approachable and kind of get right to what you need rather than needing to figure out the organization system that was there before. On top of that, we've done a lot of work around integrating with other systems, and that's kind of been the bulk of the rest of what you'll see here. On the Ansible side, if you're not familiar with how Zool executes its test jobs, it uses Ansible as an execution engine. And that means we integrate very tightly with Ansible. And what we've tried to do there is kind of follow and trail Ansible's release and support cycle. So as part of that, we've dropped support for Ansible 2.5, which was end of life by Ansible, I believe, in the middle of last year. But we've added support for Ansible 2.9, and we'll continue adding support for new releases of Ansible as they come out, and we'll drop off older releases kind of in a trailing fashion. The NodePool utility, which is part of the Zool project, manages test resources and we've added Google Cloud support to that system. That means you can run jobs inside a Google Cloud account now using Zool and NodePool. We've also added support for GitHub's checks feature. So if you're a GitHub user using Zool for CI, in the past, we would leave comments that look like typical normal users. So with the checks feature, what we get is kind of direct integration into the GitHub UI for CI results. So it looks cleaner and it's a little bit user friendly, especially if you're using other CI systems that are integrating in that way, you get all of your stuff in one place. And then we've also added some basic GitLab integration. So this is kind of early days. So what we're asking is that if you are interested in Zool and a GitLab user, definitely try it out, give us feedback, help us fix bugs. Many of the existing Zool maintainers are not GitLab users today, so this is a new project from us, or a new tool for us, and we're relying on the community to kind of help us build out this feature to make it as useful as possible. And I think it is now Jimmy's turn to talk about some community updates. Hi. Yes. Like everybody else, we've got a user survey. So we're tracking, we've got some pretty good Zool users in so far, but if you know anyone that is running Zool, please direct them towards the user survey. I'm putting the link in the chat. So thank you. Awesome. So before we move on to events, we had some other updates from the community. So the bare metal SIG is working on a white paper, as well as my ironic use cases, I think we have a new use case going up early next week on Super User from Red Hat and there's already a variety of them from both users and ecosystem companies that we published in the last year. So if you're running ironic, please share your case study. I will drop the link in the chat once I can access the chat. And Julia, I talked to Julia yesterday and so she's been posting updates on the OpenStack Discuss mailing list, as well as some meetings to get together and try and finish it. Since there's not anyone that's 100% working on it right now. So if you want to get involved or if you just want to be updated on the status of the white paper, stay tuned on the OpenStack Discuss mailing list. I believe she's using bare metal SIG and ironic as the times. And then for the edge computing white paper, I'll pass it to Ildeco. Thanks. So just briefly, there's a foundation level working group dealing with edge computing related topics we call it OSF edge computing group. The group already published a white paper, I think about two years ago, to basically set the base tone of what we are working on and just defining some terms that we are using. When it comes to talking, I'm talking about edge computing related items and infrastructure and platform type of services. So a couple of the working group members are working on a second white paper now, where we will focus on a few use cases in greater details, and the reference architecture work that the group has been doing. And we will also highlight some testing related aspects. Many of these items are also work items that the group participants are actively working on. So if you're interested in participating in any of these discussions, then please look up all the forums on the working group wiki. We have IRC channel weekly calls and the mailing list where you can get involved and reach out to the group. I'm hoping that we will be able to have the white paper out soon so you can also read what I just talked about. Back to Allison, thanks. Awesome. And the last piece is we wanted to cover some of the cross project marketing updates that we have been initiating over the last couple of weeks. So first I'll pass to Jimmy for SEO process update. So one of the things we're trying to do is raise the profile of all of our top level projects. And so part of that is simply being able to find it on search engines. So we've already started reaching out to each community with kind of general plan. We're working with an SEO company to help us identify keywords and other search targets. And I'll be sharing those goals with the community and then providing results of the work as the year goes on. Thanks. Back to you Allison. And then I sent out an email to all the different mailing lists last week but basically we really want to make sure that all the communities and projects know that the blogs and Super user are your channels as much as anything. So if you have ideas or even just project updates that you think would be a good fit for a project blog or Super user, please reach out. We definitely want them to be representative of the community and project progress. And that is very much what you all are doing and we want to hear more. So please reach out to any of these or to me directly if you have ideas or if you want to see if something is a good fit. I think that it would really benefit to hear from more more voices from the community on these different platforms so that newcomers can come in and kind of know where to go for information and who's working on the project. This is kind of connected to what Jimmy is doing. So we're going to be doing advertising campaigns to leverage some of that content that we're getting from the community. Based on some of the findings from the SEO work that he is doing so, especially with findings from the user survey as well as the articles that will be generating. I think there's going to be a lot more opportunity to create increased visibility for all the different projects. And before we move on to events I know we just covered a lot across a lot of different projects, and the chat has been really active, but I wanted to open up to see if anyone had questions for anyone who's presented or overall project progress questions before we jump into OSF events. Yeah, I have two items. One, I would like to definitely thank Matt for carrying forward the airship to close to beta alpha. So we met I would like to know if we can get the alpha release by end of April. Is that a possibility. Sorry, could you repeat that for gosh. Could you hear me properly can you hear me. Yes. I was asked I asked congratulating airship Matt for doing a good job. I would like to check if we can get the alpha release of airship 2.0 by April. He said by April 8th. Matt dropped, but the most recent thing that I have talked to him about is that their goal is in the next two to three weeks, pretty much as soon as possible but they don't have a specific set deadline but I, I would probably expect it yes by the end of April. I am attending that we had some 10 to tell items to clear to do. So if you needed any resources that's what I was trying to figure out to make sure that the close alpha early because then beta will take another six months so to ensure that we meet November deadline for open stack. That was the target. I was trying to cheat. Okay, I'll talk to him separately. We're second topic. Of course, all of these good ones even zoom one I was impressed, especially no pool stuff. But I'll look at it at a different time because I didn't follow up as I was doing parallel tasking with the TC. So what I want to bring to here is one link, let me put it, and this is related to interoperability. Interoperability working group has not met for whatever reasons I want to revive it so that something is on my mind as I speak here and there is a link here we have approved up to it. If I go to the link I think share which I have shared it shows that we have approvals for up to releases. Queen and but no implementation. So implementation the last one I see is only Carter. So if we do right now training train release if we can approve by of course going through a meeting set of meetings, deciding what set of APIs to include or exclude that should give us approximately timeframe to test it. It's already under test in the industry. So my question to all of you is, are there are there windows are there are fps which want to promote the logo, which is called as the open stack powered. One relates to the computer one relates to the storage one relates to the platform. So are there any asks from service providers to put a stamp of RF in the RFP saying that if you have something open stack driven so that we can go to the branding and who are all interested in this that something I wanted to conduct. Maybe I'll talk to Ashley to get that moving. We want to get a survey for that. To kind of just talk from an open stack perspective as someone who sits on the TC I think that's a good idea. I think we should drive that forward so I think what I can do is I can reach out to you, and we can start that discussion. In order to help figure out the approval of more of stack things so that we can pass that over the foundation stuff so they can do the marketing. So I can I can do that as an item with you, because you'd like This is Mohammed speaking with you. Mohammed. Mohammed. Oh, welcome. So yeah, we can take that as an action item to work on that together and I can help you drive that. I appreciate that. So, without spending more time there are there are past reviews has gone through the summits from Boston to us to the Sydney's and which I missed previously. And what I have is there is a lot of scope in it. But the first thing is we have to make sure that we are up to date by release T. If you can clear the literacy then we can talk about future, because other makes no sense. We are fighting the fire right now just to get T is the first. Yeah, that's perfect. I agree with you and I think that that's something that's initiative that we should move forward with and I'm happy to reach out to you. I appreciate I think we will talk offline but that is where we need to get a meeting and actually can help us out on bridges and whatever you need to get us. Thank you. Appreciate you. Awesome. Thanks Mohammed thanks for crash. So with that I'm going to pass it to Aaron from the foundation to kick off the OSF events update. Yeah, thanks Allison hi I'm Aaron Disney I run events for the foundation. It's definitely been an interesting time the last few weeks from an events perspective. Like Mark mentioned we announced a couple weeks ago that we are no longer going to physically host the Vancouver PTG and open dev as originally scheduled for June. Since that announcement we the team and I have been really focused on collecting feedback from various groups within the community. Just trying to make sure that we are thinking through all the impacts that this that this has and then gathering best practices from groups that have been doing virtual mid cycles and meetings. Kind of taking those learnings and working them all together to help ensure that we have a successful transition into this virtual gathering and still meet all of our collective goals. And the girls are going to go to Kendall and Ashley will go through both PTG and opened up specifically here in a second. But I just wanted to thank everyone who has already provided feedback and weighed in on the mailing list, shared ideas and then also joined the planning committees. If you haven't had a chance and you're interested. There's definitely still ways to get involved, but thank you to everyone that has helped so far. There's a lot to do and we do have a couple months to get it done but and we're thankful that we've been able to have that time compared to some of the other groups that have had to turn around virtual events in a matter of days or weeks so That's definitely worked out in our favor and I think the I think the best practices gathering is going to help us out a lot in the long run. So anyway, thank you for everyone's flexibility and creativity as we figure this out. And I will pass it off to I think Kendall is going first with PTG. Yes, thanks Aaron. Hi, says Kendall waters here I help plan the PTG is with Kendall Nelson and Terry and Aaron and actually never know the events team. So we are right now figuring out how we're going to make this virtual. Like Aaron said this is definitely something that's new, but we do have a lot of people in the community have who have successfully done these virtual mid cycles and other meetups so we are actually using the community to brainstorm best practices to make this successful and also just revisiting the goal of the event and key challenges that we are going to see we had our first meeting this morning which went really well. We had a few people join and then we have two more of these community brainstorms. And we'll have April 6 17 UTC and then also April 7 that to UTC and if you can join that would be great. If you are wanting to be a part of this brainstorm to make sure it's successful. If you have any questions feel free to email myself or PTG at opensack.org and back to you Aaron. I think Ashley is up with Open Dev. We can also share we've got an ether pad where some of those best practices are going. I can throw that in here too. Oh yeah that would be great. Yeah so people can follow along even if you aren't able to join the meetings and add ideas. So Ashley if you want to cover Open Dev. Yeah, hello this is Ashley again so similar to past Open Dev events. I don't know if all of you are familiar with it but in the past our goal with these events has been to really identify the questions within the tracks that we focus on that we don't have answers for yet and use kind of the time of the event to dive in and determine kind of the work ahead of us working together sharing use cases and learning from each other that you know my people that might be asking the same questions. So Open Dev is a little bit different than the summit style that most of you have been used to you know it's much more discussion based rather than being presentation heavy. So kind of as we move forward we have gathered some feedback from you know experience and advice from the programming committees from each of the tracks that we had been focusing on and we've made a couple decisions that will give us something to build on as well as you know give you all an update on the planning process and progress as we you know try to decide what you know the most effective format is that will be the most beneficial for the whole community. So with that kind of the three big building blocks that we have at this point are that Open Dev will happen virtually and after the virtual PTG you know like I said the exact format and timing is to be decided but it will happen after the PTG and there will not be simultaneous parallel or competing tracks and we think that that will be really beneficial because then you know the community will be able to dive into each of these topics and not have to worry about you know jumping between you know during the day like at an in-person event and have the opportunity to participate in more than one and then the three tracks that we're going to do are hardware automation, large-scale usage of open infrastructure software and containers in production and each of those will take place on a different date again still to be decided. So you know as we continue this process we would love to hear from you all because you know the spend is for you after all so there's an ether pot at the bottom I will drop it in the chat but we have put a couple questions into topics that we are interested in gathering feedback from you all and you know just based on your experience at other virtual events happening feel free to drop your thoughts in there we would love to hear from you so at this point I'll kind of you know open it up and see if anybody has any immediate thoughts or comments. Yeah on either OpenDev or PTG if anyone has any comments on those specific events. Yeah and I will drop the planning ether pot in the chat right now. I do have a comment. Can you hear me? So the three tracks which are there can we have an ether pad links those so that whatever hardware automation containers in production all those three can define something there or at least. Yeah absolutely so we we have an ether pad that I sent out a while ago but that you're right that's a great idea and I will recirculate that ether pad and it kind of has a. You can have existing interpad right now which is here planning the link to those three items there itself then it will be easy right rather than additional. Yes I can I can combine all those. Yeah if you do that then the other thing will be who are leading because there was some survey question previously who wants to lead what and people had applied for it. And if it is okay for those people who had applied to lead those friends to be able to manage them. Yeah so I think Prakash is talking about the so we had an application process where people could either apply to be on the programming committee or to be a moderator of a discussion. Or a or volunteer just a discussion topic that maybe they were interested in hearing about or hearing other people discuss. So yes so Prakash I know that you applied as a moderator and we would love to have you participate in that. So I think that there will definitely be areas for moderators to participate going forward. I think right now we're concentrating on the form factor. But yes we will definitely be looping in those volunteers going forward. Yeah because content is important and the order in which it is done and how we can maximize the availability of people across the globe. It's a bit of a challenge I understand so definitely fixing the format is first and bringing the content is second. I agree with you. Let's move one step at a time at least get one per week something at you because it's very difficult in this challenging climate to be able to drive and get the results. That's the key. Yes very agree. Awesome. So for the second half of the year we have the open infrastructure summit in PTG in October currently scheduled for October 18th through 19th through the 23rd in Berlin. We're continuing to evaluate the best way to host the event and are thinking through multiple options and approaches. Thankfully we have plenty of time on this one to figure it out. But as always we want to hear feedback and thoughts from all of you to help us make it successful. So yeah that is our our year of events. Does anyone have any additional comments questions. And if you think of stuff later on feel free to reach out our shared email address. You can reach us at summit at opensack.org or also feel free to reach out to me directly Aaron at opensack.org so awesome thanks. Awesome so I know we covered a lot of things this morning or evening wherever you may be based. So I wanted to share how you can get involved with all of these different areas and I know there have been a lot of links shared in the chat but I will share those on the mailing list afterwards in case you may have missed one or two. But if you have content please share it. We have a lot of different channels happy to discuss some brainstorms if people have some ideas out there. Like Aaron Ashley and Kendall said please join the virtual event planning groups. We can't do this without y'all and we want to make this as successful as possible as we go through this shift And get involved in the 10 years of open stack campaign. I put Sunny's email in here so she's been running point on this and gathering a lot of awesome testimonials so please share your experience and let us know how you're celebrating 10 years of open stack. And with that I want to pass it to Jonathan price to to share his thoughts at the end. Well I was just going to say and I'm kind of echoing some of the comments that I see in the chat which is thanks to everyone for for joining the meeting and especially to the presenters and also thank you to Allison for for organizing this and kicking it off we used to do These kind of community meetings more regularly and and just sort of fell by the wayside a little bit over the over the years as we took on more events and more activities in other areas and I think that, you know, kind of with the, the, the situation that that we're all in as a global community today. It's great to to revive these community meetings and you know here feedback. So thanks Allison for for doing that. It's a great time to get everybody together and you know the open stack foundation we exist to serve the community and we're here for all of you so You should always feel free to reach out to, to any of us. Give us your feedback, give us input, let us know if there are things that we can be helping with on any of the projects and, and you know we want to make sure that we're available to support support you and make sure that, you know, we, we continue to have a strong and healthy and active community so thanks everyone for for participating today. Thank you. Thank you all. Thank you. Thank you, everyone. Bye. Bye.