Happy New Year! We hope that everyone in the ELISA ecosystem and community had a wonderful and safe holiday season. As we take a look at the blank slate of the new year, the Linux Foundation’s Shuah Khan, ELISA Project Chair of the Technical Steering Committee, shares a few of the predictions of what the project will achieve in 2022. She chats with Swapnil Bhartiya, The Fourth Industrial Revolution Creator and Host, in this video. Watch it or read the predictions below.
Swapnil Bhartiya:
Hi, this is your host, Swapnil Bhartiya. And welcome back to TFiR’s predictions for 2022. And today we have with us, once again, Shuah Khan, Linux fellow and chair of the ELISA Project Technical Steering Committee. Shuah, it’s great to have you on the show.
Shuah Khan:
Thank you for having me.
Swapnil Bhartiya:
Before we ask you to grab your crystal ball and share your predictions, I want to know a little bit about the project. Tell us what is the project all about?
Shuah Khan:
ELISA project is all about enabling Linux and safety critical applications. What that means is that at ELISA project, what we are doing is we are bringing safety experts and Linux experts together to collaborate on developing best practices and resources for people that are enabling Linux in their products, on their safety critical applications.
Swapnil Bhartiya:
Now, if I ask you, please grab the crystal ball and tell me what predictions you have for 2022.
Shuah Khan:
My first prediction is ELISA community will keep growing. We’ll continue to add new members and will continue to engage with the kernel and safety communities.
My second prediction is we will expand our critical spaces. Right now, we focus on several like medical and automotive. We will expand into other industries by adding members from aviation and industrial spaces.
Swapnil Bhartiya:
Thanks for sharing these two predictions. Now, if I ask you what is going to be the focus of the project in 2022?
Shuah Khan:
The focus for us in 2020 do is continuing to work with Automotive Grade Linux (AGL) and Autostar in the automotive space and continue engaging the kernel and safety communities. Our second focus is to continue harmonizing best practices for our members. We want to be able to make best practices, processes, and resources available to our members that are enabling Linux on safety clinical applications.
Swapnil Bhartiya:
Shuah, thank you so much for sharing these predictions and also, the focus for the project for 2022. And as usual, I would love to have you back on the show. Thank you.
ELISA Ambassadors are technical leaders who are passionate about the mission of the ELISA Project, recognized for their expertise in functional safety and linux kernel development, and willing to help others to learn about the community and how to contribute.
Each month, we’ll put a spotlight on an ELISA Ambassador. Today, we’re excited to highlight Elana Copperman, PhD, ELISA ambassador, Chair of the Linux Features for Safety-Critical Systems (LFSCS) Working Group and TSC voting member. Elana works as a System Safety Architect in Mobileye, an Intel company, designing features to support safety as well as security features in Mobileye vision products for the automotive domain.
Background Details:
As a System Safety Architect at Mobileye, Elana provides support for designing critical system features in Mobileye products, including system boot; drivers; and Linux infrastructure. Before working at Mobileye, she worked as a Security Architect for Cisco-Il (formerly NDS) and more recently as a security consultant for major European automotive concerns on behalf of various Israeli startups. Most recently, merging with safety constraints in the automotive domain, to deploy secure as well as safe systems. Her research interests focus on software engineering methodologies and security engineering.
Q&A
How long have you been active in open source?
I have been involved in “open source” before it was formalized as we know it today. During my time as an undergraduate student, online software source code was commonly shared as freeware. In fact, even early Unix versions were provided at no cost to academics, and collaborative efforts were supported to some degree.
My PhD research focused on Object-Oriented Programming, including some investigations on Java source code and features. Open source software development, Linux in particular, has evolved since then, including many new challenges and opportunities. For example, setting up and working with Apache Server over Linux OS in the early 1990’s.
Over the last 15 years, Linux has grown to what we know & love today, with its amazing powers. As a system architect, I have been designing systems that empower Linux in embedded systems, first in Set-Top Boxes (for digital broadcasting) and currently in Automotive.
Tell us about your favorite open source project and what problems did it aim to solve?
My favorite open source project focused on security code review with ST (chip vendor) engineers for the optee code, which had been released to Linaro. To see first-hand how open source aligns vendor, kernel and user requirements with features to resolve complex security challenges was mind-blowing.
How long have you been active in the ELISA Project?
What roles and/or working groups do you have or participate in?
I was the Chair of the Kernel Development Process Working Group, and am currently the new Linux Features for Safety-Critical Systems WG. I am learning from the safety experts on board, and my primary contribution is to represent the viewpoint of the application designers and developers who will build Linux-based safety critical systems.
Where do you see the ELISA Project in three years?
My dream for ELISA is to see a community of developers providing kernel modules which may be leveraged for use in safety critical systems. For example, a suite of memory protection mechanisms derived from well defined requirements that may be deployed to protect safety-critical data. Another example, which is in our planned agenda, are test suites for concurrency issues such as deadlock and race conditions, focusing on test plans derived from safety requirements.
What is the biggest strength of the ELISA community?
I think ELISA has matured since its early days and we are currently more structured in our analysis and goals. Our strength is in current efforts to progress and making real contributions to the Linux kernel community.
What is the best piece of advice you have ever received?
Never give up. Be flexible, adapt, adjust – but keep up the hard work.
What technology can you not live without? Why?
My home coffee machine. Drop in for a fresh cup and you will know why.
What part of the world do you live in? Why do you love where you live?
I live in Israel, a tiny multicultural nation at the junction of 3 continents (Europe, Asia, Africa). It has also become a major highway for birds – and a pilgrimage site for bird watchers. A wide variety of species can be viewed making their way south in the fall and back north in the spring. Thomas Krumenacker (German journalist and photographer) wrote a book on “Birds in the Holy Land”.
Now is a great time of year to take a trip to the Hula Valley Nature Reserve, to get a view of some of the estimated 500 million migrating birds passing over the Hula Valley and stopping by for a drink of water. This exemplifies the amazing diversity of the people and wildlife of our small fast-paced country.
What’s your favorite quote?
3 Fun facts:
My first computer was a PCJr, with 64 Kb of memory, and with virtually no hardware or software. I had to install all my own hardware add-ons and get it to work, including etching bit maps for the Hebrew alphabet in memory and getting it to work from right to left. After adding more and more components to the motherboard, one day it blew up. But I had a lot of fun with it until that happened.
As a grad student at NYU, we had loads of fun playing with early internet protocols and collaboration tools, including gopher and kermit; getting our hands dirty (“finger”) working with each other’s systems; and Mosaic (an early Web browser). The crazy things we did over the internet taught me a lot about potential security issues related to networking. This expertise was the foundation for my more recent work in security and safety engineering.
As chair of the Computer Department at the Jerusalem College, we aimed high but with a low budget. Trying to keep up to date with educational (i.e., no support or documentation) versions of closed source software was a real challenge. I became adept at finding contacts working with major software vendors who were willing to break down the walls, expose the source code and support my customization for our needs. In a sense, challenging proprietary software in open-source development mode …
To learn more about ELISA ambassadors, please click here.
Written by Philipp Ahmann, ELISA Project Ambassadorand TSC member
The 8th ELISA Workshop, which took place on November 8-10, had 158 registrants that learned more about the various working groups and networked with ambassadors. Participants were active and stable in the technical discussions, which helped plan for next year, and proved that there is continuous interest and motivations in these topics. Additionally, new ideas were shared and can be considered as sources of inspiration and for critical thinking with e.g. talks about STPA, the z-model or open source and the community problem along with new approaches to safety and importance of processes and testing.
Overall, ELISA workshops have more of a conference character presenting major achievements and results of achievements from the last quarter. Interested newcomers as well as community participants receive a very good status update in which direction ELISA moves forward on its way to enable Linux in safety applications.
On the other hand, this brilliant forum to sync up and align in a virtual format, misses a bit of the in-person discussion and brainstorming that made ELISA’s first workshops so enjoyable. With a community spread across the world longer working sessions are seldom and almost not possible. Prime time slots are used to align to reach as many people as possible.
As this year’s workshops come to a close, we hope that travelling and hybrid workshops become possible again. In this type of format, the core community can take joint working sessions, while talks and presentations can still attract newcomers and other interested to get an overview about what is going on in the community and what to target next. We hope to see you in-person next year if possible.
In case you missed the November virtual workshop, let us take a look at a few selected sessions from the conference.
Day 1 started with the newcomer and welcome session. It provided an overview about what Linux is and how safety comes into picture to form the name ELISA. The statistics shown during the talk on the usage of Linux in industry are quite impressive and speak for themselves. Linux is everywhere. (Or almost everywhere.)
How important such Linux features and development processes are could be slightly depicted from the presentation about Linux in Safety Systems explained by Christopher Temple from arm. He illustrates quite well which different levels of complexity a system could have. He also reminded the audience that there can be a difference between simply following a safety integrity standard for the necessary processes and actually creating a safe product. It is interesting to see that you may be able to show standard conformance without having safety properly implemented and creating a safe system which is not certifiable or in conformance with a safety standard.
On the second day the slides about Certification Using the New Approach to Safety presented by Paul Albertella showed that modern safety certification and assessments need to bring a good tool support towards tool support and automation along with proper tool classification and qualification as a major step to achieve efficient certification and generation of evidence, irrespective if you are running proprietary or open source software.
In another session Lukas Bulwahn from Elektrobit helped the participants on understanding the z-model in which the challenge on pre-existing software is illustrated, where a logical model would be to write requirements, go over to integration and verification to derive software architectural design, leading to software unit verification to finally create a “z” by moving to the originally existing Software unit design and implementation. This can help to approach existing stacks which do not fall into strict recommendations such as demanded by e.g. ISO26262. This said, it has to be kept in mind that the “z” fills the gap and can create a complete “v” in the end, although you may run into issues during an ASPICE assessment.
Day two was concluded by Shaun Mooney from Codethink, who gave insights on how to use STPA for ISO26262. STPA has been used within the medical devices work group since a long time and recently found its way also into the automotive work group, where it serves as an alternative to a traditional HARA. A very important element of the STPA, beside others, is the identification of unsafe control actions (UCA) to unveil potential harms/hazards and risks in a very structured and visual way.
Day three was a nice mixture of technical insights into the Linux kernel and new approaches and directions towards safety qualification of Linux application. The strong demand to consider both Linux software development within the community and the strict regulations by safety integrity standards to come to a certifiable product, were brought to the point by Lukas Bulwahn’s talk. It was thought to encourage critical thinking on safety integrity standards and the community problem. Let us hope that the work of ELISA can make a difference and the effort we take will direct in the solution of this problem, eventually even with updated or new safety integrity standards, which include state of the art software development process and quality measures, so much needed for complex systems.
As for the previous workshops the last session wraps up and includes the goal settings for the next quarter along with the request to not let the discussions stop here…
If you reach this point of reading the blog post, you seem to be really interested in joining the ELISA community, so don’t miss to register to your mailing list of choice.
Short TL:DR summarizing words about the workshop:
Less registered people, but very stable number of attendees during the workshop and on level of last workshop
Good “take home” messages letting you think about the challenges of Linux and open source communities to approach safety integrity standards
New approaches in fields of architectural analysis, tools, development process, testing and engineering show the demands where Linux and open source need to go different ways and where safety integrity standards need to evolve to keep up with the complexity of software written by a large scale community.
ELISA community would benefit from a hybrid approach enabling in person working sessions to let the workshop be a workshop and have less conference style.
The ELISA community grows and reaches a point where harmonization is needed. Brainstorming times are over and everybody shares concepts and proposals how to achieve the goal to enable Linux in safety applications.
Videos and recordings of the workshop presentations can be found here.
Written by Dan Brown, Senior Manager, Content & Social Media, LF Training
As we approach a new year, this is the perfect time to consider what you want your career to look like in 2022. Job openings are at record highs, and this is especially true in the IT field, where the 2021 Open Source Jobs Report found that 92% of hiring managers are unable to find enough talent to meet their organizations’ needs. A primary mission of The Linux Foundation is helping close the talent gap so the industry has the talent necessary to carry out digital transformation activities and continue innovating, while also creating accessible pathways for anyone who wants to start an IT career to do so.
We are excited to once again offer our best pricing of the year on our entire catalog of training courses, certification exams, bundled programs, and bootcamps for Cyber Monday. From now through December 6, 2021, all these fantastic offerings covering hot topics like cloud computing, system administration, networking, blockchain, web development, embedded systems, and more are available at significantly reduced cost. As the home of some of the most important open source technologies like Kubernetes, Linux, Node.js, Hyperledger, and more, The Linux Foundation provides vendor-neutral training directly from the experts helping build these projects.
You can check out the full details of everything that is on offer on our Cyber Monday Landing Page. Begin your journey to a long-term, successful career in IT today!
Open Source Summitand Embedded Linux Conference, held in Seattle, Washington as well as virtually on September 27-30, gathered 1,944 total attendees. Approximately, 482 of those attended in person from 760 organizations across 68 countries around the globe. Learn more about the event in the post-event report here.
The ELISA Project was represented by Gabriele Paoloni, Chair of the ELISA Project Governing Board and Open Source Tech Lead (Functional Safety) at Red Hat, and Daniel Bristot de Oliveira, a member of the ELISA community and Principal Software Engineer at Red Hat. Gab and Daniel presented a talk about how to create a maintainable, scalable and verifiable SW qualification approach for automotive in linux. Watch the video below.
Over the last years, many discussions took place in Linux Foundation’s ELISA Working Groups about possible approaches to qualify Linux for safety-critical systems. To achieve this goal, an architectural description of the Linux kernel is required.
The challenge though is to find the adequate granularity for description: It must be precise enough to support safety analyses, but it cannot be too fine-grained to the point of being unmanageable. A promising approach is to leverage the ISO26262-6 and ISO26262-8 together, in a hierarchical incremental approach. Optimizing the amount of produced documentation and collaterals.
In this video, the foundations of this approach were presented. Gab and Daniel showcase why this approach is suitable for safety application as well as out-of-context using assuming safety requirements and why it provides natural scalability across different use-cases. Finally, considerations will be made with respect to available tools and mechanisms already implemented or proposed in Linux that can significantly help with the above-mentioned approach – including a detailed discussion about how to cross verify, and monitor, the documentation and the kernel using the Runtime Verification subsystem.
Written by Elana Copperman, ELISA project ambassador, Chair of the Linux Features for Safety-Critical Systems Working Group and System Safety Architect at Mobileye (Intel)
The Linux Features for Safety-Critical Systems (LFSCS) WG aims to feed into the OSEP and other WGs, working together as a team. LFSCS invites engineers, architects and integrators who actually develop and deploy Linux-based safety-critical systems to contribute from their practical experience and knowledge. In particular, to identify existing Linux kernel features that may be leveraged for use in safety-critical systems.
For example:
Mechanisms for protection of various memory types; e.g. protection from faults due to uninitialized variables or stack overflow.
Dynamic analysis for multi-threaded systems; e.g. tests based on tools such as TSAN or ASAN.
Kernel profiling using ebpf-based tools; e.g. perf-tools or bpftrace
AER (Advanced Error Reporting) for fault handling; e.g. PCIe fault handling
Safety extensions to Linux drivers; e.g. fault handling support and bridging the gap between hardware-based safety features and application layer fault handling.
The WG mailing list is open to registration here, and we are seeing an amazing group of contributors who can demonstrate use of such features in real systems, and help ELISA to learn from these experiences. Initially, we will investigate existing features but will also propose enhancements to such features and to work as a community to design / implement / deploy kernel patches. The goal of such patches will be to help make those features more amenable for use in safety critical systems. Our Github playground is here.
The alliance with ELISA, and with the new Open Source Engineering Process Working Group in particular, is a critical aspect of this effort. We will be working together to help ensure that those patches and features can be used by designers and integrators producing safety critical systems.
The scope of this WG does not include safety qualification or any safety claims on how the integrator can or should use these features or patches. The only claims that would be made are a description of the feature and its functional impact.
The WG will be formally kicked off at the upcoming ELISA workshop (November 8-10). We will be giving an overview of the working group and answer any questions on November 8 at 3 pm CET. We will be scheduling weekly meetings following the workshop. If the technical challenge of enabling real change in deploying open source Linux-based software for safety critical systems excites you, come join and help us meet the challenges!
You can still register for the Fall workshop, which is being held virtually and is free to attend. All registrants will be able to watch the sessions on-demand. Register here today!
Written by Paul Albertella, Chair of the ELISA Project Open Source Engineering Process Working Group
The ELISA Project’s new Open-Source Engineering Process (OSEP) Working Group focuses on the role of engineering processes in creating safety-related systems based on Linux and other FOSS.
Engineering processes are very important in safety, because we rely heavily on them to provide confidence in a system and its components. We achieve confidence by undertaking risk analysis to identify how harm may result from the use (or misuse) of the system, and then constructing a safety argument, which describes how these risks are managed.
When we apply this approach to a specific element of the system, such as a software component like Linux, the argument can be broken down into a number of claims that we want to make regarding that element and its role in the safety of our system. Some claims will relate to the functional responsibilities that the element has in the system; others will relate to the processes that we use to create and refine it.
Importantly, we also need to produce evidence to support these claims. Almost all of this evidence will be produced by an engineering process; some of it will be evidence relating to those processes themselves..
Safety standards like ISO 26262 and IEC 61508 describe reference processes that can act as a template for safety arguments like this. They identify the engineering practices that are seen be necessary (e.g. code review, verification through software testing), the formal processes that are used to control these (e.g. verification management), and the evidence needed to confirm that these have been applied (e.g. test plans, test results).
These reference processes are based on the V-model, which emphasises the formal specification of requirements, architecture and design, and the ability to trace formal verification processes back to these. For software, the standards focus on the processes used when developing new components for a safety-related system, although they include some guidance on applying the principles to pre-existing components, such as software libraries.
Open source projects like Linux have their own development processes, which may be sophisticated and make use of sound software engineering practices. However, it is difficult to map these directly to the reference processes described by the safety standards, because open source development models have very different goals and organizational models, which tend to emphasize refinement by rapid iteration, peer review and community contribution.
In order to address this, OSEP aims to identify and evaluate practices, processes and tools that FOSS developers, system integrators and product creators can use to bridge this gap. We plan to accomplish this by:
Selecting Linux topics and safety-related claims that we want to make about them
Identifying and evaluating practices, processes and tools to answer:
What risks are associated with the topic and claims?
To what extent are these risks addressed or mitigated by (or for) Linux?
How can we manage risks that are not sufficiently addressed or mitigated?
How can we show evidence to support our claims?
Collaborating with other WGs for technical investigations
Documenting and sharing our results as we go
If you would like to learn more about OSEP, join us for an overview presentation on November 8 at 3 pm CET at the ELISA Workshop. The Fall workshop, being held virtually on November 8-10, is free to attend and all registrants will be able to watch the sessions on-demand. Register here.
If you would like to contribute to OSEP, please join the mailing list here, where you can also find details of weekly meetings on the working group calendar.
ELISA Ambassadors are technical leaders who are passionate about the mission of the ELISA Project, recognized for their expertise in functional safety and linux kernel development, and willing to help others to learn about the community and how to contribute.
Today, we announce two new ambassadors – Jeffrey Osier-Mixon, Principal Community Architect at Red Hat, and John MacGregor, a thought leader with several decades of experience in software technology. Learn more about Jeffrey and John below.
Jeffrey “Jefro” Osier-Mixon:
Jefro currently focuses on automotive efforts. As a community architect, Jefro is responsible for maintaining Red Hat’s relationship with automotive-oriented communities, and he acts as the current chair for the CentOS Automotive Special Interest Group.Jefro has worked in open source for nearly three decades, having started his career as a technical writer with Cygnus Support working on documentation for the GNU tools. He has worked with Wind River and Montavista/Cavium Networks on embedded operating systems, and spent five years at Transmeta. He switched careers in 2011 and went to Intel to serve as the community and program manager for the Yocto Project, where he was the board chair for 7 years. During that time, he also helped launch Zephyr and Project ACRN. Most recently, he spent two years at the Linux Foundation as a program manager for RISC-V International and LF Energy.Jefro has been on the program committee for the Embedded Linux Conference series since 2010, and he speaks regularly at open source conferences. It’s best to catch him after the coffee kicks in.
John MacGregor:
John is currently spicing up his retirement by participating in various ELISA working groups. He started his long career as a scientific programmer, switched to Unix programmer and system architect, then progressed to project manager in telecommunications. He worked for several decades as Senior Expert for Software Technology in the Corporate Research Division of Robert Bosch GmbH. Among other things, he worked on software process improvement, software reuse, automotive software architecture and IoT technologies. Before retiring, John participated in the SIL2LinuxMP project, which focused on certifying Linux under IEC 61508 at the SIL2 level, and then continued to contribute to the ELISA project.
John holds a Bachelor’s degree in Industrial Engineering, specializing in operations research and information systems, as well as an MBA, specializing in marketing and finance.
Learn more about other ELISA Ambassadors here: https://elisa.tech/community/ambassadors/ Or, if you’re currently participating in the project and would like to become an ambassador, you can apply here.
Since launch in February 2019, the ELISA Project has created several working groups that collaborate and work towards providing resources for System integrators to apply and use to analyze qualitatively and quantitatively on their systems. Current groups include an Automotive Working Group, Medical Devices Working Group, Safety Architecture Working Group and Tool Investigation and Code Improvement Sub-Working Group to focus on specific activities and goals.
If you’re interested in learning more about the goals and objectives for these working groups or asking questions, we invite you to the ELISA Workshop on November 8-10. The virtual workshop, which is free to attend, will host speakers from Arm, Codethink, Elektrobit Automotive GmbH, Evidence Srl, Google, Intel, Mobileye, The Linux Foundation, Red Hat and UL LLC.
On Monday, November 8 at 5-6 am PDT, the working group chairs will provide updates on all activities. Led by Gabriele Paoloni, Lukas Bulwahn, Kate Stewart, Shuah Khan, Milan Lakhani, Jason Smith, Jochen Kall and Philipp Ahmann, you can add this to your schedule here.
Open Source Engineering Process Working Group: This working group aims to examine safety-related claims that we might like to make about Linux as part of a system, and to explore how we can gather and present evidence to support such claims.
Linux Features for Safety-Critical Systems Working Group: This working group will work to bring together kernel developers and producers of safety critical systems to demonstrate use of such features in real systems, and to learn from these experiences together as a community.
If you want to learn more about these two new working groups, we invite you to the session on November 8 at 6-630 am PDT lead by Paul Albertella and Elana Copperman. Add this to your schedule here.
ELISA Ambassadors are technical leaders who are passionate about the mission of the ELISA Project, recognized for their expertise in functional safety and linux kernel development, and willing to help others to learn about the community and how to contribute.
Each month, we’ll put a spotlight on an ELISA Ambassador. Today, we’re excited to highlight Philipp Ahmann, ambassador and TSC member within the ELISA project as well as software manager at ADIT (a joint venture of Robert Bosch GmbH and DENSO Corporation).
Background Details:
Philipp Ahmann is manager at ADIT (a joint venture of Robert Bosch GmbH and DENSO Corporation) and has been participating in the ELISA project since the start.
He has more than ten years of experience in automotive infotainment base platforms, utilizing complex multi-core system-on-chips (SoCs). Also, he is leading a group of engineers who are responsible for software integration (CI/CD), testing, development infrastructure and tooling within ADIT.
His automotive expertise started with integration of components in SoC hardware and printed circuit board (PCB) design for the same. From there, Philipp moved over to the field of software development with initial responsibility for bootloader and Linux software board bringup.
After working within the Linaro community and several years as lead of the test development within ADIT, he became software project leader. The projects mainly target OSS based in-vehicle-infotainment base platforms on various hardware variants. Nowadays also build infrastructure as well as software base platforms for autonomous driving products are in his responsibility.
Q&A
How long have you been active in open source?
My first open source work was done as a user. While I was studying in Sweden in 2006, a friend and I collected old university PCs from the electronic scrap and installed Ubuntu 6.10 on them. Afterwards we maintained and distributed them to exchange students who couldn’t afford an own laptop or PC.
Really active in open source, I became a member of the Freescale landing team within Linaro in 2011 to drive ARM Kernel and BSP development for i.mx6 SoC forward.
Tell us about your favorite open source project and what problems did it aim to solve?
It is really hard to define my favorite open source project as they are everywhere in my life. My private NextCloudPi gives me full control over my data. Home Assistant integrated perfectly with ESPHome and is helping me to automate tasks in my flat and surrounding for higher convenience and energy savings. LineageOS, CarbonROM, /e/ brought back new life to old smartphones serving as daily drivers for my kids and parents making technology more sustainable.
Thanks to projects likes Linux Mint, which shows decent performance even on old devices, old PCs and laptops get a second life. On devices tools like LibreOffice, Red Notebook, Freeplane, Arduino IDE, VS Code and others, help me to structure my day and increase productivity. For fun and entertainment there are projects such as Kodi and RetroPie.
Overall, I am pretty sure everyone touches open source at one time or another, since open source software rules the world. It is there, where people need it. From the people for the people. A big thanks and kudos to all of you who participate in open source projects.
What roles and/or working groups do you have or participate in?
I host meetings, act as moderator, write minutes and jump in where I can help to drive topics forward and where my support is needed or wished. For technical content, I mainly contribute within the Automotive Working Group, where I benefit from my many years background in Linux for Automotive.
Where do you see the ELISA Project in three years?
Since I am primarily active in the Automotive WG, I would like to try to make a forecast for this group. In 3 years, we will have completed and showcased our first use case, which is a telltale application.The created work products will act as a blueprint to get the first fully Linux-based instrument cluster on the market.
What is the biggest strength of the ELISA community?
The biggest strength of the ELISA community is the diversity, which we achieve with experts from many different working fields, domains, industries and interests from all across the globe. The diversity of perspectives, coupled with the transparency and communication, is crucial to the success of safety relevant projects. By sharing our concepts, we get a lot of feedback from e.g. the Linux and the safety community. Of course there are passionate in-depth difficult discussions, but these are open and not driven by commercial interests. Risks, potential gaps or also any other concern is addressed from the beginning.
If we continue on this path, the results from the ELISA community can act as state-of-art technology and as a benchmark for many safety critical systems in the future. We contribute to a safer world.
What’s your favorite quote?
“Be yourself (no matter what they say)” – by Sting
3 Fun Facts:
I once repaired an entertainment system of a plane during the flight and asked the pilot if he could use the internet connection in the cockpit to search for a Windows NT dll file for me. If you are curious about the root cause, get in touch with me.
Already twice I have been on an overseas business trip and my luggage was delayed for so long that it got delivered only the day before departing again. Luckily, I bought at least a T-Shirt in Paris before going to NYC.
I built an Arudino based music player with RFID and arcade button control. It took me a year from the first PoC to be robust enough for my kids. At the time I was done, my daughter learnt how to use an Android phone and preferred a touch display and cover flow. So I put a custom rom on a phone, flashed it, and removed any unintended services to make it a kids-ready data-privacy device. This took me only a week in the end.
To learn more about ELISA ambassadors, please click here.