SBOMs Supporting Safety Critical Software

By

-

March 21, 2022

A software bill of materials (SBOM) is a way of summarizing key facts about the software on a system. At the heart of it, it describes the set of software components and the dependency relationships between these components that are connected together to make up a system.

Modern software today consists of modular components that get reused in different configurations. Components can consist of open source libraries, source code or other external, third-party developed software. This reuse lets innovation of new functionality flourish, especially as a large percentage of those components being connected together to form a system may be open source. Each of these components may have different limitations, support infrastructure, and quality levels. Some components may be obsolete versions with known defects or vulnerabilities. When software runs a critical safety system, such as life support, traffic control, fire suppression, chemical application, etc., being able to have full transparency about what software is part of a system is an essential first step for being able to do effective analysis for safety claims.

Why is this important?

When a system has functionality incorporated that could have serious consequences in terms of a person’s well being or significant loss, the details matter. The level of transparency and traceability may need to be at different levels of details based on the seriousness of the consequences.

Source: NTIA’s Survey of Existing SBOM Formats and Standards

What does this have to do with Safety Critical Development?

Safety Standards, and the claims necessarily made against them, come in a variety of different forms. The safety standards themselves mostly vary according to the industry that they target: Automotive uses ISO 26262, Aviation uses DO 178C for software and DO 254 for hardware, Industrial uses IEC 61508 or ISO 13849, Agriculture uses ISO 25119, and so on. From a software perspective, all of these standards work from the same premise that the full details of all software is known: The software should be developed according to a software quality perspective, with additional measures added for safety. In some instances these additional safety measures come in the form of a software FMEA (Failure Modes and Effects Analysis), but in all of them, there are specific code coverage metrics to demonstrate that as much of the code as possible has been tested and that the code complies with the requirements.

Another item that all safety standards have in common is the expectation that the system configuration is going to be managed as part of any product release. Configuration management (CM) is an inherent expectation in software already, but with safety this becomes even more crucial because of the need to track exactly what the configuration of a system (and its software) is if there is a subsequent incident in the field while the system is being used. From a software perspective, this means we need several things:

The source code at the time of release
The documentation associated with it
The configuration used to build the software
The specific versions of the tools used to build the software

The goal, then, is to be able to rebuild exactly what the executable or binary was at the time of release.

From the above, it is inherently obvious how the SBOM fits into the need for CM. The safety standards CM requirements, from a source code and configuration standpoint, are greatly simplified by following an effective SBOM process. An SBOM supports capturing the details of what is in a specific release and supports determining what went wrong if a failure occurs.

Because software often relies upon reusable software components written by someone other than the author of the main system/application, the safety standards also have a specific expectation and a given set of criteria for software that you end up including in your final product. This can be something as simple as a library of run-time functions as we might expect to see from a run-time library, to something as extensive as a middleware that manages communication between components. While the safety standards do not always require that the included software be developed in accordance with a safety standard, there are still expectations that you can prove that the software was developed at least in compliance with a quality management framework such that you can demonstrate that the software fulfills its requirements. This is still predicated on the condition that you know all of the details about the software component and that it fulfills its intended purpose.

The included software components can be from:

Third parties
Existing SW not developed according to a safety standard
Internally developed software already in use

Regardless of the source or current usage of the software, the SBOM should describe all of the included software in the release.

To this end, the safety standards expect that the following is available for each software component included in your project:

Unique ID, something to uniquely identify the version of the software you are using. Variations in releases make it important to be able to distinguish the exact version you are using. The unique ID could be as simple as using the hash from a configuration management tool, so that you know whether it has changed.
Any safety requirements that might be violated if the included software performs incorrectly. This is specifically looking for failures in the included software that can cause the safety function to perform incorrectly. (This is referred to as a cascading failure.)
Requirements for the software component
- This should include the results of any testing to demonstrate requirements coverage
- Coverage for nominal operating conditions and behavior in the case of failure
- For highly safety critical requirements, test coverage should be in accordance with what the specification expects (e.g., Modified Condition/Decision Coverage (MC/DC) level code coverage)
The intended use of the software component
The component’s build configuration (how it was built so that it can be duplicated in the future)
Any required and provided interfaces and shared resources used by the software component. A component can add demand for system-level resources that might not be accounted for.
Application manual (documentation)
Instructions on how to integrate the software component correctly and invoke it properly
What the software might do under anomalous operating conditions (e.g., low memory or low available CPU)
Any chained dependencies that a component may require
Any existing bugs and their workarounds

