|
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
## General information
|
|
|
|
|
|
|
|
* Dates: 4&5 February 2023
|
|
|
|
* Website: https://fosdem.org/2023/
|
|
|
|
* Location: Brussels
|
|
|
|
|
|
|
|
## Participants list
|
|
|
|
|
|
|
|
| Name | Affiliation | Arrival date | Departure date | Hotel | Open to participate at EF booth? | Note |
|
|
|
|
| ------ | ------ |------ | ------ | ------ |------ | ------ |
|
|
|
|
| Agustin Benito B. | EF | Thu Feb 2 | Mon Feb 6 | | Yes | Attending to EU policy summit |
|
|
|
|
| | | | | | |
|
|
|
|
|
|
|
|
## Call for paper
|
|
|
|
|
|
|
|
* Details for CFP: https://fosdem.org/2023/news/2022-11-07-accepted-developer-rooms/
|
|
|
|
* The final deadline is **15th December** but some tracks may close earlier if they fill up or the respective call for papers specifies an earlier date.
|
|
|
|
|
|
|
|
<table>
|
|
|
|
<tr>
|
|
|
|
<th>Title</th>
|
|
|
|
<th>Speaker</th>
|
|
|
|
<th>Abstract</th>
|
|
|
|
<th>Status</th>
|
|
|
|
<th>Devroom</th>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td>Production-geared Open Source, from innovation to sustainability engine</td>
|
|
|
|
<td>Davide Ricci</td>
|
|
|
|
<td>Open Source has been a thing for developers for quite a long time, supporting rapid innovation and encouraging open-source software consumption by any industry. Companies, small and big alike, have been investing in open source mostly to reduce the costs of development and shorten the time to market. However, innovation and development costs (R&D costs) only account for a fraction of the total cost of ownership of software, while the vast majority of costs, such as long-term maintenance, certifications, standardization, and license compliance, ... have been carried entirely downstream by the consumers (broadly speaking, meaning consumers of open source software such as device makers, system integrators, etc.). Now all this is up for a change, and under the industry and regulatory push, the role of Open Source is changing, complementing Open Source communities and projects with tools, development processes, production-geared artifacts such as FOSS 3rd party notice files, testing verification, and validation reports, predictable roadmaps, clear indications of supported vs. unsupported functionalities, certification artifacts, etc. Open Source foundations are evolving, too, and play a crucial role in providing a vendor-neutral environment that promotes and mitigate the risk of those who invest in supporting such a shift. This presentation will walk the audience through the main drivers of open source thus far (including business drivers for big companies to invest), the new driver and push toward production-geared open source, the role of companies, foundations, the areas of "productization," etc</td>
|
|
|
|
<td>rejected</td>
|
|
|
|
<td>main track</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td>EDDIE - Enabling Distributed Intelligence in Oniro</td>
|
|
|
|
<td>Stefan Schmidt</td>
|
|
|
|
<td>The EDDIE project at the Eclipse Foundation has the objective to design a middleware capable of giving to the applications and services an unified global view on cross-device resources. The various devices are not seen any more as individual entities with specific resources, but as a unified pool of virtual resources. It will show the status on Linux and Zephyr in Oniro. The CoAP based communication layer, resource directory, and JSON-based ontologies for describing resources will be explained. Intelligent orchestration of the available resources will allow an efficient use and some very unique use cases e.g. peripherals like camera, storage and audio from any device in the network could operate like a local peripheral. They would be instantly compatible with your local applications. Use your doorbell camera in your mobile camera application without the need for dedicated integrations for each ecosystem.</td>
|
|
|
|
<td>rejected</td>
|
|
|
|
<td>lightning track</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td>Matter and Thread as Connectivity Solution for Embedded</td>
|
|
|
|
<td>Stefan Schmidt</td>
|
|
|
|
<td>
|
|
|
|
|
|
|
|
Matter is the kid in town when it comes to IoT protocols. As an application layer protocol based on IPv6 it aims to be the language for IoT devices. With Thread it supports a low-power wireless protocol which allows sleepy devices to operate on a coin cell battery for years and still allow end-to-end connectivity. This talk will look at the technology in Thread and Matter and its open source implementations. Topics include mesh capabilities of Thread, the border router and service discovery.
|
|
|
|
|
|
|
|
Based on my OpenThread FOSDEM talk from last year this shows an extended blueprint we created for the Oniro project to provide a connectivity solution for embedded devices running Linux or Zephyr. The Matter specification, together with an open source SDK, got just released in October 2022. As Matter is based on IPv6 it can run over a different number of connectivity solutions. From the start it supports Ethernet, Wi-Fi and Thread. The later being a low-power wireless protocol for a few years already, but without to much traction. With Matter support this might change in 2023 and forward. With border router support in popular devices like Apple Homepod and TV, Google Nest and Wi-Fi or Eero access points the needed technology infrastructure will become available in normal households.
|
|
|
|
</td>
|
|
|
|
<td>accepted</td>
|
|
|
|
<td>embedded devroom</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td>Developing an Embedded IoT Platform: The Open Source Way</td>
|
|
|
|
<td>Ettore Chimenti</td>
|
|
|
|
<td>
|
|
|
|
|
|
|
|
A story told by an industrial IoT device maker. In a world where fragmentation and lack of standards is growing, providing OS distros for custom embedded devices is just a commodity, and taken for granted by customers. However, every device maker has to provide it to their own clients in order to evaluate devices and start developing applications. Indeed creating and maintaining an ecosystem for many IoT products is undoubtedly expensive and hard. In this talk we will go through the effort to tackle this problem using an Open Source approach and what are our steps to improve the situation by adopting a sustainable method.
|
|
|
|
|
|
|
|
In the last few years we are witnessing an exponential growth in the industrial IoT market, and device makers are increasing the number of projects, designs and devices. It is important to provide an easy to use, standard, flexible and reliable distribution in order to give customers an IoT-ready ecosystem to start developing their solutions. Nonetheless, the effort to create a common distribution to support several combinations of hardware is huge and time consuming. There is no easy solution, but we can improve the situation by adopting Open Source solutions and actively maintaining the codebase that provides common and vendor-neutral features. In this talk I will tell the lessons learned of a device maker company in the journey of developing an Open Source Platform to enable Embedded Devices for IoT applications.
|
|
|
|
</td>
|
|
|
|
<td>Rejected</td>
|
|
|
|
<td>embedded devroom</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td>
|
|
|
|
|
|
|
|
_A complete compliance toolchain for Yocto projects (even very large ones, yes)_
|
|
|
|
</td>
|
|
|
|
<td>
|
|
|
|
|
|
|
|
Carlo PIana
|
|
|
|
|
|
|
|
Alberto Pianon
|
|
|
|
</td>
|
|
|
|
<td>Presenting the toolchain that we have created for Eclipse Oniro, we believe the single largest compliance effort by many metrics ever attempted for Yocto projects, featuring besides than the usual suspects (Fossology, Scancode, SPDX, BANG, Gitlab CI) some specifically developed tools, including a dashboard, aliens4friends, a graph database to map dependencies and license incompatibilities, a license resolver and way more.</td>
|
|
|
|
<td>Accepted</td>
|
|
|
|
<td>Software Bill of Material DevRoom</td>
|
|
|
|
</tr>
|
|
|
|
</table>
|
|
|
|
|
|
|
|
## Stand
|
|
|
|
|
|
|
|
Eclipse Foundation have an [stand at FOSDEM 2023](https://fosdem.org/2023/news/2022-12-08-accepted-stands-fosdem-2023/). Oniro has requested to have a demo at the stand on Saturday and Sunday. It might be that, given the demand, we would have to restrict our demo to a single day.
|
|
|
|
|
|
|
|
### Oniro demo at EF stand |
|
|
\ No newline at end of file |
