 Well, OK, let's get started. And good morning to the second day of the Linux Foundations Collaboration Summit. This here is the automotive track. And I'm Rudy Strive. I'm the director of embedded solutions for the Linux Foundation. And I'm also leading the Linux Foundation's automotive grid Linux collaboration project. And I'm going to give an overview of the state of the Union, where we stand with automotive grid Linux. Automotive grid Linux is one of the Linux Foundation's collaboration projects. We have quite a few of those. And the idea of these projects is really bring interested parties together and collaborate on common issues or common features projects and move the adoption of Linux forward. So we started automotive grid Linux last year in September. We launched it at the Automotive Linux Summit in Gaten in the UK. And at launch, this was our membership. We had our inaugural steering committee meeting there with 16 companies who were interested in joining automotive grid Linux, become a member of the steering committee, and drive the adoption of Linux in the automotive industry. Today, we have added quite a few more members. Now we're about 26. And it's really every month or so, we're adding two, maybe three more members to it. And it's a broad range of companies from the automotive industry, OEMs, tier ones, as well as from semiconductor industry and telecommunications and information technology industries. And the thought really of automotive grid Linux is not just for systems inside of a car. But of course, everyone is talking about the connected car, connecting the car to the cloud. That also includes a lot of cloud services and technology that is necessary to make this happen. And so the vision of automotive grid Linux is not just having systems in the car, but also extent to infrastructure. Our mission here is to enable the automotive industry to successfully utilize Linux and open source technologies for product development with an open collaboration on items that everyone really needs to be able to successfully develop or to deploy products inside of a car. Collaborate on the non-differentiating items, drive forward some of the technologies, future technologies that are interesting for the automotive industry. That can be what Ethernet, ABB, to network systems inside of a car can be a vehicle to vehicle to infrastructure communication stacks and many other things. And we'll also really provide processes to do so a reference software and hardware that gets engineers off the industry easily started. And if you have been to Matt Jones's keynote yesterday morning, he was talking about this survey that Geneva actually conducted looking for what are people looking for or what is their major problem, essentially, when they're trying to adopt Linux and open source. And one of the major problems really, there is nothing you can go through. There's no distribution, so to say, for automotive or even for embedded Linux. If you want to use Linux and open source on a PC, well, then you have a broad choice of distributions. You go to download it within 20 minutes or half an hour. You're up and running. And this is also one of the goals, really, also of automotive, great Linux to be such an enabler to provide these distributions and other things. And also complement that with education and best practices on open source. So these are kind of the major staples, so to say, of the deliverables of automotive, great Linux, a reference hardware and software. We don't build the hardware. We just select the hardware. Although one of the membership companies of automotive, great Linux, did build a hardware that has some typical automotive components on there. They did that. It was commissioned by Toyota. And it's a hardware that actually provides Intel x86 architecture as well as ARM-based architecture. So systems with different CPU platforms. So we have ARM reference hardware that are Intel-based as well as the ports going on to ARM-based hardware, such as the Ponderboard and also FreeScale IMX6-based platform. The demonstrator we'll be talking about runs on a Nexcom hardware that uses an Intel Sandy Bridge chipset. Really, the idea is also to have a download, really be able to download and software and go. Put it on the hardware and run with it and make it really that 20 minutes from downloading, you image your system and then you have a system up and running. And we've been working intensively on that during the last couple of weeks. And the first product of that is that demonstrator that we will be showing in detail later. Another important part, of course, is processes and tools. So OK, you have an image, a distribution that you download, you put it on your system. But you don't necessarily know how to build it. And it's not like that. There's not one size fits it all. Once you want to go into an embedded system into automotive deployment, you need to be able to build your system, essentially from scratch. And you also need to be able to modify and customize your system so that it fits your particular needs as well as your particular hardware. So one focus of automotive analytics is also build systems, of course, collaboration, source code management, eventually automatic testing, QA, and also establish some best practices. One thing with the industry is, like any industry, there's quite a learning curve in how to get involved with open-source software. And it's kind of really a three-step process. The first step is really you use open-source software, you use Linux, and you utilize it, you build something with it. And then the next step would be, eventually, you want to be able to directly collaborate in those open-source projects. Because in the course of your development, your adoption, you have maybe made some changes to the source code of some of the projects to better fit your needs. And you think, oh, yeah, well, eventually what I did there is actually also very useful for other people. So we want to contribute back, which is kind of the next level, working in open-source projects and contributing back to that project, and also make sure that what you have written, or what you have provided for the benefits for others. And it's also for benefit for yourself, because once you have submitted something to an upstream project or so, then part of the maintenance actually is done inside of that upstream project, too. And then this third step, of course, is if you say, well, I have a very specific need. I have an open-source project, or I have a project, but it's not really covered by any other open-source project. So I want to launch my own open-source project. And I want to create a community around it. And this is also what has happened. One example, you have heard it yesterday, is about the OpenMama project, which is another open, Linux foundation open-source collaboration project, where the New York Stock Exchange technology company went out and said, well, we created this software, but it's for the broader benefit of many. And we want to open-source it, and we want to basically enable the community around it. Next thing is certainly also education. I talked about this right now with the collaboration of Contagoon to Open-source Project, but also around open-source licensing and compliance. Of course, open-source has a lot of different licenses. And you need to stay compliant with these licenses. Eventually, you are sourcing from suppliers. You need to do supply chain management. And there are, of course, other talks. Today, later on, we will have a very interesting panel discussion about open-source licensing. And there is also presentations here today about the SPDX license exchange format and others. What is the idea or the concept behind Automotive Great Linux? It is really about really being developer-oriented, rapid prototyping, and some starting engineering. That's why we also call our reference distribution, or commonly dubbed or name it, the Fedora or Debian of Automotive Linux. And if you're familiar with Linux distributions, you know that Debian and Fedora are these cutting-edge developer distributions. They put the latest Linux and open-source technologies in there. They integrate it. And it's really a good way for developers and engineers to experience some of the latest and greatest technologies around Linux and open-source. And the Automotive Great Linux reference distribution seeks to do exactly that. So we want to integrate latest and greatest technologies that are relevant to the automotive industry. And put this all together in a package so that developers can easily get started with it. And that comes, of course, with these images, with source code downloads, as well as documentation to do that. Upstream focused. The idea is never ever to re-invalid really the wheel if there is an upstream project available. And it provides and has a lot of rights and necessary features or so. But there may be enhancements or so. Then Automotive Great Linux and the companies and contributors working with it would make contributions to those upstream projects. Then also, of course, eventually provide upstream projects, like really our user interface or so, our HTML framework. That could be an upstream project. And others as well as serve as an upstream project itself so that others can use what Automotive Great Linux is putting together, such as the reference distribution, the reference distribution, of course, is not meant to be production-ready, but people can use it and kind of derive production-ready production systems from it. Of course, Automotive focused, all the core components that need the needs of the automotive industry, putting things in there, developing that could be new features or can just be kind of optimization things such as, OK, how do you do fastboot with Linux so that you can show real-time images from cameras connected to the system within two to three seconds from startup, which is what you want to have for backup cameras and surround you with your cameras when you're driving your car out of a parking spot. Other things are, like how do you lay out a file system correctly for an embedded device that has to live in a vehicle for maybe 10 years or eventually longer so that you do not wear out your solid-state devices? So how do you optimize and put things into read-only sections so that you don't, or your log files or many Linux components or frequently write temporary files to disk, how do you do this without really wearing out the file system or maybe you don't have to really directly write to the SSD but you have an overlay, sort of a RAM disk or something like that to do that. It's really all about addressing and closing on those technology gaps. OK, this is structure on how it looks. So the project is hosted by the Linux Foundation. Linux Foundation provides the infrastructure for it, like we do it with many of these collaboration projects that we have. Linux Foundation, of course, is a neutral body. We don't have a stake in it, but we do provide these services to companies who are interested. And so HL is one of these Linux Foundation collaboration projects. The work group is structured in a steering committee. Steering committee, these are corporate members, companies who have a stake in automotive great Linux who want to actively drive on the development set, the directions. There's a steering committee coordinator. That's what I'm doing right now. And then we have a set of expert groups that address certain domains and focus on those. And we'll go into expert groups in a little bit. And then there can be contributors and resources from many different areas. Thank you. The open-source community, of course, companies, academia, individual contributors. Everyone really interested in driving adoption of Linux and open-source forward in the automotive industry. Or interested just in playing around with it. And that's one of the things that we enable from playing around a lot of new interesting things can be derived and come up. Steering committee members, these are the HL stakeholders. The companies who have a vested interest in it. They provide their expertise, guidance to advance HL's missions, goals. They lead the expert groups. And they contribute really actively to HL on the resources, requirements, specifications, implementation, test, and documentation. While code and open-source projects is always kind of at the center, of course, there's a lot of different things that can be done and can be contributed. And if somebody just downloads on the image and puts it on the system, maybe on a different system, and says, well, I tried this image on a different piece of hardware. And this work and that work, that's really valuable feedback, and it's a valuable contribution. And of course, if that's all documented, that helps moving the course forward. Come on in, please. The expert groups, they focus on a specific domain. They really actively drive a technical or organizational area within the project. They have their domains of focus. And they're led and run by a lead, one or multiple leads. And they are individuals who are typically employees of the Steering Committee members. And it's really a dedicated leadership. And everything requires leadership in some form to move things forward. Expert groups, they really understand the industry goals and requirements for their domain. They seek the input and form a vision where they want to be, what they want to accomplish. And one of these expert groups is our reference distribution. And we have a certain set of goals that we want to achieve, such as, well, you should be able to use the reference distribution within 20 minutes from downloading. Eventually, you should be able to build the entire reference distribution from source code, from scratch, to an image yourself, and other things. They also have a good understanding of the current reality, the status of Linux in respect to the industry requirements, what is required, what is needed, and how can we close the gap? How can we get there? Where are we? And what do we need? And also then identify stakeholders. Who do we need to make things happen? And that can be people, organizations, from the industry, as well as from the open source community, saying, OK, maybe there is some, for an example, there is a Bluetooth profile that may not be implemented yet in the standard open source Linux Bluetooth stack, which is BlueC, so how can we work with the maintainers of the BlueC project to eventually close that gap, or maybe some other things that are related to the kernel? And this is also where the Linux Foundation can provide valuable resources to the entire thing, because of our connections, of course, to the community and kernel community and many other communities. And then, of course, have a plan. How can we involve those stakeholders? How can we close the gaps? And how can we get there where we want to be? And, of course, execute that plan and work in action. So we had an automotive grade Linux steering committee had a meeting during the Linux conference in Barcelona last week. And we launched a whole set of expert groups for that, reference distribution hardware, multimedia, over the air updates, and so on. That's what we thought was a good idea. So we set up all this structure, but now we really can need to fill also everything with life. Automotive Linux is still a pretty new project. And really, the most progress really made in terms of the reference distribution and the enablement, in particular also with that demonstrated project that we just did within the last couple of months. And we're, of course, hoping to involve more and more people and more and more companies into those expert groups and say, OK, yes, we want to take a lead here. We want to do something there. And we will have a new expert group pretty soon also about vehicle-to-vehicle-vehicle-to-infrastructure communication and open source software stack. That componentality of company is also active in automotive grade Linux. We'll be open sourcing and inviting people to contribute to it and collaborate it and also to try it out and see how it works and how can we make it better. Automotive Grid Linux is really about action and getting things done. It's not really so much about standardization. Standards don't really work if you kind of sit at a table and try to dream up, oh, that's great, a new standard and everybody's going to like it. It doesn't work that way. It never worked that way. Standards evolve, eventually, and things evolve through action, getting something done, Ethernet evolved, somebody developed something, and it was made available. People used it. People improved on it, and eventually it was more formalized and standards were set. Automotive Grid Linux is also not about compliance or so. There is no such thing as automotive grid Linux compliance. The reference distribution is not meant to be the blue print of a compliance specification or so, because it doesn't really make that much sense either in this setting or so. Everybody has different requirements for that. Everybody has different requirements. There are different requirements and different ways to integrate things. You build a different head unit, company A, or OEMA builds a different head unit than OEMB. And then they also have different hardware. They need to adapt their things. They want to have a different feature set. They want to modify it. And the reference distribution is really only a super set of a lot of different technologies. And you may need all of those technologies so you can remove and customize it. So it's not like that you have to use what HAL produces. This is really something that enables you and gets you started. So what have we been doing? Elsewise, HAL webinars. We launched a webinar series. We have this really every month. And we had one in February, Matt Jones, and presented on the Jaguar Land Rover's experience in moving to Linux-based IVI systems. And in March, McVillan and Osama Othman from Intel were presenting on leveraging the Tizen IVI built infrastructure, how to build packages and software with four Tizen IVI. And now upcoming in April, we will have Constantin Kite from Confidentiality talking about open source solutions for vehicle to infrastructure. And we go to vehicle to vehicle communications. And that's also an invitation. If anybody wants to present, has something interesting to present or wants to present a webinar about technologies related or relevant for automotive and open source, we invite those. Yes, that's actually a good point. Thank you for bringing that up. We have this also always on the HAL website. There are the registrations for those webinars. You can sign up for them. And if you have missed those, you can download those. And you can download the presentation slides itself, as well as the entire video and audio feed from the webinar. So you can always come back and look at it. And all right. So we're doing also a couple of promotions here and there. In the media, we had Doug Newcomb from Wired had a nice article in which automotive grid Linux was represented. Linux drives the open source car. Jim Samlin, also in Wired, had an opinion page. The next battleground for open source is your car. And then Doug also did an interview with Doug Newcomb on automotive grid Linux in more detail than he wrote an article again for Wired can open source or solve car tech problems. And of course, we strongly believe so. And other things are events. I've been representing events. I've been representing automotive grid Linux a couple of times. I'm doing events. First time there was telematics at China in 2012. That was December 2012 in Shanghai. We talked about automotive grid Linux and what it's doing and why it makes sense. And there will be another event coming up, content and apps for automotive Europe on 2013 in June. And we'll have another one on connected cars in 2013, also in June in Amsterdam, where I'll be representing and talking about automotive grid Linux. Projects. So how have the projects been doing? Demonstrate a project that has been visible here today in vehicle IVI, vehicle demonstration, Land Rover LR4 in the breezeway down there, Valet parking area. And this actually has been really a collaboration project between HAL companies, Foylab, Symbio, Symphony, and Telica. And as Matt also yesterday said, we'll put this together in a very short time frame just to see what can be done, actually, what can be done if you really throw everything overboard, typical waterfall type of development, and just embrace some open source or kind of rapid scrum type of development, and see what you can do in three weeks and how it works out. And we think it worked out pretty well. And it's really an excellent starting point for the automotive grid Linux, some reference distribution to which we want to build more and more. So what we did really do, we integrated the system even with the CAN bus, CAN controls. We mocked around with the Linux CAN drivers and everything, tried to get that run on the kernel and load into the kernel and so on, and then send out messages, can frames to the CAN bus. We added a media player and controls for the heating ventilation, air conditioning, and it actually can control through the CAN bus the fan and the temperature in the car. And then we said, OK, we'll take it also a step further. Can we add some remote control functionality to this so you can log into a website or eventually can use your mobile phone and change settings in your car and do things. And for that, we also built up Cloud Server in the Linux Foundation's cloud that enables that functionality. And that cloud server and all this functionality will actually also be available to collaborators to do similar things. And the way how it just works, of course, it's secure. You have your own logins and things like that, so you don't control somebody else's car or systems. And those downloads will be available on automotive.linux foundation.org and the HAL demonstrated. So together with this, we also have this now user experience contest. We said, OK, so we did something in three weeks. And we said, OK, let's find people out there who can do maybe much, much more than we could do in three weeks, maybe in a rather short time frame, sorry. And enhance and improve on this even more or just use the entire framework and say, OK, well, I use the framework, but I throw away all the skins and the gooys and everything, and I decide my completely new thing. And that's what we're out for. We're looking for. So what can you really do with this enabler? Because going back to our mission, we wanted to enable this collaboration and say, OK, now we've put something together. It's not perfect. But take it and run with it and really go out and show what can be done with this. And so we created a couple of user categories for that, best user experience, best visual appearance, best new concept or additional feature. And there will be some prices for that, of course. We'll have one winner and two runners up for each category. And everybody will receive a tablet PC. And the winners will also have the opportunity to work with AJL and Jaguar Land Rover on the proof of concept and really get what they have designed into this entire thing. And well, that's by the way, at least, you get recognition. And that works for individuals as well. It works really for companies, too. For software engineers, software developers, open source is really a great way to build up your reputation. It's almost like a publicly visible resume, but not just the resume saying, I did this and I did that. But here is also the proof. This is what I did because I collaborated in these projects or did this and that. And of course, for companies, a collaboration in something like automotive grade Linux is really a way to directly show expertise and show technology that the companies have and have developed and showcase that. There's terms and conditions at this website. Of course, there is a time frame to it, so really the contest started yesterday and at the Automotive Linux Summit in Tokyo, in Japan. Well, actually, a little bit before that because we need some time to review everything and find the winners and runners. So really, what's next? Around the AJL demonstrator, reference distribution. Matt already also mentioned that yesterday, integrate open source navigation on Navit into it. Integrate Bluetooth, telephony, automotive message broker to kind of have an abstraction layer, essentially, from the middleware or from the user interface to the vehicle interfaces so that it makes it easily portable from one car to a different car. Web API for vehicle sensors and controls. That's meant to be a broad superset. Really ideally, we go out and get really input from all different OEMs and car makes and models and see what sensors are in there and provide standard input interfaces to read those sensors as well as standardized interfaces to issue commands or to take control. And this is supposed to be or will be aligned with W3C automotive platform business group. I talked to representatives of that business group last week, and coincidentally or not, this business group actually will have a meeting also viewing the automotive Linux summit in Tokyo and in Japan. So I want to bring this together and also really provide AJL's input to that business group. Another thing is really a source code and build system. Really, an image gets you quite away there, so you can work with it and play with it, but eventually you need to be able to build it yourself and build it from scratch. So we want to have some system builds from source code all the way to the image and use a build system for that. And really, what else? You name it. And this afternoon we'll have an open steering committee meeting in which we can discuss all the topics and things that our people are interested in and would like to address in the framework of automotive great Linux. OK, a couple of upcoming events. Talked about the webinar already on open source solutions for vehicle infrastructure, vehicle-to-vehicle communication that's presented by constant kite componentality, first day April 24th, sorry, 25th. We always do two webinars to accommodate the different time zones around the globe. And we have one for Europe that will be at 8 AM, Central European Summer Time there, 4 PM, Japanese Standard Time, or for the US. For me, unfortunately, it will be at midnight. And then we'll have another one for the US at 6 PM, European Standard Time, and that will be then 9 AM Pacific Time. Registration will be available shortly on automotive.linux foundation.org slash webinars. So we can sign up for it there. And then, of course, we'll have the automotive Linux summit 2013 in spring. It's a two-day event, May 27 and May 28. It's co-located with LinuxCon Japan. And we have a great lineup of speakers already. And good keynotes, and about 34 or 35 breakout sessions. The program will be published this week on our website, too. And what else? Yeah, there also will be a hands-on lab on build system, on the Tizen IVI build system, too. If you're interested in that. And yeah, thank you so much. And your questions.