Conclusion

At a minimum, the SBOM describes the software component, supplier and version number, with an enumeration of the included dependent components. This is what is being called for in the minimum viable definition of an SBOM to support cyber security[1] or safety critical software[2].

Having a minimum level of information, while better than nothing, is not sufficient for the level of analysis that safety claims expect. Knowing exactly which source files were included in the build is a better starting point. Even better still is knowing the configuration options that were used to create the image (and be able to reproduce it), and being able to check via some form of integrity check (like a hash) that the built components haven’t changed is going to be key to having a sound foundation for the safety case. SBOMs need to scale from the minimum, to the level of detail necessary to satisfy the safety analysis.

While SBOM tooling may not be able to populate all of this information today, the tools are continuing to evolve so that the facts necessary to support safety analysis can be made available. An international open SBOM standard, like SPDX[3] can become the baseline for modern configuration management and effective documentation of safety critical systems.

[1] The Minimum Elements For a Software Bill of Materials (SBOM) from NTIA

[2] ISO 26262:2018, Part 8, Clause 12 – Qualification of Software Components

[3] ISO/IEC 5962:2021 – Information technology — SPDX® Specification V2.2.1

Authors

Peter Brink, Functional Safety Engineering Leader, kVA by UL, Underwriters Laboratories (UL)

Kate Stewart, VP Dependable Embedded Systems, The Linux Foundation

Linux troubleshooting commands: 4 tools for DNS name resolution problems

By

-

March 20, 2022

Find out what’s stopping you from accessing a server, printer, or another network resource with these four Linux troubleshooting commands.

Read More at Enable Sysadmin

How to deploy an Apache web server quickly

By

-

March 20, 2022

Install, configure, and test a very basic web server deployment in just eight steps.

Read More at Enable Sysadmin

LF Energy: Solving the Problems of the Modern Electric Grid Through Shared Investment

By

adavis

-

March 17, 2022

lf energy paving the way to battle climate. woman checking wind turbines.

Arresting climate change is no longer an option but a must to save the planet for future generations. The key to doing so is to transition off fossil fuels to renewable energy sources and to do so without tanking economies and our very way of life.

The energy industry sits at the epicenter of change because energy makes everything else run. And inside the energy industry is the need for a rapid transition to electrification and our vast power grids. Like it or not, utilities face existential decisions on transforming themselves while delivering ever more power to more people without making energy unaffordable or unavailable.

The challenges are daunting:

How to move away from fossil fuels without crashing the global economy that is fueled by energy?Is it possible to speed up the modernization of the electric grid without spending trillions of dollars?Can this be done while ensuring that power is safe, reliable, and affordable for all?

These are all significant problems to solve and represent 75% of the problem in combating climate change through decarbonization. In the Linux Foundation’s latest case study, Paving the Way to Battle Climate Change: How Two Utilities Embraced Open Source to Speed Modernization of the Electric Grid, LF Energy explores the opportunities for digital transformation within electric utility providers and the role of open source technologies in accelerating the transition.

Download Case Study

Open Source meets climate change challenges with LF Energy

The growth of renewable energy sources is making the challenges of modernizing the modern grid more complicated. In the past, energy flowed from coal and gas generating plants onto the big Transmission System Operator (TSO) lines and then to the smaller Distribution System Operator (DSO) lines to be transformed into a lower voltage suitable for homes and businesses.

