 So, thanks everyone for being here. I know I'm the last thing on the conference schedule. So, if you're here, I'm super grateful just for that reason. And I'm David Duncan. I'm a member of the working group, and my day job is I work at Amazon as a partner solutions architect on operating system distributions and cloud-native solutions. So, we made it to Cloud Edition again this year, and for the F37 release, we will be in an edition, and that means that there are a lot of things that have to be done. So, I'm super excited. Thank you, Marie. Yes, also on the MindShare Committee. And that features quite a bit into where I'm going with this as well. So, it isn't just about what we do with the distribution itself, right? We have team initiatives, but we also have a responsibility for team interaction. So, we have a responsibility to infrastructure. We have a lot of bugs. We have requirements for security, just like any other part of the footer group. With MindShare, we have a lot of community outreach that needs to be done. We have a lot of marketing content to produce. We have ambassadors to enable. And then, last on this list, and somehow underneath the footer, is the QA team, and that's super fitting because, of course, nobody remembers to do the absolute best job with QA. And QA is critical to everything that we do. So, I just want to point out that we really could use your help, your time, and your guidance on what the right way to handle QA for the cloud instances is and what we can do to keep that moving forward and continue to have momentum there. But we want more momentum around marketing and the community blog and solutions that involve the things that you're already working on. So, if you're out there and you're wondering what you can do to help cloud, the biggest thing you can do is just use it as a foundation for what you're doing in the work that you're doing right now. So, we have some team initiatives, some of the things that we're working on. We're working on moving our image publication away from Image Factory, and we're also, we're moving it towards MASH and we're moving the build process to Kiwi. And you may wonder why we're doing that over some of the things that are more common, OS build in particular. And one of the reasons for that is because we are using ButterFS as our foundation, our file system. And with ButterFS as a file system, we don't have proper support in OS build. If that becomes functional, we'll look at what we need to do to integrate there as well. We wanna move our documents from the Wiki to FedorDocs. We think that that's, I mean, there's a momentum there for all of us. So, we wanna make sure that what we're doing is consistent with what everyone else is doing. And we think that, I mean, just generally, it's a better fit, easier to discover, easier to use. But we need more documentation and I'll get into a little bit more from there. So, we're also working on including 35 and up into the Azure community. So, we're working on building out the images and then the upload process will be included through MASH on to the Azure community. I hope most of you or many of you got an opportunity to see the conversation yesterday around the Azure community and there are the community marketplace, I mean, pretty exciting stuff. So, a lot of people think that what we're working on is just the cloud-based addition, right? And we really think that that's true. We do strive to continue to bring the cloud-based image to the community, but we don't think that it stops there, right? I mean, the cloud-based image is just sort of foundational to what it is that we think that we're developing here and we're working on ensuring. One of those things is platform strategy and I'll get into that a little bit more. But a lot of the public clouds have their own configurations, their own requirements for how the communications with the metadata occurs and how the communications with applications that use specific APIs is handled inside of the OS. And while we do still insist on the strictest open-source standards, right, just the same way as we would with anything, there is some flexibility that's necessary and a lot of that ends up being something that we take on as a group. That also includes packaging strategy and strategy for how we're going to handle the agent publication, the management of the tool kits, so the SDKs and all of the component parts that we think are things that just generally cloud users want to have fully functional with kind of a dial tone service. And then a framework strategy. So we wanna make sure that this is important for all of our users. So anyone who's using Fedora as a foundation for applications built on Django or WordPress or whatever, we wanna make sure that strategically we have this alignment with what they're doing and make sure that we can support the efforts that they have and maintain, especially because we feel like this is the first place they have, we want this to be the first place that they go when they decide they want to experiment or determine what it is that they do next. And then vagrant solutions, we're still supporting the vagrant solutions. We need more help with VirtualBox and VirtualBox testing. So if you're a VirtualBox user, we'd love to hear from you. And if you're using Arch64, the vagrant solutions on Arch64 are starting to be something that we wanna keep or we want to accelerate availability for and then there is some discussion around resurrecting the AWS or Amazon provider. And we're looking into making sure that we can do that. And then we wanna continue to build out support for solutions, we want to, one of the first things that I've been working on around that is trying to make sure that I can, trying to create a neural fedora cloud image so that we have a cloud image that is ready for, ready for GPU use for bigger jobs. And that's just a prototype. We've looked at that and we think that it could be a very good container-based solution and that a container-based solution would service both the requirements of the standard cloud image and also the fedora core OS images. So we can do both at the same time. So we wanna make sure that we have as much overlap there as we possibly can. And then we also wanna make some instances that can be integrated with cloud IDEs, the one that I was looking at specifically was cloud nine. Cloud nine on Amazon comes with the ability to leverage Ubuntu and Amazon Linux out of the box. But then there's nothing stopping us from being able to create an image that is effectively fully functional in fedora. I'm gonna stop just for a second and look at what's going on over here. So we're obviously building and deploying images. We want this, the integration of MASH with Koji. And the reason we want that obviously is because we wanna be able to handle a push to all of the standard cloud providers. And MASH already does that out of the box. So we don't have to redevelop any kind of, any of the work that's being done to provide these images or push the images into the various marketplaces and also into private clouds as well. And we have some policy-based requirements around the modifications that we're doing and we're trying to keep track of those and ensure that they're happening in a way that is consistent with the expectations of the council and the engineering committee. That's probably going to get thicker where there's a lot of things that people wanna do inside of cloud environments that if we were to do those on-premises, we would consider them to be some sort of a man in the middle attack or not suitable for the way that we would expect to leverage a base image. So our Fedora cloud base image doesn't include any of those refinements, but then we have very specific instances that do. So when you look at the Fedora cloud base, you'll see there's two architectures that we're producing in the environment that we have and then our friends at Red Hat are producing one for the S390. So we try to support them as much as possible. And then just like I was saying, we were trying to create these customized cloud images and then maintain that the policy exceptions for each one of them so that people can know that there are specific requirements for each one of the images here. So Google has a guest agent and similarly Azure has a VM agent and those are being used in the GCP image and then now our new Fedora for Azure image and that Azure image is coming any day. We're working hard to make sure that that happens. But there's going to be more and we expect there would be many more just because we start to see a few more purpose built configurations or configurations that are meant to achieve specific types of solutions. So ones that are being used with BDI or leveraged for, like I said, the IDE or something of that nature. And we want to make sure that those are tied back into our development process and also there's a good catalog of what's included. So we know when and exactly why to include those in say security events or in package update requirements or any kind of escalation that's necessary for making sure that we have what we need where everybody has what they need. One of the things that we've been discussing lately and Major Hayden has been good enough to help us start on is package dashboard integration. So I think all of us are really enjoying the integration, the package dashboard as packages. And it gives us a place where we can get sort of a general look at the package health in our meetings. And when we're discussing what we need to do next. So it really does help us to accelerate our understanding of what needs to happen in our own working group but then also in the upstream and then gives us time and initiatives to talk about in terms of automation and shared practice. Some of the ones that we've been looking at are the AWS CLI v2, which is we're working on right now. And we'd like to invite some of the package maintainers who are working on agents themselves to manage and maintain those in the context of the Clouds, the Cloud Edition working group. And then some others, highly specialized agents like the hibernate agent, which is beneficial when you're creating workloads that can benefit from hibernation and power management in the Cloud. So like I said, we need a lot of help when it comes to the Food or QA and release readiness. Simantro has been heaven sent in many ways for us. And Adam has been fantastic for giving us guidance where we needed it. But that doesn't help us to get more results and higher confidence scores from them. And as a QA team, that takes good test plans and some earlier availability for the images so that those images can be tested with ease and not with complicated upload requirements for the people who are doing the testing. And we're looking forward to our Cloud test days for the F37 planning coming up here pretty soon. We're gonna work with Simantro to get those on the schedule. So we also need to work with the marketing and enablement team or marketing team and focus some of our efforts around enablement. The Cloud Edition has maintained a popularity and as you may remember from the notes that were provided by Matthew in his talk, we've had some higher popularity for older versions and we're trying to nip that in the bud and make sure that we can do that. I think we also need to build more about our FS knowledge in the community because there are a lot of things that we can do. Just there's a lot of versatility in the base image that's exposed there and provides for a lot of flexibility in the way that we use our Cloud images. So I'd like that to be detailed and outlined more and to have some better profiling done so we have really good ideas of where it is that we need to improve and we need blog posts. If you've got a solution that's based around Cloud images or you've got a unique way of working with them or you think there's something that's underutilized, we'd certainly love to see content that was related to that and look forward to talking to you about it if you have ideas and we need better getting started documentation. We don't have really any good getting started documentation on the Cloud Edition and so we feel like that's something that would be super beneficial and we just wanna focus on ease of operation and ease of use and the ability to leverage this and the solutions that you have already in place. And with that I'll take questions and tell you again that I'm super grateful that you came and we're a part of this last final session. And thanks Isabella, I'm super glad to hear that the marketing team is happy to help. We wanna create some content, make sure that we're taking care of that. I think that's an important part of what we as a team can do is to provide you with that enablement. And thanks Neil for the links. I do have a link for the presentation. I just published it, but I'll happily send it over to you Isabella. So Alexandra, I think where can one read more about the build system improvements, the MASH and whatnot. There's a few bugs that are out there. There's an issue that are two specific issues but then I think most of this has been discussed in the notes or in our meetings and there was some discussion on why we had the plans to use the MASH and why we plan to use Kiwi as a result of that. And then Neil, what's the most pie in the sky thing? The pie in the sky thing for me is to create the same kind of popularity that I see in the public clouds for solution-based alternatives to in tools. As I'd love to see Fedora fit into that because our roadmap for the cloud images is predictable and consistent enough and dependable enough that the cloud providers are excited to put it on that list and we're keeping the consistency that they need in their tools. So that's my pie in the sky. Goal is for them to see this with the same kind of seriousness and support that they see for other ones. Oh, thanks for that link Neil, both of them. And yeah, Alexandra, I think that's a great idea. I think we definitely need to see more write-ups, more content that helps us to understand why we're making the decisions that we're making. Any other questions? If not, I'll give you a minute to get ready. Thanks Isabella, thanks everyone. Thanks for being here. Oh, one more slide to leave you with which is all of the things, all the places that you can find us.