 Good morning, everyone. My name is Walt Minor. I'm the AGL Community Manager. I'm here to give a talk on the Automotive Grade Linux Roadmap and UCB Update, Unified Code Base Update. So my Twitter handle here is I'm at VSTARWALT. And my email address here is if you have any questions later, you can drop me an email at wminor at linuxfoundation.org. So who is this guy? Why is he talking to me? I've been a Linux Foundation employee for seven years. And in those seven years, I've been the Community Manager and Development Manager for Automotive Grade Linux that entire time. Previously, I was at Monavista and Mentor Graphics doing automotive Linux there. I started the open source review board and delivered some Linux products to Mercedes-Benz when I was at Continental. Prior to that, starting in 2005, I was working with Motorola mobile devices on the Linux Java phones that were done. Back in those days, I was the software architect manager of software architecture and systems engineering. And then prior to that, I was also at Motorola's telematics group working on automotive projects there. So I've got quite a few years of experience here, both at the Linux Foundation and then Linux in general. It's been almost two years of this COVID-19 pandemic. And so for those of you who know me, I've lived in Chicago until very recently. I moved to Asheville, North Carolina in July. Hopefully no more freezing Chicago winters. And I also enjoy riding my motorcycle. I've done quite a few motorcycle rides. This was a recent photo at the world's famous Tale of the Dragon, which is about an hour from my house here. So that's an introduction to who I am. Now let's talk about AGL and the unified code base. So AGL has been around since 2012. I joined AGL in 2014. And in 2016, we announced the first release of the unified code base, the AGL Unified Code Base. Up until then, we'd been releasing software, but building on top of Tizen IVI. And that was more or less abandoned. And our steering committee decided that we would create the unified code base from what was out there in Tizen IVI, in Geneva, in Yachto, open embedded, and whatever code AGL created to form this unified code base. And that first release was done in January of 2016. We showed some demos at CES. I think it was our first CES. And that release was the AGL Albuquerre release. So if you're familiar with our naming convention of naming our releases after Fish, we're now 12 major releases later. And we're still unifying, but now the best of open source. Because if you think about Tizen IVI, it doesn't exist anymore. Geneva doesn't exist anymore. They've reframed themselves as something else. But in really, open source has evolved quite a bit in the last seven years. System D, if you think about seven years ago, System D was in its infancy. There were still a lot of flame wars out there on the mailing lists about whether System D was going to be used by people. Oh, it's just overkill. Nobody needs it. Well, that's all gone away. System D is an accepted part of the Linux ecosystem now. Pipewire didn't exist. The web app manager, which we've gotten upstream from WebOS, they really hadn't open sourced their stuff at this. But at that point, Flutter didn't exist. Jenkins was around, obviously. And we've also since then built a lot of AGL services and AGL reference apps. Based on an AGL application framework that we created along the way. So 12 releases later, we're still doing this. We're still focusing on reducing fragmentation, focusing on innovation and new features, but also production readiness. We are now available in Toyota and Subaru vehicles in production. And we have an IVI expert group that is being led by Toyota and has production ready in its name. So that team is definitely focusing on making AGL available in the car of the future. So having said that, 2022 and 2021 and 2022, especially, will be a year of transformation for AGL. Like I said, we're continuing to look at what's out there in the open source community and the AGL steering committee, which meets about once a month, actively prioritizes what projects we're going to spend AGL funding on for development. And they came up earlier this year with this list of projects to prioritize. So high on the list or tops on the list was Flutter for the IVI expert group, virtualization, including Vert.io, and then creating a common device interface. We have reference hardware that's been designed by our reference hardware expert group and is available for purchase from Panasonic. But continuing to advance that reference hardware and continuing to advance the instrument cluster and making it more production ready, evolving our app framework to use more upstream components rather than AGL managing its own app for creating and maintaining its own app framework. So making more use of system D and changing our Linux security module, I'll talk about that in a second. Again, more IVI features and vehicle to cloud. It's coming. Vehicle to cloud is, as connectivity and 5G becoming ubiquitous, more and more vehicles will be connecting to the cloud on a regular basis. So working on our vehicle to cloud expert group has some demos in progress, and you'll see those in the next few days. And working on identity management and some telematics demos. So what's that transformation going to look like? So over the past six years, we have AGL has invested in software components that are not available anywhere else. That included an app framework. And with audio, at first, it included the AGL Advanced Audio Agent or 4A in order to meet some of the requirements that we had that were not being met by the existing audio packages that were out there. And so you can see here in green, this is the evolution. So this here, this column, is where we are today, where we were a year or two ago with Qt and 4A and SMAC for security using IVI shell for UI management and only having an IVI profile. Well, by the end of 2022, we'll have Flutter and Web Apps available, Reference Apps available. We already have some Reference Web Apps that are available. We'll be deprecating our AGL application framework making use of better and more upstream components like SystemD. We have deprecated our 4A and stopped maintaining that. And we're now using PipeWire. We have some great collaboration between the AGL community and the PipeWire community to try to drive those automotive-specific use cases into PipeWire. And now you see PipeWire being used not only in automotive, but also being shipped in Fedora as their default audio package. So it's making strides both in the embedded and in the desktop space. In the meantime, in the last two years, we were using SMAC for our security. Really, SMAC is fallen by the wayside, so we'll be moving to SC Linux and or App Armor for security. UI management, we're using IVI shell, which was created by Addit. Now we've created an AGL compositor that we've been maintaining for a few years that, again, it manages our AGL-specific use cases and is based on Weyland. We work closely with the Weyland community through Collabra to make sure that our features are maintained there and to make sure that what we're doing is in sync with that community. And we've expanded our profiles from just the initial IVI profile to IVI instrument cluster, telematics, and eventually ADAS. So 2022 will continue to evaluate open source technologies to find best in class for automotive use cases. And in particular, we'll be transitioning away, we'll be transitioning our AGL reference apps and away from service, are the existing service binders that we have in the AGL app framework to newer technologies. And where those technologies forced WebSock, it's on us on a one-sized fits all basis. In some cases, there's newer versions of IPCs available like GRPC that we'll make use of. And we'll be replacing our existing set of cute reference apps with Flutter and Web Apps as we go through 2023. So you'll see a great transformation and I'll detail that in the next few minutes over the course of 2022. So let's talk a little bit about release planning. Where do we stand? In 2021, we released the initial version of version 11, Kuki Koi and the initial version of Lucky Lamp Ray, which was 12.0. And we have started working on Magic Marlin, our next release, which will be released in early 2022. And through next year, you'll see us develop a nifty needlefish and release that in July as release 14 and then preparing for optimistic octopus in early 2023. Now, I put on here the Yachter project releases that we'll be using. So we've been using the Yachter project LTS version 3.1, also codenamed Dunfell for the last few years and they initially promised us, they initially promised two years of support. And we'll continue to support Dunfell. They will be extending that two years out to four years they announced, recently announced, but they will also be creating version 3.5, Kirkstone, which will be the new Yachter LTS being released in the spring of this year, of 2022. And what we'll be doing is moving from Dunfell to Kirkstone in the needlefish release in time for July. And then basically continuing to use that on our master branch for the next few years. But we made the decision that Lucky Lamprey, which is version 12, we will continue to support Dunfell updates for at least through the end of 2022. And I am anticipating through the lifespan of Dunfell so I know there's people out there who are still using Cookey Koi. We probably will stop supporting that version. Lamprey and Koi are very identical in terms of APIs and what's available in them. So we will continue to support Dunfell updates through 2022 with unlucky Lamprey. But the idea is that, so right now is the initial schedule based on the schedule that I have from the Yachter project at least through 3.1, 16, I believe, 15 or 16 through April. But as they continue to announce new releases, we will add patch releases to this Lamprey schedule. And Marlin, I kind of view as more of a transition release. Like I said, 2022 will be a year of transition. We'll continue with Dunfell, but we already made the decision to remove the AGL app framework and replace it with more upstream components. So for those of you that have legacy AGL apps that you want to continue supporting using the app framework and using what we have today, you can do that with Lucky Lamprey. As Marlin and the new AGL app framework and Flutter and other things continue to mature, you can make the decision when it's appropriate for you to switch over to that newer version, whether it's Marlin or Needlefish or Octopus or whatever. So we'll continue with Dunfell because it's what's available, but we are replacing, we are removing the AGL app framework and we anticipate that the existing Qt demo apps may be less functional than Lamprey because we have to replace those service binders that were in there in the existing service layers that we have, service binders that we have. So the demo apps, the Qt demo apps may be less functional. We are in the process, AGL is in the process of making the web app manager and Chromium functional with the new app framework. Toyota is working on getting the Flutter and better into our code. We have the first commits from them. We should have a build from them. I'm recording this December 5th. We should have a build sometime this week with the Flutter and better and maybe the initial launcher and home screen. We'll continue to get some more pipe wire and wire plumber updates that are coming and instrument cluster will have their multi-container solution available, their new sound manager that they've worked on with Collabra and the instrument cluster service framework that they're planning on using. So again, that will come out. Magic Marlin will be released. The plan is February 18th. The M1, the first milestone will be next week as you're seeing this, the week of December 21st. And then Marlin, as we go through next year, we plan a release about every two months. And probably maybe a little later, maybe even past 1304. Then as we go into the middle of next year, we are working on Nifty Needlefish. So we will be switching to the Kirkstone branch of the Yachto project, version 3.5. We pick up a ton of additional features from Yachto, including the read-only PR server, which was funded by AGL and the work was done by Paul Barker and Scott Murray. Hash equivalency, again, some of that work was done with AGL, Kubernetes, K3S, the public state cache, software build materials will be available, and basically all around faster builds compared to what we have today. So we're really excited about pulling in Kirkstone and some of these features, especially for our CI team and our automated test side. The app framework and IPC will continue to evolve and be ready for new reference apps on the WAM side, especially on the WAM side, but hopefully on the Flutter side as well, in the Needlefish release in July. Web app manager will be updating to a cuteless version of Web app manager. So we are hoping to remove all of our cute dependencies, both in the apps and in the app framework, in the Needlefish release. Can't completely commit to that yet, but I think we will be there in Needlefish. We'll have an update to one of the Chromium 90 versions, 9x versions. Eagalia tells me that once we do this version to the cuteless version of WAM and do some of the other, pull some of the other upstream changes from Web OSC, that the Chromium updates will become much easier and we'll be able to keep up with the Chromium release as much faster and much better than we have in the past. And we plan on having SE Linux available in permissive mode. So at least as a test that we can have SE Linux and have it available in permissive mode, we'll make that available in Needlefish, excuse me. So schedule-wise, the milestone one will be at the end of May and the final release of Needlefish will be in the end of July. Typically I try to make the schedule so that we're not doing any releases in the August timeframe so that understanding that people usually schedule vacations in late July and August, so people can do that without a problem. We'll have Needlefish patch releases throughout the end of the second half of last next year and we will start working on the optimistic octopus release. So that is scheduled for February of 2023. Again, we will continue to use Kirkstone. We will continue through the year to make lamprey releases based on Dunfell and we anticipate that with that octopus release, the app framework and the IPC evolution will be hardened because we will be back in person for CES 2023. Let's hope we beat this thing, this COVID thing, but we will be back in person for CES in 2023 with new reference apps that are not based on Q, based on Flutter or WAM, we'll see, but this process will get us to a hardened app framework and an IPC. We will have SE Linux available in a non-permissive mode. Our AGL is looking for a donation of rules. As anybody who's configured SE Linux knows, the rules can be quite complex and so if somebody has a set of rules they'd like to donate or if somebody would like to work on a set of rules, we are happy to listen. So talk to me, talk to Yann Simon and we can make this happen and we're anticipating that our instrument cluster will be production ready by the optimistic octopus release in February of 2023. So this will be very exciting. So like I said, 2022 will be a year of transition and transformation for AGL, but we will have a production ready instrument cluster and we will be closing in on a production ready IVI system with a hardened app framework and IPC and new reference apps. So here's the schedule for optimistic octopus with an initial release of initial milestone one of in December of next year and the final release in February of 2023. So to summarize, AGL will evolve to embrace more of the best of open source, take more advantage of upstream, work more with existing communities to extend automotive use cases. That includes YAKTO and open embedded. YAKTO where we have an advisory board seat on YAKTO, we work very closely with open embedded. We will continue to replace the app framework with system D and other mature technologies wherever possible. Pipe wire and wire plumber, we have driven a lot of use cases into those projects. We'll continue to work with them and continue to take their upstream changes. Weston and Wayland communities and Flutter as well. And whatever other communities may come along, there's a lot of cool projects that have been announced recently or been released and we are willing to talk to anybody and accept, you know, if you want to bring some code in, you have a YAKTO layer, you are more than happy to accept it and get it into our, get it into AGL. So we're a very open project. Everything we do is completely in the open. You can see past presentations that I've made to introduce AGL where there's a, you know, a large number of meetings and a mailing list that you can contribute to and learn how to get your code into AGL and make it part of the reference implementation. So, you know, as we continue through the next part of the decade, we see new socks, new system on chips that are being announced that continue to grow more cheaper, more powerful, really just crazy amounts of processing and computing power in the mobile and automotive space. High-speed connectivity becomes ubiquitous and really we're thinking, we're hearing from OEMs that, you know, having the ability to rearrange functionality within the vehicle, moving some functionality to the cloud, all of that is possible and all that's being worked on by various groups within the AGL community. So in particular, the virtualization expert group, the containerization, the container and service mesh expert group and the vehicle to cloud expert groups are really tackling this. I don't, you know, we have a large variety, a large number of expert groups that meet on a regular basis. If you go to our Wiki page, you will see that each of these expert groups meets every two weeks. You're free to join any of these expert groups and find out what's going on and figure out how you can contribute or learn what you can. I like to say you don't need to be an expert to participate in an expert group. Think of it as a working group. Think of it as a group of like-minded people who are trying to make progress on the project. So this week, during Automotive Linux Summit, we have a number of other sessions that are dedicated to learning what is going on within the AGL expert groups. So today, on Tuesday, after this presentation, IVI and Flutter will be a presentation. Reference hardware will be a lot of a presentation from Toyota, from Tana Morrison. Virtualization, you'll get an expert, you'll get an update from the expert group as well as some demos from ARM and from Open Synergy. Instrument cluster, Yamaguchi-san will have an update on what the instrument cluster expert group has been doing and how they're moving towards production readiness and their multi-container solution. Hayden Peters-Wald from Amazon Web Services will have an update on our containers and mesh expert group. And then tomorrow, we'll have an update from our application framework expert group from R&O to find out what he's been working on and how we're going to continue to evolve the application framework and replace it with more upstream components. Vehicle to Cloud, Richard from Amazon will be talking about that. Yann Simon-Muller, the AGL release manager. We'll talk about CI and testing. And then Lorenzo will talk about Flutter apps and what AGL is been working on in conjunction with Toyota to make Flutter apps available. I believe either in his presentation or in the Toyota presentation, we'll see a demo of what they've been working on. So there's some of these presentations. We'll have demos, a lot of good information on what's going on in each of the expert groups. So that's it for my presentation. If you have any questions, please drop it in the Q&A box or I will try to answer them. Otherwise, have a good show. Enjoy Automotive Linux Summit and I really hope to see you all in person in 2022. Thank you.