But now, with solar panels and wind turbines increasingly feeding electricity back into the grid, the flow of power is two-way.

This seismic shift requires a new way of thinking about generating, distributing, and consuming energy. And it’s one that open source can help us navigate.

Today, energy travels in all directions, from homes and businesses, and from wind and solar farms, through the DSOs to the TSOs, and back again. This fundamental change in how power is generated and consumed has resulted in a much more complicated system that utilities must administer. They’ll require new tools to guarantee grid stability and manage the greater interaction between TSOs and DSOs as renewables grow.

Open source software allows utilities to keep up with the times while lowering expenses. It also gives utilities a chance to collaborate on common difficulties rather than operating in isolation.

The communities developing LF Energy’s various software projects provide those tools. It’s helping utilities to speed up the modernization of the grid while reducing costs. And it’s giving them the ability to collaborate on shared challenges rather than operate in silos.

Two European utility providers, the Netherlands’ Alliander and France’s RTE are leading the change by upgrading their systems – markets, controls, infrastructure, and analytics – with open source technology.

RTE (a TSO) and Alliander (a TSO) joined forces initially (as members of the Linux Foundation’s LF Energy projects) because they faced the same problem: accommodating more renewable energy sources in infrastructures not originally designed for them and doing it at the speed and scale required. And while they are not connected due to geography, the problems they are tackling apply to all TSOs and DSOs worldwide.

Two electric utility providers collaborate on shared technology investments, together

The way that Alliander and RTE collaborated via LF Energy on a project known as Short Term Forecasting, or OpenSTEF, illustrates the benefits of open source collaboration to tackle common problems.

“Short-term forecasting, for us, is the core of our existence,” According to Alliander’s Director of System Operations, Arjan Stam. “We need to know what will be happening on the grid. That’s the only way to manage the power flows,” and to configure the grid to meet customer needs.“The same is true for RTE and “every grid operator across the world,” says Lucian Balea, RTE’s Director of Open Source.

Alliander has five people devoted to OpenSTEF, and RTE has two.

Balea says that without joining forces, OpenSTEF would develop far less quickly, and RTE may not have been able to work on such a solution in the near term.

Since their original collaboration on OpenSTEF, they have collaborated on additional LF Energy Projects, CoMPAS, and SEAPATH.

CoMPAS is Configuration Modules for Power industry Automation Systems, which addresses a core need to develop open source software components for profile management and configuration of a power industry protection, automation, and control system. ComPAS is critical for the digital transformation of the power industry and its ability to move quickly to new technologies. It will enable a wide variety of utilities and technology providers to work together on developing innovative new solutions.

SEAPATH, Software Enabled Automation Platform and Artifacts (THerein): aims to develop a platform and reference design for an open source platform built using a virtualized architecture to automate the management and protection of electricity substations. The project is led by Alliander, with RTE and other consortium members contributing.

As we move to a decarbonized future, open source will play an increasingly important role in helping utilities meet their goals. It’s already helping them speed up the grid’s modernization, reduce costs, and collaborate on shared challenges. And it’s only going to become essential as we move toward a cleaner, more sustainable energy system.

Read Paving the Way to Battle Climate Change: How Two Utilities Embraced Open Source to Speed Modernization of the Electric Grid to see how it works and how you and your organization may leverage Open Source. Together, we can develop solutions.

Subscribe to LF Research

The post LF Energy: Solving the Problems of the Modern Electric Grid Through Shared Investment appeared first on Linux Foundation.

Looking to Hire or be Hired? Participate in the 10th Annual Open Source Jobs Report and Tell Us What Matters Most

By

adavis

-

March 17, 2022

Last year’s Jobs Report generated interesting insights into the nature of the open source jobs market – and informed priorities for developers and hiring managers alike. The big takeaway was that hiring open source talent is a priority, and that cloud computing skills are among the top requested by hiring managers, beating out Linux for the first time ever in the report’s 9-year history at the Linux Foundation. Here are a few highlights:

