 Anyone have anything else? Can you guys hear me? Am I am I loud enough in the back? Are there any other interruptions before I continue? Ian, I'm glad you asked that Ian. Let's get to it. Hi everybody. So I've got to talk basically about what is Red Hat what and first we're going to go into What is Red Hat about? I think most of us know but it's not a given You know, there's new faces around so I'll just kind of go into what Red Hat is and what we're doing I'm going to talk about what has changed over the last decade or so since I've been involved and Then I'm going to get into some of the changes that are happening in Fedora and why we're doing them It's the basic what had got us here won't get us their talk And then I'll talk a bit more at the end about some of the stuff that hasn't changed because some are core beliefs that we're Still working together on and then there'll be some time at the end for questions and answers Now for those of you that don't know me I joined Fedor around 2005 ish. It was around Fedor core for This is actually a picture from the very first flood con. I went to in Boston. That is me in the back just barely I think my hairline is a little bit bigger now, but not too bad and From there I went on to be a founding member of OpenShift So it's a project that's very near and dear to my heart and I joined back to the platform engineering group at Red Hat at least Which is the team in charge of building things like rel and Fedora And now I'm here with you So what what is Red Hat all about what are we up to if you actually go to Our website our company website and go to red hat comm slash e n slash about slash company You can look at this page for yourself. This is a copy and paste from the page And in it we have we are red hat along with our mission Which is our mission is to be the catalyst and communities of customers contributors partners or and partners creating better technology the open-source way and For those of you that have been paying attention This week at flock you know set flock is a very special event for us because so much of our mission comes together in these rooms in Orleans and Cape Cod and here in the the grand room and I think that's one reason why a so many red headers come because we you know, we're very involved in this But you know in terms of you know creating our mission. There's really no better way to do it than in here with all of you To you know figure out how to make the future So what has changed in the last ten years or so since I've been a part of things Well in the early 2000s around the time that I got involved Red Hat and Fedora were kind of simple I think if you go back in time and asked the 2005 me how simple the community was back then I'd say it's pretty complicated But the fact is it was if you wanted to get involved you got involved in Fedora Somehow that became a red hat product. I don't know. There's a bit of a tug of war But generally it was that was that was your options now it's a bit different, you know, we've got 2006 came J Boss and so then you could be a J Boss gap you wonder if it or again There actually wasn't a whole lot of overlap between those communities, but there was some it was fine If you look forward to today is quite a bit more complicated. We sponsor many projects These are just the things that go directly into some of our products And I'm sure that we have people contributing to many of these projects But if you go through and read these not all but a lot of these come together and touch Fedora in some way either via being packaged in Fedora as part of our release or some of them are being run in the Fedora infrastructure and You know, it's it's complicated and certainly, you know, certainly it's nice to see atomic up there Which is a very forefront project of a red hat We had many atomic talks at flock this year And if you go look at the the full ecosystem of things I actually had started to create a slide including all of these sub projects as well OS tree flat pack Like and eat and that's just a lot of things that are very red hat sponsored If you get into some of the outer ecosystem things of just projects that we contribute to like Moby or the links Colonel I very quickly realized that I did not have enough time to put that slide together And even if I did it would not make any sense. It would be a cluttered mess about a million projects Which is just absolutely insane to think about And so this is kind of the environment that we're working in there We have all of these different projects many of them came from different backgrounds. Some of them came from acquisition some of them came from inside of red hat and Now we as a company are trying to figure out how to make these things work together And we're hoping that the communities involved are also trying to make them work together And so we love to hear about people that are able to cross different communities That have common access to these different communities Because I think over the next several years better integrating and making sure all of these different things work together is going to be very important and That as it turns out you know integrating different technologies into a cohesive deliverable Is something that Fedora is very good at so you know the people in this room are in a very prime spot to make a difference there But what got us here won't get us there and so You know even with our successes what we've built in the past is kind of starting to show its age And so at a very highest level I know you know this gets very visceral to those of us that are actually trying to make this stuff work But at the higher level, you know, there's kind of kind of complaints around making changes And that's not just to Fedora itself, but to the infrastructure certainly we've learned a lot in the modularity process Just trying to get things going Trying to make the changes across several different teams and several different technologies It takes a lot of work And then once you have those changes, it's really hard to communicate them We have the mailing lists which you know, they serve a purpose But it's it's that's hardly like one-on-one training for the hundreds of people that contribute to Fedora on a regular basis And then you have the problem of what our users want Some people want the stuff we have to go even faster than it is some people want it to go slower Some people want some of the things to go faster and some of the things to go slower I guess some people want some of the things to go slower and the other things to go faster And then even more than that we have these developers that are now coming in and I know that we are developers here many of us But the the opinions and the power that developers have going forward is different than what it has been in the past And certainly Red Hat has noticed that and is trying to to make changes to it And that includes things like developers being given large budgets to purchase software That's just something that didn't happen in the past. It used to be the operators that controlled pretty much all of that along with their CIOs and things And so as Matt said in the first day, you know, we've got to light some things on fire And that's kind of what we're up to right now And by the way, if you do a if you're trying to do a creative comment search for a fire tornado There's actually a lot of options to choose from Which is amazing and this one I liked in particular because there's there's someone there He's you can see him here off to the left a little bit Amazed at the fire tornado which is many times his size, but he doesn't look like he's he's scared or anything He's you know, he's taken it cool And it's mostly protected. I think that's what we're trying to do with this change With all of the changes that are going on right now We're trying to do, you know a controlled burn of things making sure making sure that stuff is working But we also know that tearing things down is hard And I know that for a lot of people in this room and myself included there are certain aspects of this that are very Uncomfortable because we know how things do work today. It's hard to see how they're going to work in the future It's very hard to see how this stuff is all going to come together to get Especially something like foot or 27 out which as far as I know as of today We still anybody know if we have a successful compose yet a foot or 27 and we didn't have an alpha this time So yes, you know, maybe a little bit of that fire tornado is wicking out at the top of the tree branches And so we've got a you know and and and it's fine. I think that the important thing is We wish yeah, we didn't know that we thought the tree would be much taller and by the time we got done And by the point is like I think the people that are going in and making these changes I think we you know, we're just keep in mind that we're all trying to do our best both in the community and at Red Hat and If you if you have a problem bring it up and try to show up and help because you know certainly manpower is a big part of this and The stuff is hard if this was easy it probably wouldn't be worth doing or everybody would be doing it already And so because the stuff is hard sometimes we'll we'll slip along the way But now does seem to be a very good time to get some of these changes in So let's just dive in a little bit to some some of the very key things that are going on right now One of them is atomic and so if you've noticed there's been several atomic talks That I've got I'm just very curious to show of hands who here is actually just tried atomic on their lives laptop or workstation in a In a VM anything which is a lot of you. I mean I think that's very good and Atomic has done many things for us one of which is you know Obviously, it's a container optimized operating system if you haven't been paying attention as it turns out wink wink nudge nudge Containers pretty important to Red Hat. That's something that we're spending some money on So and atomic as the operating system is what we want to be the the best possible solution for containers and As part of that Atomic as you know has this very small set of packages compared to the the whole of fedora And that has allowed us to really focus on some of the core things You have the kernel and Austria and all the g-libs and all the things that go into that smaller operating system And I think that what we're really trying to do is use that as a launching pad for many of our other technologies And so one of the big parts of that is this faster-moving CI workflow that we have we have As many that do pay attention we release atomic host roughly every two weeks right now Which is actually pretty amazing inside of Red Hat It seems like magic to many of the people because you know in rel we're used to releasing that Most every six weeks with minor updates and atomic gets quite a few sometimes And so we're really trying to integrate that CI stuff to bring atomic into a fully automated Workflow that is tested to bring that CI into a situation that we can actually trust and That's a really hard thing to do As anybody that's tried it knows In the meantime, we pretty much have dusty and some of the other people Doing heroics to make sure that atomic gets out every two weeks and there's no real reason for that Like you know it really should be automated, but it's a really hard task So and then on the container side when containers came about several years ago You know with open ship we'd started with gears, which was a very container like technology It was based on se linux We have as it turns out we have a lot of internal expertise on se linux We have a lot of internal expertise sitting in row four over there and But as it turns out the industry did not did not widely adopt Gears as the container technology they picked Docker and so we very quickly shifted to adopting Docker and being able to use all of those images that are out on Docker hub and Very quickly found that Docker did not I guess just as before like making changes is a very important part of the thing that you invest in And making changes to Docker has been very hard You know that the Docker as a company has very specific needs that they're trying to address and sometimes their needs are different than ours and When it comes time to pick, you know, which one gets chosen that pick their needs over ours and that's a very hard thing for us to deal with and customers and so we've been investing in several other technologies like cryo and So now we have multiple different container technologies. We're trying to maintain both in fedora and in the community and On top of that we have other technologies like flatback, which is You know trying to to build these containers into an OCI type model But for workstation uses which is not something that I think anybody was really thinking about when Docker first came out You know the workflow for Docker had always been for developers to get their enterprise software packaged and pushed out into servers And there's a lot of there's a lot of really good benefit to that There's a lot of great lines of delineation between operations and developers in terms of what they can be responsible for but it also makes a lot of sense in the desktop use case as well and so you know, that is another one of those things that pushes some of the technologies that we're talking about to the limits and For those of you are interested in it, you know fly packet something I would encourage you to go check out and get involved in So I'd mentioned CI and I think I don't know if Steph is here step step around the church of step There's step so he's currently leading a lot of our vision and thoughts around What to do with CI and we have a lot of people in the room in red hat and in the issue Who's UCI who have UCI and kind of really understand where we're going with it? We have just as many people that really don't understand CI or at least don't see it as anything other than automating processes And it is that But it's also about changing your workflow and basically trusting the bots Being able to trust this tool chain is just as important as actually implementing it and having it work If it breaks all the time, you're not going to trust it and you're going to continue to bypass it And on the CI front, we're really trying to push forward With the ability to make changes to Fedora you can make changes to your packages And make sure that you don't break other people's packages And the whole goal of this isn't to find that out after we already ship it or after some customer puts that magic combination of packages together for the very first time and Manages to see something break or worse The goal of this is to make sure that the the the changes that you make or the breakages that you may introduce Get caught before they actually make it into the full system. You want that as close to the commit time as possible Which is just a concept that we had never had in Fedora before and so We have the CI workflow we're working on is now very heavily integrating with the factory 2.0 work that we have Because all this stuff is hard and Fedora's use cases I think are far more advanced than some some of the basic upstream use cases that we have and Trying to make all of this stuff come together is going to require a lot of effort And so, you know, I'm just as one project I think that is always looking for a community effort anything involving tests making sure those tests are up and running Anything involving the CI work that we're doing. That's definitely a great place to get involved and volunteer Because it's going to pay dividends over the next several years and I think it's going to make Fedora I think it's going to make Fedora much more stable and faster moving at the same time Within probably the next couple years and really looking forward to that The last up I have here is modularity, which is something that we've all been looking forward to I think that there's a lot of There's gonna be a lot of benefits modularity once it's in place But actually implementing that and getting it in place has been very challenging I think The I think you know, we'd all be more comfortable if it was a bit further along from where it is now But it's almost here and well, I guess it is here. You can actually go through and build modules I think that's still true today. It is and so, you know If if you think that you want to build a modular or you know, what's coming we have Langdon I'm sure is around here somewhere petters up here at front Go talk to them and figure out, you know, that we can send you to the right links and get things up And got links back there by Steph And so you can actually start building these things now. They're there. They're ready and you should start building them now We know that Fedora 27 is going to go out with some mix of modules and not but that shouldn't stop you from building whatever modules you want at this point and When you start getting involved with what modules do and then what you can do with modules The future is very interesting there not just for Fedora But the whole relationship between the Red Hat family of distros including Braille and Santos So what what are the things that don't change? first of all, you know Fedora means a foundation of Everything we do in Red Hat Red Hat supports Fedora because it's the foundation of rail and rel is the foundation of the company That's just how it is and unless something like opens, you know Just speaking numbers for a bit unless something like open stack or open ship Starts making the same level of money or any of the source of starts making that same level of revenue that rel Fedora is always going to be front and center and even when they do those things are also going to install on rail And it's just I'm just pointing out because it's very important to us and it makes sense that it's important to us It's just the reality of Red Hat As of right now, we have 35 full-time people working across release engineering IT and QE that number may actually be a little bit higher right now We have many many many part-time people that work, you know that span across both Fedora and rail It's often whenever a new invention or a new idea comes up from a customer sometimes or elsewhere We start coding on it and almost immediately the question a manager will ask or sometimes is why why don't you do this in Fedora? And so they head straight to Fedora and do it there As far as our sponsorship of it, you know, we had the rail booth out there We try to fund events like these and others as best as we can to bring all of us together Obviously, we also spend a great deal of money on the hardware infrastructure Red Hat, you know, as I mentioned earlier Fedora furthers our open-source mission. It's a pretty obvious thing, but it's worth repeating You know in terms of our mission the one that Red Hat has decided to follow You can do so much of it in Fedora, and it's a very healthy community to do it in Again Fedora benefits our products in very profound ways in terms of what's coming and you should definitely be For anybody that follows rail You should definitely be paying attention to Fedora because the rails of the future look just like the Fedora's of the past We also in terms of In terms of the communities that we would like to see and would like to build we'd love to see a community that Considered the status quo hurdle and not a goal Fedora is not the place to keep things the same And I think if you've gotten the impression that it is hopefully Flock and these presentations this week have have changed your opinion on that We also would love to see a constantly adapting and evolving community. Fedora's never done It just changes every time and we try to put these milestones along the way going forward But the fact is Fedora doesn't have an endpoint. It just keeps going and going and I think that that That journey that we're all on is very important I think that's also one of the main reasons why so many of us have been here for so long I'm actually just curious who here just a quick show hands or maybe just stand up How many of you have been involved with Fedora for more than five years more than ten It's astonishing. I mean, you know how how many I you know if I'm trying to think of other things I've been involved with for ten years. I mean, it's hard to think of anything else I don't even think my electric company lasted ten years And so it's it's really an amazing thing to to see so many people that have been dedicated to Fedora for so long How about yeah, how about less than one who's been here for less than one? Got one on the end there on the left. That's good. Welcome. Yeah Roughly nine and a half more years to go and then you'll hit the 10 year mark Also, we're hoping for positive constructive dialogue and feedback Which at least in my conversations with people and I think Matt you might agree with this too Just in my talking with you. It feels like we've had a lot of that here this year Which has been really good now this this photo did not come from the creative comment site So I guess I've got to get permission from Brennan Brennan. Can I use this? We're good. Okay. Just in case he said no, I do have an air dialogue for the most So I think you know what we really want is this continued participation and growth That we that we generally see and I think that's you know, that's really important to us So with that I'll say thank you and I've got just a little bit of time at the end for questions If someone has them I'll come by and repeat them or no questions. Everybody is very clear. Yes Dennis What's that? Ponies there's they were supposed to be a Wackenhamer's last night. Did they not show up? Okay, great. Well, and oh there's one back there. Go ahead. Do I have anything to say about what Red Hat wants from Apple? So, okay, I'll just I'll level with you Red Hat as it turns out is not just one shadow man guy with an opinion I think Red Hat's opinions on Apple are very nuanced There are certainly a lot of people myself included that really like Apple it has solved many of my needs in the past I have even seen People in internally a red hat, you know looking to Apple as a as a just a proper vehicle of the Red Hat family of Options because if there's a package that you want to get out if it doesn't go into rail where else can't go Well, we could put it into Apple. We see some of that now. I Think there are others to that view Apple is kind of a kind of confusing Maybe confusing to customers because we have this thing that works very well with with with rel and it's not always so clear You know, it's really you don't see a lot of Apple in the internal documentation and things So it's not, you know, it's kind of an official project, but it's not fully adopted and hugged In terms of its relationship with row. I think that's just kind of where it is right now I know I would love to see furthered investment and I guess dedication to Apple because I really think it's a great great project But today we just really haven't seen that and so it's there and existing and basically thriving in its own, right? As you can see from the from Matt's presentation of how it's going Okay, well with that enjoy the rest of flock and we'll see you around