 Hi everybody! Welcome to 35 Fedora releases in 30 minutes. The Fedora project turned 18 just last week so it seemed like a good time to go through our baby pictures, gawk at our awkward teenage years, and see the handsome young adult we've grown into, and also along the way reflect on what we've learned and could share from that. Normally I'd spend some time introducing myself, you know where I'm coming from, but you can find that on the internet because I have 84 slides and I tend to get through them all in time for questions. So stuff like the history of Red Hat Linux, the birth of rel, the short-lived Red Hat Linux project, that's somebody else's talk for another time. Here's the format. I'm going to not read the slides unless I get really nervous and start doing the back-sident. Some things of note, screenshot in the corner there. I'm listing the kernel version kind of as a reminder that we integrate a huge amount of upstream change that comes to us through no activity of the Fedora project ourselves. All this open source activity causes change to come to us and a lot of our work is integrating that. The events over there in the other column is basically our headline events. We actually have a whole bunch of other things that are Fedora events, Fedora Women's Day, Release Parties, Fedora Activity Day is called FADS. Those kind of things are going on, so this is just kind of our big headline events listed there. Most active on the develop list is mostly for fun there. Obviously, the most noisy person on the develop list isn't always the most productive, and as we've grown as a project, the develop list is less of a nexus for all activity anyway, so it's more for fun than like this is the winner or something, but I wanted to put some names up there and some like a way to do it. On the bottom, this is basically popularity of that release at its peak on methodology for that. Again, another talk, but basically you can judge the relative popularity of each one by that for this coming from our mirror network stats. So for the first five, we didn't have that, so we really have no good way to measure the popularity. So question marks for those. All right, here we go. Fedora Core 1. Flowers in a pond here. It's a nice quiet beginning. So Fedora Core 1 was really already in the works inside of Red Hat, and as far as I know, it was released with basically the same mechanisms that would have been used for making Red Hat Linux. I think the plan was for it to be Red Hat Linux 10. Honestly, I think it was more like a 9.1. It was just a pretty decent Red Hat Linux release that happened to have the name Fedora Core on it, and Fedora Extras was an add-on collection of the software that the external to Red Hat community could maintain and participate in. But a key thing happened shortly after the release. There's AMD64, 64-bit Intel architecture. It wasn't brand new, but it was still a high-end kind of systems thing, and Red Hat had been planning to reserve that as a differentiator for RAL. It was going to be one of the add-on value things. But a community member, Justin, went and at home rebuilt all of this stuff for 64-bit and made it available. Apparently, I wasn't there, but that caused a kind of crisis inside of Red Hat about what should be done with this, should we disavow it, whatever. But eventually they came to the decision, hey, if this is going to be a community thing, we got to empower the community. That actually was a little bit later released as an official Fedora Core one feature, which is very cool. Look at that tiny little Red Hat logo. Actually, a literal Red Hat, I find that very amusing. Next, Fedora Core 2. That's basically another fine release of what could have been Red Hat Linux. It looks pretty much the same. There's actually some important technical changes under the hood. There's a 2.6 kernel that was a big deal at the time. SE Linux is enabled. Oh, that's another talk. The big question here really is, what is this community stuff that people from Red Hat were talking about? What does it really mean here? The announcement, which wasn't really in the screenshot, I just put it over there for some where to put it as executive producer of the open source community, but didn't really feel like that. It was pretty clear that this director thing, Red Hat is the director, whether it's engineering, business, it was opaque from the outside, what exactly was going on there. It felt as an outside contributor at the time, like the Red Hat people were kind of acting overly optimistic about this community, rah, rah, rah stuff. And so Constantine, Mr. Icon, posted this thing, the famous IRC log. It's not really an IRC log. I don't know if it's even too small to read here. It's actually very long. Lots of people when I was prepping for this talk said you got to include that. So here's an excerpt of it. Basically, basically, it's some pretty incisive sarcasm about how it felt like from the outside. And you can find it and read it. And the LWN.net discussion comments on that are also actually really interesting. But behind the scenes, Red Hat folks were really trying. There was just kind of a lot of fear about this new REL model and worry that having Fedora succeed might undermine REL. We know now that that fear was unwarranted. Fedora's success is great for REL, but it took a while for that to happen. And so the first Fedora project leader, Michael Johnson, actually was talking to him and he was really discouraged by this. He actually left the project and Red Hat because he felt like he had failed the community. Michael's back around Fedora some now. He didn't fail. It just took a long time for it to be realized. Three. So the announcement for this one says the Fedora project and Red Hat would like to announce. So it's progress. It's not just Red Hat announces, but core was still really all Red Hat. But there's some stuff happening. The Fedora packages instead of actually being on the old Fedora.us separate server were actually now available from the same server, but they weren't built in a centralized build process. In fact, it was perfectly manual. It was send your spec file to set Fedora one of the early community contributors. But look how many packages there are. It's a four times growth in packages and that so people were people were getting involved in interest and stuff was happening. Just like quite what we wanted. Fedora Core four is the only time you repeated wallpaper. This release was the worst. It really it took forever to show up and you know we're still at community folks were waiting on Red Hat secret processes for it to happen. SC Linux is still a huge mess. Reviews at the time said that it clearly prioritized features over stability. And actually after that release it got worse. There was an update partway along that actually broke upgrading completely like you couldn't update your system anymore. It was just hot mess. But there was actually also a lot of great community stuff going on. We had our first Fedora conference, FUDCon Fedora user and developer conference little joke there in the name really brought us all together. I helped organize that at Boston University. So I'm really biased. But I think it was a huge success and particularly it didn't feel like it was Red Hat people coming to tell us what's what it felt like a collaborative thing where we could all work together and everybody who cared about it could actually be involved and do things. Yeah, there are lots of new packages and stuff going on. One of the really important things is we got kind of a real community governance with the thing called FESCO Fedora Engineering Steering Committee and crucially Torsten Lehmhaus who is the first chair of that committee that an example that's lived with us in Fedora ever since which is rather than looking for a majority vote and decisions, we look for consensus. Now, what is consensus is really a whole talk on its own, but it isn't that we have to get everybody to agree, but it's that everybody has a voice. Everybody who is invested in it feels like they're heard and they're willing to go forward with something for the sake of the community. And it's a really important process. That's how Fedora tries to work on all of our decision making. And this is the core of the whole open organization thing, the open source, open decision making process. All that came from the Fedora community and really had a big impact on how we do things in Fedora and on Red Hat. And I think culture at large in open source. I'm really fond of this background, the fancy new logo and the bubbles. They always felt like so designary to me. The big news in this release is Yum. Yum was a tool for managing RPM package dependencies, software updates, basically installing software without getting into RPM dependency hell. RPM hell was people called it at the time. So Red Hat internally had a thing they were working on up to date Red Hat network and they invested quite a lot in it. But Yum was just better. And so after again some soul searching, Red Hat admitted that and switched to having Yum be the default thing here. Another fun thing that happened is the Fedora core five released a broke the Red Hat corporate network and it was like end of quarter or something and nobody could get their work done. So that was fun. And Mike McGrath, who was community person actually head of Fedora infrastructure at the time working Fedora extra stuff and everything was quickly hired into the company and told to make sure that that never happened again. He's the VP of Linux engineering now at Red Hat. So I guess it worked worked out. And of course we have our now classic logo here. This was the Fedora brand, sorry, the Red Hat brand team came up with this and the slogan infinity freedom voice was something that that team invented. Yeah. There's a lot of community love for this next wallpaper too. So fancy with the 3D. So this release came out on my daughters, my second daughter's birthday. So I don't remember much about it personally. It's still taking way too long between releases. There's a whole story about the Fedora foundation. No time for details on that. But we had to find another way to make sure that there was real community governance. And so the Fedora board came out of that. It's before there was a thing called the advisory board but that was really just a mailing list where anybody could chip in and you know, advise it doesn't really a governance body and it didn't really mean anything. So now it's real. It had a mix of elected members and some appointed by the third project leader and the third project leader actually had a veto power that veto power has now was never used but it was always there as a thing. And look mirror manager system so we can actually get a count of installed systems that bar doesn't mean anything much by itself but you can see the relative values as we go. Okay, no more core. There's just one Fedora project that split core and extras are not to be causing more pain than it than it helped both for the obviously the people outside of red hat who couldn't contribute to core but also people inside of red hat was really, really frustrating. So they was a lot of work to do all of this and it turned out rather than giving external community members access to core, it turned out to be easier to just export all of core into extras. So actually really core was basically dissolved and Fedora extras, the community side thing became the one Fedora Linux. This was also the first release with live images tried before you buy Apple extra packages for enterprise Linux. Yes, that started at the flood con in Boston. And there's this new fancy file system we talked about that flood con and we kind of decided, well, maybe in a year or two, that'll be ready. Put a pin in that we'll come we'll come back to that. So the door seven brought core and extras together. But this is where it really started to feel like a community project. We introduced a features process for planning doing all the planning of what was going into it in the public. This release was really very popular. I know that there actually are at least 100 systems out there still checking in for Fedora eight updates in case we ever produce a security update for them. And also this idea for Fedora spins came out the idea that we don't just make one OS for everybody but rather tailor offerings for specific user needs that started here. And I think that is kind of essential to what makes Fedora special as a distro. The electronic lab was the first of these, but we have a whole bunch of them had a bunch over the years. Sulphur this release. Yeah, we had a lot of features. One of the key things here, the system five and it scripts and it scripts that, you know, get your system from kernel starts up to actually having other processes and running running a real running system. That old system was buggy, inconsistent, slow and not really well adapted to modern hardware. So at FUDCon, someone stood up and said, my name is Casey Dolan. I'm going to replace Fedora's init system. If you want to stop me, come to my talk. Casey was an internet red hat, but not in the operating system side of things. He was working at NIT. So really, he was just an enthusiast community member and he wanted to make things better and he did. So again, you know, community led improvements made real big changes. Now we get to the origin of the Fedora foundations. Remember the earlier Infinity Freedom voice slogan that came from the Red Hat brand team and it really felt especially to FPL, Max Vivek and put others that we needed to have something that really came from the community that resonated with the community. So there was a lot of work and came up with Freedom Friends features first, which we still use not just in marketing, but kind of to guide our decisions. Like these are the Fedora values in more than just a superficial corporate marketing kind of way. Also Trivia, Cambridge was going to be the codename for Red Hat Linux 10 before that was canceled. So it was fun for people to bring that back for Fedora 10. This was a special version of this wallpaper that was for if you had it spanning across two monitors and the lion only appears on the second monitor. So it's kind of an Easter egg. I never saw this in the time because I didn't have two monitors. But yeah. Around this time, Mo Duffy sketched these iconic graphics for the four foundations. We also still use those today and we looked at ButterFS and decided it might just a couple more years it would be ready for it to be the default file system. So I'm going to go kind of fast through the next few releases here. Here we had the first Budcon in South America. All in all, I remember this to be a pretty boring release, but in a nice way. Here we actually launched a beautiful new website. There was a marketing plan that kind of put together what a new nice website for Fedora would look like. Ironically, this screenshot I've chosen here shows the wiki rather than that. I'll fix this in the next version of this talk. An important thing happened is work started on copper, which is basically our repository for an easy to add to repository for packages that don't necessarily have the polish that go into the Fedora Linux itself, like PPAs or AUR, that kind of thing. Very dramatic wallpaper. Behind the scenes here, release engineering, Jesse Keating switched our build system over from CVS to DistGit, which is a Git repositories that also have a look aside cache for binary tar balls. There's a whole another talk about that too and how the future of that with the future that should look like. Anyway, look at the nice growth trend those bars along the bottom. They're going up and up and up. Really, things are going really well. And look, the wallpaper for this release is so lovely. This is going to be great, right? Oh, so goodbye to half of our users, not making that up. There's not enough time to discuss the actual virtues of these systems. But I think by this time, it's been clear that SystemD, GNOME 3, those are actually very popular and widely used across almost all Linux distributions. But and we worked really hard to try and manage this change. Actually, I went back and looked at some of the documentation from the time. We had video tutorials. It just wasn't enough. This was just too much change to dump on people all at the same time. So it's the right technical call, but not a good way to land it. We didn't manage it well. So this wallpaper reference to Jules Verne, of course, but I can't help but feel that the overall project feeling of navigating our way through murky depths kind of came out in the designers as they were making this. And so we're feeling a little depressed. Jared Smith, who is the Fedora project leader at the time, calls this our awkward teenage years. But there's actually really one important good thing that happened here. Up until this point, Red Hat required a CLA, a license agreement to contribute to Fedora. That was dropped in favor of a thing called FPCA, which is just basically guarantees that you have the rights to what you're working on and that it's under some open source license, so it's not a unilateral Red Hat advantage thing. It's a everybody benefits thing and are actually working on now figuring out how to make it so in some places we don't even require that. We just use explicit permissions and things lawyers are talking. We decided the Butterfests might need a couple more years. Next release, it can't all be murky depths, right? So the mustard indicates progress. Beefy here has been an unofficial mascot of Fedora for a long time and as you can see, fans were not afraid of bending the alleged process for arriving at a release name to make sure that they won here. So many people, when I talk to them, describe this as their favorite release and it was an awkward teenage years release. It wasn't necessarily a great technical release, but just that energy from this name kind of buoyed people and the positive connection, it just made people feel good about being in the Fedora community even when things were tough to have this kind of fun. So I understand why people really have fond memories of that time. On this wallpaper, those dots are actually spheres, their idealized spherical cows and some physics experiment. This release also kind of a mess. The installer code base had grown really horrible and it needed some fixing, but our feature process was just kind of aimed at each release and this was something that took more time than six months to do. We ended up slipping from our October target all the way around to January to even produce something that was functional and at the time, at almost the very last minute, we realized, oh, it doesn't even have a way to do upgrades. So Will Woods very quickly wrote a thing called FedUp, which is one of my favorite names of anything that does get upgrades in a different manner and actually turned out to be the start of a much-improved Fedora upgrade process, but it was kind of a painful way to get to that. We also had a lot of frustration with release engineering. One person had been doing a lot of the work and because of that, a lot of the knowledge and a lot of the access had fallen onto his shoulders and it wasn't his fault. It's kind of a natural thing to happen. He was doing a lot of heroic work and getting burned out and frustrated and people were frustrated with him. And yeah, that was hard and it actually took us a long time to figure out how to straighten that out. We've done it's a much better arrangement now, but yeah, we had to make some big structural changes to change that. Butterfests, again. This wallpaper, there are boxes for the cat to hide in, you see. So yeah, around this time frame, people were getting again pretty despairing about the path. All the up and downs were not good and there was rumors that there was some deal to bring CentOS into the company. What would that mean for Fedora? Were people intending to replace Fedora with CentOS? Pretty scary. But the biggest thing here was really this immense tragedy. That's Vidal, who I mentioned earlier, was killed when he was biking and by a hit and run driver and Seth was a giant in the Fedora community. He would have, he would have been, he's very humble and he would have downplayed that, but he really was not just in the technical things, but when he and I were both university assessments, he helped convince me that it was worth it, all of this work to give back and contribute into the community and act in the community. That was the benefits you got from that were worth it. And so Seth was just so important. He was kind, he was funny, he was brilliant, he was a dear friend and we miss him a lot. Wallpaper here, XX for 20. This one had so much going on, it couldn't fit it all in. I had a picture of myself with the 10 years of Fedora shirt that I'm wearing here. He decided to cut it. Those badges over there are not in the screenshot, but we got to the 10 year mark here and we decided we needed to do some strategic planning. We'd started out great at the beginning of the project, but we'd been in this kind of long slump. So what should we change so that the next five years would be better and so we'd be set up for the next 10 years of Fedora to be growth rather than going up down again. So the flock to a Fedora event was key here. The fudcons, which we've been having around the world, were not really working anymore. There was not enough of the right people all in the right place. People who are in South America, Asia, away from kind of the engineering nexuses are in Czech Republic and East Coast US kind of felt like they were left out of things. It didn't felt second class. So we had this idea to make a one global conference where we bring everybody to and do planning. And Robin Bertrand's idea and Ruth Sealy, Tom Cowley kind of made this happen. So this was a really good event where we did a lot of this planning. Fedora board at this time, it kind of faded into the background and really kind of only woke up when there was some sort of dispute about open source principles and hadn't otherwise didn't really weren't really involved in the day to day thing. So Fesco, which is the older body and Fedora anyways kind of kind of drove this strategic plan here. The Fedora rings thing still isn't quite realized, although I can see some of it actually in rel. But also this Fedora additions idea that instead of producing just those random Lego blocks, we're going to focus on making sure that we've got assembled Lego sets that people can start playing with right away. It's again goes back to that thing from eight with the spins. Like this is kind of a Fedora thing, but we wanted to really make sure those things were polished and really nice for users. So the excitement around this really like it took off. It clicked in the media and users and some of this, you know, GNOME 3 and SystemD had actually matured. Maybe they they were ready for the world at this point. But whatever the reason is this really was a very popular release. But also you notice it took 168 days to make that. That's not very long. That's way too short and our QA team was feeling pretty burned out by doing that. The release engineering, like you said, feeling even worse. And then as a project, we're asking for more polish on more things. So we decided to stop the presses and actually wait, skip a release, do a whole year to get ready for the next Fedora release things. So one year later, first of all, code names are fun. But as you kind of see from the process, they were getting very silly. And it was actually taking us a lot of lawyer time to find one that was approved and made sense and everything. So we decided to drop them. Josh Boyer says we can blame him for that. But really a lot of people were ready, ready to move on. So as part of this, we designed get Fedora as a user targeted brochure site. It was meant to go hand in hand with the thing called Fedora Hubs. The problem I felt at the time was that we had so much activity in the project. We had 1100 IRC meetings every year and a huge amount of IRC chat and then a lot of mailing list traffic. But mailing lists aren't really visible in the modern universe. And so Fedora Hubs was kind of going to basically surface all that as a Fedora contributor gateway. And for various reasons, probably also another talk that never launched. But we'll get back to some of those ideas later. I think 4,096 days since the project launched is a nice round number. 22. So I mentioned that the board didn't feel like it was really working. It wasn't just that they weren't active, but they didn't feel connected to the project. At Flock and Prague, we are talking about the additions plan, which some people were still skeptical of. And they didn't even know that the board had approved this plan. Like is this official what's going on? And in fact, we'd gone through quite a lot of work to get the board to approve it and nobody even really knew. So I came up with a new structure, which the board eventually unanimously approves Fedora Council designed to be a more active leadership and also to connect all the different various groups who I may map on the board of like 40 different committees and things in Fedora that really didn't talk to each other, kind of connect them onto an org chart. So active leadership and this body has a consensus model rather than a vote at all. And there's no more FPL veto. Like I said, it was never used. It wasn't really necessary. And with this model, we try to find consensus from everybody, not just approval of Red Hat. The Fedora Council also manages Fedora objectives designed to span multiple releases. And also we have this thing called the F cake, the Fedora Community Action and Impact Coordinator. That's basically what a community manager might be. Another project, but another talk. I hate the word community manager. Another talk. But former FPL Robin Bergeron really thought to get this role created so that the next FPL would not burn out so quickly and seems to be working so far. So to change things up a bit, the screenshots from KDE, KDE Plasma Desktop, our second most popular desktop environment. We got our first diversity and inclusion advisor, a long term time contributor from Latin America. I tried to get Red Hat to make this a fully funded paid role, but I couldn't make it happen. I still think it should be, but I wasn't going to let Red Hat not funding it block us from doing it in the project. If anybody else has some funding or anything they'd like to do, I'm talking about this. I'd like to make this happen. Other cool technical stuff for Fedora Atomic Host based on RPM OS Tree, a sort of get like approach to the operating system. And people kept asking for Fedora to be a rolling release or an LTS, one of those. And that's weird to me because those are so different on the spectrum of what you can do. But the commonality really to me is that upgrades are scary to people. So we decided to work on that fundamental problem and work on making upgrades really smooth, which is also has been very successful. This is the XFC, XFC spin. It's a marketing initiatives around this time there were kind of a minor success. Fedora loves Python, but this isn't funded by Red Hat. Red Hat does puts their marketing dollars into product, which is understandable. And so we've had some community people here with the expertise, but it tends to be kind of lonely. And so it's something that really kind of needs help. And also similarly, our docs team lead around this time, kind of the team had just naturally trickled down to one person and then he got a day job. And this is a case of someone doing so well. We took them for granted. I'm not really proud of that, but it's a lesson learned. We try to make sure that doesn't happen. We still do need help in the docs team here. So. Yeah, people really like this one. We got a lot of good press. It was encouraging to those of us who had been really feeling like we were you live through the teenage years. We were finally things are definitely on the up here like this huge jump. Green shots from the cinnamon in here. This one might be my favorite wallpaper. I like a lot of them, but I really love this one, not just because of the result here, which is beautiful, but the process, which was very community back and forth and built on it. That's actually a voice print of someone saying Fedora contrary to popular belief, it is not me. It was the designer Kyle who said that, but it's very cool. We got a new mission statement around this time and this mission statement basically we make an OS that runs a lot of places and we enable our community to make solutions for users is is really calling back to that thing from Fedora 8 with the making spins and making all these different kind of things. We make not make a bunch of building blocks, but we also make these preassembled sets. Modularity, how that went and is going in its own talk. It's really difficult to make things that span multiple releases, especially when they're big changes. We got MP3 support. Also, the trick was to wait out all the patents, so that's not really a great process. So the last release was eight months long again. We decided that this time we were not going to delay. We are going to make a very short release because otherwise it was going to be a very strong risk going around into January again. At this block, I was pretty despairing. It wasn't because of the short time. It was because modularity was pretty rough. Hey, look, squirrel, what's this over here in the other corner? This is sugar on a stick. This is the one laptop per child user interface still going strong, which is cool. Really, I will talk about modularity some other time. It's very interesting. But by twenty eight, I'm feeling a little more optimistic. Some of the modularity stuff landed. And this is actually the first time we ever released on time, according to our own plan. So we executed on our schedule. And actually, we've done that ever since. But this was that was nice. Part of the trick was we dropped having alpha releases and made sure that the rawhide development tree was up to the quality that we formally called alpha. We also had that same story about the docs team happening in our web team, a website team, where one person had kind of become essential. And, you know, it's not his fault. This is a prop, a project process fault where when he got another job, things kind of fell apart there. There's a happier story here because we now have a really nice websites and apps team that's very active and involved, but it took a while to get back around to that. This wallpaper is also amazing. Beginning of this year, we had surprised everybody by buying CoroS, the company. That deal was almost entirely about OpenShift and Kubernetes. And that meant where did the thing called CoroS container Linux briefly? Where would that land? I fought to make a home for that in Fedora. I think it's a great fit and it's going to be continued to be good going forward. I'm glad we were able to find a place for them. Fedora Silverblue is a desktop environment based on the same ideas as for the atomic host and now CoroS. In order to make a Fedora spin, like it doesn't have to be just a configuration of packages or trivial changes. You can make something that's kind of radically different. Yeah, another fine release looking at the clock. Let's move on. OK, here there's plenty of stuff, but the highlight is we Lenovo shipped laptops with Fedora Workstation pre-installed actually behind the lectern here. That's what I've got running right now. Availability out of the box is the number one blocker to widespread desktop Linux. And, you know, we're working to change that. The awesome thing I think is Lenovo came into us. They said our customers want Fedora running on our laptops. What can we do? And they really wanted to do everything the right way. This is an entirely open source Fedora operating system with no modifications from Lenovo. They're really awesome to work with. There have been some supply chain problems during the covid times, but we have some more awesome stuff coming up on this too. So covid times, since we couldn't do flock to Fedora, we had nest with Fedora instead. And I was really dreading this because I'm tired of virtual meetings already. And flock has always been an essential recharge for me getting together in person with people. So I was not happy about having to do this virtually, but it actually turned out to be awesome. We did a really good job. People came together, had a lot of fun, and it was really it's still the best virtual event. Sorry, this event, but best virtual event I've been to. I loved it and I really got that energizing spark from it again. So that was a lot. Thanks to Marie, who's our cake now, but also to the whole community. And also we looked at ButterFS and decided, OK, let's do it. And we did it. So there we go. After all this, all these slides. This is our nice covid wallpaper. There's also a nice evening version of it with fireflies kind of escaped the world relaxing wallpaper. This is the best release we've made so far until next month. Canom 40 is a big hit. It's also the first thing that has a lot of big change since Canom three. And this time you can own project and learn their lessons on that and did a huge amount of use or research going in and in short it paid off. I know some people prefer their workspaces going the other way, but most people like this has been a really good release. I mean, look, we've got a new logo. This continues from the other one, but modernizes the look and solve some technical problems and some other things with it. And I really like it as well. And finally here, the release parties. We did a virtual release party kind of focusing. Flock was very contributor focused and we kind of lost it. The user audience conference and the release parties online turned out to be a way of kind of talk and connect with new and potential for that for our users about about what we're doing and what's new and what's exciting. So we're going to keep doing those because that was a really big success. Note that the peak of the blue line hasn't been reached yet. That'll keep going up until Fedora 35 comes out. So we'll see how that goes. And this isn't the final wallpaper yet. It's the beta wallpaper. There's still some tweaks. But here we go. Screenshots from this laptop showing the GNOME 41 overview and beta release of this is tomorrow. So a little plug for that. The big question is, can we keep up the 182 days apart schedule? I think so. We're on track. We looked at the future a little bit here. We're working on some important things. I talked about the Fedora Hubs thing before. We're still trying to find ways to surface that activity. We're doing a website redesign. And as part of that, our new chat server, which is based on Matrix, is going to be kind of integrated into our new website design. And so that kind of all that active discussion will be part of our visible presence, basically. And it's not just tech. We've got a new Fedora Ambassadors program. We're really hoping to reach out and really grow the project over the next few years. We also have a program management team. This is that thing about trying not to burn out one person. Ben Cotton is our awesome program manager, but he wants to make sure that not everything falls on just him, which is good. And it also provides a team that can be a flywheel of sorts to other teams. They can help keep the process things going in the docs team, marketing websites and so on, without that becoming a burden to people as well. So that's a really nice thing that we made. So now we're caught up. Some quick distilled lessons here. You have to find a balance when you're making big changes. Docs are, you know, essential, but they're not enough. You've got to be able to explore things and you've got to, you know, be able to mess up and try new things and try different directions. Kind of the natural state of volunteer teams to drift apart and before that things to fall in one person. So Ben Cotton came up with this flywheel theory term. You don't need to make sure that someone is there to do all the things. You need to make sure that someone is there to keep those team processes flowing and to enable the community around that to do those things. That's the most important thing related to that on kind of an individual level. You got to make sure you take care of people in the project and watch when things are not going well. Letting go of control might be the hardest work to do. And you might ask, you know, if I let go of this, if I let make, let I go all in on real community, like a real community open source, how will I make money? Well, I think Red Hat and Fedora show that you can be very successful and even commercially and still also let let your open source project really thrives in open source project. And in doing that, you can make something that's awesome and goes beyond just the money as well. All right. And there we go. I'm going to stop and take a drink of water and take your questions. If anyone has them, do I continue to plan on being the Fedora, whatever my role is, Fedora Project Leader? I'm still enjoying it. And I feel like there's some things I set out to do when I started that are not done. You know, it just like the it can't all be one person forever. It shouldn't be me forever. But I feel like I'm having fun with it and doing a good job. So for the foreseeable future, I'm still in plus. I really want to do some Fedora travel. So let's get past COVID and let me travel the world again as Fedora Project Leader for sure. Even do one at a time so I can repeat the question. Yeah. So the question was, well, Adam Williamson returned to being the heaviest email list contributor. Yeah, if you've been watching that along the time, sometimes he was both the top first poster and the top reply person. Yeah. So I don't know. I think Adam is their QA team community monkey, as he describes himself, I think. And I think he probably will at some point, but we also need to make room for other people besides Adam to be the QA people we depend on for everything are part of that lesson. So yeah, so is Adam no longer being the top poster all the time indicative of a QA complication? I think that's indication of Adam getting a little bit older and a little more relaxed, but still a very prolific poster in all sorts of places and also a great wonderful person over. Yeah. The question is, is Fedora Project going to move to GitLab? It is uncertain exactly what we're going to do. We do have GitLab license available to us. There's part of the same thing that brought red hats using it and CentOS Stream is using GitLab. So I think right now a lot of the project is distributed across all sorts of Git forges. We've got stuff on our own pegger and we have a lot of things on GitHub and so on. And I think we are certainly going to at least make that GitLab that is available to us available for people to use. You know, I talked about going all in on open source. GitLab is an open core company and they don't provide all open source hosted version. And for a lot of people for the actual disk it of hosting the source packages themselves, it felt really important that that infrastructure be all open source as well. So we're still figuring out what that's going to look like. More questions? Really, there are some. Wow. Yeah. The comment was run the every release I've talked about on various systems, netbooks and think pads and so on. And the difficulties of trying to get vendors on board. So, yeah, really Lenovo has been a joy to work with. Yeah. Uh huh. Yeah. How can we convince people that it's worth ordering, waiting for and ordering the versions that come with Linux out of the box? You know, because it is only a restricted set of models and things, it's pretty, it's hard. You know, people need the systems that they want. But, you know, it really like, like I said, this came from people who cared about it asking Lenovo and saying we want this. So, you know, keep asking Lenovo and get your company to ask Lenovo or whoever else Dell, Aces, whoever all the other laptop manufacturers talk to them and tell them about your need. As for how can we convince users, you know, I don't know if we really need to lecture users into it, but just making people aware that this is really the easiest way. You want to system preset up. They are available to use. The best that I know. Sorry, I don't have magic for that one. David again. Yeah, well, I saw, I think I saw several of the times. I think again, right at the beginning, the 64 bit thing was was really huge. Then this, the core extras merge where core had been this thing that was developed under all red hat planning inside and then bringing that all out and saying, you know, anybody, anybody in the project, you don't have to be a redhead or you can actually be a committer to our kernel to libc to all these things. Like it doesn't your red hat dot com address doesn't matter, which things you have access to. So it's been just a lot of examples all throughout of that. All right, anything else? Thank you, everybody. You've been a lovely audience. Thank you, virtual audience. I'm sure you've also been a wonderful audience. I'm sorry, I can't hear from you, but. Thank you very much.