Now in its 10th year, the jobs survey and report will uncover current market data in a post-COVID (or what could soon feel like it) world.

This year, in addition to determining which skills job seekers should develop to improve their overall employability prospects, we also seek to understand the nature and impact of the “Great Resignation.” Did such a staffing exodus occur in the IT industry in 2021, and do we expect to feel additional effects of it in 2022? And what can employers do to retain their employees under such conditions? Can we hire to meet our staffing needs, or do we have to increase the skill sets of our existing team members?

The jobs market has changed, and in open source it feels hotter than ever! We’re seeing the formation of new OSPOs and the acceleration of open source projects and standards across the globe. In this environment, we’re especially excited to uncover what the data will tell us this year, to confirm or dispel our hypothesis that open source talent is much in demand, and that certain skills are more sought after than others. But which ones? And what is it going to take to keep skilled people on the job?

Only YOU can help us to answer these questions. By taking the survey (and sharing it so that others can take it, too!) you’ll contribute to a valuable dataset to better understand the current state of the open source jobs market in 2022. The survey will only take a few minutes to complete, with your privacy and confidentiality protected.

Thank you for participating!

Take 10th Annual Survey (Click)

Who We Are Looking To Participate

Employers
Hiring Managers
Human Resources Staff
Job Seekers
IT Directors and IT Management
IT Training Developers and Training Providers

Project Leadership

The project will be led by Clyde Seepersad, SVP & General Manager of Linux Foundation Training & Certification, and Hilary Carter, VP Research at the Linux Foundation.

The post Looking to Hire or be Hired? Participate in the 10th Annual Open Source Jobs Report and Tell Us What Matters Most appeared first on Linux Foundation.

The Linux Foundation Welcomes New Board Members from Ericsson, Fujitsu, Meta, Panasonic, Sony, and VMWare

By

-

March 15, 2022

The Linux Foundation’s Board of Directors represents a cross-section of our membership–from different industries with different backgrounds and expertises. This broad, diverse group works hard to ensure the Linux Foundation is achieving its mission to unlock the power of open technology to drive shared innovation for the collective benefit. Their expertise, passion, and work is essential to our joint successes.

Some of the Board is elected by the other members and their terms are limited. The Board also has turnover as executives in our members’ companies change roles. This year we welcome five new members to the Board. We are excited for the breadth of experience that will make the work we all do more impactful. Read more about each one:

Suzanne Ambiel is an 11-year veteran of VMware and “experienced traveler” in the technology space, Suzanne caught the open source bug late in life, but now considers herself “all in” thanks to a few inspiring, influential, and patient leaders. During work hours, you’ll find Suzanne playing dual roles — behind the scenes of VMware’s Open Source Program Office and in VMware’s Brand & Creative team. But when the whistle blows, she’s likely out riding the trails, walking her two dachshunds, or pondering why her sourdough didn’t rise (again).

Tim Bird is a longtime Linux kernel developer, with over 25 years experience with the Linux kernel and open source community. He is a principal software engineer and general Open Source technologist at Sony Corporation. Over the last 2 decades he has been involved with many projects in the Linux Foundation and other trade associations to enhance Linux for use in embedded and consumer electronics products. Tim is the founder of the Embedded Linux Conference and the elinux wiki. He recently served on the Linux Foundation Technical Advisory Board, and was previously the CTO of Lineo, an early embedded Linux company.

Ben Maurer is a software engineer at Meta focusing on privacy and security. He joined Meta in 2010 as a member of the infrastructure team where he played a key role in driving the performance and reliability of Meta’s products. Over the course of his time at the company, Ben has worked on several technologies that Meta has open sourced, including jemalloc, Folly, Thrift, and HHVM. He has also built deep partnerships with the open source community such as bringing Restartable Sequences to the Linux kernel and building a team within Meta dedicated to contributing to open source web browsers. Ben is one of the co-creators of the Diem blockchain and led Meta’s technical contributions to the project.

