We would like to introduce to you Software Mansion and talk a little about our involvement in the Open Source community and our role in the React Native eco-system.
We will tell you why React Native for Oniro is a good idea and how do we contribute to the development of Open Harmony.
There is perhaps no greater shared challenge facing our world today than climate change. If we are to address this issue, we must collectively improve the technologies we both create and use to help improve the world. From increasing their energy efficiency to using them for protecting the wild, open source has a key role to play in building technologies for a sustainable future.
While most connected devices are headless, some of them expose a graphical interface for users to interact with. Oniro provides several approaches for human/machine interaction, from local basic display to full featured remote control.
This talk will focus on displaying data on Oniro devices depending on use cases or devices' constraints.
Oniro is an ambitious Eclipse project, one of its challenges is to defragment existing IoT ecosystems.
In the Eclipse Oniro project, along the distributed OS for consumer electronics, we're proposing a collection of "blueprints" use cases and their implementations using embedded software on reference hardware.
Those minimal viable products are not only used for demonstration or validation purposes, but they can serve as a base to create production-ready solutions.
Many embedded systems are held back by the fact that they use ancient toolchains - often because that's what's provided by chipset makers as part of a BSP. Here's how we solve the problem in the Eclipse Oniro project - and how other IoT/embedded systems projects inside Eclipse can benefit.
The target audience is people working on IoT/Edge/embedded systems projects (including automotive) who want to know about toolchains and crosscompilers for their target devices. There are often better options than using a hardware vendor provided BSP.
Exploring high-end solutions for building at scale and testing your project on real hardware in an integrated streamlined pipeline. We will talk about TuxSuite in general, how it can be aplied to any EF Arm-based project and LAVA/SQUAD integration with Gitlab inside the EF's Oniro project with visualization examples.
Participants should be familiar with OE build systems and development pipelines in general.
In a world that is constantly changing, we believe that it is essential to drive forward a technology concept that specifically and deeply meets the consumers, devices makers and developers needs.
Panel including Member representatives of the Oniro project. Using the the information provided by the IoT & Edge Commercial Adoption report as starting point, the participants in the panel will describe some of the challenges they predict they wil be facing in the coming 2-3 years as well as how they envision open collaboration in an organization like Eclipse Foundation as a key factor..
Through the conversation, atendees will get an idea of the direction the project will go in the coming couple of years.
How does a testing team approach an Open Source project? There are two ways to do it: a reactive and a proactive approach.
In this talk we would like to present our proactive approach executed in the Oniro project and the beneficial effects that this approach gives to the product. We will compare this methodology with the reactive one and how it will improve the overall project quality.
This talk shall target Project Managers, Team Leaders and V&V People.
Real-Time Operating Systems (RTOS) are at the core of several constrained devices. Popular open-source options such as FreeRTOS and Zephyr support a wide range of hardware and provide features such as storage and networking. They also provide integration with wireless technologies such as Bluetooth and NFC. However, many open source projects aim to deliver the same features in a "bare metal" approach. In other words: they deliver frameworks that enable your applications to run directly on the hardware. Given this, which approach is right for your IoT project?