Ben also worked at the White House in 2014 as part of the U.S. Digital Service where he improved the communication tools used by the President and his staff.

Before joining Meta, Ben was an engineer at Google after the company acquired the startup he co-founded, reCAPTCHA, a system that determines if a user is human while simultaneously digitizing books. Ben has also contributed to the Mono and GNOME open source projects.

Shojiro Nakao is a general manager of the R & D Division of the Automotive Company of Panasonic. He is responsible for the development and management of automotive software platforms. He has been working with Linux for over 15 years, in a variety of product development, including mobile, IoT, and automotive devices. Responsible for software platform development, he has been promoting Panasonic’s collaboration with various open source communities. In addition, he is a steering committee member of Automotive Grade Linux.

Phil Robb is the Acting Head of Ericsson Software Technology (EST), where he leads a passionate group of engineers developing open source software across a wide range of projects including Linux, OpenStack, Kubernetes, and ONAP among many others.

Prior to Ericsson, Phil was the V.P. of Operations for the Networking Projects at the Linux Foundation including ORAN, ONAP, OpenDaylight, and Anuket. In that role, Phil led a team of technical staff who oversaw community software development based on DevOps and open source best practices. Prior to the Linux Foundation, Phil spent 12 years with Hewlett Packard working on Linux and Open Source starting in 2001. There, Phil formed and led HP’s Open Source Program Office responsible for open source strategy, tools, processes, and investments as HP transitioned from Unix to Linux in the Enterprise Server market.

The post The Linux Foundation Welcomes New Board Members from Ericsson, Fujitsu, Meta, Panasonic, Sony, and VMWare appeared first on Linux Foundation.

Made by Technology

By

Linux.com Editorial Staff

-

March 15, 2022

Every historical moment is associated with its technology. The social, political, and economic practice of human beings depends mainly on the tools at their disposal. Their relationship with the environment around them, their knowledge of the world, and their worldview depend on technological prostheses that enable them to improve their perception, to understand the past, and above all, to foresee a plan for the future.

Moreover, technological development is the backbone of our understanding of the 21st century. The new technologies define our era and make it possible to understand the creations of contemporary human beings: their science, their way of living, their cultural habits, so on.

Contemporary humankind is impossible to be understood without the constant company of technology that allows them to improve and expand their senses. Today, technology has become an extension of the human body.

The human being today is a subject made by technology. Men and women have thus shown themselves to be irremediably permeable to technology, a technology that goes beyond them. The main question is: who is in charge of this factory? With what interests? Who is making us? Who is designing us?

Utopia and dystopia

Since August 1991, when the World Wide Web was made public as a service, the Internet has spread all over the planet and become famous. The first heroic times led to the birth of an autonomous, free zone outside the control of the power of governments and large companies. A place in which to create and communicate without restrictions. A vast blank page on which to start building.

However, the idea of collective intelligence was gradually eroded by the advance of simplifying globalization, ultimately capable of fostering unidirectional and unidimensional currents of communication contrary to the illusionary possibilities from which it started. At the same time, we assist in the triumphal beginning of “democracy,” a new kind of power based on the control (monopoly) of specific tools.

In the end, the medium prevailed over the messages, and the “wall” of the social networks ended up being a torrent of disinformation and banalities. The Internet thus became a way of looking at oneself in a mirror, of forming a continuous selfie based on not seeing beyond prejudice and the saturation of information and images—a tool of individualism and separation from reality. And, what is even worse, an infinite source of personal data to be traded.

Collaboration against individualism

Against the main currents determined by tech giants, there are still many possibilities of using the ways in alternative ways, understanding the vast opportunities open by technologies, some usually forgotten by people.

Facing the idea of an Internet of massive and monolithic movements, there is another open possibility: the return to the collective, to the community, and its needs. Open source thus becomes the counterweight to the dangers of indiscriminate use and the generation of information noise on the Internet.

Open-source projects refer to software development with a license that gives access to the source code so that programmers can freely use, write, modify, and redistribute the code. Open source is developed collaboratively and distributed over the Internet. It allows generating a product with a continuous improvement from the hand of a dedicated community.

AsyncAPI is a project that considers that human beings have naturalized the tools that enhance their capacities. Technology can guide us and define our steps. It’s not merely daily practice. We should be more aware that we humans make technology and that we are the ones who create and determine the future it holds for us. We are the ones who build the future.

The light between the walls

Transparency and horizontality are the axes on which this movement is settled. The absolute exposure of a project or company’s work, economy, and politics in a society with such opaque foundations represent a return to the initial roots of the Internet. In this autonomous zone, projects are built from the ground up.

Doing things following the open-source philosophy promotes a working system based on the open exchange of ideas, teamwork-based on flexibility, and constant innovation.

This working model clashes head-on with a system based mainly on competitiveness and concealment. It appears a stepping stone to repeal opaque and oppressive government models and a step towards a freer, more transparent, and equitable society.

Collaborating in an open-source project offers you the opportunity of a community of people involved and enthusiastic about the same goal. At AsyncAPI, everyone is welcome, regardless of their sector, their experience… all you need is enthusiasm. This enthusiasm is based on the idea that another world is possible, even more so in times of climate emergency and global crisis. Technology is the only tool in our hands to shape it. It is the key element of cultural, social, and political struggle. It cannot be left in other hands. It must be built collectively, with the community’s needs and users in mind.

You don’t take technology; you make it.

The author, Barbaño González, is Education Program Manager at AsyncAPI.

Academy Software Foundation: Digital Transformation of the Entertainment Industry is Driven by Open Technology and a Visionary, Inclusive Community

By

-

March 15, 2022

In a new case study released by Linux Foundation Research, in collaboration with the Academy Software Foundation, entitled Open Source in Entertainment: How the Academy Software Foundation Creates Shared Value, we learn a compelling story of how open technology and the people who create visual effects (VFX) for motion pictures transformed a highly competitive industry.

Download Report

The Academy Software Foundation (ASWF) was formed as an entertainment industry collaboration with the Academy of Motion Picture Arts & Sciences, the organization behind the Academy Awards (aka the Oscars). ASWF has been steadily releasing software projects contributed since its inception in 2018. Four projects are fully adopted, and six are in incubation.

Adopted Projects

OpenVDB is an industry-standard library for manipulating sparse dynamic volumes used by visual effects studios to create realistic volumetric images such as water/liquid simulations and environmental effects like clouds and ice.

OpenColorIO is an industry standard for consistent color management across VFX and animation pipelines used on hundreds of feature film productions. It touches nearly every pixel of every visual effects frame in most major motion pictures.

OpenEXR is a standard HDR image file format for high-quality image processing and storage, one of the foundational technologies in computer imaging.

OpenCue is an open source render management system used to break down complex jobs into individual tasks.

Incubating Projects

OpenTimelineIO is an Open Source application programming interface and interchange format for editorial timeline information.

Open Shading Language (OSL) is the de facto standard shading language for VFX and animation.

MaterialX is an open standard for exchanging rich material and look-development content across applications and renderers.

Rez is an open source, cross-platform package manager that creates standalone configured environments for third-party and proprietary digital content creation software.

DPEL is the Digital Production Example Library, which are digital sample assets that content creators can use for instructional purposes

RawtoACES is a software package that converts digital camera RAW files to ACES container files containing image data encoded according to the Academy Color Encoding Specification (ACES)

The entertainment industry now has a home, process, and governance structure to manage open source projects essential to movie, television, and gaming production. Any new project can be proposed, and projects are managed according to a project lifecycle policy that provides various requirements and project benefits. Many ASWF projects have been foundational to creating visual effects and major motion pictures in their entirety. These elements continue to thrill audiences around the world.

The ASWF has been steadily releasing new software projects since its inception in 2018.

In addition to hosting technologies for the entertainment industry, the ASWF provides a neutral forum to coordinate open source project efforts, a common build and test infrastructure, open governance, more consistent open source licensing, and a clear path to participation for individuals and organizations wanting to advance the open source ecosystem for the motion picture industry.

In doing so, the ASWF has brought together leading studios such as DreamWorks Animation, Sony Pictures Imageworks, Walt Disney Studios (including Pixar, LucasFilm, Industrial Light & Magic, Blue Sky Studios), Warner Bros., DNEG, Netflix, and technology vendors that support the film and gaming industries.

Open Source collaboration in the entertainment industry was not always such a pretty picture

Circa 2014, the motion picture industry faced fragmented software infrastructure issues, with proprietary solutions not based on open source software or running on open source operating systems. These platforms were also not providing the innovation needed to create the landmark films and television programs we enjoy today. So it necessitated that each VFX and film studio build their own tools.

The studios had a core desire to move from their closed systems to more open ones like Linux. However, the motion picture industry’s challenges were not about accepting open source software but about getting the industry ecosystem to participate and collaborate in open environments.

As we learn in the case study, at visual effects studios such as SONY Pictures and ILM, there were no common build systems outside any company’s networks, so it became increasingly difficult to figure out the proper instructions to build the open source software that any industry contributor had released.

It was challenging to align dependencies and versions, leading to “versionitis” as projects required different versions of dependencies. Additionally, when maintainers left a company that “owned the project,” the codebase languished – such was the case with SONY DreamWorks’ OpenColorIO and ILM’s OpenEXR software, as detailed in the report.

As a result, studios were reluctant to take dependence on other companies’ projects and even more unwilling to contribute their intellectual property back to another company’s project. Add in a layer of one-sided contribution agreements, modifications to standard open source licenses, and other legal impediments. It was clear the status quo could not scale to meet the industry’s growing needs.

The entertainment industry’s open source ecosystem depends on its people

As detailed in the report, the Academy and Linux Foundation spent nearly two years working with industry stakeholders to build a better, collaborative solution, resulting in the ASWF and its associated projects. None of the success that ASWF now enjoys would have been possible without the engineers, the software developers, and the filmmakers that support the underlying ecosystem. And participating in this ecosystem has tangible benefits for the contributors.

ASWF has also become a focal point for driving new interest in software development in the motion picture industry and recognizing the contributions of its community members thanks to the “Behind the Screens” interview series featuring over two dozen software developers in the industry, along with the launch of a Diversity and Inclusion working group to raise the profile of underrepresented people in these roles.

While the ASWF has made great strides since its inception in 2018, it is still a young organization but has found its place in the industry. Diversity and Inclusion initiatives are leading the way towards educating the entertainment industry to help them attract more diversity within its ranks. New efforts underway, such as DPEL (formerly Open Asset Repository), will provide sample content to breed and help new aspiring content creators learn the trade.

Why is this research so valuable? We’ve seen related examples in telecommunications, energy, automotive, and public health, where many of these projects started as individual efforts looking for a neutral home at the Linux Foundation. Over time, these communities of competitive contributors found it beneficial to collaborate.

Suhscribe to LF Research

Although the entertainment industry has unique requirements for its vertical applications, the story behind the creation of the ASWF can serve as a “roadmap” for leaders in other industries to get a win-win by shared investment and collaboration in open technologies. Open source in entertainment is another example of open source value creation. Read the full report HERE.

The post Academy Software Foundation: Digital Transformation of the Entertainment Industry is Driven by Open Technology and a Visionary, Inclusive Community appeared first on Linux Foundation.

Check your disk space use with the Linux df command

By

-

March 14, 2022

Learn how to use df and its various options to monitor disk usage on critical mount points.

Read More at Enable Sysadmin

How to specify the CPU architecture when pulling images with Podman

By

-

March 14, 2022

If you’re building multi-architecture solutions, you need to know how container image architectures work, how to pull them, and how to run containers on different systems using Podman.

Read More at Enable Sysadmin