<?xml version="1.0" encoding="UTF-8"?>
<schedule>
  <conference>
    <title>FOSDEM 2022</title>
    <subtitle/>
    <venue>ULB (Université Libre de Bruxelles)</venue>
    <city>Brussels</city>
    <start>2022-02-05</start>
    <end>2022-02-06</end>
    <days>2</days>
    <day_change>09:00:00</day_change>
    <timeslot_duration>00:05:00</timeslot_duration>
  </conference>
  <day index="1" date="2022-02-05">
    <room name="K.fosdem">
      <event id="13549">
        <start>09:00</start>
        <duration>00:20</duration>
        <room>K.fosdem</room>
        <slug>keynotes_welcome</slug>
        <title>Welcome to FOSDEM 2022</title>
        <subtitle/>
        <track>FOSDEM</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;FOSDEM welcome and opening talk.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Welcome to FOSDEM 2021!&lt;/p&gt;</description>
        <persons>
          <person id="6">FOSDEM Staff</person>
          <person id="497">Richard Hartmann</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/K.fosdem/keynotes_welcome.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/K.fosdem/keynotes_welcome.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#fosdem-keynotes:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#fosdem-keynotes:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#fosdem-keynotes_welcome:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#fosdem-keynotes_welcome:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13549.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="M.community">
      <event id="12835">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>M.community</room>
        <slug>community_sustainable</slug>
        <title>Making a community-managed FOSS project sustainable in the medium- to long-term</title>
        <subtitle>Strategies and tactics</subtitle>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;LibreOffice was announced in 2010. After 10 years, it was necessary to review and update the strategy based on the evolution of the office suite market, to improve the sustainability model. Enterprises are not supporting the project as much as individual users. Over time, this can represent a threat for the sustainability of the project. We have changed our strategy to educate enterprises about the right approach to FOSS, by giving back to ensure the long term sustainability of the LibreOffice project.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;LibreOffice was announced in 2010 to relaunch innovation of the already stagnant OpenOffice project. After 10 years of growth, it was necessary to review and update the strategy based on the evolution of the office suite market, to improve the sustainability model.
In fact, enterprises - although deploying LibreOffice to save money over proprietary solutions - are not supporting the project as much as individual users. Over time, this can represent a threat for the sustainability, as development can be slowed down.
We have therefore changed our strategy to educate enterprises about the right approach to FOSS, by giving back in one of the many available ways: purchase the LTS version from the ecosystem, fund the development of a specific feature, pay for the solution of a bug or a regression, and so on.
The right approach from enterprises would ensure the long term sustainability of the LibreOffice project, and the evolution of the Open Document Format (ODF) ISO standard file format for true interoperability.&lt;/p&gt;</description>
        <persons>
          <person id="312">Italo Vignoli</person>
        </persons>
        <attachments>
          <attachment type="audio" href="https://fosdem.org/2022/schedule/event/community_sustainable/attachments/audio/5230/export/events/attachments/community_sustainable/audio/5230/makingacommunitymanagedfossprojectsustainable.pdf">Making a community-managed FOSS project sustainable in the medium- to long-term</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.community/community_sustainable.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_sustainable.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12835.php">Submit feedback</link>
        </links>
      </event>
      <event id="12792">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>M.community</room>
        <slug>community_open_science</slug>
        <title>Empowered for Action: Making open Science Practical in the Global South.</title>
        <subtitle/>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;As research becomes more globalised and its output grows exponentially, especially in data, the need for open scientific research practices is more evident — the future of modern science. There is now a concerted global interest in open science uptake, but barriers exist. The formal training curriculum in most, if not all, universities in the global South do not equip students with the knowledge and tools to practice open science in their research or develop open-source tools.
To work openly, collaboratively, and build a community, there is a need for awareness and training in using and developing open science tools. Through the OpenScienceKE framework, we developed a model to narrow the gap: the sensitize-train-hack-collaborate model. Using the model, we sensitised through seminars, trained on the use of tools through workshops, applied the skills learned in training through hackathons to develop open-source tools collaboratively. In this talk, I will demonstrate the need to Contextualize open source to ensure that no one is left behind, especially the Global South, and highlight some of our work in building an empowered community.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8740">Caleb Kibet</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.community/community_open_science.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_open_science.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12792.php">Submit feedback</link>
        </links>
      </event>
      <event id="13008">
        <start>12:15</start>
        <duration>00:45</duration>
        <room>M.community</room>
        <slug>community_issue_backlog</slug>
        <title>We've got issues</title>
        <subtitle>or how we learnt to squish our bugs</subtitle>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;This is the story of how we harnessed the power of the community, automation and good habits to reduce our issue burden and helped users be heard.&lt;/p&gt;

&lt;p&gt;5 years into its life and with vast number of users users, Element - a Matrix messaging client available on most desktop platforms, Android and iOS - had a growing backlog of bugs and enhancement requests. This is a common challenge faced by projects as they mature. I will share some of our lessons learnt and good practices that we have developed, and how our enthusiastic community is helping catch bugs earlier and process our backlog. While we have made good progress, we recognise that there are still further improvements to be made and will share some of our ideas for the future.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8455">Kat Gerasimova</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.community/community_issue_backlog.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_issue_backlog.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13008.php">Submit feedback</link>
        </links>
      </event>
      <event id="12526">
        <start>13:00</start>
        <duration>00:45</duration>
        <room>M.community</room>
        <slug>community_contributions</slug>
        <title>Tearing down Barriers for Contributions by Non-coders and Newcomers</title>
        <subtitle/>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Contributions to Open Source Projects are always encouraged, especially from Newcomers and Non-coders. However, actually contributing as someone not familiar with the project, its workflows and its tools is usually everything but simple and requires a substantial time investment. This is especially the case if you are not a programmer or not as experienced with the technology in use, which can ultimately discourage otherwise potential willing contributors.&lt;/p&gt;

&lt;p&gt;This talk will illustrate concrete steps that you, the maintainers of Open Source Projects, can undertake to simplify the hoops one has to jump through for their first contribution. We will cover various tools that you can use for this, be it for communication, localization, editing or publishing, how to provide good introductory material and how to build a welcoming atmosphere.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7167">Dan Čermák</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://dcermak.github.io/fosdem_2022/enabling_contributions.html">Slides</link>
          <link href="https://video.fosdem.org/2022/M.community/community_contributions.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_contributions.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12526.php">Submit feedback</link>
        </links>
      </event>
      <event id="13047">
        <start>13:45</start>
        <duration>00:45</duration>
        <room>M.community</room>
        <slug>community_mental_health</slug>
        <title>Nurturing Developer Communities in Unprecedented Times</title>
        <subtitle/>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;While the coronavirus pandemic continues to send shockwaves throughout almost all industries, it’s important for developers to nurture their communities in a well-efficient way and prepare them for the future. The overwhelmed communication systems, improving remote culture, and fostering community coordination are the three main areas on which we need to focus on. It is important to recognize that community development is an organic process, the listed steps (not in order) are to be considered on how we empower people, communities, and the industries around us:&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Learn about the community
Listen to community members
Bring people together to develop a shared vision
Assess community assets and resources, needs and issues
Help community members to recognize and articulate areas of concern and their causes
Establish a 'vehicle for change’
Develop an action plan
Implement an action plan
Evaluate the results of actions
Reflect and regroup&lt;/p&gt;

&lt;p&gt;People want to live in resilient and healthy communities. Well-being and positive mental health start here. Further mental health services need to consider how they harness the assets and strengths of communities in developing approaches that empower people in their recovery journeys.&lt;/p&gt;</description>
        <persons>
          <person id="8715">Shivam Singhal</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.community/community_mental_health.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_mental_health.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13047.php">Submit feedback</link>
        </links>
      </event>
      <event id="12719">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>M.community</room>
        <slug>community_questions</slug>
        <title>How to ask Good Questions in Open Source Communities</title>
        <subtitle>Better questions leads to better answers, saves time and makes you more productive</subtitle>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Good questions lead to better answers.&lt;/p&gt;

&lt;p&gt;Asking good questions is a must have skill for software developers, especially if you are involved in open source projects. The problem with poor questions is clear when the person answering starts explaining what you already know or what you think isn't relevant. Or they might go ahead and assume that you know a lot and you end up being confused.&lt;/p&gt;

&lt;p&gt;In this talk, Navendu walks through his experience as an open source contributor and a maintainer and how he was able to improve this skill and how it has benefitted him.&lt;/p&gt;

&lt;p&gt;This quick session is for junior and senior developers alike and offers real examples and takeaways that you can start implementing right away.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8697">Navendu Pottekkat</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.community/community_questions.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_questions.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12719.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="M.misc">
      <event id="12513">
        <start>12:00</start>
        <duration>00:30</duration>
        <room>M.misc</room>
        <slug>misc_databases</slug>
        <title>State of Open Source Databases</title>
        <subtitle>A discussion on the changes, trends, and database technologies that are going to impact your business in the next 12-18 months.</subtitle>
        <track>Miscellaneous</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;It has been an exciting year in the open-source database industry, with more choice, more cloud, and key changes in the industry. We will dive into the key developments over 2021, including the most important open-source database software releases in general, the significance of cloud-native solutions in a multi-vendor multi-cloud world, the new criticality of security challenges, and the evolution of the open-source software industry.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7756">Peter Zaitsev</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.misc/misc_databases.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.misc/misc_databases.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#misc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#misc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12513.php">Submit feedback</link>
        </links>
      </event>
      <event id="12723">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>M.misc</room>
        <slug>crowdsecurity</slug>
        <title>Crowdsecurity</title>
        <subtitle>A participative IDS/IPS</subtitle>
        <track>Miscellaneous</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;The &lt;a href="https://github.com/crowdsecurity/crowdsec/"&gt;CrowdSec&lt;/a&gt; project aims at providing a crowdsourced approach to common infrastructure defense problems, by distributing free &amp;amp; open-source software allowing to protect yourself and share information about malevolent actors. These software components, of which Crowdsec is the main piece, work by processing logs and enriching them, to apply behaviour-based scenarios (heuristics) that will identify attacks pattern. One of the core concepts of Crowdsec is to separate the detection of an attack and its reaction, to be suitable for modern architectures. While Crowdsec is in charge of the detection, the reaction is performed by "bouncers" that aim to be deployable at any level of the applicative / infrastructure stack.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The &lt;a href="https://github.com/crowdsecurity/crowdsec/"&gt;CrowdSec&lt;/a&gt; project aims at providing a crowdsourced approach to common infrastructure defence problems, by distributing free &amp;amp; open-source software allowing you to protect yourself and share information about malevolent actors.
These software components, of which Crowdsec is the main piece, work by processing logs (or more generally information stream) and enriching them, to apply behaviour-based scenarios (heuristics) that will identify attacks pattern.&lt;/p&gt;

&lt;p&gt;One of the core concepts of Crowdsec is to decorrelate the detection of an attack and its reaction, to be suitable for modern architectures.
While Crowdsec is in charge of the detection, the reaction is performed by "bouncers" that aim to be deployable at any level of the applicative / infrastructure stack :
 - as a nftables/iptables daemon "a la fail2ban"
 - as a nginx plugin
 - as a wordpress plugin - a kubernetes ingress controller
 - etc.&lt;/p&gt;

&lt;p&gt;We hope that this approach, combined with a declarative configuration and a stateless behaviour, will make it an ideal candidate to enhance the security of modern stacks (containers, k8s, serverless and more generally automatically deployed infrastructures).
We are committed to building a strong community, with all that it implies :
 - &lt;a href="https://hub.crowdsec.net"&gt;a public hub&lt;/a&gt; to find, share and amend parsers, scenarios and bouncers. - permissive open-source licence to stay business-friendly&lt;/p&gt;

&lt;p&gt;and overall a strong commitment to transparency and community-first mentality, by tooling and behaviour&lt;/p&gt;</description>
        <persons>
          <person id="8703">Thibault Koechlin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/crowdsecurity/crowdsec">gh repository</link>
          <link href="https://video.fosdem.org/2022/M.misc/crowdsecurity.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.misc/crowdsecurity.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#misc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#misc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12723.php">Submit feedback</link>
        </links>
      </event>
      <event id="12449">
        <start>16:00</start>
        <duration>00:45</duration>
        <room>M.misc</room>
        <slug>misc_network_automation</slug>
        <title>Open Source Network Automation in 2022</title>
        <subtitle>How to build a Network Automation strategy around Open Source tooling</subtitle>
        <track>Miscellaneous</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Network Automation has evolved a lot on the last years, adopting a lot of the practices from SDLC (Software Development Life Cycle) but with the intrinsic constraint of networking services. In this talk you will learn about which are the challenges and common use cases around network automation, for instance: configuration management, user-driven workflows, infrastructure as Code (for hybrid and multi clouds) or close-loop automation using Telemetry.
You will realise how a lot of open source projects are coming together to provide solutions to the previous challenges from different angles and how you could connect them together to start building a network automation strategy that could transform your network with lower OPEX, improved reliability and security, and increased innovation.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8469">Christian Adell Querol</person>
        </persons>
        <attachments>
          <attachment type="video" href="https://fosdem.org/2022/schedule/event/misc_network_automation/attachments/video/5262/export/events/attachments/misc_network_automation/video/5262/Open_Source_Network_Automation_in_2022.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.misc/misc_network_automation.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.misc/misc_network_automation.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#misc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#misc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12449.php">Submit feedback</link>
        </links>
      </event>
      <event id="12833">
        <start>17:00</start>
        <duration>01:00</duration>
        <room>M.misc</room>
        <slug>misc_ntfs_rust</slug>
        <title>Implementing the NTFS filesystem in Rust</title>
        <subtitle>Reusable code from firmware level up to user-mode</subtitle>
        <track>Miscellaneous</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Time has come to rewrite our system software in Rust and leave the pitfalls of C behind. This also includes basics such as filesystem support.
I took on the challenge to implement NTFS, the primary filesystem used by Windows, in a Rust crate that is equally usable from the firmware level up to user-mode.&lt;/p&gt;

&lt;p&gt;While Rust has been conquering the system software landscape for the past few years, there are next to no examples for implementing filesystems.
Likewise, NTFS only has a single major open-source implementation known as ntfs-3g, and it was developed in C over a decade ago.&lt;/p&gt;

&lt;p&gt;This talk will cover my motivation for targeting NTFS and various use cases for such a Rust crate. I will introduce you to the internals of the NTFS filesystem, how they influenced the crate's design, and how Rust's features can be leveraged to create a safe and maintainable implementation. My talk will cover the current implementation, but also the necessary iterations until I got there.
Finally, we will also deal with the current limitations of the Rust ecosystem and possible future improvements to the crate.&lt;/p&gt;

&lt;p&gt;You will see that Rust has many advantages for implementing filesystems, and I hope to see more such crates in the future.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8728">Colin Finck</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://colinfinck.de/posts/an-implementation-of-the-ntfs-filesystem-in-a-rust-crate/">Announcement</link>
          <link href="https://github.com/ColinFinck/ntfs">GitHub repository</link>
          <link href="https://crates.io/crates/ntfs">ntfs crate at crates.io</link>
          <link href="https://docs.rs/ntfs">Documentation at docs.rs</link>
          <link href="https://video.fosdem.org/2022/M.misc/misc_ntfs_rust.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.misc/misc_ntfs_rust.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#misc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#misc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12833.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="M.rtc">
      <event id="12930">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>M.rtc</room>
        <slug>rtc_jitsi</slug>
        <title>Jitsi: 20 years of Real Time Communications</title>
        <subtitle>How the Jitsi project has adapted and remained current in the RTC industry for almost 20 years</subtitle>
        <track>Real Time Communications</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;The Jitsi project was founded almost 20 years ago, under a different name and just for academic purposes.&lt;/p&gt;

&lt;p&gt;Almost 20 years later, the project could not be in a better shape! It has gone through a name change and several acquisitions by  large corporations, while remaining current in the industry and innovating all along.&lt;/p&gt;

&lt;p&gt;This presentation will take a trip down memory lane and see where Jitsi came from, how it has managed to stick around for so long, and what the future holds.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="186">Saúl Ibarra Corretgé</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://en.wikipedia.org/wiki/Jitsi">Wikipedia entry</link>
          <link href="https://jitsi.org/">Main project website</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_jitsi.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_jitsi.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#rtc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#rtc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12930.php">Submit feedback</link>
        </links>
      </event>
      <event id="12982">
        <start>11:00</start>
        <duration>00:45</duration>
        <room>M.rtc</room>
        <slug>rtc_webrtc</slug>
        <title>The Future of WebRTC</title>
        <subtitle>New APIs, WHIP, edge and web 2.5 </subtitle>
        <track>Real Time Communications</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;What is new in WebRTC, what can we expect to see in the next couple of years?
I'll describe some new APIs and speculate on how they might be used.
I'll introduce whipi (an opensource implementation of the new WebRTC Ingest Protocol) and use it to illustrate how the WebRTC world is changing.
I'll try to predict some new usages of WebRTC - niche high value apps.
Finally I'll describe how to create a decentralized web
(aka web 2.5) using the datachannel and existing browser technology.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;We've all spent a lot of time using centralized video conference services in the last months.
We have got a huge amount done at home whilst behind NAT on domestic ISP connections.
This has all been possible due to webRTC's design.&lt;/p&gt;

&lt;p&gt;This talk tries to look beyond that usecase to new less business orientated realtime media and data apps that are enabled by new(ish) APIs.&lt;/p&gt;

&lt;p&gt;For economic,privacy and ecological reasons I'll emphasize apps that move computing to the edge.
It will cover Baby monitors, robots, yoga classes and P2P web services and other surprising stuff...&lt;/p&gt;</description>
        <persons>
          <person id="7090">Tim Panton</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_webrtc.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_webrtc.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#rtc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#rtc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12982.php">Submit feedback</link>
        </links>
      </event>
      <event id="13103">
        <start>12:00</start>
        <duration>00:45</duration>
        <room>M.rtc</room>
        <slug>rtc_whip</slug>
        <title>WebRTC broadcasting with WHIP</title>
        <subtitle/>
        <track>Real Time Communications</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;The broadcasting industry has for years been dominated by a specific set of technologies (RTMP, HLS, etc.) that, while effective, suffer from high latencies and so are not always a good option. The IETF has started to look into WebRTC for that, starting from ingestion using the WHIP protocol. This presentation will introduce WHIP, some existing implementations, and how this could be expanded to distribute streams to a wide audience via WebRTC as well.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The broadcasting industry has for years been dominated by a well known and specific set of technologies (RTMP, HLS, etc.). These solutions do work and are widely deployed, taking advantage of CDNs for distributing streams to a potentially very large audience in an effective way. That said, they do suffer from some limitations, the stronger one being a high latency that cannot really be reduced, if not slightly. Considering there are scenarios where a very low latency may be desired, WebRTC has started to gain some traction, due to its real-time nature that, although originally conceived for conversational scenarios, has actually often used for streaming purposes as well.&lt;/p&gt;

&lt;p&gt;When it comes to broadcasting, there are two main aspects to take into account: ingestion (providing a stream to broadcast) and distribution (feeding the stream to an audience). The IETF has started addressing ingestion in the WISH Working Group, with a draft describing the WHIP protocol. This presentation will introduce what WHIP is, its requirements, and how it's supposed to work, plus some details on existing implementations. It will then move to some considerations on how distribution could be handled via WebRTC as well, possibly at scale, using the open source Janus WebRTC Server as a reference implementation.&lt;/p&gt;</description>
        <persons>
          <person id="3242">Lorenzo Miniero</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/rtc_whip/attachments/slides/5152/export/events/attachments/rtc_whip/slides/5152/fosdem2022_whip_broadcasting.pdf"/>
        </attachments>
        <links>
          <link href="https://datatracker.ietf.org/wg/wish/about/">WISH Working Group charter</link>
          <link href="https://www.ietf.org/archive/id/draft-ietf-wish-whip-01.html">WHIP draft (01)</link>
          <link href="https://www.meetecho.com/blog/whip-janus-part-ii/">Blog post on WHIP</link>
          <link href="https://github.com/IETF-Hackathon/ietf112-project-presentations/blob/main/ietf112-hackathon-whip.pdf">IETF 112 WHIP Hackathon</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_whip.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_whip.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#rtc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#rtc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13103.php">Submit feedback</link>
        </links>
      </event>
      <event id="12477">
        <start>13:00</start>
        <duration>01:00</duration>
        <room>M.rtc</room>
        <slug>rfc_rest_future</slug>
        <title>On the Far Side of REST</title>
        <subtitle>An Architecture for a Future Internet</subtitle>
        <track>Real Time Communications</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;REST, the architecture underlying the web's protocols, has proven its benefits in creating a globe-spanning, decentralized information network. However, REST is showing its age - it was designed when surveillance capitalism, identity theft, information warfare, and other threats were largely hypothetical concerns. Unavoidably, REST leaves many of these issues unaddressed. Best practices fill some gaps, but may not be universally adopted.&lt;/p&gt;

&lt;p&gt;The Interpeer Project has been awarded a grant from the Internet Society Foundation for research and development into a next generation architecture that addresses current and future Internet user needs. Such an architecture needs to embrace the strengths of REST, incorporate known best practices, but ideally make worst practices impossible.&lt;/p&gt;

&lt;p&gt;This talk presents the issues with REST in some detail and lays out proposed solution sketches. The ideal is to invite participation, however. The 'net needs a wide range of view points to be fixed.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In 2000, Roy Fielding published his dissertation on Representational State Transfer. Fielding had been actively working on the HTTP standards, which were guiding by informal design principles that REST formalizes. The talk will revisit this architectural style to disambiguate it from how the REST term has become applied since.&lt;/p&gt;

&lt;p&gt;Much as software freedoms exist, we need to address "internet user freedoms", and their relationship to human rights. Existing internet technology must be evaluated in this light, in how it supports or hinders human rights.&lt;/p&gt;

&lt;p&gt;In this presentation, architectural properties and constraints in the REST architectural style will be analyzed, with regards to the previous discussion as well as technical requirements. We will explore additional properties, and their effect on the architectural style.&lt;/p&gt;

&lt;p&gt;The talk will also provide background on concrete work already done or underway on this and adjacent topics.&lt;/p&gt;

&lt;p&gt;Finally, we'd like to briefly introduce the non-profit organization created to support work on this project. If we are to create a better digital world, we'll need patience and all the help we can get.&lt;/p&gt;</description>
        <persons>
          <person id="7343">Jens Finkhaeuser</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/rfc_rest_future/attachments/slides/5041/export/events/attachments/rfc_rest_future/slides/5041/on_the_far_side_of_rest.pdf">On the Far Side of REST</attachment>
        </attachments>
        <links>
          <link href="https://interpeer.io">Interpeer Project</link>
          <link href="https://app.element.io/#/room/#interpeer:libera.chat">#interpeer on libera.chat via element.io matrix bridge</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rfc_rest_future.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rfc_rest_future.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#rtc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#rtc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12477.php">Submit feedback</link>
        </links>
      </event>
      <event id="13003">
        <start>14:00</start>
        <duration>00:45</duration>
        <room>M.rtc</room>
        <slug>rtc_unifiedpush</slug>
        <title>UnifiedPush</title>
        <subtitle>A FOSS cross-platform push notifications protocol</subtitle>
        <track>Real Time Communications</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Our mobile devices have various apps that need updates from various servers at various intervals. Each app connecting to its own server on its own schedule, perhaps using inefficient technologies, can cause a lot of battery drain. Push Notification services are systems that can route all the important updates our devices need - whether they're instant message, VoIP, or social updates - into one shared channel.&lt;/p&gt;

&lt;p&gt;Unfortunately, the status quo in push notification services rely on centralized, proprietary services hosted by a third party. UnifiedPush is a set of free and open source specifications that allow you to get push notifications while picking your own hosting provider. This presentation goes over the history of UnifiedPush, current state of the project and architecture, and what the future goals of UnifiedPush are. It also discusses push notifications on Linux phones.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8527">Karmanyaah Malhotra</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/rtc_unifiedpush/attachments/slides/5160/export/events/attachments/rtc_unifiedpush/slides/5160/UnifiedPush.odp"/>
        </attachments>
        <links>
          <link href="https://unifiedpush.org">UnifiedPush website</link>
          <link href="https://unifiedpush.org/users/intro/">UnifiedPush users intro</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_unifiedpush.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_unifiedpush.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#rtc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#rtc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13003.php">Submit feedback</link>
        </links>
      </event>
      <event id="13011">
        <start>15:00</start>
        <duration>00:45</duration>
        <room>M.rtc</room>
        <slug>rtc_webrtc_ai_ml</slug>
        <title>Backgrounds are blurry, but the future is clear</title>
        <subtitle>More AI and ML in WebRTC applications</subtitle>
        <track>Real Time Communications</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Machine learning models have made it to the browser. Virtual backgrounds and background blurs are everywhere! Many recent developments including Tensorflow WASM backend, smaller ML models, pre-trained model repositories have enabled widely used virtual backgrounds and backgrounds blurs.&lt;/p&gt;

&lt;p&gt;This talk will explore how a simple background blur works, how developers can code their own blur for a WebRTC call, and most interestingly - what other ML/AI applications can be built using the same framework&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Machine learning models and inferences are being run on the browser and have become very performant. Libraries and frameworks like mediapipe, bodypix have made it easy to integrate ML-based experiences into a WebRTC call with relative ease. We're still in the early days of discovering their possibilities in web applications.&lt;/p&gt;

&lt;p&gt;In this talk, we will walk through how Daily integrated mediapipe in its WebRTC library. We will explore:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;How segmentation models, like the ones used blur backgrounds, work.&lt;/li&gt;
&lt;li&gt;How one can integrate an ML segmentation library (like mediapipe) in a WebRTC video call.&lt;/li&gt;
&lt;li&gt;What other sorts of custom video applications and experiences one can build using a tech stack like these.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Hopefully, this leaves the audience with ideas for writing custom video processors that might enable the next generation of video experiences on WebRTC.&lt;/p&gt;</description>
        <persons>
          <person id="8817">Ravindhran Sankar</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_webrtc_ai_ml.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_webrtc_ai_ml.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#rtc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#rtc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13011.php">Submit feedback</link>
        </links>
      </event>
      <event id="12397">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>M.rtc</room>
        <slug>rtc_media_streaming_mesh</slug>
        <title>Introduction to Media Streaming Mesh</title>
        <subtitle>Enabling Real-Time Media Applications in Kubernetes</subtitle>
        <track>Real Time Communications</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;The cloud-native approach based on containerized micro-services has transformed the software landscape but is largely focused on non-real time web-based applications, especially in the case of service meshes which use web proxies to interconnect workloads.  Media Streaming Mesh uses real-time media proxies to observe, route, encrypt and protect north-south and east-west media traffic.&lt;/p&gt;

&lt;p&gt;This talk introduces the Media Streaming Mesh architecture and its use-cases, gives an update on implementation status, and acts as a call to arms to recruit more contributors.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4135">Giles Heron</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/rtc_media_streaming_mesh/attachments/slides/5011/export/events/attachments/rtc_media_streaming_mesh/slides/5011/Introduction_to_Media_Streaming_Mesh">Introduction to Media Streaming Mesh</attachment>
        </attachments>
        <links>
          <link href="https://github.com/media-streaming-mesh">GitHub project</link>
          <link href="https://servicemeshconeu21.sched.com/event/iSAb/lightning-talks-introduction-to-media-service-mesh-use-skywalking-satellite-to-process-tracing-logging-and-metrics-in-service-mesh">ServiceMeshCon talk (using earlier name of project)</link>
          <link href="https://ciscotechblog.com/blog/introducing-media-streaming-mesh/">Tech Blog post on MSM</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_media_streaming_mesh.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.rtc/rtc_media_streaming_mesh.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#rtc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#rtc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12397.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="M.security">
    </room>
    <room name="M.test">
    </room>
    <room name="L.lightningtalks">
      <event id="12554">
        <start>13:00</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_timewarrior</slug>
        <title>Tracking your time with Timewarrior</title>
        <subtitle/>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;Time tracking is a task many people have to deal with. Be it for writing bills for your client, creating time reports for your company, or simply because you are curious what you are doing with your time all day. Timewarrior is a tool that lets you track your time easily from the command line – it does its job then gets out of your way.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The presentation wants to give you an overview of what Timewarrior can do for you (and what not), and how you can adapt Timewarrior to your needs.&lt;/p&gt;

&lt;p&gt;The talk is aimed at new users, but everyone is welcome to join the Q&amp;amp;A session afterwards.&lt;/p&gt;</description>
        <persons>
          <person id="8600">Thomas Lauf</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://timewarrior.net">The homepage of the Timewarrior project</link>
          <link href="https://github.com/GothenburgBitFactory/timewarrior">Timewarrior repository on GitHub</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_timewarrior.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_timewarrior.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12554.php">Submit feedback</link>
        </links>
      </event>
      <event id="12729">
        <start>13:20</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_reconfigure</slug>
        <title>Reconfigure from all over</title>
        <subtitle>The case of interdisciplinary open-source communities</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;As a means of enabling distributed collaboration, open-source enables people from many different disciplinary backgrounds to participate in research projects to which they would otherwise not have access. Additionally, open-source allows for reconfigurable expertise, or the ability to combine people from different backgrounds in ways depending on the task at hand. This talk will discuss the challenges associated with spontaneous interdisciplinary, in addition to opportunities provided by reconfigurable expertise. Examples from three open-source communities: OpenWorm Foundation, Rokwire Community, and the Orthogonal Research and Education Lab. The community building aspects of maintaining members for this type of adaptive and resilient resource are also addressed. When applied to academic-based communities, the ability to reconfigure working groups based on both the immediate and long-term needs of expertise is a valuable model for project management.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8683">Bradly Alicea</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_reconfigure/attachments/slides/4953/export/events/attachments/lt_reconfigure/slides/4953/Reconfigure_From_All_Over_Lightning_talk.pdf">Reconfigure From All Over</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_reconfigure.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_reconfigure.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12729.php">Submit feedback</link>
        </links>
      </event>
      <event id="12451">
        <start>13:40</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_humidity_data</slug>
        <title>Measuring and analyzing humidity data using Python, syslog-ng and Elasticsearch</title>
        <subtitle/>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;A desktop thermometer that displays relative humidity is useful, but it does not provide continuous monitoring. In comes the Raspberry Pi: it is small, inexpensive, and has many sensor options, including temperature and relative humidity. It can collect data around the clock, do some alerting, and forward data for analysis.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Originally it was a project to practice Python and learn Elasticsearch, but ended up with using syslog-ng between the two. Along the way, I also learned how to regulate humidity in my room. In my talk, I plan to cover the following topics:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;collecting environmental data on the Rasbperry Pi using Python&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;configuring Elasticsearch to work around a syslog-ng limitation&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;configuring syslog-ng to forward the collected data to Elasticsearch / OpenSearch&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;take a look at the graphs in Kibana and learn how to keep humidity low in your room&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="828">Peter Czanik</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_humidity_data/attachments/slides/5113/export/events/attachments/lt_humidity_data/slides/5113/czp_fosdem2022_syslog_ng_v2.pdf">Measuring and analyzing humidity data using Python, syslog-ng and Elasticsearch</attachment>
        </attachments>
        <links>
          <link href="https://peter.czanik.hu/">sudo/syslog-ng/personal blog</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_humidity_data.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_humidity_data.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12451.php">Submit feedback</link>
        </links>
      </event>
      <event id="13508">
        <start>14:00</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_jupyter</slug>
        <title>Jupyter for React.js developers</title>
        <subtitle>React.js components to build your custom data product with Jupyter</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;Jupyter notebook is a tool that allows Data Scientist to analyse dataset. However, it is not easy to create a custom user interface integrated in an existing application.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;Jupyter React&lt;/code&gt;, https://github.com/datalayer/jupyter-react, an open-source library, fills that gap and provides components that a developer can easily integrate in any React.js application.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The Jupyter user interface stack is built on top of Lumino, which is an imperative way to build user interface and can not be consumed by industry standard declarative frameworks like React.js.&lt;/p&gt;

&lt;p&gt;As a user interface developer, if you want to create a custom data product on top of Jupyter, you have to stick to Lumino and update the existing notebook interface. This is not what you want. You want your toolkit (like React.js) and you want to integrate on a component basis the Jupyter functionality in your application.&lt;/p&gt;</description>
        <persons>
          <person id="1513">Eric Charles</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_jupyter/attachments/slides/5157/export/events/attachments/lt_jupyter/slides/5157/Jupyter_for_React_js_developers_FOSDEM_2022.pdf"/>
        </attachments>
        <links>
          <link href="https://reactjs.org/">React.js</link>
          <link href="https://github.com/datalayer/jupyter-react">Jupyter React</link>
          <link href="https://github.com/datalayer/jupyter-examples">Jupyter React Examples</link>
          <link href="https://github.com/datalayer/jupyter-docusaurus">Jupyter Docusaurus</link>
          <link href="https://github.com/jupyterlab/jupyterlab">JupyterLab </link>
          <link href="https://github.com/jupyterlab/lumino">Lumino toolkit</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_jupyter.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_jupyter.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13508.php">Submit feedback</link>
        </links>
      </event>
      <event id="12848">
        <start>14:20</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_cmod</slug>
        <title>C meta-programming for the masses with C%: cmod</title>
        <subtitle/>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;&lt;strong&gt;C%&lt;/strong&gt; (from "C with mods") is an experimental meta-programming language that aims to make coding in C more efficient and fun!&lt;/p&gt;

&lt;p&gt;Together with &lt;strong&gt;cmod&lt;/strong&gt;, the reference pre-processor/code generator (written using &lt;strong&gt;C%&lt;/strong&gt; itself), this project enables the C programmer with generic meta-programming constructs such as: parameterized verbatim code snippets, mapping code to static data tables (in TSV or JSON format), multi-pass code evaluation (allowing meta-meta-programming), compile-time command execution (allowing code generation from any other software/language), etc. as well as C-specific constructs such as: function types, named parameters, selection over strings and structs, etc. The &lt;strong&gt;C%&lt;/strong&gt; standard library provides convenience constructs for inclusion in C programs.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Some of the things that &lt;strong&gt;C%&lt;/strong&gt; aims to make achievable are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Reusability&lt;/strong&gt;: Avoid code duplication.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consistency&lt;/strong&gt;: Use the same data across different locations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Efficiency&lt;/strong&gt;: Perform common tasks quick and easy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Concision&lt;/strong&gt;: Write and work with concise code.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Expressivity&lt;/strong&gt;: Better express the intent of code.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Transparency&lt;/strong&gt;: Hide nothing from the programmer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Abstraction&lt;/strong&gt;: Handle similar things in a uniform manner.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Extensibility&lt;/strong&gt;: Easily add new functionality.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Simplicity&lt;/strong&gt;: Keep the language simple but powerful.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;All while keeping with the spirit of C: &lt;em&gt;trust the programmer and don't prevent the programmer from doing what needs to be done&lt;/em&gt;!&lt;/p&gt;

&lt;p&gt;Beyond C meta-programming, &lt;strong&gt;C%&lt;/strong&gt;'s generic keywords enable meta-programming in other languages such as Python, Flex/Bison, etc.&lt;/p&gt;

&lt;p&gt;For full documentation, please refer to the &lt;a href="https://gitlab.com/seirios/cmod/-/blob/master/README.md" title="README"&gt;README&lt;/a&gt;.&lt;/p&gt;</description>
        <persons>
          <person id="8599">Sirio Bolaños Puchet</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_cmod/attachments/slides/4982/export/events/attachments/lt_cmod/slides/4982/lt_cmod.pdf">C meta-programming for the masses with C%: cmod</attachment>
        </attachments>
        <links>
          <link href="https://gitlab.com/seirios/cmod">Code repository</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_cmod.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_cmod.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12848.php">Submit feedback</link>
        </links>
      </event>
      <event id="12942">
        <start>14:40</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lg_qbe</slug>
        <title>Introduction to qbe</title>
        <subtitle>A lightweight compiler backend</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;qbe is an optimizing compiler backend which consumes programs in a simple intermediate language, optimizes them, and emits assembly for x86_64, aarch64, or riscv64, aiming to achieve "70% of the performance" of advanced compilers like LLVM in "10% of the code". This talk will briefly introduce qbe and its intermediate language, explain how it works and what it's capable of, and go over some sample programs which can be written in it.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5905">Drew DeVault</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lg_qbe/attachments/slides/4878/export/events/attachments/lg_qbe/slides/4878/qbe.pdf">Slidedeck</attachment>
        </attachments>
        <links>
          <link href="https://c9x.me/compile/">qbe</link>
          <link href="https://sr.ht/~mcf/cproc/">cproc C compiler</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lg_qbe.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lg_qbe.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12942.php">Submit feedback</link>
        </links>
      </event>
      <event id="12950">
        <start>15:00</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>ld_interplanetary_wheels</slug>
        <title>InterPlanetary Wheels</title>
        <subtitle>A resilient approach to distributing software</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;InterPlanetary Wheels (IPWHL) are platform-unique, singly-versioned Python built distributions backed by IPFS for security and reproducibility.
Using the peer-to-peer file system IPFS, the distributions have the advantage of being easily replicated and not having a single point of failure, thus are more resilient.
While this project targets at Python package in particular, the idea can be similarly applied to other software distributions such as Linux distributions.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8798">Huy Ngo</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ld_interplanetary_wheels/attachments/slides/4971/export/events/attachments/ld_interplanetary_wheels/slides/4971/fosdem_ipwhl_slides.pdf">Slides preview</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/ld_interplanetary_wheels/attachments/other/4973/export/events/attachments/ld_interplanetary_wheels/other/4973/transcript.txt">transcript</attachment>
        </attachments>
        <links>
          <link href="https://sr.ht/~cnx/ipwhl">Project page</link>
          <link href="https://man.sr.ht/~cnx/ipwhl">Project documentation</link>
          <link href="https://ipfs.io">IPFS home page</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/ld_interplanetary_wheels.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/ld_interplanetary_wheels.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12950.php">Submit feedback</link>
        </links>
      </event>
      <event id="13013">
        <start>15:20</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_webrecorder</slug>
        <title>Making the web preservable with open source tools</title>
        <subtitle>An overview of Webrecorder tools</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;The modern web has viewers for all sorts of formats that can be loaded in the web browser, except for other web sites.
The 'Save Page As' feature doesn't really work for most
modern web pages.
This talk will briefly cover the work of the Webrecorder project, from creating a new web archiving format to browser extensions and viewers,
in making archiving and preserving the modern web more accessible to all!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8815">Ilya Kreymer</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_webrecorder/attachments/slides/5115/export/events/attachments/lt_webrecorder/slides/5115/webrecorder_browser_based_archiving_talk.pdf">Browser Based Web Archiving</attachment>
        </attachments>
        <links>
          <link href="https://webrecorder.net/">Webrecorder Home Page</link>
          <link href="https://archiveweb.page/">ArchiveWeb.page Extension and App</link>
          <link href="https://replayweb.page">ReplayWeb.page Viewer</link>
          <link href="https://webrecorder.github.io/wacz-spec/latest/">WACZ Format Specification Draft</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_webrecorder.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_webrecorder.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13013.php">Submit feedback</link>
        </links>
      </event>
      <event id="13132">
        <start>15:40</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_vicious_circle</slug>
        <title>Let's escape this vicious circle</title>
        <subtitle/>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;Privacy on the internet is stuck in a vicious circle involving tech and legislation, which we need to escape.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;It takes far too long for legislators to transpose directives. The data industry uses an arsenal of dark patterns and technical stunts to creatively interpret or completely circumvent the applicable law.&lt;/p&gt;

&lt;p&gt;A new approach is needed to solve this problem in a sustainable way and make the web a better place again. In our talk we will give a brief insight into problematic patterns and techniques as well as approaches to overcome them.&lt;/p&gt;

&lt;p&gt;We are Frederik and Hendrik. We're building a fair and open web analytics tool and want to share what we discovered along the way with the FOSDEM audience. This lightning talk will be given by us together.&lt;/p&gt;</description>
        <persons>
          <person id="8865">Hendrik Niefeld</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_vicious_circle/attachments/slides/4909/export/events/attachments/lt_vicious_circle/slides/4909/Offen.pdf">Let's escape this vicious circle</attachment>
        </attachments>
        <links>
          <link href="https://www.offen.dev/?utm_source=conference&amp;utm_campaign=fosdem">Offen - Fair web analytics</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_vicious_circle.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_vicious_circle.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13132.php">Submit feedback</link>
        </links>
      </event>
      <event id="12726">
        <start>16:00</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_3d_exhibitions</slug>
        <title>Generating virtual 3D exhibitions from Wikipedia</title>
        <subtitle>Let's dive into some rabbit holes with The Everything Exhibition!</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;Wikipedia and Wikimedia Commons are a treasure trove of free information about a lot of topics! Wikipedia alone contains over 50 million articles in almost 300 languages. We're building a new, fun way to explore this content: "The Everything Exhibition" is an open-source generator that creates interactive, virtual 3D exhibitions on arbitrary topics, which you can explore in the browser! It has a multiplayer mode, so you can visit the exhibitions in groups. And, other than in a real museum, you can scribble on everything!&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk, we want to introduce you to how the generator works, and show you our current progress. We're using the 3D rendering engine three.js, and defined a simple datastructure for describing the exhibition content, to make the generator arbitrarily extendable. We'll go into which algorithms we tried for creating the room layouts, share what we learned in our playtest sessions, and talk about what's next.&lt;/p&gt;

&lt;p&gt;With this project, we especially have young people in mind, who are often already used to 3D games and environments. But the Everything Exhibition allows everyone to &lt;em&gt;really&lt;/em&gt; get lost in these delicious rabbit holes! :D&lt;/p&gt;</description>
        <persons>
          <person id="7632">blinry</person>
          <person id="8273">bleeptrack</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/blinry/everything-exhibition">Git repository</link>
          <link href="https://blinry.github.io/everything-exhibition/#https://en.wikipedia.org/wiki/FOSDEM">Visit the Exhibition!</link>
          <link href="https://blinry.org/everything-exhibition/">Getting in touch</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_3d_exhibitions.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_3d_exhibitions.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12726.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="B.bofs">
    </room>
    <room name="D.ada">
    </room>
    <room name="D.apache-openoffice">
      <event id="13057">
        <start>11:00</start>
        <duration>00:45</duration>
        <room>D.apache-openoffice</room>
        <slug>openoffice_overview</slug>
        <title>Project Overview 2021/22</title>
        <subtitle/>
        <track>Apache OpenOffice</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We will look at the Year 2021, check out what has worked out what did not work out.
We will look at the most imortant things that we need for 2022.
And we will talk about things around the Project&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5243">Peter Kovacs</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/openoffice_overview/attachments/slides/5100/export/events/attachments/openoffice_overview/slides/5100/Apache_OpenOffice_a2021.odp"/>
          <attachment type="video" href="https://fosdem.org/2022/schedule/event/openoffice_overview/attachments/video/5101/export/events/attachments/openoffice_overview/video/5101/FOSDEM2021_Project_Overview_2021_22_rec2.mp4"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.apache-openoffice/openoffice_overview.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.apache-openoffice/openoffice_overview.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-openoffice_overview:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-openoffice_overview:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13057.php">Submit feedback</link>
        </links>
      </event>
      <event id="13014">
        <start>11:45</start>
        <duration>00:45</duration>
        <room>D.apache-openoffice</room>
        <slug>openoffice_linux_packaging</slug>
        <title>Revisiting the Linux packaging for Apache OpenOffice</title>
        <subtitle/>
        <track>Apache OpenOffice</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The current Linux packaging used by Apache OpenOffice is inefficient in many ways. We can take advantage of technologies like AppImage, snap and flatpak in order to make OpenOffice easier to install for Linux desktop users, while saving disk space for releases at the same time.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1275">Andrea Pescetti</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/openoffice_linux_packaging/attachments/slides/5282/export/events/attachments/openoffice_linux_packaging/slides/5282/FOSDEM22_pescetti.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.apache-openoffice/openoffice_linux_packaging.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.apache-openoffice/openoffice_linux_packaging.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-openoffice_linux_packaging:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-openoffice_linux_packaging:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13014.php">Submit feedback</link>
        </links>
      </event>
      <event id="13072">
        <start>12:30</start>
        <duration>00:45</duration>
        <room>D.apache-openoffice</room>
        <slug>openoffice_translation</slug>
        <title>Translation</title>
        <subtitle>How can it go on?</subtitle>
        <track>Apache OpenOffice</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Discussion about the way to work on translating UI and Help.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7899">Mechtilde Stehmann</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-openoffice_translation:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-openoffice_translation:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13072.php">Submit feedback</link>
        </links>
      </event>
      <event id="13221">
        <start>15:00</start>
        <duration>00:45</duration>
        <room>D.apache-openoffice</room>
        <slug>openoffice_containers</slug>
        <title>How to build OpenOffice today</title>
        <subtitle>Virtual machines and containers</subtitle>
        <track>Apache OpenOffice</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Building OpenOffice is not an easy task. The purpose of this presentation is to show how it is possible to leverage virtual machines and containers to:
 1- make this task easier and as much automatic as possible,
 2- avoid filling our computers with packages and libraries we may never need otherwise,
 3- build different releases (trunk, 4.1.x), for different operating systems, on the same computer.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8901">Arrigo Marchiori</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/openoffice_containers/attachments/slides/5066/export/events/attachments/openoffice_containers/slides/5066/how_to_build_openoffice_today.pdf">Presentation slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.apache-openoffice/openoffice_containers.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.apache-openoffice/openoffice_containers.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-openoffice_containers:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-openoffice_containers:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13221.php">Submit feedback</link>
        </links>
      </event>
      <event id="12936">
        <start>15:45</start>
        <duration>00:45</duration>
        <room>D.apache-openoffice</room>
        <slug>openoffice_build</slug>
        <title>The way to a new build Environment</title>
        <subtitle>goto SCONS</subtitle>
        <track>Apache OpenOffice</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The way to a new build Environment: goto SCONS&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5243">Peter Kovacs</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/openoffice_build/attachments/slides/5162/export/events/attachments/openoffice_build/slides/5162/Apache_OpenOffice_Scons_transfere.odp"/>
          <attachment type="video" href="https://fosdem.org/2022/schedule/event/openoffice_build/attachments/video/5164/export/events/attachments/openoffice_build/video/5164/FOSDEM2021_New_Build_Environment_rec1.mp4"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.apache-openoffice/openoffice_build.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.apache-openoffice/openoffice_build.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-openoffice_build:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-openoffice_build:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12936.php">Submit feedback</link>
        </links>
      </event>
      <event id="13198">
        <start>16:30</start>
        <duration>00:45</duration>
        <room>D.apache-openoffice</room>
        <slug>openoffice_testing</slug>
        <title>Apache OpenOffice Verification Testing</title>
        <subtitle>Build and Functional Testing with JUnit</subtitle>
        <track>Apache OpenOffice</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The talk will discuss current state of Unit testing in the Apache OpenOffice project and the effort to update the test suites to be useful standalone to run tests against an installed office without being tied to the OpenOffice build process. Also areas where Java developers could get involved.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7589">Carl Marcum</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.apache-openoffice/openoffice_testing.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.apache-openoffice/openoffice_testing.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#apache-openoffice-openoffice_testing:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#apache-openoffice-openoffice_testing:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13198.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.bsd">
    </room>
    <room name="D.collab">
      <event id="12750">
        <start>10:30</start>
        <duration>00:30</duration>
        <room>D.collab</room>
        <slug>collaboniro</slug>
        <title>Oniro - an open-source starter for fast-paced IoT environments</title>
        <subtitle>A retrospect on an open-source project development</subtitle>
        <track>Collaboration and Content Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this presentation Sebastian shares project experience gained over nearly 2 years of the Oniro project development in the area of product research &amp;amp; development. He starts with the initial assumptions and various criteria that team members intended to apply to the work done. It was a very interesting experience to apply a product-driven approach to highly-paced open-source projects nowadays. Thus, the great effort was put in order to receive maximum value from products intended to deliver to the market. Ettore is an Embedded Linux Developer, and joins to share the partner experience as he is part of the Hardware Enablement Team for SECO.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk, Sebastian is going to present a few product management principles, how they were applied to the project and what lessons were learnt in this process. The talk is filled with a few open source projects (e.g. GitLab, OpenProject and others) and how they were applied to the tasks we were faced with. Work package structures and workflows applied were also described to supplement the presentation. To conclude, Ettore joins the talk as representative of one of the Oniro Project partners, SECO, describing how was the experience in the last year, as an Internet of Things Hardware manufacturer.&lt;/p&gt;

&lt;p&gt;If you are building an open source community or are aiming to build one, this talk might be an interesting option for you.&lt;/p&gt;</description>
        <persons>
          <person id="3655">Ettore Chimenti</person>
          <person id="8719">Sebastian Serewa</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/collaboniro/attachments/slides/5086/export/events/attachments/collaboniro/slides/5086/slides_Oniro_retrospect.pdf">Slides from the talk</attachment>
        </attachments>
        <links>
          <link href="https://oniroproject.org/">Oniro - The Distributed Operating System That Connects Consumer Devices</link>
          <link href="https://booting.oniroproject.org">Oniro sources</link>
          <link href="https://www.youtube.com/watch?v=p-gSvehb-As&amp;list=PLy7t4z5SYNaQBDReZmeHAknEchYmu0LLa#OniroPlaylist">Oniro Videos</link>
          <link href="https://git.ostc-eu.org">Our incubation and initial development environment</link>
          <link href="https://video.fosdem.org/2022/D.collab/collaboniro.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.collab/collaboniro.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#collab-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-collaboniro:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#collab-collaboniro:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12750.php">Submit feedback</link>
        </links>
      </event>
      <event id="12488">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>D.collab</room>
        <slug>collabinteroffice</slug>
        <title>INTEROFFICE</title>
        <subtitle>Making CryptPad more interoperable with common office formats</subtitle>
        <track>Collaboration and Content Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The import and export of common office formats (.ods/.xlsx, .odt/.docx, .odp/.ppt) is taken for granted in many online office suites. However, in the case of CryptPad, implementing such functionality presents a number of challenges to preserve our privacy requirements. This has long held back adoption of our platform as it prevented users from migrating existing documents and/or integrating CryptPad in their workflows.&lt;/p&gt;

&lt;p&gt;In this talk I will summarize our work on INTEROFFICE, a project realized by the CryptPad team in 2021 with funding from the EU's Next Generation Internet (NGI) DAPSI program. The core of this work consists of a new set of converters that use Web Assembly to perform conversions between file formats in the browser. This allows for CryptPad to be vastly more inter-operable while preserving end-to-end encryption (the server still has no access to the content being converted).&lt;/p&gt;

&lt;p&gt;Speaking as the designer on the team, I will focus on the research we conducted with users and on the ways this new functionality is making its way into CryptPad's interface.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6888">David Benque</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://cryptpad.fr/presentation/#/2/presentation/view/-9uVAS9pXEDZ1SYEAgpDUynbin82KmnaznwUHxLIkg0/">Slides</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabinteroffice.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabinteroffice.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#collab-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-collabinteroffice:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#collab-collabinteroffice:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12488.php">Submit feedback</link>
        </links>
      </event>
      <event id="12883">
        <start>11:30</start>
        <duration>00:30</duration>
        <room>D.collab</room>
        <slug>collabtracim</slug>
        <title>Tracim, the helping hand for all your collaboration needs</title>
        <subtitle>Come discover Tracim and its architecture </subtitle>
        <track>Collaboration and Content Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Tracim is a web-based collaboration software mainly written by the Algoo company. Main specificities are well-integrated functionalities and intuitive UX. It aims to be easy to use for any kind of people wanting to work in teams.&lt;/p&gt;

&lt;p&gt;During this talk, I will tell you about Tracim architecture. You will discover the components and the reasons behind major design choices. Then I will detail more specifically a technical feature which brings Tracim users an interactive experience when collaborating with others.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8705">Sébastien Grignard</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/collabtracim/attachments/slides/5130/export/events/attachments/collabtracim/slides/5130/tracim_slides.odp">Tracim Slides</attachment>
        </attachments>
        <links>
          <link href="https://www.tracim.fr">The main Tracim website, only in French.</link>
          <link href="https://github.com/tracim/tracim/">Tracim's source code repository</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabtracim.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabtracim.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#collab-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-collabtracim:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#collab-collabtracim:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12883.php">Submit feedback</link>
        </links>
      </event>
      <event id="12990">
        <start>13:30</start>
        <duration>01:00</duration>
        <room>D.collab</room>
        <slug>collabxwiki</slug>
        <title>XWiki as an FOSS alternative to Confluence and Notion</title>
        <subtitle>Status in 2021:  realtime editing, livedata feature, confluence migrator and macros</subtitle>
        <track>Collaboration and Content Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;XWiki is a structured wiki engine developed as Open Source since 2004, providing wiki-style collaboration for organizations, with many built-in features and countless extensions. XWiki has pioneered wikis by including structured data on the same level as free text content, thus enhancing significantly the expressiveness of the built knowledge bases; this same usage is also popularized by Confluence and Notion, with different user experience choices and more importantly with business models  that are keeping user's data locked-in on the Cloud or in proprietary software.&lt;/p&gt;

&lt;p&gt;In this talk we will present XWiki's journey to provide the best FOSS alternative to proprietary knowledge management tools, based on both current features and future roadmap.&lt;/p&gt;

&lt;p&gt;We will showcase XWiki's approach for collaboration on text &amp;amp; structured data, including the newly conceived "livedata" component for inline editing of structured tabular data as well as the new realtime editor based on the realtime editing technology from CryptPad.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2113">Ludovic Dubost</person>
          <person id="2114">Anca Luca</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://xwiki.org">XWiki Open Source Software</link>
          <link href="https://extensions.xwiki.org/xwiki/bin/view/Extension/Live%20Data%20Macro/">XWiki Live Data</link>
          <link href="https://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime%20WYSIWYG%20Editor/">XWiki Realtime Wysiwyg Editor</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabxwiki.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabxwiki.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#collab-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-collabxwiki:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#collab-collabxwiki:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12990.php">Submit feedback</link>
        </links>
      </event>
      <event id="12935">
        <start>14:30</start>
        <duration>01:00</duration>
        <room>D.collab</room>
        <slug>collabnextcloudin2021</slug>
        <title>Nextcloud in 2021</title>
        <subtitle>Overview of 3 releases and a bit under a million features</subtitle>
        <track>Collaboration and Content Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Nextcloud did 3 major releases in 2021, one of which we named "Nextcloud Hub II"because it was such a big step forward for online collaboration. Let's go over what is new!&lt;/p&gt;</abstract>
        <description>&lt;p&gt;A short overview:
* Nextcloud 21 brought major performance improvements with the High Performance Back-end for Files and other improvements.
* Nextcloud 22 brought user-defined groups and workflows, document signing integration, a knowledge base, and many Talk improvements.
* Nextcloud 23 or Hub II introduced Nextcloud Office, appointment booking, background blur, permissions and more in Talk, Nextcloud Backup, AIO docker image, and much more.&lt;/p&gt;

&lt;p&gt;Join the talk for more details!&lt;/p&gt;</description>
        <persons>
          <person id="79">Jos Poortvliet</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.collab/collabnextcloudin2021.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabnextcloudin2021.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#collab-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-collabnextcloudin2021:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#collab-collabnextcloudin2021:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12935.php">Submit feedback</link>
        </links>
      </event>
      <event id="12753">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.collab</room>
        <slug>collabonlyoffice</slug>
        <title>Introducing ONLYOFFICE Forms for paperwork automation and smart collaboration</title>
        <subtitle/>
        <track>Collaboration and Content Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Everyday lots of people have to deal with agreements, contracts, budget plans, and other similar documents. In this regard, an ability to automate work with such files seems appealing. With this understanding in mind, ONLYOFFICE has been working on Smart Forms intended for optimization of file creation and collaboration in any document flow.&lt;/p&gt;

&lt;p&gt;In our presentation, we’ll tell you about the newly introduced ONLYOFFICE Forms, new formats (DOCXF and OFORM) built with the purpose of creating standardized document templates and working with them through specifically designed interface elements in ONLYOFFICE Docs.&lt;/p&gt;

&lt;p&gt;Presentation milestones:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What's the difference between ONLYOFFICE Forms and Content Controls&lt;/li&gt;
&lt;li&gt;OFORM and DOCXF&lt;/li&gt;
&lt;li&gt;How Smart Forms work in ONLYOFFICE&lt;/li&gt;
&lt;li&gt;Form sharing&lt;/li&gt;
&lt;li&gt;Data protection in forms&lt;/li&gt;
&lt;li&gt;Creating and filling PDF files in ONLYOFFICE Docs&lt;/li&gt;
&lt;li&gt;Using ONLYOFFICE Forms in your infrastructure (e.g. Nextcloud, Alfresco, Redmine, etc.)&lt;/li&gt;
&lt;li&gt;Roadmap for smart form development&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="6887">Alex Mikheev</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/collabonlyoffice/attachments/slides/5124/export/events/attachments/collabonlyoffice/slides/5124/Introducing_ONLYOFFICE_Forms_for_paperwork_automation_and_smart_collaboration.pdf">Introducing ONLYOFFICE Forms (PDF)</attachment>
        </attachments>
        <links>
          <link href="https://personal.onlyoffice.com/products/files/doceditor?fileid=4505617&amp;doc=eGxHWFBWV3M1aWJZaDlxSFlERjhvR0MxYVVEWjdYUjVVaG00c053Mkwrcz0_NDUwNTYxNw">Introducing ONLYOFFICE Forms </link>
          <link href="https://video.fosdem.org/2022/D.collab/collabonlyoffice.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabonlyoffice.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#collab-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-collabonlyoffice:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#collab-collabonlyoffice:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12753.php">Submit feedback</link>
        </links>
      </event>
      <event id="12816">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.collab</room>
        <slug>collabcarbonio</slug>
        <title>How to overcome development challenges when building self-hosted collaboration platform</title>
        <subtitle>Our experience with Carbonio Community Edition</subtitle>
        <track>Collaboration and Content Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;While the world is moving toward SaaS and Cloud infrastructures, many companies want to keep things in a self-hosted platform or in a private cloud. We’ll talk about all the challenges of building a product that gives users complete control over their data, and how we overcame them, such as migrating from a monolith to services to allow scalability, managing secure service discovery, detaching database from the infrastructure, or managing an easy service installation without any orchestrator. In January, we have released Carbonio CE (Community Edition) source code to show the results of our work. Contributors are welcome!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8748">Domenico Stragliotto</person>
          <person id="8749">Davide Baldo</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.collab/collabcarbonio.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabcarbonio.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#collab-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-collabcarbonio:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#collab-collabcarbonio:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12816.php">Submit feedback</link>
        </links>
      </event>
      <event id="12487">
        <start>16:30</start>
        <duration>01:00</duration>
        <room>D.collab</room>
        <slug>collabcsp</slug>
        <title>Deploying Containerised Open-Source CSP platforms</title>
        <subtitle>Alfresco and Nuxeo in action!</subtitle>
        <track>Collaboration and Content Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Understand containerised deployment with Open-Source CSP (Content Service Provider) platforms. Both Alfresco and Nuxeo products provide an easy Docker Compose deployment that allow early adopters and enthusiast developers to use the platforms.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Public deployment templates are be provided, including detailed instructions on how to use them:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Alfresco deployment using https://github.com/alfresco/alfresco-docker-installer&lt;/li&gt;
&lt;li&gt;Nuxeo deployment using default Docker Image from https://github.com/nuxeo/docker-nuxeo&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="8418">Angel Borroy</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/collabcsp/attachments/slides/5132/export/events/attachments/collabcsp/slides/5132/fosdem_collaboration_alfresco_nuxeo_2022011.pdf">Deploying Containerised Open-Source CSP Platforms</attachment>
        </attachments>
        <links>
          <link href="https://github.com/alfresco">Alfresco GitHub</link>
          <link href="https://github.com/nuxeo">Nuxeo GitHub</link>
          <link href="https://www.slideshare.net/angelborroy/deploying-containerised-opensource-csp-platforms">Slides</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabcsp.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.collab/collabcsp.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#collab-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#collab-collabcsp:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#collab-collabcsp:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12487.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.cad">
      <event id="12967">
        <start>10:20</start>
        <duration>00:40</duration>
        <room>D.cad</room>
        <slug>advanced_sim</slug>
        <title>Advanced PCB simulation with KiCad</title>
        <subtitle>Introduction to IBIS and FEM-based simulations</subtitle>
        <track>Computer Aided Modeling and Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Faster computations, faster communication speeds, faster everything. Today electronics can use data rates of several gigabits per second. At such speed wires and tracks are far from being perfect, bugs and glitches may arise because of them. Even low-speed designs are not safe and can encounter high-speed problems because they use high-speed capable chips.&lt;/p&gt;

&lt;p&gt;While the electronic CAD software KiCad has the tools to design high-speed boards, there is no tool to validate them. The usual way is to apply all good practice rules, even if they are sometimes overly conservative and might waste some board space. The layout plays an important part in both PCB performance and cost. A PCB simulator, integrated into KiCad, would help designers to find their balance between the two. This presentation is a short introduction to IBIS and FEM, tools that will most certainly be needed for such high-speed simulations, and provides application examples.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8656">Fabien Corona</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/advanced_sim/attachments/slides/5019/export/events/attachments/advanced_sim/slides/5019/FOSDEM_2022_Kicad_PCB_Simulation.pdf">Advanced PCB simulation with KiCad</attachment>
        </attachments>
        <links>
          <link href="https://gitlab.com/Drinausaur/kicad/-/tree/ibis">IBIS parser and modeler, experimental</link>
          <link href="https://gitlab.com/pointhi/kicad/-/tree/sparselizard_fem">Sparselizard-based  FEM simulation, with data coming from KiCad PCB's editor, experimental</link>
          <link href="https://video.fosdem.org/2022/D.cad/advanced_sim.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cad/advanced_sim.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cad-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-advanced_sim:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cad-advanced_sim:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12967.php">Submit feedback</link>
        </links>
      </event>
      <event id="12621">
        <start>11:00</start>
        <duration>01:00</duration>
        <room>D.cad</room>
        <slug>freecad_link</slug>
        <title>FreeCAD Link Branch Development</title>
        <subtitle>What's done and what's to come</subtitle>
        <track>Computer Aided Modeling and Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This will be joint presentation between realthunder and officinerobotica. The talk will first give a brief introduction of FreeCAD and its Link Branch, and then proceed to talk about its development in the past year with reference to the talk in FOSDEM21. New features will be presented by walking through the construction of a CAD model using FreeCAD. The talk will finish by highlighting new features in development and the road map ahead.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7752">Florin Curelariu</person>
          <person id="8074">LEI ZHENG</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/realthunder/FreeCAD_assembly3">Github project page</link>
          <link href="https://video.fosdem.org/2022/D.cad/freecad_link.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cad/freecad_link.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cad-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-freecad_link:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cad-freecad_link:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12621.php">Submit feedback</link>
        </links>
      </event>
      <event id="13085">
        <start>12:00</start>
        <duration>00:20</duration>
        <room>D.cad</room>
        <slug>librepcb</slug>
        <title>LibrePCB Status Update</title>
        <subtitle/>
        <track>Computer Aided Modeling and Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A short overview about the progress and the current state of the LibrePCB project.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;LibrePCB is an Open-Source EDA software to design PCBs, providing the following advantages:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cross-platform: Windows/Linux/MacOS/Others | x86/ARM&lt;/li&gt;
&lt;li&gt;Intuitive &amp;amp; easy-to-use UI&lt;/li&gt;
&lt;li&gt;Powerful library concept&lt;/li&gt;
&lt;li&gt;Human readable file format&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="5141">Urban Bruhin</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/librepcb/attachments/slides/5128/export/events/attachments/librepcb/slides/5128/librepcb_slides_fosdem_22.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://librepcb.org">Website</link>
          <link href="https://github.com/LibrePCB/LibrePCB">GitHub Repository</link>
          <link href="https://video.fosdem.org/2022/D.cad/librepcb.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cad/librepcb.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cad-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-librepcb:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cad-librepcb:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13085.php">Submit feedback</link>
        </links>
      </event>
      <event id="12984">
        <start>12:20</start>
        <duration>00:20</duration>
        <room>D.cad</room>
        <slug>ngspice</slug>
        <title>ngspice - current status and future developments</title>
        <subtitle/>
        <track>Computer Aided Modeling and Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;After a short introduction to the ngspice circuit simulator the first part of the talk will present some new features available in ngspice-36. Among them are SVG plotting capability, acknowledging RKM notation (e.g. 4k7 for 4.7 KOhm resistance), new and improved convergence methods when calculation the operating point, and many others.&lt;/p&gt;

&lt;p&gt;The second part of the talk discusses some new features under development or still under discussion, like XSPICE memory management improvements, adding BSIMCMG model for FinFETs, adding IBIS capability (together with KiCad and sparselizard), and S parameter intgration. A lot of discussions is going on among FOSS simulator developers and users about better Verilog-A support.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6153">Holger Vogt</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.cad/ngspice.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cad/ngspice.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cad-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-ngspice:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cad-ngspice:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12984.php">Submit feedback</link>
        </links>
      </event>
      <event id="12601">
        <start>12:40</start>
        <duration>01:00</duration>
        <room>D.cad</room>
        <slug>kicad</slug>
        <title>KiCad Project Update</title>
        <subtitle/>
        <track>Computer Aided Modeling and Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Update on the KiCad project including recent events, version 6 stable release, and what to expect during version 7 development.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/kicad/attachments/slides/4918/export/events/attachments/kicad/slides/4918/kicad_presentation_fosdem_2022.odp">KiCad Project Status</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.cad/kicad.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cad/kicad.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cad-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-kicad:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cad-kicad:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12601.php">Submit feedback</link>
        </links>
      </event>
      <event id="12980">
        <start>13:40</start>
        <duration>00:20</duration>
        <room>D.cad</room>
        <slug>bim</slug>
        <title>Hacking through BIM models</title>
        <subtitle>A BIM-oriented hacking session featuring FreeCAD, BlenderBIM and more...</subtitle>
        <track>Computer Aided Modeling and Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;BIM (Building Information Modeling) is a paradigm for 3D CAD models made for Architecture, Engineering and Construction (AEC). Long a closed, proprietary garden, it becomes more and more an open, hackable world thanks to several Free and Open-Source tools and formats.&lt;/p&gt;

&lt;p&gt;This talk will try to illustrate how rich that world has become when your tinkering, hacking, coding itch starts to scratch...&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk, Dion (developer of BlenderBIM) and Yorik (developer of FreeCAD, specifically its BIM tools) will use these two applications and try to show some clever tricks that you can do with BIM models, that no proprietary software would dream to achieve.&lt;/p&gt;</description>
        <persons>
          <person id="2906">Yorik van Havre</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://freecad.org">FreeCAD</link>
          <link href="https://blenderbim.org">BlenderBIM</link>
          <link href="https://video.fosdem.org/2022/D.cad/bim.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cad/bim.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cad-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-bim:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cad-bim:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12980.php">Submit feedback</link>
        </links>
      </event>
      <event id="12790">
        <start>14:00</start>
        <duration>00:20</duration>
        <room>D.cad</room>
        <slug>opencascade</slug>
        <title>Open CASCADE Technology status update</title>
        <subtitle/>
        <track>Computer Aided Modeling and Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Open Cascade Technology (OCCT) is a framework for B-Rep modeling. The lecture presents a technical update from the previous talk (at FOSDEM 2021). This year we also introduce our OCCT's Community Manager who will highlight community-related activities that happened during 2021.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7077">Alexander Malyshev</person>
          <person id="8941">Vera Sdobnova</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/opencascade/attachments/slides/4839/export/events/attachments/opencascade/slides/4839/FOSDEM_2022.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.cad/opencascade.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cad/opencascade.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cad-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-opencascade:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cad-opencascade:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12790.php">Submit feedback</link>
        </links>
      </event>
      <event id="12583">
        <start>14:20</start>
        <duration>00:20</duration>
        <room>D.cad</room>
        <slug>sparselizard</slug>
        <title>Sparselizard 2021.11 - your multiphysics FEM simulation tool</title>
        <subtitle/>
        <track>Computer Aided Modeling and Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk shows the features added to Sparselizard in 2021&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6963">Alexandre Halbach</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.sparselizard.org">https://www.sparselizard.org</link>
          <link href="https://video.fosdem.org/2022/D.cad/sparselizard.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cad/sparselizard.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cad-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-sparselizard:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cad-sparselizard:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12583.php">Submit feedback</link>
        </links>
      </event>
      <event id="12964">
        <start>14:40</start>
        <duration>00:20</duration>
        <room>D.cad</room>
        <slug>cadquery</slug>
        <title>The CadQuery Ecosystem</title>
        <subtitle>A sampling of community projects and extensions</subtitle>
        <track>Computer Aided Modeling and Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;CadQuery is a Python module for building parametric 3D CAD models in boundary representation (B-rep). It has an active community that has created editors, personal projects, research projects, examples for new and advanced users, and plugins that extend the functionality of CadQuery. The project is maintained by a small core team and numerous community members. CadQuery is built on the OpenCASCADE (OCCT) CAD kernel, and has support for 2D and 3D primitives, allows 3D assemblies and 2D sketches to be created with constraints, and makes heavy use of features like selectors to help capture design intent.&lt;/p&gt;

&lt;p&gt;There are multiple editors available for CadQuery including CQ-editor (desktop application), Jupyter-CadQuery (web based), and CadHub (web based CodeCAD sharing platform). There are repositories dedicated to examples and plugins, as well as separate projects for generating sprockets, chains, fasteners, polyhedra, and complex curves. Community members are responsible for much of the content in these repositories. There are also projects that rely on CadQuery, including in fusion research (Paramak), electrical component 3D model generation (KiCAD), and a more mouse-driven CAD application called Semblage. There are several ways of connecting with the community, including Discord, Matrix, Google Group and GitHub. Please introduce yourself and connect with other CadQuery users.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8786">Jeremy Wright</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/cadquery/attachments/slides/4894/export/events/attachments/cadquery/slides/4894/cadquery_fosdem_2022_presentation.odp">The CadQuery Ecosystem</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/cadquery/attachments/slides/4895/export/events/attachments/cadquery/slides/4895/cadquery_pdf_fosdem_2022_presentation.pdf">The CadQuery Ecosystem (PDF Version)</attachment>
        </attachments>
        <links>
          <link href="https://github.com/CadQuery/cadquery">CadQuery Repository</link>
          <link href="https://cadquery.readthedocs.io/en/latest/">CadQuery Documentation</link>
          <link href="https://github.com/CadQuery/CQ-editor">CQ-editor Repository</link>
          <link href="https://video.fosdem.org/2022/D.cad/cadquery.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cad/cadquery.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cad-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-cadquery:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cad-cadquery:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12964.php">Submit feedback</link>
        </links>
      </event>
      <event id="13506">
        <start>15:00</start>
        <duration>00:20</duration>
        <room>D.cad</room>
        <slug>oshw</slug>
        <title>Pushing the Open Source Hardware Limits with KiCAD</title>
        <subtitle>OSHW industrial grade computers and servers running cloud, medical and IoT services without hiding secrets in the hardware</subtitle>
        <track>Computer Aided Modeling and Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The talk will cover the design of very complex and powerful OSHW Linux
boards based on the new NXP iMX8 and ST STMP1 SOC with FLOSS KiCAD tools
and then running FLOSS software for cloud, IoT and Health to offer full
transparency to the people who value their privacy not only on software
but also on hardware level.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The talk will cover the design of very complex and powerful OSHW Linux
boards based on the new NXP iMX8 and ST STMP1 SOC with FLOSS KiCAD tools
and then running FLOSS software for cloud, IoT and Health to offer full
transparency to the people who value their privacy not only on software
but also on hardware level.&lt;/p&gt;</description>
        <persons>
          <person id="1641">Tsvetan Usunov</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/oshw/attachments/slides/4933/export/events/attachments/oshw/slides/4933/FOSDEM_2022_Pushing_OSHW_Limites_with_KiCAD.odp">Pushing OSHW Limits with KiCAD</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.cad/oshw.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cad/oshw.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cad-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cad-oshw:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cad-oshw:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13506.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.conference">
      <event id="13111">
        <start>11:45</start>
        <duration>00:05</duration>
        <room>D.conference</room>
        <slug>conference_introduction</slug>
        <title>Welcome to the Conference Organisation Dev Room</title>
        <subtitle/>
        <track>Conference Organisation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Introduction and welcome to the dev room&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8447">Kyle Robbertze</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.conference/conference_introduction.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.conference/conference_introduction.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#conference-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-conference_introduction:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#conference-conference_introduction:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13111.php">Submit feedback</link>
        </links>
      </event>
      <event id="12605">
        <start>11:50</start>
        <duration>00:35</duration>
        <room>D.conference</room>
        <slug>conference_tools</slug>
        <title>Free tools that help you run online events in an effective way</title>
        <subtitle/>
        <track>Conference Organisation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Nowadays everyone can run an event (meetup, hackathon, etc), but sometimes we struggle in selecting the right tool to organize it in an effective way. What tools are out there that can help us run any type of event and have impact?. We will do an overview about options, limitations and resources you will need to make a great event.&lt;/p&gt;

&lt;p&gt;If you are lost trying to choose the right tool for your first online event, this talk is for you. And if you think you know everything about tools and ways to engage with your audience, you will be welcomed as well, since we will discuss about these things and more.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Nowadays everyone can run an event (meetup, hackathon, etc), but sometimes we struggle in selecting the right tool to organize it in an effective way. What tools are out there that can help us run any type of event and have impact?. We will do an overview about options, limitations and resources you will need to make a great event.&lt;/p&gt;

&lt;p&gt;If you are lost trying to choose the right tool for your first online event, this talk is for you. And if you think you know everything about tools and ways to engage with your audience, you will be welcomed as well, since we will discuss about these things and more.&lt;/p&gt;</description>
        <persons>
          <person id="2358">Francisco Picolini</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/conference_tools/attachments/slides/5141/export/events/attachments/conference_tools/slides/5141/Free_Tools_that_helps_you_run_an_event.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.conference/conference_tools.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.conference/conference_tools.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#conference-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-conference_tools:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#conference-conference_tools:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12605.php">Submit feedback</link>
        </links>
      </event>
      <event id="13109">
        <start>12:30</start>
        <duration>00:35</duration>
        <room>D.conference</room>
        <slug>conference_debconf</slug>
        <title>DebConf Conference Infrastructure</title>
        <subtitle/>
        <track>Conference Organisation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;DebConf has been online for two years using a combination of our in-person infrastructure and new tools. This talk will describe both setups and what has been done to bring DebConf online.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8447">Kyle Robbertze</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/conference_debconf/attachments/slides/5073/export/events/attachments/conference_debconf/slides/5073/debconf_infrastructure_fosdem_2022.pdf">DebConf Conference Infrastructure</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.conference/conference_debconf.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.conference/conference_debconf.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#conference-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-conference_debconf:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#conference-conference_debconf:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13109.php">Submit feedback</link>
        </links>
      </event>
      <event id="12636">
        <start>13:10</start>
        <duration>00:30</duration>
        <room>D.conference</room>
        <slug>conference_stream_edit</slug>
        <title>Using OBS, Jitsi and Kdenlive to stream and edit conference videos</title>
        <subtitle/>
        <track>Conference Organisation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In light of the pandemic, the foss-north conference has gone virtual since 2020. In this presentation we will discuss our live streaming and video recording setup built around OBS, Jitsi and Kdenlive.&lt;/p&gt;

&lt;p&gt;The talk will discuss what software we are running, how and some behind the scenes info about how we run the live events, as well as how we edit and distribute the recordings post event.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3029">Johan Thelin</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/conference_stream_edit/attachments/slides/5120/export/events/attachments/conference_stream_edit/slides/5120/2022_02_fosdem_video_workflow.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.conference/conference_stream_edit.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.conference/conference_stream_edit.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#conference-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-conference_stream_edit:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#conference-conference_stream_edit:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12636.php">Submit feedback</link>
        </links>
      </event>
      <event id="12652">
        <start>13:50</start>
        <duration>00:35</duration>
        <room>D.conference</room>
        <slug>conference_ansible_lessons</slug>
        <title>Lessons from 6 Virtual Ansible Contributor Summits</title>
        <subtitle>a.k.a. I don't know how to come up with a fancy title, I just tell it like it is.</subtitle>
        <track>Conference Organisation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I have been organizing open-source related meetups and conferences for more than a decade. The past two years have been exceptionally trying. Any guesses as to why that is? :)&lt;/p&gt;

&lt;p&gt;In this session, I will share our experiences from the 6 online Ansible Contributor Summits that we have held through 2020-2021. While the virtual platform gave us more flexibility in many ways (such as having 3 events in a year instead of the usual 1), it definitely presented many new challenges as well. From pre-event marketing to technologies used during the summits, post-event surveys + feedback that feed into the next event, it's a continuous cycle of trials, errors, and improvements.&lt;/p&gt;

&lt;p&gt;There is also a major shift towards using open source tools and workflows for the summits, at the request of some community memebers as well as the desire within our team. I'll share what fell short and what thrived, and how the changes impacted not just conference management for our team, but also how the Ansible community received these events. Because at the end of the day, these conferences are for the community contributors and participants!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4205">Carol Chen</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/conference_ansible_lessons/attachments/slides/5102/export/events/attachments/conference_ansible_lessons/slides/5102/Lessons_from_Ansible_Contributor_Summits.pdf">Lessons from 6 Virtual Ansible Contributor Summits</attachment>
        </attachments>
        <links>
          <link href="https://www.ansible.com/community">Ansible Community</link>
          <link href="https://github.com/ansible/community/wiki/News#the-bullhorn">The Bullhorn - Ansible developer newsletter</link>
          <link href="https://github.com/ansible/community/wiki/Contributor-Summit">Ansible Contributor Summit</link>
          <link href="https://video.fosdem.org/2022/D.conference/conference_ansible_lessons.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.conference/conference_ansible_lessons.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#conference-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-conference_ansible_lessons:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#conference-conference_ansible_lessons:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12652.php">Submit feedback</link>
        </links>
      </event>
      <event id="12539">
        <start>14:30</start>
        <duration>00:40</duration>
        <room>D.conference</room>
        <slug>conference_primer</slug>
        <title>FOSS Events Primer</title>
        <subtitle>Get Out There and Run One!</subtitle>
        <track>Conference Organisation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;When you want to see your community grow, running a local event is a great idea. Luckily, many FOSS projects have been down this path, so you won't need to start from scratch. This talk covers the process of running a successful community event, from finding great folks to plan with -- to follow-up for the next event.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;When you love your community, you want to see it grow and become stronger. And if you are also lucky enough to have a little extra time and enthusiasm? Well, then it might be time to run an event. Many FOSS projects have been down this path, so you won't need to start from scratch. This talk will cover:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Setting the scope for your event&lt;/li&gt;
&lt;li&gt;How to find folks to work with&lt;/li&gt;
&lt;li&gt;Creating a plan for success&lt;/li&gt;
&lt;li&gt;Making sure attendees have a great time&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Once you have a solid plan in place, running a community event can be very rewarding. Attendees will walk away with a sense of where to start and a strategy for finding the resources they'll need to put on an inspiring community event.&lt;/p&gt;</description>
        <persons>
          <person id="698">Deb Nicholson</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.conference/conference_primer.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.conference/conference_primer.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#conference-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-conference_primer:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#conference-conference_primer:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12539.php">Submit feedback</link>
        </links>
      </event>
      <event id="12635">
        <start>15:20</start>
        <duration>01:00</duration>
        <room>D.conference</room>
        <slug>conference_pgeu</slug>
        <title>Using pgeu-system to manage your conference</title>
        <subtitle/>
        <track>Conference Organisation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The pgeu-system is an integrated system for managing conferences. Originally developed for Postgresql Europe's own conferences, the system has grown into a generic system for managing events, visitors, speakers, sponsors, and volunteers. It integrates the functions such as call-for-papers, managing schedules, invoicing, accounting, and more.&lt;/p&gt;

&lt;p&gt;In this talk we will do a whirlwind tour of the tool, from the context of the foss-north conference.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3029">Johan Thelin</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/conference_pgeu/attachments/slides/5119/export/events/attachments/conference_pgeu/slides/5119/2022_02_fosdem_pgconf_v2.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.conference/conference_pgeu.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.conference/conference_pgeu.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#conference-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-conference_pgeu:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#conference-conference_pgeu:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12635.php">Submit feedback</link>
        </links>
      </event>
      <event id="13110">
        <start>16:30</start>
        <duration>00:35</duration>
        <room>D.conference</room>
        <slug>conference_fosdem</slug>
        <title>FOSDEM Conference Infrastructure</title>
        <subtitle/>
        <track>Conference Organisation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A technical overview of how the FOSDEM conference is run: the tools we use, the tools we wrote, and the processes we use; both for the in-person version of the conference as well as the online one of which we're doing our second edition this year.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="12">Wouter Verhelst</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/conference_fosdem/attachments/slides/5277/export/events/attachments/conference_fosdem/slides/5277/FOSDEM_talk.odp">Slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.conference/conference_fosdem.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.conference/conference_fosdem.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#conference-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#conference-conference_fosdem:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#conference-conference_fosdem:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13110.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.containers">
    </room>
    <room name="D.cicd">
    </room>
    <room name="D.dart-flutter">
      <event id="13021">
        <start>13:15</start>
        <duration>00:40</duration>
        <room>D.dart-flutter</room>
        <slug>flutter_project_setup</slug>
        <title>Make the code work for you: Flutter Code Generation</title>
        <subtitle/>
        <track>Dart and Flutter</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Every programmer's dream is constantly building new features and seeing how the project grows. However, there is nothing worse than writing a lot of boilerplate code just before even start implementing those features. In this talk, you will learn about Flutter code generation tools and various tips on how to avoid implementing boilerplate code and focus on your next-gen project.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8825">Mangirdas Kazlauskas</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/mkobuolys/flutter-code-generation">GitHub repository</link>
          <link href="https://github.com/mkobuolys/flutter-code-generation/blob/master/presentation-slides.pdf">Presentation slides</link>
          <link href="https://twitter.com/mkobuolys">Reach out to the speaker</link>
          <link href="https://video.fosdem.org/2022/D.dart-flutter/flutter_project_setup.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dart-flutter/flutter_project_setup.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dart-flutter-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dart-flutter-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dart-flutter-flutter_project_setup:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dart-flutter-flutter_project_setup:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13021.php">Submit feedback</link>
        </links>
      </event>
      <event id="13125">
        <start>13:55</start>
        <duration>01:00</duration>
        <room>D.dart-flutter</room>
        <slug>flutter_testing</slug>
        <title>The beautiful world of Flutter Testing</title>
        <subtitle>Introduction to Flutter Testing</subtitle>
        <track>Dart and Flutter</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Modern applications have tons of features and possibilities, and the more features there are, the harder it gets to be tested manually. Also, advocates for Test Driven Development makes testing even more important. In this session, we want to explore the possibilities of how to Test your Features in Dart and Flutter. We will discuss Unit, Widget and Integration tests in this session, what it is and why you will love the support in your next project.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8856">Max Weber</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://docs.flutter.dev/testing">Unit / Widget Testing</link>
          <link href="https://docs.flutter.dev/testing/integration-tests">Integration Testing</link>
          <link href="https://chat.fosdem.org/#/room/#dart-flutter-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dart-flutter-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dart-flutter-flutter_testing:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dart-flutter-flutter_testing:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13125.php">Submit feedback</link>
        </links>
      </event>
      <event id="13120">
        <start>14:55</start>
        <duration>01:00</duration>
        <room>D.dart-flutter</room>
        <slug>flutter_pwa</slug>
        <title>Building PWA with Flutter</title>
        <subtitle/>
        <track>Dart and Flutter</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Progressive Web Apps are web applications that have been designed, so they are capable, reliable, and installable. These three pillars transform them into an experience that feels like a platform-specific application.
The central core components that ensure that PWA works flawlessly are Service Workers. These components are a network proxy that takes control of a network request from the application and adds cache capabilities, background app sync, push notifications, and offline features.
In this talk, I will review the PWA capabilities in Flutter and show you how you can extend these functionalities to have a better progressive web app building with Flutter in order to boost user experience in your application&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8858">Majid Hajian</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://slides.com/mhadaily/building-pwa-with-flutter">slides</link>
          <link href="https://video.fosdem.org/2022/D.dart-flutter/flutter_pwa.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dart-flutter/flutter_pwa.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dart-flutter-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dart-flutter-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dart-flutter-flutter_pwa:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dart-flutter-flutter_pwa:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13120.php">Submit feedback</link>
        </links>
      </event>
      <event id="13121">
        <start>15:55</start>
        <duration>01:00</duration>
        <room>D.dart-flutter</room>
        <slug>flutter_state_management</slug>
        <title>Architectural thinking on Flutter State Management</title>
        <subtitle/>
        <track>Dart and Flutter</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Sometimes state management shapes the application architecture, which we even interchangeably call state management, app architecture. State management is a controversial topic among all developers, and it's, at the same time, one of the most complex topics that developers should decide on when they are building a Flutter app. Many developers say one solution is the best, whereas some disagree! What if I tell you that, in my opinion, there is no right and wrong answer! If you ask a software architect, which state management is the best for an application? The answer is evident; It Depends.
This talk discusses how to think like an architect and understand, recognize, and analyze tradeoffs and characteristics when choosing state management. I will show you why all state management might be best and worst, at the same time for your application which eventually helps you to make your mind to determine your appropriate solution.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8858">Majid Hajian</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://slides.com/mhadaily/architectural-thinking-on-flutter-state-management">slides</link>
          <link href="https://video.fosdem.org/2022/D.dart-flutter/flutter_state_management.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dart-flutter/flutter_state_management.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dart-flutter-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dart-flutter-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dart-flutter-flutter_state_management:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dart-flutter-flutter_state_management:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13121.php">Submit feedback</link>
        </links>
      </event>
      <event id="13127">
        <start>16:55</start>
        <duration>00:30</duration>
        <room>D.dart-flutter</room>
        <slug>flutter_nft</slug>
        <title>Flutter in the NFT world</title>
        <subtitle/>
        <track>Dart and Flutter</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;How to create and deploy NFTs with Flutter and the Algorand blockchain.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4465">Arjan van Eersel</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#dart-flutter-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dart-flutter-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dart-flutter-flutter_nft:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dart-flutter-flutter_nft:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13127.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.minimalistic">
    </room>
    <room name="D.distributions">
    </room>
    <room name="D.embedded">
      <event id="12609">
        <start>12:30</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>embedded_linux_mysteries</slug>
        <title>Five mysteries in Embedded Linux </title>
        <subtitle/>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Once you start out in embedded linux, there is a lot to do. Some things are obvious, some less so. First and foremost, you can put your knowledge of using Linux on the desktop to good use, right? This approach feels like a natural progression, but it has its pitfalls - some of which this talk aims to help you understand and ultimately avoid.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Building and developing an embedded linux system sometimes feels like magic. It's all open source, right? You can just grab the code and make it do your bidding!&lt;/p&gt;

&lt;p&gt;But just like the Sorcerer’s Apprentice in the poem, you might find yourself struggling with the spirits that you just called, like
What a “Distribution” is, and why is it important that you know
Why package management is so different
Where configuration happens, and where not
When to update, and what&lt;/p&gt;

&lt;p&gt;This talks covers five of the most common misconceptions that beginners have when they cast their first spells in embedded linux, not only to avoid them backfiring - but to actually harness the power.&lt;/p&gt;</description>
        <persons>
          <person id="8662">Josef Holzmayr</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/embedded_linux_mysteries/attachments/slides/5004/export/events/attachments/embedded_linux_mysteries/slides/5004/FOSDEM_05_02_2022_Five_Mysteries_In_Embedded_Linux.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.embedded/embedded_linux_mysteries.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/embedded_linux_mysteries.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-embedded_linux_mysteries:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-embedded_linux_mysteries:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12609.php">Submit feedback</link>
        </links>
      </event>
      <event id="12332">
        <start>13:00</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>directfb</slug>
        <title>Back to DirectFB!</title>
        <subtitle>The revival of DirectFB with DirectFB2</subtitle>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;DirectFB2 is a fork of DirectFB, a graphics library designed with embedded systems in mind that was widely used in the GNU/Linux embedded world. DirectFB2 comes with changes such as a Meson build system, a pure C implementation and a modularization of the source code.&lt;/p&gt;

&lt;p&gt;Access to the low-level display is based on a DRM/KMS system module (or possibly on a legacy Framebuffer system module), and depending on the platform, hardware-accelerated graphics rendering can be achieved using the architecture of the GFX driver modules.&lt;/p&gt;

&lt;p&gt;The core library is very light (no external dependencies) and provides basic font/image/video rendering support which can be demonstrated with the DirectFB-examples.&lt;/p&gt;

&lt;p&gt;The use of additional DirectFB providers based on external libraries is also possible thanks to the DirectFB-media package, such as rendering fonts with the FreeType library, rendering images with libpng or jpeg libraries, rendering videos with FFmpeg or GStreamer libraries.&lt;/p&gt;

&lt;p&gt;For 3D graphics, OpenGL or Vulkan rendering can be done with the DirectFB graphics backend. As an example, the Mesa 3D implementation makes OpenGL rendering possible with a DirectFBGL module or with EGL for the DirectFB platform, and the SwiftShader implementation makes Vulkan rendering possible with the DirectFB WSI.&lt;/p&gt;

&lt;p&gt;This talk aims at getting started with DirectFB2 which may be worth considering on some devices.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6436">Nicolas Caramelli</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/directfb/attachments/slides/5077/export/events/attachments/directfb/slides/5077/fosdem_2022_directfb2.pdf">Back to DirectFB!</attachment>
        </attachments>
        <links>
          <link href="https://github.com/directfb2">The DirectFB2 open source project</link>
          <link href="https://video.fosdem.org/2022/D.embedded/directfb.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/directfb.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-directfb:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-directfb:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12332.php">Submit feedback</link>
        </links>
      </event>
      <event id="12497">
        <start>13:30</start>
        <duration>01:00</duration>
        <room>D.embedded</room>
        <slug>automotive_eth_phy</slug>
        <title>Automotive Ethernet PHY bring-up: lessons learned and debug tips</title>
        <subtitle/>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I would like to share my experience bringing up various Automotive Ethernet Gigabit PHYs on an iMX8 platform.&lt;/p&gt;

&lt;p&gt;Agenda:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;PHY configuration CheckList (= What I need to know about my PHY, my schematic before starting the bring-up)&lt;/li&gt;
&lt;li&gt;SW implementation (= step-by-step SW integration + common pitfalls to avoid, mainly focused on Linux, but I talk also about U-Boot)&lt;/li&gt;
&lt;li&gt;Debug tips (= SW and HW tips)&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description>&lt;p&gt;This presentation is based on a training I already gave internally in the Valeo Group (with some extra additions).
This experience led to some patches that I hope to push at U-boot and Linux level.&lt;/p&gt;</description>
        <persons>
          <person id="8580">Jean-Louis Thekekara</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/automotive_eth_phy/attachments/slides/5005/export/events/attachments/automotive_eth_phy/slides/5005/fosdem_2022_automotive_ethernet_jl_thekekara_V2.pdf">Automotive Ethernet PHY bring-up</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.embedded/automotive_eth_phy.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/automotive_eth_phy.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-automotive_eth_phy:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-automotive_eth_phy:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12497.php">Submit feedback</link>
        </links>
      </event>
      <event id="12670">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>rauc_ab_updates</slug>
        <title>Bringing RAUC A/B Updates to More Linux Devices</title>
        <subtitle/>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;RAUC is a safe and secure open source software solution for A/B updates of embedded Linux devices. RAUC supports industry-leading build system: the Yocto Project and OpenEmbedded, Buildroot and PTXdist. Porting RAUC to a new device requires several advanced technical steps. Layer meta-rauc-community exists to speed up and simplify the integration process for Yocto and OpenEmbedded by providing examples for popular devices such as Rasperry Pi, Allwinner (Sunxi), NVIDIA Tegra and QEMU.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;RAUC is a popular solution for A/B updates of embedded Linux devices because of its flexibility, safety and security features. It supports industry-leading build system: Yocto Project and OpenEmbedded, Buildroot and PTXdist. Upgrades are performed through RAUC bundles which can be installed either through the network or just using a USB stick.&lt;/p&gt;

&lt;p&gt;To port RAUC to a new device, we need to go through several steps: setup appropriate bootloader like U-Boot, enable SquashFS in the Linux kernel configurations, use ext4 file system, create partitions and configure RAUC slots, generate certificates and setup bootloader environment configurations with a script to switch RAUC slots over upgrades. To simplify the getting started process of developers using RAUC with Yocto and OpenEmbedded in 2020 Leon Anavi created layer meta-rauc-community. In 2021 the layer was moved to the RAUC organization in GitHub. Initially it offered only Raspberry Pi support and over the time, thanks to numerous community contributions, the support was extended to more machines. As of the moment meta-rauc-community provides RAUC sample integrations for Raspberry Pi, Sunxi (Allwinner), QEMUx86 and NVIDIA Jetson TX2.&lt;/p&gt;

&lt;p&gt;This presentation will provide a brief introduction to RAUC and will focus on layers meta-rauc and meta-rauc-community. We will go through the exact steps how build, flash and update an image using bitbake to the currently supported platforms. Furthermore we will discuss general guidelines for porting RAUC and adding new supported machines to meta-rauc-community in the future.&lt;/p&gt;

&lt;p&gt;The talk is appropriate for anyone with basic knowledge about Linux. It will hopefully help other software developers in the community to overcame faster and easier similar technical difficulties while integrating the RAUC client on embedded Linux devices and hopefully contribute back to the Yocto/OpenEmbedded layer meta-rauc-community.&lt;/p&gt;</description>
        <persons>
          <person id="1603">Leon Anavi</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/rauc_ab_updates/attachments/slides/4863/export/events/attachments/rauc_ab_updates/slides/4863/leon_anavi_rauc_fosdem_2022.pdf">Bringing RAUC A/B Updates to More Linux Devices</attachment>
        </attachments>
        <links>
          <link href="https://rauc.io/">RAUC</link>
          <link href="https://github.com/rauc/meta-rauc">Yocto/OE layer meta-rauc</link>
          <link href="https://github.com/rauc/meta-rauc-community">Yocto/OE layer meta-rauc-community</link>
          <link href="https://pretalx.com/yocto-project-summit-2021-11/talk/83YKWV/">A/B Linux updates with RAUC and meta-rauc-community: now &amp; in the future</link>
          <link href="https://pretalx.com/yocto-project-summit-2020/talk/JJYPH3/">Software Updates with RAUC, the Yocto Project and OpenEmbedded</link>
          <link href="https://www.konsulko.com/getting-started-with-rauc-on-raspberry-pi-2/">Getting Started with RAUC on Raspberry Pi</link>
          <link href="https://video.fosdem.org/2022/D.embedded/rauc_ab_updates.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/rauc_ab_updates.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-rauc_ab_updates:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-rauc_ab_updates:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12670.php">Submit feedback</link>
        </links>
      </event>
      <event id="12620">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>D.embedded</room>
        <slug>ply_ebpf</slug>
        <title>ply: lightweight eBPF tracing</title>
        <subtitle/>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk, I will show you how to build and deploy ply (a dynamic tracing language for eBPF) to a BeagleBone Black then write ply scripts to attach probes and tracepoints to a running kernel and application on that same target. eBPF has rapidly eclipsed all previous tracers for Linux. While eBPF has taken the cloud native community by storm, the technology has yet to make significant inroads within the embedded Linux ecosystem. I will explain the reasons for this current situation and demonstrate a possible way forward.&lt;/p&gt;

&lt;p&gt;The bpftrace dynamic tracing language relies on the LLVM-based BCC toolchain to compile scripts down to eBPF bytecode. Because of its dependency on LLVM, BCC only supports a few 64-bit CPU architectures, severely limiting the use of eBPF in embedded systems. Fortunately, the IO Visor Project offers a lightweight alternative to bpftrace called ply. Like bpftrace, ply’s syntax is inspired by both DTrace and awk. Unlike bpftrace, ply targets embedded CPU architectures like ARM and PowerPC making it possible to deploy eBPF to many more devices. Buildroot includes ply as of its 2021.02 LTS release.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8663">Frank Vasquez</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.embedded/ply_ebpf.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/ply_ebpf.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-ply_ebpf:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-ply_ebpf:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12620.php">Submit feedback</link>
        </links>
      </event>
      <event id="12669">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>build_systems_all_way_down</slug>
        <title>Build Systems all the way down.</title>
        <subtitle>Untangling OpenEmbedded/meta-zephyr/zephyr integration in Eclipse Oniro</subtitle>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk, pidge will take a critical look at the places where meta-zephyr
succeeds and fails in its original goals, the reasons behind that and the
steps being taken to fix those issues.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;OpenEmbedded, Zephyr and meta-zephyr are powerful tools that can give IoT
developers the ability to rapidly develop embedded solutions. Integrating
them all however is challenging, made more so by wrapping multiple build
systems, machine configurations and build languages into a coherent solution.&lt;/p&gt;

&lt;p&gt;In this talk, pidge is going to show changes being implemented through her work
on the Eclipse Oniro project to the meta-zephyr layer that bring most zephyr
supported machine configurations into meta-zephyr but also removes the need for
OE machine  configurations to have any knowledge of core zephyr modules. She will
discuss the issues she encountered around integating those changes from the zephyr
side.&lt;/p&gt;</description>
        <persons>
          <person id="8676">Eilís Ní Fhlannagáin</person>
        </persons>
        <attachments>
          <attachment type="audio" href="https://fosdem.org/2022/schedule/event/build_systems_all_way_down/attachments/audio/5075/export/events/attachments/build_systems_all_way_down/audio/5075/Build_systems_all_the_way_down.pdf">Build Systems All The Way Down FOSDEM-2022</attachment>
        </attachments>
        <links>
          <link href="https://git.yoctoproject.org/meta-zephyr">meta-zephyr</link>
          <link href="https://oniroproject.org/">Oniro: The Distributed Operating System That Connects Consumer Devices Big and Small</link>
          <link href="https://video.fosdem.org/2022/D.embedded/build_systems_all_way_down.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/build_systems_all_way_down.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-build_systems_all_way_down:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-build_systems_all_way_down:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12669.php">Submit feedback</link>
        </links>
      </event>
      <event id="12632">
        <start>16:30</start>
        <duration>01:00</duration>
        <room>D.embedded</room>
        <slug>fpga_programming</slug>
        <title>One stop shop: Best Practices for Programming Embedded FPGAs</title>
        <subtitle/>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;FPGAs are increasingly being used in today's embedded systems. But they are notoriously complex for having a difficult programming model. In order to counter this complexity, there has been a growing focus to design FPGA hardware at a higher level of abstraction with new languages and compilers. This talk will serve as "one stop shop" for topics related to these developments.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Are you an embedded developer? Do you like FPGAs? Do you want to know the best programming practices for embedded systems that deploy FPGAs?  Do you like economical hardware? Do you like open source projects? If your answer is "yes" to either of the aforementioned questions, then this talk is for you. As the title goes, this talk and its content will actually be "one stop shop" for best practices related to FPGA programming. Considering C-based languages still dominate the embedded systems, the talk will focus on new methodologies that can be broadly implemented while using all C-based (C/C++/C#) languages when it comes to implement your designs on FPGAs. To take it further, the talk will shift focus on C++ as C++ is finally picking up pace to come even more closer to low level hardware as compared to previous C++ standards. The last four C++ standards have come a long way to make C++ language even more compatible with embedded systems. Many open source FPGA libraries are based on modern C++. At the end of the day, you will know how a modern embedded developer can adopt certain coding practices to fully exploit the underlying spatial parallelism of FPGA hardware. Additionally, you will learn about open source compilers, open source projects, and economical FPGAs hardware to implement these best practices.&lt;/p&gt;</description>
        <persons>
          <person id="7580">Babar Khan</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.embedded/fpga_programming.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/fpga_programming.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-fpga_programming:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-fpga_programming:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12632.php">Submit feedback</link>
        </links>
      </event>
      <event id="12685">
        <start>17:30</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>gpio_linux_vs_zaphyr</slug>
        <title>GPIO across Linux and Zephyr kernels</title>
        <subtitle>Maximizing code reuse in the example of the Oniro doorlock blueprint</subtitle>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Sometimes it is useful to share code across multiple kernels -- in projects
like the Oniro door lock blueprint, for the typical use cases a Cortex-M
CPU running Zephyr is more than sufficient, but using its functionality as
part of a larger project makes using Linux on Cortex-A an interesting
option. Can we find a way to maximize code reuse despite the very different
GPIO APIs?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Sometimes it is useful to share code across multiple kernels -- we avoid
doing the work twice. However, this might be complicated when one version
is using Zephyr with a Cortex-M, and another Linux on a Cortex-A.
We will explore this problem using an example of the door lock blueprint
from the Eclipse Oniro project - an implementation of basic door lock
functionality.
For a typical use-case, a Cortex-M with Zephyr is more than sufficient,
but we might also want to integrate the same application in a bigger one
using Linux on a Cortex-A. Will we find a way to do so?&lt;/p&gt;</description>
        <persons>
          <person id="2501">Bernhard Rosenkränzer</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://oniroproject.org/">The Oniro Project</link>
          <link href="https://docs.oniroproject.org/projects/blueprints/en/latest/doorlock.html">The Door Lock blueprint</link>
          <link href="https://video.fosdem.org/2022/D.embedded/gpio_linux_vs_zaphyr.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/gpio_linux_vs_zaphyr.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-gpio_linux_vs_zaphyr:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-gpio_linux_vs_zaphyr:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12685.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.emulator">
    </room>
    <room name="D.mobile">
      <event id="12493">
        <start>10:10</start>
        <duration>00:40</duration>
        <room>D.mobile</room>
        <slug>mobile_kernel_tablet</slug>
        <title>Mainlining the reMarkable 2 eInk tablet</title>
        <subtitle/>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The reMarkable 2 is an eInk tablet, based on the i.MX7 SoC. The tablet
ships with a fork of the 4.14 kernel and a custom rootFS built with
OpenEmbedded. The vendor kernel is based on the NXP vendor kernel with a
large collection of rM2 specific patches on top.&lt;/p&gt;

&lt;p&gt;This talk discusses the process of adding support for the rM2 to the mainline
Linux kernel. The talk first discusses the process of understanding the
original boot process and then getting access to a download mechanism and
serial console.&lt;/p&gt;

&lt;p&gt;Finally the talk covers the process to start upstreaming the patches from a
vendor kernel to the mainline kernel.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8553">Alistair Francis</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_kernel_tablet/attachments/slides/4921/export/events/attachments/mobile_kernel_tablet/slides/4921/rM2_FOSDEM_Slides.pdf">rM2 FOSDEM Slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_tablet.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_tablet.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_kernel_tablet:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_kernel_tablet:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12493.php">Submit feedback</link>
        </links>
      </event>
      <event id="12333">
        <start>10:55</start>
        <duration>00:40</duration>
        <room>D.mobile</room>
        <slug>mobile_nemomobile</slug>
        <title>Nemomobile</title>
        <subtitle>Bringing freedom to mobile</subtitle>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Nemomobile is operating system for mobile devices based on Manjaro Linux and Glacier UI. It mainly developed on PinePhone, but it could be runned also on android devices. The talk will summarize its current status and its direction in future.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8464">Jozef Mlich</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_nemomobile/attachments/slides/4960/export/events/attachments/mobile_nemomobile/slides/4960/2022_02_05_Fosdem_NemoMobile.odp">NemoMobile Presentation</attachment>
        </attachments>
        <links>
          <link href="https://nemomobile.net/">https://nemomobile.net/</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_nemomobile.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_nemomobile.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_nemomobile:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_nemomobile:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12333.php">Submit feedback</link>
        </links>
      </event>
      <event id="12566">
        <start>11:45</start>
        <duration>00:25</duration>
        <room>D.mobile</room>
        <slug>mobile_kernel_l5</slug>
        <title>Librem 5 phone kernel report</title>
        <subtitle/>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I work with Purism SPC on the Librem 5 phone kernel. I regularly post
what our team pushes upstream into the mainline kernel at
https://puri.sm/posts/author/martin/&lt;/p&gt;

&lt;p&gt;In this little talk I want to summarize what we've done, describe how
we do it and put it into perspective a bit.&lt;/p&gt;

&lt;p&gt;I'll outline rough future plans and of course encourage to participate
in case you own that phone.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4178">Martin Kepplinger</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_l5.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_l5.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_kernel_l5:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_kernel_l5:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12566.php">Submit feedback</link>
        </links>
      </event>
      <event id="12692">
        <start>12:30</start>
        <duration>00:30</duration>
        <room>D.mobile</room>
        <slug>mobile_mandriva</slug>
        <title>Taking a desktop OS to mobile phones</title>
        <subtitle>OpenMandriva now runs on the PinePhone - what did we have to do?</subtitle>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;OpenMandriva and its predecessors have been in the desktop and server world since the 1990s - now OpenMandriva 4.3 can run on the PinePhone. What did we have to do to get there and what problems have to be solved before it can fully replace that Android phone in my pocket?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Porting to the ARM (64-bit) architecture was relatively easy (and needed for some other projects).
Modifying the build system to handle bootloaders other than grub and distribution formats other than iso images and special per-device kernels? Easy to hack but not that easy if you want to do it right. We needed to do something that doesn't go quite as far as OpenEmbedded/Yocto, but still is powerful enough to handle many different devices.
Making the hardware work? Largely solved by the upstream community.
Finding or developing apps for base functionality, and making them work for the phone form factor? Mostly solved (with a few caveats).
But how can we work with Android and/or iOS apps (currently required to e.g. log in to most bank accounts)? How can we make this appealing to a normal user?&lt;/p&gt;</description>
        <persons>
          <person id="2501">Bernhard Rosenkränzer</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://openmandriva.org/">OpenMandriva</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_mandriva.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_mandriva.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_mandriva:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_mandriva:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12692.php">Submit feedback</link>
        </links>
      </event>
      <event id="12375">
        <start>13:30</start>
        <duration>00:40</duration>
        <room>D.mobile</room>
        <slug>mobile_mobian</slug>
        <title>2 Years of Mobian</title>
        <subtitle>Birth and growth of a mobile Linux distribution</subtitle>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Mobian project was initiated a few days prior to FOSDEM'20, back when the first PinePhones (BraveHeart edition) were arriving in the hands of developers and enthusiasts. From a single-person weekend project aimed at running Debian on one specific device, to one of the major mobile Linux distributions, let's board into a journey through the past, present and future of Mobian!&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Mobian started as a collection of hacks and scripts for running Debian on the PinePhone. Initially published as "Debian+Phosh" on the PINE64 forum, all packages were manually (cross) compiled and uploaded to the developer's personal web server.&lt;/p&gt;

&lt;p&gt;Over time, it gathered a strong community of users and developers and ultimately gained recognition from the wider mobile Linux community, to the point where it partnered with PINE64 to release a "Mobian Community Edition" PinePhone. Over the course of its 2 years of existence, the project implemented tools to ease development and automate deployment, and added support for more mobile devices, such as Purism's Librem 5, but also Surface Pro tablets and a few Android phones such as the OnePlus 6 and Pocophone F1.&lt;/p&gt;

&lt;p&gt;This talk will walk you through those 2 years of development, highlighting the project's contributions to the (mobile) FLOSS ecosystem. We will also emphasize how its members work, as part of the DebianOnMobile team, towards its ultimate goal of becoming irrelevant by making Debian a reference distribution on mobile devices. Finally, we will give you an update on the project's current status and plans.&lt;/p&gt;</description>
        <persons>
          <person id="5682">Arnaud Ferraris</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_mobian/attachments/slides/5146/export/events/attachments/mobile_mobian/slides/5146/Mobian_FOSDEM22.pdf"/>
        </attachments>
        <links>
          <link href="https://mobian-project.org">Project website</link>
          <link href="https://gitlab.com/mobian1">Git repositories</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_mobian.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_mobian.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_mobian:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_mobian:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12375.php">Submit feedback</link>
        </links>
      </event>
      <event id="12682">
        <start>14:20</start>
        <duration>00:40</duration>
        <room>D.mobile</room>
        <slug>mobile_kernel_mainline</slug>
        <title>Porting mainline Linux to mobile phones</title>
        <subtitle/>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A general overview of porting Linux to mobile phones, with a focus on Qualcomm. From the device tree to how you get started and why you should do it.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Android phones have long been plagued by being based on old versions of the Linux kernel which are seldom patched against vulnerabilities and other security flaws. Additionally being based on old versions which are most of the time not being maintained by anyone anymore a vendor has to evaluate if a given patch applies to the old kernel version they are using or not and modify the patch if necessary. This problem has been somewhat mitigated by closer collaboration between SoC vendors and the Linux kernel community (LTS kernels) but this only applies to drivers and components that are actually present in the main branch of the Linux kernel. Drivers only present in vendor-maintained branches often get left out of security and general bug fixes.&lt;/p&gt;

&lt;p&gt;Unfortunately for many companies there isn't a clear financial reason to clean up device drivers and submit them upstream, so in this talk I will give an introduction into how you can get started in making your device run a kernel that's based on mainline Linux.&lt;/p&gt;

&lt;p&gt;Running alternative operating systems (other than Android) on your phone is in some cases possible with the kernel provided by the vendor but in these cases you need to rely on solutions like libhybris to work with proprietary user space binaries and libraries to make hardware work. Running 100% open source software while using a vendor-provided kernel ("downstream kernel") is not feasible due to the sheer number of proprietary user space components that would need to be replaced. But with a mainline kernel you can get to a fully free and open source operating system for your phone. And this talk will give you can introduction to some of the basics in getting started with running mainline Linux kernel on your phone and some of the tips and tricks that I have learned over the years.&lt;/p&gt;</description>
        <persons>
          <person id="8640">Luca Weiss</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_kernel_mainline/attachments/slides/4856/export/events/attachments/mobile_kernel_mainline/slides/4856/Porting_mainline_Linux_to_mobile_phones.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_mainline.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_mainline.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_kernel_mainline:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_kernel_mainline:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12682.php">Submit feedback</link>
        </links>
      </event>
      <event id="12842">
        <start>15:20</start>
        <duration>00:40</duration>
        <room>D.mobile</room>
        <slug>mobile_kernel_ebook_reader</slug>
        <title>The road towards using regular linux on ebook readers</title>
        <subtitle>Experiences and progress with Kobo/Tolino readers</subtitle>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Most Kobo/Tolino readers offer a well marked console port and often a second UART. If they are not water resistant, they offer an internal µSD card slot containing the whole operating system and bootloader so that sounds like an invitation to do something interesting with them besides just reading books. Especially in prolonged outdoor activities, the display and their low power consumption have their merits. Hardware is quite similar, so you also have chances to get a replacement next corner.
Several devicetrees and also some drivers made their way into mainline linux now, on others upstreaming work is in progress. Support is starting to find its way into mobile linux distributions like postmarketOS and graphics start to work with standard APIs.
In this talk I talk about my experiences, especially the current state of support in mainline linux, what is missing and what are the challenges. I will also talk about requirements for the graphics userspace and shortly present my favorite use case: displaying maps.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8708">Andreas Kemnade</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/akemnade/linux/wiki/Kobo---Tolino-E-Bookreader-branches-and-status">Kernel/Mainlining overview</link>
          <link href="https://github.com/akemnade/u-boot-fslc/wiki">U-Boot 2020.10 for mentioned e-book readers</link>
          <link href="https://wiki.postmarketos.org/wiki/Kobo_Clara_HD_(kobo-clara)">postmarketOS for Kobo Clara HD</link>
          <link href="https://wiki.postmarketos.org/wiki/Tolino_Shine_2HD_(tolino-shine2hd)">postmarketOS for Tolino Shine 2HD</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_ebook_reader.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_ebook_reader.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_kernel_ebook_reader:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_kernel_ebook_reader:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12842.php">Submit feedback</link>
        </links>
      </event>
      <event id="12752">
        <start>16:30</start>
        <duration>01:30</duration>
        <room>D.mobile</room>
        <slug>mobile_camera</slug>
        <title>Status of camera support on mobile FOSS devices</title>
        <subtitle>An open discussion about the state of cameras on Linux-powered mobile devices</subtitle>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Camera support has traditionally been a pain point when it comes to
Linux phones.&lt;/p&gt;

&lt;p&gt;Years and years of competition on the photography capabilities of
consumer devices have pushed vendors to adopt more and more custom,
closed source implementations, leaving users of free software powered mobile
devices with nothing but poor solutions limited to work on the single
devices they have been developed for.&lt;/p&gt;

&lt;p&gt;With the increasing maturation of libcamera, a complete user space
camera stack for Linux devices is now finally available, and Linux
phones developers can now cooperate on more mature camera solutions
for their devices.&lt;/p&gt;

&lt;p&gt;The BoF will serve for phone developers and camera developers as a
cooperation space, to better understand their mutual needs and move
forward camera support for the whole Linux ecosystem.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Cameras have traditionally been a distinguishing factor in the
traditional mobile/smartphone market. Year after year the number of
pixels available in a phone's camera have become a stable part of the
phone producers marketing material and as a direct consequence of such
fierce competition everything around cameras has usually been quite
secretive, with vendors implementing rather cumbersome software
architectures to work around the software licensing requirements which
would have otherwise required them to open at least part of what they
consider their secret sauces.&lt;/p&gt;

&lt;p&gt;Vendor's reluctance to discuss and innovate in a common shared space
and the undeniable deficiencies (or better, the complete lack of
existence) of anything resembling a camera stack in the Linux
ecosystem has pushed camera support to a quite uncomfortable position
when it comes to FOSS-powered mobile devices. Until very recently nothing
comparable to what could be achieved by a rather cheap Android phone,
running binary blobs both in user and kernel space, can be easily
realized by using a fully open infrastructure.&lt;/p&gt;

&lt;p&gt;Three years after starting of the libcamera project,
its adoption as the default camera stack for the Raspberry Pi
ecosystem and its increasing permeation in the x86 device space thanks to
the support of vendors like ChromeOS and a more robust integration in Pipewire,
it's now time to finally address the camera issue in the FOSS phone space.&lt;/p&gt;

&lt;p&gt;With the recent interest from Librem5 and Pinephone communities in the
project, this BoF intends to provide a space where phone developers,
libcamera developers and hopefully vendors can discuss their mutual
headaches and try to sketch a way forward in order to provide to
free-software equipped mobile device a camera support that can do more than what
an Android phone was capable of 10+ years ago.&lt;/p&gt;</description>
        <persons>
          <person id="4604">Jacopo Mondi</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_camera/attachments/slides/5167/export/events/attachments/mobile_camera/slides/5167/camera_on_mobile.pdf"/>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_camera/attachments/slides/5172/export/events/attachments/mobile_camera/slides/5172/bof.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_camera.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_camera.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_camera:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_camera:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12752.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.radio">
    </room>
    <room name="D.openjdk">
      <event id="12349">
        <start>10:00</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>javahotnfresh</slug>
        <title>Keeping Your Java Hot &amp; Fresh in 2022</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Despite being nearly 27 years old, Java is still consistently rated in the top three most popular programming languages in use.  The reason for this popularity extends beyond the syntax of the language to the power of the Java Virtual Machine (JVM).  With its ability to handle internet-scale workloads, the JVM delivers the performance required for mission-critical enterprise applications.&lt;/p&gt;

&lt;p&gt;In this session, we’ll explore Java as it is in 2022.  JDK 17 is the ninth (yes, ninth) release in four years.  As a long-term support (LTS) release, this is one that many users will choose to use in production.  We’ll review the significant new features developers will now be able to exploit as they develop their next applications. With JDK 18 just around the corner and longer term projects like Loom likely to be included soon, what does this year hold for Java?&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3512">Simon Ritter</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/javahotnfresh.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/javahotnfresh.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-javahotnfresh:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-javahotnfresh:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12349.php">Submit feedback</link>
        </links>
      </event>
      <event id="13131">
        <start>10:40</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>openjdk17</slug>
        <title>Records and Text Blocks: But What Else Is Interesting In OpenJDK 17?</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;By now, we all know that JDK 17 is the latest Java long-term supported release with several new language features. There are already many resources that explain the Java Record and Text Blocks in detail. But JDK 17 has much more interesting changes since JDK 11.&lt;/p&gt;

&lt;p&gt;In this session, I go into more detail about some other interesting changes that are not language features but are a good reason to switch to JDK 17.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Improvements in the Class Data Sharing feature.&lt;/li&gt;
&lt;li&gt;JDK Flight Recorder for monitoring purposes.&lt;/li&gt;
&lt;li&gt;Improvements in Performances in the Garbage collectors&lt;/li&gt;
&lt;li&gt;Preventing security issues with context-specific deserialization filters.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Besides the explanation, you also see these changes in action with some demos.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7725">Rudy De Busscher</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/openjdk17/attachments/slides/5126/export/events/attachments/openjdk17/slides/5126/OpenJDK17_WhatElseIsInteresting"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/openjdk17.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/openjdk17.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-openjdk17:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-openjdk17:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13131.php">Submit feedback</link>
        </links>
      </event>
      <event id="12908">
        <start>11:20</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>kotlin</slug>
        <title>Introducing Kotlin In Your Organization: From The Ground Up</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A little guide on how to convince management to try out new technologies!&lt;/p&gt;

&lt;p&gt;For you it's obvious, Kotlin is the next big thing and it'll bring your team to the next level. You see clear advantages, but others are not quite there yet. In this talk, I'll describe the ways we found to get Kotlin inside ING, one of the largest European bank. We'll look into simple ways to convince your colleagues, your management and make it a success for everyone!&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Those days, there are so many tools to improve one developer's workflow that it's hard to make a choice, and sometimes convince others. Languages, frameworks, tooling, paradigms, there is so much to try and not everything can be a benefit.&lt;/p&gt;

&lt;p&gt;In this talk, we will have a look at why Kotlin probably makes a lot of sense for your team. We'll have a quick glance at some language features, the ecosystem and the community as well.&lt;/p&gt;

&lt;p&gt;But we'll mostly have a look at various techniques to make Kotlin (or for that matter, any other kind of proposal) a convincing user case for your team.
Finding your heroes, making small experiments, using external influence, building in public, defusing possible worries, there are many ways to go about it!&lt;/p&gt;

&lt;p&gt;By the end of this talk, you will have extra information on why Kotlin can be useful for you (or not); and be equipped with strategies to help convince others as well.&lt;/p&gt;</description>
        <persons>
          <person id="8783">Julien Lengrand-Lambert</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://lengrand.fr/introducing-kotlin-at-ing-a-long-but-rewarding-story/">A blog about how we introduced Kotlin at ING</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/kotlin.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/kotlin.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-kotlin:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-kotlin:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12908.php">Submit feedback</link>
        </links>
      </event>
      <event id="12913">
        <start>12:00</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>foreignfunctions</slug>
        <title>Let's Talk About Foreign Functions In Java</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Java 17 finally gave us the first incubator of Foreign Function &amp;amp; Memory API. Let's do a test drive of what is in store and see if it is good enough to replace JNI. Let's be honest, JNI is not that secure and is controversial and it's high time we move away from it and adopt FFI like in many other modern languages. But is the new API enough or do we need to consider external libraries like JNA or JNR-FFI? I'll showcase some examples of using the new API with some of my other favorite languages.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8784">Deepu  K Sasidharan</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/foreignfunctions/attachments/slides/5165/export/events/attachments/foreignfunctions/slides/5165/Lets_talk_about_FFI_in_Java.pdf">Lets talk about FFI in Java</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/foreignfunctions.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/foreignfunctions.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-foreignfunctions:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-foreignfunctions:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12913.php">Submit feedback</link>
        </links>
      </event>
      <event id="12916">
        <start>12:40</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>panama</slug>
        <title>Native Language Access: Project Panama for Newbies</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A brief introductory talk on Java 17's New project Panama APIs to get your feet wet into the world of native language access or better known as Foreign Function Interface APIs (JEP 412).&lt;/p&gt;</abstract>
        <description>&lt;p&gt;As a Java developer, you may have a need to access native libraries, such as Tensorflow, SqlLite, ffmpeg, OpenGL, but later find that JNI is your default choice. JNI (Java Native Interface) requires native code to be installed. You’ll quickly find that JNI wrapper code is difficult to maintain. New to OpenJDK 17 is the Foreign Linker API (JEP 412) as a replacement or alternative for JNI to provide a pure-Java solution and perform comparable to, or better than, JNI.
The aim of this talk is to help you be proficient at creating Java programs capable of accessing devices and/or native libraries mainly focussing on OpenJDK 17’s Foreign Linker API.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Intro (what, why, where) &lt;/li&gt;
&lt;li&gt;Requirements &lt;/li&gt;
&lt;li&gt;IDE, environment setup &lt;/li&gt;
&lt;li&gt;Getting started &lt;/li&gt;
&lt;li&gt;Anatomy of a Hello World in C &lt;/li&gt;
&lt;li&gt;What is jextract &lt;/li&gt;
&lt;li&gt;Panama Hello World in Java &lt;/li&gt;
&lt;li&gt;How to allocate memory to work with C primitives, arrays, &amp;amp; C strings. &lt;/li&gt;
&lt;li&gt;How to allocate and mimic pointers, structs, and array of structs. &lt;/li&gt;
&lt;li&gt;What are VarHandles? &lt;/li&gt;
&lt;li&gt;What are MethodHandles? &lt;/li&gt;
&lt;li&gt;Using your super powers to access system libraries &lt;/li&gt;
&lt;li&gt;Using your super powers to access third party libraries (demos) 
Demos may include: OpenGL, LeapMotion device, Git, ffmpeg, Python, Swift, MacOS touchID,
MacOS SpeechSynthesizer.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;All Code will be available online at https://github.com/carldea/panama4newbies&lt;/p&gt;</description>
        <persons>
          <person id="7941">Carl Dea</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://foojay.io/today/project-panama-for-newbies-part-1/">Panama 4 Newbies Part 1</link>
          <link href="https://foojay.io/today/project-panama-for-newbies-part-2/">Panama 4 Newbies Part 2</link>
          <link href="https://foojay.io/today/project-panama-for-newbies-part-3/">Panama 4 Newbies Part 3</link>
          <link href="https://github.com/carldea/panama4newbies">GitHub source code</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/panama.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/panama.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-panama:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-panama:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12916.php">Submit feedback</link>
        </links>
      </event>
      <event id="12773">
        <start>13:20</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>log4j1</slug>
        <title>Java Security: Log4J, the SecurityManager, and Funding</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A demonstration of log4j exploits, which defenses people tried, and which worked. We'll cover how groups responded effectively to patch to see what was common.
We'll also look at open source funding models, subscriptions, and bug bounty programs to see why it's sometimes hard to donate.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This talk will use actual exploit code that takes over systems through their log messages to open calculators.&lt;/p&gt;</description>
        <persons>
          <person id="8735">Erik Costlow</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/log4j1.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/log4j1.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-log4j1:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-log4j1:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12773.php">Submit feedback</link>
        </links>
      </event>
      <event id="13212">
        <start>14:00</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>log4j2</slug>
        <title>Security Warning: Your Java Attack Surface Just Got Bigger</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Building cloud-native Java applications is undoubtedly awesome.&lt;/p&gt;

&lt;p&gt;However, it comes with undeniable new risks. Next to your own code, you are relying on so many other things.&lt;/p&gt;

&lt;p&gt;Blindly depending on open-source libraries and Docker images can form a massive risk for your application.&lt;/p&gt;

&lt;p&gt;The wrong package can introduce severe vulnerabilities into your application, exposing your application and your user's data.&lt;/p&gt;

&lt;p&gt;Join this talk where we’ll show common threats, vulnerabilities, and misconfiguration including the recently disclosed issues in Log4j.&lt;/p&gt;

&lt;p&gt;Most importantly, you’ll learn how to protect your application with actionable remediation and best practices.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7937">Brian Vermeer</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/log4j2.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/log4j2.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-log4j2:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-log4j2:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13212.php">Submit feedback</link>
        </links>
      </event>
      <event id="13077">
        <start>14:40</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>jvmtweaks</slug>
        <title>Simple Tweaks To Get The Most Out Of Your JVM</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Many developers don’t think about the JVM level when creating applications. It is something that just simply works. Now more applications are becoming cloud-native and we have JVM’s running in every microservice container, each performance gain can have massive benefits when scaled up. Some tweaks are very easy to implement and can have huge impacts on start-up time and performance of your applications. This talk will go through all the different JVM options and give you some easy and simple advice on how to get the most out of your JVM to save not only money but also energy on the cloud.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8843">Jamie Coleman</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/jvmtweaks.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/jvmtweaks.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-jvmtweaks:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-jvmtweaks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13077.php">Submit feedback</link>
        </links>
      </event>
      <event id="12637">
        <start>15:20</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>tornadovm</slug>
        <title>TornadoVM: Hardware Acceleration For Java In Practice</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Hardware acceleration has become prevalent in most application domains as a means to increase performance, while also achieving high energy efficiency. However, the programming models for heterogeneous hardware accelerators inherently support C/C++, thereby hindering the exploitation of heterogeneous resources from managed languages, such as Java. In the University of Manchester, we have been developing  TornadoVM; an open-source software technology that can be used as a plugin to OpenJDK and other JVM distributions to enable hardware acceleration in a programmer friendly manner.&lt;/p&gt;

&lt;p&gt;In this talk, we will present a practical view of TornadoVM and focus on two parts: (i) analyze what can impact the performance of applications on heterogeneous co-processors, and (ii) how Java developers can utilize TornadoVM to increase the performance of their applications.&lt;/p&gt;

&lt;p&gt;https://github.com/beehive-lab/TornadoVM&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7005">Thanos Stratikopoulos</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/tornadovm/attachments/slides/5272/export/events/attachments/tornadovm/slides/5272/slides">TornadoVM-FOSDEM22</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/tornadovm.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/tornadovm.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-tornadovm:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-tornadovm:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12637.php">Submit feedback</link>
        </links>
      </event>
      <event id="12864">
        <start>16:00</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>alpaca</slug>
        <title>Java &amp; Alpaca: A Beautiful Friendship</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;BellSoft created tiny containers based on Alpine Linux. But Alpine has its cons: musl sometimes performs worse than glibc, LTS support is not long enough. So we developed Alpaca Linux based on Alpine. Alpaca is more performant and secure, has longer LTS support, and is perfect for Java deployment.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The size matters when it comes to containers: they should be small but performant. BellSoft engineers came up with the solution and integrated the Alpine musl port into JDK 16. We made containers based on Alpine Linux and immediately understood that we hit the spot. These containers are still in demand and keep gaining popularity.
Alpine Linux is based on musl. There is usually no difference in performance, but in some cases, musl is less efficient than glibc. The problem is that any Linux distro is made for general purposes, and Linux engineers don’t have Java in mind when developing them.
In addition, LTS support for Linux kernel and OpenJDK is longer than that for Alpine Linux, which leads to a more frequent migration between OS versions within one Java release.
We want to make sure that Java LTS visions are stable within the environments we offer. This is why we created our own distribution, Alpaca Linux, based on Alpine.
Alpaca Linux has a longer support cycle and includes musl-perf and other components to boost the performance of apps, including Java-based ones.
In my talk, I will describe the differences between Alpaca and Alpine and show the results of the benchmarks. I will also tell you about the Alpaca release cycle and how to get hands on with this new Linux distro. You will find out how to boost the performance and security of Java deployment with Alpaca Linux. All in all, I think that this is the beginning of a beautiful friendship between Alpaca and Java.&lt;/p&gt;</description>
        <persons>
          <person id="8769">Dmitry Chuyko</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/alpaca.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/alpaca.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-alpaca:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-alpaca:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12864.php">Submit feedback</link>
        </links>
      </event>
      <event id="12843">
        <start>16:40</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>threading</slug>
        <title>Java Threading Essentials</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;To be a proficient java developer, you must learn Java Thread programming. Thread is the heart of the Java ecosystem. All the server-side programming model heavily depends on the java concurrency model. In this session, I will explain a few essential aspects of the java thread model from the ground up so that a beginner can build up their concurrency knowledge on top of it. The session will include -&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;How to create a simple concurrent program&lt;/li&gt;
&lt;li&gt;Identify the benefits of java threadings&lt;/li&gt;
&lt;li&gt;Understanding the bagasse that comes with threads and how to avoid them&lt;/li&gt;
&lt;li&gt;What are the threadsafe classes available in the JDK&lt;/li&gt;
&lt;/ol&gt;
</abstract>
        <description></description>
        <persons>
          <person id="8686">Bazlur Rahman</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/threading.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/threading.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-threading:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-threading:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12843.php">Submit feedback</link>
        </links>
      </event>
      <event id="12924">
        <start>17:20</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>fuzion</slug>
        <title>Fuzion: A New Language For The OpenJDK Unifying Java's Concepts</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Fuzion is a modern general purpose programming language that unifies concepts
found in structured, functional and object-oriented programming languages into
the concept of a Fuzion feature.  It combines a powerful syntax and safety
features based on the design-by-contract principle with a simple intermediate
representation that enables powerful optimizing compilers and static analysis
tools to verify correctness aspects.&lt;/p&gt;

&lt;p&gt;This talk will explain how Java's concepts such as classes, interfaces, methods,
constructors, packages, etc. are mapped to the single concept of a Fuzion
feature.  The fzjava tool will be explained that provides Fuzion interfaces to
Java libraries.  Finally, the Fuzion interpreter and a (planned) Java byte-code
back-end are presented.&lt;/p&gt;</abstract>
        <description>&lt;h1&gt;Introduction&lt;/h1&gt;

&lt;p&gt;Fuzion is a modern general purpose programming language that unifies concepts
found in structured, functional and object-oriented programming languages into
the concept of a Fuzion feature.  It combines a powerful syntax and safety
features based on the design-by-contract principle with a simple intermediate
representation that enables powerful optimizing compilers and static analysis
tools to verify correctness aspects.&lt;/p&gt;

&lt;p&gt;Fuzion was influenced by many other languages including Java, Python, Eiffel,
Rust, Go, Lua, Kotlin, C#, F#, Nim, Julia, Clojure, C/C++, and many more.  The
goal of Fuzion is to define a language that has the expressive power present in
these languages and allow high-performance implementations and powerful analysis
tools.  Furthermore, Fuzion addresses requirements for safety-critical
applications by adding support for contracts that enable formal specification and
enable detailed control over run-time checks.&lt;/p&gt;

&lt;p&gt;Many current programming language are getting more and more overloaded with new
concepts and syntax to solve particular development or performance issues.
Languages like Java/C# provide classes, interfaces, methods, packages, anonymous
inner classes, local variables, fields, closures, etc.  And these languages are
currently further extended by the introductions of records/structs, value types,
etc.  The possibility of nesting these different concepts results in
complexity for the developer and the tools (compilers, VMs) that process and
execute the code.&lt;/p&gt;

&lt;p&gt;For example, the possibility to access a local variable as part of the closure
of a lambda expression may result in the compiler allocating heap space to hold
the contents of that local variable.  Hence, the developer has lost control over
the allocation decisions made by the compiler.&lt;/p&gt;

&lt;p&gt;In Fuzion, the concepts of classes, interfaces, methods, packages, fields and
local variables are unified in the concept of a Fuzion feature. The decision
where to allocate the memory associated with a feature (on the heap, the stack
or in a register) is left to the compiler just as well as the decision if
dynamic type information is needed.  The developer is left with the single
concept of a feature, the language implementation takes care of all the rest.&lt;/p&gt;

&lt;h1&gt;Fuzion Feature Declarations&lt;/h1&gt;

&lt;p&gt;A Fuzion feature has a name, similar to the name of a class or a function.
The main operation that can be performed on a feature is a feature call.  The
constituents of a feature declaration are as follows:&lt;/p&gt;

&lt;h2&gt;Formal Arguments&lt;/h2&gt;

&lt;p&gt;Features may have a list of formal arguments, which are themselves features
implemented as fields.  On a call to a feature with formal arguments, actual
arguments have to be provided to the call, unless the list of formal arguments
is empty.&lt;/p&gt;

&lt;h2&gt;Feature Result&lt;/h2&gt;

&lt;p&gt;The result of a feature call is an instance of the feature.  Alternatively, a
feature may declare a different result type, then it must return a value of that
type on a call.&lt;/p&gt;

&lt;h2&gt;Closures&lt;/h2&gt;

&lt;p&gt;Features are nested, i.e., every feature is declared within the context of an
outer feature.  The only exception is the universe, which is the outermost
feature in Fuzion.  A feature can access features declared in its
outer feature or, recursively, any outer feature of these outer features.  This
means, a feature declaration also defines a closure of the feature and its
context.&lt;/p&gt;

&lt;p&gt;When calling a feature &lt;em&gt;f1&lt;/em&gt; declared as an inner feature of &lt;em&gt;f2&lt;/em&gt;, the call must
include a target value which is the result of a call to &lt;em&gt;f2&lt;/em&gt;, e.g., &lt;em&gt;f2.f1&lt;/em&gt;.&lt;/p&gt;

&lt;h2&gt;Generics&lt;/h2&gt;

&lt;p&gt;Features may have generic type parameters. E.g. a feature declaration may leave
the actual type used within that feature open and to be defined by the user of
the feature.&lt;/p&gt;

&lt;p&gt;The list of generic type parameters may be open, i.e., the number of actual
generic type parameters is not fixed at feature declaration.  This turns out to
be useful in the declaration of choice types and functions as explained below.&lt;/p&gt;

&lt;h2&gt;Inheritance&lt;/h2&gt;

&lt;p&gt;Fuzion features can inherit from one or several other features.  When inheriting
from an existing features, all inner features of the parent automatically become
inner features of the heir feature.  It is possible to redefine inherited
features.  In particular, when inheriting from a feature with abstract inner
features, one can implement the inherited abstract features.&lt;/p&gt;

&lt;p&gt;A redefinition of an inherited feature may implement an inherited feature as a
routine or as a field.  An inherited feature that is implemented as a field,
however, cannot be redefined as something else since fields might be mutable.&lt;/p&gt;

&lt;p&gt;Inheritance may result in conflicts. An example would be two features with the
same name that are inherited from two different parents.  In this case, the heir
must resolve the conflict either by redefining the inherited features and
providing a new implementation or by renaming the inherited features resulting
in two inner features in the heir feature.&lt;/p&gt;

&lt;p&gt;Inheritance and redefinition in Fuzion does not require dynamic binding.  By
default, the types defined by features are value types and no run-time overhead
for dynamic binding is imposed by inheritance.&lt;/p&gt;

&lt;h2&gt;A Contract&lt;/h2&gt;

&lt;p&gt;A feature may declare a contract that specifies what the features does and under
which conditions the feature may be called.&lt;/p&gt;

&lt;h2&gt;An implementation&lt;/h2&gt;

&lt;p&gt;Features must have one of the following implementations&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;a routine is a feature implementation with code that is executed on a call&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;a field is a memory slot that stores a value and whose contents are returned on a call&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;an abstract feature has no implementation and cannot be called directly, but can be implemented by heir features&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;an intrinsic feature is a low-level feature implemented by the compiler or
run-time system, e.g., the infix + operator to add two 32-bit integer values
may be an intrinsic operation.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;A feature implemented as a routine can contain inner feature declarations.&lt;/p&gt;

&lt;h1&gt;Feature examples&lt;/h1&gt;

&lt;p&gt;Here is an example that declares a feature &lt;em&gt;point&lt;/em&gt; that functions similar to a
struct or record in other languages:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;point(x, y i32) is # empty
p1 := point 3 4
say "p1.x is {p1.x}"    # will print "p1.x is 3"
say "p1.y is {p1.y}"    # will print "p1.y is 4"
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The next example shows a feature &lt;em&gt;base&lt;/em&gt; that provides an inner feature &lt;em&gt;plus&lt;/em&gt;
that adds its argument to the value passed to the enclosing base:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;base(v i32) is
  plus(w i32) =&amp;gt; v + w

b1 := base 30
b2 := base 100
say (b1.plus 23)    # will print "53"
say (b2.plus 23)    # will print "123"
&lt;/code&gt;&lt;/pre&gt;

&lt;h1&gt;Fuzion FZJava Tool&lt;/h1&gt;

&lt;p&gt;Fuzion provides a tool &lt;code&gt;fzjava&lt;/code&gt; that takes a Java module file and converts it
into Fuzion features.  In the spirit of Fuzion, Java's packages, classes,
interfaces, methods, constructors, static methods and fields are all converted
into Fuzion features.  Java methods that may throw an exception are
converted into features resulting in a choice type that is either the exception
type or the result type of that method.&lt;/p&gt;

&lt;p&gt;A few intrinsic functions in the Java interpreter back-end use Java's reflection
API to access the corresponding Java code.&lt;/p&gt;

&lt;h2&gt;Basic approach&lt;/h2&gt;

&lt;p&gt;The FZJava tool converts each Java class into three Fuzion Features.  Say you
have a Java class as follows&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;package x.y;
class MyClass
{
  MyClass(String arg)
  {
   ...
  }
  void myMethod()
  {
  }
  void myStaticMethod()
  {
  }
}
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This will be converted into a Fuzion feature &lt;code&gt;x.y.MyClass&lt;/code&gt; that may not be
instantiated directly:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;Java.x.y.MyClass(redef forbidden void) ref : Java.java.lang.Object(forbidden), fuzion.java.JavaObject(forbidden) is

  unit myMethod is
    ...
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This feature defines a Fuzion type &lt;code&gt;x.y.MyClass&lt;/code&gt; and contains wrappers for the
instance methods.  It is, however, not permitted to directly create instances of
this feature, which is ensured the forbidden parameter of type void (which
makes this feature 'absurd', it cannot be called directly since void values
cannot be created).&lt;/p&gt;

&lt;p&gt;Additionally, a Fuzion feature containing features for static methods and
constructors is generated as follows:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;Java.x.y.MyClass_static is

  new(arg string) is
    ...

  myStaticMethod is
    ...
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This Feature defines a unit type.  Finally, a Fuzion feature returning an
instance of this unit type is generated for convenience&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;Java.x.y.MyClass =&amp;gt; x.y.MayClass_static
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;With this, the following code can be used to create an instance of &lt;code&gt;MyClass&lt;/code&gt;
within Fuzion and call &lt;code&gt;myMethod&lt;/code&gt; and &lt;code&gt;myStaticMethod&lt;/code&gt; of this class:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;o := Java.x.y.MyClass.new "test"
o.myMethod
Java.x.y.MyClass.myStaticMethod
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The counterpart to &lt;code&gt;import&lt;/code&gt; a Java class in Fuzion would be to declare a field
and assign the class' unit type value to it, i.e., the code above could be
simplified as&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;MyClass := Java.x.y.MyClass
o := MyClass.new "test"
o.myMethod
MyClass.myStaticMethod
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;or even&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;mc := Java.x.y.MyClass
o := mc.new "test"
o.myMethod
mc.myStaticMethod
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;using &lt;code&gt;mc&lt;/code&gt; as an alias of &lt;code&gt;Java.x.y.MyClass&lt;/code&gt;.  Note that since the value of
field &lt;code&gt;mc&lt;/code&gt; is a unit type, this assignment or any accesses of &lt;code&gt;mc&lt;/code&gt; will not
execute any code at runtime.&lt;/p&gt;

&lt;h2&gt;Small Example&lt;/h2&gt;

&lt;p&gt;Here is a example how Java code can be used from Fuzion:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;javaString := java.lang.String.new "Hello Java 🌍!"                          # create Java string, type Java.java.lang.String
javaBytes  := javaString.getBytes "UTF8"                                     # get its UTF8 bytes, type is fuzion.java.Array&amp;lt;i8&amp;gt;
match javaBytes
  err error =&amp;gt; say "got an error: $err"
  bytes fuzion.java.Array =&amp;gt;
    say "string has {bytes.count} bytes: $bytes"
    javaString2 := java.lang.String.new bytes 6 bytes.count-6                # create Java string from bytes subset,
    say "Hello "+javaString2                                                 # append Java string to Fuzion string and print it
&lt;/code&gt;&lt;/pre&gt;

&lt;h2&gt;Web Server Example&lt;/h2&gt;

&lt;p&gt;The following code shows how Java APIs can be used to create a minimalistic web
server in Fuzion.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;webserver is

   # declare short hands to access Java net and io packages
   net := Java.java.net
   io  := Java.java.io

   # open socket
   port := 8080
   serversocket := net.ServerSocket.new port
   match serversocket
     err error =&amp;gt; say "#### $err ####"
     ss Java.java.net.ServerSocket =&amp;gt;

       for n in 1.. do
         say "accepting connections to localhost:$port"

         match accept
           unit      =&amp;gt; say "ok."
           err error =&amp;gt; say "#### $err ####"

         accept outcome&amp;lt;unit&amp;gt; is
           # accept and handle connection
           s := serversocket.accept?
           input  := io.BufferedReader.new (io.InputStreamReader.new s.getInputStream?)
           output := io.DataOutputStream.new s.getOutputStream?

           req := read?
           say "got request ({req.byteLength} bytes): $req"
           if req.startsWith "GET "
             (send200 "&amp;lt;html&amp;gt;Hello Fuzion $n!&amp;lt;/html&amp;gt;")?

           # close streams
           input.close?
           output.close

           # helper to read request
           #
           read outcome&amp;lt;string&amp;gt; is
             for
               r := "", "$r$s\n"
               s := input.readLine?
               ready := input.ready?
             until s = "" || !ready
               r

           # helper to send data in HTTP response with status 200
           #
           send200(data string) outcome&amp;lt;unit&amp;gt; is
             output.writeBytes ( "HTTP/1.1 200 OK\n"
                               + "Connection: close\n"
                               + "Server: Fuzion demo WebServer v0.01\n"
                               + "Content-Length: " + data.byteLength + "\n"
                               + "Content-Type: text/html\n"
                               + "\n"
                               + data)?
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Java methods that may result in an exceptions are represented by Fuzion features
that result in the type outcome&amp;lt;T&gt; where T is the Fuzion type corresponding to
the Java result type of the method.  outcome is a union type that may be either
error, which wraps the Java exception, or the actual result type T.&lt;/p&gt;

&lt;p&gt;Java methods that result in void are mapped to Fuzion features that result in
unit, or, outcome&amp;lt;unit&gt; in case the method has any declared exception.f&lt;/p&gt;

&lt;h1&gt;Fuzion Interpreter&lt;/h1&gt;

&lt;p&gt;Fuzion currently supports two back-ends: An interpreter implemented in Java and
running on top of OpenJDK and a C code generator implemented in Java using clang
to create machine code.&lt;/p&gt;

&lt;p&gt;The goal of the interpreter was to quickly obtain a way to execute Fuzion
applications.  Performance was not the main concern.  The interpreter operates
directly on Fuzion's abstract syntax tree.&lt;/p&gt;

&lt;p&gt;For better performance, a byte-code back-end is planned that will operate on
Fuzion's intermediate code instead.&lt;/p&gt;

&lt;h1&gt;Fuzion Byte-Code Back-End&lt;/h1&gt;

&lt;p&gt;Similar to Fuzion's C back-end, the byte-code back-end is planned to work on top of
Fuzion's intermediate code.&lt;/p&gt;

&lt;h2&gt;Fuzion intermediate code&lt;/h2&gt;

&lt;p&gt;Fuzion uses intermediate files during different stages of compilation: module
files that contain library code, application files for whole applications and
Fuzion intermediate representation files that serve as input to the back ends.&lt;/p&gt;

&lt;p&gt;Fuzion uses a simple intermediate code to represent pre-compiled modules and
whole applications. This intermediate code serves as the input for static
analysis tools, optimizers and for different back-ends that produce executable
applications.  The goal in the design of the intermediate file format was high
performance and simplicity for tools using this code.&lt;/p&gt;

&lt;p&gt;The intermediate code is a binary format containing features and types in a way
that may be mapped to memory and used directly, so overhead of parsing this
format into an in-memory representation is avoided.  In particular, if only parts
of a pre-compiled module are used by an application, there is no need to read and
unpack parts of the module intermediate representation that are not used.&lt;/p&gt;

&lt;p&gt;For features containing code, a very simple stack-based format is used. There
are currently only ten different instructions:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;* Unit -- produce a value of unit type
* Current -- produce the current instance as a value
* Constant -- produce a constant value
* Assign -- perform an assignment to a field
* Call -- perform a call to a given feature
* Tag -- convert a value into a tagged value of a choice type
* Match -- match a choice type
* Box -- convert a value type to a ref type
* Unbox -- extract the value from a ref type
* Pop -- drop the top element from the stack
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The intermediate code uses indices to refer to features and types within
intermediate files.  This means that lookup is very efficient, but it also means
that a change in a library module requires recompilation of all dependent
modules.  Any incompatibilities would be found at compile time instead of
resulting in something like Java's &lt;code&gt;IncompatibleClassChangeError&lt;/code&gt; at run-time.&lt;/p&gt;

&lt;h2&gt;Instance Implementation&lt;/h2&gt;

&lt;p&gt;Fuzion instances should be mapped directly to instances of Java classes
generated for the corresponding features.  Fuzion fields should be mapped to Java
fields and Fuzion routines to Java methods.&lt;/p&gt;

&lt;p&gt;Fuzion instances that are accessed only locally by their defining features code,
i.e., they do not live longer than their code is executed and they are not
passed to any other features, might be optimized and implemented as Java methods
using local variables instead of fields.&lt;/p&gt;

&lt;h2&gt;Call Implementation&lt;/h2&gt;

&lt;p&gt;Fuzion's support multiple inheritance similar to Eiffel. Java support multiple
inheritance only for interfaces, so one way to implement dynamic binding in
calls would be to define interfaces for every Fuzion feature and use the JVM's
invokeinterface byte-code for calls.&lt;/p&gt;

&lt;p&gt;A more flexible alternative might be to use invokedynamic to implement dynamic
dispatch, but this will likely result in higher overhead compared to highly
optimized invokeinterface implementations.&lt;/p&gt;

&lt;h1&gt;Conclusion and Next Steps&lt;/h1&gt;

&lt;p&gt;The Fuzion language definition and implementation are far from stable, but are
getting closer to become useful.  Big improvements come from the ability to
pre-compile modules and from the foreign language interface for Java, which
makes a giant code base accessible for Fuzion applications to build on.&lt;/p&gt;

&lt;p&gt;Additionally, new projects such as the language server implementation for Fuzion
by Michael Lill help by integrating Fuzion support in popular IDEs and editors.&lt;/p&gt;

&lt;p&gt;Main points that are missing right now are&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a powerful standard library&lt;/li&gt;
&lt;li&gt;additional library modules for all sorts of application needs&lt;/li&gt;
&lt;li&gt;low-level foreign language interface for C&lt;/li&gt;
&lt;li&gt;actual implementations of static analyzers and optimizers&lt;/li&gt;
&lt;li&gt;highly optimizing back-ends&lt;/li&gt;
&lt;li&gt;garbage collection for the C back-end&lt;/li&gt;
&lt;li&gt;documentation, tutorials&lt;/li&gt;
&lt;li&gt;enthusiastic contributors and users!&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Please feel free to contact me in case you want to use Fuzion or want to help
making it a success!&lt;/p&gt;</description>
        <persons>
          <person id="7627">Fridtjof Siebert</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/fuzion/attachments/slides/5170/export/events/attachments/fuzion/slides/5170/fosdem_2022_fuzion_a_new_language_for_the_openjdk.pdf">Fuzion: a New Language for the OpenJDK</attachment>
        </attachments>
        <links>
          <link href="https://flang.dev       ">Fuzion portal website</link>
          <link href="https://github.com/tokiwa-software/fuzion ">Fuzion sources on GitHub</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/fuzion.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/fuzion.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-fuzion:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-fuzion:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12924.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.geospatial">
    </room>
    <room name="D.go">
      <event id="13116">
        <start>13:00</start>
        <duration>00:20</duration>
        <room>D.go</room>
        <slug>go_welcome</slug>
        <title>Welcome to the Go Devroom</title>
        <subtitle/>
        <track>Go</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A warm welcome to The Go Devroom at FOSDEM 2022&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4618">Maartje Eyskens</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.go/go_welcome.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.go/go_welcome.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#go-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#go-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#go-go_welcome:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#go-go_welcome:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13116.php">Submit feedback</link>
        </links>
      </event>
      <event id="12448">
        <start>13:20</start>
        <duration>00:35</duration>
        <room>D.go</room>
        <slug>go_slices_maps_channels</slug>
        <title>Dissecting Slices, Maps and Channels in Go</title>
        <subtitle/>
        <track>Go</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Slices, Maps and Channels in go, are first class citizens of the language, they are used widely in our day to day work, but… do you know how they works under the hood? Do you know the implications of adding elements to an slice, or new keys to a map?&lt;/p&gt;

&lt;p&gt;Do you know why you can’t relay in maps order? Do you know how channels handle the buffer or the blocked goroutines? If you don’t know about that, this is your talk. I going to access the go runtime memory state of the maps, slices and channels, and show you how they evolve over time while we change them.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2500">Jesús Espino</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/go_slices_maps_channels/attachments/slides/5131/export/events/attachments/go_slices_maps_channels/slides/5131/Slides_of_Dissecting_Go">Dissecting Go Slices, Maps and Channels</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.go/go_slices_maps_channels.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.go/go_slices_maps_channels.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#go-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#go-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#go-go_slices_maps_channels:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#go-go_slices_maps_channels:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12448.php">Submit feedback</link>
        </links>
      </event>
      <event id="13071">
        <start>13:55</start>
        <duration>00:35</duration>
        <room>D.go</room>
        <slug>go_errors</slug>
        <title>Mastering Your Error Domain</title>
        <subtitle>Graceful error handling in Go</subtitle>
        <track>Go</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Error handling is one of Go’s key features. The errors.As helper added in Go 1.13 gives Gophers the tools they need to build their own error domains and ensure that all errors are handled properly across their applications.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The errors.As feature of Go 1.13 makes it easy to create error systems that work for your particular applications, users, and operators without being straitjacketed by the language into a one-size-fits-all approach that inadvertently exposes users to the internal operations of your system. Don’t let your end users be distracted by irrelevant warning messages. Handle errors properly by thinking about their roles and domain within your application.&lt;/p&gt;</description>
        <persons>
          <person id="8841">Carl Johnson</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://blog.carlmjohnson.net/post/2020/working-with-errors-as/">Creating Domain Specific Error Helpers in Go With errors.As</link>
          <link href="https://docs.google.com/presentation/d/1Y5sjthZt00QZqegCtrYBMgnxQ0H-xyk9ogipI19ZNxA/edit?usp=sharing">Google Slides</link>
          <link href="https://video.fosdem.org/2022/D.go/go_errors.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.go/go_errors.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#go-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#go-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#go-go_errors:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#go-go_errors:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13071.php">Submit feedback</link>
        </links>
      </event>
      <event id="12997">
        <start>14:30</start>
        <duration>00:35</duration>
        <room>D.go</room>
        <slug>go_tinygo_wifi</slug>
        <title>Go Further Without Wires</title>
        <subtitle>WiFi Programming Using TinyGo</subtitle>
        <track>Go</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Last year in "Go Without Wires" we saw how you can use TinyGo to program code that runs directly on Bluetooth devices.&lt;/p&gt;

&lt;p&gt;Now in "Go Further Without Wires" we will see some of the ways that TinyGo can connect to WiFi networks, and consequently to the Internet itself.&lt;/p&gt;

&lt;p&gt;This talk will include several actual demonstrations, including a drone.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this second chapter of the "Wireless Saga", we will get to see how our TinyGo programs can extend out further into the real world, by connecting to Wireless Local Area Networks (WLAN) using several different wireless chips such as the popular ESP-32.&lt;/p&gt;</description>
        <persons>
          <person id="4480">Ron Evans</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://deadprogram.github.io/fosdem-2022">Slides</link>
          <link href="https://github.com/deadprogram/fosdem-2022">Repo</link>
          <link href="https://tinygo.org">TinyGo</link>
          <link href="https://video.fosdem.org/2022/D.go/go_tinygo_wifi.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.go/go_tinygo_wifi.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#go-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#go-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#go-go_tinygo_wifi:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#go-go_tinygo_wifi:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12997.php">Submit feedback</link>
        </links>
      </event>
      <event id="12823">
        <start>15:05</start>
        <duration>00:35</duration>
        <room>D.go</room>
        <slug>go_finite_automata</slug>
        <title>Fun with Finite Automata</title>
        <subtitle>Optimising the Go regexp package</subtitle>
        <track>Go</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Go regexp package is an extremely competent piece of engineering, with attractive features such as being guaranteed to run in time linear in the size of the input.
However, it can be made to go faster.&lt;/p&gt;

&lt;p&gt;This talk will describe:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;how Go regexp works&lt;/li&gt;
&lt;li&gt;five changes that improve regexp performance&lt;/li&gt;
&lt;li&gt;the basic profiling techniques used to identify these optimisations&lt;/li&gt;
&lt;li&gt;further opportunities for optimisation, including via Generics.&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="4278">Bryan Boreham</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/go_finite_automata/attachments/slides/5155/export/events/attachments/go_finite_automata/slides/5155/go_regexp.pdf">Fun with Finite Automata</attachment>
        </attachments>
        <links>
          <link href="https://github.com/grafana/regexp/tree/speedup#readme">Go rexexp code for you to to try out the optimisations.</link>
          <link href="https://video.fosdem.org/2022/D.go/go_finite_automata.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.go/go_finite_automata.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#go-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#go-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#go-go_finite_automata:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#go-go_finite_automata:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12823.php">Submit feedback</link>
        </links>
      </event>
      <event id="12585">
        <start>15:40</start>
        <duration>00:35</duration>
        <room>D.go</room>
        <slug>go_log4shell</slug>
        <title>Fuzzy generics</title>
        <subtitle>Several months of using 1.18 features</subtitle>
        <track>Go</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Several months ago, a new project was started: FerretDB, an open-source alternative to MongoDB. It is a proxy between MongoDB clients/driver and PostgreSQL, developed in Go. Since the very first commit, it used a version of Go which soon will be released as Go 1.18. The two biggest reasons for that were first-class support for type parameters (generics) and fuzzing. In my talk, I will cover both of them: how they work in theory and our practice, how they were useful for us (spoiler: very useful), and what are their downsides and gotchas.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4759">Alexey Palazhchenko</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.go/go_log4shell.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.go/go_log4shell.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#go-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#go-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#go-go_log4shell:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#go-go_log4shell:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12585.php">Submit feedback</link>
        </links>
      </event>
      <event id="12568">
        <start>16:15</start>
        <duration>00:35</duration>
        <room>D.go</room>
        <slug>go_json</slug>
        <title>JSON Serialization - The Fine Print</title>
        <subtitle>A journey of JSON serialization</subtitle>
        <track>Go</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We'll look into JSON serialztion, starting from the easy cases and moving toward more advanced ones.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;A quiz! Consider the following code:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;a := 1
data, _ := json.Marshal(a)
var b interface{}
json.Unmarshal(data, &amp;amp;b)
fmt.Println(a == b)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;What will be printed? And why it's "1 1 false"? :)&lt;/p&gt;

&lt;p&gt;We all work with JSON, and even though it's a simple format, there are several sharp edges you should should avoid.
In this talk, we'll journey from the common well lit areas of JSON serialization and end in some darker corners. I hope you'll enjoy the ride.&lt;/p&gt;</description>
        <persons>
          <person id="7647">Miki Tebeka</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/go_json/attachments/slides/5154/export/events/attachments/go_json/slides/5154/fosdem22.zip"/>
        </attachments>
        <links>
          <link href="https://github.com/tebeka/talks/tree/master/fosdem22">Slide &amp; code</link>
          <link href="https://video.fosdem.org/2022/D.go/go_json.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.go/go_json.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#go-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#go-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#go-go_json:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#go-go_json:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12568.php">Submit feedback</link>
        </links>
      </event>
      <event id="12857">
        <start>16:50</start>
        <duration>00:35</duration>
        <room>D.go</room>
        <slug>go_why_embedded</slug>
        <title>Why your next embedded project should be written in Go</title>
        <subtitle>Confessions of a recovering C developer</subtitle>
        <track>Go</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Go ecosystem has established itself as the language of choice for many cloud and server software. We present arguments that Go is also uniquely suited to thrive for Linux-based embedded development. We present our case in the context of the SysOTA and NetOTA projects&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7945">Zygmunt Krynicki</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/go_why_embedded/attachments/slides/5057/export/events/attachments/go_why_embedded/slides/5057/go.pdf"/>
        </attachments>
        <links>
          <link href="https://gitlab.com/zygoon/sysota">SysOTA repository</link>
          <link href="https://gitlab.com/zygoon/netota">NetOTA repository</link>
          <link href="https://video.fosdem.org/2022/D.go/go_why_embedded.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.go/go_why_embedded.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#go-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#go-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#go-go_why_embedded:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#go-go_why_embedded:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12857.php">Submit feedback</link>
        </links>
      </event>
      <event id="12326">
        <start>17:25</start>
        <duration>00:35</duration>
        <room>D.go</room>
        <slug>go_state_of_go</slug>
        <title>The State of Go</title>
        <subtitle>What's new in Go 1.17 and 1.18</subtitle>
        <track>Go</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Go 1.18 is planned to be released in February 2022 and this talk covers what's coming up with it.&lt;/p&gt;

&lt;p&gt;We'll talk about new features and fixes in Go, new proposals for Go 2. All of the new things you might have missed.&lt;/p&gt;

&lt;p&gt;This has been a staple talk of the Go devroom, opening the stage every year, and has always been a successful one.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4618">Maartje Eyskens</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.go/go_state_of_go.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.go/go_state_of_go.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#go-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#go-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#go-go_state_of_go:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#go-go_state_of_go:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12326.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.graphics">
    </room>
    <room name="D.trusted-hardware">
      <event id="13135">
        <start>10:00</start>
        <duration>00:05</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_welcome</slug>
        <title>Opening</title>
        <subtitle>Welcome, overview, lineup</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A brief introduction to the room and to the sessions.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This year's TEE devroom will again be a full-day virtual event with an impressive lineup! The day will be roughly divided into session blocks grouping related talks as follows:&lt;/p&gt;

&lt;h2&gt;10h00-12h25: TEE attacks, defenses, and enclave shielding runtimes&lt;/h2&gt;

&lt;p&gt;featuring an enclave exploit analysis, Guardian, Gramine, Enarx, and Veracruz&lt;/p&gt;

&lt;h2&gt;13h25-14h40: Emerging TEEs and best practices&lt;/h2&gt;

&lt;p&gt;featuring logging in confidential computing, secure boot, and ARM CCA&lt;/p&gt;

&lt;h2&gt;14h55-16h10: OS and and page-based isolation&lt;/h2&gt;

&lt;p&gt;featuring FlexOS, Intravisor, and EDP for AWS Nitro&lt;/p&gt;

&lt;h2&gt;16h30-17h30: Wrap up and discussion on process-based abstractions for VM-based environments&lt;/h2&gt;

&lt;p&gt;we wrap up the day with a live presentation and a following discussion&lt;/p&gt;</description>
        <persons>
          <person id="1138">Vasily A. Sartakov</person>
          <person id="6115">Jo Van Bulck</person>
          <person id="8281">Fritz Alder</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_welcome.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_welcome.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_welcome:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_welcome:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13135.php">Submit feedback</link>
        </links>
      </event>
      <event id="12484">
        <start>10:05</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_sgx_analysis</slug>
        <title>SGX Enclave Exploit Analysis and Considerations for Defensive SGX Programming</title>
        <subtitle/>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Intel SGX provided a mechanism to better isolate user-level software from attackers. However, attackers will still use various methods to attack SGX and user’s Enclaves. And user’s code inside Enclave may also have bugs, which can be leveraged by the attackers. We are from intel SGX SDK team, we have conducted security analysis and pen-test for SGX Enclave (based on SGX SDK) during the past 10+ years. We want to summarize some past exploits we encountered in our daily work and what's the mitigation, hope it can help the Enclave developers to write more secure Enclave code.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Target topics category:
TEE-specific attacks and defenses (vulnerabilities, exploits, defensive programming)&lt;/p&gt;

&lt;p&gt;Purpose:
Explain the Security Properties of Intel® SGX Technology.
Help Enclave Developers write more secure code within an enclave.
Analyze a sampling of enclave defense-in-depth strategies and protections against known attacks.&lt;/p&gt;

&lt;p&gt;SGX Enclave Security and Challenge:
Code running within the enclave must be written securely.
Poorly written code may be subject to attack by various methods.
Developers must also be aware of potential side-channel attacks on code.&lt;/p&gt;</description>
        <persons>
          <person id="8547">Shunda Zhang</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/tee_sgx_analysis/attachments/slides/5013/export/events/attachments/tee_sgx_analysis/slides/5013/SGX_Enclave_Analysis_pdf">Considerations for defensive SGX programming PDF</attachment>
        </attachments>
        <links>
          <link href="https://github.com/intel/linux-sgx">Intel SGX SDK</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_sgx_analysis.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_sgx_analysis.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_sgx_analysis:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_sgx_analysis:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12484.php">Submit feedback</link>
        </links>
      </event>
      <event id="12623">
        <start>10:30</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_gramine</slug>
        <title>Gramine Library OS</title>
        <subtitle>Overview, current state and future plans</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Gramine (formerly called "Graphene") is a lightweight library OS, designed to run a single Linux application in an isolated environment. Currently, Gramine runs on Linux and Intel SGX enclaves on Linux platforms. With Intel SGX support, Gramine can secure a critical application in a hardware-encrypted memory region and protect the application from a malicious system stack with minimal porting effort ("lift and shift" approach).&lt;/p&gt;

&lt;p&gt;Several major events happened to the Gramine project in 2021. Gramine changed its name, moved to a new GitHub repository, and joined Confidential Computing Consortium. The first production-ready release of Gramine -- v1.0 -- was published in October 2021. This talk will discuss all these events, as well as the current status of the project and its future plans.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7873">Dmitrii Kuvaiskii</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/gramineproject">Gramine GitHub organization</link>
          <link href="http://www.gramineproject.io/">Gramine official web-site</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_gramine.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_gramine.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_gramine:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_gramine:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12623.php">Submit feedback</link>
        </links>
      </event>
      <event id="12714">
        <start>10:55</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_enarx</slug>
        <title>WebAssembly + Confidential Computing</title>
        <subtitle>Enarx first release brings WebAssembly to Confidential Computing</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Enarx project reached a huge milestone: its first official release, featuring WebAssembly runtime. WebAssembly and Confidential Computing are a great match because WebAssembly offers developers a wide range of language choices, it works across silicon architectures, and it provides a sandboxed environment. This presentation will highlight the benefits of WebAssembly to Confidential Computing and showcase some demos.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;After 3 years since its inception, the Enarx project finally had its first official release, bringing WebAssembly to Confidential Computing.&lt;/p&gt;

&lt;p&gt;Enarx is a deployment framework for running applications in TEE instances – which we refer to as “Keeps” – without the need to trust lots of dependencies, without the need to rewrite the application, and without the need to implement attestation separately.&lt;/p&gt;

&lt;p&gt;The WebAssembly runtime, based on wasmtime, offers developers a wide range of language choices for implementation, including Rust, C, and C++. It is designed to work across silicon architectures transparently to the user so that the application can run equally simple on Intel platforms (SGX or the recently-announced TDX), AMD platforms (SEV) or forthcoming platforms such as Arms’ Realms and IBM’s PEF - all without having to recompile the application code. WebAssembly's sandbox model offers an extra layer of protection, isolating the application from the host.&lt;/p&gt;</description>
        <persons>
          <person id="995">Nick Vidal</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://enarx.dev/">Website</link>
          <link href="https://github.com/enarx/enarx">GitHub</link>
          <link href="https://chat.enarx.dev/">Chat</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_enarx.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_enarx.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_enarx:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_enarx:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12714.php">Submit feedback</link>
        </links>
      </event>
      <event id="13138">
        <start>11:20</start>
        <duration>00:15</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_break1</slug>
        <title>Short break</title>
        <subtitle>15 minutes</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Short break.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8281">Fritz Alder</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_break1:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_break1:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13138.php">Submit feedback</link>
        </links>
      </event>
      <event id="12505">
        <start>11:35</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_veracruz</slug>
        <title>Privacy-preserving video object detection in WebAssembly inside Veracruz</title>
        <subtitle/>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Veracruz is a framework for designing and deploying privacy-preserving computations amongst a group of mutually mistrusting individuals. Veracruz uses strong isolation technologies, such as AWS Nitro Enclaves, Arm CCA Realms, and the high-assurance seL4 hypervisor, to provide a safe, neutral ground, within which a sandboxed WebAssembly program executes.
Recent enhancements to Veracruz have made it possible to support larger, more complex privacy-preserving computations: we have adopted the WebAssembly System Interface (WASI) as our programming model, which can be used by executing WebAssembly programs to query and modify an efficient in-memory filesystem, for example.
In this talk, I will first introduce Veracruz before finally focusing on a real-world use-case for Veracruz, in privacy-preserving video object detection, developed as part of a collaboration between the Veracruz team and IOTEX, a manufacturer of IoT cameras.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8554">Guilhem Bryant</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_veracruz.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_veracruz.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_veracruz:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_veracruz:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12505.php">Submit feedback</link>
        </links>
      </event>
      <event id="12688">
        <start>12:00</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_guardian</slug>
        <title>Symbolic Validation of SGX enclaves using Guardian </title>
        <subtitle>Avoid known enclave vulnerabilities by automatically checking for orderliness​</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The confidentiality and integrity guarantees offered by Intel SGX enclaves can be easily thwarted if the enclave has not been properly designed. Its interface with the untrusted software stack is a perhaps the largest attack surface that adversaries can exploit; unintended interactions with untrusted code can expose the enclave to memory corruption attacks, for instance.&lt;/p&gt;

&lt;p&gt;We have proposed a notion, called orderliness, that embodies good practice set out by academic papers and the principles of the Intel SGX SDK’s programming model.  It is concerned especially with these interactions between the trusted and untrusted worlds. This notion underpins Guardian: an open-source tool that we have created to help enclave developers check their enclaves are orderly before they are deployed. It automatically validates enclaves and reports violations to our notion of orderliness. These violations help find  parts of their code that may need changing – they should usually point to an attack primitive.&lt;/p&gt;

&lt;p&gt;We have found some security issues in enclaves that had been extensively vetted by other researchers – one of which was crafted by Intel engineers.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Modern processors can offer hardware primitives that allow a process to run in isolation. These primitives implement a trusted execution environment (TEE) in which a program can run in such a way that the integrity and confidentiality of its execution are guaranteed. Intel's Software Guard eXtensions (SGX) is an example of such primitives and its isolated processes are called enclaves. These guarantees, however, can be easily undermined if the enclave has not been properly designed.&lt;/p&gt;

&lt;p&gt;We propose a notion of an orderly enclave that splits the enclave’s behaviour into the following execution phases: entry, secure, ocall, and exit. Each of them imposes a set of restrictions that enforce a particular policy of access to untrusted memory and, in some cases, sanitisation conditions. A violation of these policies and conditions might indicate an undesired interaction with untrusted data/code or a lack of sanitisation, both of which can be harnessed to perpetrate attacks against the enclave. We also introduce Guardian: an open-source tool that uses symbolic execution to carry out the validation of an enclave against our notion of an orderly enclave; in this process, it also looks for some other typical attack primitives. We discuss how our approach can prevent and flag enclave vulnerabilities that have been identified in the literature. Moreover, we have evaluated how our approach fares in the analysis of some enclave samples. In this process, Guardian identified some previously undetected security issues in some of these samples.  These were subsequently acknowledged and fixed by the corresponding maintainers.&lt;/p&gt;</description>
        <persons>
          <person id="8647">Pedro Antonino</person>
          <person id="8933">Wojciech Aleksander Woloszyn</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_guardian.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_guardian.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_guardian:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_guardian:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12688.php">Submit feedback</link>
        </links>
      </event>
      <event id="13137">
        <start>12:25</start>
        <duration>01:00</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_lunch</slug>
        <title>Lunch break</title>
        <subtitle>1 hour</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Lunch break&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8281">Fritz Alder</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_lunch:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_lunch:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13137.php">Submit feedback</link>
        </links>
      </event>
      <event id="12720">
        <start>13:25</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_logging</slug>
        <title>Logging, debugging and error management in Confidential Computing</title>
        <subtitle>Challenges around maintaining confidentiality and integrity when logging</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Debugging applications is an important part of the development process. However, error messages and general logging can leak sensitive data, and in some cases even compromise your whole stack, as developers worldwide have recently learned from the log4j vulnerability.&lt;/p&gt;

&lt;p&gt;With Conﬁdential Computing, the world gets much more complicated, as every piece of information that a malicious entity on the host (including the host itself!) can gather may be leaking vital information about your workload. This talk details some of the problems that arise, and discusses some options to address them whilst considering real life workloads and application lifecycles.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Log entries and other error messages can be very useful, but they can also provide information to other parties - sometimes information which you’d prefer they didn’t have.  This is particularly true when you are thinking about Confidential Computing: running applications or workloads in environments where you really want to protect the confidentiality and integrity of your application and its data.&lt;/p&gt;

&lt;p&gt;This talk examines some of the issues that we need to consider when designing Confidential Computing frameworks, the applications we run in them, and their operations. Designers and architects of the TEE infrastructure and even, to a lesser extent, of potential workloads themselves, need to consider very carefully the impact of host gaining access to messages associated with the workload and the infrastructure components.  It is, realistically, infeasible to restrict all communication to levels appropriate for deployment, so it is recommended that various profiles are created which can be applied to different stages of a deployment, and whose use is carefully monitored, logged (!) and controlled by process.&lt;/p&gt;</description>
        <persons>
          <person id="3940">Mike Bursell</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://blog.enarx.dev/confidential-computing-logging-and-debugging/">Confidential Computing: logging and debugging</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_logging.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_logging.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_logging:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_logging:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12720.php">Submit feedback</link>
        </links>
      </event>
      <event id="12563">
        <start>13:50</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_oniro</slug>
        <title>Secure boot, TEEs, different OSes and more</title>
        <subtitle>Making sense of the trusted computing landscape in Eclipse Oniro embedded distribution</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk Marta is going to present a map of the trusted computing
landscape, explaining different types hardware support. She is going
to put it in a context of implementing secure boot and trusted execution
in an embedded distribution, namely Yocto-based Eclipse Oniro project.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The trusted computing landscape could be hard to understand for newcomers.
Just at the beginning, they encounter a number of abbreviations like TEE,
OPTEE, SEV, TF-A, TF-M and many more.&lt;/p&gt;

&lt;p&gt;In this talk Marta is going to present a map of those technologies, illustrate
how they are (or are expected to) be used, which market needs they address.
She will show how they could be implemented in practice in an embedded
distribution. The example will be the secure boot work in the Eclipse Oniro
project, an embedded multi-OS distribution for Internet of Things (IOT)
devices. The multi-OS specificity of Oniro will be used how the trusted
computing technologies compare on different types of processors running
Linux and Zephyr, with different security hardware support.&lt;/p&gt;</description>
        <persons>
          <person id="936">Marta Rybczynska</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/tee_oniro/attachments/slides/4842/export/events/attachments/tee_oniro/slides/4842/FOSDEM2022_Secure_Boot_Slides.pdf">Slides for the talk</attachment>
        </attachments>
        <links>
          <link href="https://www.youtube.com/watch?v=u6Xo0QF6AMQ">A previous presentation covering the more general topic of security in the distribution at Embedded Linux Conference 2021</link>
          <link href="https://booting.oniroproject.org/">Oniro project and its security tooling</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_oniro.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_oniro.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_oniro:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_oniro:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12563.php">Submit feedback</link>
        </links>
      </event>
      <event id="12561">
        <start>14:15</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_arm_cca</slug>
        <title>Arm CCA enablement through the Trusted Firmware community project</title>
        <subtitle/>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Arm Confidential Compute Architecture (CCA) is an extension of the Armv9 architecture designed to provide confidential computing in standardised and scalable way. CCA builds on existing principles built for TrustZone and virtualization to create a scalable and secure solution. CCA places requirements on hardware and firmware, which together provide the trusted computing base for a new class of secure execution environment that we call a Realm. Trusted Firmware is the key community project that provides a reference implementation of open source Secure firmware for Arm-based processors. This talk briefly introduce Arm CCA and illustrate how Arm plans to develop and enable it in the open by leveraging the community effort that drives Trusted Firmware as open-source project.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8632">Charles Garcia-Tobin</person>
          <person id="8919">Matteo Carlini</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.trustedfirmware.org/">TrustedFirmware.org</link>
          <link href="https://developer.arm.com/architectures/architecture-security-features/confidential-computing?_ga=2.131023695.1588019393.1639645055-206256897.1636988566">Arm CCA specifications</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_arm_cca.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_arm_cca.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_arm_cca:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_arm_cca:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12561.php">Submit feedback</link>
        </links>
      </event>
      <event id="13136">
        <start>14:40</start>
        <duration>00:15</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_break2</slug>
        <title>Short break</title>
        <subtitle>15 minutes</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Short break.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8281">Fritz Alder</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_break2:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_break2:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13136.php">Submit feedback</link>
        </links>
      </event>
      <event id="12721">
        <start>14:55</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_flexos</slug>
        <title>Rethinking the OS for Isolation Flexibility with FlexOS</title>
        <subtitle/>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Operating Systems (OSes) have historically been classified according to their isolation properties: monolithic OSes, microkernels, single-address-space OSes, or unikernels... Decades of experience in research and industry showed that there is no silver bullet and that different use-cases might demand different approaches to optimize safety and performance.&lt;/p&gt;

&lt;p&gt;What if we tried to design an operating system able to be easily reconfigured into any of these points in the OS design space? What if the OS could be a microkernel, a unikernel, or a monolithic OS, at will, and using a wide range of hardware- and software-backed isolation mechanisms?&lt;/p&gt;

&lt;p&gt;In this talk, we will present FlexOS, the result of our recent research work in trying to answer this question. FlexOS is an OS allowing users to easily specialize the safety and isolation strategy of an OS at compilation/deployment time, instead of design time. Depending on the configuration, the same FlexOS code can mimic a microkernel with multiple address-spaces, a single-address-space OS with Intel MPK compartments, or many other OS isolation approaches. We have implemented a prototype of FlexOS on top of Unikraft, a popular library OS framework.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8699">Hugo Lefeuvre</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/project-flexos">GitHub Organization of FlexOS</link>
          <link href="https://arxiv.org/abs/2112.06566">Preprint of the FlexOS ASPLOS paper</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_flexos.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_flexos.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_flexos:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_flexos:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12721.php">Submit feedback</link>
        </links>
      </event>
      <event id="12767">
        <start>15:20</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_intravisor</slug>
        <title>Intravisor -- a hypervisor for fine-grained isolation using CHERI</title>
        <subtitle/>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Hardware and container virtualisations are the fundamental technologies of modern cloud stacks. While these technologies virtualise different layers of software and hardware, they have one common thing: they are quite inefficient in terms of communication between isolated entities. The isolation relies on MMU and involves a privileged intermediary, which leads to heavy transitions or sharing data at the page granularity. The escape from this trap we see in the hardware capabilities introduced in CHERI. The CHERI architecture efficiently combines hardware memory capabilities with conventional MMU architectures. It gives not only safety to memory pointers, but also provides lightweight isolation mechanisms.&lt;/p&gt;

&lt;p&gt;In this talk, I will present Introvisor, a lightweight hypervisor for microservices. It uses CHERI capabilities for isolation and data sharing, does not require software porting thus compatible with existing software, and provides strong security guarantees.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1138">Vasily A. Sartakov</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_intravisor.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_intravisor.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_intravisor:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_intravisor:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12767.php">Submit feedback</link>
        </links>
      </event>
      <event id="12793">
        <start>15:45</start>
        <duration>00:25</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_edp_nitro</slug>
        <title>Developing for the AWS Nitro Enclave Platform</title>
        <subtitle>A new Enclave Development Platform (EDP) Target</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Intel, AMD, ARM, all have launched their own TEE. Amazon can be added to that list with AWS Nitro, but unlike the others it is not a hardware manufacturer. Instead, it chooses to provides its own abstractions over the platform used. This leads to some interesting characteristics.
The Enclave Development Platform (EDP) is a TEE platform SDK developed by Fortanix. EDP already targeted the Intel SGX platform. Recently we also support the AWS Nitro platform. In this talk we discuss the AWS Nitro platform in detail and interesting design decisions we made for the EDP platform.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In the AWS Nitro architecture, the hypervisor plays a key role. Hardware resources (processor cores and memory) are split off of a parent VM and can be repurposed to run the Nitro enclave. This enclave can be viewed as a separate VM with only processor cores and memory. A hard disk drive is not present, nor can it directly access an Ethernet network. All communication needs to take place over VSOCK to the parent VM. An attestation report can be provided by the hypervisor to ensure that the enclave has been build correctly.
The Enclave Development Platform (EDP) provides a way to easily build Rust applications on top of TEEs. It should be as easy for developers to target TEEs any other modern operating system. Next to Intel SGX, the Nitro platform has been added recently. To target the Nitro platform, EDP reimplements parts of the Rust standard library. It takes care of starting a runner process in the parent VM, forwarding network packets to/from the enclave and providing attestation evidence.&lt;/p&gt;</description>
        <persons>
          <person id="8727">Raoul Strackx</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_edp_nitro.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_edp_nitro.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_edp_nitro:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_edp_nitro:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12793.php">Submit feedback</link>
        </links>
      </event>
      <event id="13139">
        <start>16:10</start>
        <duration>00:20</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_break3</slug>
        <title>Short break</title>
        <subtitle>20 minutes</subtitle>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Short break.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8281">Fritz Alder</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_break3:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_break3:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13139.php">Submit feedback</link>
        </links>
      </event>
      <event id="12369">
        <start>16:30</start>
        <duration>01:00</duration>
        <room>D.trusted-hardware</room>
        <slug>tee_discussion</slug>
        <title>Process-based abstractions for VM-based environments</title>
        <subtitle/>
        <track>Hardware-Aided Trusted Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Inaugural secure enclave platforms operate at the single user process level (e.g. SGX), meaning a single address space with potentially multiple threads, with a standard OS outside the enclave responsible for resource management and scheduling. More recent platforms (AMD SEV, Intel TDX, AWS Nitro Enclaves) operate at the VM level. This provides significant new capabilities for multi-process abstractions such as mmap and fork, which will be beneficial for enclavizing legacy software.&lt;/p&gt;

&lt;p&gt;However, taking a VM image and running it in an enclave is not great from a TCB minimization standpoint. For platforms where there's currently no alternative (AMD, AWS), how can we build--with a minimal TCB--an abstraction that's similar to single-process enclaves? Of course you can “just run Linux” with a single process but this again is clearly suboptimal. We'll explore the solution space in this interactive session.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="936">Marta Rybczynska</person>
          <person id="1138">Vasily A. Sartakov</person>
          <person id="3940">Mike Bursell</person>
          <person id="6115">Jo Van Bulck</person>
          <person id="6574">Jethro G. Beekman</person>
          <person id="8699">Hugo Lefeuvre</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_discussion.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.trusted-hardware/tee_discussion.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#trusted-hardware-tee_discussion:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#trusted-hardware-tee_discussion:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12369.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.hpc">
      <event id="12382">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>opensearch_dashboards</slug>
        <title>Low-code data visualization and aggregation with OpenSearch Dashboards</title>
        <subtitle/>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Working with Big Data means that we need tools to organise and understand the data. And you don’t have to be a developer to search, aggregate and visualise your data. Whether you need an affordable business analytics tool or you want to analyse log data in near real time, OpenSearch can help you. And all of it through a visual interface of OpenSearch Dashboards.&lt;/p&gt;

&lt;p&gt;After listening to this talk you’ll understand the basics of working with an OpenSearch cluster and different use cases it supports. You’ll also learn to create your first search and aggregation query and visualise the outcomes with the help of OpenSearch Dashboards.&lt;/p&gt;

&lt;p&gt;This talk is for those who have little or no previous experience of OpenSearch (and Elasticsearch) and who are looking for solutions for searching, monitoring or data analysis with no coding required.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this session the audience will get theoretical and a knowledge on what OpenSearch is, which use cases it supports and how the audience can start using it for their data already today. Roles outside of developers are welcome, the information will be presented in uncomplicated terms and we’ll use visualisation tools to create and run requests, so no coding is required.&lt;/p&gt;</description>
        <persons>
          <person id="8503">Olena Kutsenko</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.hpc/opensearch_dashboards.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/opensearch_dashboards.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-opensearch_dashboards:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-opensearch_dashboards:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12382.php">Submit feedback</link>
        </links>
      </event>
      <event id="12820">
        <start>10:30</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>arcon_rust_streaming</slug>
        <title>Uncovering Arcon: A state-first Rust streaming analytics runtime</title>
        <subtitle/>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk, I will present Arcon, a Rust-native streaming runtime that integrates seamlessly with the Apache Arrow ecosystem. The Arcon philosophy is streaming first, similarly to systems such as Apache Flink and Timely Dataflow. However, unlike all existing systems, Arcon features great flexibility when it comes to its application state. Arcon's TSS query language allows extracting and operating on state snapshots consistently based on application-time constraints and interfacing with other systems for batch and warehouse analytics.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8635">Max Meldrum</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/cda-group/arcon">Github Repository</link>
          <link href="https://video.fosdem.org/2022/D.hpc/arcon_rust_streaming.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/arcon_rust_streaming.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-arcon_rust_streaming:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-arcon_rust_streaming:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12820.php">Submit feedback</link>
        </links>
      </event>
      <event id="12395">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>batch_proc_data_streaming</slug>
        <title>Build an Open Source Streaming Data Pipeline</title>
        <subtitle/>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Any conversation about Big Data would be incomplete without talking about Apache Kafka and Apache Flink: the winning open source combination for high-volume streaming data pipelines.&lt;/p&gt;

&lt;p&gt;In this talk we'll explore how moving from long running batches to streaming data changes the game completely. We'll show how to build a streaming data pipeline, starting with Apache Kafka for storing and transmitting high throughput and low latency messages. Then we'll add Apache Flink, a distributed stateful compute engine, to create complex streaming transformations using familiar SQL statements.&lt;/p&gt;

&lt;p&gt;This session is aimed at data professionals, who are ready to embrace open source streaming and make their data fly.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8503">Olena Kutsenko</person>
          <person id="8515">Francesco Tisiot</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/batch_proc_data_streaming/attachments/slides/5030/export/events/attachments/batch_proc_data_streaming/slides/5030/Build_an_Open_Source_Data_Pipeline">Build an Open Source Data Pipeline</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.hpc/batch_proc_data_streaming.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/batch_proc_data_streaming.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-batch_proc_data_streaming:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-batch_proc_data_streaming:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12395.php">Submit feedback</link>
        </links>
      </event>
      <event id="12494">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>openstack_hpc</slug>
        <title>Using OpenStack to reduce HPC service complexity</title>
        <subtitle>... no, that is not an oxymoron!</subtitle>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Why build #4 on the Green500 using OpenStack? It makes it easier to manage. Cambridge University started using OpenStack in 2015. Since mid 2020, all new hardware is controlled using OpenStack. Compute nodes, GPU nodes, Lustre nodes, Ceph nodes, almost everything. OpenStack allows large baremetal slurm clusters and dedicated TRE (trusted research environments) to share the same images. Is this a cloud native supercomputer?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;We will explore how OpenStack is used to manage a supercomputer as a shared pool of hardware resources, that can be partitioned between a multitude of different platforms required by a diverse group of scientists. Ranging from Trusted Research Environments (TREs), on demand dedicated AI platforms, dedicated big data platforms, and to traditional shared Slurm clusters.&lt;/p&gt;

&lt;p&gt;We will focus on providing a range of services from a single shared hardware pool, allowing for the delivery of both on demand interactive compute platforms for STFC's IRIS e-Infrastrcture and Slurm clusters such as the #4 in the Green500, called Wilkes-3:
https://www.top500.org/system/179930/&lt;/p&gt;

&lt;p&gt;This makes use of both OpenStack Ironic, for the baremetal deployment, and on-demand OpenStack KVM powered VMs running Cluster API provisioned Kubernetes, with KubeApps to deploy JuypterHub.&lt;/p&gt;</description>
        <persons>
          <person id="3249">John Garbutt</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/openstack_hpc/attachments/slides/5136/export/events/attachments/openstack_hpc/slides/5136/OpenStackHPCSlides.pdf">OpenStack to reduce HPC service complexity</attachment>
        </attachments>
        <links>
          <link href="https://docs.openstack.org/kayobe/latest/">OpenStack Kayobe and Kolla-ansible</link>
          <link href="https://github.com/stackhpc/ansible-slurm-appliance">OpenHPC Slurm Appliance</link>
          <link href="https://github.com/stackhpc/Azimuth">Azimuth Cloud Portal</link>
          <link href="https://video.fosdem.org/2022/D.hpc/openstack_hpc.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/openstack_hpc.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-openstack_hpc:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-openstack_hpc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12494.php">Submit feedback</link>
        </links>
      </event>
      <event id="12866">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>containers_hpc</slug>
        <title>Containers in HPC</title>
        <subtitle>State of Containers in HPC</subtitle>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This short talk will disect the container ecosystem for HPC in four segments and discusses what to look out for, what is already settled and how to navigate containers in 2022.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3568">Christian Kniep</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/containers_hpc/attachments/slides/5178/export/events/attachments/containers_hpc/slides/5178/Cihpc_2022_01_14v2.pdf">Container-in-HPC slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.hpc/containers_hpc.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/containers_hpc.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-containers_hpc:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-containers_hpc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12866.php">Submit feedback</link>
        </links>
      </event>
      <event id="12531">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>managing_cpus_k8s</slug>
        <title>This is The Way- A Crash Course on the Intricacies of Managing CPUs in K8s</title>
        <subtitle>From homogenous single-socket to heterogenous multi-socket clusters</subtitle>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Optimizing CPU management improves cluster performance and security, but is daunting to almost everyone.  CPU management may seem complex, but it can be explained in such a way that even your inner toddler will comprehend.  With this talk, we will give a path to success.&lt;/p&gt;

&lt;p&gt;You may have a multi-socket node cluster where your AI/ML workloads care about the proximity of your CPUs to GPUs.  You may be running scientific workloads where you want to pin in cores within containers instead of just a pod level.  You may have a single-socket server where you want to save a single core outside of Kubernetes for a daemon dedicated to mining bitcoin, without affecting your other jobs (please do not do this).  We will cover these and more, helping you understand the intricacies of CPU management within the kubelet and what Kuberenetes can and cannot currently do.  We will also cover how you can help escalate the visibility of use cases not currently covered within Kubernetes.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Many clusters do not have CPU management because it is difficult to do correctly without impacting performance. While there are static and dynamic pinning abilities, we will consolidate the use cases and remove the pain it takes for users to deploy Kubernetes. This talk will help the audience gain an insight into features that can be used for resource management and orchestration of containerized applications with focus on CPU management. Users that have performance sensitive workloads such as AI/ML, Telco, 5G and Networking workloads will benefit from this talk. This talk will also help CTOs, system architects, developers and engineers in their planning to develop, test, or optimize their deployments in a Kubernetes environment. We also hope to use this forum to find other community members with specific needs in our desire to make the kubelet more flexible with regard to CPU management.&lt;/p&gt;</description>
        <persons>
          <person id="8612">Swati Sehgal</person>
          <person id="8872">Marlow Weston</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/managing_cpus_k8s/attachments/slides/5176/export/events/attachments/managing_cpus_k8s/slides/5176/This_is_the_way_CPU_Mgmt_in_k8s">This is the way: A Crash Course on the Intricacies of Managing CPUs in K8s</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.hpc/managing_cpus_k8s.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/managing_cpus_k8s.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-managing_cpus_k8s:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-managing_cpus_k8s:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12531.php">Submit feedback</link>
        </links>
      </event>
      <event id="12826">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>spark_mahout_kubeflow_k8s</slug>
        <title> Making Apache Spark, Apache Mahout, Kubeflow, and Kubernetes Play Nice</title>
        <subtitle/>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Working with big data matrices is challenging, Kubernetes allows users to elastically scale, but can only have a pod as large as a node, which may not be large enough to fit the matrix in memory. While Kubernetes allows for other paradigms on top of it which allows pods to coordinate on individual jobs, setting them up and making them play nice with ML platforms is not straightforward. Using Apache Spark and Apache Mahout we can work with matrices of any dimension and distribute them across an unbounded number of pods/nodes, and we can use Kubeflow to make our work quickly and easily reproducible. In this talk, we’ll discuss how we used Apache Spark and Mahout to denoise DICOM images of lungs of COVID patients and published our Pipeline with Kubeflow to make the process easily repeatable which could help doctors in more resource limited hospitals, as well as other researchers seeking to automate the detection of COVID.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5239">Trevor Grant</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.hpc/spark_mahout_kubeflow_k8s.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/spark_mahout_kubeflow_k8s.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-spark_mahout_kubeflow_k8s:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-spark_mahout_kubeflow_k8s:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12826.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.infra">
      <event id="13536">
        <start>10:00</start>
        <duration>00:45</duration>
        <room>D.infra</room>
        <slug>cue_pratical_guide</slug>
        <title>A practical guide to CUE: patterns for everyday use</title>
        <subtitle/>
        <track>Infra Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;CUE (https://cuelang.org/) solves a previously unsolved technical problem in the configuration space. It does so by taking a compositional approach that reduces the complexity of managing configuration from a combinatorial problem to a linear problem. CUE is based on 20 years of experience in the field of configuration. Its declarative, aspect-oriented approach is powerful yet simple, making it possible to manage large amounts of configuration data and policies in multiple formats (JSON, YAML, Protocol Buffers, OpenAPI, etc.) with relative ease.
It also makes CUE well suited to a wide range of applications.&lt;/p&gt;

&lt;p&gt;This all sounds great! But for someone new to CUE, it may not be obvious how to get started.&lt;/p&gt;

&lt;p&gt;In this talk, Marcel van Lohuizen and Paul Jolly start with a quick overview of CUE the language, then move on to present practical examples of CUE in action, including common patterns for validation, policy, integration with existing non-CUE configuration and more. Because CUE is new, established patterns are still in the making, but at the very least it will be a reflection of the current thinking.&lt;/p&gt;

&lt;p&gt;No previous experience of CUE required, although familiarity with an existing configuration and data languages will help provide some context to the examples.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8966">Marcel van Lohuizen</person>
          <person id="8969">Paul Jolly</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/cue_pratical_guide/attachments/slides/5121/export/events/attachments/cue_pratical_guide/slides/5121/slides.pdf">A practical guide to CUE: patterns for everyday use</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.infra/cue_pratical_guide.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.infra/cue_pratical_guide.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#infra-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-cue_pratical_guide:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#infra-cue_pratical_guide:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13536.php">Submit feedback</link>
        </links>
      </event>
      <event id="13530">
        <start>11:00</start>
        <duration>00:45</duration>
        <room>D.infra</room>
        <slug>foreman_katello_leapp_elevate</slug>
        <title>Migrating Foreman/Katello from EL7 to EL8 using LEAPP/ELevate</title>
        <subtitle/>
        <track>Infra Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;With the Foreman Project dropping support for EL7 in Foreman 3.3 (~Summer 2022), it's finally time to tackle that migration to EL8 you have been putting off for a while now.
In this session we will present various ways how you can migrate your installation from EL7 to EL8, with the main focus on the in-place upgrade using LEAPP/ELevate.&lt;/p&gt;

&lt;p&gt;The Foreman Project is planning to &lt;a href="https://community.theforeman.org/t/deprecation-plans-for-foreman-on-el7-debian-10-and-ubuntu-18-04/25008"&gt;drop support for EL7-based deployments in Foreman 3.3&lt;/a&gt;, mostly due to the fact that EL7 is considered "feature complete" and there are no further updates (besides security fixes) planned for it.
Contrary to &lt;a href="https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html"&gt;Debian&lt;/a&gt; or &lt;a href="https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/"&gt;Fedora&lt;/a&gt;, EL-based distributions aren't designed to be upgraded in-place without special tooling. This tooling exists in form of the &lt;a href="https://leapp.readthedocs.io/en/latest/"&gt;LEAPP project&lt;/a&gt; for RHEL and the &lt;a href="https://almalinux.org/elevate"&gt;ELevate&lt;/a&gt; fork by AlmaLinux for AlmaLinux, CentOS, Rocky Linux, and Oracle Linux.
We have developed a plugin for LEAPP that helps with the Foreman-specific parts of the migration, which we would like to present to you. As usual, there were a few challenges during the development, which will hopefully entertain you and maybe even help if you need to write own LEAPP plugins.
And last but not least, we will also discuss other approaches you can take for the migration, if you do not want to upgrade in-place.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8232">Evgeni Golov</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/foreman_katello_leapp_elevate/attachments/slides/5283/export/events/attachments/foreman_katello_leapp_elevate/slides/5283/Migrating_Foreman_from_EL7_to_EL8_using_LEAPP_ELevate.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.infra/foreman_katello_leapp_elevate.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.infra/foreman_katello_leapp_elevate.mp4">Video recording(mp4)</link>
          <link href="https://leapp.readthedocs.io/en/latest/">LEAPP project</link>
          <link href="https://almalinux.org/elevate">ELevate</link>
          <link href="https://wiki.almalinux.org/elevate/ELevate-quickstart-guide.html">ELevate quickstart guide</link>
          <link href="https://github.com/oamg/leapp-repository/pull/733">Foreman/Katello/Satellite Actor PR for LEAPP</link>
          <link href="https://chat.fosdem.org/#/room/#infra-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#infra-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-foreman_katello_leapp_elevate:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#infra-foreman_katello_leapp_elevate:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13530.php">Submit feedback</link>
        </links>
      </event>
      <event id="13535">
        <start>12:00</start>
        <duration>00:45</duration>
        <room>D.infra</room>
        <slug>ansible_proxmox_rpmbuild</slug>
        <title>Using Ansible and Proxmox to manage an embedded RPM distro build factory:  lessons learned</title>
        <subtitle/>
        <track>Infra Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;With redpesk, we provide customers the ability to cross-build an embedded, CentOS Stream-based Linux distribution in the cloud. This requires a significant infrastructure: Koji/RPM builders, Angular-based WebUI, Gitlab forge, network and RPM package dependency management, Qemu test lab management, all need to come together and be connected, in a mix of Qemu virtual machines and LXC containers. Fortunately, Ansible and Proxmox comes to the rescue to manage this complexity.&lt;/p&gt;

&lt;p&gt;In this talk, we'll present our architecture of a self-contained CI/CD environment in the cloud, to cross-build RPM packages and Linux images. We will then dive into the specifics of using Ansible to drive Proxmox and deploy a mix of Packer-built Qemu virtual machines and LXC containers. Those provide a full Koji build system (hub and builders), an Angular frontend, Go backend, a Gitlab forge as well as network isolation/firewalling and a Qemu virtual target lab.
We'll continue with lessons learned from doing these deployments for multiple customers. We will finish describing solutions we are currently working on, like Ansible AWX, to address the challenges of doing it at scale and increase automation.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7030">Vincent Rubiolo</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.infra/ansible_proxmox_rpmbuild.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.infra/ansible_proxmox_rpmbuild.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#infra-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-ansible_proxmox_rpmbuild:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#infra-ansible_proxmox_rpmbuild:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13535.php">Submit feedback</link>
        </links>
      </event>
      <event id="13531">
        <start>13:00</start>
        <duration>00:45</duration>
        <room>D.infra</room>
        <slug>trusted_payload_nomand_waypoint</slug>
        <title>Running trusted payloads with Nomad and Waypoint</title>
        <subtitle/>
        <track>Infra Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Things like Infrastructure as Code, Service Discovery and Config Management can and have helped us to quickly build and rebuild infrastructure but we haven't nearly spend enough time to train our self to review, monitor and respond to outages.&lt;/p&gt;

&lt;p&gt;With the the introduction of CI/CD best practices into our day to day workflows we protect ourselves for introducing "bad" code into production and exposing flaws to our (end-)users. But what about influences from bad actors in- and out-side our projects. This talk will focus on the additional steps we can add to our Waypoint build pipelines to also protect ourselves to so called supply chain attacks while running our jobs in Nomad. We ll discuss scanning for vulnerabilities in incoming code, packages and images and signing the content artifacts we trust before exposing them to our users.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6629">Bram Vogelaar</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/trusted_payload_nomand_waypoint/attachments/slides/5081/export/events/attachments/trusted_payload_nomand_waypoint/slides/5081/RTPWNaW.pdf">Running Trusted Payloads with Nomad and Waypoint</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.infra/trusted_payload_nomand_waypoint.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.infra/trusted_payload_nomand_waypoint.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#infra-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-trusted_payload_nomand_waypoint:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#infra-trusted_payload_nomand_waypoint:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13531.php">Submit feedback</link>
        </links>
      </event>
      <event id="13533">
        <start>14:00</start>
        <duration>00:45</duration>
        <room>D.infra</room>
        <slug>ansible_reporting_ara</slug>
        <title>Simple (but useful) Ansible reporting with ara</title>
        <subtitle/>
        <track>Infra Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;ARA Records Ansible playbooks and makes them easier to understand and troubleshoot.
The author will explain why he created the project back in 2016 and how it might be useful for a wide range of use cases wherever Ansible runs from.
Including a live demo, we'll see how it works under the hood and you can expect to walk away from the presentation with an understanding on how to get started for your own Ansible playbooks within minutes.&lt;/p&gt;

&lt;p&gt;ARA Records Ansible playbook results in local (sqlite) or remote (mysql/postgresql) databases with a regular Ansible callback plugin. It provides an API, a reporting interface as well as a CLI to query, search and browse detailed and granular playbook task results for individual hosts.
Highlighting simplicity as a feature of the project, this presentation will provide examples that are appropriate for use whether Ansible runs from a laptop or at a large scale in production.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8637">David Moreau-Simard</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ansible_reporting_ara/attachments/slides/5093/export/events/attachments/ansible_reporting_ara/slides/5093/ara_fosdem_2022.pdf">Simple (but useful) Ansible reporting with ara</attachment>
        </attachments>
        <links>
          <link href="https://github.com/ansible-community/ara">Source code on GitHub</link>
          <link href="https://ara.recordsansible.org">Website and blog</link>
          <link href="https://twitter.com/RecordsAnsible">@RecordsAnsible on Twitter</link>
          <link href="https://matrix.to/#/#ara:libera.chat">#ara:libera.chat on Matrix</link>
          <link href="https://video.fosdem.org/2022/D.infra/ansible_reporting_ara.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.infra/ansible_reporting_ara.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#infra-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-ansible_reporting_ara:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#infra-ansible_reporting_ara:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13533.php">Submit feedback</link>
        </links>
      </event>
      <event id="13529">
        <start>15:00</start>
        <duration>00:45</duration>
        <room>D.infra</room>
        <slug>flatcar_container_linux</slug>
        <title>Immutable Infrastructure with Flatcar Container Linux</title>
        <subtitle/>
        <track>Infra Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Flatcar Container Linux is a minimal base OS to run containers.
As a friendly fork of CoreOS Container Linux it continues the project under a new name.
The main features are the A/B partitions for automatic updates and rollbacks, and the integration of Ignition for declarative configuration on first boot.
Declarative configuration is a key element for managing machines following the principle of Immutable Infrastructure, but causes friction if it means that the whole machine has to be reprovisioned for configuration changes.
With Ansible instead of Ignition for the configuration management we can find a compromise by giving up on avoiding configuration drift due to leftovers of old configurations and their side effects.
Out of this experience the idea was born to rerun Ignition on configuration changes.
While the big hammer method is to reformat the filesystem and losing application data, a more fine-grained solution could exist by clearing only parts of the filesystem.
This talk shows how to use Flatcar Container Linux with Terraform, Ignition, and Ansible, and ends with a proof-of-concept demo for Flatcar Container Linux to allow configuration changes through Ignition while avoiding configuration drift.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8842">Kai Lüke</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/flatcar_container_linux/attachments/slides/4965/export/events/attachments/flatcar_container_linux/slides/4965/Immutable_Infrastructure_with_Flatcar_Container_Linux.pdf"/>
        </attachments>
        <links>
          <link href="https://www.flatcar.org/">Flatcar Website</link>
          <link href="https://github.com/flatcar-linux/flatcar-terraform">Flatcar Terraform Examples</link>
          <link href="https://video.fosdem.org/2022/D.infra/flatcar_container_linux.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.infra/flatcar_container_linux.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#infra-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-flatcar_container_linux:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#infra-flatcar_container_linux:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13529.php">Submit feedback</link>
        </links>
      </event>
      <event id="13534">
        <start>16:00</start>
        <duration>00:45</duration>
        <room>D.infra</room>
        <slug>openshift_baremetal</slug>
        <title>Central Infrastructure Management: a user friendly deployment of OpenShift on Bare Metal</title>
        <subtitle/>
        <track>Infra Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The use of Bare Metal to run containerized workload is coming back into popularity.
There are multiple reasons for this increase of interest. First, the rise of big data analytics, high performance computing, machine learning workloads that need high-bandwidth and low latency and sometimes even requires access to special hardware devices like GPUs or DPUs. And at the same time, in the telecommunication space, the 5G networks technology stacks that drive the need for IPv6, SR-IOV, Container Network Functions (CNFs), NUMA topologies, and other innovations in containerized applications on bare metal.&lt;/p&gt;

&lt;p&gt;All of these emphasize the need for the ability to easily create Bare Metal based OpenShift clusters as automatically as possible.&lt;/p&gt;

&lt;p&gt;Central Infrastructure Management (CIM) exposes an intuitive user interface, allowing the infrastructure administrator to define a pool of Bare Metal machines making them available for users to independently create OpenShift clusters from them.&lt;/p&gt;

&lt;p&gt;Assisted Installer is an operator that introduces a new way to deploy a new OpenShift cluster on bare metal basically by only booting the nodes that will be part of the cluster, with an ISO it generates. The Assisted Installer will report inventory, run validations and orchestrate the needed steps based on the user parameters.&lt;/p&gt;

&lt;p&gt;CIM and Assisted Installer are components of Open Cluster Management (OCM), an operator that enables a single OCP cluster to manage a fleet of clusters.&lt;/p&gt;

&lt;p&gt;In this session, you will learn about Central Infrastructure Management and Assisted Installer architecture and its components. We will discuss the installation flow and how the components interact with each other. Finally, we will demonstrate how to build a pool of Bare Metal and install an OpenShift cluster on them via the CIM user interface.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8947">Jiří Tomášek</person>
          <person id="8957">Eran Cohen</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.infra/openshift_baremetal.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.infra/openshift_baremetal.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#infra-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-openshift_baremetal:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#infra-openshift_baremetal:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13534.php">Submit feedback</link>
        </links>
      </event>
      <event id="13532">
        <start>17:00</start>
        <duration>00:45</duration>
        <room>D.infra</room>
        <slug>rport_remote_access_management</slug>
        <title>RPort remote access and remote management</title>
        <subtitle/>
        <track>Infra Management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;An introduction (live demo with questions and answers) into RPort - a new open-source software for remote access and remote management of heterogeneous it-landscapes. Use the UI, the command line or an REST API to manage servers and desktop efficiently from a central place.&lt;/p&gt;

&lt;p&gt;RPort is a comprehensive solution for remote management of servers and desktop systems. Even if they are behind firewalls, routers and NAT. RPort is built on the client-server principle, clients connect to the server, the management component, using a secure reverse tunnel. Unlike pure SSH, RPort is made for heterogeneous environments (Windows, Linux, macOS) and addresses four basic needs of system administrators:
•  Secure remote access from anywhere via tunnels and SSH/RDP/VNC/HTTP and other TCP connections
•  Script and command execution on target machines via a central dashboard.
•  Automation of recurring tasks such as updates, inventory, configuration and fine-tuning of systems.
•  Monitoring and logging system load and resource usage.&lt;/p&gt;

&lt;p&gt;With RPort, a complete IT infrastructure with Windows, Linux and macOS systems can be managed via command line or a convenient web-based, central dashboard. The server component can be self-hosted or deployed in minutes using the automated installer provided by RPort.
RPort is released under the MIT open-source license.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8743">tkramm</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.infra/rport_remote_access_management.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.infra/rport_remote_access_management.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#infra-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#infra-rport_remote_access_management:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#infra-rport_remote_access_management:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13532.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.javascript">
      <event id="13149">
        <start>12:15</start>
        <duration>00:15</duration>
        <room>D.javascript</room>
        <slug>javascript_welcome_day_1</slug>
        <title>JavaScript welcome session - day #1</title>
        <subtitle/>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A short introduction about JavaScript Devroom with some interesting resources about JavaScript and a presentation about this special day for the FOSDEM JS Devroom.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1687">Ludovic Gasc</person>
          <person id="4435">Fabien Benetou (@Utopiah)</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.javascript/javascript_welcome_day_1.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/javascript_welcome_day_1.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-javascript_welcome_day_1:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-javascript_welcome_day_1:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13149.php">Submit feedback</link>
        </links>
      </event>
      <event id="13093">
        <start>12:30</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>technology_kits_choices</slug>
        <title>Technology kits (choices) that enable to consistently deliver high quality frontend solutions at speed</title>
        <subtitle/>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Did you face the difficulty of choosing a right architecture solution for a specific project or a client while considering their “rather” complex environment? Do you feel like you need to change your tech stack continuously?&lt;/p&gt;

&lt;p&gt;If the answer is yes to both of the questions, join my talk about the solutions I’ve found so we can ca discuss your best practice as well.&lt;/p&gt;

&lt;p&gt;Accelerators (technology kits) are opinionated yet pragmatic that I’ve identified and tested on the projects in production.
They allow me to go faster on delivering high-quality code with an easy to master architecture, to on-board other team members on the project and increase their productivity without reinventing everything from scratch.&lt;/p&gt;

&lt;p&gt;We will discuss about the main JS frameworks (Vue.js, React, Svelte, Angular) and their meta-framework (why use them?), the state management (local and server state), the accessibility (how to integrate it from the beginning?), the testing and styling (CSS, SCSS, CSS-In-JS, Tailwind, which one to choose?).&lt;/p&gt;

&lt;p&gt;Of course, take everything that will be said in this talk as an opinion, not as an absolute word because there is only one way to develop.&lt;/p&gt;

&lt;p&gt;Be ready to share your tips during Q&amp;amp;A session.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8848">Boubacar Siddighi BARRY</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/technology_kits_choices/attachments/slides/5148/export/events/attachments/technology_kits_choices/slides/5148/mirahi_fosdem_2022_technology_choices">Content</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.javascript/technology_kits_choices.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/technology_kits_choices.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-technology_kits_choices:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-technology_kits_choices:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13093.php">Submit feedback</link>
        </links>
      </event>
      <event id="12384">
        <start>13:00</start>
        <duration>01:00</duration>
        <room>D.javascript</room>
        <slug>destructuring_frontend_monoliths_with_microfrontends</slug>
        <title>Destructuring Frontend monoliths with MicroFrontends</title>
        <subtitle/>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;From loading Ajax requests in browsers to have full-blown frameworks; Javascript has come a long way. While moving stuff from backend to frontend the problems of backend are also ported. The Bigger the code gets bigger the problems, more dependencies, harder maintainability, eventually all the problems of a huge monolith.
With MicroFrontends, we can break this monolith into smaller independent, maintainable apps.
Sounds good? Let’s see how in this talk.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In the modern app architecture, Frontend contributes a major chunk of the setup, most of the business logic is housed in the Frontend. Over time Frontend app becomes a huge monolith, harder to maintain, trickier to add new features, and so on. With Microfrontends we break this monolith into smaller independent apps. These apps are developed independently but stitched as a SPA on the fly with all the goodies of client-side javascript. This has been done traditionally with several approaches, but with Webpack 5 we now have Module Federation, which opens the door for seamless MicroFrontend integrations.
In this talk, we will discuss the Microfrontends architecture pattern, how to destructure an existing monolith into MicroFrontends with help of Module Federation from Webpack 5. By the end of this talk, the attendees will be having a new vision of how they architect their Frontends.&lt;/p&gt;</description>
        <persons>
          <person id="4032">Trishul Goel</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.youtube.com/watch?v=frregZU6ck0&amp;list=PLI08QU9qtPEIwA1zukgHW8D7hdB7dh7Pz">Previous talks</link>
          <link href="https://slides.com/trishulgoel/microfrontends">Slides for MicroFrontends talk</link>
          <link href="https://github.com/tsl143/microfrontend-demo">MicroFrontends demo</link>
          <link href="https://github.com/module-federation/module-federation-examples">Module Federation examples</link>
          <link href="https://video.fosdem.org/2022/D.javascript/destructuring_frontend_monoliths_with_microfrontends.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/destructuring_frontend_monoliths_with_microfrontends.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-destructuring_frontend_monoliths_with_microfrontends:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-destructuring_frontend_monoliths_with_microfrontends:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12384.php">Submit feedback</link>
        </links>
      </event>
      <event id="13073">
        <start>14:00</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>behavior_graph</slug>
        <title>Behavior Graph</title>
        <subtitle>A proven architecture for complex applications</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Behavior Graph is a software architecture and state management library. It greatly enhances your ability to write complex user facing software and control systems.&lt;/p&gt;

&lt;p&gt;Broadly speaking, it belongs to the category of libraries which includes Redux, MobX, Rx (Reactive Extensions), and XState.&lt;/p&gt;

&lt;p&gt;It works by providing a new unit of composition which we call the behavior. Behaviors are simple blocks of code together with their dependency relationships.&lt;/p&gt;

&lt;p&gt;We developed Behavior Graph to address our own complexity challenges while building an iOS video playing library which is used internally throughout the suite of native Yahoo mobile apps. After years of development and production usage, it has proven to be incredibly competent at scale.&lt;/p&gt;

&lt;p&gt;We have since ported it to multiple languages including Javascript/Typescript. It is less than 1500 lines of code and contains no external dependencies.&lt;/p&gt;

&lt;p&gt;Behavior Graph should appeal to anyone with an interest in software architectures and willingness to rethink how we write software applications.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Behavior Graph makes the dependency relationships between blocks of code its primary responsibility. We believe these relationships are the main source of complexity in most applications. Behavior Graph asks programmers to explicitly declare these dependency relationships. In exchange, it ensures that blocks of code are run at the correct time and in the correct order. As a result, the programmer is freed to reason locally about contained units of functionality, while the computer takes on the increasing complexity burden as an application grows in size.&lt;/p&gt;

&lt;p&gt;In the presentation we will introduce the primary abstractions provided by Behavior Graph. We will do this by working through a simple example of how the library works with code samples. Then we will show how these pieces hold together as an architecture.&lt;/p&gt;

&lt;p&gt;We will briefly touch on how it compares to similarly positioned libraries. Finally we will look at the current state of the library and a roadmap for the future.&lt;/p&gt;</description>
        <persons>
          <person id="8834">Sean Levin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/yahoo/bgjs">Github</link>
          <link href="https://www.npmjs.com/package/behavior-graph">NPM</link>
          <link href="https://yahoo.github.io/bgdocs/docs/typescript/intro.html">Intro</link>
          <link href="https://yahoo.github.io/bgdocs/docs/typescript/guide.html">Programming Guide</link>
          <link href="https://video.fosdem.org/2022/D.javascript/behavior_graph.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/behavior_graph.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-behavior_graph:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-behavior_graph:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13073.php">Submit feedback</link>
        </links>
      </event>
      <event id="13123">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>metaverse</slug>
        <title>Can JS also build the metaverse?</title>
        <subtitle>How Javascript can be used to build linked social WebXR applications</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We keep on hearing about the metaverse but what is it and more importantly, can JS be used to build it?&lt;/p&gt;

&lt;p&gt;We'll briefly clarify what the metaverse is and give practical examples today with federated virtual reality servers managed by different persons.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Behind the buzzword from Facebook/Meta there is a truly interesting concept : connecting virtual worlds!&lt;/p&gt;

&lt;p&gt;To do so there is no need to be one of the largest advertising company. In fact there are several solutions working today allowing to navigate from 3D or VR web pages and even keep information across, like a profile. During this presentation we will explore the WebXR specifications, in particular links between pages, and test an implementation running today named ImmersSpace based on Mozilla Hubs and ActivityPub.&lt;/p&gt;</description>
        <persons>
          <person id="4435">Fabien Benetou (@Utopiah)</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://immers-space.github.io/immers-client/">Immers client documentation</link>
          <link href="https://hubs.mozilla.com/">Mozilla Hubs</link>
          <link href="https://activitypub.rocks/">ActivityPub</link>
          <link href="https://video.benetou.fr/videos/watch/37679db0-750d-40c1-b76c-67bad6c0207b">Video on installing Hubs on Digital Ocean</link>
          <link href="https://github.com/immers-space/immers-app/tree/main/immers-hubs">Documentation on installing Immers for Hubs</link>
          <link href="https://www.w3.org/2016/06/vr-workshop/minutes.html#traversal">W3C WebVR 2016 workshop notes on link traversal</link>
          <link href="https://fabien.benetou.fr/Wiki/VirtualRealityInterface">Using VR to manage notes</link>
          <link href="https://aframe.io/">AFrameVR framework</link>
          <link href="https://threejs.org/">ThreeJS framework</link>
          <link href="https://twitter.com/utopiah/status/1488871519451287552/">Connectivity in the metaverse</link>
          <link href="https://github.com/Igalia/wolvic">Wolvic WebXR browser</link>
          <link href="https://video.fosdem.org/2022/D.javascript/metaverse.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/metaverse.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-metaverse:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-metaverse:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13123.php">Submit feedback</link>
        </links>
      </event>
      <event id="13088">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>rapid_prototyping_physical_interfaces_with_web_serial_and_cheap_mcus</slug>
        <title>Rapid Prototyping Physical Interfaces with Web Serial and Cheap MCUs.</title>
        <subtitle>Quickly and cheaply doing design discovery and prototype development with only a web browser</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;(With a $4 microcontroller to build fun, accessible, and unique forms of interaction)&lt;/p&gt;

&lt;p&gt;The magic of computers and smartphones is the fact that they provide a very malleable interface - the screen. Without having to manufacture extra parts for every new application, this is a massive time and cost saving for engineers. However, this comes at a cost of accessibility and usability, as well as diminishing the physical connection one might have to the device they are using. Physical interfaces are now much easier to develop, and can even be constructed by the end user, since MCUs are now very cheap and readily available, along with lots of modular parts to construct interfaces with. Web Serial provides the added benefit of being able to use the highly distributed and easy to code with JavaScript / Web platform with these MCUs. This means rapid prototyping can be performed, along with user testing, very easily, making it much cheaper and faster to reach an end product. This talk intends to demonstrate some basic examples along with some steps to getting a process together yourself.&lt;/p&gt;</abstract>
        <description>&lt;ul&gt;
&lt;li&gt;Introduction to Web Serial API&lt;/li&gt;
&lt;li&gt;An overview of the MCU market today&lt;/li&gt;
&lt;li&gt;Demonstrations of some homemade physical interfaces for web applications&lt;/li&gt;
&lt;li&gt;How to set up a basic web app using web serial&lt;/li&gt;
&lt;li&gt;Overview of reading values from a physical input component through a circuit and converting it to serial data&lt;/li&gt;
&lt;li&gt;Using browser-based circuit design tools for safe pre-breadboard experimentation using Wokwi and CircuitJS&lt;/li&gt;
&lt;li&gt;Building a simple physical input, through to reading the data into the web application&lt;/li&gt;
&lt;li&gt;Ideas for potential tangible user interfaces, summary, questions.&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="8846">Louis Foster</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/drohen">Drohen Github</link>
          <link href="https://github.com/drohen/fosdem-2022-demo">Code for this talk</link>
          <link href="https://www.google.com/chrome/">Google Chrome</link>
          <link href="https://en.wikipedia.org/wiki/Serial_communication">Serial Communication Wikipedia</link>
          <link href="https://developer.mozilla.org/">MDN Browser Documentation</link>
          <link href="https://www.chromium.org/teams/web-capabilities-fugu">Project Fugu</link>
          <link href="https://www.falstad.com/circuit/circuitjs.html">CircuitJS</link>
          <link href="https://github.com/drohen/serial-web-test">Web Serial API example project</link>
          <link href="https://github.com/drohen/paddle-game">Paddle controller challenge</link>
          <link href="https://www.reddit.com/r/WebSerialAPI/">Web Serial API subreddit</link>
          <link href="https://github.com/drohen/awesome-web-serial">Web Serial API Awesome List</link>
          <link href="https://pocketmechatronics.com/posts/better-prototyping-with-web-serial-raspberry-pico/">https://pocketmechatronics.com/posts/better-prototyping-with-web-serial-raspberry-pico/</link>
          <link href="https://pocketmechatronics.com/posts/reflection-2-components-1-week/">https://pocketmechatronics.com/posts/reflection-2-components-1-week/</link>
          <link href="https://jaycarlson.net/microcontrollers/">$1 microcontrollers</link>
          <link href="https://free-pdk.github.io/">0.03c microcontrollers</link>
          <link href="https://www.raspberrypi.com/products/raspberry-pi-pico/">Raspberry Pi Pico</link>
          <link href="http://wiring.org.co/">Wiring</link>
          <link href="https://processing.org/">Processing</link>
          <link href="https://micropython.org/">Micropython</link>
          <link href="http://www.espruino.com/">Espruino</link>
          <link href="https://kaluma.io/">Kaluma</link>
          <link href="https://wokwi.com/arduino/new?template=kaluma-pi-pico">Wokwi - Kaluma blank project</link>
          <link href="https://glitch.com/edit/#!/remix/glitch-blank-website">Glitch - blank web app</link>
          <link href="https://video.fosdem.org/2022/D.javascript/rapid_prototyping_physical_interfaces_with_web_serial_and_cheap_mcus.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/rapid_prototyping_physical_interfaces_with_web_serial_and_cheap_mcus.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-rapid_prototyping_physical_interfaces_with_web_serial_and_cheap_mcus:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-rapid_prototyping_physical_interfaces_with_web_serial_and_cheap_mcus:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13088.php">Submit feedback</link>
        </links>
      </event>
      <event id="12945">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>bridging_the_gap_between_jamstack_and_big_data</slug>
        <title>Bridging the Gap between Jamstack and Big Data</title>
        <subtitle/>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I want to explain how to build data-intensive Jamstack apps with outstanding performance, low costs, and scalability while having great developer experience.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;It's been 15 years since the quote “Data is the new oil” was coined, and Jamstack is here for more than 6 years already. Yet, there's no straightforward way to build a data-intensive app with outstanding performance, low costs, and scalability while having great developer experience. Oh, really? In this talk, I'll show how you can build a lightning-fast Jamstack app that works with massive loads of data with open-source tools and having lots of fun.&lt;/p&gt;</description>
        <persons>
          <person id="8799">Igor  Lukanin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.javascript/bridging_the_gap_between_jamstack_and_big_data.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/bridging_the_gap_between_jamstack_and_big_data.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-bridging_the_gap_between_jamstack_and_big_data:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-bridging_the_gap_between_jamstack_and_big_data:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12945.php">Submit feedback</link>
        </links>
      </event>
      <event id="13086">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>accessibility_testing_with_html_validate</slug>
        <title>Accessibility testing with HTML-Validate</title>
        <subtitle/>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The hows and whys of using HTML-validate to automate accessibility testing for SPA.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7656">David Sveningsson</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://html-validate.org/">Project website</link>
          <link href="https://gitlab.com/html-validate/html-validate">Git source</link>
          <link href="https://video.fosdem.org/2022/D.javascript/accessibility_testing_with_html_validate.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/accessibility_testing_with_html_validate.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-accessibility_testing_with_html_validate:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-accessibility_testing_with_html_validate:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13086.php">Submit feedback</link>
        </links>
      </event>
      <event id="13063">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>e2e_testing_with_microsoft_playwright</slug>
        <title>E2E testing with Microsoft Playwright</title>
        <subtitle/>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Automated browser end-to-end testing is a powerful technique to ensure your web UI and backend work together nicely. In this talk, we show how we've leveraged Microsoft's Playwright library to refactor our test suite, enhance productivity and code quality.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;At ownCloud, we pride ourselves in shipping well-tested code. Besides the typical unit- and integration-tests, we use automated browser/end-to-end tests for our new web frontend, which is supported both by our "ownCloud classic" backend as well as developed alongside our new generation "ownCloud Infinite Scale" backend.&lt;/p&gt;

&lt;p&gt;Confronted with a flaky and complex continuous integration suite of end-to-end tests that was not actively maintained, hard to reason about (as well as sub-optimally documented due to the original creators leaving the project and running for, well, "longer than acceptable"), we opted to switch from Selenium/Nightwatch to Microsoft's Playwright (playwright.dev).&lt;/p&gt;

&lt;p&gt;Tune in for this talk when we show how our test suite evolved over time, listen to our reasoning about the technological switch, and also learn from the mistakes we made and best practices we extracted into practical examples.&lt;/p&gt;</description>
        <persons>
          <person id="8795">Florian Schade</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/e2e_testing_with_microsoft_playwright/attachments/slides/4983/export/events/attachments/e2e_testing_with_microsoft_playwright/slides/4983/fosdem22.pdf"/>
        </attachments>
        <links>
          <link href="https://github.com/owncloud/web">ownCloud Web</link>
          <link href="https://github.com/owncloud/ocis">ownCloud Infinite Scale</link>
          <link href="https://github.com/owncloud/core">ownCloud Core</link>
          <link href="https://github.com/microsoft/playwright">Microsoft Playwright</link>
          <link href="https://video.fosdem.org/2022/D.javascript/e2e_testing_with_microsoft_playwright.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/e2e_testing_with_microsoft_playwright.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-e2e_testing_with_microsoft_playwright:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-e2e_testing_with_microsoft_playwright:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13063.php">Submit feedback</link>
        </links>
      </event>
      <event id="12380">
        <start>17:00</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>search_and_aggregations_made_easy_with_nodejs_and_opensearch</slug>
        <title>Search and aggregations made easy with NodeJS and OpenSearch</title>
        <subtitle/>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Learn how OpenSearch works and get equipped with practical knowledge to search, aggregate and visualise your data.&lt;/p&gt;

&lt;p&gt;This is a hands-on session where we will use JavaScript to interact with the OpenSearch cluster - create an index, add documents, search and aggregate data. At the end we’ll visualise results with OpenSearch Dashboards.&lt;/p&gt;

&lt;p&gt;JavaScript engineers who are ready to add search and aggregation features to their applications should attend this session; no previous knowledge of OpenSearch is required.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this session the audience will get both theoretical and practical knowledge on what OpenSearch is and how they can work with it by using its NodeJS client. This is a hands-on session where the audience is invited to follow along.&lt;/p&gt;

&lt;p&gt;There will be an accompanying GitHub repository to allow the audience to follow me during or after the lecture.&lt;/p&gt;

&lt;p&gt;References to old talks:&lt;/p&gt;

&lt;p&gt;I’ve already run a similar session at AWS Community Day, added its link to the list of links. However, I will modify and improve the content based on the learnings from the previous session. So the content will not be the same.&lt;/p&gt;

&lt;p&gt;Audience:&lt;/p&gt;

&lt;p&gt;Javascript Developers with no or little knowledge on Opensearch or Elasticsearch.&lt;/p&gt;</description>
        <persons>
          <person id="8503">Olena Kutsenko</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://youtu.be/6ZMgamq2opc">Example of my talk on a similar topic</link>
          <link href="https://drive.google.com/file/d/17KrVDxSZEqkRTqXXGqxa__SGOs9mMaoQ/view?usp=sharing">Slides from my talk performed for a similar topic</link>
          <link href="https://video.fosdem.org/2022/D.javascript/search_and_aggregations_made_easy_with_nodejs_and_opensearch.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/search_and_aggregations_made_easy_with_nodejs_and_opensearch.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-search_and_aggregations_made_easy_with_nodejs_and_opensearch:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-search_and_aggregations_made_easy_with_nodejs_and_opensearch:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12380.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.kotlin">
    </room>
    <room name="D.legal">
      <event id="12955">
        <start>13:00</start>
        <duration>00:30</duration>
        <room>D.legal</room>
        <slug>teachingoss</slug>
        <title>How to teach OSS licenses and compliances at a university</title>
        <subtitle>how to teach to the students with some of the use cases</subtitle>
        <track>Legal and Policy Issues</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I have started to teach OSS licences and compliances at a Japanese university since last year. it was difficult to teach OSS licences and compliances because I should have shown many of use cases so that the students could learn what the licences and compliance are and more, they even didn't know how to deal with ordinal software licenses. So, I had to talk many of the background knowledges to the students as an 'introduction' so that students could understand the OSS licences with compliances with ease. Fortunately, there were good feedbacks from the students, though, I need to improve my lecture more gathering more use cases etc.
I will give a talk my experiences there at the university and discuss how to improve my lecture to teach such 'licences and compliances' to students. the feedbacks/ideas for my talk are really welcome!&lt;/p&gt;

&lt;p&gt;I will give a talk&lt;/p&gt;</abstract>
        <description>&lt;h1&gt;The opportunities to teach OSS licenses and compliances&lt;/h1&gt;

&lt;ol&gt;
&lt;li&gt;increase the incidents of OSS licenses violation&lt;/li&gt;
&lt;li&gt;keep compliances not to violate OSS licenses&lt;/li&gt;
&lt;li&gt;respect the authors and keep the licenses rules.&lt;/li&gt;
&lt;li&gt;reinventing of the wheel with compliances&lt;/li&gt;
&lt;/ol&gt;


&lt;h2&gt;the Difficulties to teach several OSS licenses&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;the difficulties for students to read several OSS license descriptions directly, really complex for them, especially GPL licenses.&lt;/li&gt;
&lt;li&gt;need to gather many of the incidents of OSS licenses violation.&lt;/li&gt;
&lt;li&gt;need to prepare good quiz(exam) so that students could understand with ease.&lt;/li&gt;
&lt;/ol&gt;


&lt;h2&gt;the lecture last year&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;why the University needs the lecture&lt;/li&gt;
&lt;li&gt;the trial and error for the students&lt;/li&gt;
&lt;li&gt;the advice from the staff at the university&lt;/li&gt;
&lt;li&gt;the feedbacks from the students&lt;/li&gt;
&lt;/ol&gt;


&lt;h2&gt;the lecture coming next year&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;gather more incidents to check&lt;/li&gt;
&lt;li&gt;looking into the incidents more - deep-diving for the practice.&lt;/li&gt;
&lt;li&gt;looking into new OSS licenses for DX&lt;/li&gt;
&lt;li&gt;any ideas...welcome!&lt;/li&gt;
&lt;/ol&gt;
</description>
        <persons>
          <person id="5568">Masafumi Ohta</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.legal/teachingoss.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.legal/teachingoss.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#legal-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-teachingoss:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#legal-teachingoss:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12955.php">Submit feedback</link>
        </links>
      </event>
      <event id="12725">
        <start>13:30</start>
        <duration>00:30</duration>
        <room>D.legal</room>
        <slug>dma</slug>
        <title>An update on the Digital Markets Act</title>
        <subtitle>The new European rules for online competition</subtitle>
        <track>Legal and Policy Issues</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Last year we introduced the reasons and the plans for the new Digital Markets Act of the European Union, regulating online markets to further more competition with the dominant gatekeepers. In 2021, the act was discussed and finally voted by the European Parliament, which expanded many of its provisions and strengthened the new rules. In 2022, the act will be negotiated again with member States and then, possibly, finally approved by the Parliament. In this update we will explain in details what has changed and where we are.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The Digital Markets Act introduces rules for "gatekeeper" digital companies, defining how to recognize them and setting obligations for them to fulfil. These obligations generally affect their business practices, such as the terms and conditions that they impose onto their business users and the consumers; the way they enter new markets and exploit their strength to conquer them; the opportunities that are left for users to choose competing services or move out of the walled gardens. Principles like unbundling and interoperability have been recognized as useful tools to promote competition.&lt;/p&gt;

&lt;p&gt;It is still to be understood whether all these obligations will survive the negotiation phases and will be confirmed in the final act. However, discussions are also starting on how some of these new provisions may be implemented, and how to define the details and the technical standards. The talk will present the current situation and solicit feedback and comments from the community.&lt;/p&gt;</description>
        <persons>
          <person id="4611">Vittorio Bertola</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/dma/attachments/slides/5240/export/events/attachments/dma/slides/5240/An_update_on_the_DMA_FOSDEM_2022.pdf">Slides for the talk</attachment>
        </attachments>
        <links>
          <link href="https://archive.fosdem.org/2021/schedule/event/digitalmarketsact/">Last year's talk on this subject</link>
          <link href="https://video.fosdem.org/2022/D.legal/dma.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.legal/dma.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#legal-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-dma:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#legal-dma:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12725.php">Submit feedback</link>
        </links>
      </event>
      <event id="12885">
        <start>14:00</start>
        <duration>00:30</duration>
        <room>D.legal</room>
        <slug>intlarbitration</slug>
        <title>A globally unified governance framework for Open Source</title>
        <subtitle>International arbitration to harmonize the security provisions of sovereign states and Open Source? Learning from the Java Virtual Machine, Ceph and abstraction layers</subtitle>
        <track>Legal and Policy Issues</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Differentiating between architectural flaws and bugs in socio-technical systems: Open Source is no legal term or a political institution in dominant sovereign state systems, making it vague and interpretable in different contexts. However, it is a fundamental institution in security provisions in today's socio-technical societies. But it remains impossible to harmonize the transnational Open Source system with sovereign systems: both cannot be clearly mapped to each other. Yet, international arbitration provides a type of remedy that already exists in software development, illustrating how a shift from just fighting bugs to mitigating architectural flaws can look like.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Initially, the Internet imitated the institutions of the social world despite their limited eligibility (such as "emails" with their complex and vulnerable architecture). Today, societies are socio-technical without delimitable transitions between technology/Internet and society. Societies have started to adapt to and integrate the possibilities the code provides, no longer vice versa. Sovereign state systems early found their limitations in tackling the resulting challenges. However, software development had already to manage comparable issues. The Java Virtual Machine and Ceph are two of many examples: another abstraction layer can create flexibility, simplification and unification on top of different systems.&lt;/p&gt;

&lt;p&gt;International arbitration could offer Open Source a transnational and globally-unified framework, enshrined in an arbitration agreement: embedded in a dedicated organization in an eligible legal system to facilitate the conduct of organizations and communities on which code and the Internet depend.&lt;/p&gt;

&lt;p&gt;Open source and its related institutions are already the core element of a transnational separation of powers, which is based upon competition: public processes &amp;amp; public code in conjunction with distribution (of development, code, review &amp;amp; testing) enable forking (to avoid monopolies and irrevocable consolidation of powers at one place). Reflecting the software engineering concept "secure by design", Open Source has created a "socio-technical system secure by design" because it avoids single points of failure both in social and technical realms: it does not relate governance to centralization but to distribution. Indeed, if issues like the 2020 Solarwinds Hack would spread in deployed Linux kernels, this could have unprecedented consequences far beyond the technical realms. However, Open Source and its institutions remain capable of providing sufficient security and deterrence. There is much more behind Open Source than just open/public code.&lt;/p&gt;

&lt;p&gt;The increasing use and consolidation of IT in governments may break the traditional separations of powers and does not provide the "security by design" of Open Source institutions if applied to socio-technical systems. Indeed, if one administrator and his password in one consolidated IT department can manipulate the databases used in executive, legislative and judiciary operations, new risks can arise. The system around Open Source already contributes to the security provision of and on the Internet and thus, indirectly to the overall security provision of people and entities that depend on the Internet: it facilitates security in socio-technical societies.&lt;/p&gt;

&lt;p&gt;If it proves eligible, enshrining the relevant (and legally implementable) Open Source institutions in an arbitration agreement may result in an compatible abstraction layer on top of the traditional state systems. Complementary, this abstraction layer may facilitate to release traditional systems from tackling issues they simply cannot tackle without softening and blurring their own institutional architecture. It may turn antagonism into symbiosis.&lt;/p&gt;

&lt;p&gt;However, Facebook's Libra indicates the complexity (but also the possibility) of creating such "implicit legal" ventures (in Switzerland). It also indicates that Switzerland could possibly enable the fusion of an international arbitration body (through its "international private law") with an open/public/distributed but regulable cryptocurrency to facilitate not just the (Open) Source but also (open) exchange within one globally unified system.&lt;/p&gt;

&lt;p&gt;Although they will be critical and challenging for any international arbitration approach, legal patent- and license-related questions are not considered in this lecture.&lt;/p&gt;

&lt;p&gt;This lecture is derived from the perspective of the field of international relations. It illustrates the role of Open Source in contemporary security provisions (next to and in interaction with sovereign states' security provisions for citizens) and it aims to put alternative (types of) approaches with and around Open Source into discussion.&lt;/p&gt;</description>
        <persons>
          <person id="8701">Christopher Klooz</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.legal/intlarbitration.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.legal/intlarbitration.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#legal-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-intlarbitration:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#legal-intlarbitration:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12885.php">Submit feedback</link>
        </links>
      </event>
      <event id="12834">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.legal</room>
        <slug>pandemicnowin</slug>
        <title>Why the pandemic could help FOSS, but was a win for proprietary software</title>
        <subtitle/>
        <track>Legal and Policy Issues</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;During the pandemic we have experienced a sudden growth of remote activities, with people working and studying from home. Most proprietary solutions were not suited for the task, as they were not compliant with GDPR, as they were profiling users beyond the provided service, and in many cases could not guarantee that end user data were maintained within Europe acconrding to EU legislations. Unfortunately, EU governments ignored the situation and signed contracts with big techs for remote work and remote teaching, exposing the personal information of million of EU citizens - the majority of them being students - to unauthorized practices. OSS could be the answer, but was ignored because there wasn't enough time to deploy appropriate solutions. The talk tries to provide a different perspective.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="312">Italo Vignoli</person>
        </persons>
        <attachments>
          <attachment type="audio" href="https://fosdem.org/2022/schedule/event/pandemicnowin/attachments/audio/5229/export/events/attachments/pandemicnowin/audio/5229/thepandemiccouldhelpfoss.pdf">Why the pandemic could help FOSS, but was a win for proprietary software</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.legal/pandemicnowin.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.legal/pandemicnowin.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#legal-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-pandemicnowin:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#legal-pandemicnowin:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12834.php">Submit feedback</link>
        </links>
      </event>
      <event id="12452">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.legal</room>
        <slug>deviceneutrality</slug>
        <title>Why Device Neutrality is important for Free Software?</title>
        <subtitle/>
        <track>Legal and Policy Issues</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The number of devices on which users cannot run Free Software is exponentially increasing. The consequence is an increased loss of control over users’ technology. In order to remediate this situation, the FSFE has been working with the concept of Device Neutrality, understood as a policy principle that ensures users equal access and non-discriminatory use of their devices. The FSFE has advocated for four main principles: stricter consent rules for pre-installed apps, no vendor lock-in, full interoperability, and real-time data portability. The talk will explain the concepts and the challenges ahead.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;While digital devices are a ubiquitous reality in all aspects of life, control over the hardware and software running on them is increasingly being limited by internet platforms, digital services providers, hardware manufacturers, and vendors. Several policy and legal concepts have been developed by the academic sector in cooperation with regulatory bodies and courts to tackle this issue in the EU.&lt;/p&gt;

&lt;p&gt;The whole debate boiled down to principles that have been included in the EU's major overhaul of internet law: the Digital Markets Act. Device neutrality is a policy term that translates as non-discrimination of services and apps by providers, manufacturers, and vendors. The objective of device neutrality is to enable consumers to bypass gatekeepers and enable a fair and non-discriminatory use of Free Software.&lt;/p&gt;

&lt;p&gt;The talk will explain the four main demands the FSFE has been leveraging in the public debates and legislative processes:
* Strict end-user consent for pre-installed apps;
* No vendor lock-in;
* Interoperability of services based on Open Standards
* Real-time data portability&lt;/p&gt;</description>
        <persons>
          <person id="7023">Lucas Lasota</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://fsfe.org/news/2021/news-20211122-01.en.html">Device Neutrality demands</link>
          <link href="https://video.fosdem.org/2022/D.legal/deviceneutrality.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.legal/deviceneutrality.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#legal-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-deviceneutrality:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#legal-deviceneutrality:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12452.php">Submit feedback</link>
        </links>
      </event>
      <event id="13543">
        <start>15:30</start>
        <duration>01:00</duration>
        <room>D.legal</room>
        <slug>organizerslegalpolicy</slug>
        <title>Panel: Hot Topics</title>
        <subtitle>Organizers of the Legal &amp; Policy DevRoom discuss the issues of the day</subtitle>
        <track>Legal and Policy Issues</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The organizers of the Legal and Policy DevRoom for FOSDEM 2022 discuss together the issues they've seen over the last year in FOSS, and consider what we can learn from the presentations on the track this year, and look forward together about the future of FOSS policy.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The organizers of the Legal and Policy DevRoom for FOSDEM 2022 discuss together the issues they've seen over the last year in FOSS, and consider what we can learn from the presentations on the track this year, and look forward together about the future of FOSS policy.&lt;/p&gt;</description>
        <persons>
          <person id="441">Bradley M. Kuhn</person>
          <person id="448">Karen Sandler</person>
          <person id="3794">Max Mehl</person>
          <person id="7487">Alexander Sander</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.legal/organizerslegalpolicy.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.legal/organizerslegalpolicy.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#legal-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#legal-organizerslegalpolicy:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#legal-organizerslegalpolicy:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13543.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.open-hardware">
    </room>
    <room name="D.libreoffice">
      <event id="12832">
        <start>13:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_odfbetterthanooxml</slug>
        <title>Why ODF is a better standard than OOXML</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Open Document Format (ODF) and Office Open XML (OOXML) are both ISO/IEC open document standards, but while the first is loyal to standard definitions the second is an unfortunate attempt to propagate proprietary formats in a pseudo-standard format to lock-in users to Microsoft Office for the foreseeable future. The presentation explains why ODF is a better standard than OOXML.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="312">Italo Vignoli</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_odfbetterthanooxml/attachments/slides/5227/export/events/attachments/lotech_odfbetterthanooxml/slides/5227/whyodfisabetterstandardthanooxml.pdf">Why ODF is a better standard than OOXML</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_odfbetterthanooxml.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_odfbetterthanooxml.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_odfbetterthanooxml:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_odfbetterthanooxml:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12832.php">Submit feedback</link>
        </links>
      </event>
      <event id="12850">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_ooxmldocument</slug>
        <title>OOXML Document Analysis</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I will talk about how do we proceed when we receive a problematic OOXML document from a customer and show a solution of a sample bug.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3452">Gülşah Köse</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_ooxmldocument.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_ooxmldocument.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_ooxmldocument:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_ooxmldocument:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12850.php">Submit feedback</link>
        </links>
      </event>
      <event id="12336">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_200pagelecturebook</slug>
        <title>Let's Build a 200-Page-Long Lecture Book with LibreOffice Writer</title>
        <subtitle>Challanges, tips and tricks that work and that don't</subtitle>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In 2021, a tender financed by the Australian Government has been won. The purpose of the project was to create a lecture book for kids, parents and their teachers who have a European (Hungarian) background, and who want to keep their cultural heritage, while they are living in a non-Hungarian speaking country.&lt;/p&gt;

&lt;p&gt;Such a project has a lot of interesting challenges but in this talk, mostly the technical aspects will be introduced. The perspective and the journey of the editor of the book will be demonstrated, whose responsibility was to combine the chapters written by three different authors into a single, ready-to-print document.&lt;/p&gt;

&lt;p&gt;The main tools were LibreOffice Writer and Draw but GIMP and InkScape also played a significant role.&lt;/p&gt;

&lt;p&gt;In the talk, various tricks and steps will be shown how the document has been created and how the different tools were able to cooperate. Besides the working ways, some non-working paths and traps also will be shown.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8467">Csongor Halmai</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_200pagelecturebook.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_200pagelecturebook.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_200pagelecturebook:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_200pagelecturebook:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12336.php">Submit feedback</link>
        </links>
      </event>
      <event id="12925">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_professionaltemplates</slug>
        <title>Creating professional templates with LibreOffice Writer</title>
        <subtitle>A brief panorama on how much important templates are and what can be done (and automated) inside them.</subtitle>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;One of the tasks of my job is to create corporate templates. It is really important to spend the right amount of time on them, since they are the image of the entity (whatever kind of) to the public, and they usually last for decades. Knowing well the needs and requirements is possible to automate a lot of things, still without macros. But pushing so much Writer to its limits let us discover some minor bug or possible enhancements.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8789">Gabriele Ponzo</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_professionaltemplates/attachments/slides/4966/export/events/attachments/lotech_professionaltemplates/slides/4966/2022_02_FOSDEM_PonzoGabriele_ProTemplates.pdf">PonzoGabriele Creating Professional Templates with LibreOffice Writer</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_professionaltemplates.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_professionaltemplates.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_professionaltemplates:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_professionaltemplates:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12925.php">Submit feedback</link>
        </links>
      </event>
      <event id="12512">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_documentthemes</slug>
        <title>Document themes in LibreOffice Impress and elsewhere</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;LibreOffice was capable of handling color palettes on its UI for a while
already. In the meantime, the competition introduced document themes, which
are a fixed set of 12 colors, to be attached to various parts of documents.
This allows referring to those colors by name, and apply color filters. These
color filters are maintained even if the source theme changes. Come and see
how this now starts to work also in Impress, what still needs doing and how
you can help.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="779">Miklos Vajna</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_documentthemes.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_documentthemes.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_documentthemes:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_documentthemes:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12512.php">Submit feedback</link>
        </links>
      </event>
      <event id="12818">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_advantagesoflotech</slug>
        <title>Advantages of LibreOffice Technology</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Today, the LibreOffice Technology platform is based on the same software engine for all modules, based on a clean and refactored source code, with a focus on code quality and consistency, and supported by easy and extensive APIs. LibreOffice consistency represents a strong advantage over the "siloed" approach of all other office suites, where there is a different software engine for each application and each platform. The result is a lack of consistency for files, which are also different by platform. LibreOffice Technology is the best open source platform for personal productivity, and is tightly integrated on desktop, mobile and cloud.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="312">Italo Vignoli</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_advantagesoflotech/attachments/slides/5226/export/events/attachments/lotech_advantagesoflotech/slides/5226/advantagesoflotechnology.pdf">Advantages of LibreOffice Technology</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_advantagesoflotech.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_advantagesoflotech.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_advantagesoflotech:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_advantagesoflotech:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12818.php">Submit feedback</link>
        </links>
      </event>
      <event id="12708">
        <start>17:00</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_canvasforux</slug>
        <title>Canvas For Rendering UX</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I will present why we needed to use Canvas for rendering the UI and the document. Then i will explain the structure we created for this task.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8694">Gökay Şatır</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_canvasforux.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_canvasforux.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_canvasforux:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_canvasforux:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12708.php">Submit feedback</link>
        </links>
      </event>
      <event id="12567">
        <start>17:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_informationengineering</slug>
        <title>Information Engineering Operations</title>
        <subtitle>A DevOps paradigm for Product Documentation Group</subtitle>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The product document intersects between product and non-product teams. The dependency on the product features is invariably high with the early adopters and existing user base.&lt;/p&gt;

&lt;p&gt;Integrating with the non-product groups to understand the expected use cases, building scenarios with the product team with quality and security being implicit will be the objective of this information engineering operations group.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Imagine the user base is trying to figure out a mail-merge situation using Base and Writer modules. LibreOffice offers features to integrate with the modules to merge and generate compelling mails.&lt;/p&gt;

&lt;p&gt;An authoritative multilingual guide to accomplishing the scenarios will take a whale of time to reach the user base. Treating it as a lost opportunity, the new paradigms to integrate with the non-product and product teams will table the perspective of mirroring DevSecOps.&lt;/p&gt;

&lt;p&gt;This talk will highlight the opportunities available within the industry for the Information Engineering team.&lt;/p&gt;</description>
        <persons>
          <person id="8530">Vasudev Narayanan</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_informationengineering/attachments/slides/4777/export/events/attachments/lotech_informationengineering/slides/4777/IEOps.odp">Product User Documentation - A Modern Approach</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_informationengineering.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_informationengineering.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_informationengineering:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_informationengineering:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12567.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.llvm">
      <event id="12959">
        <start>13:00</start>
        <duration>00:35</duration>
        <room>D.llvm</room>
        <slug>llvm_fortran_debug</slug>
        <title>Enhanced debuggability support in LLVM for various Fortran language features</title>
        <subtitle>Fortran debuggabiliy support in LLVM</subtitle>
        <track>LLVM</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The aim of this abstract is to showcase the enhanced debuggability support added in LLVM for the Fortran language features. LLVM being emerging compiler framework, there was some gap to be bridged w.r.t. Fortran language debug info generation. This is because Fortran language has few features which are very powerful, as compared to other languages.&lt;/p&gt;

&lt;p&gt;Fortran dynamic arrays are one such powerful language feature. There are variety of arrays like adjustable array, assumed shape, assumed size, assumed rank, allocatable and pointer arrays. LLVM generated debug info was not sufficient to debug these many variety of arrays with GDB/LLDB. The LLVM was lacking support for multiple DWARF operators (DW&lt;em&gt;OP&lt;/em&gt;push&lt;em&gt;object address, DW&lt;/em&gt;OP&lt;em&gt;over), DWARF attributes (DW&lt;/em&gt;AT&lt;em&gt;data&lt;/em&gt;location, DW&lt;em&gt;AT&lt;/em&gt;allocated, DW&lt;em&gt;AT&lt;/em&gt;associated, DW&lt;em&gt;AT&lt;/em&gt;rank) and a DWARF TAGs (DW&lt;em&gt;TAG&lt;/em&gt;generic_subrange). Other than these, existing support for DISubrange was not sufficient to handle Fortran arrays. The same was true for Fortran strings which is not mere pointer to character type and needed more support from LLVM. Other features which needed similar LLVM support for debugging were Fortran modules, namelist and signed constants etc.&lt;/p&gt;

&lt;p&gt;All these enhancements made in LLVM are as per DWARF4 or DWARF5 specification for the Fortran language. These enhanced debug info are used by GDB/LLDB and user debugging experience is improved now while handling these Fortran features with GDB/LLDB. In order to make use of these enhanced debug info emitted by LLVM, GDB/LLDB is also enhanced in cases where required. With these enhancements added now in LLVM, Fortran program debugging experience with the clang/flang emitted programs are on par with gcc/gfortran emitted programs and in some cases it’s even better than gcc/gfortran.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8791">Alok Sharma</person>
          <person id="9012">Bhuvanendra Kumar N</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/llvm_fortran_debug/attachments/slides/5097/export/events/attachments/llvm_fortran_debug/slides/5097/Enhanced_debuggability.pdf"/>
        </attachments>
        <links>
          <link href="https://reviews.llvm.org/D79484">https://reviews.llvm.org/D79484</link>
          <link href="https://reviews.llvm.org/D86305">https://reviews.llvm.org/D86305</link>
          <link href="https://reviews.llvm.org/D108553">https://reviews.llvm.org/D108553</link>
          <link href="https://reviews.llvm.org/D99273">https://reviews.llvm.org/D99273</link>
          <link href="https://reviews.llvm.org/D79306">https://reviews.llvm.org/D79306</link>
          <link href="https://reviews.llvm.org/D79592">https://reviews.llvm.org/D79592</link>
          <link href="https://reviews.llvm.org/D80197">https://reviews.llvm.org/D80197</link>
          <link href="https://reviews.llvm.org/D83544">https://reviews.llvm.org/D83544</link>
          <link href="https://reviews.llvm.org/D87500">https://reviews.llvm.org/D87500</link>
          <link href="https://reviews.llvm.org/D89141">https://reviews.llvm.org/D89141</link>
          <link href="https://reviews.llvm.org/D89208">https://reviews.llvm.org/D89208</link>
          <link href="https://reviews.llvm.org/D89218">https://reviews.llvm.org/D89218</link>
          <link href="https://reviews.llvm.org/D99335">https://reviews.llvm.org/D99335</link>
          <link href="https://reviews.llvm.org/D109343">https://reviews.llvm.org/D109343</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_fortran_debug.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_fortran_debug.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-llvm_fortran_debug:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-llvm_fortran_debug:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12959.php">Submit feedback</link>
        </links>
      </event>
      <event id="12385">
        <start>13:35</start>
        <duration>00:25</duration>
        <room>D.llvm</room>
        <slug>llvm_c_extension</slug>
        <title>How to write an extension for C</title>
        <subtitle>In this talk we will briefly describe how to add your own extension to C, what steps may be needed to do it. And then we will review a small example</subtitle>
        <track>LLVM</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk we will briefly describe how to add your own extension to C, what steps may be needed to do it. And then we will review a small example&lt;/p&gt;</abstract>
        <description>&lt;p&gt;We want to summarize our findings, which we gathered during implementation of procedural-parametric extension for C. This work will present a list of examples about how to extend existing structures in clang, and how to map your new constructions from source code to LLVM IR
More details about procedural-parametric approach: https://dl.acm.org/doi/10.1145/2556610.2556619
In that article you'll see examples of this extension implemented in Modula-like programming language. It will give you full picture about what we implemented in C&lt;/p&gt;</description>
        <persons>
          <person id="8509">Pavel Kosov</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_c_extension.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_c_extension.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-llvm_c_extension:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-llvm_c_extension:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12385.php">Submit feedback</link>
        </links>
      </event>
      <event id="12577">
        <start>14:00</start>
        <duration>00:35</duration>
        <room>D.llvm</room>
        <slug>llvm_ebpf</slug>
        <title>Coverage for eBPF programs</title>
        <subtitle/>
        <track>LLVM</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;eBPF is fastly becoming the first choice for implementing tracing and security-critical applications and software.&lt;/p&gt;

&lt;p&gt;Yet, its ecosystem lacks tooling to make developers' life easier.&lt;/p&gt;

&lt;p&gt;Join this talk to get to know bpfcov: an open-source tool I wrote that uses the LLVM pass infrastructure to instrument your eBPF programs to collect coverage data while they run in the eBPF VM in the Linux kernel.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;I bet we all have heard so much about eBPF in recent years. Isn't it?&lt;/p&gt;

&lt;p&gt;Every day we hear about a new project using some eBPF magic underneath.&lt;/p&gt;

&lt;p&gt;eBPF programs are written in C but compiled for a specific ISA later executed by the eBPF Virtual Machine.&lt;/p&gt;

&lt;p&gt;LLVM has a specific backend allowing us to write C and get eBPF ELF objects out.&lt;/p&gt;

&lt;p&gt;Still, there are no tools helping developers to clearly understand which path their code took while running, which branches were uncovered, and maybe why.
Even testing the eBPF programs is a pain, given that not all the types of eBPF programs are supported by &lt;code&gt;BPF_PROG_TEST_RUN&lt;/code&gt; in the Linux kernel.&lt;/p&gt;

&lt;p&gt;Yes, BTF and CO-RE are improving the situation.
But, writing eBPF is still mostly about fighting against the BPF VM verifier.&lt;/p&gt;

&lt;p&gt;Until today, there is no simple way to visualize how the flow of your eBPF program running in the kernel actually was.&lt;/p&gt;

&lt;p&gt;That's why I sat down and wrote bpfcov.
A tool to gather source-based coverage info from your eBPF programs.&lt;/p&gt;

&lt;p&gt;During this talk, I will show the audience the secrets of the BPF target in LLVM and how I wrote an out-of-tree LLVM pass to instrument eBPF programs with counters, counters expressions, and friends.&lt;/p&gt;

&lt;p&gt;The goal is to help eBPF developers to get to know how to use the powerful LLVM infrastructure to make the eBPF ecosystem - and their life - better.&lt;/p&gt;</description>
        <persons>
          <person id="6561">Leonardo Di Donato</person>
        </persons>
        <attachments>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/llvm_ebpf/attachments/other/4778/export/events/attachments/llvm_ebpf/other/4778/143920095_22ad5959_25e7_4b8b_a39b_535cbc485daf.png">Source based coverage for eBPF programs using the LLVM tools</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/llvm_ebpf/attachments/other/4779/export/events/attachments/llvm_ebpf/other/4779/143920675_66a88f5f_86fe_45fa_a45f_27461eb6768e.png">Coverage expanding macros</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/llvm_ebpf/attachments/other/4891/export/events/attachments/llvm_ebpf/other/4891/html2.png">Coverage for BPF LSM</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/llvm_ebpf/attachments/other/4892/export/events/attachments/llvm_ebpf/other/4892/mult1.png">HTML reports for source-based code coverage of multiple eBPF programs/files</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/llvm_ebpf/attachments/other/4893/export/events/attachments/llvm_ebpf/other/4893/json1.png">JSON report</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/llvm_ebpf/attachments/slides/5159/export/events/attachments/llvm_ebpf/slides/5159/slides.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/elastic/bpfcov">bpfcov repository</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_ebpf.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_ebpf.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-llvm_ebpf:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-llvm_ebpf:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12577.php">Submit feedback</link>
        </links>
      </event>
      <event id="12460">
        <start>14:35</start>
        <duration>00:25</duration>
        <room>D.llvm</room>
        <slug>llvm_llsoftsecbook</slug>
        <title>Llsoftsecbook: an open source book on software security for compiler developers</title>
        <subtitle/>
        <track>LLVM</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Compilers play a crucial role in hardening software against security attacks. As compiler engineers we experience an increase in demand for security-related features: we simply work on security-related features more often.
We find it tough to analyze whether the hardenings we implement are easy or hard to circumvent by attackers. After chatting about this with many compiler developers, our experience is that most feel their work would benefit from a deeper understanding of attacks and hardening techniques. After having looked around, we didn't find much educational material that gives a broad overview, covering all aspects compiler developers ought to know about.
Therefore, we recently started an open source book titled "Low Level Software Security for Compiler developers" at https://github.com/llsoftsec/llsoftsecbook/. It aims to improve the industry-wide knowledge about security hardening in compilers and related tools; ultimately leading to more innovation and better implementations of security features.
In this presentation, we'll explain the rationale for this new open source project in more detail. We will discuss what content we have so far and what content we plan to add. The project very much welcomes new contributors: we need more new content, more review of content, discussion of ideas for how to make the book better, improvement in the design and layout of the produced HTML and PDF output, etc. We hope this presentation will reach both anyone interested in learning more about low-level software security and anyone interested in helping to grow this project further.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3445">Kristof Beyls</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/llvm_llsoftsecbook/attachments/slides/4988/export/events/attachments/llvm_llsoftsecbook/slides/4988/Llsoftsecbook_Low_level_software_security_for_compiler_developers_fosdem_2022_slides.pdf"/>
        </attachments>
        <links>
          <link href="https://github.com/llsoftsec/llsoftsecbook/">https://github.com/llsoftsec/llsoftsecbook/</link>
          <link href="https://llsoftsec.github.io/llsoftsecbook/">Live version of the book</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_llsoftsecbook.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_llsoftsecbook.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-llvm_llsoftsecbook:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-llvm_llsoftsecbook:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12460.php">Submit feedback</link>
        </links>
      </event>
      <event id="12630">
        <start>15:00</start>
        <duration>00:35</duration>
        <room>D.llvm</room>
        <slug>llvm_8bit</slug>
        <title>8-bit Character support on architectures were the smallest addressable unit size is 64-bit in Clang and LLVM</title>
        <subtitle>8-bit characters in VIAMPP</subtitle>
        <track>LLVM</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Clang and LLVM have a great history of supporting a great variety of CPUs, from 8- to 64-bits assuming they all have a smallest size of an addressable unit of 8-bits words. Despite the fact that a lot of types and there alignment can be defined with the “target datalayout” string, the “character” and “short” type have been hard-coded into clang and llvm.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Clang and LLVM have a great history of supporting a great variety of CPUs, from 8- to 64-bits assuming they all have a smallest size of an addressable unit of 8-bits words. Despite the fact that a lot of types and there alignment can be defined with the “target datalayout” string, the “character” and “short” type have been hard-coded into clang and llvm. Once you compile with clang you will get for example:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;@.str = private unnamed_addr constant [6 x i8] c"Hallo\00", align 8
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Some proposals exist to that offer a solutions to this problem (e.g. FOSDEM 2012: “Adding 16-bit Character Support in LLVM” or https://lists.llvm.org/pipermail/llvm-dev/2019-May/132080.html: “On removing magic numbers assuming 8-bit bytes”). Following this ideas one has to apply changes to over 120 files (clang and llvm v12.0.0) and keeping a patch set nearly impossible.&lt;/p&gt;

&lt;p&gt;Looking for simpler solution for this problem we explored a couple of alternative solutions. Two design goals have to be satisfied:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;don’t change CHAR_BIT
keep CharWidth at 8-bits
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Only the modification of the character alignment to 64-bits is allowed. With modifying only 8 files (some of them only dealing with character assertions) we end up with the desired result of:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;@.str = private unnamed_addr constant [6 x i64] [i64 72, i64 97, i64 108, i64 108, i64 111, i64 0], align 8
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This solutions can also easily be adopted to machines with a minimal addressable unit of 16- or 32-bits. Also “WChar” can be addressed with minimal changes.&lt;/p&gt;

&lt;p&gt;As this is solution is still under testing, the amount of files changed might be further reduced, and should allow for a small and simple patch set.&lt;/p&gt;</description>
        <persons>
          <person id="8665">Thomas Pietsch</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/llvm_8bit/attachments/slides/5026/export/events/attachments/llvm_8bit/slides/5026/Slide_set">8-bit Character Support</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_8bit.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_8bit.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-llvm_8bit:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-llvm_8bit:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12630.php">Submit feedback</link>
        </links>
      </event>
      <event id="12668">
        <start>15:35</start>
        <duration>00:25</duration>
        <room>D.llvm</room>
        <slug>llvm_oniro</slug>
        <title>Libc++ on Linux - using the example of Oniro</title>
        <subtitle>Experiences with switching from libstdc++ to libc++</subtitle>
        <track>LLVM</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Oniro - the Eclipse Foundation's embedded operating system -
is switching from libstdc++ to libc++ by default. This talk
gives an overview of our experience daring to
make the switch.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Oniro - the Eclipse Foundation's embedded operating system -
is switching from libstdc++ to libc++ by default.&lt;/p&gt;

&lt;p&gt;Binary compatibility is a holdup for libc++ adoption on
Linux desktops and servers - but in the embedded world,
we have more options.&lt;/p&gt;

&lt;p&gt;This talk gives an overview of our experience daring to
make the switch.&lt;/p&gt;</description>
        <persons>
          <person id="2501">Bernhard Rosenkränzer</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://oniroproject.org/">The Oniro Project</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_oniro.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_oniro.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-llvm_oniro:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-llvm_oniro:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12668.php">Submit feedback</link>
        </links>
      </event>
      <event id="12645">
        <start>16:00</start>
        <duration>00:25</duration>
        <room>D.llvm</room>
        <slug>llvm_antlr</slug>
        <title>LLVM and ANTLR: A Starter on a non-Linux Machine</title>
        <subtitle/>
        <track>LLVM</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Although Linux is still the best preferred operating system, the talk begins with a problem statement regarding the dependencies of ANTLR and LLVM on Windows. To this end, the presenter will explain how these dependency issues can be resolved through an easy-to-use environment for building, installing and running native LLVM and ANTLR on Windows. Furthermore, the talk will briefly explain how we can design domain specific languages (DSLs) using a powerful combination of ANTLR and LLVM front end while maintaining a logical isolation of parsing and code generation.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7580">Babar Khan</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_antlr.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.llvm/llvm_antlr.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#llvm-llvm_antlr:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#llvm-llvm_antlr:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12645.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.mariadb">
      <event id="12989">
        <start>10:00</start>
        <duration>00:05</duration>
        <room>D.mariadb</room>
        <slug>mariadb_welcome</slug>
        <title>Welcome to the MariaDB devroom</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A brief introduction and overview of what you can expect from the MariaDB devroom at FOSDEM&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5872">Ian Gilfillan</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_welcome.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_welcome.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_welcome:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_welcome:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12989.php">Submit feedback</link>
        </links>
      </event>
      <event id="12733">
        <start>10:05</start>
        <duration>00:20</duration>
        <room>D.mariadb</room>
        <slug>mariadb_model</slug>
        <title>MariaDB Server's new release model</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As was announced in December 2021 https://mariadb.org/new-innovation-release-model/, MariaDB Server now has a new release model, with more frequent major releases. MariaDB Server 10.7 is the first release following this model.&lt;/p&gt;

&lt;p&gt;Some of these releases will have 1 year support cycles, while others will be supported long term just like before. In this talk, I will present the pros and cons of this new release model, what it means for the MariaDB Server community, its users and also its developers. This will also give the community a chance to better understand the changes and give us feedback and ultimately ensure MariaDB Server properly serves its purpose of being a true Open Source Database.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7772">Michael "Monty" Widenius</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://mariadb.org/new-innovation-release-model/">New release model announcement</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_model.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_model.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_model:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_model:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12733.php">Submit feedback</link>
        </links>
      </event>
      <event id="12724">
        <start>10:25</start>
        <duration>00:20</duration>
        <room>D.mariadb</room>
        <slug>mariadb_106</slug>
        <title>What is new in mariadb 10.6 ?</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;MariaDB is one of the most used open-source relational databases. The development of MariaDB focuses on stability and performance.MariaDB 10.6 is the current stable version of MariaDB and comes with a number of new features. This presentation covers - MariaDB in Open Source Ecosystem, Features in MariaDB 10.6, Variables added and Removed.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8702">Praveen GR</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_106.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_106.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_106:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_106:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12724.php">Submit feedback</link>
        </links>
      </event>
      <event id="12643">
        <start>10:45</start>
        <duration>00:25</duration>
        <room>D.mariadb</room>
        <slug>mariadb_107_108</slug>
        <title>New features in MariaDB 10.7 and MariaDB 10.8</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;At the time of writing, MariaDB 10.7 is in RC, and the MariaDB 10.8 preview releases are imminent. The new release model means new features no longer have to wait a year between major releases before seeing the light of day, and the initiative of separate preview releases for each major feature eases testing and reduces instability.&lt;/p&gt;

&lt;p&gt;This presentation covers some of the major new features being unveiled in MariaDB 10.7 and 10.8.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5872">Ian Gilfillan</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_107_108.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_107_108.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_107_108:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_107_108:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12643.php">Submit feedback</link>
        </links>
      </event>
      <event id="12660">
        <start>11:10</start>
        <duration>00:25</duration>
        <room>D.mariadb</room>
        <slug>mariadb_macos</slug>
        <title>MariaDB Server on macOS</title>
        <subtitle>Does it make sense to even try?</subtitle>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Current MariaDB Server GA versions are formally not supported on macOS 10.x and 11.y. But it;s relatively easy to set up the environment and build it from current 10.2 - 10.7 GitHub sources, with few minor issues to resolve in the process depending on maxOS and major server version used. This talk is a summary of my related experience, with a quick review of related fixed and open bugs, as well as some unique features like DTrace support that one may benefit from on macOS.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Current MariaDB Server GA versions are formally not supported (and probably not even regularly built or tested) on macOS 10.x and 11.y. But it's relatively easy to set up the environment and build MariaDB Server from current 10.2 - 10.7 GitHub sources, with few minor issues to resolve in the process, depending on maxOS and major server version used.&lt;/p&gt;

&lt;p&gt;This talk is a summary of my related experience on 10.13 High Sierra that I had a chance to work on recently, with additional quick review of related fixed and open bugs, as well as some unique features like DTrace support that one may benefit from on macOS. Actually, studying DTrace in context of MariaDB Server troubleshooting and performance tuning was one of the goals why I started to use macOS again.&lt;/p&gt;</description>
        <persons>
          <person id="2718">Valerii Kravchuk</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mariadb_macos/attachments/slides/5009/export/events/attachments/mariadb_macos/slides/5009/MariaDB_Server_on_macOS_FOSDEM_2022_MariaDB_Devroom.pdf"/>
        </attachments>
        <links>
          <link href="https://jira.mariadb.org/issues/?jql=text%20~%20%22macOS%22">MariaDB Server bugs and feature requests possibly specific to macOS</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_macos.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_macos.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_macos:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_macos:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12660.php">Submit feedback</link>
        </links>
      </event>
      <event id="12736">
        <start>11:35</start>
        <duration>00:25</duration>
        <room>D.mariadb</room>
        <slug>mariadb_histograms</slug>
        <title>Improved histograms in MariaDB 10.8</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;MariaDB 10.8 is getting improved histograms, called JSON_HB. This talk will cover
- what the new histograms are,
- what are the advantages over the old histograms,
- how do they compare to histograms in MySQL 8.&lt;/p&gt;

&lt;p&gt;At the end of the talk, I'll cover a closely related topic of usage of the histogram
data in the query optimizer:
- why this is hard,
- what are known limitations and their workarounds
- what MariaDB team is doing to improve this.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3487">Sergei Petrunia</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_histograms.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_histograms.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_histograms:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_histograms:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12736.php">Submit feedback</link>
        </links>
      </event>
      <event id="12560">
        <start>12:00</start>
        <duration>00:30</duration>
        <room>D.mariadb</room>
        <slug>mariadb_innodb</slug>
        <title>Performance oriented InnoDB log format changes</title>
        <subtitle>How InnoDB crash recovery works</subtitle>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The persistent circular buffer (the &lt;code&gt;ib_logfile0&lt;/code&gt;) is the fundament of the persistent InnoDB buffer pool.&lt;/p&gt;

&lt;p&gt;Over the years, the log file format has been changed in MariaDB Server to improve the performance. A well-designed file format imposes minimal write amplification and is easy to parse.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The 512-byte block size of the InnoDB log was a perfect match for the industry standard that was defined by the venerable Seagate ST-225. Alas, the industry moved on, and now block sizes range from 64 bytes (the size of a memory cache line) to 4096 bytes. Therefore, a format that works efficiently with any block size is needed.&lt;/p&gt;

&lt;p&gt;We present a flexible format where each mini-transaction (comprising log records) is a block on its own, with a checksum that is calculated in a local buffer, reducing contention on the mutex that protects the global log buffer. The old 12-byte block header is shrunk to a 1-bit sequence number, for detecting the end of the circular log. The additional overhead is 4 bytes per mini-transaction for a CRC-32C checksum.&lt;/p&gt;

&lt;p&gt;No-op records may be written to pad the log buffer to match the physical block size. Encryption will only cover data. The length of each record is explicitly stored in clear, which allows consistent hot backups without having any encryption keys. For encrypted log, 8-byte part of initialization vector will be written after each mini-transaction.&lt;/p&gt;</description>
        <persons>
          <person id="6968">Marko Mäkelä</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mariadb_innodb/attachments/slides/5140/export/events/attachments/mariadb_innodb/slides/5140/Performance_oriented_InnoDB_log_format_changes.pdf">Performance oriented InnoDB log format changes</attachment>
        </attachments>
        <links>
          <link href="https://jira.mariadb.org/browse/MDEV-12353">MDEV-12353 redo log record format changes in 10.5</link>
          <link href="https://jira.mariadb.org/browse/MDEV-14425">MDEV-14425 redo log block format changes (10.8)</link>
          <link href="https://github.com/MariaDB/server/tree/preview-10.8-MDEV-14425-innodb">preview-10.8-MDEV-14425</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_innodb.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_innodb.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_innodb:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_innodb:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12560.php">Submit feedback</link>
        </links>
      </event>
      <event id="12734">
        <start>12:30</start>
        <duration>00:25</duration>
        <room>D.mariadb</room>
        <slug>mariadb_optimizer</slug>
        <title>MariaDB Optimizer - ongoing development and changes</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The MariaDB optimizer has its roots in the original MySQL optimizer. Being a long standing project, it has inherited a number of quirks and features that -at the time of coding- made sense. The datasets had different sizes 10-20 years ago and the cost model is not always accurate for current workloads.&lt;/p&gt;

&lt;p&gt;Thus, there is now an ongoing effort to significantly improve the calculations that the MariaDB Optimizer is doing. With the addition of JSON Histograms, the range optimizer is one of the most impacted modules. The end goal of this effort is to provide the user with a better query optimizer, but also put the user in control and allow the user to tweak many more parameters than were previously available. In this talk I will go through the major changes that are upcoming in MariaDB, changes that could impact query performance (for the better) and also raise awareness about which parameters have the highest impact on query optimizer performance.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7772">Michael "Monty" Widenius</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_optimizer.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_optimizer.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_optimizer:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_optimizer:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12734.php">Submit feedback</link>
        </links>
      </event>
      <event id="12515">
        <start>13:00</start>
        <duration>00:30</duration>
        <room>D.mariadb</room>
        <slug>mariadb_mysql</slug>
        <title>MySQL 8 vs MariaDB 10.7</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;MySQL 8 and MariaDB 10.6 are the latest Major versions for MySQL and MariaDB. While MariaDB started by being slightly different MySQL variant,  now it has grown into very much different database platforms which grows more different from every release.&lt;/p&gt;

&lt;p&gt;In this presentation, we will look into the differences between MySQL and MariaDB in the core areas such as SQL features, query optimizations, replication, storage engines, and security. We will also discuss the unique features and capabilities MySQL 8 and MariaDB 10.6 offers compared to each other.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7756">Peter Zaitsev</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_mysql.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_mysql.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_mysql:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_mysql:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12515.php">Submit feedback</link>
        </links>
      </event>
      <event id="12709">
        <start>13:30</start>
        <duration>00:20</duration>
        <room>D.mariadb</room>
        <slug>mariadb_pit_recovery</slug>
        <title>MariaDB Point-in-Time-Recovery</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Backup is typically done once a a day. But if you destroy your data hours later: What about the changes between your backup and the catastrophic event? In this presentation I will show you how you can recover your data between your backup until a specific point in time before the incident.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="279">Oli Sennhauser</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_pit_recovery.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_pit_recovery.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_pit_recovery:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_pit_recovery:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12709.php">Submit feedback</link>
        </links>
      </event>
      <event id="12665">
        <start>13:50</start>
        <duration>00:30</duration>
        <room>D.mariadb</room>
        <slug>mariadb_backup_restic</slug>
        <title>Mariabackup + Restic: a simple and efficient online backup solution for your DBs</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Mariabackup is a wonderful tool to perform physical online backups of MariaDB Server. By coupling it with Restic you can easily and efficiently create encrypted incremental backups of your DBs on the wide range of Restic's supported backends (local, sftp, s3, OpenStack swift, etc.).&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8292">Faustin Lammler</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mariadb_backup_restic/attachments/slides/5135/export/events/attachments/mariadb_backup_restic/slides/5135/mariabackup_restic.pdf">Presentation slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_backup_restic.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_backup_restic.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_backup_restic:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_backup_restic:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12665.php">Submit feedback</link>
        </links>
      </event>
      <event id="12731">
        <start>14:20</start>
        <duration>00:25</duration>
        <room>D.mariadb</room>
        <slug>mariadb_deny</slug>
        <title>MariaDB DENY command</title>
        <subtitle>Upcoming functionality for sysadmins and database service providers</subtitle>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;MariaDB allows fine grained control of access over different database objects. Granting access to a very specific resource is easy. A problem comes up when one wants to grant access to a whole database &lt;em&gt;except&lt;/em&gt; for a particular resource (table, column, etc.). The only solution thus far is to grant access to each individual resource and omit the ones that must not be accessible. Clearly this is not maintainable, nor practical.&lt;/p&gt;

&lt;p&gt;This is where the DENY command comes in. The gist of the feature: A user will not be able to access denied resources unless the deny is explicitly revoked. MDEV-14443 - Reverse privileges in MariaDB is an ongoing tasks that will implement it. During this talk we will go through use cases, comparison to similar features of other databases well as implementation details of the feature which will (very likely) be part of MariaDB 10.9.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3999">Vicentiu Ciorbaru</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://jira.mariadb.org/browse/MDEV-14443">JIRA Task describing the technical aspects</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_deny.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_deny.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_deny:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_deny:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12731.php">Submit feedback</link>
        </links>
      </event>
      <event id="12711">
        <start>14:45</start>
        <duration>00:25</duration>
        <room>D.mariadb</room>
        <slug>mariadb_galera</slug>
        <title>MariaDB Galera Cluster and M/S replication</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Many say: Galera or Master/Slave replication. What about Galera AND Master/Slave Replication? In this presentation we look at different scenarios where it makes sense to use both technologies together...&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="279">Oli Sennhauser</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_galera.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_galera.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_galera:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_galera:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12711.php">Submit feedback</link>
        </links>
      </event>
      <event id="12516">
        <start>15:15</start>
        <duration>00:30</duration>
        <room>D.mariadb</room>
        <slug>mariadb_tips</slug>
        <title>Ten Tips for Better MariaDB Performance</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Optimizing MariaDB performance and troubleshooting MariaDB problems are two of the most critical and challenging tasks for DBA’s. The databases powering your applications need to be able to handle heavy traffic loads while remaining responsive and stable so that you can deliver an excellent user experience. Further, DBA’s are also expected to find cost-efficient means of solving these issues.
In this presentation, we will discuss how you can optimize and troubleshoot MariaDB performance. We will look at specific, common MariaDB problems and review the ten tips that allow you to diagnose and resolve them.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7756">Peter Zaitsev</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_tips.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_tips.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_tips:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_tips:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12516.php">Submit feedback</link>
        </links>
      </event>
      <event id="12655">
        <start>15:45</start>
        <duration>00:25</duration>
        <room>D.mariadb</room>
        <slug>mariadb_triggers</slug>
        <title>Creative uses of triggers</title>
        <subtitle>Things you people wouldn't believe</subtitle>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Sometimes you shouldn't do something just because you can. Really. Nevertheless, you can.
This talk will explore the creative, occasionally useful, often unhealthy things that you can do with triggers. Attend at your risk.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7643">Federico Razzoli</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_triggers.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_triggers.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_triggers:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_triggers:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12655.php">Submit feedback</link>
        </links>
      </event>
      <event id="12710">
        <start>16:15</start>
        <duration>00:25</duration>
        <room>D.mariadb</room>
        <slug>mariadb_connectionid</slug>
        <title>MariaDB Connection ID</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The MariaDB Connection ID exists since "ever". So why bother about such a boring thing? Because you can get many interesting information out of it...&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="279">Oli Sennhauser</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://fromdual.com/mariadb_connection_id">You are here MariaDB Connection ID</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_connectionid.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_connectionid.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_connectionid:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_connectionid:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12710.php">Submit feedback</link>
        </links>
      </event>
      <event id="12662">
        <start>16:40</start>
        <duration>00:25</duration>
        <room>D.mariadb</room>
        <slug>mariadb_bfptrace</slug>
        <title>More on bpftrace for MariaDB DBAs and Developers</title>
        <subtitle>Summary of recent experience</subtitle>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;bpftrace is a relatively new open source tracer for modern Linux (kernels 5.x.y) that may help to troubleshoot performance issues in production as well as to get insights on how software really works. More exotic use cases for the tool, as well as few more advanced bpftrace-based scripts useful for MariaDB DBAs and developers are presented.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;bpftrace is a relatively new open source tracer for modern Linux (kernels 5.x.y) that may help to troubleshoot performance issues in production as well as to get insights on how software really works. I use it for a couple of years and would like to present more details on how to do it efficiently, including but not limited to adding tracepoints to different lines of the code inside functions, suing bpftrace as a code coverage tool and tracing in Docker etc.&lt;/p&gt;</description>
        <persons>
          <person id="2718">Valerii Kravchuk</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mariadb_bfptrace/attachments/slides/5008/export/events/attachments/mariadb_bfptrace/slides/5008/More_on_bpftrace_for_MariaDB_DBAs_and_Developers_FOSDEM_2022_MariaDB_Devroom.pdf"/>
        </attachments>
        <links>
          <link href="https://archive.fosdem.org/2021/schedule/event/mariadb_bpftrace/">My talk on bpftrace basics</link>
          <link href="https://github.com/iovisor/bpftrace">bpftrace on GitHub </link>
          <link href="https://www.percona.com/resources/technical-presentations/monitoring-and-tracing-mysql-or-mariadb-server-bpftrace-percona">My related long presentation from Percona Live 2021</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_bfptrace.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_bfptrace.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_bfptrace:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_bfptrace:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12662.php">Submit feedback</link>
        </links>
      </event>
      <event id="12634">
        <start>17:05</start>
        <duration>00:30</duration>
        <room>D.mariadb</room>
        <slug>mariadb_json</slug>
        <title>Introducing MYSQL_JSON plugin</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;MYSQL_JSON plugin is created in MariaDB as a bridge to bypass the confusion between MySQL and MariaDB JSON data type representation and to help MariaDB users in that regard.
Purpose of this talk will be to highlight how to convert MySQL data directory containing JSON native data type in MySQL to the MariaDB data directory where JSON is stored as an alias for LONGTEXT and how to deal with errors in that process.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7663">Anel Husakovic</person>
        </persons>
        <attachments>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/mariadb_json/attachments/paper/5137/export/events/attachments/mariadb_json/paper/5137/Introducing_MYSQL_JSON">FOSDEM 2022 Introducing MYSQL_JSON</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_json.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_json.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_json:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_json:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12634.php">Submit feedback</link>
        </links>
      </event>
      <event id="12365">
        <start>17:35</start>
        <duration>00:25</duration>
        <room>D.mariadb</room>
        <slug>mariadb_confidential</slug>
        <title>The future of databases is confidential</title>
        <subtitle/>
        <track>MariaDB Server</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In today’s cloud-first world, data security is still a major concern. Confidential computing addresses this at the root by protecting data in use: sensitive workloads are run inside hardware-isolated and runtime-encrypted environments called enclaves.&lt;/p&gt;

&lt;p&gt;We have developed the first open-source database based on MariaDB designed for confidential computing. EdgelessDB is a MySQL-compatible database that runs entirely inside Intel SGX enclaves.&lt;/p&gt;

&lt;p&gt;In this talk, we'll introduce EdgelessDB and compare it to conventional databases as well as existing database encryption solutions. We'll explore the benefits, novelties, and why confidentiality is an important feature of a database. Finally, you'll learn about uses cases and how to easily get started.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8991">Felix Schuster</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_confidential.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mariadb/mariadb_confidential.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mariadb-mariadb_confidential:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-mariadb_confidential:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12365.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.matrix">
    </room>
    <room name="D.microkernel">
      <event id="13124">
        <start>10:40</start>
        <duration>00:10</duration>
        <room>D.microkernel</room>
        <slug>ssumpf</slug>
        <title>Introduction</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Welcome talk and introduction to the Microkernel and Component-based OS devroom at FOSDEM 2022.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="605">Martin Děcký</person>
          <person id="3629">Sebastian Sumpf</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="http://fosdem.microkernel.info/">About the devroom</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-ssumpf:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-ssumpf:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13124.php">Submit feedback</link>
        </links>
      </event>
      <event id="12458">
        <start>10:50</start>
        <duration>00:30</duration>
        <room>D.microkernel</room>
        <slug>jstecklina</slug>
        <title>Advanced Unit Testing in the Hedron Microkernel</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Concurrent code is hard to get right, but at the same time also hard to test. It gets worse when hardware interaction is required. This leads to a comparatively poor culture of unit testing in kernel code, where both come together.&lt;/p&gt;

&lt;p&gt;In this talk, I’m going to highlight one particular method of unit testing the page table manipulation code in Hedron, a microkernel written in C++ specially geared towards virtualization workloads. This code safely modifies page tables that are concurrently used by the CPU. Usually, unit tests only check whether the state after an operation meets the expectation of the programmer. In contrast, Hedron employs completely deterministic unit tests that show that the CPU will always see a valid virtual memory mappings while a page table manipulation is in progress (for the tested cases).&lt;/p&gt;

&lt;p&gt;The goal of this task is to show that unit tests can be a powerful tool even for properties of code that are usually not deemed unit testable.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="608">Julian Stecklina</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/jstecklina/attachments/slides/4836/export/events/attachments/jstecklina/slides/4836/hedron_unit_testing.pdf">Talk Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/cyberus-technology/hedron/">Hedron Source</link>
          <link href="https://x86.lol/">Blog about x86 low-level topics</link>
          <link href="https://syslog.show/">Podcast about OS topics</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/jstecklina.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/jstecklina.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-jstecklina:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-jstecklina:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12458.php">Submit feedback</link>
        </links>
      </event>
      <event id="12926">
        <start>11:20</start>
        <duration>00:30</duration>
        <room>D.microkernel</room>
        <slug>dzammit</slug>
        <title>A practical solution for GNU/Hurd's lack of drivers: NetBSD's rumpkernel framework</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;GNU/Hurd is the original Free Software operating system started in the 1980s. Its microkernel design has been evolving over the years and the project has not quite hit mainstream use. I believe this is due to one main reason: the lack of drivers for peripherals and hardware. In this talk, I explain how NetBSD kernel drivers have been reused in a microkernel setting and demonstrate their use to boot up a GNU/Hurd system via a userspace rump disk driver, with a driverless Hurd kernel, gnumach. The ACPI management, PCI management, and actual driver are in separate processes with RPC interfaces between them, which separates out their debugging, licencing concerns and execution. I believe this aligns with the original vision for the operating system, (as a Hurd of servers).&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8788">Damien Zammit</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/dzammit/attachments/slides/4850/export/events/attachments/dzammit/slides/4850/rump_hurd_talk.pdf">Rump Hurd Talk Slides</attachment>
        </attachments>
        <links>
          <link href="http://hurd.gnu.org">GNU/Hurd</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/dzammit.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/dzammit.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-dzammit:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-dzammit:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12926.php">Submit feedback</link>
        </links>
      </event>
      <event id="12859">
        <start>11:50</start>
        <duration>00:50</duration>
        <room>D.microkernel</room>
        <slug>nfeske</slug>
        <title>Genode meets the Pinephone</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Driven by the vision of a truly trustworthy smartphone, I dedicated the past year to bringing the component-based Genode OS to the Pinephone. The talk presents my experience story, touching on the hardware, booting, the porting of the kernel, component-architecture concerns, and device drivers.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Smartphones have become a commodity almost everyone relies on. With the convenience, however, comes complexity that is impossible to comprehend and constantly changing. The opaqueness of hardware and software puts the user in a subordinate position, making their devices - and by extension many aspects of their life - dependent on the decisions of a few dominant corporations. Our personal devices are constantly changing under our fingertips. Steady updates are presumably needed to stay secure, similar to how medicine is needed to stay healthy. But are the incentives of the platform providers aligned with my interests?&lt;/p&gt;

&lt;p&gt;I want my digital life healthy without a constant supply of medicine! To reinforce trust, both hardware and software must become transparent, traceable, and tractable. The Pinephone satisfies the urge for transparency of the hardware, thanks to publicly available schematics and documentation. However, the predominant software stacks - even though based on the open-source Linux kernel - are practically inscrutable because of their immense complexity. Genode's rigid component architecture promises to bring order and clarity - and thereby trustworthiness - to the software.&lt;/p&gt;

&lt;p&gt;Over the course of the past year, I pursued the combination of Genode with the Pinephone, diving deep into the Pinephone schematics, the SoC, booting, Genode's kernel, and device drivers. In my talk, I present the experiences made, touch on the use of Linux drivers directly on Genode, and draft a plan forward. The talk will be garnished by a demonstration.&lt;/p&gt;</description>
        <persons>
          <person id="607">Norman Feske</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/nfeske/attachments/slides/4876/export/events/attachments/nfeske/slides/4876/genode_meets_pinephone.pdf">Genode meets the Pinephone</attachment>
        </attachments>
        <links>
          <link href="https://genodians.org">Genodians.org</link>
          <link href="https://genode.org">Genode OS Framework</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/nfeske.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/nfeske.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-nfeske:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-nfeske:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12859.php">Submit feedback</link>
        </links>
      </event>
      <event id="13002">
        <start>12:40</start>
        <duration>00:35</duration>
        <room>D.microkernel</room>
        <slug>agrinten</slug>
        <title>Managarm: Design of a pragmatic fully-asynchronous microkernel</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk, we explore the design of Managarm's microkernel. Managarm is a pragmatic microkernel-based OS with a focus on asynchronous operations. The talk covers various aspects of the microkernel, such as its IPC model, resource management, and user space API. Managarm's microkernel employs a capability-based design to manage hardware resources. In contrast to current mainstream OSes, Managarm's system calls never block but report completion asynchronously whenever possible. This includes system calls for common tasks such as memory management or inter-process communication (IPC). A lock-free ring buffer is used to quickly deliver asynchronous completion notifications to user space. Managarm implements a POSIX subsystem to be able to run various well-known UNIX applications (e.g., a Wayland desktop) on top of the microkernel. This subsystem is implemented entirely in user space. The kernel uses various acceleration strategies to to efficiently support this use case.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8814">Alexander van der Grinten</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/agrinten/attachments/slides/5149/export/events/attachments/agrinten/slides/5149/managarm_fosdem22.pdf"/>
        </attachments>
        <links>
          <link href="https://github.com/managarm/managarm">Repository</link>
          <link href="https://managarm.org">https://managarm.org</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/agrinten.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/agrinten.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-agrinten:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-agrinten:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13002.php">Submit feedback</link>
        </links>
      </event>
      <event id="12678">
        <start>13:15</start>
        <duration>00:35</duration>
        <room>D.microkernel</room>
        <slug>skuenzer</slug>
        <title>Debugging and Monitoring in Unikraft</title>
        <subtitle>Everything beyond printf()</subtitle>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Unikernels are hard to debug? Unikernels cannot be easily administrated or monitored? While unikernels have the potential to revolutionize our infrastructures and take cloud computing into the next era, many worry that unikernels cannot be seamlessly integrated into today’s development and production workflows.
At the Unikraft team, we are heavily working on addressing these concerns and changing the status quo. Although unikernels are monolithic bundles of only necessary kernel functions and an application, we follow the concept that everything is a (micro-)library. Users can pick and choose kernel functionality at build time. The same applies for monitoring and debugging: In this talk, we will give an overview of our current debugging and monitoring capabilities, and we will present our vision for how these pieces will enable a cloud-native experience. We will also give a deep dive into our GDB backend implementation with a live demo.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Unikraft is an open source Xen Project incubator under the auspices of the Linux Foundation. We are currently launching a start-up with the mission to provide Unikraft unikernels for production and enterprise use.&lt;/p&gt;</description>
        <persons>
          <person id="5391">Simon Kuenzer</person>
          <person id="8718">Marc Rittinghaus</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/skuenzer/attachments/slides/5153/export/events/attachments/skuenzer/slides/5153/unikraft_microkerneldevroom_fosdem2022.pdf">Debugging and Monitoring in Unikraft</attachment>
        </attachments>
        <links>
          <link href="https://unikraft.org">Unikraft OSS</link>
          <link href="https://github.com/unikraft">GitHub Community</link>
          <link href="https://unikraft.io">Unikraft - The lightweight virtualization company</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/skuenzer.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/skuenzer.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-skuenzer:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-skuenzer:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12678.php">Submit feedback</link>
        </links>
      </event>
      <event id="12999">
        <start>13:50</start>
        <duration>00:40</duration>
        <room>D.microkernel</room>
        <slug>anano</slug>
        <title>Hardware accelerated applications on Unikernels for Serverless Computing</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Serverless computing facilitates the use of resources without the burden of administering and maintaining infrastructure. The simplification of IaaS appears ideal (in theory) but providers and users are presented with several challenges: providers aim to reduce infrastructure maintenance overheads; users require isolation, flexibility and programming freedom.&lt;/p&gt;

&lt;p&gt;Serverless deployments are mostly backed by sandboxed containers. To enable programming freedom for users, providers allow the use of containers for function deployment, however, to ensure strict isolation, these containers are sandboxed in VMs. As a result, this bloated stack brings complicated maintenance costs: (a) several layers of abstraction between the user function to be executed and the actual execution environment; (b) increased attack surface; (c) increased request-to-exec time; (d) reduced set of feature availability for functions (hardware acceleration).&lt;/p&gt;

&lt;p&gt;Unikernels promise fast boot times, small memory footprint and stronger security but lack in terms of manageability. Additionally, Serverless frameworks only support containers. Moreover, unikernels provide a different environment for applications, with limited or no support for widely used libraries and OS features. This issue is even more apparent in the case of ML/AI workloads. ML/AI libraries are often dynamically linked and have numerous dependencies, which directly contradict the statically linked notion of unikernels. Finally, hardware acceleration is almost non-existent in unikernel frameworks, mainly due to the absence of suitable virtualization solutions for such devices.&lt;/p&gt;

&lt;p&gt;In this talk, we present the design of a flexible serverless framework designed for the cloud and the edge, backed by unikernels that can access hardware accelerators. We go through the components that comprise the framework and elaborate on the challenges in building such a software stack: we first present an overview of the necessary components of a serverless framework; then we focus on the function execution framework based on two popular unikernel frameworks; finally, we present a hardware acceleration abstraction to expose semantic acceleration functionality to workloads running on top of this framework.&lt;/p&gt;

&lt;p&gt;A short demo of the working components will be presented, discussing the challenges and trade-offs of this approach.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5495">Anastassios Nanos</person>
          <person id="8216">Charalampos Mainas</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/anano/attachments/slides/4924/export/events/attachments/anano/slides/4924/NBFC_microkernel_2022.pdf">Hardware accelerated applications on unikernels for Serverless Computing</attachment>
        </attachments>
        <links>
          <link href="https://vaccel.org">vAccel: a hardware acceleration abstraction for serverless computing</link>
          <link href="https://github.com/nubificus/solo5-faas">Solo5 on OpenFaaS (Demo 1)</link>
          <link href="https://github.com/nubificus/unikraft-vaccel-faas">Image Classification with vAccel on OpenFaaS using Unikraft (Demo 2)</link>
          <link href="https://github.com/cloudkernels/vaccelrt">vAccelRT</link>
          <link href="https://github.com/nubificus/unikraft-vaccel">vAccel on Unikraft</link>
          <link href="https://nubificus.co.uk/jobs">Join us!</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/anano.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/anano.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-anano:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-anano:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12999.php">Submit feedback</link>
        </links>
      </event>
      <event id="12491">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.microkernel</room>
        <slug>awarkentin</slug>
        <title>UX/RT - a QNX-like OS based on seL4</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;UX/RT is a new QNX-like OS based on the seL4 microkernel, with improvements in security and reliability over mainstream systems as well as several features they lack, while still maintaining a high degree of compatibility with and comparable performance to existing operating systems. Similar to QNX, UX/RT will be a single-personality Unix-like OS with fast synchronous kernel IPC, a lightweight IPC transport layer, services looked up through the filesystem, and an avoidance of vertical modularity for most subsystems. I will introduce the general architecture of UX/RT and how it differs from existing operating systems, describe a few notable features, and explain why I consider it to be the best balance of practicality, performance, compatibility, and features.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8575">Andrew Warkentin</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/awarkentin/attachments/slides/4831/export/events/attachments/awarkentin/slides/4831/uxrt_intro.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://gitlab.com/uxrt">Top-level UX/RT GitLab group</link>
          <link href="https://gitlab.com/uxrt/uxrt-toplevel/-/blob/master/architecture_notes">Notes on UX/RT's architecture</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/awarkentin.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/awarkentin.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-awarkentin:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-awarkentin:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12491.php">Submit feedback</link>
        </links>
      </event>
      <event id="12975">
        <start>15:00</start>
        <duration>00:45</duration>
        <room>D.microkernel</room>
        <slug>vnarayanan</slug>
        <title>RedLeaf: Isolation and Communication in a Safe Operating System</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;At least since the final Multics report in 1977, researchers identified the ability to isolate kernel subsystems as a critical mechanism for increasing the reliability and security of the kernel. Unfortunately, despite many attempts to introduce isolation to the kernel, modern systems remain monolithic. Historically, software and hardware mechanisms introduce a prohibitively high overhead for the isolation of subsystems with the tightest performance budgets. Today, however, the balance of isolation and performance is starting to change with the development of Rust, arguably, the first practical programming language that achieves safety without garbage collection.&lt;/p&gt;

&lt;p&gt;RedLeaf is a new operating system developed from scratch in Rust with the goal to explore the impact of language safety on operating system organization, and specifically on the ability to utilize fine-grained isolation and its benefits in the kernel. In contrast to commodity systems, RedLeaf does not rely on hardware address spaces for isolation and instead uses only type and memory safety of the Rust language. Departure from costly hardware isolation mechanisms allows us to explore the design space of systems that embrace lightweight fine-grained isolation of kernel subsystems. We develop a new abstraction of a language-based isolation domain that implements a unit of information hiding and isolation of faults. Domains can be dynamically loaded and cleanly terminated. Building on  RedLeaf isolation mechanisms, we demonstrate the possibility to implement end-to-end zero-copy, fault isolation, and transparent recovery of device drivers.&lt;/p&gt;

&lt;p&gt;To evaluate the practicality of RedLeaf abstractions, we implemented a subset of the POSIX interface as a collection of RedLeaf domains. RedLeaf's isolation mechanisms allow us to support the transparent recovery of device drivers. To demonstrate that Rust and fine-grained isolation introduce a practically-acceptable overhead, we develop efficient versions of 10Gbps network and PCIe-attached solid state-disk NVMe device drivers that match the performance of carefully-optimized kernel-bypass device drivers used in modern network and storage processing frameworks.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8790">Vikram Narayanan</person>
          <person id="8928">Anton Burtsev</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.microkernel/vnarayanan.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/vnarayanan.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-vnarayanan:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-vnarayanan:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12975.php">Submit feedback</link>
        </links>
      </event>
      <event id="13006">
        <start>15:45</start>
        <duration>00:45</duration>
        <room>D.microkernel</room>
        <slug>gparmer</slug>
        <title>The Composite Component-Based OS</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Composite CBOS is in many ways a traditional micro-kernel. Services and policies are implemented at user-level, the kernel focuses on fast IPC, and it uses a strong capability-based access control mechanism. It has historically focused on being a research laboratory for strange features including a thread-migration-based IPC, user-level scheduling of system-level threads, user-level definition of capability policies, a wait-free kernel that scales linearly with increasing cores, and temporal capabilities to coordinate between untrusting schedulers. It also scales down and supports paravirtualized RTOSes on microcontrollers (with on the order of 64KiB SRAM, between 16 and 200 Mhz, and MPUs). Composite represents a design that deviates from the L4 lineage in some interesting ways. In this talk, we'll discuss the design with a focus on how the system provides the challenging combination of predictability, performance, and scalable parallelism.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8816">Gabe Parmer</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/gparmer/attachments/slides/4875/export/events/attachments/gparmer/slides/4875/Presentation_v1_slides.pdf">The Composite Component-Based OS</attachment>
        </attachments>
        <links>
          <link href="https://composite.seas.gwu.edu/">Composite webpage</link>
          <link href="https://www2.seas.gwu.edu/~gparmer/pubs.html">Composite publications</link>
          <link href="https://www.github.com/gwsystems/composite">Composite source</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/gparmer.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/gparmer.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-gparmer:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-gparmer:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13006.php">Submit feedback</link>
        </links>
      </event>
      <event id="12523">
        <start>16:30</start>
        <duration>00:35</duration>
        <room>D.microkernel</room>
        <slug>seydam</slug>
        <title>Mitigating Processor Vulnerabilities by Restructuring the Kernel Address Space</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk, I will present a new Spectre/Meltdown mitigation that I have prototyped for the Hedron microhypervisor. This prototype has also been used to quantify the runtime overhead of the proposed mitigation.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Processor-level vulnerabilities, such as Meltdown and Spectre v1/v2, allow attackers in userspace to leak information from the kernel address space. This is particularly devastating for kernel designs where the kernel address space is identical for all processes and thus allows the attacker to break the system's confidentiality boundaries.&lt;/p&gt;

&lt;p&gt;Previous mitigation attempts, such as kernel page-table isolation (formerly KAISER) for Meltdown and various branch predictor/speculation barriers for Spectre v1/v2, introduce costly instructions into performance critical parts of the operating system kernel. Especially mitigations related to the branch predictor are only possible if the CPU vendor has exposed special functionality.&lt;/p&gt;

&lt;p&gt;During the last six months I investigated an alternative mitigation strategy on the kernel design level that shows good mitigation properties, but adds negligible runtime overhead. This alternative mitigation involves moving process-related information in the kernel into a process-local part of the kernel address space. A userspace attacker that can infer the content of its associated kernel page table can thus only read information about its own process. Switching between these kernel address spaces is done as part of the normal address space switch when a thread in a different process is scheduled and thus comes with no additional cost.&lt;/p&gt;</description>
        <persons>
          <person id="8588">Sebastian Eydam</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/seydam/attachments/slides/4837/export/events/attachments/seydam/slides/4837/fosdem_pres_seydam.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/amphi/hedron/tree/new-mitigation-prototype">Sources on Github</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/seydam.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/seydam.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-seydam:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-seydam:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12523.php">Submit feedback</link>
        </links>
      </event>
      <event id="12970">
        <start>17:05</start>
        <duration>00:55</duration>
        <room>D.microkernel</room>
        <slug>bgarst</slug>
        <title>Unhackable across 30 Years, End in Sight</title>
        <subtitle/>
        <track>Microkernel and Component-based OS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As tech lead on commercial UNIX at Bell Labs, an opportunity arose in 1988 to write a nano-kernel to end all nano-kernels, complete with an unhackable boot requirement. It was clear that a cryptographically secure chip level boot assistance was required, which guided subsequent patented ECC work at NeXT and Apple. Post Apple, in a “Social Purpose” company of his own, work has continued to fully realize this dream. The 1988 nanokernel had no threads and delivered messages across upcall channels to a thread simulation, yet that was unsatisfactory. The social element of phishing etc. is now the most feared secuirity breach, and in new work, discussed, the complete solution space is described, in the first half. New hardware is underway, solving such issues as weak memory models.&lt;/p&gt;

&lt;p&gt;In the second half of the talk, key lockless queuing primitives are discussed that form the basis fo a multi-core actor runtime (MART) to subsume most if not all duties of the executive. Far richer than a hypervisor, the executive manages memory in new manners, in a memory safe programmer nature. In practice, a single core actor runtime (START), running across 32, 64 arm, x86, and extensa cpu architectures is available. The language and runtime are destined to the Open Source world, unless the larger project, TheDew, makes file systems and databases obsolete in its first rollout, which will include unhackable identity. Ask: Join us!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8773">Blaine Garst</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/bgarst/attachments/slides/4851/export/events/attachments/bgarst/slides/4851/2022_01_14UnhackableV1.pdf">Unhackable: 30 Years, End In SIght</attachment>
        </attachments>
        <links>
          <link href="https://www.platformsecuritysummit.com/2019/speaker/chen/">XBox One story</link>
          <link href="https://www.bunniestudios.com/blog/?p=5706">Unhackable Hardware?</link>
          <link href="http://www.dalnefre.com/wp/humus/">humus - Dale Schumacher</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/bgarst.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.microkernel/bgarst.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#microkernel-bgarst:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#microkernel-bgarst:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12970.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.monitoring">
    </room>
    <room name="D.mozilla">
      <event id="12595">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>D.mozilla</room>
        <slug>mozilla_suggestions_community</slug>
        <title>Suggestions for a Stronger Mozilla Community</title>
        <subtitle>Personal Thoughts and Ideas for Possible Improvements</subtitle>
        <track>Mozilla</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As one of the earliest large FLOSS projects, Mozilla had a strong and growing community of volunteer contributors for a long time. Then, a lot of factors leading up to today led to the environment changing very significantly, and today's community has some good groups in some areas, but not the kind of connected movement that existed in those earlier times. The speaker has been part of all of that development, starting off as a volunteer very early in the project, working on Mozilla staff for a few years in between, and still being part of the volunteer community in recent years. From that point of view, he'll bring up some ideas and suggestions on how this community can become stronger and grow again, so that a significant voice for the Open Web and the Mozilla Manifesto will hopefully be out there also in the future.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="142">Robert Kaiser</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://slides.kairo.at/fosdem2022/">Slides</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_suggestions_community.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_suggestions_community.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-mozilla_suggestions_community:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-mozilla_suggestions_community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12595.php">Submit feedback</link>
        </links>
      </event>
      <event id="12547">
        <start>11:30</start>
        <duration>00:30</duration>
        <room>D.mozilla</room>
        <slug>mozilla_sentence_collector</slug>
        <title>Collecting Sentences for Common Voice</title>
        <subtitle>Collecting Sentences through different means to allow others to record voices for them</subtitle>
        <track>Mozilla</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Common Voice is a project to help make voice recognition open and accessible to everyone. To create this data set Common Voice allows volunteers to record defined sentences to contribute their voice. A good data set needs a lot of recordings, and therefore we need to have a lot of sentences to be read out aloud. In this talk Michael will introduce the audience to several ways we are collecting these sentences and goes into more technical detail for these mechanisms. This talk will also feature an intro to Common Voice at the beginning.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8430">Michael Kohler</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mozilla_sentence_collector/attachments/slides/4866/export/events/attachments/mozilla_sentence_collector/slides/4866/sentence_collection_slides.pdf">Sentence Collection Slides</attachment>
        </attachments>
        <links>
          <link href="https://commonvoice.mozilla.org">Common Voice</link>
          <link href="https://commonvoice.mozilla.org/sentence-collector/">Sentence Collector</link>
          <link href="https://github.com/Common-Voice/cv-sentence-extractor">Sentence Extractor</link>
          <link href="https://github.com/common-voice/common-voice/">Common Voice Repository</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_sentence_collector.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_sentence_collector.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-mozilla_sentence_collector:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-mozilla_sentence_collector:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12547.php">Submit feedback</link>
        </links>
      </event>
      <event id="12612">
        <start>12:00</start>
        <duration>00:30</duration>
        <room>D.mozilla</room>
        <slug>mozilla_babiaxr</slug>
        <title>BabiaXR: Virtual Reality Data Visualizations for the browser</title>
        <subtitle/>
        <track>Mozilla</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;BabiaXR is a set of FOSS modules for VR (virtual reality) data visualization for the browser. BabiaXR is based on A-Frame and Threejs, with the goal of making it very easy to create different kinds of data visualizations (bar charts, bubble charts, cities, ...), by exploiting the power of WebVR and regular web front-end programming. In this talk, I will do an overview of BabiaXR, showing different examples of different common visualizations. Then, I will focus on showing how we use the city metaphor to represent a popular FOSS project, showing its evolution over time. The talk will show examples (in VR) that the public can try on the fly.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;There are plenty of tools that can analyze data in many ways, but just a few of them try to visualize this data beyond 2D. This is the goal of BabiaXR, a set of front-end modules for 3D VR (virtual reality) data visualization. The visualization part of BabiaXR is based on A-Frame and Threejs, providing a collection of components for creating different kinds of visualizations. Among them there are common ones like bar charts, pie charts, bubbles chart, but now we are moving beyond that, exploring new ways of showing data in 3D. For example, we are working on representing software projects using the city metaphor, showing the evolution of the project as the evolution of a city, with building corresponding to the different files. In this talk, I will do an overview of BabiaXR, showing different examples of the power of WebVR and A-Frame with different visualizations. Then, I will analyze a city corresponding to a well-known FOSS project, showing its evolution in different time snapshots and explaining how the code evolves as the city does. Moreover, there will be examples that the public of the room can try on the fly in their devices, and I will bring a set of two different VR devices to show the examples in an immersive environment after the talk.&lt;/p&gt;

&lt;p&gt;As A-Frame was developed in part by Mozilla developers, and it is used in some Mozilla services (such as Hubs), I think that it is interesting to show what kind of things, beyond games, can be done with this awesome framework, specifically, related to data analysis and new different ways of data visualization, like the cities that you can build with BabiaXR.&lt;/p&gt;</description>
        <persons>
          <person id="4886">David Moreno-Lumbreras</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mozilla_babiaxr/attachments/slides/4902/export/events/attachments/mozilla_babiaxr/slides/4902/slides.pdf"/>
        </attachments>
        <links>
          <link href="https://babiaxr.gitlab.io/">Main Page</link>
          <link href="https://babiaxr.gitlab.io/aframe-babia-components/">Live Demo examples</link>
          <link href="https://gitlab.com/babiaxr/aframe-babia-components">BabiaXR main repository</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_babiaxr.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_babiaxr.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-mozilla_babiaxr:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-mozilla_babiaxr:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12612.php">Submit feedback</link>
        </links>
      </event>
      <event id="12347">
        <start>12:30</start>
        <duration>00:30</duration>
        <room>D.mozilla</room>
        <slug>mozilla_cv_project_app</slug>
        <title>"CV Project app": How an Android app can change the Mozilla Common Voice project</title>
        <subtitle/>
        <track>Mozilla</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Talk about the "CV Project" app, which is a native Android app to contribute to Mozilla Common Voice via the smartphone.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8474">Saverio Morelli</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mozilla_cv_project_app/attachments/slides/4935/export/events/attachments/mozilla_cv_project_app/slides/4935/Slides">Slides for the CV Project talk</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_cv_project_app.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_cv_project_app.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-mozilla_cv_project_app:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-mozilla_cv_project_app:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12347.php">Submit feedback</link>
        </links>
      </event>
      <event id="12684">
        <start>13:00</start>
        <duration>00:45</duration>
        <room>D.mozilla</room>
        <slug>mozilla_support</slug>
        <title>Mozilla Support: 24, 7, 365</title>
        <subtitle/>
        <track>Mozilla</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;An overview of the Mozilla Support team and how a group of contributors spread all across the world work together to help users of Firefox, Thunderbird and other Mozilla apps.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8684">Paul Wright</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_support.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_support.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-mozilla_support:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-mozilla_support:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12684.php">Submit feedback</link>
        </links>
      </event>
      <event id="12608">
        <start>13:45</start>
        <duration>00:15</duration>
        <room>D.mozilla</room>
        <slug>mozilla_thunderbird_2022</slug>
        <title>Thunderbird in 2022</title>
        <subtitle>Highlights of Thunderbird plans for this year.</subtitle>
        <track>Mozilla</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk will go through recent highlights of Thunderbird development. What are we working on for the mid 2022 release.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7357">Magnus Melin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.thunderbird.net">Thunderbird website</link>
          <link href="https://developer.thunderbird.net">Developer documentation</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_thunderbird_2022.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_thunderbird_2022.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-mozilla_thunderbird_2022:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-mozilla_thunderbird_2022:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12608.php">Submit feedback</link>
        </links>
      </event>
      <event id="12597">
        <start>14:00</start>
        <duration>00:45</duration>
        <room>D.mozilla</room>
        <slug>mozilla_language_common_voice</slug>
        <title>How to Start a Language on Mozilla Common Voice?</title>
        <subtitle>A case study for under-resourced Turkish Language</subtitle>
        <track>Mozilla</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;On Mozilla Common Voice, as of December 2021, there are 154 locales, but only 87 fulfilled the requirements to collect voices, where 27 of them are fairly new. In this two-part presentation, we want to give some starting points for the new language communities, share our accumulated knowledge in the last year while working on the under-resourced Turkish language, with initial training results.&lt;/p&gt;

&lt;p&gt;The presentation includes the following topics: Resources on Mozilla Common Voice, how to analyze your dataset, how to set goals, how to design a social media campaign, what tools you can use, Google Colabs, Coqui STT, and our roundups on training Common Voice Turkish Dataset v1 - v7.0, all with our successes and failures as Common Voice Turkish Volunteers group as lessons learned.&lt;/p&gt;</abstract>
        <description>&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Errata&lt;/strong&gt;: In the video "checkpoint" is mistakenly written/spoken as "breakpoint", these are corrected in the slides.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Addendum&lt;/strong&gt;: Our dataset analysis and training results for the Common Voice v8.0 dataset have been added as new slides and video.&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="8651">Bülent Özden</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mozilla_language_common_voice/attachments/slides/5033/export/events/attachments/mozilla_language_common_voice/slides/5033/common_voice_turkish_slides.pdf">Common Voice Turkish - Video Slides (PDF)</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mozilla_language_common_voice/attachments/slides/5034/export/events/attachments/mozilla_language_common_voice/slides/5034/common_voice_turkish_slides.pptx">Common Voice Turkish - Video Slides (PPTX)</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mozilla_language_common_voice/attachments/slides/5035/export/events/attachments/mozilla_language_common_voice/slides/5035/common_voice_turkish_slides_v8_update.pdf">Common Voice Turkish - v8.0 update (PDF)</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mozilla_language_common_voice/attachments/slides/5036/export/events/attachments/mozilla_language_common_voice/slides/5036/common_voice_turkish_slides_v8_update.pptx">Common Voice Turkish - v8.0 update (PPTX)</attachment>
        </attachments>
        <links>
          <link href="https://commonvoice.mozilla.org/en">Mozilla Common Voice</link>
          <link href="https://commonvoice.mozilla.org/sentence-collector">CV - Sentence Collector</link>
          <link href="https://discourse.mozilla.org/c/voice/239">CV - Discourse</link>
          <link href="https://pontoon.mozilla.org/projects/common-voice/">CV - Pontoon (UI translation)</link>
          <link href="https://discourse.mozilla.org/c/voice/tr/610">CV - Turkish sub-Discourse</link>
          <link href="https://chat.mozilla.org/#/room/#common-voice:mozilla.org">CV - Matrix chat</link>
          <link href="https://github.com/common-voice">CV - Github repositories</link>
          <link href="https://common-voice.github.io/community-playbook/">CV - Community Playbook</link>
          <link href="https://github.com/ftyers/commonvoice-utils">Common Voice Utils repo</link>
          <link href="https://github.com/ftyers/commonvoice-docker">Common Voice Docker repo</link>
          <link href="https://coqui.ai/">Coqui Website</link>
          <link href="https://github.com/HarikalarKutusu/common-voice-tr-experiments">Github Repo of the Colab Notebooks used in experiments presented</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_language_common_voice.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_language_common_voice.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-mozilla_language_common_voice:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-mozilla_language_common_voice:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12597.php">Submit feedback</link>
        </links>
      </event>
      <event id="12594">
        <start>14:45</start>
        <duration>00:45</duration>
        <room>D.mozilla</room>
        <slug>mozilla_searchfox</slug>
        <title>Searchfox</title>
        <subtitle>Fast code search and indexing</subtitle>
        <track>Mozilla</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Short overview of how Searchfox works, how to use it on other projects (like Igalia is doing with https://webkit-search.igalia.com), planned improvements, and how to contribute to it.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8649">Emilio Cobos Álvarez</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/mozsearch/mozsearch">Main repo</link>
          <link href="https://github.com/mozsearch/mozsearch-mozilla">Mozilla repo configuration</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_searchfox.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_searchfox.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-mozilla_searchfox:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-mozilla_searchfox:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12594.php">Submit feedback</link>
        </links>
      </event>
      <event id="12498">
        <start>15:30</start>
        <duration>01:00</duration>
        <room>D.mozilla</room>
        <slug>mozilla_firefox_dev_101</slug>
        <title>Firefox Desktop Development 101</title>
        <subtitle>How new Firefox developers are onboarded to the code</subtitle>
        <track>Mozilla</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this presentation, Mike Conley walks you through the same onboarding process that new Firefox desktop developers go through to get familiarized with the project. Want to know what Firefox's relationship with Gecko is? What's the relationship between the Firefox and Thunderbird codebases? What does Firefox code even look like? Find out this and more!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8584">Mike Conley</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://docs.google.com/presentation/d/1988IypnODb6BFjO0gM_2En8dtSJUn91g4GtJYoL4SFs/edit?usp=sharing">Slide deck</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_firefox_dev_101.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_firefox_dev_101.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-mozilla_firefox_dev_101:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-mozilla_firefox_dev_101:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12498.php">Submit feedback</link>
        </links>
      </event>
      <event id="12496">
        <start>16:30</start>
        <duration>00:20</duration>
        <room>D.mozilla</room>
        <slug>mozilla_foxfooding</slug>
        <title>Introduction to Foxfooding</title>
        <subtitle>A story about how Mozillians test and give feedback for products before release</subtitle>
        <track>Mozilla</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Foxfooding is Mozilla's internal dogfooding process that includes both employees and community members. The goal is to encourage all Mozillians to give early feedback about the products that we are shipping, in an open and collaborative way.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8581">Konstantina Papadea</person>
          <person id="8916">Krupa Raj</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mozilla_foxfooding/attachments/slides/4867/export/events/attachments/mozilla_foxfooding/slides/4867/slides.pdf">Foxfooding Slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_foxfooding.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mozilla/mozilla_foxfooding.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mozilla-mozilla_foxfooding:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mozilla-mozilla_foxfooding:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12496.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.mysql">
      <event id="12801">
        <start>14:00</start>
        <duration>00:30</duration>
        <room>D.mysql</room>
        <slug>mysql_binlogs_encryption</slug>
        <title>Encrypting binary (and relay) logs in MySQL</title>
        <subtitle/>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Keeping your data secure is an important task of the DBA. We protect our servers, encrypt filesystems and/or datafiles. But what about log files? And especially log files that contain actual data such as the MySQL binary or relay logs. These are technically called log files but they contain the actual data going through your MySQL systems for replication purposes. I will describe how you can enable and use them and also, in case of disaster, how you can recover your encrypted binary logs so you can use them for point in time recovery.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4684">Matthias C</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mysql_binlogs_encryption/attachments/slides/5010/export/events/attachments/mysql_binlogs_encryption/slides/5010/FOSDEM_2022_Encrypting_binary_and_relay_logs_in_MySQL.pdf">Encrypting binary (and relay) logs in MySQL</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_binlogs_encryption.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_binlogs_encryption.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_binlogs_encryption:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_binlogs_encryption:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12801.php">Submit feedback</link>
        </links>
      </event>
      <event id="13070">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.mysql</room>
        <slug>mysql_hash_join</slug>
        <title>Hash join in MySQL 8.0</title>
        <subtitle/>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Hash join was introduced in MySQL 8.0.18 and was presented for the first time at FOSDEM 2020.  Since then, the performance of hash join has been improved, and I will present results that show this.  We will also discuss what kind of queries benefit from hash join, what you need to do for hash join to be used, and how to tune your system for optimal hash join performance.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3321">Øystein Grøvlen</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mysql_hash_join/attachments/slides/5114/export/events/attachments/mysql_hash_join/slides/5114/hashjoin_fosdem22.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_hash_join.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_hash_join.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_hash_join:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_hash_join:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13070.php">Submit feedback</link>
        </links>
      </event>
      <event id="13091">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.mysql</room>
        <slug>proxysql2021</slug>
        <title>ProxySQL 2021 Dev Submit</title>
        <subtitle/>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;ProxySQL has proven itself as the de-facto standard reverse proxy for MySQL, yet, we are always looking for new features and improvements. During this past year starting with v2.1.0, four new major ProxySQL versions were released, and with them new features of all sorts were introduced, ranging from protocol changes, authentication improvements, clustering improvements, new monitoring features (for Galera, Group Replication, Aurora AWS) to DDOS protection. Join us for a deeper dive on the details of these (and more) new features, what they have to offer and how you can get the most out of them.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8845">Javier Jaramago Fernández</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/proxysql2021.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/proxysql2021.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-proxysql2021:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-proxysql2021:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13091.php">Submit feedback</link>
        </links>
      </event>
      <event id="13087">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.mysql</room>
        <slug>mysql_backup_restore</slug>
        <title>Backup/Restore tools performance comparison</title>
        <subtitle/>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Backup and restore methods are concepts that everyone knows the importance of. Over the years, open-source tools emerged like MyDumper, Xtrabackup, and Mariabackup. Also, with MySQL 8 new shell, new utils for dump and restore were introduced as well.&lt;/p&gt;

&lt;p&gt;In this presentation, we are going to compare the newest backup/restore methods with the most used ones. We will see how parallelization can influence the speed of backup and restore process and also how the compression algorithms can influence the performance.&lt;/p&gt;

&lt;p&gt;In this talk, we will compare mysqldump, mydumper/myloader, mysqlpump, MySQL Shell utils, and Xtrabackup.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6401">Vinicius Grippa</person>
          <person id="8926">Jean Da Silva</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_backup_restore.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_backup_restore.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_backup_restore:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_backup_restore:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13087.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.network">
    </room>
    <room name="D.nim">
      <event id="12796">
        <start>12:30</start>
        <duration>00:35</duration>
        <room>D.nim</room>
        <slug>nim_concurrency</slug>
        <title>Nim concurrency</title>
        <subtitle>Past, Present and Future</subtitle>
        <track>Nim Programming Language</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This is a talk about Nim's concurrency mechanisms, how the old things worked, how the current things work and what the future holds.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7150">Andreas Rumpf (Araq)</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.nim/nim_concurrency.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_concurrency.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#nim-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-nim_concurrency:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#nim-nim_concurrency:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12796.php">Submit feedback</link>
        </links>
      </event>
      <event id="12844">
        <start>13:05</start>
        <duration>00:35</duration>
        <room>D.nim</room>
        <slug>nim_ngmicrocontrollers</slug>
        <title>Next generation micro-controller programming</title>
        <subtitle>Zero-cost abstractions for better embedded programming</subtitle>
        <track>Nim Programming Language</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk builds on my previous talks about micro-controller programming in Nim, and my talk on writing a keyboard firmware from scratch in Nim. It outlines how a Nim ecosystem for microcontrollers can be built with zero-cost abstractions which means that the resulting code is almost exactly the same size as pure C code (no Arduino). All this while keeping an interface which is much nicer than anything you'd find in C, maybe even better than that of high-level microprocessor coding frameworks like MicroPython and TinyGo.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5879">Peter Munch-Ellingsen</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.nim/nim_ngmicrocontrollers.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_ngmicrocontrollers.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#nim-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-nim_ngmicrocontrollers:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#nim-nim_ngmicrocontrollers:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12844.php">Submit feedback</link>
        </links>
      </event>
      <event id="12538">
        <start>13:40</start>
        <duration>00:40</duration>
        <room>D.nim</room>
        <slug>nim_libvfio</slug>
        <title>LibVF.IO: vGPU &amp; SR-IOV on Consumer GPUs using Nim</title>
        <subtitle>LibVF.IO is bringing vGPU functionality that's historically been restricted to the enterprise datacenter segment to normal consumer GPUs running free open source desktop operating systems.</subtitle>
        <track>Nim Programming Language</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I'd like to showcase LibVF.IO's new LIME Runtime feature (Lime Is Mediated Emulation) and do a deep dive on open source vGPU technology in general.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Some of the topics I would like to cover are the VFIO-Mdev API, the differences between Virgl vs. Hardware GPU virtualization (SR-IOV) vs. Software GPU virtualization (soft Mdev), various common GPU driver virtualization implementations (Intel i915, AMD GPU-IOV Module, and Nvidia), then talk about the benefits of hardware virtualization of GPUs for projects like Qubes OS and the ongoing effort to run LibVF.IO with Xen for use with Qubes. I'd like to share LibVF.IO's vision to bring vGPU SR-IOV functionality out of the datacenter and to most consumer devices running free software. Finally I'd like to explore what a world might look like if we're successful in bringing the benefits vGPU SR-IOV functionality to every day people running free software (native performance backwards compatibility via virtualization, hardware isolation, &amp;amp; workload balancing).&lt;/p&gt;</description>
        <persons>
          <person id="8616">Arthur Rasmusson</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://libvf.io">The link to LibVF.IO's full source code.</link>
          <link href="https://arccompute.com/blog/libvfio-commodity-gpu-multiplexing/">LibVF.IO setup guide.</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_libvfio.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_libvfio.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#nim-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-nim_libvfio:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#nim-nim_libvfio:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12538.php">Submit feedback</link>
        </links>
      </event>
      <event id="12839">
        <start>14:20</start>
        <duration>00:40</duration>
        <room>D.nim</room>
        <slug>nim_polymorph</slug>
        <title>Polymorph: a compile time approach to entity-component-systems in Nim</title>
        <subtitle>Queryless ECS: removing runtime overhead by orienting around systems</subtitle>
        <track>Nim Programming Language</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The entity-component-system pattern (ECS) is popular in game development for its ability to model complex dynamic simulations with mechanical sympathy, in an environment where microseconds matter.&lt;/p&gt;

&lt;p&gt;The pattern is focused on run time composition. Entities are mutable sets of component data types, and systems run for entities with specific sets of components. Many ECS frameworks are oriented around components or entities, and systems use run time queries or filters to match their component data requirements against the live state.&lt;/p&gt;

&lt;p&gt;In this talk, a system oriented ECS is presented which removes all run time work for systems by storing execution state in the systems themselves. Changing an entity's components leverages Nim's static typing and powerful AST macros to precalculate affected systems and generate pared down system state changes.&lt;/p&gt;

&lt;p&gt;The result is statically defined and intrinsically optimised to the user's system/component design, allowing efficient embedded event loops through to complex interactive simulations.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8756">Ryan Lipscombe</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/rlipsc/polymorph">The Polymorph ECS</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_polymorph.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_polymorph.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#nim-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-nim_polymorph:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#nim-nim_polymorph:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12839.php">Submit feedback</link>
        </links>
      </event>
      <event id="12849">
        <start>15:00</start>
        <duration>00:45</duration>
        <room>D.nim</room>
        <slug>nim_potatozombies</slug>
        <title>Potato Zombies</title>
        <subtitle>Helping a 6 year old build a 3D game using Enu and Nim</subtitle>
        <track>Nim Programming Language</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;&lt;a href="https://github.com/dsrw/enu"&gt;Enu&lt;/a&gt; is a 3D live coding environment that can be used for education, exploration, and light game development. It uses a simple, logo-style Nim DSL, and aims to be accessible to as many people as possible, even those who may not yet be able to read or type. It's still fairly immature, but will eventually be suitable for implementing simple multiplayer 3D games.&lt;/p&gt;

&lt;p&gt;In this presentation, Enu's creator will walk through creating a simple 3D game with his 6 year old son using Enu 0.2.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8598">Scott Wadden</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.nim/nim_potatozombies.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_potatozombies.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#nim-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-nim_potatozombies:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#nim-nim_potatozombies:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12849.php">Submit feedback</link>
        </links>
      </event>
      <event id="12840">
        <start>15:45</start>
        <duration>00:45</duration>
        <room>D.nim</room>
        <slug>nim_pararules</slug>
        <title>Pararules</title>
        <subtitle>A Nim rules engine for reactive programs and games</subtitle>
        <track>Nim Programming Language</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Reactive programming has become commonplace in many kinds of software, while others, including games, have been slow to adopt it. There is an idea stretching back to the 70s that enables reactive programming in an extremely general way: rules engines. This talk will demonstrate pararules, a breakthrough rules engine for Nim. It will demonstrate how games and other software can define their entire logic as a series of independent rules, and how it decouples your data much like (but more powerful than) an entity component system. It will show why this kind of library is only practical to implement in a language with a Lisp-like macro system such as Nim's.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8758">Zach Oakes</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/paranim/pararules">pararules github repo</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_pararules.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_pararules.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#nim-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-nim_pararules:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#nim-nim_pararules:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12840.php">Submit feedback</link>
        </links>
      </event>
      <event id="12770">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.nim</room>
        <slug>nim_hpcfrompythontonim</slug>
        <title>HPC from Python to Nim</title>
        <subtitle>A preliminary introduction to performance optimization</subtitle>
        <track>Nim Programming Language</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Numpy is considered the go-to library for fast performant python scientifc computing, as it is a heavily optimized scientific computing library written in C. But is it really that fast (spoiler: yes, but not when used with python)? In this talk, I will be covering a real-world example in the domain of genetics, and demonstrating how I was able to out-perform numpy code running on my intel-7700k machine with a raspberry pi running code from the Nim programming language!&lt;/p&gt;

&lt;p&gt;I will also be providing optimization tips for speeding up your code, with a focus on comparing python with the Nim programming language.&lt;/p&gt;

&lt;p&gt;The talk can be roughly divided into the following sections:&lt;/p&gt;

&lt;p&gt;Part 1 (32 min) - Introduction to myself. Describing a computationally expensive problem that I have experienced when working with Python.
- My background is in data science and biology
- Biologists tend to work with large datasets
- One common problem we face is preprocessing of large amounts of data. A common technique used here using distance calculations
- Why I decided to learn a different language
Part 2 (1 min) - High level introduction to Nim
- Nim is a statically compiled programming language
- Etc...
Part 3 (10 min) - Going through step-by-step on how to write performance optimal code with Nim. Describing common performance pitfalls that Python users may not be aware of.
- Inlining
- Using the type system to your advantage
- Taking advantage of domain knowledge
- Multi-threading (openmp)
- Bounds checking
- Compiler flags
- Mathematical and algorithmic optimizations
Part 4 (3 min) - Benchmarks and closing statement
- Show benchmark comparing the naive python numpy implementation with the highly optimized Nim one
- Top tips to keep in mind when writing high performance code.&lt;/p&gt;

&lt;p&gt;Please note: the purpose of this talk isn't to be an exploration of some new state-of-the-art way of doing performance optimization or some relatively unknown optimization techniques. This is a general introduction for people hoping to use Nim for HPC that are coming from Python. Lots of emphasis will be put comparing the two languages.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8733">Ayman Al Baz</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/ayman-albaz/distances">Some code-snippets from my distances library will be shown in the talk</link>
          <link href="https://docs.google.com/presentation/d/1HTgsPkMyvVHmfS_GLrrw-zkscwhJwmXsPYzSNXB-DSs/edit?usp=sharing">Presentation Link</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_hpcfrompythontonim.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_hpcfrompythontonim.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#nim-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-nim_hpcfrompythontonim:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#nim-nim_hpcfrompythontonim:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12770.php">Submit feedback</link>
        </links>
      </event>
      <event id="12500">
        <start>17:00</start>
        <duration>00:40</duration>
        <room>D.nim</room>
        <slug>nim_metaprogramming</slug>
        <title>Nim Metaprogramming in the real world</title>
        <subtitle/>
        <track>Nim Programming Language</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Metaprogramming in Nim is very powerful. But why would you use it? How is it used in the real world? We will explore the "power levels": starting from generics, continuing to templates and finally arriving at macros.&lt;/p&gt;

&lt;p&gt;We will first look at generics usage in VMath (Vector Math Library) and Jsony (JSON Parsing Library). Then we will continue on to templates and how they are used in VMath and Windy. Finally we will look macros, the top of the "power levels", and how they are used in Shady (a Nim to GLSL compiler) and Genny (Generates bindings for Nim libraries).&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8587">Andre von Houck</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.nim/nim_metaprogramming.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.nim/nim_metaprogramming.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#nim-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#nim-nim_metaprogramming:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#nim-nim_metaprogramming:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12500.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.research">
      <event id="13562">
        <start>10:00</start>
        <duration>00:05</duration>
        <room>D.research</room>
        <slug>open_research_welcome</slug>
        <title>Welcome to the Open Research Tools and Technologies devroom</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Open Research Tools and Technologies devroom managers welcome words announcing the schedule.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This years the Open Research devroom schedule has been organized in thematic panels:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Academics developing software testimonies panel&lt;/li&gt;
&lt;li&gt;Visual inquiries panel&lt;/li&gt;
&lt;li&gt;Policies panel&lt;/li&gt;
&lt;li&gt;Artificial Intelligence Panel&lt;/li&gt;
&lt;li&gt;Open Hardware Panel&lt;/li&gt;
&lt;li&gt;Standards panel&lt;/li&gt;
&lt;li&gt;Knowledge management communities panel&lt;/li&gt;
&lt;li&gt;Open Data Panel&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="2865">Paul Girard</person>
          <person id="3641">Matthieu Totet</person>
          <person id="4280">Mathieu Jacomy</person>
          <person id="7525">Célya Gruson-Daniel</person>
          <person id="7635">Yo Yehudi</person>
          <person id="7686">Maya Anderson-González</person>
          <person id="8471">Sara Petti</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.research/open_research_welcome.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_welcome.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_welcome:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_welcome:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13562.php">Submit feedback</link>
        </links>
      </event>
      <event id="12647">
        <start>10:05</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_heurist</slug>
        <title>From pipe dreams and waste to functional accretion: building a capable infrastructure for the Digital Humanities</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This presentation is about the development and trajectory of Heurist (HeuristNetwork.org), a shared, integrated, extensible data infrastructure (model, build, manage, analyse, visualise, share, publish via integrated CMS) for Humanities research capable of handling the needs of many heterogeneous projects on a single standalone service*, with optional integration across multiple servers by a coordinating index (itself based on Heurist).&lt;/p&gt;

&lt;p&gt;Humanities data are interesting (both technically and to the public). They are rich in text, images, objects, people and events, heterogeneous, eminently linkable and sparse-matrix. Personal computers, the internet and other accessible technologies have spawned an exploding field (or fad?) known as Digital Humanities (DH), and opened exciting new horizons for research and public engagement.&lt;/p&gt;

&lt;p&gt;However, this technological turn has created many problems for a poorly funded research culture with 1-3 year grant funding cycles - choice of appropriate technology, finding and retaining technical staff, initial and ongoing costs, sustainability ... The outcome is often least-effort and inadequate technology (eg. spreadsheets) or ad hoc development, incomplete functionality, maintenance nightmares, data silos and rapid end-of-funding decay; only rich or statutory organisations can maintain a multi-component system for long. Heurist aims to overcome these problems by mutualised Open Source development, schemas stored as editable data rather than fixed structures, demand-driven priority development, and free centralised services and maintenance.&lt;/p&gt;

&lt;p&gt;In this presentation I will outline the evolution of our development process, from haphazard experimentation and many costly unused features (2005 - 2009) to a coherent, stable but evolving structure and Extreme Programming (aka living dangerously!), driven by immediate user requirements and incremental daily interface refinement. I will outline some of the fundamental principles we use to maintain backwards compatibility, stability, rapid development and low cost of maintenance for such a complex beast and for so many projects, on a self-funding staff of just 3 FTE. I also hope to attract some technical collaborators, as most of our users are (by design) non-technical.&lt;/p&gt;</abstract>
        <description>&lt;ul&gt;
&lt;li&gt;We maintain a central index and two free services (based in Australia and France), plus some institution-based servers,  currently supporting a couple of hundred research projects in different fields, ranging from doctoral students to networks of researchers.&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="8596">Ian Johnson</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://HeuristNetwork.org">Heurist project web site</link>
          <link href="https://heuristplus.sydney.edu.au/heurist/startup/">Database creation page</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_heurist.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_heurist.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_heurist:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_heurist:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12647.php">Submit feedback</link>
        </links>
      </event>
      <event id="12529">
        <start>10:25</start>
        <duration>00:15</duration>
        <room>D.research</room>
        <slug>open_research_prospero</slug>
        <title>Code Liberation and Software Sustainability</title>
        <subtitle>The Prospero Experience</subtitle>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Developed from 1995 onward, Prospero is a framework for longitudinal analysis of text corpora. Based on dictionaries and semi-automatic classification, it mainly allows its user to combine approaches of statistical computation, co-occurrence network and search for nested patterns. Inspired by pragmatic sociology, it focuses on the multiple forms of expression and argumentation used by actors, on language regimes and on the identification of transformations occurring in the research case. Initially distributed commercially, then from 2011, by the Doxa association,  as shareware under a non-profit and ethical charter, it is now hosted by the Corpora association and developed under the aGPLV3 CECILL variant Affero compliant license.&lt;/p&gt;

&lt;p&gt;In this presentation, we will discuss more specifically the question of the permanence of a research-targeted software approach, through its evolution over almost 30 years. During this period, evolving expectations and technical developments have led to a client/server step (which remained in the prototype stage) and now to the transition to SaaS. Based on this experience, we will also discuss the conditions we consider relevant for the durability of the software in a new interconnected phase. The broadening of its audience of users and developers calls for ever greater interoperability, on the technical level, but with an approach that combines non-profit and academic models (with limited resources) and business uses.&lt;/p&gt;

&lt;p&gt;Josquin  Debaz
With a PhD in history of science, he has worked more than 10 years on contemporary controversies in health, environment and energy at GSPR (Pragmatic  and  Reflexive  Sociology  Group, EHESS). He is now developer at Finsit. With F. Chateauraynaud, he published Aux bords de l'irréversible. Sociologie pragmatique des transformations (Paris, Pétra, 2017).&lt;/p&gt;

&lt;p&gt;Waldir Lisboa Rocha
With a degree in Environmental Engineering, he co-founded Luminae, an energy efficiency company, where he served as Chief Operating Officer between 2008 and 2012, before deciding to make a turn in his career and dedicate himself to the Social Sciences. He holds a Master's degree in Sociology from the École des Hautes Études en Sciences Sociales - EHESS, and is currently working on his PhD at the same institution, in which he is focusing on the relations between media, inquiry and democracy. In parallel to his academic research, he has been dedicated to the conception and structuring of Prefigura, an experimental institution, and of Enumera, an operating ecosystem.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8597">Josquin Debaz</person>
          <person id="8903">Waldir Lisboa Rocha</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/open_research_prospero/attachments/slides/5118/export/events/attachments/open_research_prospero/slides/5118/fosdem2022_debaz_lisboaRocha_presentation.pdf">Code Liberation and Software Sustainability</attachment>
        </attachments>
        <links>
          <link href="http://prosperologie.org/">Official Prospero's website</link>
          <link href="https://socioargu.hypotheses.org/">Theorical blog</link>
          <link href="http://prosperologie.org/mrlw/blog/">Christopher Marlowe's blog</link>
          <link href="https://www.zotero.org/groups/4562722/ fosdem_prosperoexperience">Bibliography's webpage</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_prospero.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_prospero.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_prospero:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_prospero:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12529.php">Submit feedback</link>
        </links>
      </event>
      <event id="12546">
        <start>10:40</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_textnets</slug>
        <title>Free Software Development as Observant Participation</title>
        <subtitle>Developing textnets, Studying Digital Cultures</subtitle>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I am a social scientist who mostly teaches and conducts qualitative research, but I am also a programmer. Over the years, I have contributed to a variety of free and open source software projects, and since 2019, I have developed and maintained &lt;code&gt;textnets&lt;/code&gt;, a Python package for text analysis that represents collections of texts as networks of documents and words, providing novel possibilities for the visualization and analysis of texts. In my field, such software development efforts are not usually rewarded, but I have been very fortunate. My academic superiors have been supportive of my endeavors, and a publication in the &lt;em&gt;Journal of Open Source Software&lt;/em&gt; also helped me get official recognition for this work in the standard currency of my field.&lt;/p&gt;

&lt;p&gt;While I developed &lt;code&gt;textnets&lt;/code&gt; to scratch my own itch, I seek to make the package widely available by providing extensive documentation and making it easily installable across multiple platforms. This part of my software development work -- learning the intricacies of version control, package managers, continuous integration testing, and dependency management -- puts me in a position to learn not just about the technical side of coding, but about the social side of the choices developers make. At least in the Python world, the way you learn about what dependencies to use, if any, and how many, is informed by norms more than by technical considerations, and the same is true for much else. By engaging in software development work, I engage in a version of the research method of participant observation -- learning by taking part -- that sociologists have called observant participation -- becoming part of what you want to learn about. In my case, I want to learn not just about software development and its culture and norms, but the wider world of free software, hacker culture, artistic practice based on FOSS tools, and more.&lt;/p&gt;

&lt;p&gt;In my talk, I provide some background to the development of &lt;code&gt;textnets&lt;/code&gt;, give a brief demonstration of the package's features, and finally reflect on my experiences engaging in observant participation as well as some of the insights I have gained and still hope to gain.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8622">John Boy</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://textnets.readthedocs.io">textnets Documentation</link>
          <link href="https://code.jboy.space/fosdem22">demo code repository</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_textnets.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_textnets.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_textnets:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_textnets:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12546.php">Submit feedback</link>
        </links>
      </event>
      <event id="13030">
        <start>11:00</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_testimony</slug>
        <title>Academics developing software testimonies panel</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Discussion panel of three testimonies from academics developing software.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Developing software from academia is not easy. Scholars are meant to teach and write.
Releasing a research software demands much more than writing code.
In this panel discussion, the four speakers will share their thoughts on those challenges. The discussion will benefit from the variety of situations they all bring : a "scholar-analyst" collaborating with a tech team, a team of scholars/engineers and a sociologist who codes alone.
Should scholars leave coding to the professional?
What does open sourcing code brings to the game?
What does maintaining a research software require?
Is coding from academia actually fun or a burden?&lt;/p&gt;

&lt;p&gt;Add your own questions to this list by participating to the live event.
Questions from the audience (chatroom) will be asked to the panel by the moderator.&lt;/p&gt;</description>
        <persons>
          <person id="2865">Paul Girard</person>
          <person id="8596">Ian Johnson</person>
          <person id="8597">Josquin Debaz</person>
          <person id="8622">John Boy</person>
          <person id="8903">Waldir Lisboa Rocha</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_testimony:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_testimony:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13030.php">Submit feedback</link>
        </links>
      </event>
      <event id="12535">
        <start>11:20</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_writing_data_visualization</slug>
        <title>Writing with data visualization</title>
        <subtitle>Multimodal encounters in the making of digital social sciences publications</subtitle>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The writing of web publications mixing data visualization and textual prose opens novel opportunities for connecting evidence, arguments and narrative in social sciences communities. Such a practice poses a variety of challenges in terms of website design and development ; but also and maybe more importantly, it asks for experimenting specific workflows for coordinating a variety of expertises ranging from social sciences disciplines (history, sociology, etc.) to data science, information design and web-related skills. It also reconfigures, for the research processes themselves, the relationships between activities of (data-related) enquiry and (communication-oriented) writing, creating a renewed space for discovery, invention and verification for the data sustaining a given argument or narrative.&lt;/p&gt;

&lt;p&gt;Relying on recent experiments in making collective digital publications grounded in sociology of technology (https://medialab.github.io/carnet-algopresse/#/publication/en) and history of economy (https://medialab.github.io/portic-storymaps-2021/), this talk accounts for the diverse challenges arising from such activities of “data visualization-driven writing”, and some strategies we used to cope with them. It describes and compares the technical and methodological workflows we developed in order to simultaneously develop text, datasets and visualizations, taking into account a variety of aims, data materials, and distribution of skills. Doing so, it advocates for an extended understanding of the notion of “academic writing”, encompassing the practices of writing software, data and diagrams. Such an extended understanding, we argue, is necessary to design and develop writing workflows allowing to foster a multimodal and scientifically productive dialogue between these heterogeneous practices, taking full advantage of the web publication format as a research situation.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6981">Robin De Mourat</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://medialab.github.io/carnet-algopresse/#/publication/en">AI critiques in the press</link>
          <link href="https://medialab.github.io/portic-storymaps-2021/fr/">Commerce multi-échelles autour du port de La Rochelle au XVIIIe siècle</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_writing_data_visualization.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_writing_data_visualization.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_writing_data_visualization:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_writing_data_visualization:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12535.php">Submit feedback</link>
        </links>
      </event>
      <event id="12376">
        <start>11:40</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_livemark</slug>
        <title>Livemark: data presentation framework</title>
        <subtitle>Express everything in Markdown</subtitle>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk will show a new Python tool called Livemark, which is designed for data journalism software education, and documentation writing. Using Livemark, you can collect and present data with interactive tables, charts, and other elements without leaving a text editor. You can also write documentation with live script execution similar to a lightweight version of a Jupiter Notebook. This talk will demo Livemark and will be well-suited for a technical and non-technical audience that is interested in learning about data storytelling.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;No prior knowledge is required although a basic knowledge of Markdown and Python scripting will help understand in-depth sections.&lt;/p&gt;</description>
        <persons>
          <person id="8501">Evgeny Karev</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/open_research_livemark/attachments/slides/4931/export/events/attachments/open_research_livemark/slides/4931/Livemark_FOSDEM22.odp">Slides (ODP)</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/open_research_livemark/attachments/slides/4932/export/events/attachments/open_research_livemark/slides/4932/Livemark_FOSDEM22.pdf">Slides (PDF)</attachment>
        </attachments>
        <links>
          <link href="https://livemark.frictionlessdata.io/">Livemark Website</link>
          <link href="https://covid-tracker.frictionlessdata.io/">COVID-19 Tracker (written in Livemark)</link>
          <link href="https://zoom.us/rec/share/pddeWHKzQ0wSfNMKxytpvMcNu6gN3sfNojsdW6uvndytajjw64fjfBh19tbXFxzI.aj5eZIJSp32vq6LM?startTime=1635487241000">PyData Global Lightening Talk (1:03)</link>
          <link href="https://docs.google.com/presentation/d/1EEqcYIgMzvcRV6BNn2Q-3B4ZVjfzk8ikSdMjXYU5ED8/edit#slide=id.gfaff7fb3b5_0_203">PyData Global Slides</link>
          <link href="https://docs.google.com/presentation/d/16N8s6uCVnkADzOASAsQSgEeRMVqE2bm2wDC-ss8jfGc/edit?usp=sharing">FOSDEM22 Slides</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_livemark.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_livemark.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_livemark:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_livemark:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12376.php">Submit feedback</link>
        </links>
      </event>
      <event id="12374">
        <start>12:00</start>
        <duration>00:15</duration>
        <room>D.research</room>
        <slug>open_research_metaindex</slug>
        <title>MetaindeX and user requirements for a generic catalog application</title>
        <subtitle>Discussing user requirements for a generic cataloger app and its implementation with MetaindeX</subtitle>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We will try to define in this presentation basic user needs for a generic working environment on historical data, discuss then some key technologies and architecture orientations for online open-source application MetaindeX, which intends to fulfill those user requirements. At last, we will illustrate its usage with a real corpus of few thousands French archives from "Archives Nationales", from 16th and 17th century.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This presentation intends to illustrate how MetaindeX opensource application could match a significant part of user needs, especially in the fields of history and humanities.
It first defines an overview of what user requirements could be for a working environment offering a ready-to-use, coding-free, quick and efficient access to advanced exploration, analytics and graphs capabilities over an historical data corpus for the researcher. It supposes that input data has already been collected, cleaned and reconciled, focusing on the exploration and analytics parts of researcher workflow.
In a second part, it then develops those needs through key technologies and architecture choices made for design and development of online open-source application MetaindeX [1].
At last, a sample use-case illustrates user experience and shows some analytics results from the use of MetaindeX and its ecosystem (Kibana and Gephi mainly), based on a set of French archives from 16th and 17th century.&lt;/p&gt;</description>
        <persons>
          <person id="8498">Laurent MILLET-LACOMBE</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://metaindex.fr">Deployed MetaindeX tool</link>
          <link href="https://github.com/laurentmldev/metaindex">Source code</link>
          <link href="http://ceur-ws.org/Vol-2981/paper1.pdf">Original paper</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_metaindex.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_metaindex.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_metaindex:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_metaindex:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12374.php">Submit feedback</link>
        </links>
      </event>
      <event id="13031">
        <start>12:15</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_visual_inquiries</slug>
        <title>Visual inquiries panel</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Panel discussion between speakers of the visual inquiries session.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6981">Robin De Mourat</person>
          <person id="7525">Célya Gruson-Daniel</person>
          <person id="7686">Maya Anderson-González</person>
          <person id="8498">Laurent MILLET-LACOMBE</person>
          <person id="8501">Evgeny Karev</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.research/open_research_visual_inquiries.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_visual_inquiries.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_visual_inquiries:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_visual_inquiries:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13031.php">Submit feedback</link>
        </links>
      </event>
      <event id="12672">
        <start>12:35</start>
        <duration>00:15</duration>
        <room>D.research</room>
        <slug>open_research_cdur</slug>
        <title>On the dissemination/evaluation loop for Research Software</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk explores the interconnections that links Research Software (RS) dissemination and evaluation issues, in the Open Science context, following the guidelines of the CDUR RS assessment protocol.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In our presentation of FOSDEM 2021:&lt;/p&gt;

&lt;p&gt;Free/Open source Research Software production at the Gaspard-Monge Computer Science laboratory - Lessons learnt
&lt;a href="https://archive.fosdem.org/2021/schedule/event/open_research_gaspard_monge/"&gt;https://archive.fosdem.org/2021/schedule/event/open&lt;em&gt;research&lt;/em&gt;gaspard_monge/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;we have analyzed the evolution of several problems that rise when considering the Research Software (RS) production of a laboratory, and we have highlighted several issues that should be addressed to deal with these problems within the Open Science context. Among them we have called to the establishment of sound dissemination and evaluation procedures following the guidelines of the CDUR RS assessment protocol presented in:&lt;/p&gt;

&lt;p&gt;Gomez-Diaz T and Recio T.
On the evaluation of research software: the CDUR procedure. F1000Research 2019, 8:1353
&lt;a href="https://doi.org/10.12688/f1000research.19994.2"&gt;https://doi.org/10.12688/f1000research.19994.2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;CDUR comprises four steps that can be succinctly described as follows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Citation, to deal with correct RS identification,&lt;/li&gt;
&lt;li&gt;Dissemination, to measure good dissemination practices,&lt;/li&gt;
&lt;li&gt;Use, devoted to the evaluation of usability aspects, and&lt;/li&gt;
&lt;li&gt;Research, to assess the impact of the scientific work.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;In this talk we would like to analyze more in depth RS dissemination and  evaluation issues and the above mentioned protocols, referring, in particular, to how these protocols can be adapted to different situations that may appear in evaluation processes such as, for example, different evaluation contexts (career, review...).&lt;/p&gt;

&lt;p&gt;We will also highlight the interconnections that link both dissemination and evaluation issues, as the RS dissemination needs to adjust to evaluation rules and only suitably disseminated RS (maybe in a restricted context) can be evaluated.&lt;/p&gt;

&lt;p&gt;This is a collaboration work with Tomas Recio, Professor at the University Antonio de Nebrija (Madrid).&lt;/p&gt;</description>
        <persons>
          <person id="7704">Teresa Gomez-Diaz</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/open_research_cdur/attachments/slides/5142/export/events/attachments/open_research_cdur/slides/5142/2022_02_05_FOSDEM_TGD_TR_talk.pdf">On the dissemination/evaluation loop for Research Software</attachment>
          <attachment type="video" href="https://fosdem.org/2022/schedule/event/open_research_cdur/attachments/video/5158/export/events/attachments/open_research_cdur/video/5158/2022_02_05_FOSDEM_TGD_talk.mp4">On the dissemination/evaluation loop for Research Software</attachment>
        </attachments>
        <links>
          <link href="https://archive.fosdem.org/2021/schedule/event/open_research_gaspard_monge/">Free/Open source Research Software production at the Gaspard-Monge Computer Science laboratory - Lessons learnt (FOSDEM 2021)</link>
          <link href="https://doi.org/10.12688/f1000research.19994.2">Gomez-Diaz T and Recio T. On the evaluation of research software: the CDUR procedure. F1000Research 2019, 8:1353</link>
          <link href="https://zenodo.org/record/4577066">Gomez-Diaz T and Recio T. Towards an Open Science definition as a political and legal framework: on the sharing and dissemination of research outputs</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_cdur.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_cdur.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_cdur:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_cdur:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12672.php">Submit feedback</link>
        </links>
      </event>
      <event id="12749">
        <start>12:50</start>
        <duration>00:15</duration>
        <room>D.research</room>
        <slug>open_research_french_ecosystem</slug>
        <title>What is special about open source research software and why does it matters?</title>
        <subtitle>Reporting about progresses and challenges from the French ecosystem</subtitle>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;French citizens have a right to request source code developed by their administration.  This includes source code developed by public research labs.  But the research sector has a distinct place in the "public code" landscape.  It produces open source gems like scikit-learn, and many researchers contribute to Free Software, but some source code is never published because public labs are requested to use them as assets for new startups.  This talk will explore this distinct place, the work that has been done in France to promote the publication of research source code and the challenges ahead.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2418">Bastien</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.etalab.gouv.fr/les-pratiques-de-publication-des-codes-sources-dans-lenseignement-superieur-et-la-recherche">French study on researchers practices for open sourcing their source code</link>
          <link href="https://www.ouvrirlascience.fr/second-national-plan-for-open-science/">Second French Plan for Open Science</link>
          <link href="https://code.gouv.fr">The list of French public code </link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_french_ecosystem.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_french_ecosystem.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_french_ecosystem:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_french_ecosystem:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12749.php">Submit feedback</link>
        </links>
      </event>
      <event id="13042">
        <start>13:05</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_policies</slug>
        <title>Policies panel</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Discussion between the Policies panel speakers.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2418">Bastien</person>
          <person id="4280">Mathieu Jacomy</person>
          <person id="7704">Teresa Gomez-Diaz</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.research/open_research_policies.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_policies.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_policies:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_policies:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13042.php">Submit feedback</link>
        </links>
      </event>
      <event id="12445">
        <start>13:25</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_ersilia</slug>
        <title>Ersilia, a hub of AI/ML models for infectious disease research</title>
        <subtitle>Democratizing the access to state-of-the-art data science to researchers worldwide.</subtitle>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Low and Middle Income Countries (LMIC) produce less than 10% of the world's scientific output, largely relying on solutions devised in the Global North, which are often unable to meet the real needs of their population. Data science and machine learning offer a unique opportunity to empower scientists in LMIC by providing cost-effective tools ideal for underfunded settings, but there is a gap in accessibility, infrastructure and skills that must be bridged before these tools can be effectively implemented.
We are developing the Ersilia Model Hub, a FLOSS platform where scientists can browse through a catalogue of AI/ML models and run them without the need to write a single line of code. The platform features both models published in the literature and models developed by us on-demand or in collaboration with researchers in LMIC. The pilot tool focuses on models for drug discovery in infectious and neglected tropical diseases, but we plan to expand to other global health.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The Ersilia Model Hub is currently in alpha development, and it will be released in January 2022, containing 100 models. The MVP must be downloaded in the user’s computers and is accessible via a command-line interface. The models are fetched from our GitHub repository and run locally. They are designed to perform on regular personal computers. In the next phases, an online query system will be implemented for the most popular models, together with a user-friendly interface which does not require use of the CLI.
In addition, we are working towards an end-to-end automated AI/ML pipeline to facilitate the creation and implementation of models trained on specific datasets of relevance to each of our users. This package will also be available early 2022.&lt;/p&gt;</description>
        <persons>
          <person id="8529">Gemma Turon</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/open_research_ersilia/attachments/slides/4854/export/events/attachments/open_research_ersilia/slides/4854/Ersilia_slides">Ersilia, a hub of AI/ML models for neglected diseases</attachment>
        </attachments>
        <links>
          <link href="https://ersilia.io">EOSI webpage, the organization developing the Ersilia Model Hub</link>
          <link href="https://github.com/ersilia-os/ersilia">Main repo containing the code</link>
          <link href="https://ersilia.gitbook.io/ersilia-book/ ">Gitbook with documentation</link>
          <link href="https://youtu.be/yWzO8hIyf-4 ">Presentation delivered at the BOSC2021</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_ersilia.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_ersilia.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_ersilia:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_ersilia:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12445.php">Submit feedback</link>
        </links>
      </event>
      <event id="12598">
        <start>13:45</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_diagnostics_typhoid</slug>
        <title>Improve diagnostics of typhoid through Open Science: An Artificial Intelligence-based technique</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Typhoid fever is one of the severe infectious human diseases in Africa. Out of an estimated 11–21 million cases of typhoid fever and 200,000 deaths occur worldwide each year. Other elements contribute to this situation and particularly in rural areas where patients to doctors ratio is very low, lack of medical facilities and costly tests. There are a number of tests available presently, from molecular to immunological and biochemical to microbiological. However, Users are unsatisfied due to delays in getting test results and Imprecise diagnosis.  Misdiagnosis is usually experienced since most health care facilities use only Widal test without confirmation of results with a second test method. In addition, the diagnosis of Typhoid involves several levels of uncertainties. Patients cannot tell exactly how they feel, doctors and nurses cannot tell exactly what they observe.  There is therefore, an urgent need to develop a rapid, highly sensitive and cheap diagnostic tool for diagnosis of typhoid fever.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The absence of a reliable diagnosis pushes rural populations towards self-medication with all the consequences that this entails, in particular drug poisoning which can lead to death.  As such, we want to develop a new method to diagnose Typhoid early, quickly, and with accurate results at a low cost. We propose a hybrid diagnosis method with a Deep Learning algorithm applied on blood serum images which seems to be the best accepted test by laboratory technicians. We use CNNs as algorithms on the collected images to train the algorithm. We use a second algorithm Rough Set Theory. This algorithm based on symptoms variables which are structured data collected from medical doctors allow us not only to confirm the diagnosis but above all to determine the level of severity of the disease and serve as a Decision Support System. The two algorithms will be part of a mobile app connected to an optical microscope, the phone camera will scan images from the slides on the microscope and classify them into Normal or Infected.  In a series of rapid spotlights, we present tools and frameworks that serve as cornerstones for the envisioned diagnostics system including: 1) Values, influences and forces that shape the diagnostics 2) AI solutions to be used; 3) Data sources 4) Ethics and governance model.&lt;/p&gt;</description>
        <persons>
          <person id="7741">Elisee JAFSIA</person>
        </persons>
        <attachments>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/open_research_diagnostics_typhoid/attachments/paper/4818/export/events/attachments/open_research_diagnostics_typhoid/paper/4818/ABSTRACT">Improve diagnostics of typhoid through Open Science: An Artificial Intelligence-based technique</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/open_research_diagnostics_typhoid/attachments/slides/4967/export/events/attachments/open_research_diagnostics_typhoid/slides/4967/Presentation_slide">Improve diagnostics of typhoid through Open Science: An Artificial Intelligence-based technique</attachment>
        </attachments>
        <links>
          <link href="https://www.mboalab.africa">Mboalab website</link>
          <link href="https://archive.fosdem.org/2021/schedule/event/prototyping_in_cameroon/">Past presentation</link>
          <link href="https://github.com/Mboalab/Mboalab-Outreachy_December-to-March-2022-internship-round">Project repository</link>
          <link href="https://orcid.org/ 0000-0001-9262-4053">Orcid</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_diagnostics_typhoid.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_diagnostics_typhoid.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_diagnostics_typhoid:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_diagnostics_typhoid:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12598.php">Submit feedback</link>
        </links>
      </event>
      <event id="13043">
        <start>14:05</start>
        <duration>00:15</duration>
        <room>D.research</room>
        <slug>open_research_artificial_intelligence</slug>
        <title>Artificial Intelligence Panel</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Discussion between the Artificial Intelligence panel's speakers.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7635">Yo Yehudi</person>
          <person id="7741">Elisee JAFSIA</person>
          <person id="8529">Gemma Turon</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.research/open_research_artificial_intelligence.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_artificial_intelligence.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_artificial_intelligence:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_artificial_intelligence:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13043.php">Submit feedback</link>
        </links>
      </event>
      <event id="12783">
        <start>14:20</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_gitbuilding</slug>
        <title>GitBuilding: Open source documentation for open source hardware</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;GitBuilding is an Open source program for writing hardware documentation. GitBuilding uses your tags and meta-data to automatically generate and insert bills of materials into your documentation. It correctly links different steps to one another (even when you have multiple variants), allowing you to write instructions once and reuse them for multiple projects. It also shows previews of 3D files and lets you easily include links to generated zips and other files in the correct places. You can output the entire documentation in pure Markdown, HTML, or PDF.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Open hardware is beginning to mature. International agencies such as the European Commission and UNESCO see open hardware as key to open access, especially for science hardware. Open hardware could help bring an end to the reproducibility crisis where researchers cannot replicate the work of others. However, open hardware has a key hurdle to overcome: documentation.&lt;/p&gt;

&lt;p&gt;Documentation is important for any open project. You can't study and improve something unless it is documented. For hardware the problem is more pronounced, distribution of hardware relies either on people replicating a design themselves, or on a manufacturer producing the design. Without assembly instructions a project can't be used by anyone, for anything but the most simple project, the digital design files are not enough.&lt;/p&gt;

&lt;p&gt;As open hardware matures documentation becomes even more important. Most people don't have the time to build all of the products they use. Even those who care about open hardware want to buy a pre-made product. To manufacture a product the documentation must be far more complete, including enough design rationale that a manufacturer can fix problems, and containing not just assembly steps, but also quality assurance procedures.&lt;/p&gt;

&lt;p&gt;GitBuilding is a tool designed to allow open hardware designers to keep markdown documentation with their hardware designs, such as in a Git repository. Extra syntax has been introduced to semantically link pages together, and to identify when tools and components are used. This allows the automatic creation of Bills of Materials, as well as reuse of specific instructions for multiple variations of the same project.&lt;/p&gt;

&lt;p&gt;GitBuilding was initially designed for the OpenFlexure Microscope (OFM) project. The OFM is an open source laboratory grade motorised microscope that is being trialled for malaria diagnosis in Tanzania. The open project plans to support manufacturers across the world in selling the OFM as an in vitro diagnostic (IVD) device. For this to be possible our documentation must be complete enough that manufacturers can verify the microscopes performance and design, and their own manufacturing of it to a standard acceptable to their IVD regulator. GitBuilding must be powerful enough to support this documentation.&lt;/p&gt;

&lt;p&gt;GitBuilding is now needs to generalise. The project needs to be sure it is collecting the correct data for other types of hardware and for other industries. We need to gather input from across the open hardware community, so we know what data needs to be captured, and so where possible this information can be captured exactly one, and used wherever it is needed.&lt;/p&gt;</description>
        <persons>
          <person id="8738">Julian  Stirling</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://gitbuilding.io">Project page</link>
          <link href="https://gitlab.com/gitbuilding/gitbuilding">GitLab repository</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_gitbuilding.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_gitbuilding.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_gitbuilding:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_gitbuilding:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12783.php">Submit feedback</link>
        </links>
      </event>
      <event id="12462">
        <start>14:40</start>
        <duration>00:15</duration>
        <room>D.research</room>
        <slug>open_research_beehive</slug>
        <title>BeeHive: a flexible open hardware platform for behavioural experiments</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Digital and technical literacies are an ubiquitous requirement in modern research teams. Despite being fundamental, they are rarely part of the curriculum in universities, thus undergrad and early career researchers often struggle to code data analysis pipelines and to automate data collection from experimental setups. Neurosciences, in particular, relies a lot on these skills, with behavioural experiments planning, design of the testing boxes, data visualisation and analysis. To Successfully complete these tasks, researchers need to acquire a significant level of skill in programming and hardware design.
To address these problems, we are developing a flexible open hardware platform to lower the barrier in creating experimental setups: BeeHive. It consists of a main board, which nests an ESP32 microcontroller, and several dedicated “daughter boards”, each designed to perform one function (e.g. one board senses temperature, another controls motors, etc). These boards are connected to one another using a standard system already used by other Open Hardware systems, so that there is no need to reinvent the wheel. We can then focus on developing things that are not available yet. The system runs MicroPython, which is a Python derivative for microcontrollers.
This architecture allows users to be in control of everything that the platform is doing while also providing plenty of room for completely new applications. Modular structure helps users to get familiar with electronic components already at entry-level expertise while Python is employed for its strong points such as simplicity and widespread usage. In this presentation we set out to explore the core concept of Beehive, describe existing and possible applications.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6097">Andre Maia Chagas</person>
          <person id="8550">Ihor Sobianin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/BeeHive-org/BeeHive">BeeHive github project</link>
          <link href="https://bit.ly/contactbeehive">BeeHive contact form</link>
          <link href="https://bit.ly/fosdem22">Download this presentation</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_beehive.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_beehive.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_beehive:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_beehive:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12462.php">Submit feedback</link>
        </links>
      </event>
      <event id="13044">
        <start>14:55</start>
        <duration>00:15</duration>
        <room>D.research</room>
        <slug>open_research_open_hardware</slug>
        <title>Open Hardware Panel</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Discussion between the Open Hardware panel's speakers..&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3641">Matthieu Totet</person>
          <person id="6097">Andre Maia Chagas</person>
          <person id="8550">Ihor Sobianin</person>
          <person id="8738">Julian  Stirling</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.research/open_research_open_hardware.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_open_hardware.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_open_hardware:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_open_hardware:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13044.php">Submit feedback</link>
        </links>
      </event>
      <event id="12540">
        <start>15:10</start>
        <duration>00:10</duration>
        <room>D.research</room>
        <slug>open_research_actigraphy_light_exposure</slug>
        <title>Building a consensus meta-data standard for actigraphy and light exposure data</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In chronobiology and sleep science, researchers often collect data using research-grade activity trackers called actigraphs, which measure movement and determine rest-activity cycles, and light dosimeters, which measure light exposure. At present, there is no meta-data standard for actigraphy and light exposure data that describe aspects of the data collection, such as device manufacturer, sampling rate, or instructions given to the participant. However, meta-data like those are critical for aggregating data and comparing data collected in different samples or across various research sites. Over the past 1+ year, we have been working on developing a consensus meta-data standard for describing actigraphy and light exposure data. The standard is written in JSON-schema, and is extendable to other time-series modalities (such as temperature). The standard is the joint effort of two teams of researchers volunteering their time. In this talk, I will describe the journey from inception to standard, along with the challenges and barriers encountered.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8619">Manuel Spitschan</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.research/open_research_actigraphy_light_exposure.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_actigraphy_light_exposure.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_actigraphy_light_exposure:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_actigraphy_light_exposure:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12540.php">Submit feedback</link>
        </links>
      </event>
      <event id="12506">
        <start>15:20</start>
        <duration>00:10</duration>
        <room>D.research</room>
        <slug>open_research_brapi</slug>
        <title>BrAPI: a standard API specification for plant breeding data</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Modern plant breeding research requires a large amount of data to function effectively. Data repositories are improving in their ability to store this data, but there is a growing need for interoperability between disparate data sources and applications. The Breeding Application Programming Interface (BrAPI) project offers a solution to this problem with a standardized RESTful web service API specification. This specification provides a standard data model for the plant breeding domain, plus a well-defined set of methods for interacting with the data. The goal of the project is to promote interoperability, data sharing, and open source code sharing across organizations who produce and consume data in this domain. The BrAPI project is a community built project and that community is well established and continuously growing. The standard is built based on concrete use cases to solve real interoperability challenges faced by the community.  Beyond the core standard, the community has built a variety of open source tools and resources to help build and test implementations of the specification. The community is also constantly producing new BrAPI compliant applications, analysis tools, and visualizations that will work with any BrAPI data source.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8593">Peter Selby</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/open_research_brapi/attachments/slides/4922/export/events/attachments/open_research_brapi/slides/4922/BrAPI_FOSDEM2022_Selby.pptx">BrAPI: a standard API specification for plant breeding data</attachment>
        </attachments>
        <links>
          <link href="https://brapi.org/ ">BrAPI Project Website</link>
          <link href="https://github.com/plantbreeding/ ">BrAPI Project Source Code</link>
          <link href="https://doi.org/10.1093/bioinformatics/btz190">BrAPI Project Publication</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_brapi.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_brapi.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_brapi:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_brapi:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12506.php">Submit feedback</link>
        </links>
      </event>
      <event id="13045">
        <start>15:30</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_standards_panel</slug>
        <title>Standards panel</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Discussion between Standards panel's speakers.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4280">Mathieu Jacomy</person>
          <person id="8593">Peter Selby</person>
          <person id="8619">Manuel Spitschan</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.research/open_research_standards_panel.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_standards_panel.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_standards_panel:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_standards_panel:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13045.php">Submit feedback</link>
        </links>
      </event>
      <event id="12362">
        <start>15:50</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_ontology_development_kit</slug>
        <title>Ontology Development Kit</title>
        <subtitle>A toolkit for building, maintaining, and standardising ontologies</subtitle>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In biomedical sciences, ontologies are used to annotate and organize data stored in knowledge databases and facilitate their exploitation. Following the pioneering work of the Gene Ontology at the turn of the century, the Open Biomedical and Biological Ontologies (OBO) Foundry was created to coordinate the development of a family of interoperable ontologies sharing a core set of principles. The Foundry now includes more than 150 ontologies.
The Ontology Development Kit (ODK) [1] was developed to facilitate the implementation of standardized ontology development practices across the Foundry. It takes the form of a Docker image that provides ontology editors with all the command-line tools they need to manage, edit, build, and test their ontologies, as well as standardized and carefully crafted Makefile rules to pilot all steps of the ontology life cycle. In recent years, many ontologies such as the Uberon multi-species anatomy ontology, the Cell Ontology (CL), or the Unified Phenotype Ontology (uPheno) have been converted to use the ODK. By moving most of the management, building, and testing logic from the individual ontologies to the ODK, the kit aims to make the life of ontology editors easier, by allowing them to focus solely on actual ontology editing, all the while contributing to the standardisation of the various ontologies.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;[1] Nicolas Matentzoglu, Chris Mungall, and Damien Goutte-Gattat (2021). Ontology Development Kit. doi:10.5281/zenodo.5762512&lt;/p&gt;</description>
        <persons>
          <person id="8491">Damien Goutte-Gattat</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/INCATools/ontology-development-kit">Public repository for the Ontology Development Kit</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_ontology_development_kit.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_ontology_development_kit.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_ontology_development_kit:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_ontology_development_kit:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12362.php">Submit feedback</link>
        </links>
      </event>
      <event id="12507">
        <start>16:10</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_wikibase</slug>
        <title>Sustainable community building with the Wikibase Stakeholder Group</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Wikibase Stakeholder Group is a new initiative testing alternative approaches to governance, decision-making and community-building for open source digital knowledge management. It aims to facilitate collaboration across various institutional and individual partners in order to ensure the continued development and long-term sustainability of Wikibase, a suite of tools for data management within a linked open data environment. Wikibase is currently developed and maintained by Wikimedia Germany, a chapter of the non-profit Wikimedia Foundation. Wikibase is vital infrastructure for the public linked data project Wikidata, but since its open release in 2015 it has been increasingly taken up in research, cultural and institutional contexts due to its flexible, open and collaborative architecture. Rhizome have been piloting the use of Wikibase within GLAM contexts since its release, and have co-organized the first set of public meetups and events around the emerging Wikibase community and ecosystem of decentralized Wikibase instances. Following the success in bringing the community together through these events Rhizome and a few early adopters started the Wikibase Stakeholder Group at the end of 2020. In this talk, we will present the activities of the Group to date, lessons learned from our experiences in collective decision-making, funding for collaborative development efforts, and negotiating between individual project requirements towards a common roadmap in line with ongoing efforts of the Wikimedia team.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Expected prior knowledge / intended audience:
No prior knowledge is required for this talk, except general familiary with open source community contexts and open data management tools. The intended audience is other practitioners actively involved in open source communities, in the governance and organization of communities, and/or the development of tools for linked open data management.&lt;/p&gt;</description>
        <persons>
          <person id="8594">Lozana Rossenova</person>
          <person id="8859">Dragan Espenschied</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://wbstakeholder.group/ ">Link to main subject of the lightning talk</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_wikibase.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_wikibase.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_wikibase:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_wikibase:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12507.php">Submit feedback</link>
        </links>
      </event>
      <event id="13039">
        <start>16:30</start>
        <duration>00:15</duration>
        <room>D.research</room>
        <slug>open_research_knowledge_management_panel</slug>
        <title>Knowledge management communities panel</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Discussion between speakers of the Knowledge Management Communities panel.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Open source software can help in building communities around common practices.
Damien Goutte-Gattat's talk shows how a piece of software (Ontology Development Kit) can help ontology editors to deploy their tools and at same time foster standardized ways to write and publish their work.
A double benefit grounded in FOSS practices.&lt;/p&gt;

&lt;p&gt;But Open source software also benefits in return of organized users communities.
Lozana Rossenova and Dragan Espenschied present the Wikibase Stakeholder Group which gathers a community of wikibase server and its plugins users and developers.
A detailed explanation of how to care a community around a FOSS.&lt;/p&gt;

&lt;p&gt;Those two sides of community building around knowledge management will be discussed with the speakers in a live discussion panel.
Questions from the audience will be collected from the textual chatroom and voiced by the session moderator.&lt;/p&gt;</description>
        <persons>
          <person id="2865">Paul Girard</person>
          <person id="8491">Damien Goutte-Gattat</person>
          <person id="8594">Lozana Rossenova</person>
          <person id="8859">Dragan Espenschied</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.research/open_research_knowledge_management_panel.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_knowledge_management_panel.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_knowledge_management_panel:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_knowledge_management_panel:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13039.php">Submit feedback</link>
        </links>
      </event>
      <event id="13519">
        <start>16:45</start>
        <duration>00:15</duration>
        <room>D.research</room>
        <slug>open_research_f_uji</slug>
        <title>F-UJI : A Tool for the automated assessment and improvement of the FAIRness of Research Data</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Funders, publishers and scientific organizations have highly endorsed the adoption of FAIR principles (Findable, Accessible, Interoperable, and Reusable) to promote research data reusability and reproducibility.
However, FAIR principles are high-level guidelines without explicit requirements for their implementation. Practical solutions such as metrics and associated tools are required to support the assessment of FAIR compliance of research artefacts such as services and datasets. This talk will introduce an open-source tool named F-UJI which was mainly developed to support trustworthy data repositories committed to FAIR data provision to programmatically measure datasets for their level of FAIRness over time. The talk will provide an overview the development and application of F-UJI and use cases it has supported so far.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8932">Patricia Herterich</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.research/open_research_f_uji.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_f_uji.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_f_uji:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_f_uji:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13519.php">Submit feedback</link>
        </links>
      </event>
      <event id="12771">
        <start>17:00</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_agrometeorology</slug>
        <title>Internal R packages for Open Science in Agrometeorology</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Argentina's National Institute of Agricultural Technology (INTA) conducts research and development for the agricultural sector. Environmental conditions influence agricultural activity; in particular, climatic conditions have a favorable or detrimental effect on production. Thus, it is essential to monitor and analyze the different agro-meteorological variables to describe these conditions and their impact on agricultural and livestock production. With this approach, INTA has an extensive ground network of conventional and automatic weather stations. In addition, there is an information system (http://siga.inta.gob.ar) with predefined queries and visualization on this data for internal and external use. All the information generated by the institution is openly shared under a CC-BY-NC license.
INTA is a decentralized institution and generates research, analysis, and reports at different scales (national to local).  The processes to perform these tasks use various software tools and different methodologies.  Moreover, these processes are in the computer and the head of the researchers.&lt;br/&gt;
Developing internal packages or libraries has great potential to promote reproducible analysis frameworks, improve an organization's code quality, enhance knowledge management (Riederer, 2021), standardize and make processes transparent, and open software and data to society.&lt;/p&gt;

&lt;p&gt;The {agromet} package includes a series of functions that can be used regularly for the calculation of agrometeorological indices and statistics. The input meteorological data works under the tidy data philosophy, so the package functions are generic. They can be applied to any tabular dataset regardless of its origin, order, or column names. However, according to INTA's internal requirements, the package also incorporates tools to read data in an INTA format.  This package has implemented functions for calculating indexes and variables of agricultural interest, standardizing how these computations are made.  It also incorporates mapping functions with scale and reports templates.&lt;/p&gt;

&lt;p&gt;The package {siga} downloads and reads data from INTA's Agrometeorological Information and Management System programmatically.&lt;/p&gt;

&lt;p&gt;This talk will discuss the decision process to generate a series of internal packages designed to be used by INTA users but with enough generality to be helpful to a broad community. Their development, current use, and this experience encouraged the generation of similar packages for soil data.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Organization on GitHub: https://github.com/AgRoMeteorologiaINTA&lt;/p&gt;</description>
        <persons>
          <person id="8579">Yanina Bellini Saibene</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/AgRoMeteorologiaINTA/siga">Siga package</link>
          <link href="https://github.com/AgRoMeteorologiaINTA/agromet">AgroMet package</link>
          <link href="https://github.com/AgRoMeteorologiaINTA/SistemaAnguil">Local information system using agromet</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_agrometeorology.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_agrometeorology.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_agrometeorology:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_agrometeorology:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12771.php">Submit feedback</link>
        </links>
      </event>
      <event id="12758">
        <start>17:20</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_lhc</slug>
        <title>Unveiling Hidden Physics at the LHC using Open Data</title>
        <subtitle>Making particle physics Open Data usable</subtitle>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The experiments at the Large Hadron Collider (LHC) at &lt;a href="https://home.cern/"&gt;CERN&lt;/a&gt; have been running for more than a decade. The data recorded by the detectors such as the &lt;a href="https://cms.cern/"&gt;CMS experiment&lt;/a&gt; are analysed by thousands of physicists all over the world. The CMS Collaboration has made openly available more than 2.5 petabytes of data on the &lt;a href="http://opendata.cern.ch/"&gt;CERN Open Data Portal&lt;/a&gt;, containing billions of recorded and simulated events.&lt;/p&gt;

&lt;p&gt;Open Data are, however, only useful when accompanied by realistic usage examples. The sheer amount of data as well as the fact that the software used to analyse them is often more than ten years old poses several challenges. In this presentation, Clemens will discuss how the CMS Data Preservation and Open Access group tries to overcome these challenges so that potentially everyone could use the data to &lt;a href="https://arxiv.org/abs/2109.06065"&gt;unveil hidden physics&lt;/a&gt;.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8725">Clemens Lange</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/open_research_lhc/attachments/slides/5071/export/events/attachments/open_research_lhc/slides/5071/Slides_FOSDEM_ClemensLange_UnveilingHiddenPhysics_OpenData.pdf">Slides for Unveiling Hidden Physics at the LHC using OpenData</attachment>
        </attachments>
        <links>
          <link href="http://opendata.cern.ch/">CERN Open Data Portal</link>
          <link href="https://arxiv.org/abs/2109.06065">Community White Paper on Open Data in particle physics</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_lhc.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_lhc.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_lhc:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_lhc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12758.php">Submit feedback</link>
        </links>
      </event>
      <event id="13040">
        <start>17:40</start>
        <duration>00:20</duration>
        <room>D.research</room>
        <slug>open_research_open_data_panel</slug>
        <title>Open Data Panel</title>
        <subtitle/>
        <track>Open Research Tools and Technologies</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Discussion between the Open data Panel speakers.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8471">Sara Petti</person>
          <person id="8579">Yanina Bellini Saibene</person>
          <person id="8725">Clemens Lange</person>
          <person id="8932">Patricia Herterich</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.research/open_research_open_data_panel.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.research/open_research_open_data_panel.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#research-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#research-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#research-open_research_open_data_panel:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#research-open_research_open_data_panel:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13040.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.design">
      <event id="13193">
        <start>10:00</start>
        <duration>00:20</duration>
        <room>D.design</room>
        <slug>osd_introduction_to_open_source_design</slug>
        <title>Introduction to Open Source Design</title>
        <subtitle/>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Every year we take some time to introduce the Open Source Design collective, what we do, where to find us and how to get involved.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2363">Bernard Tyers</person>
          <person id="8674">Eriol Fox</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.design/osd_introduction_to_open_source_design.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_introduction_to_open_source_design.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_introduction_to_open_source_design:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_introduction_to_open_source_design:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13193.php">Submit feedback</link>
        </links>
      </event>
      <event id="12981">
        <start>10:20</start>
        <duration>00:25</duration>
        <room>D.design</room>
        <slug>osd_lessons_learned_from_open_sourcing_the_orbit_docs</slug>
        <title>Documenting a Design System</title>
        <subtitle>Lessons learned from open sourcing the Orbit docs</subtitle>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A design system helps contributors create consistent user experiences. To elevate from a collection of patterns to a system, you need to provide clear standards and reasoning. Clear and comprehensive documentation helps you put this system together into something everyone can use.&lt;/p&gt;

&lt;p&gt;This talk will go through how we open sourced the documentation for the &lt;a href="https://orbit.kiwi/"&gt;Orbit design system&lt;/a&gt; and discuss what we learned from the process. It will discuss creating both visual and content standards for the docs and how it was all accomplished. The lessons from this experience can help in the creation of useful and accessible documentation to guide the design process.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8811">Aaron Collier</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://orbit.kiwi">Orbit documentation</link>
          <link href="https://github.com/kiwicom/orbit/tree/master/docs">Source for documentation</link>
          <link href="https://presentations.collier.cz/slides/documenting-design-system.html">Slides</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_lessons_learned_from_open_sourcing_the_orbit_docs.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_lessons_learned_from_open_sourcing_the_orbit_docs.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_lessons_learned_from_open_sourcing_the_orbit_docs:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_lessons_learned_from_open_sourcing_the_orbit_docs:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12981.php">Submit feedback</link>
        </links>
      </event>
      <event id="12804">
        <start>12:10</start>
        <duration>00:25</duration>
        <room>D.design</room>
        <slug>osd_stories_and_learnings_from_1_and_a_half_years_of_supporting_designers_and_open_design_processes_in_the_bitcoin_ecosystem</slug>
        <title>Supporting open design in Bitcoin</title>
        <subtitle>Stories and learnings from 1.5 years of supporting designers and open design processes in the Bitcoin ecosystem.</subtitle>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;At FOSDEM 2021, we shared an introduction to, and the ambitions of, the Bitcoin Design Community. 6 months into the effort, we were brimming with ideas and big goals for designing amazing user experiences, connecting designers with open-source projects, and lots more. Now, one year later, we’d like to look back and share where we are, what has worked for us, and what hasn’t (yet?).&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7728">Christoph Ono</person>
          <person id="8981">Johns Beharry</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://bitcoin.design">Bitcoin Design Community website</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_stories_and_learnings_from_1_and_a_half_years_of_supporting_designers_and_open_design_processes_in_the_bitcoin_ecosystem.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_stories_and_learnings_from_1_and_a_half_years_of_supporting_designers_and_open_design_processes_in_the_bitcoin_ecosystem.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_stories_and_learnings_from_1_and_a_half_years_of_supporting_designers_and_open_design_processes_in_the_bitcoin_ecosystem:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_stories_and_learnings_from_1_and_a_half_years_of_supporting_designers_and_open_design_processes_in_the_bitcoin_ecosystem:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12804.php">Submit feedback</link>
        </links>
      </event>
      <event id="12657">
        <start>14:00</start>
        <duration>00:25</duration>
        <room>D.design</room>
        <slug>osd_synthesising_user_testing_insights_with_oss_tool_teams</slug>
        <title>Synthesising user testing insights with OSS tool teams</title>
        <subtitle/>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;So you’ve done some user testing or usability testing as an open source software team and now you have interesting user insights collected. But...what do you do with it? How does user feedback correspond to issues in the backlog? How do you get the wider OSS community team up to speed if they haven’t been part of the synthesis process? These are some of the questions you may ask yourself after participating in user testing or usability testing. You’re ready for a synthesis process!&lt;/p&gt;

&lt;p&gt;The USABLE team has already published two resources about user testing and usability testing, now they are presenting their third resource about user insight synthesis. You’ll see how they supported open source software tool teams to work with user insights in an open source way of user testing, usability and synthesis work.
In this session you will observe how the USABLE team supported OSS tool teams with user insight synthesis processes with detailed explanations of why, how and when to do synthesis. You will also view clips of a previous closed session in which the USABLE team and OSS tool teams collaborated on a synthesis work session.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;So you’ve done some user testing or usability testing as an open source software team and now you have interesting user insights collected. But...what do you do with it? How does user feedback correspond to issues in the backlog? How do you get the wider OSS community team up to speed if they haven’t been part of the synthesis process? These are some of the questions you may ask yourself after participating in user testing or usability testing. You’re ready for a synthesis process!&lt;/p&gt;

&lt;p&gt;The USABLE team has already published two resources about user testing and usability testing, now they are presenting their third resource about user insight synthesis. You’ll see how they supported open source software tool teams to work with user insights in an open source way of user testing, usability and synthesis work.
In this session you will observe how the USABLE team supported OSS tool teams with user insight synthesis processes with detailed explanations of why, how and when to do synthesis. You will also view clips of a previous closed session in which the USABLE team and OSS tool teams collaborated on a synthesis work session.&lt;/p&gt;</description>
        <persons>
          <person id="8674">Eriol Fox</person>
          <person id="8904">Kelsey Smith</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/simplysecure/usable-user-testing-can-be-fun">First USABLE resource</link>
          <link href="https://github.com/simplysecure/a-devs-guide-to-user-testing">Second USABLE resource</link>
          <link href="https://usable.tools/">USABLE tools website</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_synthesising_user_testing_insights_with_oss_tool_teams.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_synthesising_user_testing_insights_with_oss_tool_teams.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_synthesising_user_testing_insights_with_oss_tool_teams:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_synthesising_user_testing_insights_with_oss_tool_teams:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12657.php">Submit feedback</link>
        </links>
      </event>
      <event id="12933">
        <start>14:30</start>
        <duration>00:25</duration>
        <room>D.design</room>
        <slug>osd_penpot_we_hear_you_collecting_and_processing_user_feedback</slug>
        <title>We hear you!</title>
        <subtitle>Collecting and processing user feedback, for real!</subtitle>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A lot of UX practitioners don't talk to users on a regular basis, at Penpot we might be on the opposite side of the spectrum. We gather a lot of feedback from our users. What for? Fixing (bugs), improving (enhancements), discovering (new needs), prioritizing (asking/frequent queries as an indicator). And the most important thing is what do we do with that feedback and which kind of feedback would we like to receive?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;At Penpot, we work as a full support team. We think of our users as a knowledgeable open space they provide us and we all work to learn from the market. Also it’s important to mention that we design Penpot with Penpot, the team members are users too. Plus we manage all our work at Penpot with our sibling Taiga, a powerful agile project management tool which is our sibling company. Obviously we have our own product development vision, but we like to discover what our users think with an open- feedback policy, and feel validation with conducted tests. Our community is the most important and fundamental part in Penpot’s roadmap.&lt;/p&gt;</description>
        <persons>
          <person id="8796">Clara Garcia</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/osd_penpot_we_hear_you_collecting_and_processing_user_feedback/attachments/slides/5161/export/events/attachments/osd_penpot_we_hear_you_collecting_and_processing_user_feedback/slides/5161/We_hear_you_slides">We hear you - slides</attachment>
        </attachments>
        <links>
          <link href="https://penpot.app/">https://penpot.app/</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_penpot_we_hear_you_collecting_and_processing_user_feedback.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_penpot_we_hear_you_collecting_and_processing_user_feedback.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_penpot_we_hear_you_collecting_and_processing_user_feedback:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_penpot_we_hear_you_collecting_and_processing_user_feedback:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12933.php">Submit feedback</link>
        </links>
      </event>
      <event id="12679">
        <start>15:00</start>
        <duration>00:25</duration>
        <room>D.design</room>
        <slug>osd_when_to_invest_in_the_ux_of_scientific_open_source</slug>
        <title>When to invest in the UX of (scientific) open source</title>
        <subtitle/>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Software has become increasingly central to scientific research. Both software development and its use are essential activities for scientific teams. But investment in its production, maintenance, and adoption is often overlooked, and academia often fails to leverage best practices for software engineering from industry, the open source community, or elsewhere. Furthermore, investment in the user experience (UX) and usability of scientific software is largely an afterthought, if considered at all. As such, any future investment in UX is expected to have a disproportionately positive impact on adoption of scientific tools (i.e. broadening access) and on scientific discovery itself. Currently, the impact of this kind of investment (or lack thereof) is largely unknown.&lt;/p&gt;

&lt;p&gt;Scientific software stands to benefit from the learnings and current practices in open source design. This talk will explore the unique workflows and incentives of research institutions (and other contexts in which scientific software is produced) and map them to current practices of open source design with the intention of bringing to light the opportunities to better understand how and when to invest in the UX of research software, how to grow expertise in UX, and how to cultivate norms on peer-production platforms toward good UX practices.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8485">Elizabeth Vu</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://sloan.org/programs/digital-technology">https://sloan.org/programs/digital-technology</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_when_to_invest_in_the_ux_of_scientific_open_source.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_when_to_invest_in_the_ux_of_scientific_open_source.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_when_to_invest_in_the_ux_of_scientific_open_source:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_when_to_invest_in_the_ux_of_scientific_open_source:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12679.php">Submit feedback</link>
        </links>
      </event>
      <event id="12748">
        <start>15:30</start>
        <duration>00:25</duration>
        <room>D.design</room>
        <slug>osd_why_designers_are_the_mediators_of_accessibility</slug>
        <title>Why Designers are the Mediators of Accessibility</title>
        <subtitle>How the designer's perspective leads to a more accessible OSS</subtitle>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Two designers came together to tackle this under-addressed issue in OSS. In this talk, we'll cover
- How design principles have shaped our understanding of the technical challenges in implementing accessibility in OSS, such as writing 'alt-text' for scientific diagrams
- Learn about the real impact our workshops have made in NumPy, JupyterLab and scikit-learn
- How other OSS projects can host their own accessibility workshops and sprints&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Designers have valuable skills that go beyond the visual arts: the ability to zoom out and see the big picture, finding connections between disparate objects, and creating a pleasant user flow.&lt;/p&gt;

&lt;p&gt;It is exactly these skills that make designers such valuable mediators of accessibility!&lt;/p&gt;

&lt;p&gt;Mediators are required as the needs of accessible technology and OSS can seem at odds:
- Accessible technology needs to recognize the variety of disabilities, that there are many possible solutions, and to create cohesive alternative experience
- OSS needs flexibility and variety: it is exactly because individual contributors add different things that it can be difficult to uniformly follow any sort of guidelines for one disability, much less for a variety of disabilities&lt;/p&gt;

&lt;p&gt;This talk will explore how two designers came together to start mediating for more accessible OSS. Hear about our messy beginning trying to decode terms and guidelines, talking to developers of what they need, and finally creating accessibility-focused workshops for NumPy, JupyterLab and scikit-learn that have already made changes to the codebase.&lt;/p&gt;

&lt;p&gt;Designers will leave with an understanding of accessibility, their role in it and actionable steps, such as how to host their own accessibility workshops in their communities.&lt;/p&gt;

&lt;p&gt;Note: While accessibility is a broad term that encompasses accommodating for a variety of disabilities, this talk focuses on making OSS accessible to people with visual disabilities via implementation of 'alt-text' for scientific diagrams.&lt;/p&gt;</description>
        <persons>
          <person id="8717">Mars Lee</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://docs.google.com/presentation/d/10P3KsYnaRL1s0JrWhV3pfs00_XISgfgs/edit?usp=sharing&amp;ouid=110556856523158639329&amp;rtpof=true&amp;sd=true">Presentation Slides</link>
          <link href="https://gist.githubusercontent.com/MarsBarLee/64b7194dc40b79ff217d85cbefb7b138/raw/c5a14fd338086a15f8d3af28a20d0a2f0df6f1f0/Why%2520Designers%2520are%2520the%2520Mediators%2520of%2520Accessibility%2520Transcript.md">Transcript of Talk</link>
          <link href="https://www.youtube.com/watch?v=FCWCtUmWmkk">Video with Captions</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_why_designers_are_the_mediators_of_accessibility.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_why_designers_are_the_mediators_of_accessibility.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_why_designers_are_the_mediators_of_accessibility:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_why_designers_are_the_mediators_of_accessibility:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12748.php">Submit feedback</link>
        </links>
      </event>
      <event id="12478">
        <start>16:00</start>
        <duration>00:45</duration>
        <room>D.design</room>
        <slug>osd_successful_remote_workshop_in_a_remote_workshop</slug>
        <title>Remote workshops</title>
        <subtitle>Learn how to conduct a successful remote workshop in a remote workshop</subtitle>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this workshop, you will learn how to plan and conduct a remote workshop. It will cover helpful tools and methods, energizers, and collaborative design. On top of that, you will get insights and first-hand experience solving workshop issues like scheduling over timezones, mixing real-life and remote settings and involving people even in virtual formats.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The open-source software company Grafana Labs successfully holds virtual workshops in a remote setting, both with small and large groups. Facilitator Jess will show how she conducts such workshops and teach you her tried and tested insights – in an interactive workshop format!&lt;/p&gt;</description>
        <persons>
          <person id="8560">Jess Müller</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://docs.google.com/presentation/d/1qiBENz2EGPC7e7RaskuXwydh1Nz1RokqtdLI2m1Zxjs/edit?usp=sharing">Slides</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_successful_remote_workshop_in_a_remote_workshop.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_successful_remote_workshop_in_a_remote_workshop.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_successful_remote_workshop_in_a_remote_workshop:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_successful_remote_workshop_in_a_remote_workshop:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12478.php">Submit feedback</link>
        </links>
      </event>
      <event id="12367">
        <start>16:45</start>
        <duration>00:25</duration>
        <room>D.design</room>
        <slug>osd_attracting_and_keeping_ux_designers_on_foss_projects</slug>
        <title>Calling all UX Designers!</title>
        <subtitle>Attracting and keeping UX designers on FOSS projects</subtitle>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;How can your project attract (and keep!) UX designers? I'll list few specific changes that should help. But I have to warn you, these aren't quick hacks. They're small but meaningful changes to your culture that will also improve your product overall.&lt;/p&gt;

&lt;p&gt;I gave a talk at &lt;a href="https://www.youtube.com/watch?v=Mjup7Mrj7uU"&gt;FOSS Backstage on UX and FOSS&lt;/a&gt;. This is really 'part 2' in the series, making concrete suggestions maintainers can use to help make their projects more UX focused and by extension, help attract UX designers.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7710">Scott Jenson</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.design/osd_attracting_and_keeping_ux_designers_on_foss_projects.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_attracting_and_keeping_ux_designers_on_foss_projects.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_attracting_and_keeping_ux_designers_on_foss_projects:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_attracting_and_keeping_ux_designers_on_foss_projects:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12367.php">Submit feedback</link>
        </links>
      </event>
      <event id="12966">
        <start>17:15</start>
        <duration>00:25</duration>
        <room>D.design</room>
        <slug>osd_sustaining_open_source_design_podcast</slug>
        <title>1 year of the Sustaining open source design podcast</title>
        <subtitle>What key themes emerged from 1 year and 17 episodes of design in open source podcasts?</subtitle>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Sustaining open source design podcast has been hosting conversations about open source and design over the last year with designers of all kinds across the spectrum of open source software projects. From new to open source to long term contributors and from practicing visual designers to design researchers. We've spent over 30 hours in conversation with designers and we are coming together as hosts to discuss the main themes throughout these conversations in 2021 at FOSDEM 2022 with a look ahead to what might come up in 2022 for design in OSS.&lt;/p&gt;

&lt;p&gt;This will be a conversation between hosts of the SOS design podcast: Eriol Fox, Georgia Bullen, Memo Esparza, Peace Omejeh and Richard Littuar&lt;/p&gt;

&lt;p&gt;https://sosdesign.sustainoss.org/&lt;/p&gt;</abstract>
        <description>&lt;p&gt;N/A&lt;/p&gt;</description>
        <persons>
          <person id="7288">Georgia Bullen</person>
          <person id="7878">Memo Esparza</person>
          <person id="8674">Eriol Fox</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://sosdesign.sustainoss.org/">The SOS design podcast</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_sustaining_open_source_design_podcast.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_sustaining_open_source_design_podcast.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_sustaining_open_source_design_podcast:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_sustaining_open_source_design_podcast:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12966.php">Submit feedback</link>
        </links>
      </event>
      <event id="13195">
        <start>17:40</start>
        <duration>00:20</duration>
        <room>D.design</room>
        <slug>osd_pitch_your_project</slug>
        <title>Pitch your project</title>
        <subtitle/>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this session, FOSS projects as given time to present and ask for contributions to the designers in the room. Each project is given 2 minutes to present. In those 2 minutes, they should briefly introduce the project, explain what design help they need, and provide contact details so designers can reach them after FOSDEM.&lt;/p&gt;

&lt;p&gt;The Open Source Design collective will use the information to submit a "job" for each project to the Open Source Design "jobs board" (https://opensourcedesign.net/jobs/), so that the request for design help reaches not just the designers in the room, but also the wider design community.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8674">Eriol Fox</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_pitch_your_project:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_pitch_your_project:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13195.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.firmware">
      <event id="13528">
        <start>11:00</start>
        <duration>00:10</duration>
        <room>D.firmware</room>
        <slug>welcome_ttosfbabd</slug>
        <title>Welome to the Open Source Firmware, BMC and Bootloader devroom</title>
        <subtitle/>
        <track>Open Source Firmware, BMC and Bootloader</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Warm welome to the Open Source Firmware, BMC and Bootloader devroom.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5202">Daniel Kiper</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.firmware/welcome_ttosfbabd.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.firmware/welcome_ttosfbabd.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-welcome_ttosfbabd:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-welcome_ttosfbabd:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13528.php">Submit feedback</link>
        </links>
      </event>
      <event id="13113">
        <start>11:10</start>
        <duration>00:50</duration>
        <room>D.firmware</room>
        <slug>fw_settings_and_menus</slug>
        <title>Firmware Settings and Menus</title>
        <subtitle/>
        <track>Open Source Firmware, BMC and Bootloader</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Among many challanges around initializing hardware, security, and booting into
operating systems, firmware also needs to provide an interface for the user to
change settings, set up a trust anchor, or simply enjoy colorful graphics.
This talk summarizes approaches from (U)EFI &lt;a href="https://www.intel.com/content/dam/www/public/us/en/documents/reference-guides/efi-human-interface-infrastructure-specification-v09.pdf"&gt;dating back to 2003&lt;/a&gt;,
looking at modern OEM UIs in comparison to open implementations such as the menu
in &lt;a href="https://github.com/u-root/webboot"&gt;webboot&lt;/a&gt;, those from &lt;a href="https://github.com/system76/firmware-setup"&gt;System76&lt;/a&gt;, EDK2, and &lt;a href="https://github.com/Dasharo/edk2/tree/dasharo/MdeModulePkg/Library/UefiBootManagerLib"&gt;Dasharo&lt;/a&gt;,
and showcasing prototyping environments for further development, finishing with
a short discussion of reusable and portable abstractions for designing APIs.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7248">Daniel Maslowski (CyReVolt)</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/fw_settings_and_menus/attachments/slides/5143/export/events/attachments/fw_settings_and_menus/slides/5143/firmware_settings_menus_fosdem22.pdf">Firmware Settings and Menus</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.firmware/fw_settings_and_menus.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.firmware/fw_settings_and_menus.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-fw_settings_and_menus:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-fw_settings_and_menus:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13113.php">Submit feedback</link>
        </links>
      </event>
      <event id="13104">
        <start>12:10</start>
        <duration>00:50</duration>
        <room>D.firmware</room>
        <slug>grub_status_update</slug>
        <title>GRUB - Project Status Update</title>
        <subtitle/>
        <track>Open Source Firmware, BMC and Bootloader</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The presentation will discuss current state of GRUB upstream development.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5202">Daniel Kiper</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/grub_status_update/attachments/slides/5150/export/events/attachments/grub_status_update/slides/5150/grub_project_status_update_20220119_dk.pdf">grub_project_status_update_20220119.dk.pdf</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.firmware/grub_status_update.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.firmware/grub_status_update.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-grub_status_update:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-grub_status_update:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13104.php">Submit feedback</link>
        </links>
      </event>
      <event id="13101">
        <start>13:10</start>
        <duration>00:25</duration>
        <room>D.firmware</room>
        <slug>osf_on_amd_3rd</slug>
        <title>Open Source Firmware status on AMD platforms 2022</title>
        <subtitle>OSF on AMD 3rd edition</subtitle>
        <track>Open Source Firmware, BMC and Bootloader</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This is the 3rd edition of the "Status of AMD platform in coreboot". The talk
will cover the most recent news around the AMD support in open source firmware
ecosystem and updates of the topics covered in previous years. We would like to
present status of FSF RYF KGPE-D16 platform revival and related upstreaming
effort, TrenchBoot progress for AMD platforms and status of recent support in
coreboot and oreboot projects. Finally we would like to present Dasharo - open
source firmware distribution with long term stable support for older AMD
platforms.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The history of AMD cooperation in coreboot projects reaches 2007 where the
first contribution appeared for the Geode LX processors. AMD's open-source
support continued for many years until now (with some break). This presentation
will briefly repeat the history of AMD and open source firmware. Moreover,
recent coreboot releases started to enforce certain requirements on the
features supported by the silicon code base. Aging platforms kept losing
interest and many of them (including fully open ones) starting to cause
unjustifiable overhead, because of accumulated technical debt. Most probably it
will result in similar situation as with famous 4.11 branch becoming de facto
stable branch for some platforms (e.g. FSP1.0 Bay Trail or ASUS KGPE-D16).
Nowadays AMD is releasing the newest AGESA with the cooperation of hired
coreboot developers, but charter covers modern Ryzen-based processors. We
trying to support the AMD platforms by reimplementing the ASUS KGPE-D16 (FSF
RYF platform) support in coreboot and keeping the PC Engines platforms in the
top of tree. We would like to present Dasharo plan for long term stable and
sustainable support for older platforms. If you are interested in open source
firmware for most open x86 platforms on the market feel free to tune in and
discuss the ideas with us.&lt;/p&gt;</description>
        <persons>
          <person id="7269">Michał Żygowski</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/osf_on_amd_3rd/attachments/slides/5052/export/events/attachments/osf_on_amd_3rd/slides/5052/Open_Source_Firmware_status_on_AMD_platforms_2022.pdf">Open Source Firmware status on AMD platforms 2022 </attachment>
        </attachments>
        <links>
          <link href="https://trenchboot.org/">TrenchBoot documentation</link>
          <link href="https://docs.dasharo.com/variants/asus_kgpe_d16/releases/">Dasharo for ASUS KGPE-D16</link>
          <link href="https://video.fosdem.org/2022/D.firmware/osf_on_amd_3rd.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.firmware/osf_on_amd_3rd.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-osf_on_amd_3rd:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-osf_on_amd_3rd:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13101.php">Submit feedback</link>
        </links>
      </event>
      <event id="13544">
        <start>13:50</start>
        <duration>00:55</duration>
        <room>D.firmware</room>
        <slug>ost2</slug>
        <title>OST2: A new way to grow security talent for open source projects</title>
        <subtitle>Open Security Training 2</subtitle>
        <track>Open Source Firmware, BMC and Bootloader</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk, we'll describe how OpenSecurityTraining2 (OST2) can help grow security talent and awareness on open source projects, and we'll use the coreboot open source firmware as a case study.&lt;/p&gt;

&lt;p&gt;Newly structured as a 501c3 non-profit, OST2's core goal is to provide free and open training that helps increase system security. This can take multiple forms, such as training dedicated security engineers, training developers to write more secure code, training potential contributors to security-focused projects, or training engineers on safer alternatives to technologies they're already using. In this talk we'll describe current and future examples of all the previous use cases, and drill deeper into a case study of how 3mbdeb, a licensed service provider for the coreboot open source firmware project, is contributing to OST2 to advance the state of open source firmware security.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6960">Piotr Król</person>
          <person id="8984">Xeno Kovah</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.firmware/ost2.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.firmware/ost2.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-ost2:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-ost2:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13544.php">Submit feedback</link>
        </links>
      </event>
      <event id="13218">
        <start>15:10</start>
        <duration>01:00</duration>
        <room>D.firmware</room>
        <slug>attestations_requirements</slug>
        <title>Attestation's Requirements</title>
        <subtitle>Secure Firmware, now what...</subtitle>
        <track>Open Source Firmware, BMC and Bootloader</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The increased need for secure firmware of all kinds in "IoT" devices from simple sensors to SBC's capable of running large operating systems (eg: Pis, IMXx boards etc) is well known and being driven by many forces, eg: Industry 4.0, 5G, 6G etc.   What interestingly is missing is how this firmware provides additional security beyond that of the individual device:  to the system as a whole, supply-chain provenance and applications; then further on to how we deal with security incidents through the added forensics and analysis of these devices. Finally we reach the impact of secure firmware to safety-critical systems.  Trusted computing, TPM and remote attestation are all well known, but their integration between themselves and the systems they are part of are going to be critical.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk we will set out how secure and high-integraty aspects of systems will or should be reflected in the development of firmware for a wide-range of devices.&lt;/p&gt;

&lt;p&gt;Trusted computing, remote attestation and the unbiquitous TPM (not forgetting Pluton and friends) are all well known technologies. Indeed a trusted computing base requires firmware with specific capabilies that promote certain aspects of immutability, identity and integrity measurements - if these properties are provides then we have the start of a chain of trust and a measurement and identity mechanism that allows that device to be "attestable".  The further property of being "trustable" needs more explanation but refers to the core root of trust measurement and how this is established, amongst other requirements.&lt;/p&gt;

&lt;p&gt;Once we have a collection of attestable (and trustable) devices then remote attestation offers us the possibility of trust relationships between those devices leading to higher-level trust capabilities and integration with supply-chain and forensics.&lt;/p&gt;

&lt;p&gt;To further demonstrate this we have developed case studies from the medical and railway verticals based upon edge cloud and 5G communications. As part of this talk we will use these safety-critical domains as the drivers for a wider and more integrated trusted computing base and ultimately the requiremnts towards firmware and hardware that sits at the core of this.&lt;/p&gt;</description>
        <persons>
          <person id="8876">Ian Oliver</person>
        </persons>
        <attachments>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/attestations_requirements/attachments/paper/4814/export/events/attachments/attestations_requirements/paper/4814/IEEE5GWF_2021_TrustedComputing.pdf">Trust, Security and Privacy through Remote Attestation in 5G and 6G Systems</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.firmware/attestations_requirements.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.firmware/attestations_requirements.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-attestations_requirements:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-attestations_requirements:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13218.php">Submit feedback</link>
        </links>
      </event>
      <event id="12340">
        <start>16:20</start>
        <duration>00:30</duration>
        <room>D.firmware</room>
        <slug>mono_lake_story</slug>
        <title>Mono Lake Story - how we enabled an open hardware platform</title>
        <subtitle/>
        <track>Open Source Firmware, BMC and Bootloader</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We are living in exciting times - we are finally seeing hyperscale server platforms opening up and running on open source software (with caveats still). The journey though is a road full of potholes, braking and sharp turns. Opening up hardware is not easy! Follow along and see how we enabled the Mono Lake platform that was originally created by Facebook (now Meta).&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Opening up hardware is a difficult process. But necessary for those who are part of the circular economy. Being able to extend the life of hardware platforms by making community supported can be quite a lift but the end is can be filled iwth possibilitles. While there has been many instances of open hardware - none though is built to run as hyperscale platform in data centers.&lt;/p&gt;

&lt;p&gt;The Mono Lake platform was originally open spec'd and built by Facebook (now Meta) - with it, we can build powerful data center class computing engines that run modern workloads. But because the platform is 4 years old, it needed to move from a singular purpose to general purpose. This talk will be focused on the journey of opeining up the Mono Lake platform and the end result and the work still left to do.&lt;/p&gt;</description>
        <persons>
          <person id="2560">Sri Ramkrishna</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/SesameEngineering/OpenSystemFirmware">github page for Mono Lake submission</link>
          <link href="https://www.sysproconsulting.com/">contact for our partner - SysPro Consulting</link>
          <link href="https://sesame.com/">Link to Sesame and related products</link>
          <link href="https://">https://</link>
          <link href="https://video.fosdem.org/2022/D.firmware/mono_lake_story.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.firmware/mono_lake_story.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-mono_lake_story:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-mono_lake_story:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12340.php">Submit feedback</link>
        </links>
      </event>
      <event id="13515">
        <start>17:00</start>
        <duration>00:50</duration>
        <room>D.firmware</room>
        <slug>plan_9_cpu_cmd</slug>
        <title>Plan 9 CPU command, in Go, for Linux</title>
        <subtitle>the network is the computer -- for real this time</subtitle>
        <track>Open Source Firmware, BMC and Bootloader</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I have reimplemented the Plan 9 cpu command in pure Go, available at github.com/u-root/cpu. It uses the ssh transport protocol for data, and the 9p protocol for file system traffic.&lt;/p&gt;

&lt;p&gt;If you are used to ssh, cpu will look very similar, to the point of even honoring your .ssh/config! What's different is that when you cpu from your local note to a remote node, file systems of your choosing are visible on the remote node, mounted over 9p, connected to a server running in the cpu command itself. Translation: you don't ever need to talk to a sysadmin to get network mounts set up. Want to use programs from your local node, libraries from your node, and see your home directory? No problem, run with the default namespace. Is the node a different architecture, but you want to use your /home? No problem, just tailor the CPU&lt;em&gt;NAMESPACE variable, e.g.: CPU&lt;/em&gt;NAMESPACE=/home:/bin=/arm/bin:/usr=/arm/usr:/lib=/arm/lib cpu cat /proc/cpuinfo. Want all this from power-on/reset? No problem, we embed kernels and a cpu daemon in flash on any of x86, ARM, ARM64, and RISC-V. Want to embed a cpu capability into your Go program? No problem there is a simple package that implements the Go exec.Command interface. Want to understand cpu? No problem, it's easy to read, consisting of 1164 lines of code for the client and 799 for the server.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3107">Ron Minnich</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/u-root/cpu">github.com/u-root/cpu</link>
          <link href="https://github.com/linuxboot/book/tree/master/cpu">github.com/linuxboot/book/tree/master/cpu</link>
          <link href="https://video.fosdem.org/2022/D.firmware/plan_9_cpu_cmd.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.firmware/plan_9_cpu_cmd.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#firmware-plan_9_cpu_cmd:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#firmware-plan_9_cpu_cmd:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13515.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.openpower">
      <event id="13538">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.openpower</room>
        <slug>openpower_workstation</slug>
        <title>OpenPOWER Ask Me Anything (AMA)</title>
        <subtitle>*RESCHEDULED*</subtitle>
        <track>OpenPOWER</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This is the OpenPOWER Foundation Ask Me Anything session.
As part of the OpenPOWER Foundation, we will be have a short session where you can ask any question related to OpenPOWER.
As this is a reschedule, please not we will have a live session and the speaker will try to answer any OpenPOWER related question they can.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt; RESCHEDULED &lt;/em&gt;&lt;/strong&gt; LIVE SESSION&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6782">Toshaan Bharvani</person>
          <person id="8377">James Kulina</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openpower/openpower_workstation.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openpower/openpower_workstation.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openpower-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openpower-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openpower-openpower_workstation:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openpower-openpower_workstation:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13538.php">Submit feedback</link>
        </links>
      </event>
      <event id="13510">
        <start>16:00</start>
        <duration>01:00</duration>
        <room>D.openpower</room>
        <slug>libresocproject</slug>
        <title>The Libre-SOC Project</title>
        <subtitle>a status update for the OpenPOWER Libre-SOC core: booting linux</subtitle>
        <track>OpenPOWER</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Libre-SOC Project aims to develop a family of OpenPOWER processors, ultimately working towards a full hybrid 3D CPU-VPU-GPU.  After two years of development funded by NLnet, the current phase is to develop a Gigabit Ethernet Router ASIC. Funded by NGI POINTER, this ASIC is intended to be capable of running OpenWRT with OpenPOWER-compliant RADIX Virtual Memory.&lt;/p&gt;

&lt;p&gt;This talk will provide background, a status update, and go through the incremental development and debugging that is leading up to being able to boot a microwatt linux-5.7 kernel with a buildroot initramfs, under verilator.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3743">Luke Kenneth Casson Leighton</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://libre-soc.org">Libre-SOC Project website</link>
          <link href="https://video.fosdem.org/2022/D.openpower/libresocproject.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openpower/libresocproject.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openpower-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openpower-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openpower-libresocproject:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openpower-libresocproject:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13510.php">Submit feedback</link>
        </links>
      </event>
      <event id="13539">
        <start>17:00</start>
        <duration>01:00</duration>
        <room>D.openpower</room>
        <slug>openpowerfoundation</slug>
        <title>OpenPOWER Foundation 2.0</title>
        <subtitle/>
        <track>OpenPOWER</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This is a presentation about the revamp of OpenPOWER platform by the OpenPOWER Foundation&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8377">James Kulina</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openpower/openpowerfoundation.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openpower/openpowerfoundation.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openpower-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openpower-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openpower-openpowerfoundation:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openpower-openpowerfoundation:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13539.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.postgresql">
    </room>
    <room name="D.public-code">
    </room>
    <room name="D.python">
    </room>
    <room name="D.raku">
      <event id="12328">
        <start>10:00</start>
        <duration>00:05</duration>
        <room>D.raku</room>
        <slug>rakudevroomintro</slug>
        <title>Raku devroom intro</title>
        <subtitle/>
        <track>Raku</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Welcome to the Raku devroom at FOSDEM 2022!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5581">Andrew Shitov</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.raku/rakudevroomintro.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.raku/rakudevroomintro.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#raku-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-rakudevroomintro:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#raku-rakudevroomintro:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12328.php">Submit feedback</link>
        </links>
      </event>
      <event id="13025">
        <start>10:05</start>
        <duration>00:45</duration>
        <room>D.raku</room>
        <slug>grammar</slug>
        <title>A Raku Grammar for Navigation Lights</title>
        <subtitle>code walkthrough with live examples</subtitle>
        <track>Raku</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;One feature that sets raku apart from other programming languages is the built-in Grammar parser syntax. This provides a concise, clean and extensible tool for parsing text and triggering Actions according to the content. Navigation aids such as buoys and markers sport flashing lights with characteristics such as color, duration, phase, occulting, speed, height, visibility and so on are represented on navigation charts by way of a short code e.g. &lt;code&gt;Fl(4)15s37m28M&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;This talk aims to show how raku provides the average coder (me) with a new practical alternative to Regexs and/or specialist recursive descent modules. It should illustrate how the combination of the raku built-in OO system and Grammars/Actions keeps the problem domain / problem solution in focus via code and visual examples.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8827">Steve Roe</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/grammar/attachments/slides/4889/export/events/attachments/grammar/slides/4889/rgnl_slides.pdf">Raku Grammar for Nav Lights</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.raku/grammar.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.raku/grammar.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#raku-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-grammar:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#raku-grammar:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13025.php">Submit feedback</link>
        </links>
      </event>
      <event id="12615">
        <start>10:50</start>
        <duration>00:45</duration>
        <room>D.raku</room>
        <slug>dependencymanagement</slug>
        <title>Free Software, Dependency Management, and what I got wrong at FOSDEM 21 </title>
        <subtitle/>
        <track>Raku</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Writing Free Software is very different from writing proprietary software for a huge software company like Google or Facebook – the team size, incentives, and likelihood of turnover are all completely different – and, as a result, the ideal languages are very different as well.  Or at least, this was the thesis for my 2021 FOSDEM talk "&lt;a href="https://archive.fosdem.org/2021/schedule/event/programming_lang_for_free_software/"&gt;Imagining the Ideal Language for Writing Free Software&lt;/a&gt;".&lt;/p&gt;

&lt;p&gt;Over the past year, however, I've concluded that this argument – while correct any many areas – does &lt;em&gt;not&lt;/em&gt; apply to dependency management.  When it comes to dependency management, writing Free Software isn't on the opposite end of the spectrum from writing code for Google — it's on the same end, but even further along.  This talk will elaborate on what I mean by that statement and discuss the implication I believe that this has for Raku.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7841">Daniel Sockwell</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.raku/dependencymanagement.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.raku/dependencymanagement.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#raku-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-dependencymanagement:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#raku-dependencymanagement:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12615.php">Submit feedback</link>
        </links>
      </event>
      <event id="13094">
        <start>11:35</start>
        <duration>01:00</duration>
        <room>D.raku</room>
        <slug>dataaquisition</slug>
        <title>Multi-language Data Wrangling and Acquisition Conversational Agents</title>
        <subtitle>Using Raku in data acquisition and wrangling</subtitle>
        <track>Raku</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this presentation we discuss the Conversational Agent (CA) designs for two closely related problem areas:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Data Acquisition Workflows (DAWs)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Data Transformation Workflows (DTWs)&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The CA perspective is taken mostly for exposition and didactic purposes. Nevertheless, we emphasise the practical applicability of the underlying designs and implementations.&lt;/p&gt;

&lt;p&gt;Although, operationally data acquisitions are prerequisite for data wrangling we discuss data wrangling first -- the corresponding DTWs designs and implementations are more mature and the related materials are more universal, applicable to multiple programming languages.&lt;/p&gt;</abstract>
        <description>&lt;h1&gt;Multi-language Data Wrangling and Acquisition Conversational Agents&lt;/h1&gt;

&lt;p&gt;Anton Antonov  &lt;br/&gt;
FOSDEM 2022&lt;/p&gt;

&lt;h2&gt;Abstract&lt;/h2&gt;

&lt;p&gt;In this presentation we discuss the Conversational Agent (CA) designs for two closely related problem areas:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Data Acquisition Workflows (DAWs)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Data Transformation Workflows (DTWs)&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The CA perspective is taken mostly for exposition and didactic purposes. Nevertheless, we emphasise the practical applicability of the underlying designs and implementations.&lt;/p&gt;

&lt;p&gt;Although, operationally data acquisitions are prerequisite for data wrangling we discuss data wrangling first -- the corresponding DTWs designs and implementations are more mature and the related materials are more universal, applicable to multiple programming languages.&lt;/p&gt;

&lt;h2&gt;Outline&lt;/h2&gt;

&lt;h3&gt;Data Wrangling&lt;/h3&gt;

&lt;p&gt;In the first part of the presentation we show and compare data wrangling examples in different programming languages using different packages.&lt;/p&gt;

&lt;p&gt;Here is a list of the programming languages and packages we consider:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Julia-DataFrames&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Python-pandas&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;R&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;R-tidyverse&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;WL&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;We look into the common data wrangling workflows and how we can design a conversational agent that translates natural language commands into data wrangling code for Julia, Python, R, SQL, WL.&lt;/p&gt;

&lt;p&gt;WL's external evaluator features are heavily utilized.&lt;/p&gt;

&lt;h3&gt;Data Acquisition Workflows&lt;/h3&gt;

&lt;p&gt;In the second part of the presentation we discuss the following facets of a data acquisition system:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Conversational Agent based on a Finite State Machine&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Gathering and utilizing metadata taxonomies&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The making of datasets recommender systems and search engines&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;In/for both R and WL&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Making (ingredient) variables queries&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Introspection queries&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Random data generation specifications&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Data obfuscation specifications&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Extensions to ML models acquisition workflows&lt;/p&gt;</description>
        <persons>
          <person id="8849">Anton Antonov</person>
        </persons>
        <attachments>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/dataaquisition/attachments/other/5106/export/events/attachments/dataaquisition/other/5106/FOSDEM_2022_mind_map">FOSDEM 2022 presentation mind-map</attachment>
        </attachments>
        <links>
          <link href="https://www.youtube.com/watch?v=3OUkSa-5vEk">(Improved) presentation recording</link>
          <link href="https://www.youtube.com/watch?v=wS1lqMDdeIY">Doing it like Cro (movie demo 7min)</link>
          <link href="https://github.com/antononcube/RakuForPrediction-book">"Raku for Prediction" book project at GitHub</link>
          <link href="https://conf.raku.org/talk/157">Raku for Prediction talk at TRC-2021</link>
          <link href="https://video.fosdem.org/2022/D.raku/dataaquisition.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.raku/dataaquisition.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#raku-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-dataaquisition:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#raku-dataaquisition:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13094.php">Submit feedback</link>
        </links>
      </event>
      <event id="12651">
        <start>12:35</start>
        <duration>00:25</duration>
        <room>D.raku</room>
        <slug>learninganalytics</slug>
        <title>Class learning analytics with Raku</title>
        <subtitle>How Raku helps improve learning in a cloud computing class at the University of Granada</subtitle>
        <track>Raku</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Rakulang is great not only as a scripting language, but also at the conceptual level, allowing you to map problem-domain concepts to data structures easily. This comes handy when you use a specific kind of learning procedure that needs to track general class progress as well as individual attainment levels in a very precise way. In this context, we have created a Raku mini-library and a series of scripts that give us information on how a whole class of Cloud Computing students is progressing, and allows to pinpoint choke points, hurdles to progress, as well as individuals who might have been left behind.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;We think that teaching software engineering should be just like software engineering, and in this context we have created a class with project-based learning, and objective-based learning. Students progress asynchronously through a series of objectives, with the student giving them individualized feedback on how to achieve those objectives.
Objectives fulfillment is public, and this gives us a storage platform on which to build a series of scripts that show us the general degree of attainment by the class, as well as how every individual students are doing. These scripts are, for the time being, run manually. In the near future they will be integrated in a learning analytics workfow using GitHub actions, reducing the amount of manual running as much as possible.
This, while not using a big amount of high-magic, shows how Raku expresiveness and whippipitude make the management of class extremely easy.&lt;/p&gt;</description>
        <persons>
          <person id="1263">Juan Julián Merelo</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/JJ/IV-21-22">Repo for the class</link>
          <link href="https://video.fosdem.org/2022/D.raku/learninganalytics.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.raku/learninganalytics.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#raku-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-learninganalytics:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#raku-learninganalytics:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12651.php">Submit feedback</link>
        </links>
      </event>
      <event id="13090">
        <start>14:00</start>
        <duration>00:40</duration>
        <room>D.raku</room>
        <slug>auth</slug>
        <title>Decentralized Authentication</title>
        <subtitle>Authentication and identification techniques on Ethereum blockchain</subtitle>
        <track>Raku</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Authentication is the «‎must-have» feature of every web application. Traditional centralized auth feature has the major disadvantage: if the authenticator is down, it affects on to all related services. In this talk I would like to discuss auth on Ethereum blockchain, go through its major benefits and introduce sample application with the decentralized authentication implemented in Raku.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Authentication module — «must-have» feature of modern web application.&lt;/p&gt;

&lt;p&gt;Traditionally the authenticator was integrated right into an application (web1.0). The user had to register and then, using a login (email) and a unique password, enter the personal account, post the comment or download the file. Credentials were stored on the web application server, and the flow of authentication, authorization and identification was managed by some module or service. This the sample of hyper centralized authentication.&lt;/p&gt;

&lt;p&gt;Built-in authenticators have been evolved to external third-party authenticators. In the era of global services and social networks (web2.0) the visitors (as well as the site owners) began to delegate authentication to corporations. At the back side of that process we had got the bloom of the phishing sites and an explicit target ads. In addition, there were the clear symptoms of centralization and de-anonymization.&lt;/p&gt;

&lt;p&gt;Blockchain (web3.0) has naturally become the third iteration in the evolution of authenticators. On the one hand, this technology provides a truly decentralized and transparent audit platform for the authentication, and on the other hand, it makes the authentication and identification flow much more anonymous.&lt;/p&gt;

&lt;p&gt;In this talk I will consider the main benefits of decentralized authentication on the Ethereum blockchain, discuss disadvantages and common attack vectors, talk about the integration tricks and demonstrate and briefly analyze a working example in Raku.&lt;/p&gt;

&lt;p&gt;This talk might be of interest to system architects, security software developers, Raku and Ethereum enthusiasts.&lt;/p&gt;</description>
        <persons>
          <person id="7555">Konstantin Narkhov</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://gitlab.com/pheix-research/talks/-/tree/main/fosdem/2022">Talk repository</link>
          <link href="https://video.fosdem.org/2022/D.raku/auth.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.raku/auth.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#raku-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-auth:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#raku-auth:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13090.php">Submit feedback</link>
        </links>
      </event>
      <event id="12330">
        <start>14:40</start>
        <duration>00:35</duration>
        <room>D.raku</room>
        <slug>backpan</slug>
        <title>Keeping the past to preserve the future</title>
        <subtitle>On the development of a BackPAN for Raku</subtitle>
        <track>Raku</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Raku ecosystem is growing at an impressive rate.  The Raku Programming Language allows developers to specify the exact version of a module that is needed in production.  This is a very good thing, and makes sysadmins all over the world pretty happy, as they know they can install new versions of modules without fear of breaking production code.&lt;/p&gt;

&lt;p&gt;However, developers can also &lt;em&gt;remove&lt;/em&gt; distributions from the ecosystem.  This presentation describes efforts to make sure that this will never become a problem for production.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7859">Elizabeth Mattijsen</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.raku/backpan.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.raku/backpan.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#raku-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-backpan:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#raku-backpan:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12330.php">Submit feedback</link>
        </links>
      </event>
      <event id="12614">
        <start>15:15</start>
        <duration>00:30</duration>
        <room>D.raku</room>
        <slug>simpletesting</slug>
        <title>Radically simple testing in Raku</title>
        <subtitle/>
        <track>Raku</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Some languages offer a very simple syntax for testing via assertion statements, for example with an &lt;code&gt;assert&lt;/code&gt; function that creates a simple test that passes if given a true value and fails for anything else.  This style of testing is admirably concise, but can lead to cryptic test messages that make it very difficult to determine what a test was attempting to check without opening up the file containing the failing test.  At the other extreme, it's possible to write very expressive tests with a fluent, method-chaining API.  For example, using the Chai.js assertion library, a test might read &lt;code&gt;beverages.should.have.property('tea').with.lengthOf(3)&lt;/code&gt;.  This allows tests to automatically generate much more useful messages but comes at the cost of creating a fairly complex test API with many new methods to learn.&lt;/p&gt;

&lt;p&gt;Raku's core Test module falls somewhere between these two extremes – it offers an API with a handful of functions that's easier to learn than a full fluent API but more expressive than simple &lt;code&gt;assert&lt;/code&gt; statements.  This is a sensible compromise.&lt;/p&gt;

&lt;p&gt;But I claim (assert?) that, with a bit of metaprogramming trickery, Raku lets us have the best of both worlds: we can have a zero-learning-curve test API that's just as simple as assert statements while &lt;em&gt;also&lt;/em&gt; being just as expressive as a long chain of method calls in a fluent style.  I'll present this style of testing, discuss its use in Raku, and consider ways in which Raku lets us improve on the status quo.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7841">Daniel Sockwell</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.raku/simpletesting.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.raku/simpletesting.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#raku-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-simpletesting:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#raku-simpletesting:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12614.php">Submit feedback</link>
        </links>
      </event>
      <event id="12965">
        <start>15:45</start>
        <duration>00:50</duration>
        <room>D.raku</room>
        <slug>github</slug>
        <title>GitHub Actions (in|for) Raku</title>
        <subtitle>Containerizing Raku for testing and other automation tasks</subtitle>
        <track>Raku</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;GitHub has a nice environment for carrying out repository-event triggered workflows; these use a variety of runner platforms, including containers. This talk is about how to create a Raku container that can successfully act as a runner for workflows, and how to Rakuize the workflow API so that Raku scripts can interact meaningfully with this environment.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;There are two parts on this talk; first, how to create a chain of increasingly complex Raku containers that can be used mainly for testing, and second, how to run some Raku scripts within those containers, with cool things that can be done inside those workflow using Raku.&lt;/p&gt;</description>
        <persons>
          <person id="1263">Juan Julián Merelo</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/JJ/docker-raku">Base container for Raku </link>
          <link href="https://video.fosdem.org/2022/D.raku/github.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.raku/github.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#raku-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-github:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#raku-github:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12965.php">Submit feedback</link>
        </links>
      </event>
      <event id="12742">
        <start>16:35</start>
        <duration>01:00</duration>
        <room>D.raku</room>
        <slug>rsc</slug>
        <title>Raku Steering Council Q&amp;A Panel</title>
        <subtitle>RSC members to answer live questions.</subtitle>
        <track>Raku</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Raku Steering Council Q&amp;amp;A panel is aimed at the audience interested in the Raku® programming language, its current state, and its future. Members of the Council will try to answer any related questions, including those about the Council itself.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1263">Juan Julián Merelo</person>
          <person id="2965">Stefan Seifert (nine)</person>
          <person id="7841">Daniel Sockwell</person>
          <person id="7859">Elizabeth Mattijsen</person>
          <person id="8627">Vadim Belman</person>
          <person id="8995">Geoffrey Broadwell</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.raku/rsc.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.raku/rsc.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#raku-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#raku-rsc:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#raku-rsc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12742.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.retro">
      <event id="13129">
        <start>10:00</start>
        <duration>00:05</duration>
        <room>D.retro</room>
        <slug>retro_intro</slug>
        <title>Welcome to Retro-Computing devroom</title>
        <subtitle>Vintage everywhere!</subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A brief introduction to our devroom and the schedule ahead.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="666">Pau Garcia Quiles (pgquiles)</person>
          <person id="3587">François Revol (mmu_man)</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/retro_intro/attachments/slides/4957/export/events/attachments/retro_intro/slides/4957/FOSDEM2022_Retro_Intro.odf">Slides (PDF)</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/retro_intro/attachments/slides/4958/export/events/attachments/retro_intro/slides/4958/FOSDEM2022_Retro_Intro.odp">Slides (ODP)</attachment>
        </attachments>
        <links>
          <link href="https://lists.fosdem.org/listinfo/retrocomputing-devroom">Retro devroom mailing list (if you want to help)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_intro.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_intro.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_intro:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_intro:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13129.php">Submit feedback</link>
        </links>
      </event>
      <event id="12360">
        <start>10:05</start>
        <duration>00:25</duration>
        <room>D.retro</room>
        <slug>retro_chess</slug>
        <title>Getting 1K Chess for the ZX81 online</title>
        <subtitle>Or, how I used $2 Billion of internet infrastructure to run 672 bytes of code, from 1982</subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In 1982, David Horne wrote a version of chess which managed to fit inside the memory of a 1K ZX81. Although it wasn't a complete implementation, it was impressive enough to be remembered now, almost 40 years later. But running it in 2022 requires at least an emulator, ROM file, and the .P file, which limits the appeal to retro enthusiasts and excludes the intended audience - chess players!&lt;/p&gt;

&lt;p&gt;So, I modified the EMF emulator (and the game) to run as an emulator-as-a-service, so that it can be played via the lichess servers with a modern web-friendly interface.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk I'll cover a brief history of the program, how the emulator was modified, how the program was reverse engineered and understood, how this code connects to the lichess server and, most crucially, why someone would do it!&lt;/p&gt;

&lt;p&gt;Along the way we'll look at the chess notation, FEN, Z80 assembler, NDJSON, and a few other pieces to show you the complete puzzle fits together.&lt;/p&gt;</description>
        <persons>
          <person id="392">Steven Goodwin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://marquisdegeek.com/code_chessbots.php">A few notes</link>
          <link href="https://github.com/MarquisdeGeek/LichessBots">Lichess bots for beginners</link>
          <link href="https://unbound.com/books/20goto10/">20 GOTO 10 : The book</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_chess.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_chess.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_chess:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_chess:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12360.php">Submit feedback</link>
        </links>
      </event>
      <event id="13029">
        <start>10:30</start>
        <duration>00:45</duration>
        <room>D.retro</room>
        <slug>retro_serial</slug>
        <title>Let's Get Serial!</title>
        <subtitle>Histroy and current state of everyone's favourite interface</subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The 'serial port,' usually carrying RS-232, has once been the window to the world on capable systems. This talk is a brief history on it, its use cases and its current state. Is it still relevant? Do we still love it? Are there alternatives?&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8805">Stephan Hohmann</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/retro_serial/attachments/slides/5095/export/events/attachments/retro_serial/slides/5095/FOSDEM_2022_Lets_Get_Serial.pdf">FOSDEM 2022 — Let's Get Serial!</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.retro/retro_serial.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_serial.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_serial:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_serial:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13029.php">Submit feedback</link>
        </links>
      </event>
      <event id="12766">
        <start>11:15</start>
        <duration>00:45</duration>
        <room>D.retro</room>
        <slug>retro_apple1</slug>
        <title>Made by Woz: how Apple-1 operating system works?</title>
        <subtitle>Brilliant Steve Wozniak’s code every software engineer should know</subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Operating system of Apple-1 written by Steve Wozniak is an engineering piece of art – 256 bytes only! We will explain how it works using the original 6502 assembler source code along with our own rewritten in Python version so every software engineer could understand how It works. It should be useful for engineers who want to know basics of operating systems.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;We will cover:
– what are the functions of the simplest operating system
– what functions of operating system are hardware-specific
– how it communicates with the user
– how it runs the programs&lt;/p&gt;</description>
        <persons>
          <person id="8533">Sergey Panarin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/smartykit/apple1/blob/master/ROM%20development/Woz_Monitor.asm">Operating system of Apple-1 by Steve Wozniak</link>
          <link href="https://discord.gg/ynmSdRXc">Discord for Woz OS Q&amp;A</link>
          <link href="https://youtu.be/rniZDdS6toI">Running Woz OS on emulator</link>
          <link href="https://github.com/smartykit/apple1/tree/master/Emulator_Pom1">Apple-1 emulator to run Woz OS</link>
          <link href="https://github.com/smartykit/apple1/tree/master/ROM%20development">SmartyKit ROM with Woz OS to use in emulator</link>
          <link href="https://github.com/smartykit/apple1/blob/master/WozOS.py">Woz OS in Python (high-level view)</link>
          <link href="https://www.twitter.com/spanarin">Sergey Panarin's Twitter</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_apple1.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_apple1.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_apple1:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_apple1:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12766.php">Submit feedback</link>
        </links>
      </event>
      <event id="12722">
        <start>12:00</start>
        <duration>01:25</duration>
        <room>D.retro</room>
        <slug>retro_museum</slug>
        <title>A Computer Museum</title>
        <subtitle>Why and how? </subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The HomeComputerMuseum is founded in 2018 after its initial plan in 2016. The idea of an interactive computer museum while being a social company and fully independent of subsidy. In 2020, right after a move to a bigger and more permanent location, the unsubsidized museum had to deal with corona. Against all odds, the museum survived and even grew faster than ever before, becoming world's largest museum on social media and collaborating with museums all over the world. This all with a social impact by helping people with a distance to the labor market. The museum has an unique collection which can not be found anywhere else and it only keeps on growing in impact. Currently (early 2022) being the computer heritage expert for the Dutch government.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The HomeComputerMuseum opened its door on March 17, 2018 and went nearly bankrupt by the end of 2018. But we pulled through and from the beginning of 2019, we managed to turn it around. Starting with a collection of roughly 35 computers, 4 active board members, 3 volunteers and an empty building without electricity we built the museum. By the end of 2021 we have over 500 computers in the active museum and another +/- 2500 computers in storage. 1500 CD-i titles, 2203 boxed PC games, over 4000 unique software titles and over 3000 manuals. Open 7 days a week in a 1090m2 location in the city center of Helmond with 40 volunteers and 6 board members. All without big sponsors and no subsidy we are researching the history, sharing the history, recreating the history by allowing everyone to use the old computers. From the only working Aesthedes2 (which is repaired by in-house technicians) to the computer used for the movie Titanic. We do digital heritage (read old media) and offer repairs to both new and old computers. We created a functioning business model that is world renowned and ready for anything to come and we love to share what we went through and why we are considered as an essential part of the Dutch heritage.. all in less than 4 years.&lt;/p&gt;</description>
        <persons>
          <person id="8700">Bart van den Akker</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.homecomputermuseum.nl/en/">Website</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_museum.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_museum.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_museum:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_museum:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12722.php">Submit feedback</link>
        </links>
      </event>
      <event id="12904">
        <start>13:25</start>
        <duration>00:30</duration>
        <room>D.retro</room>
        <slug>retro_trajectware</slug>
        <title>Trajectware - timeline-based navigation across computing heritage</title>
        <subtitle/>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The history of calculation, information processing and computation is very rich. It is driving the industrial revolution and digital transformation of our world. This history is composed of many events related to conceptual and technological breakthroughs. In order to help in the analysis (by researchers) and explanation (to citizens), the NAM-IP Computer Museum is actively developing the "Trajectware" Open Source framework based on a the structuration of illustrated events in the form of timeline fragments that can be explored using various navigation operations to focus on specific periods, aspects (technological, conceptual, cultural, contextual,...) or the involved people/organisations.&lt;/p&gt;

&lt;p&gt;This talk is intended to everyone. It will first present the global design based on (1) a knowledge base back-end inspired by different ontology standards (SEM, DOLCE/Spatial History Ontology, Constructed Past Theory, DBPedia) and accessed through queries and/or a specific API to extract a relevant timeline, and (2) a navigation front-end, currently based on ReactNative. Different timeline navigation features will be illustrated on a concrete application case: the "micro-computer, meg@ revolution" exhibition of the NAM-IP museum.&lt;/p&gt;

&lt;p&gt;Through our presentation, we hope to trigger interesting discussion about our current work and to gather suggestions and interests to grow this project !&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3079">Christophe Ponsard</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/retro_trajectware/attachments/slides/5015/export/events/attachments/retro_trajectware/slides/5015/FOSDEM22_Trajectware_V3.pdf"/>
        </attachments>
        <links>
          <link href="https://github.com/NAMIP-Computer-Museum/guideApp">Trajectware on Github</link>
          <link href="https://drive.google.com/file/d/17YhNBCE-d_gmcUPEi_gO5CmNyrL9eU7B">Android APK (museum guide)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_trajectware.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_trajectware.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_trajectware:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_trajectware:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12904.php">Submit feedback</link>
        </links>
      </event>
      <event id="13112">
        <start>13:55</start>
        <duration>00:35</duration>
        <room>D.retro</room>
        <slug>retro_ewaste_reveng</slug>
        <title>Hack for the Planet</title>
        <subtitle>Reverse Engineering Embedded Systems to Reduce E-Waste</subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The lecture will discuss reverse engineering e-waste. It will shortly present the open source hardware tools that are used internally at Unbinare and how these are used when the aim is to reduce e-waste.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8852">Maurits Fennis</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://unbina.re">website</link>
          <link href="https://unbinare.be">wiki</link>
          <link href="https://hackaday.com/2022/01/06/remoticon-2021-unbinare-brings-a-reverse-engineering-toolkit-into-recycling/">Hackaday feature</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_ewaste_reveng.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_ewaste_reveng.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_ewaste_reveng:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_ewaste_reveng:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13112.php">Submit feedback</link>
        </links>
      </event>
      <event id="13026">
        <start>14:30</start>
        <duration>01:00</duration>
        <room>D.retro</room>
        <slug>retro_pkgsrc</slug>
        <title>Keeping old Unix/Linux up-to-date with pkgsrc</title>
        <subtitle>Keeping software on unsupported Unix-ish operating systems up-to-date</subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Sometimes good working hardware is obsoleted by missing update support for the operating systems. Using outdated networking software from these systems on today's Internet is a security risk (to the user and the Internet as a whole), and old software might fail altogether (old SSH clients can't connect to modern SSH server, Webbrowser can't load websites using modern transport encryption, TLS).&lt;/p&gt;

&lt;p&gt;pkgsrc is a cross-platform package manager maintained by the NetBSD project. With pkgsrc, it is possible to compile and install modern Linux/Unix tools and applications on Unix systems that were abandoned by their makers.&lt;/p&gt;

&lt;p&gt;In this talk, I will give my experience, tips and tricks with keeping old Unix systems up-to-date:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;MacOS X PowerPC 10.4 "Tiger"&lt;/li&gt;
&lt;li&gt;MacOS X i686 10.9 "Mavericks"&lt;/li&gt;
&lt;li&gt;Ubuntu 10.04 on ARM (old Linux 2.6.x kernel with special hardware patches that never got upstream)&lt;/li&gt;
&lt;li&gt;Slackware Linux on Pentium 2&lt;/li&gt;
&lt;li&gt;Solaris 9 on SUN Ultra 5&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="8234">Carsten Strotmann</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://pkgsrc.org">pkgsrc Homepage</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_pkgsrc.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_pkgsrc.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_pkgsrc:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_pkgsrc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13026.php">Submit feedback</link>
        </links>
      </event>
      <event id="12744">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.retro</room>
        <slug>retro_aosc</slug>
        <title>AOSC OS/Retro - An Introduction</title>
        <subtitle>An Ongoing Quest for the Possibility of Modern Linux on Vintage Hardware</subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this presentation, I will share our community's ongoing exploration of running modern and "standard" Linux distributions on vintage hardware - AOSC OS/Retro. AOSC OS/Retro, as an official branch of AOSC OS (the modern-device-facing mainline), runs a generally similar feature set - systemd, Glibc/Binutils/GCC/Coreutils/Util-Linux, X.org/Mesa, etc. and shares the same source tree with the latter.&lt;/p&gt;

&lt;p&gt;With over a year of spending our spare time on the project, tweaking features, designing a desktop experience, and optimising compiler flags, we have a usable distribution that could run on systems as slow as a 486SX, and as fast as "modern" Core Duo systems. We also have an active effort to port AOSC OS/Retro across multiple architectures, with the tally currently standing at eight architectures - and counting (alpha, armv4, armv6hf, armv7hf, i486, loongson2f, powerpc, ppc64). We still have a long list of issues to solve, such as login delays and throttled I/O on ISA-based systems. I hope to gather feedback and criticism through this presentation.&lt;/p&gt;</abstract>
        <description>&lt;ul&gt;
&lt;li&gt;What is AOSC OS (self introduction)?&lt;/li&gt;
&lt;li&gt;What is AOSC OS/Retro (and how it differs from AOSC OS)?&lt;/li&gt;
&lt;li&gt;Design Goals and Self-Afflicted Agonies&lt;/li&gt;
&lt;li&gt;Application Stack and Software Selection&lt;/li&gt;
&lt;li&gt;End Results (so far)&lt;/li&gt;
&lt;li&gt;Thoughts, Reflections, and Questions&lt;/li&gt;
&lt;li&gt;Q&amp;amp;A&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="8602">Mingcong Bai</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/retro_aosc/attachments/slides/5016/export/events/attachments/retro_aosc/slides/5016/20210113_slides.pdf">Slides (PDF)</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/retro_aosc/attachments/slides/5017/export/events/attachments/retro_aosc/slides/5017/20210113_slides.odp">Slides (ODP)</attachment>
        </attachments>
        <links>
          <link href="https://aosc.io/">Website</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_aosc.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_aosc.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_aosc:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_aosc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12744.php">Submit feedback</link>
        </links>
      </event>
      <event id="13005">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.retro</room>
        <slug>retro_flash</slug>
        <title>Old Web Today: Keeping Flash (and other) Retro Web Sites Accessible on the modern web</title>
        <subtitle>Techniques for combining web archives and emulation using FOSS tools.</subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;It's been just over a year since all browsers dropped support for Flash, but much Flash content continue to exist both in web archives and on the live web. This presentation will cover various techniques tried by the Webrecorder project to keep Flash content still working in today's browsers, such as running old browsers in containers, running full system emulation in WebAssembly, and using the Ruffle emulator. We will cover the trade-offs between these approaches and the current challenges in combining web archives and emulation, and present the tools we have built to make these approaches possible.&lt;/p&gt;

&lt;p&gt;As one of the options, will also talk about the OldWeb.today project (https://oldweb.today/) which provides several JS-based emulation connected to web archives, how it works and how it can be used to run not only Flash, but also old Java applets that may exist in web archives.&lt;/p&gt;

&lt;p&gt;We will leave time for a Q&amp;amp;A session to answer any questions about the tools and how they could be improved!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8815">Ilya Kreymer</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/retro_flash/attachments/slides/5174/export/events/attachments/retro_flash/slides/5174/oldweb_today_slides.pdf">OldWeb.today Presentation Slides</attachment>
        </attachments>
        <links>
          <link href="https://oldweb.today/">OldWeb Today JS Emulator</link>
          <link href="https://github.com/oldweb-today/oldweb.today">Source for oldweb.today</link>
          <link href="https://webrecorder.net/2020/12/23/new-oldweb-today.html">Blog post about OldWeb.tody</link>
          <link href="https://gitlab.com/emulation-as-a-service/eaas-proxy">EaaS Web Network (used in oldweb.today)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_flash.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_flash.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_flash:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_flash:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13005.php">Submit feedback</link>
        </links>
      </event>
      <event id="13001">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.retro</room>
        <slug>retro_frogfind</slug>
        <title>FrogFind and 68k News</title>
        <subtitle>Building Modern Web Portals for Vintage Machines</subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk will cover the creation of two web portals, which use open source libraries to make much of the modern web accessible to vintage machines and old web browsers. By using the Readability library, along with some haphazard PHP, I was able to take modern sites down to text content and HTML 1.1 on the server side. FrogFind.com serves as a web portal for limited browsers, such as old versions of Mosiac, or even text browsers like Contiki's on an Apple ][, to make much of the web's content accessible to them in a perfectly readable way.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;It is often said that the modern internet has left vintage computers behind. However, it is not the internet - it is the complexity of content. One way of bringing vintage machines to the modern web is through upgrades and accelerators. This creates a moving target of machines that will still age-out of sufficient upgrade-ability as the web continues to evolve. Another option is to deconstruct the modern web to make it accessible to vintage computers.&lt;/p&gt;

&lt;p&gt;Using an open source library called Readability and some haphazard PHP, I've built two web portals: 68k.news and FrogFind.com. These sites allow vintage machine to view many websites as text-only, by stripping out complicated HTML and scripts and delivering HTML 1.1 content to old browsers, with images optional.&lt;/p&gt;

&lt;p&gt;This talk will cover the idea behind these portals, their use, and just how usable and pleasant a vintage machine can become for daily internet content consumption without the distractions of the modern web.&lt;/p&gt;</description>
        <persons>
          <person id="8472">Sean Malseed</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="http://frogfind.com">frogfind.com</link>
          <link href="http://68k.news">68k.news</link>
          <link href="https://www.youtube.com/watch?v=c_v2_vTogS8">[Youtube] I Rebuilt the Entire Internet... for Vintage Computers</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_frogfind.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_frogfind.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_frogfind:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_frogfind:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13001.php">Submit feedback</link>
        </links>
      </event>
      <event id="12483">
        <start>17:00</start>
        <duration>01:00</duration>
        <room>D.retro</room>
        <slug>retro_spreadsheets</slug>
        <title>A Brief History of Spreadsheets</title>
        <subtitle>From LANPAR to VisiCalc to Lotus to LibreOffice</subtitle>
        <track>Retrocomputing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Have you ever wondered why spreadsheets look and act that way? Why does LibreOffice and Excel use letters for columns and numbers for rows? In this high energy presentation, Jim Hall will discuss a brief history of spreadsheets, from LANPAR to VisiCalc to Lotus 1-2-3 to LibreOffice. A great history lesson and practical demonstration.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The first 'spreadsheet' program was LANPAR, which invented the interactive concept of working with values and originated the idea of forward referencing. But the spreadsheet as you might recognize it today started with VisiCalc on the Apple II. We'll explore several favorite DOS spreadsheets as we review a history of spreadsheets, including: VisiCalc, Lotus 1-2-3, As Easy As, Quattro Pro, .. to to understand why modern spreadsheets like LibreOffice Calc look and act that way.&lt;/p&gt;</description>
        <persons>
          <person id="7938">Jim Hall</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.retro/retro_spreadsheets.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.retro/retro_spreadsheets.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#retro-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#retro-retro_spreadsheets:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#retro-retro_spreadsheets:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12483.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.safety">
      <event id="12702">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>D.safety</room>
        <slug>safety_subplot_documenting_your_criteria_for_success</slug>
        <title>Subplot - documenting your criteria for success</title>
        <subtitle>Expressing argumentation in a validatable way</subtitle>
        <track>Safety and Open Source</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Believing a system is safe is not the same as knowing it meets all
the criteria defined to demonstrate that safety. Too often is the
argumentation around the safety of a system presented as a document
for humans to agree on, which is disconnected from the mechanism of
asserting compliance with that argumentation.  Subplot is a tool for
processing documents containing such argumentation along with
verification scenarios which are both human &lt;em&gt;and&lt;/em&gt; machine readable
so that this disconnect can be resolved.&lt;/p&gt;

&lt;p&gt;This talk introduces Subplot and describes the concept.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Software engineers usually understand requirements and testing against
requirements.  All too often though, those responsible for the safety of
a system do not understand how to express requirements which can be
understood by engineers, such that the system can be verified.  This
could be for a myriad reasons, but usually it is due to a gulf between
those who are specifying how to determine that a system is safe, and those
who are implementing the system.&lt;/p&gt;

&lt;p&gt;Subplot demonstrates how stakeholders at all stages of system design and
implementation can come together to maintain a document which describes the
criteria which, if met, demonstrate compliance with the safety argumentation
made about the system.  This document can then be rendered as a PDF or some
stand-alone HTML for presentation to non-engineer stakeholders for confirmation.&lt;/p&gt;

&lt;p&gt;Subplot can also generate a test program, from such a document, that when run will
perform all of the verification scenarios contained in the document and produce a
final report.&lt;/p&gt;

&lt;p&gt;While Subplot is fairly new software, still under active development,
the concepts in Subplot are built on those explored in a decade-old
previous project, by the same authors, which considered similar problems purely
from a software engineering perspective, used a similar Gherkin-inspired language
and Markdown input structure, and was used in a variety of projects for
paying customers; proving the concept works.&lt;/p&gt;

&lt;p&gt;Subplot is a refinement of this older implementation.&lt;/p&gt;</description>
        <persons>
          <person id="8692">Daniel Silverstone</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://subplot.liw.fi/">Subplot website</link>
          <link href="https://gitlab.com/subplot/subplot.git">Subplot Gitlab page</link>
          <link href="https://video.fosdem.org/2022/D.safety/safety_subplot_documenting_your_criteria_for_success.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.safety/safety_subplot_documenting_your_criteria_for_success.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#safety-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#safety-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#safety-safety_subplot_documenting_your_criteria_for_success:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#safety-safety_subplot_documenting_your_criteria_for_success:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12702.php">Submit feedback</link>
        </links>
      </event>
      <event id="13056">
        <start>11:00</start>
        <duration>00:45</duration>
        <room>D.safety</room>
        <slug>safety_dont_trust_us_trust_the_math_behind_immudb</slug>
        <title>Don't trust us, trust the math behind immudb</title>
        <subtitle>How immudb protects safety critical data (with math and cryptography)</subtitle>
        <track>Safety and Open Source</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Immutability is a powerful concept. Without it we wouldn’t be able to rely on bank transactions, medical records or even some of our private data.
And we usually take for granted that our data is safe somewhere out there in the "cloud". But is it?
There are well-known multi-billion dollar stories where attackers were able to break into well-secured systems and modify data stored in databases.&lt;/p&gt;

&lt;p&gt;What if there was a way to protect the immutability with math? What if any attempt of historical data manipulation could easily be detected?
In this talk I’ll share how we do it in immudb - a new database built on a zero-trust model.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8828">Bartłomiej Święcki</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/safety_dont_trust_us_trust_the_math_behind_immudb/attachments/slides/5117/export/events/attachments/safety_dont_trust_us_trust_the_math_behind_immudb/slides/5117/FOSDEM_2022_Immudb.pdf"/>
        </attachments>
        <links>
          <link href="https://immudb.io">immudb homepage</link>
          <link href="https://github.com/codenotary/immudb">immudb github project</link>
          <link href="https://docs.immudb.io/">immudb documentation</link>
          <link href="https://video.fosdem.org/2022/D.safety/safety_dont_trust_us_trust_the_math_behind_immudb.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.safety/safety_dont_trust_us_trust_the_math_behind_immudb.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#safety-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#safety-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#safety-safety_dont_trust_us_trust_the_math_behind_immudb:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#safety-safety_dont_trust_us_trust_the_math_behind_immudb:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13056.php">Submit feedback</link>
        </links>
      </event>
      <event id="13059">
        <start>12:00</start>
        <duration>00:45</duration>
        <room>D.safety</room>
        <slug>safety_designing_a_new_language_for_safety_fuzion</slug>
        <title>Designing a new Language for Safety: Fuzion</title>
        <subtitle>A minimal language for safety-critical systems</subtitle>
        <track>Safety and Open Source</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Fuzion is a modern general purpose programming language that unifies concepts
found in structured, functional and object-oriented programming languages into
the concept of a Fuzion feature.  It combines a powerful syntax and safety
features based on the design-by-contract principle with a simple intermediate
representation that enables powerful optimizing compilers and static analysis
tools to verify correctness aspects.&lt;/p&gt;

&lt;p&gt;This talk will focus on Fuzion's aspects related to safety-critical software
development.  A fundamental idea of Fuzion is to provide a simple language at a
high level of abstraction and move implementation decisions from the developer
to the compiler. To enable this, the language defines a simple but powerful
intermediate representation for static analysis tools to operate on.&lt;/p&gt;

&lt;p&gt;Furthermore, pre- and post-conditions for design-by-contract are provided in a
way that enables different levels of verification: static analysis as well as
dynamic checks at different levels from safety to debugging.&lt;/p&gt;

&lt;p&gt;Fuzion does not support exceptions, a run-time error has to be part of the result
of a call and must be checked explicitly.  Fuzion does not support dynamic
loading of code. Numeric operations such as 'infix +' check for overflow.&lt;/p&gt;

&lt;p&gt;Fuzion applications consist of a set of library modules and a main modules.
Modules are verified for correctness individually as well as whole
applications. This is possible since dynamic loading of code is not supported.&lt;/p&gt;</abstract>
        <description>&lt;h1&gt;Introduction&lt;/h1&gt;

&lt;p&gt;Fuzion is a modern general purpose programming language that unifies concepts
found in structured, functional and object-oriented programming languages into
the concept of a Fuzion feature.  It combines a powerful syntax and safety
features based on the design-by-contract principle with a simple intermediate
representation that enables powerful optimizing compilers and static analysis
tools to verify correctness aspects.&lt;/p&gt;

&lt;p&gt;Fuzion was influenced by many other languages including Java, Python, Eiffel,
Rust, Go, Lua, Kotlin, C#, F#, Nim, Julia, Clojure, C/C++, and many more.  The
goal of Fuzion is to define a language that has the expressive power present in
these languages and allow high-performance implementations and powerful analysis
tools.  Furthermore, Fuzion addresses requirements for safety-critical
applications by adding support for contracts that enable formal specification and
enable detailed control over run-time checks.&lt;/p&gt;

&lt;p&gt;Many current programming language are getting more and more overloaded with new
concepts and syntax to solve particular development or performance issues.
Languages like Java/C# provide classes, interfaces, methods, packages, anonymous
inner classes, local variables, fields, closures, etc.  And these languages are
currently further extended by the introductions of records/structs, value types,
etc.  The possibility of nesting these different concepts results in
complexity for the developer and the tools (compilers, VMs) that process and
execute the code.&lt;/p&gt;

&lt;p&gt;For example, the possibility to access a local variable as part of the closure
of a lambda expression may result in the compiler allocating heap space to hold
the contents of that local variable.  Hence, the developer has lost control over
the allocation decisions made by the compiler.&lt;/p&gt;

&lt;p&gt;In Fuzion, the concepts of classes, interfaces, methods, packages, fields and
local variables are unified in the concept of a Fuzion feature. The decision
where to allocate the memory associated with a feature (on the heap, the stack
or in a register) is left to the compiler just as well as the decision if
dynamic type information is needed.  The developer is left with the single
concept of a feature, the language implementation takes care of all the rest.&lt;/p&gt;

&lt;h1&gt;Fuzion Feature Declarations&lt;/h1&gt;

&lt;p&gt;A Fuzion feature has a name, similar to the name of a class or a function.
The main operation that can be performed on a feature is a feature call.  The
constituents of a feature declaration are as follows:&lt;/p&gt;

&lt;h2&gt;Formal Arguments&lt;/h2&gt;

&lt;p&gt;Features may have a list of formal arguments, which are themselves features
implemented as fields.  On a call to a feature with formal arguments, actual
arguments have to be provided to the call, unless the list of formal arguments
is empty.&lt;/p&gt;

&lt;h2&gt;Feature Result&lt;/h2&gt;

&lt;p&gt;The result of a feature call is an instance of the feature.  Alternatively, a
feature may declare a different result type, then it must return a value of that
type on a call.&lt;/p&gt;

&lt;h2&gt;Closures&lt;/h2&gt;

&lt;p&gt;Features are nested, i.e., every feature is declared within the context of an
outer feature.  The only exception is the universe, which is the outermost
feature in Fuzion.  A feature can access features declared in its
outer feature or, recursively, any outer feature of these outer features.  This
means, a feature declaration also defines a closure of the feature and its
context.&lt;/p&gt;

&lt;p&gt;When calling a feature &lt;em&gt;f1&lt;/em&gt; declared as an inner feature of &lt;em&gt;f2&lt;/em&gt;, the call must
include a target value which is the result of a call to &lt;em&gt;f2&lt;/em&gt;, e.g., &lt;em&gt;f2.f1&lt;/em&gt;.&lt;/p&gt;

&lt;h2&gt;Generics&lt;/h2&gt;

&lt;p&gt;Features may have generic type parameters. E.g. a feature declaration may leave
the actual type used within that feature open and to be defined by the user of
the feature.&lt;/p&gt;

&lt;p&gt;The list of generic type parameters may be open, i.e., the number of actual
generic type parameters is not fixed at feature declaration.  This turns out to
be useful in the declaration of choice types and functions as explained below.&lt;/p&gt;

&lt;h2&gt;Inheritance&lt;/h2&gt;

&lt;p&gt;Fuzion features can inherit from one or several other features.  When inheriting
from an existing features, all inner features of the parent automatically become
inner features of the heir feature.  It is possible to redefine inherited
features.  In particular, when inheriting from a feature with abstract inner
features, one can implement the inherited abstract features.&lt;/p&gt;

&lt;p&gt;A redefinition of an inherited feature may implement an inherited feature as a
routine or as a field.  An inherited feature that is implemented as a field,
however, cannot be redefined as something else since fields might be mutable.&lt;/p&gt;

&lt;p&gt;Inheritance may result in conflicts. An example would be two features with the
same name that are inherited from two different parents.  In this case, the heir
must resolve the conflict either by redefining the inherited features and
providing a new implementation or by renaming the inherited features resulting
in two inner features in the heir feature.&lt;/p&gt;

&lt;p&gt;Inheritance and redefinition in Fuzion does not require dynamic binding.  By
default, the types defined by features are value types and no run-time overhead
for dynamic binding is imposed by inheritance.&lt;/p&gt;

&lt;h2&gt;A Contract&lt;/h2&gt;

&lt;p&gt;A feature may declare a contract that specifies what the features does and under
which conditions the feature may be called.&lt;/p&gt;

&lt;h2&gt;An implementation&lt;/h2&gt;

&lt;p&gt;Features must have one of the following implementations&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;a routine is a feature implementation with code that is executed on a call&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;a field is a memory slot that stores a value and whose contents are returned on a call&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;an abstract feature has no implementation and cannot be called directly, but can be implemented by heir features&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;an intrinsic feature is a low-level feature implemented by the compiler or
run-time system, e.g., the infix + operator to add two 32-bit integer values
may be an intrinsic operation.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;A feature implemented as a routine can contain inner feature declarations.&lt;/p&gt;

&lt;h1&gt;Feature examples&lt;/h1&gt;

&lt;p&gt;Here is an example that declares a feature &lt;em&gt;point&lt;/em&gt; that functions similar to a
struct or record in other languages:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;point(x, y i32) is # empty
p1 := point 3 4
say "p1.x is {p1.x}"    # will print "p1.x is 3"
say "p1.y is {p1.y}"    # will print "p1.y is 4"
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The next example shows a feature &lt;em&gt;base&lt;/em&gt; that provides an inner feature &lt;em&gt;plus&lt;/em&gt;
that adds its argument to the value passed to the enclosing base:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;base(v i32) is
  plus(w i32) =&amp;gt; v + w

b1 := base 30
b2 := base 100
say (b1.plus 23)    # will print "53"
say (b2.plus 23)    # will print "123"
&lt;/code&gt;&lt;/pre&gt;

&lt;h1&gt;Design-by-Contract&lt;/h1&gt;

&lt;p&gt;Fuzion features can be equipped with pre- and post-conditions to formally
document the requirements that must be met when a feature is called and the
guarantees given by a feature.  An example is a feature that implements a square
root function for 32-bit integers:&lt;/p&gt;

&lt;p&gt;  sqrt(a i32) i32&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;pre
  safety: a &amp;gt;= 0
post
  debug: result * result &amp;lt;= a,
  debug: (result + 1) &amp;gt; a / (result + 1),
  debug: result &amp;gt;= 0
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;  is&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;if a == 0
  0
else
  for
    last := 0, r
    r    := 1, (last +^ a / last) / 2         # +^ performs saturating addition
  until r == last
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;In this case, the function defines the pre-condition that its argument
'a' is non-negative.  A call of this function with a negative value will
result in a run-time error.  On the other hand, its post-conditions make a clear
statement about the result: The result will be the largest value that, when
squared, is less than or equal to 'a'.&lt;/p&gt;

&lt;h2&gt;Checking Pre- and Post-conditions&lt;/h2&gt;

&lt;p&gt;Pre- and post-conditions can be classified for different purposes.  Default
qualifiers provided in the standard library are&lt;/p&gt;

&lt;h3&gt;safety&lt;/h3&gt;

&lt;p&gt;   This qualifier protects pre-conditions that are required for the safety of an operation.&lt;/p&gt;

&lt;p&gt;   An example is the index check pre-condition of the intrinsic operation to
   access an element of an array: Not performing the index check would allow
   arbitrary memory accesses and break the application's safety.&lt;/p&gt;

&lt;p&gt;   This qualifier should therefore never be disabled unless you are running code
   in an environment where performance is essential and safety is irrelevant.&lt;/p&gt;

&lt;h3&gt;debug, debug(n)&lt;/h3&gt;

&lt;p&gt;   This qualifier is generally for debugging, it is set iff debugging is
   enabled or enabled at the given level, respectively..&lt;/p&gt;

&lt;h3&gt;pedantic&lt;/h3&gt;

&lt;p&gt;   This qualifier is for conditions that a pedantic purist would require, that
   otherwise a more relaxed hacker would prefer to do without.&lt;/p&gt;

&lt;h3&gt;analysis&lt;/h3&gt;

&lt;p&gt;   Qualifier for conditions that are generally not reasonable as
   run-time checks, either because they are prohibitively expensive or even not
   at all computable in this finite universe.  These conditions may, however, be
   useful for formal analysis tools that do not execute the code but
   perform techniques such as abstract interpretation or formal deduction to
   reason about the it.&lt;/p&gt;

&lt;p&gt;Additional user defined qualifiers may be added, any expression resulting in a
'bool' can be used.&lt;/p&gt;

&lt;p&gt;Run-time checks for pre- and post-conditions can be enabled or disabled for each
of these qualifiers (except for 'analysis', which is always disabled).  This
gives a fine-grain control over the kind of checks that are desired at run-time.
Usually, one would always want to keep safety checks enabled in a system that
processes data provided from the outside to avoid vulnerabilities such as buffer
overflows.  However, in a closed system like a rocket controller, it might make
sense to disable checks since a run-time error would mean definite loss of the
mission, while an unexpected intermediate value may still result in a useful
final result of a calculation.&lt;/p&gt;

&lt;h1&gt;Explicit results instead of Exceptions&lt;/h1&gt;

&lt;p&gt;Instead of exceptions that provide an alternative path for a function to return,
Fuzion requires all functions to return a result.  To indicate failure, the
generic result type 'outcome' is provided.&lt;/p&gt;

&lt;p&gt;outcome is a choice type that represents the result of a routine that
may either produce something useful or fail producing an error condition.&lt;/p&gt;

&lt;p&gt;Here is a small example of using an outcome result&lt;/p&gt;

&lt;p&gt;  getData (u User, t Type) outcome&amp;lt;data&gt; is&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;if u.allowedToAcces T
  (readFile t.fileName)?
else
  error "user $u not allowed to access $t"
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;  readFile (n string) outcome&amp;lt;data&gt; is&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;if dataExists n
  readData n
else
  error "data $t not available"
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;A user of this code when would have to explicitly unwrap the read data as follows&lt;/p&gt;

&lt;p&gt;  o := getData user type
  match o&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;d data  =&amp;gt; say "success: $d"
e error =&amp;gt; say "*** error $e"
&lt;/code&gt;&lt;/pre&gt;

&lt;h1&gt;Fuzion Modules&lt;/h1&gt;

&lt;p&gt;Modules in Fuzion are collections of Fuzion features that form a library to be
used by other modules. Modules may define a main entry point, such that they can
be used to build applications.&lt;/p&gt;

&lt;p&gt;The Fuzion front end performs static code analysis at the module level.  This
means that any features exported by a module are save to be used in different
contexts by other modules.  This includes static checking of the following
aspects:&lt;/p&gt;

&lt;h2&gt;Field Initialization&lt;/h2&gt;

&lt;p&gt;In Fuzion, the front end ensures that all fields are assigned an initial value.
There is no default initial value for uninitialized fields and there is no means
to access an uninitialized fields, as there is, e.g., for final fields in Java.&lt;/p&gt;

&lt;p&gt;Instead, it is checked that whenever an instance containing a field becomes
accessible outside of the feature declaring that field, the call chain is
analyzed to ensure it may not contain any accesses to the field.  In particular,
if an instance may become visible outside of the module, no uninitialized field
may be accessible by any exported features of that module.&lt;/p&gt;

&lt;h2&gt;Function Purity&lt;/h2&gt;

&lt;p&gt;The result of any feature visible to the outside must be independent of state
modifiable by other exported features and must not itself modify state that may
affect the result of other exported features.  This purity will allow
optimizations such as memoization or lazy evaluation common in functional
languages.&lt;/p&gt;

&lt;p&gt;Nevertheless, a pure function may use mutable fields, e.g., to store
intermediate results during its calculations.  If the mutable field's life span
is limited to the call of the exported feature and the field is not accessed by
any other exported feature, mutation does not make a function impure.&lt;/p&gt;

&lt;h2&gt;Race Freedom&lt;/h2&gt;

&lt;p&gt;Closely related to function purity is race freedom: Any exported feature is
checked to be safe to be called in a threaded environment without causing data
races.  There are no explicit locks in Fuzion, so there is no danger
of deadlocks due to nested locking.&lt;/p&gt;

&lt;h1&gt;Immutability&lt;/h1&gt;

&lt;p&gt;Fuzion encourages the use of immutable data by simple syntax for the declaration
of immutable fields.  Also, the use of tail calls for loops automatically
converts iterator variables used in that loop into immutable variables with a
life span of a single loop iteration.&lt;/p&gt;

&lt;p&gt;Since immutability is essential to ensure correctness of parallel execution
within threads that do not rely on locks or similar synchronization mechanisms,
Fuzion's analyzer will verify that data shared between threads is immutable.&lt;/p&gt;

&lt;p&gt;The standard library has been designed to provide immutable data types.
Nevertheless, there are mutable types such as 'marray', which provides a
mutable array.  These, however, should be used for local calculations only,
escape analysis will ensure that no accesses to mutable types occur from
outside the code manipulating the state.&lt;/p&gt;

&lt;h1&gt;Memory Management&lt;/h1&gt;

&lt;p&gt;Fuzion to a large extend relies on static analysis to reduce memory management
overhead.  Instances are by default value instances that do not require heap
allocation.  Furthermore, immutability in many cases avoids the need to keep a
shared copy on the heap.  For dynamic calls, heap allocation and dynamic binding
overhead is avoided by specialization of calls.&lt;/p&gt;

&lt;p&gt;Only for those instances for which all of these optimizations would fail, in
particular instances shared between threads or long-lived instances with mutable
fields, heap allocation will be required.  Memory allocated on the heap will be
reclaimed by a real-time garbage collector.&lt;/p&gt;

&lt;h1&gt;Fuzion Thread Safety&lt;/h1&gt;

&lt;p&gt;Static analysis at module and application level ensure that mutable data is not
shared between threads in Fuzion.  However, there must be means for threads to
communicate, e.g., for the result of a thread to become available to other
threads.  How this will be done in Fuzion is still open, thread safe libraries
such as thread-safe queues between might be provided here.&lt;/p&gt;

&lt;h1&gt;Conclusion and Next Steps&lt;/h1&gt;

&lt;p&gt;I hope Fuzion shows some interesting ideas how to approach the development of
safety-critical software.&lt;/p&gt;

&lt;p&gt;The Fuzion language definition and implementation are far from stable, but are
getting closer to become useful.  Currently, two execution options for Fuzion
are available: An interpreter implemented in Java and a back-end that compiles to
C code.  A tool to interface Java code is available for the interpreter.&lt;/p&gt;

&lt;p&gt;Main points that are missing right now are&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a powerful standard library&lt;/li&gt;
&lt;li&gt;additional library modules for all sorts of application needs&lt;/li&gt;
&lt;li&gt;low-level foreign language interface for C&lt;/li&gt;
&lt;li&gt;actual implementations of static analyzers and optimizers&lt;/li&gt;
&lt;li&gt;highly optimizing back-ends&lt;/li&gt;
&lt;li&gt;garbage collection for the C back-end&lt;/li&gt;
&lt;li&gt;documentation, tutorials&lt;/li&gt;
&lt;li&gt;enthusiastic contributors and users!&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Please feel free to contact me in case you want to use Fuzion or want to help
making it a success!&lt;/p&gt;</description>
        <persons>
          <person id="7627">Fridtjof Siebert</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/safety_designing_a_new_language_for_safety_fuzion/attachments/slides/5169/export/events/attachments/safety_designing_a_new_language_for_safety_fuzion/slides/5169/fosdem_2022_designing_a_new_language_for_safety_fuzion.pdf">Designing a new Language for Safety — Fuzion</attachment>
        </attachments>
        <links>
          <link href="https://flang.dev">Fuzion portal website</link>
          <link href="https://github.com/tokiwa-software/fuzion ">Fuzion sources on GitHub</link>
          <link href="https://video.fosdem.org/2022/D.safety/safety_designing_a_new_language_for_safety_fuzion.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.safety/safety_designing_a_new_language_for_safety_fuzion.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#safety-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#safety-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#safety-safety_designing_a_new_language_for_safety_fuzion:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#safety-safety_designing_a_new_language_for_safety_fuzion:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13059.php">Submit feedback</link>
        </links>
      </event>
      <event id="12920">
        <start>13:30</start>
        <duration>00:30</duration>
        <room>D.safety</room>
        <slug>safety_testing_requirements_documents</slug>
        <title>Testing Requirements Documents</title>
        <subtitle>Integrating Specifications into your CI/CD pipeline</subtitle>
        <track>Safety and Open Source</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In a traditional document driven process any changes to requirements need
to be verified and validated manually. A solution is proposed to link
requirements specifications to their implementation and track changes.&lt;/p&gt;

&lt;p&gt;Integrating specifications documents into CI/CD pipelines enables the agile
creation of always up-to-date documentation for the built/shipped artefacts.
We link specific versions of specification items with code, tests, and other
artefacts through their identifier and hash value.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Modern development practices have introduced continuous integration. It
ensures that ingtegration steps create as little friction as possible.
Furthermore all unit-tests are supposed to be succesfull at any given point in
time.&lt;/p&gt;

&lt;p&gt;Specifications documents can not trace this gap automatically and any changes
on either side (implementation or specification) is subject to manual
verification.&lt;/p&gt;

&lt;p&gt;An extensible solution is proposed to link specification items with code
(text) or any binary with a specific interpreter.&lt;/p&gt;

&lt;p&gt;A demonstration is given how a hypothetical spacecraft has its tea brewer connected
with Spacewire and the traceability is established. The data import from a DOORS
Excel dump is shown and how to link it to a given specification.&lt;/p&gt;</description>
        <persons>
          <person id="8780">Kristoffer Nordström</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/safety_testing_requirements_documents/attachments/slides/5058/export/events/attachments/safety_testing_requirements_documents/slides/5058/rmtoo_Traceability.pdf">Testing Requirements Documents</attachment>
        </attachments>
        <links>
          <link href="https://">sltoo.dev</link>
          <link href="https://video.fosdem.org/2022/D.safety/safety_testing_requirements_documents.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.safety/safety_testing_requirements_documents.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#safety-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#safety-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#safety-safety_testing_requirements_documents:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#safety-safety_testing_requirements_documents:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12920.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.dependency">
    </room>
    <room name="D.sds">
    </room>
    <room name="D.testing">
      <event id="12359">
        <start>10:00</start>
        <duration>00:10</duration>
        <room>D.testing</room>
        <slug>welcome</slug>
        <title>Welcome to Testing and Automation devroom</title>
        <subtitle/>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A warm welcome from your devroom managers, practical information, lineup and administrivia. Happy Testing!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1538">Alexander Todorov</person>
          <person id="5014">Cyril Hrubis</person>
          <person id="7104">Anders Roxell</person>
          <person id="8417">Zaklina Stojnev</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/welcome/attachments/slides/4803/export/events/attachments/welcome/slides/4803/welcome_testing_automation_2022.odp">Slides in ODF format</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/welcome/attachments/slides/4804/export/events/attachments/welcome/slides/4804/welcome_testing_automation_2022.pdf">Slides in PDF format</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.testing/welcome.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/welcome.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-welcome:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-welcome:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12359.php">Submit feedback</link>
        </links>
      </event>
      <event id="12377">
        <start>10:15</start>
        <duration>00:50</duration>
        <room>D.testing</room>
        <slug>custom_c_static_analysis_with_sparse</slug>
        <title>Automating Code Review with Sparse</title>
        <subtitle>Project specific static analysis of a large C codebase</subtitle>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;How we use the Sparse C Abstract Syntax Tree and linearized Intermediate Representation to write custom checks for the Linux Test Project API.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5048">Richard Palethorpe</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://richiejp.com/custom-c-static-analysis-tools">Related article</link>
          <link href="https://richiejp.github.io/ltp-sparse-pres/">Interactive slides</link>
          <link href="https://video.fosdem.org/2022/D.testing/custom_c_static_analysis_with_sparse.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/custom_c_static_analysis_with_sparse.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-custom_c_static_analysis_with_sparse:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-custom_c_static_analysis_with_sparse:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12377.php">Submit feedback</link>
        </links>
      </event>
      <event id="12593">
        <start>11:20</start>
        <duration>00:35</duration>
        <room>D.testing</room>
        <slug>unit_testing_linux_drivers</slug>
        <title>Unit testing Linux kernel drivers</title>
        <subtitle/>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The technical presentation is about how to use mocks to unit test Linux kernel drivers. The presentation explains how mocks help validating operational code. For instance by checking parameters passed to mocked function, or by configuring the mock to return an error code.&lt;/p&gt;

&lt;p&gt;The presentation will include some unit test examples that use a mocking tool which is called EasyMock. I'm the author of EasyMock.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8648">Laurent Carlier</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/unit_testing_linux_drivers/attachments/slides/5249/export/events/attachments/unit_testing_linux_drivers/slides/5249/Unit_testing_linux_kernel_driver.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/lcarlier/EasyMock">Mocking tool</link>
          <link href="https://github.com/lcarlier/simpleFifoKernelDriver">Example showing how the mocking tool is used</link>
          <link href="https://video.fosdem.org/2022/D.testing/unit_testing_linux_drivers.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/unit_testing_linux_drivers.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-unit_testing_linux_drivers:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-unit_testing_linux_drivers:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12593.php">Submit feedback</link>
        </links>
      </event>
      <event id="12661">
        <start>12:00</start>
        <duration>00:40</duration>
        <room>D.testing</room>
        <slug>continuous_testing_in_cloud</slug>
        <title>Continuous testing in a cloud based infrastructure using virtualization and real hardware in the loop</title>
        <subtitle/>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The concerns about code complexity, cybersecurity and LTS have made a continuous testing infrastructure a must have.&lt;/p&gt;

&lt;p&gt;The tests must take place both in virtual and real target. Virtual target because developers never get enough physical boards to test from, and real in order to limit virtualization/reality deviation.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;With the exponential growth of software complexity, to keep the cost and time of critical embedded application development under control, a continuous testing infrastructure is a must have feature.&lt;/p&gt;

&lt;p&gt;Not only should software tests be run early and automatically each time a developer pushes a new code commit in the system, but tests should also be run in a virtualized environment because developers typically never get enough physical board to test from. Nevertheless we should keep enough real hardware in the loop to limit virtualization/reality deviation and ensure developers can transparently move test from virtualization to the real world.&lt;/p&gt;

&lt;p&gt;This presentation shows how virtualization can ensure early code integration to reduce development/testing cycle, while at the same time keeping track with real hardware to ensure that  application is also running correctly on the final production device.  Then it gives feedback on the different challenges Iot.bzh faced while deploying its continuous tests infrastructure. Finally it focuses on the way virtualization and real targets can be combined to offer developers a complete and efficient CI infrastructure.&lt;/p&gt;</description>
        <persons>
          <person id="7329">Armand Bénéteau</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/continuous_testing_in_cloud/attachments/slides/4823/export/events/attachments/continuous_testing_in_cloud/slides/4823/Armand_CT_in_cloud_infra_virtual_real_FOSDEM.pdf">C.T. in cloud using virtualization and real hardware</attachment>
        </attachments>
        <links>
          <link href="https://redpesk.bzh/welcome/home">Redpesk home page</link>
          <link href="https://video.fosdem.org/2022/D.testing/continuous_testing_in_cloud.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/continuous_testing_in_cloud.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-continuous_testing_in_cloud:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-continuous_testing_in_cloud:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12661.php">Submit feedback</link>
        </links>
      </event>
      <event id="12821">
        <start>14:00</start>
        <duration>00:40</duration>
        <room>D.testing</room>
        <slug>frisbee</slug>
        <title>Frisbee: An advanced suite for the automated testing of cloud apps over Kubernetes </title>
        <subtitle/>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As distributed systems evolve, the testing scale multiplies, asking for dozens of test cases, combined with different application benchmarks (e.g., performance, correctness), and arbitrary operating conditions. Kubernetes holds a promise to enable automation and process improvement directly contributing to a system's reliability. Establishing a declarative API and providing a cheap and disposable environment, Kubernetes makes it easy to create uniform experiments, which may run manually or be exercised multiple times over the development cycle through a CI/CD system. Despite their abundance, existing benchmarks and Chaos engineering tools work in isolation, thus restricting the complexity of testing scenarios we can build.&lt;/p&gt;

&lt;p&gt;This talk will present Frisbee: an automated suite for the unified testing of distributed applications over Kubernetes. Frisbee simplifies a series of time-demanding activities, including the spin-up of the dependency stack required to bring the system into a steady state, the combined execution of workloads and faultloads, and the validation of the system's behavior via test cases. We will demonstrate Frisbee through a series of tests, focusing on uncertainties at the level of application (e.g., dynamically changing request patterns), infrastructure (e.g., crashes, network partitions), and deployment (e.g., saturation points).&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8750">Fotis Nikolaidis</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/frisbee/attachments/slides/5145/export/events/attachments/frisbee/slides/5145/Frisbee_Fosdem22.pdf"/>
        </attachments>
        <links>
          <link href="https://github.com/CARV-ICS-FORTH/frisbee">Frisbee@GitHub</link>
          <link href="https://github.com/CARV-ICS-FORTH/frisbee/blob/main/docs/tutorial.md">Frisbee Tutorial</link>
          <link href="https://video.fosdem.org/2022/D.testing/frisbee.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/frisbee.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-frisbee:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-frisbee:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12821.php">Submit feedback</link>
        </links>
      </event>
      <event id="12666">
        <start>14:45</start>
        <duration>00:45</duration>
        <room>D.testing</room>
        <slug>lava_openqa</slug>
        <title> LAVA + OpenQA = Automated, Continuous Full System Testing</title>
        <subtitle/>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Maintaining software systems for a long time is hard. Backporting kernel patches is a complex and expensive overhead. The Linux project's position is - quite rightly - to instruct down-streams to upgrade to the latest release.&lt;/p&gt;

&lt;p&gt;In practice, upgrading is difficult, scary and sometimes avoided. It takes time and effort before there is enough confidence that new releases will work in context: full system testing in embedded environments can be arduous. What if we could have continuous, automated full system tests, from from UI, to OS, to kernel, on hardware?&lt;/p&gt;

&lt;p&gt;This talk will provide an overview of how this can be achieved with a combination of OpenQA, LAVA and Continuous Integration pipelines. The talk will cover:
- How the same tests can be used in both kernel space and user space testing
- How the same tests can run in both virtualisation (with OpenQA and QEMU, developed originally for GNOME-OS) and also on hardware
- How images are then deployed and tested in hardware (LAVA triggers OpenQA via VNC to begin testing on boards)&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3596">James Thomas</person>
          <person id="8675">Laurence Urhegyi</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lava_openqa/attachments/slides/4786/export/events/attachments/lava_openqa/slides/4786/LAVA_OpenQA_Automated_Continuous_System_Testing.pdf"/>
        </attachments>
        <links>
          <link href="https://https://lava.qa.codethink.co.uk">Kernel Testing blog post: LAVA + OpenQA</link>
          <link href="https://https://openqa.qa.codethink.co.uk/">Kernel Testing blog post: LAVA + OpenQA</link>
          <link href="https://https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/1251">GNOME testing blog post</link>
          <link href="https://https://openqa.gnome.org/">GNOME testing blog post</link>
          <link href="https://video.fosdem.org/2022/D.testing/lava_openqa.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/lava_openqa.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-lava_openqa:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-lava_openqa:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12666.php">Submit feedback</link>
        </links>
      </event>
      <event id="13064">
        <start>15:45</start>
        <duration>00:10</duration>
        <room>D.testing</room>
        <slug>oniro_ci_with_lava</slug>
        <title>Oniro CI/Testing integration with LAVA</title>
        <subtitle/>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this session we introduce and explain the integration between LAVA (Linaro Automated Validation Architecture) and GitLab as part of the testing efforts in the Oniro OS from Eclipse foundation. The session will cover brief introductions to LAVA and Oniro, integration with GitLab and also present on how we provide vendors the opportunity to test the full software stack on the live devices in-house in completely integrated manner with the main lab and have the test results available for reporting in the upstream gitlab instance.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8840">Stevan Radaković</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/oniro_ci_with_lava/attachments/slides/5006/export/events/attachments/oniro_ci_with_lava/slides/5006/Oniro_CI_Testing_integration_with_LAVA_FOSDEM_22.pdf"/>
        </attachments>
        <links>
          <link href="https://lavasoftware.org/">LAVA documentation</link>
          <link href="https://git.lavasoftware.org/lava/lava">LAVA sources</link>
          <link href="https://docs.oniroproject.org/en/latest/">Oniro documentation</link>
          <link href="https://oniroproject.org/join-us/#fosdem2022">Oniro Join us page</link>
          <link href="https://fosdem.org/2022/schedule/event/welcome_oniro/">Welcome to FOSDEM2022's Oniro online stand</link>
          <link href="https://video.fosdem.org/2022/D.testing/oniro_ci_with_lava.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/oniro_ci_with_lava.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-oniro_ci_with_lava:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-oniro_ci_with_lava:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13064.php">Submit feedback</link>
        </links>
      </event>
      <event id="12899">
        <start>16:00</start>
        <duration>00:15</duration>
        <room>D.testing</room>
        <slug>mockery_of_trust</slug>
        <title>How (not) to make a mockery of trust</title>
        <subtitle>Testing client software for public-key infrastructure</subtitle>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The ever-continuing push for digitalisation has increased our reliance on trust services of various kinds, filling various needs relating to document signing, code signing, authorization tokens, and so forth.
Many of these trust services rely on public-key infrastructure (PKI) and X.509 certificates.&lt;/p&gt;

&lt;p&gt;The sensitive nature of these tools makes them difficult to use in a testing environment. On the one hand, exposing access to production keys in your CI is obviously a terrible idea. But on the other hand, setting up and maintaining a fully functional "mock" PKI environment is also pretty tricky. What can you do about that?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Using PKI tools in test workflows involves many challenges. Here are a few examples:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Even a (supposedly) basic task like validating an X.509 certificate involves quite a bit of complexity. Apart from "local" validation logic, you might also have to check the revocation status of your certificate, which could entail talking to an OCSP responder service or looking up a CRL.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;If you're using secure timestamps (RFC 3161) in your code, your tests might also require access to a time stamping service.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Maybe you're using a remote signing service vendor that doesn't offer any sort of "sandbox" for testing purposes.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;In all of these scenarios, both test data generation and mock service integration can be quite cumbersome.
Both in my own time and on the job, I write a lot of code that relates to digital signing in various ways, and this is a kind of problem that I run into all the time. After trying out a variety of methods, I grew dissatisfied with the "traditional" options, and rolled my own PKI testing framework: &lt;a href="https://github.com/MatthiasValvekens/certomancer"&gt;Certomancer&lt;/a&gt;.
Certomancer helps with both test data generation, performs trust service mocking, comes with a plugin API, and most importantly, it's FOSS (MIT licence).&lt;/p&gt;

&lt;p&gt;In my talk, I'll take you through some of the "how"s and "why"s of Certomancer's feature set, and talk about some of the mileage that I've gotten out of it.&lt;/p&gt;</description>
        <persons>
          <person id="7832">Matthias Valvekens</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mockery_of_trust/attachments/slides/4942/export/events/attachments/mockery_of_trust/slides/4942/trust_mockery_slides_handout.pdf">Slide deck (handout version)</attachment>
        </attachments>
        <links>
          <link href="https://github.com/MatthiasValvekens/certomancer">Project repository</link>
          <link href="https://mvalvekens.be">Personal website</link>
          <link href="https://asciinema.org/a/406798">Project demo clip</link>
          <link href="https://video.fosdem.org/2022/D.testing/mockery_of_trust.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/mockery_of_trust.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-mockery_of_trust:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-mockery_of_trust:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12899.php">Submit feedback</link>
        </links>
      </event>
      <event id="12454">
        <start>16:20</start>
        <duration>00:15</duration>
        <room>D.testing</room>
        <slug>1000000_test_cases</slug>
        <title>Fuzzing, or How I Generated 1,000,000 New Emulator Test Cases in an Afternoon</title>
        <subtitle>Fill your boots. Then fill somebody else's.</subtitle>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Emulation of classic hardware is a solved problem and like all solved problems that are sufficiently fun it attracts countless new implementations every year. This has led to the creation of many public test suites — test suites independent of any particular emulator, which can usually even run on real hardware. But these suites tend to assume a lot of working functionality beyond the part they are specifically testing, being designed by an intelligent human being to test complete emulators holistically.&lt;/p&gt;

&lt;p&gt;This presentation covers an alternative source and target of emulator tests: random numbers, to test individual processor instructions, so that future emulator authors can test from day one.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7577">Thomas Harte</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/TomHarte/ProcessorTests">The 6502 test cases mentioned in the video.</link>
          <link href="https://video.fosdem.org/2022/D.testing/1000000_test_cases.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/1000000_test_cases.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-1000000_test_cases:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-1000000_test_cases:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12454.php">Submit feedback</link>
        </links>
      </event>
      <event id="12978">
        <start>16:40</start>
        <duration>00:05</duration>
        <room>D.testing</room>
        <slug>history_of_testing</slug>
        <title>History of Testing</title>
        <subtitle>let's write it together</subtitle>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As a side project the Kiwi TCMS team has started collecting facts about people who've made important contributions to the testing field. We're calling upon other testers for ideas and contributions.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1538">Alexander Todorov</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/history_of_testing/attachments/slides/4805/export/events/attachments/history_of_testing/slides/4805/LIGHTNING_TALK_History_of_Testing.odp">Slides in ODF format</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/history_of_testing/attachments/slides/4806/export/events/attachments/history_of_testing/slides/4806/LIGHTNING_TALK_History_of_Testing.pdf">Slides in PDF format</attachment>
        </attachments>
        <links>
          <link href="https://github.com/kiwitcms/history-of-testing/">GitHub repository</link>
          <link href="https://video.fosdem.org/2022/D.testing/history_of_testing.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/history_of_testing.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-history_of_testing:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-history_of_testing:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12978.php">Submit feedback</link>
        </links>
      </event>
      <event id="12371">
        <start>16:50</start>
        <duration>01:00</duration>
        <room>D.testing</room>
        <slug>10_oss_test_automation_tools</slug>
        <title>5 OpenSource Test Automation tools in 45 minutes!</title>
        <subtitle>See a working example of these cool OSS (Test) Automation Tools and see how they compare.</subtitle>
        <track>Testing and Automation</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;5 OpenSource Test Automation tools in 45 minutes! You will be left with a general oversight of various well known OpenSource Test Automation tools which are applicable in a large (or smaller) companies or OSS projects. With a working example demo where you see it in action. The talk will also score these tools (subjectively) among each other (installation, ease of use, stability, speed, etc) and provide insights on how to get started. When to use it, and when not to use it.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this session the speaker will show 5 well known OpenSource Test Automation tools applicable in the enterprise for test automation. The cool thing is that many OSS projects could also benefit from incorporating therse tools as part of their CI/CD approach. The talk will cover how it could be used and show a working example of the code. This will give a quick glance of various OSS (Test) Automation tools. Some examples are: SeleniumBase, Cypress.io, Cucumber, RobotFramework and Cerberus.&lt;/p&gt;</description>
        <persons>
          <person id="8496">Eric de Graaf</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/10_oss_test_automation_tools/attachments/slides/5022/export/events/attachments/10_oss_test_automation_tools/slides/5022/FOSDEM_2022_5_Cool_OSS_TA_tools_TesterTech.pdf"/>
        </attachments>
        <links>
          <link href="https://github.com/TesterTech/2022-awesome-oss-ta-tools">Github</link>
          <link href="https://video.fosdem.org/2022/D.testing/10_oss_test_automation_tools.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.testing/10_oss_test_automation_tools.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#testing-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#testing-10_oss_test_automation_tools:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#testing-10_oss_test_automation_tools:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12371.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.valgrind">
    </room>
    <room name="D.virtualization">
      <event id="12571">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_virtualio</slug>
        <title>What's coming in VIRTIO 1.2</title>
        <subtitle>New virtual I/O devices and features</subtitle>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The VIRTIO standard defines I/O devices that are commonly used in virtual machines today. The last version of the standard was released in 2019 and much has changed since then. This presentation covers new devices and features in the upcoming VIRTIO 1.2 standard.&lt;/p&gt;

&lt;p&gt;There are 9 new device types: fs, rpmb, iommu, sound, mem, i2c, scmi, gpio, and pmem. We will look at the functionality offered by these devices and their status in Linux.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This presentation is aimed at users of virtualization who may be interested in new virtual devices that are becoming available in Linux, QEMU, etc. It may also be of interest to driver and virtual machine monitor developers who are considering implementing new devices.&lt;/p&gt;</description>
        <persons>
          <person id="2816">Stefan Hajnoczi</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vai_virtualio/attachments/slides/4992/export/events/attachments/vai_virtualio/slides/4992/stefanha_fosdem_2022.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=virtio">VIRTIO standard homepage</link>
          <link href="https://blog.vmsplice.net/search/label/virtio">My blog with VIRTIO related material</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_virtualio.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_virtualio.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_virtualio:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_virtualio:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12571.php">Submit feedback</link>
        </links>
      </event>
      <event id="12592">
        <start>10:30</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_codeready</slug>
        <title>Cross-platform/cross-hypervisor virtio vsock use in go</title>
        <subtitle>Usermode networking in CodeReady Containers</subtitle>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;CodeReady Containers runs an OpenShift cluster on a laptop or workstation using virtualization. It's written in go, and uses KVM, HyperV or HyperKit depending on the OS it's running on. External network access is done through gVisor's userland TCP/IP stack which the virtual machine uses over virtio-vsock.&lt;/p&gt;

&lt;p&gt;This talk will start with a short presentation of what CodeReady Containers is, explain why it needs a userland TCP/IP stack, but its main focus will be around virtio vsock, how to use it from go, and the differences to expect on the different hypervisors.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="157">Christophe Fergeau</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vai_codeready/attachments/slides/4879/export/events/attachments/vai_codeready/slides/4879/Cross_platform_cross_hypervisor_virtio_vsock_use_in_go.pdf">Slides for the presentation</attachment>
        </attachments>
        <links>
          <link href="https://github.com/code-ready/">GitHub organization with the various projects mentioned in this talk</link>
          <link href="https://github.com/containers/gvisor-tap-vsock">Usermode network daemon</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_codeready.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_codeready.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_codeready:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_codeready:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12592.php">Submit feedback</link>
        </links>
      </event>
      <event id="12432">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_intro_okd</slug>
        <title>Introducing OKD Virtualization</title>
        <subtitle/>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;OKD Virtualization is the community project bringing traditional virtualization technology into OKD. Meet the OKD Virtualization community and learn about it!&lt;/p&gt;</abstract>
        <description>&lt;p&gt;OKD Virtualization is the community project bringing traditional virtualization technology into OKD. It’s built on top of the KubeVirt project and the Hyperconverged Cluster Operator project.
HCO ensures a single installable unit for Kubevirt and its sibling components leveraging the operator framework to provide the easiest way of installing and maintaining this additional control plane.
This bundle will ship additional tools required to do traditional virtualization tasks like uploading disk images, host network configuration, local storage provisioning, and other functionality which is not covered by the core KubeVirt. On top of this a user interface embedded within the OKD Console is provided for managing the lifecycle of the Virtual Machines. Virtual Machines from other virtualization systems can be imported into OKD Virtualization leveraging the Konveyor Forklift project. Meet the OKD Virtualization community and learn about it!&lt;/p&gt;

&lt;p&gt;After this session you will
Know what KubeVirt is
Know what HCO (Hyper Converged Cluster Operator) is and how it relates to KubeVirt
How the OKD UI is presenting VMs
A rough idea of the featureset of what this setup provides
Seen a demo, and knowledge of how to set this up yourself&lt;/p&gt;</description>
        <persons>
          <person id="3534">Simone Tiraboschi</person>
          <person id="8522">Sandro Bonazzola</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vai_intro_okd/attachments/slides/4843/export/events/attachments/vai_intro_okd/slides/4843/OKD_Virtualization_Community.pdf">Introducing OKD Virtualization</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_intro_okd.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_intro_okd.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_intro_okd:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_intro_okd:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12432.php">Submit feedback</link>
        </links>
      </event>
      <event id="12331">
        <start>11:30</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_torov</slug>
        <title>ToroV, a kernel in user-space, or sort of</title>
        <subtitle/>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk presents ToroV, a novel open-source technology that combines virtualization and containerization to enable the execution of users’ applications in a safer and improved manner. In ToroV, applications run as Virtual Machines without the need of an OS, unikernel nor device-model. ToroV combines a minimalist Virtual Machine Monitor and a virtualized guest program communicating through POSIX APIs. When the guest application requires to open or write a file, it just invokes the VMM using hypercalls. The VMM intercepts those hypercalls, processes the request, and returns to the guest. The sysadmin defines the ACL (Access Control List) of authorized hypercall per virtualized guest application. This allows the user to control the host’s surface that is exposed to the guest. In this talk, we propose to present the ToroV architecture together with several ongoing experiments. For example, the minimalist VMM allows us to boot up a VM in KVM in less than 6 ms. Also, we show how we debug guest applications by simply using GDB and the KVM API for debugging. During the talk, we discuss the main differences with unikernels and containers and how ToroV gets the best of both worlds. Also, we present the main differences with gVisor, which is a similar project from Google.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2450">Matias Vara</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vai_torov/attachments/slides/4979/export/events/attachments/vai_torov/slides/4979/fosdem22_torov.pdf"/>
        </attachments>
        <links>
          <link href="https://github.com/torokernel/torov">This the source code of ToroV which is hosted at github</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_torov.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_torov.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_torov:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_torov:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12331.php">Submit feedback</link>
        </links>
      </event>
      <event id="12559">
        <start>12:00</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_kubevirt_scale</slug>
        <title>KubeVirt scale test by creating 400 VMIs on a single node</title>
        <subtitle/>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As the number of VMs per node gets larger, using more powerful nodes (i.e. with more CPUs and RAM), the scalability of Kubevirt's control plane becomes a bottleneck, slowing down the VMI creation process. This talk will cover the motivations and concepts around general benchmarking of the KubeVirt control plane, as well as explaining the journey to running a density test with hundreds of VMs per node.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Kubevirt's performance and scalability are determined by several factors. As the number of VMs per node gets larger, using more powerful nodes (i.e. with more CPUs and RAM), the scalability of Kubevirt's control plane becomes a bottleneck, slowing down the VMI creation process. This talk will cover the motivations and concepts around general benchmarking of the KubeVirt control plane, as well as explaining the journey to running a density test with hundreds of VMs per node. In addition, I'll provide some performance metrics comparing VM build time in various scenarios. Participants will have a high-level knowledge of the on-going KubeVirt's sig-scale community performance assessment and the single-node scalability characteristics of KubeVirt.&lt;/p&gt;</description>
        <persons>
          <person id="8629">Marcelo Amaral</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vai_kubevirt_scale/attachments/slides/5139/export/events/attachments/vai_kubevirt_scale/slides/5139/kubevirt_scale_test.pptx">KubeVirt Scale test</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_kubevirt_scale.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_kubevirt_scale.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_kubevirt_scale:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_kubevirt_scale:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12559.php">Submit feedback</link>
        </links>
      </event>
      <event id="12542">
        <start>12:30</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_future_evolution</slug>
        <title>DevOps, Cloud Native, DPUs: beyond the buzzwords</title>
        <subtitle>The future and evolution of on-prem open source virtualization platforms</subtitle>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Open Source virtualization is almost 20 years old. Obviously, things have evolved a lot in that time: the public cloud, new CPU architectures, new storage technologies, and more.&lt;/p&gt;

&lt;p&gt;What about the real, on-the-ground usage? Sysadmins, Ops and Devops are not leveraging virtualization the same way today as they did before. But what really changed? In what direction is it evolving? Is on-premise open source virtualization still relevant today?&lt;/p&gt;

&lt;p&gt;Through our own journey as engineers of an open source virtualization platform, we'll give you an inside look into what our users are requesting from us, and what we did to modernize our virtualization stack based on the Xen hypervisor.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2730">Olivier Lambert</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_future_evolution.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_future_evolution.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_future_evolution:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_future_evolution:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12542.php">Submit feedback</link>
        </links>
      </event>
      <event id="12699">
        <start>13:00</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_isolating_pci</slug>
        <title>Isolating PCI/CXL Devices: It All Starts with System Launch</title>
        <subtitle/>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;It has been well established that the integrity of critical systems must be rooted in the launch. Early works such as the Xoar architecture demonstrated the need for virtualized environments to begin with a lightweight, restricted bootstrap from which  isolation of PCI management could be established. Since that time, knowledge of real IOMMU implementations and how to leverage them for system integrity has evolved. In this presentation, the new Hyperlaunch capability for starting hypervisors will be presented with a short discussion of the Xen implementation. The talk will progress to a discussion of how Hyperlaunch is connected with TrenchBoot (Linux Secure Launch) and Mandatory Access Control communication fabrics. With a focus on how it enables dedicated PCI management constructs that can provide secure and trustworthy isolation for PCI devices, with the potential for CXL devices. The talk will close with an open discussion on how hypervisors might unify around a common approach for IOMMU management.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8004">Daniel Smith</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.cs.ubc.ca/~andy/papers/xoar-sosp-final.pdf">Xoar Architecture</link>
          <link href="https://xenbits.xen.org/docs/unstable/designs/launch/hyperlaunch.html">Hyperlaunch Design for Xen</link>
          <link href="https://trenchboot.org/events/">Presentations on TrenchBoot</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_isolating_pci.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_isolating_pci.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_isolating_pci:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_isolating_pci:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12699.php">Submit feedback</link>
        </links>
      </event>
      <event id="12604">
        <start>13:30</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_automatic_cpu</slug>
        <title>Automatic CPU and NUMA pinning</title>
        <subtitle/>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In FOSDEM 2019 we presented the addition of high-performance virtual machines in oVirt.
With this new VM type, parts of the VM configuration were changed to improve the performance of workloads it runs.
In particular, it was useful for CPU-intensive workloads, such as SAP HANA.
However, better performance came at the expense of usability. Users were still expected to set various things manually, like CPU and NUMA pinning and hugepages.
In this talk, I will guide you through our journey of simplifying and automating the settings of high performance VMs in oVirt.
We'll see the evolution of the changes, the challenges we faced, where we are today and what's more to come in oVirt 4.5.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8658">Liran Rotenberg</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vai_automatic_cpu/attachments/slides/4877/export/events/attachments/vai_automatic_cpu/slides/4877/Automatic_CPU_and_NUMA_pinning">Automatic CPU and NUMA pinning</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_automatic_cpu.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_automatic_cpu.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_automatic_cpu:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_automatic_cpu:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12604.php">Submit feedback</link>
        </links>
      </event>
      <event id="12433">
        <start>14:00</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_network_interface</slug>
        <title>Network interface hotplug for Kubernetes</title>
        <subtitle/>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Design and implementation of dynamic network attachment for Kubernetes pods and KubeVirt VMs.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Immutable infrastructure is the law of the land in the cloud native landscape, promising benefits to software architectures run in Kubernetes.
… except sometimes the rules must be broken to achieve certain use cases; take for instance the dynamic attachment of L2 networks to a running VM: to hotplug an interface into the VM running in a pod, you first need to hotplug that interface into the pod.&lt;/p&gt;

&lt;p&gt;This feature is particularly of interest (required, actually) to enable scenarios where the workload (VM) cannot tolerate a restart, or when the workload is created prior to the network.&lt;/p&gt;

&lt;p&gt;When thinking about strategies for tackling this problem, we faced a recurring question when trying to come up with a modular design to provide this functionality: "should the changes be located in KubeVirt, and thus solve this issue for Virtual Machines, or should we take the longer path and address this issue also for pods ?" We chose the latter, which unlocks dynamic network attachment for pods, thus also benefiting the Kubernetes community.&lt;/p&gt;

&lt;p&gt;This talk will provide the audience with a basic understanding of KubeVirt, CNI, and Multus, and then propose a design to add (or remove) network interfaces from running pods (and virtual machines), along with the changes required in Multus and KubeVirt to make it happen.&lt;/p&gt;

&lt;p&gt;It will also factor in a community perspective, explaining how we pitched and got both the Multus and KubeVirt communities involved in a working arrangement to deliver this functionality.&lt;/p&gt;</description>
        <persons>
          <person id="6376">Miguel Barroso</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vai_network_interface/attachments/slides/4898/export/events/attachments/vai_network_interface/slides/4898/fosdem2022_Interface_Hotplug_for_Kubernetes.pdf"/>
        </attachments>
        <links>
          <link href="https://asciinema.org/a/f5hBUy5dL0mPvddaZo07JhO31">Asciinema demo for pods</link>
          <link href="https://asciinema.org/a/gjlJnBw5EpHQuYadSbHXfNSJ6">Asciinema demo for VMs</link>
          <link href="https://github.com/kubevirt/community/blob/main/design-proposals/nic-hotplug/nic-hotplug.md">Feature design plan</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_network_interface.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_network_interface.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_network_interface:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_network_interface:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12433.php">Submit feedback</link>
        </links>
      </event>
      <event id="12569">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_story_tpm</slug>
        <title>The story of adding TPM support to oVirt</title>
        <subtitle/>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;oVirt is an open source virtualization solution based on kvm, QEMU and libvirt.  Trusted Platform Module (TPM) device support, which brings new security capabilities that modern operating systems utilize or even require, was added to oVirt recently.&lt;/p&gt;

&lt;p&gt;In theory, adding TPM support should be as easy as just adding a TPM device to the virtual machine libvirt XML.  But features built on top of a lower-level virtualization platform are not always as easy to implement as they may initially seem to be.  This talk will present the challenges experienced when adding TPM support to oVirt.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The talk will explain that a supposedly complete feature support in libvirt/QEMU may still require challenging design considerations. What can be used easily in a simple virtual machine running on a desktop computer may not be enough to get the things working well and reliably in a virtual machine management running across many hosts.&lt;/p&gt;

&lt;p&gt;Some of the challenges experienced with TPM support have been sorted out while other ones still wait for a good solution.  Although focusing on TPM, the lessons presented in this talk can apply to a wide range of features.  Whatever we work on, we cannot be just passive consumers of features but we must look for the right ways of using them and be proactive in avoiding pitfalls.&lt;/p&gt;</description>
        <persons>
          <person id="8633">Milan Zamazal</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vai_story_tpm/attachments/slides/5065/export/events/attachments/vai_story_tpm/slides/5065/tpm_fosdem.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_story_tpm.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_story_tpm.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_story_tpm:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_story_tpm:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12569.php">Submit feedback</link>
        </links>
      </event>
      <event id="12674">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.virtualization</room>
        <slug>vai_deploying_vms</slug>
        <title>Deploying VMs and Containers across Infrastructure Providers</title>
        <subtitle>Presenting OpenNebula’s new Edge Cloud Architecture</subtitle>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk presents OpenNebula's new distributed Edge Cloud Architecture, which is composed of Edge Clusters that can run any workload (both Virtual Machines and application containers), on any resource (bare-metal or virtualized), anywhere (on-prem and on a cloud/edge provider). An Edge Cluster, built on open source technologies that already exist in the Linux operating system, is a hyperconverged functional set of managed objects that include storage, network, and host resources. An Edge Cluster provides all the resources needed to run virtualized or containerized applications. OpenNebula’s management services, including scheduling, monitoring and life-cycle management, run in the cloud Front-end and orchestrate from there the local or remote Edge Clusters. The Front-end also provides access to the administration tools, user interfaces, and API. Although the requirements may vary depending on the number and size of the clusters and API load, the Front-end node only requires 8 GB of main memory and 4 cores. The Edge Cloud Architecture is able to provide a lightweight and easy-to-use storage platform for medium-sized clusters consisting of tens of nodes. OpenNebula’s Edge Cloud Architecture is able to manage hundreds of these clusters, as they operate autonomously in terms of networking and storage, and handle thousands of virtualized hosts and tens of thousands of virtualized applications. In this presentation we will explain in detail the deployment model for Edge Clusters, the specialized storage solution they incorporate (OneStor), and the performance benefits of this multi-cloud architecture as confirmed by the latest benchmarks.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7687">Alejandro Huertas</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_deploying_vms.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_deploying_vms.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_deploying_vms:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_deploying_vms:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12674.php">Submit feedback</link>
        </links>
      </event>
      <event id="12586">
        <start>15:30</start>
        <duration>00:45</duration>
        <room>D.virtualization</room>
        <slug>vai_phyllomeos</slug>
        <title>Phyllome OS</title>
        <subtitle>A Fedora Remix built to leverage KVM/QEMU virtualization locally</subtitle>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Most Linux distributions are not designed to support desktop virtualization, and GPU vendors have failed to agree on a common way to let virtual machines access 3D capabilities (SR-IOV; vfio-pci; vfio-mdev or virtio-gpu...). The result is that it is still complicated to create fast and responsive virtual machines locally.&lt;/p&gt;

&lt;p&gt;Phyllome OS is a Fedora Remix based on Fedora Server which attempts to make it easier to run virtual machines locally on computers that support hardware-assisted virtualization, using mostly paravirtualization (aka virtio-devices). It currently relies on existing technologies (libvirt; KVM/QEMU; virt-manager; GNOME Shell; etc), but will eventually implement its own virtual machine manager, package the cloud hypervisor as an alternative to QEMU, and use filesystem-level  encryption to protect virtual machines disks. The main idea behind this OS is to treat the host, Phyllome OS, as a read-only system, i.e. as a mere appliance to host virtual machines. The presentation will give a demonstration of Phyllome OS in its current state.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Despite steady progress, especially on the KVM/QEMU front, desktop virtualization today still leaves much to be desired when it comes to usability. For most users, it is still complicated to create virtual machines with advanced media capabilities, including 3D acceleration. 3D-accelerated guests are a must-have nowadays and most desktop environments leverage it to provide a smooth user experience. Existing approaches attempting to grant 3D capabilities to virtual machines are not straightforward,  sometimes incompatible and often require trade-offs between usability, performance and security. As a result, a successful implementation on a single host typically requires careful considerations and is often hardware-dependent. For instance, passing through real hardware to a virtual machine using vfio-pci is only possible if the piece of hardware is well-isolated in a single IOMMU group. Paravirtualization, on the other hand, and especially virtio-gpu, promises to be hardware-independent but is not (yet?) supported by all modern guest operating systems.&lt;/p&gt;

&lt;p&gt;What if an operating system was designed to provide the best experience regardless of the guest operating system in use?&lt;/p&gt;</description>
        <persons>
          <person id="8606">Lukas Greve</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://phyllo.me">Main website</link>
          <link href="https://wiki.phyllo.me">Wiki</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_phyllomeos.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_phyllomeos.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_phyllomeos:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_phyllomeos:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12586.php">Submit feedback</link>
        </links>
      </event>
      <event id="12691">
        <start>16:15</start>
        <duration>01:00</duration>
        <room>D.virtualization</room>
        <slug>vai_hardware_accel</slug>
        <title>Hardware-accelerated graphics in secure multi-tenant environments</title>
        <subtitle>What is the current status, and what is blocking it?</subtitle>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Hardware-accelerated graphics is becoming an essential part of modern computing environments, yet it is currently very difficult to impossible to use in secure environments such as Qubes OS.  SR-IOV promises to solve this problem, but multiple problems have limited its adoption.  This workshop is about these problems and about what is needed to solve them.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8660">Demi Obenour</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vai_hardware_accel/attachments/slides/5177/export/events/attachments/vai_hardware_accel/slides/5177/GPU_secure_multi_tenant.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_hardware_accel.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_hardware_accel.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_hardware_accel:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_hardware_accel:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12691.php">Submit feedback</link>
        </links>
      </event>
      <event id="12335">
        <start>17:15</start>
        <duration>00:20</duration>
        <room>D.virtualization</room>
        <slug>vai_tracing_kubevirt</slug>
        <title>Tracing KubeVirt traffic with Istio</title>
        <subtitle/>
        <track>Virtualization and IaaS</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Software development has been gradually shifting from monolithic to distributed containerized applications. Such applications are composed of components referred to as micro services.
With the increasing number of micro services, it becomes increasingly difficult to understand how all the components communicate.&lt;/p&gt;

&lt;p&gt;This is where Istio service mesh comes into play. Istio allows developers to manage and monitor network traffic between micro services and by providing features like mutual TLS, request retries or request circuit breaking. Vendoring these features from Istio helps keeping micro services focused on the actual application logic as they don't need to be implemented by the micro services.
The IT industry has broadly adopted this architecture, but there are still plenty of legacy workloads running in virtual machines, which can't easily take the advantage of the features provided by service mesh. At least not until recently when KubeVirt introduced support for Istio service mesh.&lt;/p&gt;

&lt;p&gt;Attendees of this talk gain insight into the concept of the Istio sidecar proxy. A short demonstration showing typical use case of Istio service mesh -- canary deployment -- is presented. Next, this talk explains subtle differences of network traffic routing between regular Kubernetes pods and containerized KubeVirt virtual machines, leading to the challenges that these differences pose for traffic proxying.
Finally, the changes necessary to support Istio for KubeVirt virtual machines are explained and the resulting functionality presented using the same scenario, but with the workload running in virtual machines instead of Kubernetes Pods.&lt;/p&gt;

&lt;p&gt;The takeaway of this talk is understanding of routing concepts behind Istio proxy sidecar with regular Kubernetes pods as well as with containerized KubeVirt virtual machines. Audience will have a chance to observe typical use case of Istio with both pods and virtual machines and get insight into the necessary changes that made this possible.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8465">Radim Hrazdil</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vai_tracing_kubevirt/attachments/slides/4923/export/events/attachments/vai_tracing_kubevirt/slides/4923/tracing_kubevirt_traffic.pdf">Tracing Kubevirt Traffic with Istio</attachment>
        </attachments>
        <links>
          <link href="https://github.com/istio/istio">Istio Service mesh GitHub</link>
          <link href="https://https://github.com/kubevirt/kubevirt">KubeVirt GitHub</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_tracing_kubevirt.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.virtualization/vai_tracing_kubevirt.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#virtualization-vai_tracing_kubevirt:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#virtualization-vai_tracing_kubevirt:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12335.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.web3">
      <event id="13020">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>trustgraphs</slug>
        <title>Decentralized Self Sovereign Trust Graphs</title>
        <subtitle/>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;What if all our decentralized apps and platforms could share trust/ratings/attestation information, in the form of portable cryptographically signed claims?  What if this self-sovereign, user owned and controlled, privately sharable trust network could become the backbone to unite our many disparate decentralized web apps and platforms?  These are the goals of Trust Graph, and its reference implementation built on Holochain.&lt;/p&gt;

&lt;p&gt;In this talk we will cover:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;TrustAtom format: &lt;code&gt;source&lt;/code&gt;, &lt;code&gt;target&lt;/code&gt;, semantic &lt;code&gt;content&lt;/code&gt;, normalized scalar &lt;code&gt;value&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Quick survey of the ecosystem of similar protocols&lt;/li&gt;
&lt;li&gt;Use cases, including the potential to tackle major global challenges&lt;/li&gt;
&lt;li&gt;An example illustrating Trust Graph "rollups" for caching Trust Graphs in TrustAtoms&lt;/li&gt;
&lt;li&gt;Trust Graph on Holochain: using Holochain links to allow for searchable TrustAtoms&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="8810">Harlan Wood</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/trustgraphs/attachments/slides/5116/export/events/attachments/trustgraphs/slides/5116/Trust_Graph_Deck">Trust Graph Deck</attachment>
        </attachments>
        <links>
          <link href="https://github.com/trustgraph">https://github.com/trustgraph</link>
          <link href="http://trustgraph.net/">http://trustgraph.net/</link>
          <link href="https://">https://</link>
          <link href="https://video.fosdem.org/2022/D.web3/trustgraphs.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/trustgraphs.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-trustgraphs:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-trustgraphs:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13020.php">Submit feedback</link>
        </links>
      </event>
      <event id="13022">
        <start>14:00</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>ceramic</slug>
        <title>Open Source Data with Ceramic</title>
        <subtitle>Why the future of the web is self-certifying</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Why is code open source, but data still locked into silos of big corporations? In this talk we asses the current situation of the web, and evaluate what we can do differently with Web3. We look into what it means for data to be "open source", the implications for developers as data is not locked into their apps, and the core pieces of technology that makes this possible.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8824">Joel Thorstensson</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ceramic/attachments/slides/4904/export/events/attachments/ceramic/slides/4904/ceramic.pdf">Open source data with Ceramic</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.web3/ceramic.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/ceramic.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-ceramic:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-ceramic:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13022.php">Submit feedback</link>
        </links>
      </event>
      <event id="12988">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>i3market</slug>
        <title>i3-Market Self Sovereign Identity Authentication</title>
        <subtitle> Authentication based on Distributed Identity and Verifiable credentials using OpenID Connect and Veramo</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Video presenting the user registration and authentication processes on a Single Page Application towards the i3-Market Platform, using the i3-Market crypto wallet.
i3-Market IAM solution is based on Veramo framework and the OpenID Connect standard&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8793">alessandro.amicone</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.web3/i3market.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/i3market.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-i3market:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-i3market:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12988.php">Submit feedback</link>
        </links>
      </event>
      <event id="13222">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>holochain_scaffolding</slug>
        <title>Scaffold a Holochain App in 10 minutes</title>
        <subtitle>Demo and workshop for making a simple, functional Holochain App with scaffolding tools</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Using the new Holochain Rapid Application Development tools, we'll scaffold a Holochain application from scratch, generating all the necessary boilerplate, code and types for your specific use case.&lt;/p&gt;

&lt;p&gt;You'll learn how to use the RAD tools yourself, and what are the next steps you can follow to start developing a hApp.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8902">guillem.cordoba</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.web3/holochain_scaffolding.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/holochain_scaffolding.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-holochain_scaffolding:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-holochain_scaffolding:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13222.php">Submit feedback</link>
        </links>
      </event>
      <event id="13027">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>livepeer</slug>
        <title>Building Web3's Video Infrastructure Layer</title>
        <subtitle>Why Openness and Decentralization Matters with livepeer</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Video is foundational to the web experience, representing roughly 80% of internet bandwidth. Using desktop, mobile and other devices, video is how individuals learn, work, create, are entertained, and share their human stories. Given that all industries have a need for video and that mainstream audiences are increasingly interested in Web3 solutions, understanding the advantages of decentralization and openness at technical and user levels is essential if these solutions are to be successfully adopted. Join this talk to learn about how Livepeer is positioning itself as the video infrastructure layer of web3 and opportunities for open source contributors to build the future with us.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8829">Jaron  Vietor </person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/livepeer/attachments/slides/5007/export/events/attachments/livepeer/slides/5007/livepeer_fosdem_2022_talk.pdf"/>
        </attachments>
        <links>
          <link href="https://livepeer.org/">Homepage</link>
          <link href="https://video.fosdem.org/2022/D.web3/livepeer.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/livepeer.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-livepeer:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-livepeer:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13027.php">Submit feedback</link>
        </links>
      </event>
      <event id="12700">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>agregore</slug>
        <title>Mixing Peer to Peer Protocols on the Web</title>
        <subtitle>With The Agregore Web Browser</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Peer to peer to protocols (P2P) are useful for creating applications that are less reliant on central physical and digital infrastructure. With a p2p backend, an application can easily move between connecting people over the internet, to local and ad-hoc networks, and working entirely offline. We take this ability a step further by integrating several protocols into web browsers so that applications can be authored and distributed just like any other data in the network.&lt;/p&gt;

&lt;p&gt;This talk will go over some of these protocols, their strengths and weaknesses, and how we have applied them to the web. We'll also have a live demo of what it looks like as a developer.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This talk will be using the desktop version of the open source Agregore Browser, a minimal web browser built on top of the Electron framework which deeply integrates several protocols everywhere that a browser might use a URL.&lt;/p&gt;

&lt;p&gt;The specific protocols we will be going over are IPFS, Hypercore-Protocol, and BitTorrent.&lt;/p&gt;

&lt;p&gt;We'll also be talking about the benefits of using P2P software in ad-hoc mesh networks and how it can enable communities to make the most of their local networks.&lt;/p&gt;

&lt;p&gt;Feel free to install the browser ahead of time if you'd like to follow along for the live coding portion.&lt;/p&gt;</description>
        <persons>
          <person id="8687">Mauve Signweaver</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://agregore.mauve.moe/">Agregore Website</link>
          <link href="https://twitter.com/AgregoreBrowser">Agregore Twitter</link>
          <link href="https://video.fosdem.org/2022/D.web3/agregore.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/agregore.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-agregore:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-agregore:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12700.php">Submit feedback</link>
        </links>
      </event>
      <event id="13140">
        <start>16:30</start>
        <duration>00:20</duration>
        <room>D.web3</room>
        <slug>flux</slug>
        <title>The Peoples' Web3</title>
        <subtitle>Bringing decentralized hosting infrastucture and dapp development to all the corners of the globle.</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Flux Ecosystem is a suite of decentralized computing services and blockchain-as-a-service solutions together to offer an interoperable, decentralized AWS-like development
environment. Flux utilizes a native POW coin to power this ecosystem, providing incentive for hardware hosters, governance on-chain, and bad actor mitigation via staking
requirements for running hardware. The Flux operating system runs on top of Linux to provide the network with verified, enterprise-grade compute power and utilizes the
blockchain to ensure transparency in governance operations.  This allows almost anyone to be rewarded for providing hardware to the network, from anywhere in the world.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8867">Nicholas Pawelk</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://runonflux.io">Main website</link>
          <link href="https://home.runonflux.io">FluxOS Dashboard</link>
          <link href="https://github.com/RunOnFlux">Github</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-flux:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-flux:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13140.php">Submit feedback</link>
        </links>
      </event>
      <event id="13034">
        <start>17:00</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>neighbourhoods</slug>
        <title>Introduction to Neighbourhoods</title>
        <subtitle>A Holochain-based framework for reputation data</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk introduces Neighbourhoods: a proposed organizing principle for social spaces on the distributed web using Holochain. We envision “groupware” (like calendars, simple games, chat, collaborative docs, etc.) decoupled from reputation and group culture metrics (e.g. entry and exit rules, engagement incentives, likes or claps, visibility and feed ordering); in social platforms on the centralized web, these distinct functions are typically combined.
To facilitate neighbourhoods, we are building a language and “interchange” for reputation data on Holochain such that users can connect a portable reputation extension to bundles of Holochain groupware.&lt;/p&gt;

&lt;p&gt;Groups can then use the neighbourhoods framework to bundle p2p modules with reputational and cultural inputs that relate to their particular use cases and style of relating. This also means individuals’ reputation and activity records are stored on their devices, and so can be ported to other neighbourhoods and verified using Holochain’s gossip protocol for data validation. Neighbourhoods is centered on the Holochain ecosystem, but it may also be of interest to dWeb communities and projects aspiring to traffic in “richer” data than ownership claims &amp;amp; token counts - especially when those data support community collective intelligence.&lt;/p&gt;

&lt;p&gt;Much of the system remains to be built, but the core language - &lt;code&gt;rep_lang&lt;/code&gt; - has been integrated with Holochain. We’ll close with a brief demo showing one key aspect of the system: &lt;code&gt;rep_lang&lt;/code&gt; computations being validated by multiple agents on Holochain.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8760">Emaline Friedman</person>
          <person id="8930">Michael Hueschen</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/neighbourhoods/attachments/slides/5020/export/events/attachments/neighbourhoods/slides/5020/Intro_to_NH_slides">Intro to NH slides</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/neighbourhoods/attachments/slides/5021/export/events/attachments/neighbourhoods/slides/5021/Intro_to_NH_demo_slides">Intro to NH demo slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/neighbour-hoods">codebase to be discussed</link>
          <link href="https://neighbourhoods.network">main project page</link>
          <link href="https://video.fosdem.org/2022/D.web3/neighbourhoods.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/neighbourhoods.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-neighbourhoods:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-neighbourhoods:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13034.php">Submit feedback</link>
        </links>
      </event>
      <event id="13035">
        <start>17:30</start>
        <duration>00:35</duration>
        <room>D.web3</room>
        <slug>gun</slug>
        <title>Scaling a Decentralized Metaverse in Browser without Data Leaks</title>
        <subtitle>Hacking old tech to achieve new protocols</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Is a decentralized metaverse with hundreds of millions of users possible? From my experience working on open source tools with over a half billion downloads in a year, the answer is yes. But not through blockchains, tokens, or gimmicks. This talk is for the pure hearted, those who want scale, security, speed, and small code. I'll first briefly cover some mind blowing demos that our community, GUN (a p2p Firebase), has achieved, then showcase a new way to make apps &amp;amp; games that can instantly render user data (without login or registration) without the app itself being able to access it (preventing apps from being able to mine or spy on your data).&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8823">Mark Nadal</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://twitter.com/marknadal/status/1459369619488010243">twitter</link>
          <link href="https://github.com/amark/gun">github</link>
          <link href="https://video.fosdem.org/2022/D.web3/gun.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/gun.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-gun:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-gun:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13035.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.box86">
      <event id="13150">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.box86</room>
        <slug>welcome_box86</slug>
        <title>Welcome to the Box86 stand</title>
        <subtitle/>
        <track>Box86 stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#box86-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#box86-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13150.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.checkmk">
      <event id="13151">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.checkmk</room>
        <slug>welcome_checkmk</slug>
        <title>Welcome to the Checkmk stand</title>
        <subtitle/>
        <track>Checkmk stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#checkmk-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#checkmk-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13151.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.civicrm">
      <event id="13152">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.civicrm</room>
        <slug>welcome_civicrm</slug>
        <title>Welcome to the CiviCRM stand</title>
        <subtitle/>
        <track>CiviCRM stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#civicrm-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#civicrm-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13152.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.opensuse">
      <event id="13153">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.opensuse</room>
        <slug>welcome_opensuse</slug>
        <title>Welcome to the openSUSE stand</title>
        <subtitle/>
        <track>openSUSE stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#opensuse-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#opensuse-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13153.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.debian">
      <event id="13154">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.debian</room>
        <slug>welcome_debian</slug>
        <title>Welcome to the Debian stand</title>
        <subtitle/>
        <track>Debian stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#debian-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#debian-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13154.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.eclipse">
      <event id="13155">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.eclipse</room>
        <slug>welcome_eclipse</slug>
        <title>Welcome to the Eclipse Foundation stand</title>
        <subtitle/>
        <track>Eclipse Foundation stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#eclipse-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#eclipse-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13155.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.fedora">
      <event id="13156">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.fedora</room>
        <slug>welcome_fedora</slug>
        <title>Welcome to the Fedora Project stand</title>
        <subtitle/>
        <track>Fedora Project stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#fedora-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#fedora-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13156.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.foreman">
      <event id="13157">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.foreman</room>
        <slug>welcome_foreman</slug>
        <title>Welcome to the Foreman stand</title>
        <subtitle/>
        <track>Foreman stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#foreman-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#foreman-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13157.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.fossasia">
      <event id="13158">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.fossasia</room>
        <slug>welcome_fossasia</slug>
        <title>Welcome to the FOSSASIA stand</title>
        <subtitle/>
        <track>FOSSASIA stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#fossasia-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#fossasia-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13158.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.fsfe">
      <event id="13159">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.fsfe</room>
        <slug>welcome_fsfe</slug>
        <title>Welcome to the Free Software Foundation Europe stand</title>
        <subtitle/>
        <track>Free Software Foundation Europe stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#fsfe-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#fsfe-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13159.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.freebsd">
      <event id="13160">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.freebsd</room>
        <slug>welcome_freebsd</slug>
        <title>Welcome to the FreeBSD Project stand</title>
        <subtitle/>
        <track>FreeBSD Project stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#freebsd-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#freebsd-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13160.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.gnome">
      <event id="13161">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.gnome</room>
        <slug>welcome_gnome</slug>
        <title>Welcome to the GNOME stand</title>
        <subtitle/>
        <track>GNOME stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#gnome-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#gnome-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13161.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.gsoc">
      <event id="13162">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.gsoc</room>
        <slug>welcome_gsoc</slug>
        <title>Welcome to the Google Summer of Code stand</title>
        <subtitle/>
        <track>Google Summer of Code stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#gsoc-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#gsoc-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13162.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.haiku">
      <event id="13163">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.haiku</room>
        <slug>welcome_haiku</slug>
        <title>Welcome to the Haiku stand</title>
        <subtitle/>
        <track>Haiku stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#haiku-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#haiku-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13163.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.illumos">
      <event id="13164">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.illumos</room>
        <slug>welcome_illumos</slug>
        <title>Welcome to the illumos stand</title>
        <subtitle/>
        <track>illumos stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#illumos-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#illumos-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13164.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.kde">
      <event id="13165">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.kde</room>
        <slug>welcome_kde</slug>
        <title>Welcome to the KDE Community stand</title>
        <subtitle/>
        <track>KDE Community stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#kde-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kde-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13165.php">Submit feedback</link>
        </links>
      </event>
      <event id="13552">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>S.kde</room>
        <slug>kde_plasme_mobile</slug>
        <title>Plasma Mobile in 2022</title>
        <subtitle>Bhushan Shah</subtitle>
        <track>KDE Community stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#kde-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kde-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13552.php">Submit feedback</link>
        </links>
      </event>
      <event id="13561">
        <start>11:15</start>
        <duration>00:30</duration>
        <room>S.kde</room>
        <slug>kde_kalendar_aonadi</slug>
        <title>Kalendar and the case for Akonadi</title>
        <subtitle>Claudio Cambra</subtitle>
        <track>KDE Community stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#kde-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kde-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13561.php">Submit feedback</link>
        </links>
      </event>
      <event id="13553">
        <start>13:00</start>
        <duration>01:00</duration>
        <room>S.kde</room>
        <slug>kde_eco</slug>
        <title>KDE Eco</title>
        <subtitle>Joseph De Veaugh-Geiss</subtitle>
        <track>KDE Community stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#kde-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kde-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13553.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.kiwi">
      <event id="13166">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.kiwi</room>
        <slug>welcome_kiwi</slug>
        <title>Welcome to the Kiwi TCMS stand</title>
        <subtitle/>
        <track>Kiwi TCMS stand</track>
        <type>standtrack</type>
        <language/>
        <abstract>&lt;p&gt;Kiwi TCMS is the leading open source test management system for both manual &amp;amp; automated testing with over 1 million downloads. It has been made by testers and licensed under GPLv2. Our mission is to transform the testing process by making it more organized, transparent &amp;amp; accountable for everyone on your team. Kiwi TCMS is used during software testing and quality assurance to collect information about what, when and how has been tested. This information is later used when making a go/no-go decision before a release, monitoring and planning the workload of the QA team or answering questions like "How did we test this?" and "Why didn't we catch this bug before?"! 1m downloads from Docker Hub&lt;/p&gt;</abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#kiwi-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kiwi-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13166.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.libreoffice">
      <event id="13167">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.libreoffice</room>
        <slug>welcome_libreoffice</slug>
        <title>Welcome to the LibreOffice stand</title>
        <subtitle/>
        <track>LibreOffice stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13167.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.libresoc">
      <event id="13168">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.libresoc</room>
        <slug>welcome_libresoc</slug>
        <title>Welcome to the LibreSOC Project stand</title>
        <subtitle/>
        <track>LibreSOC Project stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#libresoc-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libresoc-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13168.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.mariadb">
      <event id="13169">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.mariadb</room>
        <slug>welcome_mariadb</slug>
        <title>Welcome to the MariaDB Foundation stand</title>
        <subtitle/>
        <track>MariaDB Foundation stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#mariadb-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mariadb-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13169.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.matrix">
      <event id="13170">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.matrix</room>
        <slug>welcome_matrix</slug>
        <title>Welcome to the Matrix stand</title>
        <subtitle/>
        <track>Matrix stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#matrix-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13170.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.mautic">
      <event id="13171">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.mautic</room>
        <slug>welcome_mautic</slug>
        <title>Welcome to the Mautic stand</title>
        <subtitle>Discover the power of open source marketing automation with Mautic!</subtitle>
        <track>Mautic stand</track>
        <type>standtrack</type>
        <language/>
        <abstract>&lt;p&gt;Discover the power of open source marketing automation with Mautic!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#mautic-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mautic-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13171.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.nextcloud">
      <event id="13172">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.nextcloud</room>
        <slug>welcome_nextcloud</slug>
        <title>Welcome to the Nextcloud Hub stand</title>
        <subtitle/>
        <track>Nextcloud Hub stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#nextcloud-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#nextcloud-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13172.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.ntop">
      <event id="13173">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.ntop</room>
        <slug>welcome_ntop</slug>
        <title>Welcome to the ntop stand</title>
        <subtitle/>
        <track>ntop stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#ntop-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ntop-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13173.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.oniro">
      <event id="13174">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.oniro</room>
        <slug>welcome_oniro</slug>
        <title>Welcome to the Oniro Project stand</title>
        <subtitle>The Distributed Operating System That Connects Consumer Devices Big and Small</subtitle>
        <track>Oniro Project stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#oniro-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#oniro-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13174.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.onlyoffice">
      <event id="13175">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.onlyoffice</room>
        <slug>welcome_onlyoffice</slug>
        <title>Welcome to the ONLYOFFICE stand</title>
        <subtitle/>
        <track>ONLYOFFICE stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#onlyoffice-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#onlyoffice-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13175.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.openmandriva">
      <event id="13176">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.openmandriva</room>
        <slug>welcome_openmandriva</slug>
        <title>Welcome to the OpenMandriva stand</title>
        <subtitle/>
        <track>OpenMandriva stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#openmandriva-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openmandriva-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13176.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.opentap">
      <event id="13177">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.opentap</room>
        <slug>welcome_opentap</slug>
        <title>Welcome to the OpenTAP stand</title>
        <subtitle/>
        <track>OpenTAP stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#opentap-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#opentap-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13177.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.openuk">
      <event id="13178">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.openuk</room>
        <slug>welcome_openuk</slug>
        <title>Welcome to the OpenUK stand</title>
        <subtitle/>
        <track>OpenUK stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#openuk-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openuk-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13178.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.openwifi">
      <event id="13179">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.openwifi</room>
        <slug>welcome_openwifi</slug>
        <title>Welcome to the openwifi stand</title>
        <subtitle>The open-source WiFi chip (FPGA currently)</subtitle>
        <track>openwifi stand</track>
        <type>standtrack</type>
        <language/>
        <abstract>&lt;p&gt;There are many WiFi chips around each one. The WiFi router, the smart light, the TV, the phone, etc., all have WiFi chips inside. Ever imagine replacing those chips with an open-source design?&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://github.com/open-sdr/openwifi"&gt;openwifi&lt;/a&gt; project has been online for more than 2 years. We have paved solid steps towards an open-source WiFi chip. Now if you have commercial off the shelf FPGA boards, you can download our design onto your board and start to use this FPGA based WiFi in the same way as other commercial WiFi chips!&lt;/p&gt;

&lt;p&gt;Related event:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Feb 6 13:10 (Brussels time): &lt;a href="https://fosdem.org/2022/schedule/event/radio_openwifi/"&gt;Opensource WiFi chip (openwifi) progress and future plan&lt;/a&gt; in &lt;a href="https://fosdem.org/2022/schedule/track/free_software_radio/"&gt;Free Software Radio devroom&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Feb 6 11:20 (Brussels time): &lt;a href="https://fosdem.org/2022/schedule/event/openwifipynqz1/"&gt;Bring openwifi to PYNQ-Z1 with ultra low cost&lt;/a&gt; in &lt;a href="https://fosdem.org/2022/schedule/track/libre_open_vlsi_and_fpga/"&gt;Libre-Open VLSI and FPGA devroom&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;a href="/2022/stands.fosdem.org/stands/openwifi/"&gt;openwifi stand&lt;/a&gt; welcome you the whole weekend.&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/open-sdr/openwifi">The openwifi Linux driver and user space tools</link>
          <link href="https://github.com/open-sdr/openwifi-hw">The openwifi FPGA/chip design</link>
          <link href="https://github.com/open-sdr">The main openwifi github site</link>
          <link href="https://chat.fosdem.org/#/room/#openwifi-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openwifi-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13179.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.ow2">
      <event id="13180">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.ow2</room>
        <slug>welcome_ow2</slug>
        <title>Welcome to the OW2 Open Source Community stand</title>
        <subtitle/>
        <track>OW2 Open Source Community stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#ow2-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ow2-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13180.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.pharo">
      <event id="13181">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.pharo</room>
        <slug>welcome_pharo</slug>
        <title>Welcome to the Pharo stand</title>
        <subtitle/>
        <track>Pharo stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#pharo-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#pharo-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13181.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.postgresql">
      <event id="13182">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.postgresql</room>
        <slug>welcome_postgresql</slug>
        <title>Welcome to the PostgreSQL stand</title>
        <subtitle/>
        <track>PostgreSQL stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#postgresql-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13182.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.pulp">
      <event id="13183">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.pulp</room>
        <slug>welcome_pulp</slug>
        <title>Welcome to the Pulp stand</title>
        <subtitle/>
        <track>Pulp stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#pulp-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#pulp-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13183.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.reactos">
      <event id="13184">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.reactos</room>
        <slug>welcome_reactos</slug>
        <title>Welcome to the ReactOS stand</title>
        <subtitle/>
        <track>ReactOS stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#reactos-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#reactos-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13184.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.refpersys">
      <event id="13185">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.refpersys</room>
        <slug>welcome_refpersys</slug>
        <title>Welcome to the RefPerSys stand</title>
        <subtitle/>
        <track>RefPerSys stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#refpersys-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#refpersys-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13185.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.schulfrei">
      <event id="13186">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.schulfrei</room>
        <slug>welcome_schulfrei</slug>
        <title>Welcome to the schul-frei stand</title>
        <subtitle/>
        <track>schul-frei stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#schulfrei-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#schulfrei-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13186.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.apache">
      <event id="13187">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.apache</room>
        <slug>welcome_apache</slug>
        <title>Welcome to the The Apache Software Foundation stand</title>
        <subtitle/>
        <track>The Apache Software Foundation stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#apache-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#apache-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13187.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.ubuntu">
      <event id="13188">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.ubuntu</room>
        <slug>welcome_ubuntu</slug>
        <title>Welcome to the Ubuntu stand</title>
        <subtitle/>
        <track>Ubuntu stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#ubuntu-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ubuntu-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13188.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.xcpng">
      <event id="13189">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.xcpng</room>
        <slug>welcome_xcpng</slug>
        <title>Welcome to the XCP-ng stand</title>
        <subtitle/>
        <track>XCP-ng stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#xcpng-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#xcpng-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13189.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.xwiki">
      <event id="13523">
        <start>09:30</start>
        <duration>00:30</duration>
        <room>S.xwiki</room>
        <slug>welcome_xwiki</slug>
        <title>Welcome to the XWiki &amp; CryptPad stand</title>
        <subtitle/>
        <track>XWiki &amp; CryptPad stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#xwiki-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#xwiki-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13523.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="I.infodesk">
      <event id="13010">
        <start>09:00</start>
        <duration>09:00</duration>
        <room>I.infodesk</room>
        <slug>infodesk_saturday</slug>
        <title>The Virtual FOSDEM Infodesk (Saturday)</title>
        <subtitle/>
        <track>Infodesk</track>
        <type>infodesk</type>
        <language/>
        <abstract>&lt;p&gt;Need any assistance during the event?  Join us in here!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#infodesk:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#infodesk:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13010.php">Submit feedback</link>
        </links>
      </event>
    </room>
  </day>
  <day index="2" date="2022-02-06">
    <room name="K.fosdem">
      <event id="13550">
        <start>18:00</start>
        <duration>00:30</duration>
        <room>K.fosdem</room>
        <slug>closing_fosdem</slug>
        <title>Closing FOSDEM 2022</title>
        <subtitle/>
        <track>FOSDEM</track>
        <type>maintrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
          <person id="6">FOSDEM Staff</person>
          <person id="497">Richard Hartmann</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/K.fosdem/closing_fosdem.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/K.fosdem/closing_fosdem.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#fosdem-keynotes:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#fosdem-keynotes:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#fosdem-closing_fosdem:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#fosdem-closing_fosdem:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13550.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="M.community">
      <event id="12573">
        <start>13:30</start>
        <duration>01:00</duration>
        <room>M.community</room>
        <slug>community_incentives</slug>
        <title>Establishing an incentivised partners programme in an open source project</title>
        <subtitle/>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;While money is helpful in open source projects, hands-on contributions are probably more valuable to the long term health and sustainability of the project.&lt;/p&gt;

&lt;p&gt;In the Mautic project, we wanted to establish a partners programme which would allow us to highlight to our community the organisations who were both financially supporting the project as a sponsor, and were actively contributing to the project.  Here's how we did it.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this session I’ll outline how we came up with a way to make the financial element equitable for partners around the world, and the steps we took toward ensuring that organisations couldn’t just buy their way to partner status.&lt;/p&gt;

&lt;p&gt;We’ll dig into thorny topics like determining what we mean by contributions, how we recognise non-code contributions alongside code contributions, and the tooling that underpins it all.&lt;/p&gt;

&lt;p&gt;I’ll also explain how we’ve built our partners portal to incentivise active contributions from the organisations, and some of the improvements that we’re thinking of making in the future.&lt;/p&gt;</description>
        <persons>
          <person id="6835">Ruth Cheesley</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/community_incentives/attachments/slides/5144/export/events/attachments/community_incentives/slides/5144/FOSDEM_2022_Parters_Program.pdf">FOSDEM - Establishing an incentivised partners program</attachment>
        </attachments>
        <links>
          <link href="https://opensource.com/article/21/12/open-source-project-partner-program">opensource.com write up</link>
          <link href="https://mautic.org/mautic-community-partners">Mautic Community Partners Program</link>
          <link href="https://video.fosdem.org/2022/M.community/community_incentives.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_incentives.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12573.php">Submit feedback</link>
        </links>
      </event>
      <event id="12390">
        <start>14:30</start>
        <duration>01:00</duration>
        <room>M.community</room>
        <slug>community_success</slug>
        <title>Celebrating failure or success? Why not both?</title>
        <subtitle/>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;As an engineer failure is not a matter of if but when.
We all know that corrective actions are expensive, that is why we focus on preventive actions.
The knowledge gained from understanding and embracing failure is potentially the source of better preventive actions.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Failure is an inevitable part of success. Failure in the context of innovation efforts has helped  thousands of start-up companies to succeed but in the context of a known execution process, it can harm results or reputations or create undue risk.
In software development we are situated at the cross road between innovation and known process so how do we benefit from failure and achieve success?
In this session we will explore several studies and best practices of successful companies that have embrace them both.&lt;/p&gt;</description>
        <persons>
          <person id="8512">Ixchel Ruiz</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.community/community_success.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_success.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12390.php">Submit feedback</link>
        </links>
      </event>
      <event id="13052">
        <start>15:30</start>
        <duration>00:45</duration>
        <room>M.community</room>
        <slug>community_diversity</slug>
        <title>How Implicit Bias Affects Diversity and Inclusion in Open Source.</title>
        <subtitle/>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;The topic of diversity and inclusion has for long been practised in theory within open source communities. Yet, in reality, our believes in diversity and inclusion is frequently questioned because of our biases, particularly Implicit Bias. In this session, I will discuss these biases are, how they affect open-source communities and how to improve on these biases.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Open Source communities operate on a set of values that include a commitment to inclusion and diversity.  The idea that the Tech Ecosystem at large is faced with the challenges of Diversity and Inclusion is not a myth.
 To everyone, there is a level of implicit bias and beliefs about various social and identity groups to some degree. Implicit biases are the attitudes or stereotypes that affect our understanding, actions, and decisions in an unconscious manner.
 Studies have shown that the majority of the problems posed by diversity and inclusion result from implicit bias. As users, maintainers and contributors of Open Source Software, we may have encountered different marginalized groups that have shared their encounters of bias in Open Source communities.
  Most persons are ignorant of this bias and its impact on the victims. In an Open Source Project, a typical example of implicit bias could be, assuming that a female employee will be less competent for a role compared to a male employee.
 In this session, I will be talking about: What Diversity and Inclusion is, Why Diversity and Inclusion matter? Challenges faced by underrepresented groups in open source communities, Identifying Bias, What implicit Bias is, The different forms of implicit Bias, Why it is important to create awareness of this bias and How these biases can be improved.&lt;/p&gt;</description>
        <persons>
          <person id="7614">Anita Ihuman</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.community/community_diversity.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_diversity.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13052.php">Submit feedback</link>
        </links>
      </event>
      <event id="12459">
        <start>16:15</start>
        <duration>00:45</duration>
        <room>M.community</room>
        <slug>community_recognition</slug>
        <title>Are we being inclusive with our community recognitions? </title>
        <subtitle/>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Recognizing community members is one of the most enjoyable activities for community managers. It is a great opportunity to thank people for their work and highlight their contributions to the rest of the community. However, we need to evaluate if we’re truly being inclusive with our community recognitions. For example, when discussing contributors, we still see a lot of emphasis on the volume of contributions on project repositories (i.e., code) that some may find intimidating. This focus on code is partly because contributions on tools like GitHub and GitLab are easier to measure and quantify.&lt;/p&gt;

&lt;p&gt;On the other hand, it can be more challenging to measure (or even notice) how much a community member is helping others on platforms like Discord, Matrix, Slack, etc. When someone helps a newcomer by answering a quick question in chat, it’s easy to miss that among other discussion threads. Even though it can be more challenging to quantify non-code contributions, it’s crucial to look beyond repositories to see how people are helping to improve our communities. In addition to contributions in chat-like platforms, this can include sharing their use cases, participating in meetups, providing honest feedback in 1-on-1 conversations, etc. Looking across a broad spectrum of contributions will help ensure that we recognize everyone regardless of their background, interests, and skillset.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Also, not everyone is comfortable with public recognition. Some may feel uncomfortable being in the spotlight or even think what they have done is not significant enough (sometimes I see this with contributors from underrepresented groups). In these instances, it is important to find ways to let them know that the community appreciates their work without putting them in an awkward position.&lt;/p&gt;

&lt;p&gt;In this talk, Ray will share his experience identifying different contributions, community recognition examples (both good and bad), and feedback he received on community recognition programs. There will also be a discussion on how inclusive recognition is vital for strengthening the sense of belonging in the community.&lt;/p&gt;</description>
        <persons>
          <person id="5699">Ray Paik</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/community_recognition/attachments/slides/4998/export/events/attachments/community_recognition/slides/4998/FOSDEM22_more_inclusive_recogrnitions.pdf">More inclusive recognitions</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/community_recognition/attachments/other/5258/export/events/attachments/community_recognition/other/5258/Q_A_screenshot_1">Screenshot from Q&amp;A (1 of 4)</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/community_recognition/attachments/other/5259/export/events/attachments/community_recognition/other/5259/Q_A_screenshot_2">Screenshot from Q&amp;A (2 of 4)</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/community_recognition/attachments/other/5260/export/events/attachments/community_recognition/other/5260/Q_A_screenshot_3">Screenshot from Q&amp;A (3 of 4)</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/community_recognition/attachments/other/5261/export/events/attachments/community_recognition/other/5261/Q_A_screenshot_4">Screenshot from Q&amp;A (4 of 4)</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.community/community_recognition.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_recognition.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12459.php">Submit feedback</link>
        </links>
      </event>
      <event id="12587">
        <start>17:00</start>
        <duration>01:00</duration>
        <room>M.community</room>
        <slug>community_mentorship</slug>
        <title>Enabling Next Gen of Diverse Maintainers and Employees Through Mentorship</title>
        <subtitle/>
        <track>Community</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Finding brilliant and diverse engineers, who could maintain complex open-source projects, lead communities and be productive employees is an extremely hard task these days. It’s easy for aspiring talents to feel lost, be ashamed and give up in the process due to the transparent aspect of work in open source. We believe we found a quite neat shortcut to this!&lt;/p&gt;

&lt;p&gt;The solution is called “structured mentoring” and in this talk, Prem and Bartek, maintainers of CNCF projects, will explain why this is a game-changer, based on their experience mentoring 20+ talents for the Thanos and Prometheus projects.&lt;/p&gt;

&lt;p&gt;There are many mentoring programs like LFX, GSoC or Outreachy but it is easy to make mistakes, get lost and have no results from mentoring if not done carefully.&lt;/p&gt;

&lt;p&gt;Join us to learn what processes worked the best to get the most out of the open-source mentorship. Learn what mistakes to avoid, how to get mentored and how to start mentoring in your company or open source project today&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5750">Bartek Plotka</person>
          <person id="8931">Prem Saraswat</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/community_mentorship/attachments/slides/5245/export/events/attachments/community_mentorship/slides/5245/Slides">Slides</attachment>
        </attachments>
        <links>
          <link href="https://thanos.io/tip/contributing/mentorship.md/">Mentorship Guide</link>
          <link href="https://www.bwplotka.dev/2020/thanos-mentoring-office-hours/">Mentorship Guide 2</link>
          <link href="https://community.cncf.io/cncf-mentees-meetup/">Mentoring Meetups</link>
          <link href="https://video.fosdem.org/2022/M.community/community_mentorship.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.community/community_mentorship.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#community:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12587.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="M.misc">
      <event id="13097">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>M.misc</room>
        <slug>misc_foss</slug>
        <title>All the World's a Stage and FOSS is playing many parts</title>
        <subtitle>With the spotlight of the world's Governments shining on security, sustainability and software, how will FOSS survive the limelight?</subtitle>
        <track>Miscellaneous</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;The FOSS Communities have been debating how to manage security, sustainability and funding of FOSS for years but today a global and political lens is being shone on them.&lt;/p&gt;

&lt;p&gt;Commercial debates over licensing and revenue models around FOSS based businesses peak in 2021 with the Elastic transition away from FOSS to an SSPL licence and the fallout and debate from this.&lt;/p&gt;

&lt;p&gt;The European Commission's Digital Decade is clear that its basis will be a FOSS infrastructure and Europe has been passing laws and regulations to support its open first approach, as it seeks digital and data sovereignty.&lt;/p&gt;

&lt;p&gt;The inevitable success and adoption of FOSS in our national infrastructures and recent security issues have the minds of Governments focused on FOSSS, to the extent that the White House plans a meeting to discuss FOSS security in January having issued an ordinance recommending the use of Software Bill of Materials.&lt;/p&gt;

&lt;p&gt;China's Ministry of Industry and Information Technology has shared a 5 year software plan saying "software defines the world of the future, open source determines the future of software," as it plans global collaboration to improve its open source activities.&lt;/p&gt;

&lt;p&gt;In the UK, hosting COP26 shone a spotlight on energy and the UK Energy Sector Digitalisation Task force which has already suggested Open Data, will consider the use of open source software by default in its recommendations to Government in January. Whilst the NHS' data strategy issued in 2021 requires that open source software should be the default in healthcare.&lt;/p&gt;

&lt;p&gt;This talk will stitch together these global threads, laws and policies to take a holistic view on the insurmountable success of FOSS in the last decade and the inevitable challenges being faced as a consequence of that success and the very nature and heart of FOSS in the Commons.&lt;/p&gt;

&lt;p&gt;Sharing some policy suggestions and thoughts this talk will consider whether it may be time to shift the landscape. Is 2022 the year to recognise the need for FOSS to be characterised as a public good and to secure the interaction not only of business but of the State in funding and securing FOSS in the long term? How can this ensure sustainability of FOSS through its maintenance and sustainability of the planet by elevating the role of FOSS within environmental sustainability?&lt;/p&gt;

&lt;p&gt;With a deep consideration of recent economic and policy discussions this keynote talk with pull many strands together to start 2022 with a focus on FOSS, funding and a secure and sustainable future.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6847">Amanda Brock</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.youtube.com/watch?v=tzQZoW996fQ">talk</link>
          <link href="https://021.berlinbuzzwords.de/session/commercial-models-and-open-source-how-revenue-generation-and-open-source-fit-together">Berlin Buzzwords talk commercial models</link>
          <link href="https://www.itpro.co.uk/development/open-source/356939/it-pro-live-its-open-under-the-cloud">IT Pro Keynote open and cloud</link>
          <link href="https://www.youtube.com/watch?v=yWK_d3t_MCk">talk commerical</link>
          <link href="https://https://www.brighttalk.com/webcast/18708/507033">Percona Live Keynote</link>
          <link href="https://https://www.facebook.com/watch/?v=968225393620820">Keynote</link>
          <link href="https://https://community.cncf.io/events/details/cncf-kcd-uk-presents-kubernetes-community-days-uk-2021/">Keynote</link>
          <link href="https://video.fosdem.org/2022/M.misc/misc_foss.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.misc/misc_foss.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#misc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#misc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13097.php">Submit feedback</link>
        </links>
      </event>
      <event id="12524">
        <start>11:00</start>
        <duration>01:00</duration>
        <room>M.misc</room>
        <slug>misc_business</slug>
        <title>The Business Of Open Source</title>
        <subtitle>How big money, investors, and greed are changing open source forever</subtitle>
        <track>Miscellaneous</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;The changing landscape of the open-source industry has taken a potentially dark turn in the last few years. Instead of focusing on inclusion, innovation, and collaboration a new generation of so called open source drive companies has emerged flush with investor money and looking to maximize the returns for their investors and shareholders at all costs. In an effort to accelerate “revenue” and “profits” these companies are looking to rewrite the definition of what they consider open source. We are in a battle for not only the hearts and minds of the FOSS community but our collective future. As new developers start open source projects more will be compelled to choose more restrictive licensing models ( i.e. SSPL ), invest less in the community, and “control” as much of the code and product as possible. I will talk about the trend, talk about the common business models, and offer a few alternatives.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8577">Matt Yonkovit</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.misc/misc_business.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.misc/misc_business.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#misc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#misc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12524.php">Submit feedback</link>
        </links>
      </event>
      <event id="12716">
        <start>12:00</start>
        <duration>00:45</duration>
        <room>M.misc</room>
        <slug>misc_europe</slug>
        <title>European digital sovereignty and open source</title>
        <subtitle>How Europe is regulating big tech and what's in it for FLOSS</subtitle>
        <track>Miscellaneous</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;The European Union is working with great energy on new rules for digital markets, targetting first of all the big global Internet platforms. Building on the global impact of the GDPR, efforts like the Digital Services Act, the Digital Markets Act, the AI Regulation, the Data Governance Act and the GAIA-X initiative attempt to restrain the superpowers of the big American and Chinese companies and promote rights and opportunities for Europeans, restoring the EU's ability to control its own slice of the Internet and reducing the dependency on foreign products and services. Open source is one of the strategic tools for this objective, and open source projects and companies could be benefited by these changes. Watch the talk to learn what is happening!&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The talk will start by recollecting how we started up with an open, interoperable Internet that allowed everyone to cooperate and deploy new content and services, and ended up with a concentration of money and power of unseen scale in the history of mankind. Technical and market developments are centralizing the Internet more and more into the hands of a few companies, very concentrated in terms of geography, jurisdiction, ownership and views of the world. We will discuss how the EU plans to counter these trends, what the various regulations and projects are, and how they would work.&lt;/p&gt;

&lt;p&gt;We will then focus on how open source in Europe could be impacted by the new rules. Some of the provisions are particularly in line with an open, distributed Internet architecture, mandating the adoption of open standards and interoperability and preventing dominant players from advantaging their own applications and services over independent ones. Social media, instant messaging and mobile apps are three sectors that could be particularly affected.&lt;/p&gt;

&lt;p&gt;In the end, the talk aims to create awareness in the European open source community around the changing regulatory scenario, so that we are ready for it.&lt;/p&gt;</description>
        <persons>
          <person id="4611">Vittorio Bertola</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/misc_europe/attachments/slides/5237/export/events/attachments/misc_europe/slides/5237/European_digital_sovereignty_and_open_source_FOSDEM_2022.pdf">Slides for the talk</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.misc/misc_europe.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.misc/misc_europe.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#misc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#misc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12716.php">Submit feedback</link>
        </links>
      </event>
      <event id="12743">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>M.misc</room>
        <slug>misc_raku</slug>
        <title>Debunking The Myths About The Raku® Language</title>
        <subtitle>Let's talk about some common misconceptions about the Raku language and why it is not Perl6 anymore</subtitle>
        <track>Miscellaneous</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;The Raku language, formerly known as Perl6, sometimes gets incorrect coverage when it comes to "expert opinions". In this talk we will consider the common misconceptions about the language, what's wrong about them, and why your impression about the language might be wrong. Let's see how we can make it much better!&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Developers are mostly busy people. Such resource as "spare time" is scarce among them and must be used wisely. When there is no time to research a topic on our own, we trust others to do it for us and express their opinion, which we tend to accept. But, unfortunately, for many reasons those opinions may not represent the real state of the things. When it comes to Raku, some still consider it based on factors, which are no longer valid, or which influence the language in an anticipated way. This talk in intended to provide you with real information about the Raku language, its strong and, perhaps, weak sides. Bight first of all, this talk is about letting you to build up your own view at the language.&lt;/p&gt;</description>
        <persons>
          <person id="8627">Vadim Belman</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://raku.org">The Raku® Programming Language</link>
          <link href="https://rakudo.org">The most mature, production-ready implementation of the Raku language.</link>
          <link href="https://video.fosdem.org/2022/M.misc/misc_raku.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.misc/misc_raku.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#misc:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#misc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12743.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="M.rtc">
    </room>
    <room name="M.security">
      <event id="13207">
        <start>10:00</start>
        <duration>00:25</duration>
        <room>M.security</room>
        <slug>security_seamless_kernel</slug>
        <title>Seamless Kernel Update</title>
        <subtitle>Seamless kernel update practice in linux based on kexec and criu</subtitle>
        <track>Security</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Currently, operating systems have become increasingly complex and thus more sensitive to security problems and performance issues. In some circumstances, developers have to reboot their systems in order to patch security vulnerabilities, fix bugs, and add new features, which will bring unavoidable downtime for running applications. Live-patch is an elegant solution. But, it can only work in 30 percent of circumstances. In our project, we put another solution into practice. We use a checkpoint-and-restart mechanism to retore applications' status and then switch the kernel fastly.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8888">Longjun Luo</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/security_seamless_kernel/attachments/slides/5061/export/events/attachments/security_seamless_kernel/slides/5061/Seamless_Kernel_Update.pdf">Seamless Kernel Update.pdf</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.security/security_seamless_kernel.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.security/security_seamless_kernel.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#security:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#security:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13207.php">Submit feedback</link>
        </links>
      </event>
      <event id="13203">
        <start>11:00</start>
        <duration>00:25</duration>
        <room>M.security</room>
        <slug>security_secpaver</slug>
        <title>secPaver: Security Policy Development Tool</title>
        <subtitle/>
        <track>Security</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Security design is an very important step in the software development. In order to meet the principle of least privilege, developers make rules for applications based on data flow and control flow of processes, such as SELinux and AppArmor. This step can be automated with secPaver. With the permission description of application, secPaver can generate security policy for different security mechanisms. By this way, security design can be simplified, and developers do not need to know many details about security mechanisms.&lt;/p&gt;

&lt;p&gt;secPaver is a policy development tool that supports multiple security mechanisms. It aims to help users implement end-to-end security policy development, including visible policy design, iterative development, and policy release. It provides functions such as policy configuration, automatic generation, running test, missing rule gathering, and policy package export. secPaver shields security mechanism details and abstracts unified policy configuration file definitions and operation interfaces for different security mechanisms, improving policy development efficiency and reducing learning costs for developers.&lt;/p&gt;

&lt;p&gt;project address: https://gitee.com/openeuler/secpaver/&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8891">HuaxinLu</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.security/security_secpaver.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.security/security_secpaver.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#security:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#security:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13203.php">Submit feedback</link>
        </links>
      </event>
      <event id="12912">
        <start>12:00</start>
        <duration>00:40</duration>
        <room>M.security</room>
        <slug>security_rust</slug>
        <title>Why safe programming matters and why Rust</title>
        <subtitle>Fast, safe and sustainable programming with Rust</subtitle>
        <track>Security</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Security in programming starts from the programming language itself. The majority of CVEs we encounter are due to memory safety issues and I'm here to talk about how a language like Rust is the way forward in avoiding those. Rust is a great programming language. It is a developer favorite and is rapidly gaining a foothold outside of systems programming. It has the potential to become a great general-purpose language with little of the overhead of traditional high-level general-purpose languages. Rust is fast, safe, and sustainable. Today I'm going to take you through the strengths and weaknesses of Rust and why it will be a great general-purpose language. Beware, I'll be doing comparisons with your favorite languages.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8784">Deepu  K Sasidharan</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/security_rust/attachments/slides/5166/export/events/attachments/security_rust/slides/5166/Why_safe_programming_matters_and_why_Rust.pdf">Why safe programming matters and why Rust?</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.security/security_rust.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.security/security_rust.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#security:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#security:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12912.php">Submit feedback</link>
        </links>
      </event>
      <event id="13012">
        <start>13:00</start>
        <duration>00:45</duration>
        <room>M.security</room>
        <slug>security_sbom</slug>
        <title>The distinctive qualities of Software Bill of Materials</title>
        <subtitle/>
        <track>Security</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Software Bill of Materials (SBOMs) have emerged as a powerful tool for
guiding supply chain security in modern software development
environments. As an 'ingredients list' of files, package dependencies
and other artefacts that a piece of software is made up of, Software
Bill of Materials are becoming an essential part of modern software
development practices.&lt;/p&gt;

&lt;p&gt;Open source software provides great transparency and can yield rapid
vulnerability patching, but this is too often compromised by sprawling
dependency trees which make it difficult to find vulnerable components
in larger software projects. With SBOMs, there's a way of effectively
cataloguing software components and the package metadata needed to check
the integrity, pedigree and provenance of software supply chains. This
talk will cover the benefits of having a common standard for creating,
sharing and consuming Software Bill of Materials, what SBOMs should and
should not contain, and how to use SBOMs to inform security measures
across the diverse range of package ecosystems.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In particular, this talk will cover the distinctive qualities of
effective Software Bill of Materials:&lt;/p&gt;

&lt;p&gt;Immutability - it may be tempting to include known vulnerabilities and
other dynamic data in SBOMs, but this leads to uncertainty and
duplication of effort when that data inevitably changes. This talk will
show how to link dynamic data into SBOMs in a way that maintains the
SBOM's immutability.&lt;/p&gt;

&lt;p&gt;Verifiability - it's hard to trust an SBOM when you can't verify that
its contents are correct. Including robust cryptographic hashes is a
critical part of creating SBOMs. This talk will show how relationships
in SBOMs can be used to associate the hashes of build artefacts with
source code, providing a way to trace back to the original projects even
when programs are statically linked!&lt;/p&gt;

&lt;p&gt;Compatibility - no one program can check for vulnerabilities of all the
different types and across all package ecosystems, so the use of SBOMs
as a compatible format for communication between security tools is
essential for dependency analysis at scale. This talk will cover the
current state of compatibility between security tools, concluding with
practical ways that developers can integrate SBOM creation and ingestion
into their build systems.&lt;/p&gt;</description>
        <persons>
          <person id="8650">Sebastian Crane</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.security/security_sbom.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.security/security_sbom.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#security:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#security:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13012.php">Submit feedback</link>
        </links>
      </event>
      <event id="12457">
        <start>14:00</start>
        <duration>00:45</duration>
        <room>M.security</room>
        <slug>security_trousseau</slug>
        <title>Trousseau - the Kubernetes Key Management Service provider</title>
        <subtitle>How to keep all your Kubernetes secrets safe the native way</subtitle>
        <track>Security</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;By design, Kubernetes will store secrets encoded in base64 within its etcd resulting in an insecure solution.&lt;br/&gt;
While a couple commercial and open-source solutions exist to solve this problem, they all call for a separate set of tools, skills and limitations along with hardstop from CISO and Security Architect.
Kubernetes put in place a KMS provider plugin framework and Trousseau leverages it to solve the secret management using standard Kubernetes API secret objects and constructs.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;While there are significant efforts to improve Kubernetes component layers, the state of Secret Management is not receiving much interests.
Using etcd to store API object definition &amp;amp; states, Kubernetes secrets are encoded in Base64 and shipped into the key value store database. Even if the filesystems on which etcd runs are encrypted, the secrets are still not.&lt;/p&gt;

&lt;p&gt;Instead of leveraging the native Kubernetes way to manage secrets, commercial and open source solutions solve this design flaw by leveraging different approaches all using different toolsets or practices. This leads to training and maintaining niche skills and tools increasing cost and complexity of Kubernetes day 0, 1 and 2.&lt;/p&gt;

&lt;p&gt;Once deployed, Trousseau will enable seamless secret management using the native Kubernetes API and kubectl CLI usage while leveraging an existing Key Management Service (KMS) provider.
How? By using using the Kubernetes KMS provider framework to provide an envelop encryption scheme to encrypt secrets on the fly.&lt;/p&gt;</description>
        <persons>
          <person id="6458">Romuald Vandepoel</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/security_trousseau/attachments/slides/5074/export/events/attachments/security_trousseau/slides/5074/fosdem2022_trousseau_k8s_kms_provider_20220206">Trousseau - the Kubernetes Key Management Service provider</attachment>
        </attachments>
        <links>
          <link href="https://github.com/Trousseau-io/trousseau">Trousseau Project Repository</link>
          <link href="https://trousseau.io">Trousseau website</link>
          <link href="https://archive.fosdem.org/2021/schedule/event/kubernetes_secret_management/">Fosdem 2021 - Lightning Talk - Secrets or not, but don't clear text</link>
          <link href="https://video.fosdem.org/2022/M.security/security_trousseau.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.security/security_trousseau.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#security:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#security:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12457.php">Submit feedback</link>
        </links>
      </event>
      <event id="12902">
        <start>15:00</start>
        <duration>00:45</duration>
        <room>M.security</room>
        <slug>security_wishes</slug>
        <title>What I wish I knew about security when I started programming</title>
        <subtitle/>
        <track>Security</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Eighteen years into my career, I decided to pivot and move from infrastructure-related work to the world of application security.
If there’s one thing I’ve learned in the three years of working in application security is that it’s a funny business. Our entire business model is based on pointing out the mistakes of other programmers.&lt;/p&gt;

&lt;p&gt;In this talk, I want to shoot myself in the foot and share some concepts that could help eliminate a lot of those mistakes, and reduce my job to snuffing out the more interesting mistakes.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1828">Allon Mureinik</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/security_wishes/attachments/slides/4888/export/events/attachments/security_wishes/slides/4888/What_I_wish_I_knew_about_security.pdf">Slides from the talk</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/M.security/security_wishes.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.security/security_wishes.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#security:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#security:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12902.php">Submit feedback</link>
        </links>
      </event>
      <event id="12421">
        <start>16:00</start>
        <duration>01:00</duration>
        <room>M.security</room>
        <slug>security_tls</slug>
        <title>Secure Communication with Tls</title>
        <subtitle/>
        <track>Security</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Tls/ssl forms the backbone of secure digital communication. This presentation covers the details about the tls protocol and its use of lower-level cryptographic methods. There is also an extensive section about the creation and use of digital certificates for authentication, with examples from web servers and Postgres.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3126">Bruce Momjian</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://momjian.us/main/writings/tls.pdf">slides</link>
          <link href="https://video.fosdem.org/2022/M.security/security_tls.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.security/security_tls.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#security:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#security:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12421.php">Submit feedback</link>
        </links>
      </event>
      <event id="12450">
        <start>17:00</start>
        <duration>00:45</duration>
        <room>M.security</room>
        <slug>security_sudo</slug>
        <title>Sudo</title>
        <subtitle>Watch and control your blind spots</subtitle>
        <track>Security</track>
        <type>maintrack</type>
        <language/>
        <abstract>&lt;p&gt;Sudo is used by millions to control and log administrator access to systems, but using only the default configuration, there are plenty of blind spots. Using the latest features in sudo lets you watch some functions that previously were blind spots and you can also control access to them. There were several minor and major changes since the 1.9.0 release that I discussed in my previous FOSDEM talks. Here are the four major new features allowing you see your blind spots:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;instead of giving full shell access, you can fine-tune the working directory and chroot settings&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;JSON-formatted logs give you more details on events and are easier to act on&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;relays in sudo_logsrvd make session recording collection more secure and reliable&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;you can log and control sub-commands executed by the command that is run through sudo&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description>&lt;p&gt;Previously, there were quite a few situations where you had to give users full shell access through sudo. Typical examples are when you run a command from a given directory, or run commands in a chroot environment. You can now configure the working directory or the chroot directory and give access only to the command the user really needs.&lt;/p&gt;

&lt;p&gt;Logging is one of the main roles of sudo, to see who did what on the system. Using JSON-formatted log messages gives you even more information about events. Also, structured logs are easier to act on. Setting up alerting for suspicious events is much easier when you have a single parser to configure for any kind of sudo logs. You can collect sudo logs not only by local syslog, but also by using sudo_logsrvd, the same application used to collect session recordings.&lt;/p&gt;

&lt;p&gt;Speaking of session recordings: instead of using a single central server, you can now have multiple levels of sudo_logsrvd relays between the client and the final destination. This allows session collection even if the central server is unavailable, providing you with additional security. It also makes your network configuration simpler.&lt;/p&gt;

&lt;p&gt;Finally, you can log sub-commands executed from the command issued through sudo. You can see commands started from a shell. No more unnoticed shell access from text editors. And, best of all: you can also intercept sub-commands.&lt;/p&gt;</description>
        <persons>
          <person id="828">Peter Czanik</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/security_sudo/attachments/slides/5112/export/events/attachments/security_sudo/slides/5112/czp_fosdem2022_sudo_v2.pdf">Sudo -- watch and control your blind spots</attachment>
        </attachments>
        <links>
          <link href="https://peter.czanik.hu/">sudo/syslog-ng/personal blog</link>
          <link href="https://video.fosdem.org/2022/M.security/security_sudo.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/M.security/security_sudo.mp4">Video recording(mp4)</link>
          <link href="https://peter.czanik.hu/posts/fosdem-2022-sudo/">Answers to Q&amp;A questions I could not answer live</link>
          <link href="https://chat.fosdem.org/#/room/#security:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#security:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12450.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="M.test">
    </room>
    <room name="L.lightningtalks">
      <event id="12890">
        <start>13:00</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_whale</slug>
        <title>Open source to IRL whale card game (python/Golang/WebGL)</title>
        <subtitle>How open source helped me create a physical card game</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;How open source gave life to a physical cards project and raised funds to help saving whales.&lt;/p&gt;

&lt;p&gt;Inkscape helps to create digital designs from paper, machine learning balances the rules of the game, golang and TUI make the game virtual and webgl creates music with whales singing in the ocean.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Drawing entousiast I created a set of whales designs that I liked.&lt;/p&gt;

&lt;p&gt;Talking with a friend I encontered a nice ML project about card games rlcard (link below).&lt;/p&gt;

&lt;p&gt;This helped me to create a ml version to explore rules of the game whale-ml (link below). The created bots showed that the number of card available in the game would change the strategy of players, knowing that I could choose to balance the rules so that new players could win too !&lt;/p&gt;

&lt;p&gt;Helped by the golang community I could create A TUI version : whale-tui (link below).&lt;/p&gt;

&lt;p&gt;Fascinated by the sounds of whales is the sea I decided to create a sampler to use singing whales to create music : whale-sampler (link below).&lt;/p&gt;

&lt;p&gt;Donate for the whales to a nice NGO Miraceti (link below).&lt;/p&gt;</description>
        <persons>
          <person id="5525">pmalhaire</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_whale/attachments/slides/5201/export/events/attachments/lt_whale/slides/5201/whale_cards_pmalhaire.pdf">Whale slides</attachment>
          <attachment type="video" href="https://fosdem.org/2022/schedule/event/lt_whale/attachments/video/5284/export/events/attachments/lt_whale/video/5284/lt_whale.mp4">Video recording(mp4)</attachment>
        </attachments>
        <links>
          <link href="https://github.com/pmalhaire/whale-ml">whale-ml project to explore rules of the game</link>
          <link href="https://github.com/pmalhaire/whale">whale-tui terminal version of the game in golang.</link>
          <link href="https://github.com/pmalhaire/threejs-caustics">whale-sampler sampler to use the sounds of whales to create music</link>
          <link href="https://miraceti.org/">donate for whales to miraceti</link>
          <link href="https://rlcard.org/">RLCard: A Toolkit for Reinforcement Learning in Card Games</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_whale.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_whale.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12890.php">Submit feedback</link>
        </links>
      </event>
      <event id="12863">
        <start>13:20</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_netota</slug>
        <title>NetOTA - repository protocol for embedded systems</title>
        <subtitle>The sweet spot between global stores and latest-image URLs</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;NetOTA is a new repository protocol designed for the IoT ecosystem. It sits between global app-stores and single-URL update links, offering practical features without sacrificing simplicity.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7945">Zygmunt Krynicki</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_netota/attachments/slides/4997/export/events/attachments/lt_netota/slides/4997/lt_netota.pdf"/>
        </attachments>
        <links>
          <link href="https://gitlab.com/zygoon/netota">NetOTA Git repository</link>
          <link href="https://gitlab.com/zygoon/sysota">SysOTA Git repository</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_netota.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_netota.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12863.php">Submit feedback</link>
        </links>
      </event>
      <event id="12387">
        <start>13:40</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_openhps</slug>
        <title>Rapid Prototyping of a Positioning System</title>
        <subtitle>Using the OpenHPS Framework</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;The creation of a positioning system has use cases for indoor, outdoor and even small-scale deployments. These solutions often use a broad range of technologies and algorithms that each have their advantages as well as limitations. Existing open source positioning solutions often offer a complete package for indoor navigation or asset tracking that allows developers to set up a specific application with minimal effort. However, these positioning solutions offer little room for developers to customise them.&lt;/p&gt;

&lt;p&gt;OpenHPS is an open source hybrid positioning framework for creating a positioning system without being bound to a specific technology or a set of algorithms. Developers are free to choose the data they want to use, from where they want to obtain this data, how to process the data and finally how to use the outcome of the positioning system. In this presentation we will present the modularity and ecosystem around the OpenHPS framework, some technical aspects as well as the current state of the project.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;A localisation system often has use cases such as tracking employees or navigating people at a conference. When looking at the problem in a more broader
perspective the use cases often span way beyond the tracking and navigation of people. Whether it is a use case where pawns need to be tracked on chessboard or
a robot needs to navigate itself outside and through multiple buildings, different approaches need to be used.&lt;/p&gt;

&lt;p&gt;Using use case specific software development kits would be an easy solution for developers, but with the constantly changing technologies and algorithms these different platforms cause a fragmentation
of knowledge over multiple programming languages and hardware. Being created in TypeScript, the framework can be deployed on a variety of devices while making use of the large number of packages that are available. A process network design is used to process data from a source to sink. The processing can be done locally, remote and even distributed over multiple processes, web workers or remote machines. Each part of the process network is modular, allowing developers to share algorithms that will be compatible with the same data structure used throughout the framework. In addition, this process network design allows existing algorithms in different programming languages to be accessed as 'part of the processing'.&lt;/p&gt;

&lt;p&gt;With the OpenHPS project we want to create an ecosystem of modules that each focus on a specific aspect in the creation of a positioning system. Modules for different storage techniques, remote communication, computer vision and different sensor sources already exist that will be further discussed in the current state part of the presentation. At its core, the framework is aimed towards developers that have a basic understanding of implementing a positioning system by means of combining parts of the process network. This method of development allows the rapid prototyping of a complete positioning system that can later on be deployed in a production environment.&lt;/p&gt;

&lt;p&gt;Future work in the project will create additional layers of abstraction that allows the development of a system without the required knowledge of the algorithms. However, because the framework is still modular at its core, these abstractions will still allow developers to tweak the system to do the task it is designed to do.&lt;/p&gt;</description>
        <persons>
          <person id="8408">Maxim Van de Wynckel</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_openhps/attachments/slides/5096/export/events/attachments/lt_openhps/slides/5096/openhps_fosdem2022.pdf">Presentation Slides</attachment>
        </attachments>
        <links>
          <link href="https://openhps.org">OpenHPS Website</link>
          <link href="https://github.com/orgs/OpenHPS/repositories">GitHub Repositories</link>
          <link href="https://github.com/OpenHPS/openhps-core">Core Component</link>
          <link href="https://arxiv.org/pdf/2101.05198.pdf">Technical Report</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_openhps.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_openhps.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12387.php">Submit feedback</link>
        </links>
      </event>
      <event id="12728">
        <start>14:00</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_car_whispering</slug>
        <title>Car Whispering: the AI Mechanic</title>
        <subtitle>TinyML Audio Event Detection</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;Embedded Machine learning is a fascinating subject that I am researching as part of my PhD. Several years ago, a buddy (Pearse Gough) and I discussed audio fault detection for common faults, but the technology was less accessible and primarily cloud dependant.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Running TinyML on an ESP32 Microcontroller or Arduino BLE Sense with a microphone, I will demonstrate fault detection through audio event detection on a vehicle. Using a pre-trained model of audio events, running on an MCU with a microphone. I will also share my model and code via Edge Impulse and Git.&lt;/p&gt;</description>
        <persons>
          <person id="8513">Eoin Jordan</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_car_whispering/attachments/slides/5269/export/events/attachments/lt_car_whispering/slides/5269/Fosdem_AI_Mechanic_v3.pdf">Fosdem AI Mechanic v3 slides</attachment>
          <attachment type="audio" href="https://fosdem.org/2022/schedule/event/lt_car_whispering/attachments/audio/5270/export/events/attachments/lt_car_whispering/audio/5270/Fosdem_AI_Mechanic_v3.pdf">Fosdem AI Mechanic v3 slides</attachment>
        </attachments>
        <links>
          <link href="https://drive.google.com/file/d/1sSDsacou-8OYSqMsROFAIdzQaCDxb3vD/view?usp=sharing">AI Mechanic V2 as presented</link>
          <link href="https://github.com/eoinjordan/CarWhispering">Sample Code on Git CarWhispering</link>
          <link href="https://studio.edgeimpulse.com/studio/69300/">Shared Model on Edge Impulse</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_car_whispering.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_car_whispering.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12728.php">Submit feedback</link>
        </links>
      </event>
      <event id="12727">
        <start>14:20</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_oniro</slug>
        <title>Oniro project, the new IoT platform from Eclipse Foundation</title>
        <subtitle>How to transform existing impediments towards a healthier competition in the IoT &amp; Edge space</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;Oniro is an Open Source platform hosted by the Eclipse Foundation that aims to create a healthier competition in the IoT &amp;amp; Edge industries by providing a vendor-neutral environment to foster collaboration under open governance principles and processes.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Oniro Platform for IoT &amp;amp; Edge enables the interconnectivity of devices and machinery from different vendors as well. It allows new business propositions that, unlike today, are not necessarily cloud-dependant, among other business and product innovations.&lt;/p&gt;

&lt;p&gt;The talk will describe what is Oniro, focusing on architectural and technical aspects, its state of the art, some relevant early results and next steps.&lt;/p&gt;

&lt;p&gt;Oniro is currently in Incubation stage and initial contributions to the Eclipse Foundation from the Supporter organizations (code, infrastructure, tools, documentation, etc.) are being migrated to Eclipse. These assets are already published under Open Source licences so distribution and contributions are not just possible but welcome.&lt;/p&gt;</description>
        <persons>
          <person id="2342">toscalix</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_oniro/attachments/slides/5236/export/events/attachments/lt_oniro/slides/5236/oniro_ligrining_talk_fosdem_2022_agustin_toscalix.pdf">Oniro project, the new IoT platform from Eclipse Foundation</attachment>
        </attachments>
        <links>
          <link href="https://oniroproject.org">Project landing page at this stage</link>
          <link href="https://www.eclipse.org/org/workinggroups/oniro-charter.php">Oniro Working Group Charter</link>
          <link href="https://projects.eclipse.org/projects/oniro.oniro-core">Oniro Platform community Driven projects Charter</link>
          <link href="https://oniroproject.org/resource-center/">Assets being transferred to Eclipse Foundation</link>
          <link href="https://booting.oniroproject.org/distro">Source code</link>
          <link href="http://docs.oniroproject.org/">Documentation</link>
          <link href="https://docs.oniroproject.org/en/latest/community-chat-platform.html">Oniro chat</link>
          <link href="https://accounts.eclipse.org/mailing-list/oniro-wg">Oniro working group mailing list</link>
          <link href="https://accounts.eclipse.org/mailing-list/oniro-dev">General technical discussions mailing list</link>
          <link href="http://www.toscalix.com/about">More about the speaker</link>
          <link href="https://gitlab.eclipse.org/eclipse/oniro-core/sysota">First Oniro project contributed: SysOTA</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_oniro.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_oniro.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12727.php">Submit feedback</link>
        </links>
      </event>
      <event id="13512">
        <start>14:40</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_edge_workloads</slug>
        <title>Manage workloads on disconnected far edge</title>
        <subtitle>Edge Computing.</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;Edge devices deployed out in the field pose very different operational, environmental, and business challenges from those of cloud computing. These motivate different engineering trade-offs for Kubernetes at the far edge than for cloud or near-edge scenarios.&lt;/p&gt;

&lt;p&gt;In this lightning talk we will introduce an open source project called microshift and demonstrate how microshift can run and manage workloads on disconnected far edge devices by making frugal use of system resources. We will demonstrate managing edge deployments that can tolerate severe networking constraints, update/rollback securely, safely, speedily, and seamlessly, esp without disrupting workloads, and build on and integrate cleanly with edge-optimized OSes like Fedora IoT. Microshift can be used as a development tool, we provide a MicroShift image that bundles host dependencies like CRI-O and useful tools like the kubectl client, so it can run on most modern Linux distros, on OSX, and on Windows.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7961">parsingh</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/redhat-et/microshift/">https://github.com/redhat-et/microshift/</link>
          <link href="https://microshift.io/">https://microshift.io/</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_edge_workloads.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_edge_workloads.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13512.php">Submit feedback</link>
        </links>
      </event>
      <event id="13038">
        <start>15:00</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_re_lsearch</slug>
        <title>A lightning intro to re-Isearch </title>
        <subtitle>re-Isearch, the 27 year old new kid on the search block</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;Project re-isearch is a novel multimodal search and retrieval engine using mathematical models and algorithms different from the all-too-common inverted index. The design allows it to have, in practice, effectively no limits on the frequency of words, term length, number of fields or complexity of structured data and support even overlap--- where fields or structures cross other's boundaries (common examples are quotes, line/sentences, biblical verse, annotations). Its model enables a completely flexible unit of retrieval and modes of search.
Developed using a highly portable C++ subset to be RAM efficient, the engine provides also bindings to a number of other languages such as Python, Tcl, Java etc.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;“Re-isearch” is a project following in the spirit of the original isearch developed back in the 1990s.  Reborn in 2020 in the middle of the global Covid19 pandemic as Project re-Isearch.&lt;/p&gt;

&lt;p&gt;Like the original, it is not just about textual words but pushes the envelope. re-Isearch is multi-object, multi-modal and with an unharnessed unit of retrieval.&lt;/p&gt;

&lt;p&gt;Mainstream search engines are about finding any information: "a list of all documents containing a specific word or phrase”.
So search engines paradoxically return both too much information (i.e. long lists of links) and too little information (i.e. links to content, not content itself).
The re-Isearch engine is, by contrast, about exploiting document structure, both implicit (XML and other markup) and explicit (visual groupings such as paragraph), to zero in on relevant sections of documents, not just links to documents. This concept of search granularity is a radical departure from other designs. With typical text indexers one has the concept of document or record and that is the unit of index and the unit of retrieval. Instead we can have a dynamic search time unit of retrieval: user specified or heuristically determined. The structure of of documents can be exploited to identify which document elements (such as the appropriate chapter or page) to retrieve. Retrieval granularity may be on the level of sub-structures of a given document or page such as line, paragraph but may also be as part of a larger collection.&lt;/p&gt;

&lt;p&gt;Like the original, it is not just about textual words but the design contains a large number of objects: numerical, range, geospatial etc. It is unique among full-text systems in that it also provides numerous object types with their own methods of search and allows these to be viewed parallel as text--- a date field (of which it will be one of the first to support some key parts of the new ISO-8601:2019 standard date semantics), for instance, can be searched as a date but also a text, searching for the words in the field.&lt;/p&gt;</description>
        <persons>
          <person id="8608">Edward Zimmermann</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/re-Isearch/re-Isearch">Repro</link>
          <link href="https://www.nonmonotonic.net/re-isearch">Linkage</link>
          <link href="https://github.com/re-Isearch/re-Isearch/raw/master/docs/ProjectRe-Isearch-LFOSDEM22-r3_compressed.pdf">PDF of (updated) slide stack</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_re_lsearch.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_re_lsearch.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13038.php">Submit feedback</link>
        </links>
      </event>
      <event id="12481">
        <start>15:20</start>
        <duration>00:15</duration>
        <room>L.lightningtalks</room>
        <slug>lt_luox</slug>
        <title>luox</title>
        <subtitle>An open-source, open-access web platform implementing international standards for the quantification of light</subtitle>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;Light exposure is not only important for seeing the world around us, it is also a key driver for health and well-being. The quantification of light, particularly in parameters relevant for humans, is subject to international consensus documents developed by the International Commission on Illumination (abbreviated as CIE = Commission Internationale de l’Eclairage). This includes quantities for the intensity of light exposure (e.g., illuminance, measured in lux) or indices of how well a light source renders colours (e.g., Rf). The CIE provides various spreadsheet-based tools for calculating these quantities from spectral measurements of radiant energy. Here, we present and discuss the open-source and open-access web platform luox, which was developed with researchers in mind to simplify the process of calculating relevant aspects of light exposures in experiments with human participants. We specifically focus on the challenges of translating written documents and equations into a web based platform using ES6 and ReactJS.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8567">Somang Nam</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lt_luox/attachments/slides/5111/export/events/attachments/lt_luox/slides/5111/FOSDEM_Conference_Lightning_Talk_1.pptx">luox_fosdem_slides</attachment>
        </attachments>
        <links>
          <link href="https://luox.app/">https://luox.app/</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_luox.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_luox.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12481.php">Submit feedback</link>
        </links>
      </event>
      <event id="12351">
        <start>15:40</start>
        <duration>00:20</duration>
        <room>L.lightningtalks</room>
        <slug>lt_aretext</slug>
        <title>aretext: minimalist text editor with vim-compatible key bindings</title>
        <subtitle/>
        <track>Lightning Talks</track>
        <type>lightningtalk</type>
        <language/>
        <abstract>&lt;p&gt;Aretext is a terminal-based text editor with vim-compatible key bindings. Today, aretext supports nearly 100 of the most common vim commands, with more added in each release. Its minimalist design reflects the Unix philosophy: simple software that composes easily with other terminal-based tools -- compilers, formatters, tmux, and more!&lt;/p&gt;

&lt;p&gt;In this lightning talk, we'll see how aretext's carefully-chosen features provide an efficient and powerful editing experience with minimal configuration.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8479">Will Daly</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/aretext/aretext">aretext GitHub repo</link>
          <link href="https://aretext.org">aretext website</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_aretext.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/L.lightningtalks/lt_aretext.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#lightningtalks:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#lightningtalks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12351.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="B.bofs">
    </room>
    <room name="D.ada">
      <event id="13117">
        <start>10:00</start>
        <duration>00:15</duration>
        <room>D.ada</room>
        <slug>ada_introduction_room</slug>
        <title>Introduction to the Ada DevRoom</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Welcome to the Ada Developer Room at FOSDEM 2020, which is organized in cooperation with Ada-Europe and Ada-Belgium.&lt;/p&gt;

&lt;p&gt;This year marks the first edition on which the devroom takes place on an online format. For that reason, this presentation will explain how does it work and how can the public use the systems provided by FOSDEM and interact with the speakers. We will also introduce the Ada-Europe and Ada-Belgium organisations. This small introduction also serves as a test to make sure the systems are working as expected and that any questions that may take place from the public can be answered.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7529">Fernando Oleo Blanco</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_introduction_room/attachments/slides/5063/export/events/attachments/ada_introduction_room/slides/5063/ada_intro_slides.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="http://www.cs.kuleuven.be/~dirk/ada-belgium/events/22/220206-fosdem/00-ada-welcome.pdf">Ada-Europe info-sheet</link>
          <link href="http://www.cs.kuleuven.be/~dirk/ada-belgium/events/22/220206-fosdem-cfpart.pdf">Ada DevRoom information and schedule sheet</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_introduction_room.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_introduction_room.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_introduction_room:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_introduction_room:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13117.php">Submit feedback</link>
        </links>
      </event>
      <event id="12870">
        <start>10:15</start>
        <duration>01:05</duration>
        <room>D.ada</room>
        <slug>ada_introduction_beginning_experienced</slug>
        <title>Introduction to Ada for Beginning and Experienced Programmers</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;An overview of the main features of the Ada language, with special emphasis on those features that make it especially attractive for free software development.&lt;/p&gt;

&lt;p&gt;Ada is a feature-rich language, but what really makes Ada stand-out is that the features are nicely integrated towards serving the goals of software engineering. If you prefer to spend your time on designing elegant solutions rather than on low-level debugging, if you think that software should not fail, if you like to build programs from readily available components that you can trust, you should really consider Ada&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="861">Jean-Pierre Rosen</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_introduction_beginning_experienced/attachments/slides/5048/export/events/attachments/ada_introduction_beginning_experienced/slides/5048/01_ada_introduction.pdf">Introduction to Ada for Beginning and Experienced Programmers</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.ada/ada_introduction_beginning_experienced.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_introduction_beginning_experienced.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_introduction_beginning_experienced:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_introduction_beginning_experienced:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12870.php">Submit feedback</link>
        </links>
      </event>
      <event id="12453">
        <start>11:20</start>
        <duration>00:25</duration>
        <room>D.ada</room>
        <slug>ada_looks_good_game</slug>
        <title>Ada Looks Good, Now Program a Game Without Knowing Anything</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In 2020 I started live streaming the development of a turn-based strategy game. At that time I had little idea about Ada, programming or game development (nothing has changed about that to this day). But by September 2020 it had taken the early form of a Civilization clone. After more than a year of development, it has become almost a real game with its own features. And now I'm going to talk a little bit about some experiences and weirdnesses with game development in Ada&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8516">Stefan Hild</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/HonkiTonk/Civ-Klon">My Civilization like game on GitHub</link>
          <link href="https://github.com/HonkiTonk/Test-Rollenspiel">My test rpg game on GitHub</link>
          <link href="https://www.youtube.com/user/tpHonkiTonk">I stream the development of my game on YouTube.</link>
          <link href="https://www.twitch.tv/tphonkitonk">I also stream the development of my game on Twitch.</link>
          <link href="https://en.wikibooks.org/wiki/Ada_Programming/All_Chapters">Good tutorial to learn Ada.</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_looks_good_game.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_looks_good_game.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_looks_good_game:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_looks_good_game:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12453.php">Submit feedback</link>
        </links>
      </event>
      <event id="12879">
        <start>11:45</start>
        <duration>00:35</duration>
        <room>D.ada</room>
        <slug>ada_numerics_model</slug>
        <title>The Ada Numerics Model</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The requirements for Ada numerics were to provide portable arithmetics without unacceptable performance cost. This talk shows how this was achieved by interval arithmetics without requiring a particular implementation model, like IEEE arithmetics.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="861">Jean-Pierre Rosen</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_numerics_model/attachments/slides/5049/export/events/attachments/ada_numerics_model/slides/5049/Rosen_Ada_Numerics_Model.pdf">The Ada Numerics Model</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.ada/ada_numerics_model.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_numerics_model.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_numerics_model:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_numerics_model:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12879.php">Submit feedback</link>
        </links>
      </event>
      <event id="12378">
        <start>12:20</start>
        <duration>00:30</duration>
        <room>D.ada</room>
        <slug>2022_alire_update</slug>
        <title>2022 Alire Update</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;At FOSDEM 2020 we presented the first version of Alire, the package manager for the Ada Open Source ecosystem. Two years later, the tools and its ecosystem have evolved, in some instances based on the feedback received at FOSDEM. So we want to give you an update on the new features and improvements, including:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pin system: intended to help with the development and use of WIP crates.&lt;/li&gt;
&lt;li&gt;Crate configuration: that enables static code generation before compilation.&lt;/li&gt;
&lt;li&gt;Toolchains: that enable easy installation of [cross-]compiler and builder versions.&lt;/li&gt;
&lt;li&gt;Auto GPR with: for automatic “with”ing of dependencies.&lt;/li&gt;
&lt;li&gt;Etc.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;We will also have a look at the ecosystem of crates available in the Alire community index.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3897">Fabien Chouteau</person>
          <person id="7411">Alejandro R. Mosteo</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://alire.ada.dev">Alire website</link>
          <link href="https://video.fosdem.org/2022/D.ada/2022_alire_update.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/2022_alire_update.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-2022_alire_update:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-2022_alire_update:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12378.php">Submit feedback</link>
        </links>
      </event>
      <event id="13118">
        <start>12:50</start>
        <duration>00:25</duration>
        <room>D.ada</room>
        <slug>ada_sweetada</slug>
        <title>SweetAda</title>
        <subtitle>A Lightweight Development Framework for the Implementation of Ada-based Software Systems</subtitle>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;SweetAda is a lightweight development framework whose purpose is the implementation of Ada-based software systems.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Welcome to SweetAda.&lt;/p&gt;

&lt;p&gt;SweetAda is a lightweight development framework whose purpose is the implementation of Ada-based software systems.&lt;/p&gt;

&lt;p&gt;The code produced by SweetAda is able to run on a wide range of machines, from ARM® embedded boards up to x86-64-class machines, as well as MIPS® machines and Virtex®/Spartan® PowerPC®/MicroBlaze® FPGAs. It could theoretically run even on System/390® IBM® mainframes (indeed it runs on the Hercules emulator). SweetAda is not an operating system, however it includes a set of both low- and high-level primitives and kernel services, like memory management, PCI bus handling, FAT mass-storage handling, which could be used as building blocks in the construction of complex software-controlled devices.&lt;/p&gt;

&lt;p&gt;SweetAda has some distinctive characteristics, like:
- is ROMable
- uses a ZFP run-time
- has no dependencies; neither external libraries nor underlying code are needed&lt;/p&gt;

&lt;p&gt;SweetAda has a complete toolchain (assembler, linker, Ada compiler and debugger), and optionally you could even use a machine emulator, which can execute the final output code inside a virtual target. In order to use SweetAda, a decent POSIX® environment with a Bash shell and GNU Make are required. For a Linux® workstation this is quite standard, while for a Windows® machine you can download and install either MSYS2 (preferred) or Cygwin®. Anyway, SweetAda toolchains for Windows have an integrated Make suited for a Windows CLI. Being completely makefile- and script- driven, SweetAda is completely configurable and has many hooks which allow an easy integration in a GUI environment such as, e.g., Eclipse, KDE Kate or Visual Studio Code. Insight debugger is also available.&lt;/p&gt;

&lt;p&gt;SweetAda comes with high-quality GNU toolchains based on modern official FSF Binutils/GCC/GDB releases, unpatched and compiled with strictly controlled options. The emulators are mainly based on the latest QEMU™ official release, augmented with the IOEMU physical I/O system, which allows software code to interact with a visual environment.&lt;/p&gt;

&lt;p&gt;To make SweetAda generic and, at the same time, reliable, it is regularly tested against an heterogeneous set of machines which are able to successfully execute the system code, e.g.:
- PC-style PIIX3/PIIX4 motherboards (ROM-boot)
- DECstation 5000/133 MIPS R3000 (ROM-boot)
- Memec FX12 Virtex-4 PPC405 (JTAG-boot)
- DigiNS7520 board ARM7TDMI (JTAG-boot)
- Terasic DE10-Lite Nios®II softcore (JTAG-boot)
- MVME1600-011 PPC603 VME board (JTAG-boot)
- Force SPARC®/CPU-3CE VME board (ROM-boot)
- M5235BCC ColdFire development board (ROM-boot)
- SPARCstation™ 5 (ROM-boot)
- Spartan 3E MicroBlaze softcore (JTAG-boot)
- Raspberry Pi™ 3 ARMv8 (microSD-boot)&lt;/p&gt;

&lt;p&gt;The SweetAda software code is compiled by a build machinery which enforces a very high severity level. Usefulness, simplicity and expandability rather than extreme or obscure optimizations are the key features behind the project. Nevertheless, SweetAda grants the possibility of employ appropriate customizations, down to machine code level, to satisfy specific needs.&lt;/p&gt;

&lt;p&gt;SweetAda is in a state of steady growth. BSPs, device drivers, a TLSF memory allocator, TCP/IP basic functionalities, as well as low-level CAN primitives are under heavy development. More target machines and additional feautures/modules such as intrinsic floating point support and expanded SFP runtimes are scheduled in future releases, as well as language tools and system utilities, like ASIS.&lt;/p&gt;

&lt;p&gt;Please note that the platform-specific code included in SweetAda is given as an example. The emphasis of SweetAda is not about operating system design, but rather on exploiting the Ada language everywhere.&lt;/p&gt;

&lt;p&gt;SweetAda is distributed under the terms of the MIT license.&lt;/p&gt;</description>
        <persons>
          <person id="8881">Gabriele Galeotti</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_sweetada/attachments/slides/5044/export/events/attachments/ada_sweetada/slides/5044/SweetAda.odp">SweetAda slides</attachment>
        </attachments>
        <links>
          <link href="https://www.sweetada.org/">Homepage</link>
          <link href="https://github.com/gabriele-galeotti/SweetAda">SweetAda repository</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_sweetada.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_sweetada.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_sweetada:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_sweetada:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13118.php">Submit feedback</link>
        </links>
      </event>
      <event id="12873">
        <start>13:15</start>
        <duration>00:30</duration>
        <room>D.ada</room>
        <slug>ada_2022_json_like</slug>
        <title>Use (and Abuse?) of Ada 2022 Features in Designing a JSON-like Data Structure</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Ada 2022 is around the corner with many goodies in the form of new features and featurettes. Arguably small syntax sugar additions combine for the programmer's comfort, like for example user-defined literals and container aggregates, that allow natural initialization of user-defined containers with the same expressions used for basic arrays since the beginnings of Ada. In this talk, I discuss how these features allow the initialization of a container data type for heterogeneous values (a-la JSON) without the need of crutch functions (like the usual "+"). Such an structure could be used for compiled-in definitions but, more ambitiously, a relatively simple parser for a strict subset of Ada could leverage this data structure for natural-looking (to the Ada programmer) configuration files. Such configuration files could be useful for tools that are strictly Ada-oriented, written by and for Ada programmers.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7411">Alejandro R. Mosteo</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_2022_json_like/attachments/slides/5051/export/events/attachments/ada_2022_json_like/slides/5051/FOSDEM_2022_Yeison_Mosteo.pdf">Slides for the presentation</attachment>
        </attachments>
        <links>
          <link href="https://github.com/mosteo/yeison">GitHub repo of the project</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_2022_json_like.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_2022_json_like.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_2022_json_like:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_2022_json_like:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12873.php">Submit feedback</link>
        </links>
      </event>
      <event id="12887">
        <start>13:45</start>
        <duration>00:25</duration>
        <room>D.ada</room>
        <slug>ada_adawebpack</slug>
        <title>Getting Started with AdaWebPack</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Have been tired from JavaScript in Web development?
Do you want to write both client and server sides in Ada?
Are you looking for modern user interface for you application?
Try to use AdaWebPack and run your Ada code in the web browser!&lt;/p&gt;

&lt;p&gt;The presentation introduces AdaWebPack - Ada compiler to
WebAssembly, customized Run-Time library and Web API
binding. It explains the overall architecture of the pack
and includes a short get started demo.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8778">Max Reznik</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_adawebpack/attachments/slides/4813/export/events/attachments/ada_adawebpack/slides/4813/AdaWebPack_2022.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/godunko/adawebpack">Repository</link>
          <link href="https://blog.adacore.com/use-of-gnat-llvm-to-translate-ada-applications-to-webassembly">Introductory blog post</link>
          <link href="https://blog.adacore.com/android-application-with-ada-and-webassembly">Run Ada on Android blog post</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_adawebpack.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_adawebpack.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_adawebpack:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_adawebpack:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12887.php">Submit feedback</link>
        </links>
      </event>
      <event id="12847">
        <start>14:10</start>
        <duration>00:30</duration>
        <room>D.ada</room>
        <slug>ada_adagui</slug>
        <title>Overview of Ada GUI</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This presentation will introduce the participants to Ada GUI, an Ada-oriented GUI, its philosophy and use, and differences from typical GUI frameworks.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This presentation will introduce the participants to Ada GUI, an Ada-oriented GUI, its philosophy and use, and differences from typical GUI frameworks. Several examples will be presented and some aspects of how the concepts presented are implemented will be discussed.&lt;/p&gt;

&lt;p&gt;Outline:&lt;/p&gt;

&lt;p&gt;  I. Introduction
 II. Traditional GUI Frameworks
III. Ada GUI philosophy and concepts
 IV. Examples
  V. Implementation
 VI. Summary&lt;/p&gt;</description>
        <persons>
          <person id="8645">Jeffrey Carter</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_adagui/attachments/slides/5042/export/events/attachments/ada_adagui/slides/5042/Ada_GUI.odp">Ada-GUI Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/jrcarter/Ada_GUI">Github Ada-GUI repo</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_adagui.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_adagui.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_adagui:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_adagui:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12847.php">Submit feedback</link>
        </links>
      </event>
      <event id="12354">
        <start>14:45</start>
        <duration>01:05</duration>
        <room>D.ada</room>
        <slug>ada_sparknacl</slug>
        <title>SPARKNaCl: A Verified, Fast Re-implementation of TweetNaCl</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;SPARKNaCl is a new, verified and fast reefrence implementation of the NaCl API, based on the TweetNaCl distribution. It has a fully automated, complete and sound proof of type-safety and several key correctness properties. In addition, the code is fast - out-performing TweetNaCl on an Ed25519 Sign operation by a factor of 3 at all optimization levels. This talk will cover how "Proof Driven Optimization" can result in code that is both correct and fast on bare-metal embedded targets.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;TweetNaCl is a compact reference implementation of the NaCl API. It was initially
constructed to show that an entire crypto library could fit into "100 tweets", but has
since been re-used in some critical applications, such as the WireGuard VPN.
There are no comments in the code at all, and all assurance rests on a single brief
academic paper, and the formidable reputation of the authors.&lt;/p&gt;

&lt;p&gt;Can we do better? Can we produce a reference implementation which is amenable to
automatic verification and yet is competitive with TweetNaCl in terms of performance and code
size?&lt;/p&gt;

&lt;p&gt;This talk presents SPARKNaCl - a complete re-implementation of
TweetNaCl in SPARK, which comes with a fully automated proof of type-safety,
memory-safety and a number of key correctness properties.
Having established a solid foundation, we went on to compare the performance and code size of
SPARKNaCl against the original C implementation. Various transformations and optimizations
have been applied that result in SPARKNaCl out-performing TweetNaCl
on a bare-metal 32-bit RISC-V machine for a single Ed25519 "Sign" operation,
while retaining automation and completeness of the proof. Furthermore, SPARKNaCl is freely available under the 3-clause BSD licence.&lt;/p&gt;

&lt;p&gt;This talk will present an overview of the results from both the
proof work and performance analysis of SPARKNaCl.&lt;/p&gt;</description>
        <persons>
          <person id="8481">Roderick Chapman</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_sparknacl/attachments/slides/4848/export/events/attachments/ada_sparknacl/slides/4848/sparknacl_fosdem2022.pdf">SPARKNaCl Talk Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/rod-chapman/SPARKNaCl">SPARKNaCl on GitHub</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_sparknacl.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_sparknacl.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_sparknacl:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_sparknacl:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12354.php">Submit feedback</link>
        </links>
      </event>
      <event id="12891">
        <start>15:50</start>
        <duration>00:35</duration>
        <room>D.ada</room>
        <slug>ada_outsiders_guide</slug>
        <title>The Outsider's Guide to Ada</title>
        <subtitle>Lessons from Learning Ada in 2021</subtitle>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Ada can be difficult to approach due to using a different vernacular to most other languages, and also having many unfamiliar structures and ways of doing things.&lt;/p&gt;

&lt;p&gt;This is an overview of the Ada language by someone who is new to the language, for programmers from other languages, kept as neutral and objective as possible.  See how syntax falls into four categories and the language allows you to opt into features.  Learn how Ada fits together at a high level, with an emphasis on the ways Ada differs, using code samples from open source Ada projects.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;About a year ago, I still thought Ada looked like COBOL.  Since then, I've spent a long time trying to understand the language as a whole, since it's different from many others that I've used.  This talk isn't to sell you on the language, but instead to provide a general overview of how the language works.&lt;/p&gt;

&lt;p&gt;This will complement Jean-Pierre Rosen's "Introduction to Ada for Beginning and Experienced Programmers" talk. If you haven't watched his talk yet, I recommend you do so after this one. If you have watched his talk, this should provide a different perspective to help you understand Ada better.&lt;/p&gt;</description>
        <persons>
          <person id="8757">Paul Jarrett</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_outsiders_guide/attachments/slides/5027/export/events/attachments/ada_outsiders_guide/slides/5027/Outsiders_Guide_To_Ada.pdf">Outsider's Guide to Ada Slides</attachment>
        </attachments>
        <links>
          <link href="https://pyjarrett.github.io/programming-with-ada/">https://pyjarrett.github.io/programming-with-ada/</link>
          <link href="https://learn.adacore.com/">https://learn.adacore.com/</link>
          <link href="https://en.wikibooks.org/wiki/Ada_Programming">https://en.wikibooks.org/wiki/Ada_Programming</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_outsiders_guide.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_outsiders_guide.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_outsiders_guide:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_outsiders_guide:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12891.php">Submit feedback</link>
        </links>
      </event>
      <event id="12401">
        <start>16:25</start>
        <duration>00:40</duration>
        <room>D.ada</room>
        <slug>ada_proving_gnat_light_runtime</slug>
        <title>Proving the Correctness of GNAT Light Runtime Library</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As a programming language, Ada offers a number of features that require runtime support, e.g. exception propagation or concurrency (tasks, protected objects). The GNAT compiler implements this support in its runtime library, which comes in a number of different flavors, with more or less capability. The GNAT light runtime library is a version of the runtime library targeted at embedded platforms and certification, with an Operating System or without it (baremetal). It contains around 180 units focused mostly on I/O, numerics, text manipulation, memory operations.&lt;/p&gt;

&lt;p&gt;Variants of the GNAT light runtime library have been certified for use at the highest levels of criticality in several industrial domains: avionics (DO-178), space (ECSS-E-ST40C), railway (EN 50128), automotive (ISO-26262). Details vary across certification regimes, but the common approach to certification used today is based on written requirements traced to corresponding tests, supported by test coverage analysis. Despite this strict certification process, some bugs were found in the past in the code. An ongoing project at AdaCore is applying formal proof with SPARK to the light runtime units, in order to prove their correctness: that the code is free of runtime errors, and that it satisfies its functional specifications.&lt;/p&gt;

&lt;p&gt;So far, 30 units (out of 180) have been proved, and a few bugs fixed along the way (including a security vulnerability). In this talk, I will describe the approach followed, what was achieved, and what we expect to achieve.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3978">Yannick Moy</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_proving_gnat_light_runtime/attachments/slides/4989/export/events/attachments/ada_proving_gnat_light_runtime/slides/4989/slides.pdf">Proving the Light Runtime</attachment>
        </attachments>
        <links>
          <link href="https://github.com/AdaCore/bb-runtimes">Project to build baremetal GNAT runtimes</link>
          <link href="https://gcc.gnu.org/git.html">GCC (including GNAT) source repository</link>
          <link href="https://www.adacore.com/download">GNAT and SPARK community download</link>
          <link href="https://docs.adacore.com/live/wave/spark2014/html/spark2014_ug/index.html">SPARK User’s Guide</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_proving_gnat_light_runtime.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_proving_gnat_light_runtime.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_proving_gnat_light_runtime:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_proving_gnat_light_runtime:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12401.php">Submit feedback</link>
        </links>
      </event>
      <event id="12867">
        <start>17:05</start>
        <duration>00:25</duration>
        <room>D.ada</room>
        <slug>ada_build_manager</slug>
        <title>Implementing a Build Manager in Ada</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Having used Jenkins with more than 30 projects during 8 years,
it was time to switch to another build manager.
Written in Ada, Porion is a new build manager intended to replace
Jenkins by providing more security, safety and performance.&lt;/p&gt;

&lt;p&gt;The presentation describes the complexity of designing a build
manager.  It highlights some security issues that apply to
a build manager and its implementation.  It explains the overall
architecture that was chosen and the reason of the choice.
Finally it presents the Ada generation tools that have been
used in this project.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5344">Stephane Carrez</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_build_manager/attachments/slides/5068/export/events/attachments/ada_build_manager/slides/5068/porion_ada_presentation.pdf">Implementing a Build Manager in Ada</attachment>
        </attachments>
        <links>
          <link href="https://gitlab.com/stcarrez/porion">Porion sources on Gitlab</link>
          <link href="https://porion.vacs.fr/porion/index.html">Porion live server</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_build_manager.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_build_manager.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_build_manager:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_build_manager:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12867.php">Submit feedback</link>
        </links>
      </event>
      <event id="12896">
        <start>17:30</start>
        <duration>00:25</duration>
        <room>D.ada</room>
        <slug>ada_python_and_julia</slug>
        <title>Exporting Ada Software to Python and Julia</title>
        <subtitle>Applying GPRbuild to make shared object files</subtitle>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The objective is to demonstrate the making of Ada software
available to Python and Julia programmers using GPRbuild.
GPRbuild is the project manager of the GNAT toolchain.
This talk will first present a self-contained small example
to illustrate the making of shared object files from Ada software,
so the software can be used in Python and Julia.
The second part of the talk concerns the application to PHCpack,
a free and open source software package to solve polynomial systems
by homotopy continuation methods, written mainly in Ada, and
available at github at https://github.com/janverschelde/PHCpack.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1899">Jan Verschelde</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ada_python_and_julia/attachments/slides/5108/export/events/attachments/ada_python_and_julia/slides/5108/fosdem22gprbuild.pdf"/>
        </attachments>
        <links>
          <link href="https://github.com/janverschelde/PHCpack">PHCpack repository</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_python_and_julia.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_python_and_julia.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_python_and_julia:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_python_and_julia:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12896.php">Submit feedback</link>
        </links>
      </event>
      <event id="13560">
        <start>17:55</start>
        <duration>00:05</duration>
        <room>D.ada</room>
        <slug>ada_closing</slug>
        <title>Closing of the Ada DevRoom</title>
        <subtitle/>
        <track>Ada</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Thank you for participating in this year's Ada devroom!&lt;/p&gt;

&lt;p&gt;After this short closing event, a room will be open for anybody to join and just talk about anything.&lt;/p&gt;

&lt;p&gt;We hope you enjoyed this years edition. Should you have any feedback on how it went, do not hesitate to submit it to the organisers!&lt;/p&gt;

&lt;p&gt;Cheers,
The Ada FOSDEM team.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="581">Dirk Craeynest</person>
          <person id="7529">Fernando Oleo Blanco</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.ada/ada_closing.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.ada/ada_closing.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#ada-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#ada-ada_closing:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#ada-ada_closing:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13560.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.apache-openoffice">
    </room>
    <room name="D.bsd">
      <event id="13565">
        <start>10:00</start>
        <duration>00:15</duration>
        <room>D.bsd</room>
        <slug>welcome_to_the_bsd_devroom</slug>
        <title>Welcome to the BSD devroom</title>
        <subtitle/>
        <track>BSD</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;speech&lt;/p&gt;</abstract>
        <description>&lt;p&gt;speech&lt;/p&gt;</description>
        <persons>
          <person id="2366">Rodrigo Osorio</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#bsd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#bsd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#bsd-welcome_to_the_bsd_devroom:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#bsd-welcome_to_the_bsd_devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13565.php">Submit feedback</link>
        </links>
      </event>
      <event id="13084">
        <start>10:20</start>
        <duration>00:35</duration>
        <room>D.bsd</room>
        <slug>firmware_updates_for_opnsense_and_pfsense</slug>
        <title>Firmware updates for OPNsense and pfSense with fwupd/LVFS</title>
        <subtitle>Secure firmware for routers with the BSD based operating systems</subtitle>
        <track>BSD</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This presentation will describe the results of the proof of concept work that takes into consideration integration of firmware update framework - fwupd/LVFS for OPNsense and pfSense. It will explain the challenges connected with the implementation of firmware update systems for BSD-based firewall and routing software. It will show basic concepts connected to the fwupd and LVFS.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The security of the whole system is not determined only by the software it runs, but also by the firmware. Firmware is a piece of software inseparable from the hardware. It is responsible for proper hardware initialization as well as its security features. That means that the safety of the machine strongly depends on the mitigations of vulnerabilities provided by firmware (like microcode updates, bug/exploit fixes). For these particular reasons, the firmware should be kept up-to-date.&lt;/p&gt;

&lt;p&gt;Routers are highly popular attack vectors, therefore they must be appropriately secured. pfSense and OPNsense are well known secure firewall and routing software, but they do not have any firmware update methods. Therefore to secure hardware initialization of the routers, in this presentation we will present proof of concept work that takes into consideration integration of firmware update framework - fwupd/LVFS.&lt;/p&gt;

&lt;p&gt;Nowadays, this is one of the most popular firmware update software. fwupd is a daemon that manages firmware updates of each of your hardware components that have some kind of firmware. What is more fwupd is open source, which makes it more trustworthy than proprietary applications delivered by hardware vendors designed for (only) their devices.&lt;/p&gt;</description>
        <persons>
          <person id="7798">Norbert Kamiński</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/fwupd/fwupd">fwupd GitHub repository</link>
          <link href="https://fwupd.org">LVFS web service</link>
          <link href="https://lvfs.readthedocs.io/en/latest/intro.html">fwupd documentation</link>
          <link href="https://opnsense.org/">OPNsense webpage</link>
          <link href="https://www.pfsense.org/">pfSense webpage</link>
          <link href="https://video.fosdem.org/2022/D.bsd/firmware_updates_for_opnsense_and_pfsense.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.bsd/firmware_updates_for_opnsense_and_pfsense.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#bsd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#bsd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#bsd-firmware_updates_for_opnsense_and_pfsense:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#bsd-firmware_updates_for_opnsense_and_pfsense:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13084.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.collab">
    </room>
    <room name="D.cad">
    </room>
    <room name="D.conference">
    </room>
    <room name="D.containers">
      <event id="12837">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.containers</room>
        <slug>container_boot2container</slug>
        <title>Boot2container: An initramfs for reproducible infrastructures</title>
        <subtitle>Who needs host OSes for containers anyway?</subtitle>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Fed up with managing your host OS for your docker environment? Try booting your containers directly from a light-weight initramfs! Flash a USB pendrive with the kernel and initramfs, or netboot it locally or from the internet, configure it from the kernel command line. Bonus: It also supports syncing volumes with S3-compatible cloud storages, making provisioning and back-ups a breeze!&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Containers have been an effective way to share reproducible environments for services, CI pipelines, or even user applications.&lt;/p&gt;

&lt;p&gt;In the high availability world, orchestration can then be used to run multiple instances of the same service. However, if your goal is to run these containers on your local machines, you would first need to provision them with an operating system capable of connecting to the internet, and then downloading, extracting, and running the containers. This operating system would then need to be kept up to date across all your machines which is error-prone and can lead to subtle differences in the run environment which may impact your services.&lt;/p&gt;

&lt;p&gt;In order to lower this maintenance cost and improve the reproducibility of the run environment, it would be best if we could drop this Operating System and directly boot the containers you want to run. With newer versions of podman, it is even painless to run systemd as the entrypoint, so why not create an initramfs that would perform the simple duty of connecting to the internet, and download a "root" container which can be shared between all the machines? If the size could be kept reasonable, both the kernel and initramfs could then be downloaded at boot time via iPXE either locally via PXE or from the internet.&lt;/p&gt;

&lt;p&gt;This is with this line of reasoning that we started working on a new project called boot2container which would receive its configuration via the kernel command line and construct a pipeline of containers. Additionally, we added support for volumes, optionally synced with any S3-compatible cloud storages.&lt;/p&gt;

&lt;p&gt;This project was then used in a bare-metal CI, both for the test machines and the gateways connecting them to the outside world. There, boot2container helps to provide the much-needed reproducibility of the test environment while also making it extremely easy to replicate this infrastructure in multiple locations to maximize availability.&lt;/p&gt;</description>
        <persons>
          <person id="900">Martin Roukala</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_boot2container/attachments/slides/4860/export/events/attachments/container_boot2container/slides/4860/fosdem2022_boot2container.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://gitlab.freedesktop.org/mupuf/boot2container">Boot2container</link>
          <link href="https://mupuf.org/blog/2021/02/10/setting-up-a-ci-system-part-2-generating-and-deploying-your-test-environment/">Story about the creation of boot2container</link>
          <link href="hhttps://mupuf.org/blog/2022/01/10/setting-up-a-ci-system-part-3-provisioning-your-ci-gateway/">How to netboot your machines from a local network or the internet</link>
          <link href="https://mupuf.org/blog/2021/02/08/setting-up-a-ci-system-preparing-your-test-machine/">Setting up a desktop PC for testing:</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_boot2container.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_boot2container.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_boot2container:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_boot2container:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12837.php">Submit feedback</link>
        </links>
      </event>
      <event id="12558">
        <start>10:35</start>
        <duration>00:30</duration>
        <room>D.containers</room>
        <slug>container_debugging</slug>
        <title>Debugging in containers</title>
        <subtitle>Using containers to facilitate debugging by end users</subtitle>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A user reports a bug. Its hardware/kernel/data specific. Is it fixed already? How do we get a debug container to the user to use and get meaningful results back?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;MariaDB did this with quay.io/mariadb-foundation/mariadb-devel as the continuously released, in progress latest version of release series. Preview features are also provided here.&lt;/p&gt;

&lt;p&gt;Also created are quay.io/mariadb-foundation/mariadb-debug containers that include debuginfo packages. The mariadb-debug containers needed to include a range of tools and instructions to make it easy for the users and the developers to bridge their divide for an enhanced bug fixing process.&lt;/p&gt;

&lt;p&gt;Containers can also be used to transport a userspace workload to kernel developers to assist improving/fixing kernel features.&lt;/p&gt;

&lt;p&gt;For users wanting to help with bug reporting, or for other communities wanting to replicate the concept, a number of really simple things can help this process along significantly.&lt;/p&gt;</description>
        <persons>
          <person id="7677">Daniel Black</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://mariadb.org/mariadb-debug-container/"> Tricky Problems? MariaDB debug container</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_debugging.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_debugging.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_debugging:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_debugging:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12558.php">Submit feedback</link>
        </links>
      </event>
      <event id="12618">
        <start>11:10</start>
        <duration>00:20</duration>
        <room>D.containers</room>
        <slug>container_devfile</slug>
        <title>Devfile file format</title>
        <subtitle>Containerized development environment specification</subtitle>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Red Hat, AWS and JetBrains are working on the Devfile specification. A file format to define container-based development environments. Software development acceleration is the ultimate goal.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Infrastructure as code. Network as code. Everything as a code. It looks like everything can be defined as code, versioned and tested automatically. Everything except development environments. The industry hasn’t come up with a file format to define software environments yet.&lt;/p&gt;

&lt;p&gt;But It is in the best interest of developers that the industry starts to settle on an unified environment configuration format. Currently, vendors of remote cloud-based development environment solutions such as GitHub Codespaces and GitPod are building proprietary solutions for hosting and operating development environments using a similar, yet slightly different environment configuration file (devcontainer.json and gitpod.yaml).&lt;/p&gt;

&lt;p&gt;A big challenge for the Devfile is to ensure that it doesn’t become “yet another configuration file”. Instead, we want it to relate and align with any neighboring configuration files used for CI/CD runs or infrastructure provisioning. A Devfile should be able to give developers an inner dev loop that is in sync with the outer dev loop, yet still provide enough flexibility for developers to experiment and have personal tooling preferences.&lt;/p&gt;</description>
        <persons>
          <person id="4321">Mario Loriedo</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://devfile.io">Devfile Project Webpage</link>
          <link href="https://github.com/devfile/api">OpenAPI Specification GitHub repository</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_devfile.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_devfile.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_devfile:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_devfile:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12618.php">Submit feedback</link>
        </links>
      </event>
      <event id="12522">
        <start>11:35</start>
        <duration>00:30</duration>
        <room>D.containers</room>
        <slug>container_distributed_storage</slug>
        <title>Distributed Storage in the Cloud</title>
        <subtitle/>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Cloud brought many innovations - one of them is inexpensive, scalable and sometimes secure Distributed Storage options. In this presentation we will talk about distributed storage Options modern clouds offers ranging from elastic block devices and object storage to sophisticated transactional data stores.  We will discuss the benefits and new architecture options such distibuted storage systems enable as well as the challenges pitfals you need to be aware about.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7756">Peter Zaitsev</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_distributed_storage/attachments/slides/5224/export/events/attachments/container_distributed_storage/slides/5224/FOSDEM2022_Containers_Distributed_Storage_in_The_Cloud"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.containers/container_distributed_storage.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_distributed_storage.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_distributed_storage:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_distributed_storage:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12522.php">Submit feedback</link>
        </links>
      </event>
      <event id="12798">
        <start>12:10</start>
        <duration>00:10</duration>
        <room>D.containers</room>
        <slug>container_k8s_webassembly</slug>
        <title>Extending Kubernetes with WebAssembly</title>
        <subtitle>Making Kubernetes Dynamic Admission Control even more Dynamic Using WebAssembly</subtitle>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;WebAssembly is a portable binary instruction format that was originally created with the browser as the main execution runtime. However, during the last years, WebAssembly is finding its way also outside of the browser because of the many benefits it provides like portability, security and flexibility. We think WebAssembly can be leveraged by Kubernetes in many ways. This short session will focus on how WebAssembly can be used to write Kubernetes admission policies. We will show an open source Kubernetes Dynamic admission controller that uses policies written in WebAssembly to validate and mutate the requests made against the Kubernetes API server.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8742">Rafael Fernández López</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_k8s_webassembly/attachments/slides/4833/export/events/attachments/container_k8s_webassembly/slides/4833/Extending_Kubernetes_with_WebAssembly.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.containers/container_k8s_webassembly.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_k8s_webassembly.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_k8s_webassembly:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_k8s_webassembly:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12798.php">Submit feedback</link>
        </links>
      </event>
      <event id="12474">
        <start>12:25</start>
        <duration>00:30</duration>
        <room>D.containers</room>
        <slug>container_k8s_disappear</slug>
        <title>Freedom Means That Kubernetes Needs To Disappear</title>
        <subtitle/>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We can enable developers to manage everything yet still be in complete control of the aspects they care about.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;We are all moving towards service-based operations and self-sufficient teams. We are all trying to enable developers to be more autonomous. However, it is unrealistic to expect everyone to become an expert on everything, from infrastructure to Kubernetes and everything in between. So, we cannot shift left due to lack of expertise, but we also cannot continue being reactive to the needs of others. The only option left is to simplify services or even remove direct access to infrastructure and Kubernetes.&lt;/p&gt;

&lt;p&gt;We might be able to accomplish those goals through Argo CD or Flux (GitOps), Crossplane (universal control plane), and KubeVela (OAM). By combining those, we can enable developers to manage everything yet still be in complete control of the aspects they care about. GitOps allows us to establish Git as the only point of interaction with the system. Crossplane Composites enable us to simplify developer experience when managing infrastructure. Finally, the Open Application Model (OAM) with KubeVela allows us to define applications instead of Kubernetes resources. If we combine those three types of tools and processes, we can enable operations to define the services used by developers to manage infrastructure and applications. We can do all that without anyone even knowing that there is Kubernetes behind all that.&lt;/p&gt;

&lt;p&gt;For everyone to use Kubernetes, it needs to disappear.&lt;/p&gt;</description>
        <persons>
          <person id="6552">Viktor Farcic</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.containers/container_k8s_disappear.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_k8s_disappear.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_k8s_disappear:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_k8s_disappear:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12474.php">Submit feedback</link>
        </links>
      </event>
      <event id="12465">
        <start>13:00</start>
        <duration>00:30</duration>
        <room>D.containers</room>
        <slug>container_harbor</slug>
        <title>Harbor - The Container Registry</title>
        <subtitle>Harbor 101</subtitle>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;&lt;strong&gt;Harbor - The Container Registry 101&lt;/strong&gt;
Harbor is an open source registry that secures artefacts with policies and role-based access control, ensures images are scanned and free from vulnerabilities, and signs images as trusted.
Harbor, a CNCF Graduated project, delivers compliance, performance, and interoperability to help you consistently and securely manage artefacts across cloud native compute platforms like Kubernetes and Docker.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt; In this talk: &lt;/strong&gt;&lt;br/&gt;
* Quick project overview and status, what added value can have to your infrastructure.
* Demo install and few use-cases
* Community walk through - how community works, what meetings we have, how you can participate, what projects we are working on
* Getting engaged with the project! - getting stared with contributing - code, docs -  10 min&lt;/p&gt;

&lt;h1&gt;&lt;strong&gt;Come and joins us!&lt;/strong&gt;&lt;/h1&gt;</abstract>
        <description>&lt;p&gt;Orlin Vasilev aka Orlin - Community Manager for Contour - past life: +15 years of SysAdmin/Infra Engineer/Cloud Engineer/DevOps/SRE&lt;/p&gt;</description>
        <persons>
          <person id="8461">Orlin Vasilev</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_harbor/attachments/slides/5219/export/events/attachments/container_harbor/slides/5219/OrlinVasilev_Harbor_FOSDEM_2022.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://goharbor.io/">Project home page</link>
          <link href="https://github.com/goharbor/">Project GitHub</link>
          <link href="https://github.com/OrlinVasilev/harbor-fosdem2022">Demo and Slides</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_harbor.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_harbor.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_harbor:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_harbor:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12465.php">Submit feedback</link>
        </links>
      </event>
      <event id="12642">
        <start>13:35</start>
        <duration>00:30</duration>
        <room>D.containers</room>
        <slug>container_flatcar_autoupdate</slug>
        <title>How I learned to stop worrying and love Flatcar’s auto-update</title>
        <subtitle/>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Running an up-to-date and fully patched cluster is a key element in operational security. But keeping your cluster’s OS up to date can be challenging for ops/maintenance, sometimes imposing significant effort just to keep the lights on while at the same time keep the workloads functioning. This talk will briefly introduce the atomic OS update mechanism in Flatcar Container Linux - a minimal Linux distribution optimised for running containers at scale - before elaborating on common patterns we recommend and employ to make updating nodes and clusters a low-risk and automatable endeavor.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This talk will discuss common patterns for patching and updating nodes and clusters, focusing on container operating systems with atomic update capabilities – and Flatcar Container Linux in particular. To some extend these patterns and learnings can also be applied to traditional OSes. Target audience are operators and engineers interested in keeping their clusters’ OS updated while running workloads at scale.&lt;/p&gt;

&lt;p&gt;The advent and widespread use of containers to deploy applications helped a great deal to separate application workloads from the underlying operating system. This separation can be leveraged to make OS updates safe and unintrusive.&lt;/p&gt;

&lt;p&gt;For the purposes of this talk we will focus on Flatcar Container Linux, though settings, patterns, and components can be generalised to also apply to other distributions. After w brief overview of Flatcar’s update process, we’ll discuss the importance of testing (with a brief excursion into canaries) and dive into a number of common cluster scenarios and how to keep one’s OS fresh in the respective environment.&lt;/p&gt;</description>
        <persons>
          <person id="8667">Thilo Fromm</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_flatcar_autoupdate/attachments/slides/5089/export/events/attachments/container_flatcar_autoupdate/slides/5089/FOSDEM_containers_flatcar_autoupdate.pdf"/>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_flatcar_autoupdate/attachments/slides/5090/export/events/attachments/container_flatcar_autoupdate/slides/5090/FOSDEM_containers_flatcar_autoupdate.pptx"/>
        </attachments>
        <links>
          <link href="https://github.com/flatcar-linux/Flatcar">Flatcar Container Linux project on Github</link>
          <link href="https://github.com/kinvolk/nebraska">Nebraska update server project on Github</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_flatcar_autoupdate.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_flatcar_autoupdate.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_flatcar_autoupdate:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_flatcar_autoupdate:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12642.php">Submit feedback</link>
        </links>
      </event>
      <event id="12555">
        <start>14:10</start>
        <duration>00:30</duration>
        <room>D.containers</room>
        <slug>container_k8gb_balancer</slug>
        <title>A cloud native Kubernetes Global Balancer</title>
        <subtitle>Introduction to k8gb</subtitle>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;k8gb is DNS based global service load balancer that can interconnect multiple Kubernetes clusters into one resilient system. Join this talk to learn how it can handle a failover scenario when pods in one cluster go down and second cluster in different location saves the situation.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;k8gb is an open-source Kubernetes operator that is deployed in each participating cluster. It is comprised of CoreDNS, ExternalDNS and the k8gb controller itself. Using ExternalDNS it can create a zone delegation on a common cloud DNS server like Route53 or Infoblox so that the embedded CoreDNS servers work as an authoritative DNS. K8gb controller makes sure these CoreDNS servers are updated accordingly based on the readiness probes of the application.&lt;/p&gt;

&lt;p&gt;In this sense this solution is unique, because it is using Kubernetes native tools with customisable probes and battle tested DNS protocol instead of HTTP pings or other similar approaches where single point of failure might be a problem. In k8gb architecture all k8s clusters are equal and there is no SPoF except the common edge DNS server.&lt;/p&gt;

&lt;p&gt;Recently the project has been accepted to the CNCF sandbox.&lt;/p&gt;</description>
        <persons>
          <person id="5024">Jiří Kremser</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_k8gb_balancer/attachments/slides/5003/export/events/attachments/container_k8gb_balancer/slides/5003/k8gb_fosdem.pdf"/>
        </attachments>
        <links>
          <link href="https://k8gb.io">webpage</link>
          <link href="https://github.com/k8gb-io/k8gb">code</link>
          <link href="https://github.com/k8gb-io/k8gb-manim">high-lvl explanation using Manim</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_k8gb_balancer.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_k8gb_balancer.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_k8gb_balancer:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_k8gb_balancer:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12555.php">Submit feedback</link>
        </links>
      </event>
      <event id="12806">
        <start>14:45</start>
        <duration>00:20</duration>
        <room>D.containers</room>
        <slug>container_ipfs_image</slug>
        <title>P2P Container Image Distribution on IPFS With Containerd and Nerdctl</title>
        <subtitle/>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;nerdctl is a Docker-compatible CLI of containerd, developed as a subproject of containerd. nerdctl recently added support of P2P image distribution on IPFS. This enables to share container images among hosts without hosting or relying on the registry.&lt;/p&gt;

&lt;p&gt;In this session, Kohei, one of the maintainers of nerdctl, will introduce IPFS-based P2P image distribution with containerd and nerdctl. This session will also show the combination of IPFS-based distribution with the existing image distribution techniques, focusing on lazy pulling (eStargz) and image encryption (OCIcrypt). The status of integration work with other tools including Kubernetes will also be shared.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7624">Kohei Tokunaga</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_ipfs_image/attachments/slides/5242/export/events/attachments/container_ipfs_image/slides/5242/slides.pdf">slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/containerd/nerdctl">nerdctl</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_ipfs_image.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_ipfs_image.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_ipfs_image:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_ipfs_image:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12806.php">Submit feedback</link>
        </links>
      </event>
      <event id="12730">
        <start>15:10</start>
        <duration>00:20</duration>
        <room>D.containers</room>
        <slug>container_redpak</slug>
        <title>Redpak: Ultra light weight container for embedded systems</title>
        <subtitle/>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Choosen by the French Government in the Big Cyber Challenge, Redpak is the new embedded container engine to run programs under heavy ressource constraints within microseconds.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;While Linux “name space” provides a good foundation for embedded application isolation, popular containers mostly focus on Linux fragmentation, and none of the Docker, LXC, Snap or Flatpak focus on embedded systems constrains.  Everyone understands that installing a software component on millions of cars, on a submarine or in a train is very different from installing a new application on a desktop or a phone. Embedded containers target managed systems that, on one hand require less composability than phone or desktop, on the other hand require a stronger control on package qualification and resources usage.&lt;/p&gt;

&lt;p&gt;This talk presents how to run containerise programs  under heavy resource constrains. It exposes how containers permit to operate multiple flavors of a given toolkit and finally exposes how containers simplify configuration management, security and hierarchical model, SOTA.&lt;/p&gt;</description>
        <persons>
          <person id="8707">Clément BENIER</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_redpak/attachments/slides/4870/export/events/attachments/container_redpak/slides/4870/fosdem2022_redpak.pdf"/>
        </attachments>
        <links>
          <link href="https://github.com/redpesk-labs/red-pak">red-pak github</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_redpak.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_redpak.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_redpak:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_redpak:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12730.php">Submit feedback</link>
        </links>
      </event>
      <event id="12501">
        <start>15:35</start>
        <duration>00:30</duration>
        <room>D.containers</room>
        <slug>container_k8s_mysql</slug>
        <title>Solutions for running MySQL in Kubernetes</title>
        <subtitle/>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;There are several good MySQL-based Operators in the open-source world, made by Oracle, Presslabs, PlanetScale(Vitess), and Percona. Each of them has its unique architecture inside to guaranty minimal downtime and data loss during failover.
Orchestration of MySQL on Kubernetes is a no way a straightforward process. Let's do deep dive into how Operators are working inside and what solution should be used in each particular case.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4801">Mykola Marzhan</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_k8s_mysql/attachments/slides/5180/export/events/attachments/container_k8s_mysql/slides/5180/MySQL_in_k8s.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.containers/container_k8s_mysql.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_k8s_mysql.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_k8s_mysql:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_k8s_mysql:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12501.php">Submit feedback</link>
        </links>
      </event>
      <event id="12654">
        <start>16:10</start>
        <duration>00:20</duration>
        <room>D.containers</room>
        <slug>container_userlan_tcpip</slug>
        <title>Userland TCP/IP stack for external container connectivity</title>
        <subtitle/>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;CodeReady Containers runs an OpenShift cluster on a laptop or workstation using virtualization.&lt;/p&gt;

&lt;p&gt;Recent developments have made it possible to skip running the OpenShift runtime, and to use it for the sole purpose of running containers with podman when using macOS or Windows. This talk will focus on one specific part of CodeReady Containers, which is its userland TCP/IP stack based on gVisor. We will explore why this was needed, and how the container -&gt; VM -&gt; host connectivity is achieved.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="157">Christophe Fergeau</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_userlan_tcpip/attachments/slides/5094/export/events/attachments/container_userlan_tcpip/slides/5094/CodeReady_Containers_user_mode_networking_using_gVisor.pdf">Slides for the presentation</attachment>
        </attachments>
        <links>
          <link href="https://github.com/code-ready/crc/">CodeReady Containers source repository</link>
          <link href="https://github.com/containers/gvisor-tap-vsock">gvisor-tap-vsock source repository</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_userlan_tcpip.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_userlan_tcpip.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_userlan_tcpip:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_userlan_tcpip:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12654.php">Submit feedback</link>
        </links>
      </event>
      <event id="12485">
        <start>16:35</start>
        <duration>00:10</duration>
        <room>D.containers</room>
        <slug>container_fat_layers</slug>
        <title>What made your container fat?</title>
        <subtitle>Visualizing the size of Container Layers</subtitle>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Keeping the size of of your containers small is more important than ever, especially when distributing container images for others to build upon them. However, once multiple container layers get involved, even the data collection aspect becomes challenging and most existing tools do not primarily focus on visualization.&lt;/p&gt;

&lt;p&gt;We will present a simple tool that we created for this: it is a simple web app that produces sunburst graphs for each layer of a container image and can thereby aid you in finding out where the size bloat comes from. Go and grab it from https://github.com/dcermak/container-layer-sizes and give it a spin yourself!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7167">Dan Čermák</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/dcermak/container-layer-sizes">Source code repository</link>
          <link href="https://dcermak.github.io/container-layer-sizes-presentation/container-layer-analyzer.html">Slides</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_fat_layers.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_fat_layers.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_fat_layers:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_fat_layers:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12485.php">Submit feedback</link>
        </links>
      </event>
      <event id="12855">
        <start>16:50</start>
        <duration>00:20</duration>
        <room>D.containers</room>
        <slug>container_notebook_images</slug>
        <title>An easy and elegant way to manage and build your notebook images</title>
        <subtitle/>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Crane is a minimalist open-source image builder, and aims to provide a dead-simple image building experience for your notebook with a beautiful user interface, which could work with your existing ML pipeline and increase productivity for data scientists.&lt;/p&gt;

&lt;p&gt;Instead of building an end-to-end solution for MLOps, Crane focuses on one piece of the puzzle and provides a friendly solution to a problem we encountered daily. Building a container, dealing with registries, and keeping track of what you’ve already built, are tedious tasks, but they’re things you need to do often. Let’s build a tool for it and save time for data scientists, then they can focus on the real problems to solve.&lt;/p&gt;

&lt;p&gt;When it comes to building a container image, there are lots of gaps to fill. In this talk, we’re going to share why we build Crane, how could it help data scientists, why we choose to build Crane with the community, and what’s the possibilities Crane has to boost productivity for data scientists.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8762">Kuan Lin Huang</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/container_notebook_images/attachments/slides/5186/export/events/attachments/container_notebook_images/slides/5186/FOSDEM2022_Crane.pdf">Crane</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.containers/container_notebook_images.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_notebook_images.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_notebook_images:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_notebook_images:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12855.php">Submit feedback</link>
        </links>
      </event>
      <event id="12797">
        <start>17:15</start>
        <duration>00:30</duration>
        <room>D.containers</room>
        <slug>container_singularity_apptainer</slug>
        <title>From Singularity to Apptainer</title>
        <subtitle/>
        <track>Containers</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Singularity, an open-source containerization platform built for high performance computing use cases and utilized by HPC sites all over the world, was recently moved into the Linux Foundation and renamed to "Apptainer." This presentation will focus on exploring what this change means for Apptainer, including what the current state of the project is, what the priorities for the project in the near-term are, and what the roadmap for the future of the project looks like.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8685">Forrest Burt</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://apptainer.org">Apptainer Project Site</link>
          <link href="https://github.com/apptainer/apptainer">Apptainer GitHub</link>
          <link href="https://docs.google.com/document/d/1mEjRmwOfFXiz4U5uPQ6paa-h3jDgMeGoxM5PPs6r8SI/edit#heading=h.n1yeb4bm2rnm">Apptainer Roadmap</link>
          <link href="https://apptainer.org/news/community-announcement-20211130/">Community Announcement</link>
          <link href="https://apptainer.org/news/article-20211130/">Linux Foundation Press Release</link>
          <link href="https://groups.google.com/a/lbl.gov/g/singularity/c/XlzUf0gRCbE?pli=1">Community Meeting Contact Info</link>
          <link href="https://github.com/apptainer/apptainer/releases/tag/v1.0.0-rc.1">Apptainer Release Candidate</link>
          <link href="mailto:dwd@fnal.gov">Alternative Community Meeting Contact Info</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_singularity_apptainer.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.containers/container_singularity_apptainer.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#containers-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#containers-container_singularity_apptainer:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#containers-container_singularity_apptainer:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12797.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.cicd">
      <event id="12658">
        <start>10:00</start>
        <duration>00:35</duration>
        <room>D.cicd</room>
        <slug>interoperability_in_the_continuous_delivery_space_with_cdevents</slug>
        <title>Interoperability in the Continuous Delivery space with CDEvents</title>
        <subtitle/>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Continuous Delivery is all about getting your software released, and as software/system complexity continues to increase, so does the need to have many different tools, services and even people involved in building, verifying, deploying and monitoring your software. So, how do we make all these tools and services work together to complement each other without creating a massive spider web of explicit interconnectedness? CDEvents!&lt;/p&gt;

&lt;p&gt;In this talk, Andrea Frittoli and Erik Sternerson will present the CDEvents project and protocol from the Continuous Delivery Foundation, describe how events in continuous delivery will help build a strong toolbox of CI/CD tools that can be used for delivery of different types of software projects, and showcase some integrations done by the community.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The number of tools and services supporting CI/CD keeps growing. Each tool has its own strengths and enables its own unique use cases. It is not one-size-fits-all, every project needs to be able to select CI/CD tools according to their own needs.&lt;/p&gt;

&lt;p&gt;What CDEvents aims to do is to give these tools and services an obvious way to become interoperable through a shared event/messaging protocol, so that true end-to-end continuous delivery pipelines and processes with associated monitoring, metrics and insights can be built without the need for “manually gluing things together”.&lt;/p&gt;

&lt;p&gt;Having the freedom to add and replace CI/CD tools and services without needing to worry about compatibility and interoperability issues will help projects keep their delivery processes optimized, and will also enable a new kind of visualization and monitoring tools that can inspect and understand all actors in the CI/CD system without explicitly knowing any of them.&lt;/p&gt;</description>
        <persons>
          <person id="5852">Andrea Frittoli</person>
          <person id="8666">Erik Sternerson</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/interoperability_in_the_continuous_delivery_space_with_cdevents/attachments/slides/5214/export/events/attachments/interoperability_in_the_continuous_delivery_space_with_cdevents/slides/5214/presentation_slides">Interoperability in the Continuous Delivery space with CDEvents</attachment>
        </attachments>
        <links>
          <link href="https://github.com/cdevents">CDEvents GitHub project</link>
          <link href="https://github.com/cdfoundation/sig-events">Events in CI/CD SIG</link>
          <link href="https://video.fosdem.org/2022/D.cicd/interoperability_in_the_continuous_delivery_space_with_cdevents.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/interoperability_in_the_continuous_delivery_space_with_cdevents.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-interoperability_in_the_continuous_delivery_space_with_cdevents:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-interoperability_in_the_continuous_delivery_space_with_cdevents:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12658.php">Submit feedback</link>
        </links>
      </event>
      <event id="12757">
        <start>10:35</start>
        <duration>00:25</duration>
        <room>D.cicd</room>
        <slug>how_to_improve_the_developer_experience_in_heptapod_gitlab</slug>
        <title>How to improve the developer experience in Heptapod/GitLab</title>
        <subtitle>Automate the dull works to focus on development</subtitle>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Logilab has been using heptapod, a GitLab fork with mercurial support, for 2 years now.
We are maintaining the open source software CubicWeb and its components called cubes.
Thus, the code is split in dozens of repositories, depending on one another.
Over the years, it has become hard to maintain code quality and good practices in the whole codebase.&lt;/p&gt;

&lt;p&gt;In this talk, we will present the tools that helped us.
Some of them are mercurial specific, but most could be used in GitLab.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Create Merge Request automatically across repositories based on some rules, such as deprecation warnings.&lt;/li&gt;
&lt;li&gt;Pick a reviewer for Merge requests based on the developers' preferences&lt;/li&gt;
&lt;li&gt;Making sure to commit, tag, update the changelog, publish to PyPi when releasing a new version&lt;/li&gt;
&lt;li&gt;Mutualize GitLab CI configurations with templates&lt;/li&gt;
&lt;li&gt;Host docker images of your project on the forge&lt;/li&gt;
&lt;li&gt;Have up-to-date static websites, documentation or web applications&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Each use case can be solved easily, but combining them is what truly makes developer life easier.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7785">Noé Gaumont</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/how_to_improve_the_developer_experience_in_heptapod_gitlab/attachments/slides/4847/export/events/attachments/how_to_improve_the_developer_experience_in_heptapod_gitlab/slides/4847/How_to_improve_the_developer_experience_in_Heptapod_GitLab.pdf">How to improve the developer experience in Heptapod/GitLab</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.cicd/how_to_improve_the_developer_experience_in_heptapod_gitlab.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/how_to_improve_the_developer_experience_in_heptapod_gitlab.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-how_to_improve_the_developer_experience_in_heptapod_gitlab:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-how_to_improve_the_developer_experience_in_heptapod_gitlab:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12757.php">Submit feedback</link>
        </links>
      </event>
      <event id="13015">
        <start>11:00</start>
        <duration>00:35</duration>
        <room>D.cicd</room>
        <slug>decentralized_devops_with_unfurl</slug>
        <title>Decentralized DevOps with Unfurl</title>
        <subtitle/>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Unfurl is a brand-new open-source command line tool for managing your DevOps infrastructure without depending on any server infrastructure. Unfurl lets you easily track configuration, secrets, software and code dependencies, and deployment history all in git. It integrates with the DevOps tools you are already using -- like Terraform, Ansible, and Helm -- allowing you to encapsulate your DevOps processes into reusable building blocks and describe your cloud infrastructure in simple, application-centric terms.&lt;/p&gt;

&lt;p&gt;The ultimate goal of Unfurl is enable anyone to clone, fork, and deploy live cloud services as easily as cloning and building code from git -- so that we can cooperatively build and run cloud services the same way we build open source software.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8813">Adam Souzis</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/decentralized_devops_with_unfurl/attachments/slides/5199/export/events/attachments/decentralized_devops_with_unfurl/slides/5199/OneCommons_Unfurl_FOSDEM_22_CI_CD_Track.pdf">Slides for Talk</attachment>
        </attachments>
        <links>
          <link href="https://unfurl.run">Unfurl Website</link>
          <link href="https://github.com/onecommons/unfurl">Github repo</link>
          <link href="https://onecommons.org">onecommons.org</link>
          <link href="https://video.fosdem.org/2022/D.cicd/decentralized_devops_with_unfurl.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/decentralized_devops_with_unfurl.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-decentralized_devops_with_unfurl:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-decentralized_devops_with_unfurl:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13015.php">Submit feedback</link>
        </links>
      </event>
      <event id="12504">
        <start>11:35</start>
        <duration>00:25</duration>
        <room>D.cicd</room>
        <slug>git_credentials_binding_for_sh_bat_and_powershell</slug>
        <title>Git Credentials binding for sh, bat, and powershell</title>
        <subtitle>Support Git authentication in Jenkins Pipeline</subtitle>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Jenkins a self-contained, open-source automation server used in automation of all sorts of tasks related to building, testing, and delivering or deploying software. With high extensibility through plugins to provide much of the user-needed functionality. One such plugin is the Git plugin which deals with git operations for Jenkins project but lacked authenticated access to git repositories for Pipeline users. The Git Credentials binding project provides an out of the box solution by supporting git authentication over HTTPS and SSH protocols, so join in the session to learn more about it's implementation and outcome.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8582">Harshit Chopra</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/git_credentials_binding_for_sh_bat_and_powershell/attachments/slides/4886/export/events/attachments/git_credentials_binding_for_sh_bat_and_powershell/slides/4886/Slides">Git Credentials binding for sh, bat, and powershell</attachment>
        </attachments>
        <links>
          <link href="https://www.jenkins.io/blog/2021/07/27/git-credentials-binding-phase-1/">Git username / password credentials binding blog</link>
          <link href="https://www.jenkins.io/blog/2021/08/19/git-credentials-binding-work-report/"> Git Credentials Binding for sh, bat, powershell </link>
          <link href="https://video.fosdem.org/2022/D.cicd/git_credentials_binding_for_sh_bat_and_powershell.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/git_credentials_binding_for_sh_bat_and_powershell.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-git_credentials_binding_for_sh_bat_and_powershell:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-git_credentials_binding_for_sh_bat_and_powershell:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12504.php">Submit feedback</link>
        </links>
      </event>
      <event id="12888">
        <start>12:00</start>
        <duration>00:45</duration>
        <room>D.cicd</room>
        <slug>cicd_using_jenkins_and_nomad</slug>
        <title>CICD using jenkins and Nomad</title>
        <subtitle/>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Things like Infrastructure as Code, Service Discovery and Config Management can and have helped us to quickly build and rebuild infrastructure but we haven't nearly spend enough time to train our self to review, monitor and respond to outages. Does our platform degrade in a graceful way or what does a high cpu load really mean? What can we learn from level 1 outages to be able to run our platforms more reliably.&lt;/p&gt;

&lt;p&gt;This talk will focus on on setting up a CICD pipeline using Jenkins. We start by configuring Jenkins to use our Nomad platform to autoscale job runners. After which we ll look at using the newly released nomad-pack tool to convert, deploy and test and existing nomad job.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6629">Bram Vogelaar</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/cicd_using_jenkins_and_nomad/attachments/slides/5082/export/events/attachments/cicd_using_jenkins_and_nomad/slides/5082/CICDUJNaV_fosdem.pdf">CICD using Jenkins Nomad and Vault</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.cicd/cicd_using_jenkins_and_nomad.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/cicd_using_jenkins_and_nomad.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-cicd_using_jenkins_and_nomad:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-cicd_using_jenkins_and_nomad:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12888.php">Submit feedback</link>
        </links>
      </event>
      <event id="12602">
        <start>12:45</start>
        <duration>00:25</duration>
        <room>D.cicd</room>
        <slug>leveraging_windows_containers_in_your_kubernetes_native_ci_cd_pipelines</slug>
        <title>Leveraging Windows Containers in Your Kubernetes-Native CI/CD Pipelines</title>
        <subtitle/>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;How can you leverage Kubernetes-native CI/CD solutions for your Windows applications? What's needed to create Windows container images in your pipelines? This hands-on talk will get developers and operators started with Windows container support of Argo Workflows and Tekton. You will learn how you can use these solutions to build and test your Windows applications and create Windows container images for them. All work presented will be shared with you.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Windows applications make up a large portion of the services running in many enterprises. Thanks to Windows containers and the work of SIG-Windows, you can manage and orchestrate them on Kubernetes, similar to Linux-based containers.&lt;/p&gt;

&lt;p&gt;If you are developing Windows applications, you may want to use Kubernetes-native CI/CD solutions to build, test and package your application as you do with your Linux applications. To enable such scenarios, Argo Workflows and Tekton recently added support for Windows containers.&lt;/p&gt;</description>
        <persons>
          <person id="8659">Markus Lippert</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://tekton.dev/docs/pipelines/windows/">Tekton Windows Docs</link>
          <link href="https://argoproj.github.io/argo-workflows/windows/">Argo Workflows Windows Docs</link>
          <link href="https://github.com/lippertmarkus/presentations/tree/main/2021-02-FOSDEM-CICD">Slides and session resources</link>
          <link href="https://video.fosdem.org/2022/D.cicd/leveraging_windows_containers_in_your_kubernetes_native_ci_cd_pipelines.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/leveraging_windows_containers_in_your_kubernetes_native_ci_cd_pipelines.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-leveraging_windows_containers_in_your_kubernetes_native_ci_cd_pipelines:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-leveraging_windows_containers_in_your_kubernetes_native_ci_cd_pipelines:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12602.php">Submit feedback</link>
        </links>
      </event>
      <event id="12909">
        <start>13:35</start>
        <duration>00:25</duration>
        <room>D.cicd</room>
        <slug>massive_unikernel_matrices_with_unikraft_concourse_and_more</slug>
        <title>Massive Unikernel Matrices with Unikraft, Concourse and More</title>
        <subtitle>How Unikraft builds many peremutations of unique unikernels</subtitle>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Unikernels are bespoke, single-address space, lightweight Virtual Machines which do one thing and one thing only: fully facilitate the runtime of one application.  Unikernels represent a compile-time specialization strategy and leverage the joining of user and kernel space via a library Operating System in order to achieve this, offering as a result incredible runtime performance whilst increasing application security via isolated hardware virtualization.  As Unikraft, an open-source unikernel SDK and library Opeating System toolkit, has grown over the last few years, the number of available off-the-shelf applications, interpreted languages, libraries, target hypervisors and architectures has grown significantly.  In order to ensure consistency between builds, prevent bugs and performance regression, and to allow for new features, a massive effort has been undertaken to facilitate massive build permutations of specialized unikernels which target and include variations of this growing ecosystem based on new commits and Github Pull Requests.  In this talk, we discuss the journey of this undertaking, highlight and demo several CI/CD solutions in this space with Concourse, and how we are continuing to expand the ecosystem to automatically and intelligently build unique additional performance-oriented permutations from configurations available in the underlying libOS.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8058">Alexander Jung</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.cicd/massive_unikernel_matrices_with_unikraft_concourse_and_more.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/massive_unikernel_matrices_with_unikraft_concourse_and_more.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-massive_unikernel_matrices_with_unikraft_concourse_and_more:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-massive_unikernel_matrices_with_unikraft_concourse_and_more:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12909.php">Submit feedback</link>
        </links>
      </event>
      <event id="12919">
        <start>14:00</start>
        <duration>00:35</duration>
        <room>D.cicd</room>
        <slug>masking_known_issues_across_six_kernel_ci_systems</slug>
        <title>Masking known issues across six kernel CI systems</title>
        <subtitle/>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Aggregating testing results from multiple kernel CI systems is hard, but masking known issues in them is next level. That's what Kernel CI's KCIDB is trying to do. Learn more about the problem, our ideas, and suggest your solutions on this session!&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The Linux Foundation's Kernel CI project has been aggregating CI system results in KCIDB for a while. We have six systems contributing and have started sending result notifications to maintainers.&lt;/p&gt;

&lt;p&gt;However, as a kernel maintainer or developer, the last thing you want is someone else's issue attributed to your patches. With 10K build and 100K test results daily, it's a given that tested revisions are often red with known issues, despite submitting CI systems masking them independently.&lt;/p&gt;

&lt;p&gt;We're trying to come up with a way to aggregate known issues, similarly to test results, and to prevent misattribution of problems to innocent changes for results coming from all CI systems, equally. We want to give maintainers, test authors, and CI system operators the ability to submit their issue descriptions, manually or automatically, so that we can deal with them, and all can save their time and effort.&lt;/p&gt;

&lt;p&gt;The contributed information could be a human-readable description, plus a regular expression to look for in a log or output file, or it could be something more complicated. We could be generating those automatically ourselves, and/or rely on human contributions. We plan to process and apply those ourselves, but perhaps it's a good idea to let submitters do that, and let us know the results instead. We don't know yet.&lt;/p&gt;

&lt;p&gt;Come, see how different kernel CI systems already deal with the problem, how we plan to unify that, and let us know what you think!&lt;/p&gt;</description>
        <persons>
          <person id="3164">Nikolai Kondrashov</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/masking_known_issues_across_six_kernel_ci_systems/attachments/slides/4882/export/events/attachments/masking_known_issues_across_six_kernel_ci_systems/slides/4882/Masking_known_issues_across_six_kernel_CI_systems_FOSDEM_2022.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://kernelci.org/">Linux Foundation's Kernel CI project</link>
          <link href="https://kcidb.kernelci.org/">Aggregated results in KCIDB dashboard</link>
          <link href="https://github.com/kernelci/kcidb/">Main KCIDB source repository</link>
          <link href="https://video.fosdem.org/2022/D.cicd/masking_known_issues_across_six_kernel_ci_systems.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/masking_known_issues_across_six_kernel_ci_systems.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-masking_known_issues_across_six_kernel_ci_systems:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-masking_known_issues_across_six_kernel_ci_systems:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12919.php">Submit feedback</link>
        </links>
      </event>
      <event id="12917">
        <start>14:35</start>
        <duration>00:25</duration>
        <room>D.cicd</room>
        <slug>multi_master_scaling_for_mariadb_buildbot</slug>
        <title>Multi-master scaling for MariaDB Buildbot</title>
        <subtitle/>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Continuous Integration is a very important part in order to ensure a high quality software product. In order to be able to test the MariaDB server across multiple platforms, operating systems and configurations, the MariaDB Foundation has developed a continuous integration framework based on Buildbot. This talk will focus on describing the design decisions in order to be able to scale and test the MariaDB server on over 100 different configurations. We use a multi-master setup and combine Docker latent workers with LibVirt workers and classical Buildbot workers in order to achieve this.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In order to ensure that MariaDB runs smoothly, it needs to be tested on multiple platforms and configurations. In order to ensure this, the MariaDB Foundation has developed a new continuous integration framework, based on Buildbot, that thoroughly tests the server across multiple platforms, operating systems and configurations.&lt;/p&gt;

&lt;p&gt;In order to achieve this, we use a mixture of builders, varying from Docker latent workers, to LibVirt workers but also the classical “always on” buildbot workers. For easier management, we have a separate master process that deals with each type of worker. In this talk, I will talk about our design decisions and some limitations that stand behind these. For example, the testing phase of the MariaDB server generates a very high amount of logs. Since Buildbot can deal with around 10k lines of logs per second, having multiple builds that run at the same time may saturate the master process. In order to deal with this, we use a master locking mechanism together with a multi-master setup.&lt;/p&gt;</description>
        <persons>
          <person id="6945">Vlad Bogolin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.cicd/multi_master_scaling_for_mariadb_buildbot.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/multi_master_scaling_for_mariadb_buildbot.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-multi_master_scaling_for_mariadb_buildbot:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-multi_master_scaling_for_mariadb_buildbot:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12917.php">Submit feedback</link>
        </links>
      </event>
      <event id="12853">
        <start>15:00</start>
        <duration>00:35</duration>
        <room>D.cicd</room>
        <slug>opentelemetry_and_ci_cd</slug>
        <title>OpenTelemetry and CI/CD</title>
        <subtitle/>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;If you would like to know more about measuring your CI/CD for troubleshooting or improving your CI/CD services this talk can be interesting for you.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;CI/CD at large scale, even at small scale, is hard and might affect your team’s mood, frustration with slow builds, or flakiness in your CI/CD.
By using OpenTelemetry for each execution, test, deployment that happens in your CI/CD you can answer questions that are not possible at a glance.
The main aim is to reduce the time that developers spend checking log errors, pointing them to the root cause of errors. Filter real verifications errors related to the CI/CD service and third-party systems. Debugging an error is as easy as going to the trace related where all the context information is accessible.
In this talk, we want to show you what we have done and learned in the last year since we switched to using distributed traces for the CI/CD and implemented some integrations that help us to leverage our CI/CD.&lt;/p&gt;</description>
        <persons>
          <person id="7231">Victor Martinez</person>
          <person id="7232">Ivan Fernandez Calvo</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://opentelemetry.io/docs/">OpenTelemetry Documentation</link>
          <link href="https://www.elastic.co/guide/en/observability/current/ci-cd-observability.html">CI/CD Observability</link>
          <link href="https://docs.ansible.com/ansible/latest/collections/community/general/opentelemetry_callback.html">Ansible - create distributed traces with OpenTelemetry</link>
          <link href="https://pypi.org/project/pytest-otel/">Python - pytest-otel plugin for reporting APM traces of tests executed</link>
          <link href="https://www.devopsworld.com/agenda/speakers/1194690">Who Observes the Watchers? An Observability Journey</link>
          <link href="https://www.devopsworld.com/agenda/speakers/1195140">Observing the CI/CD in Practice</link>
          <link href="https://video.fosdem.org/2022/D.cicd/opentelemetry_and_ci_cd.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/opentelemetry_and_ci_cd.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-opentelemetry_and_ci_cd:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-opentelemetry_and_ci_cd:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12853.php">Submit feedback</link>
        </links>
      </event>
      <event id="12868">
        <start>15:35</start>
        <duration>00:25</duration>
        <room>D.cicd</room>
        <slug>porion_a_new_build_manager</slug>
        <title>Porion a new Build Manager</title>
        <subtitle/>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Yes, another build manager to address security, safety and
performance issues after having used Jenkins with more
than 30 projects during 8 years.&lt;/p&gt;

&lt;p&gt;The talk presents the Porion build manager with its command line
interface but also with its responsive web UI.  I will also
explain some security and safety aspects provided by this
new build manager.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5344">Stephane Carrez</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/porion_a_new_build_manager/attachments/slides/5069/export/events/attachments/porion_a_new_build_manager/slides/5069/porion_cdci_short_presentation.pdf">Porion a new Build Manager</attachment>
        </attachments>
        <links>
          <link href="https://gitlab.com/stcarrez/porion">Porion sources on Gitlab</link>
          <link href="https://porion.vacs.fr/porion/index.html">Porion live server</link>
          <link href="https://video.fosdem.org/2022/D.cicd/porion_a_new_build_manager.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/porion_a_new_build_manager.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-porion_a_new_build_manager:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-porion_a_new_build_manager:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12868.php">Submit feedback</link>
        </links>
      </event>
      <event id="12475">
        <start>16:35</start>
        <duration>00:25</duration>
        <room>D.cicd</room>
        <slug>using_kubernetes_api_to_manage_everything</slug>
        <title>Using Kubernetes API To Manage Everything</title>
        <subtitle>Explore the principles behind the universal control plane implemented through the open-source project Crossplane.</subtitle>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Wouldn't it be beneficial if we had a single API and a universal control plane responsible for managing applications, infrastructure, services, and everything else, no matter whether we are in the public cloud and on-prem?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;If we had to define the most significant benefit Kubernetes provides, that would not be the ability to run containers, fault-tolerance, or immutability. The main benefit is its API. It is well defined, versatile, and extensible. It might be the main culprit behind the "explosion" of the ecosystem created around Kubernetes.&lt;/p&gt;

&lt;p&gt;Can we take Kubernetes API to the next level? Can we use it to manage not only the workloads running inside Kubernetes clusters but for everything else? Wouldn't it be beneficial if we had a single API and a universal control plane responsible for managing applications, infrastructure, services, and everything else, no matter whether we are in the public cloud and on-prem?&lt;/p&gt;

&lt;p&gt;In this hands-on session, we'll explore the principles behind the universal control plane implemented through the open-source project Crossplane.&lt;/p&gt;</description>
        <persons>
          <person id="6552">Viktor Farcic</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.cicd/using_kubernetes_api_to_manage_everything.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/using_kubernetes_api_to_manage_everything.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-using_kubernetes_api_to_manage_everything:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-using_kubernetes_api_to_manage_everything:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12475.php">Submit feedback</link>
        </links>
      </event>
      <event id="12372">
        <start>17:00</start>
        <duration>00:35</duration>
        <room>D.cicd</room>
        <slug>unifying_infrastructure_and_application_delivery_using_keptn</slug>
        <title>Unifying Infrastructure and Application Delivery Using Keptn </title>
        <subtitle/>
        <track>Continuous Integration and Continuous Deployment</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Did you ever promote your application from a staging to production and forgot some important infrastructure changes? Do you wonder how to automate chaos tests into your delivery pipeline to validate your services can deal with failing nodes? When we at Dynatrace started our microservice journey, we had to deal with precisely those and many more questions. Using Keptn as a control plane for application delivery, we can orchestrate all those tasks to avoid any bad deployments while providing a unified deployment experience for our developers. In this talk, I will bring some light into combined infrastructure and application deployment using Keptn to show you how those seemingly separated activities can be unified.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8497">Thomas Schuetz</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://medium.com/dynatrace-engineering/how-to-combine-and-automate-infrastructure-and-application-deployment-in-a-microservice-environment-a16b664bb8b5">A blog post related to the content of this talk</link>
          <link href="https://video.fosdem.org/2022/D.cicd/unifying_infrastructure_and_application_delivery_using_keptn.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.cicd/unifying_infrastructure_and_application_delivery_using_keptn.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#cicd-unifying_infrastructure_and_application_delivery_using_keptn:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#cicd-unifying_infrastructure_and_application_delivery_using_keptn:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12372.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.dart-flutter">
    </room>
    <room name="D.minimalistic">
      <event id="12934">
        <start>10:00</start>
        <duration>00:15</duration>
        <room>D.minimalistic</room>
        <slug>declarativeminimalistic</slug>
        <title>Declarative and Minimalistic Computing</title>
        <subtitle>Entry talk</subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Welcome to the Declarative and Minimalistic Computing Devroom.&lt;/p&gt;

&lt;p&gt;In this year's virtual conference we will honour the late Professor John McCarthy as the founder of AI and the inventor of LISP. McCarthy with his work pioneered artificial intelligence, developed the Lisp programming language family and kickstarted our modern computing world. Lisp is one of the two oldest computer languages in use today.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3311">Manolis Ragkousis</person>
          <person id="8839">Oliver Propst</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.minimalistic/declarativeminimalistic.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/declarativeminimalistic.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-declarativeminimalistic:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-declarativeminimalistic:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12934.php">Submit feedback</link>
        </links>
      </event>
      <event id="12717">
        <start>10:15</start>
        <duration>00:30</duration>
        <room>D.minimalistic</room>
        <slug>rakumetaprogramming</slug>
        <title>The manifold joys of metaprogramming</title>
        <subtitle>In Raku and elsewhere... </subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Metaprogramming is a technique that allows the creation of data and control structures during runtime. This gives adaptiveness and expressiveness to languages, allowing the creation of data structures with complex behavior, and adapted to the environment or to the data used. In this talk we will talk about general metaprogramming techniques, with examples in Raku and other modern languages.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1263">Juan Julián Merelo</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.minimalistic/rakumetaprogramming.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/rakumetaprogramming.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-rakumetaprogramming:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-rakumetaprogramming:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12717.php">Submit feedback</link>
        </links>
      </event>
      <event id="12363">
        <start>10:45</start>
        <duration>00:30</duration>
        <room>D.minimalistic</room>
        <slug>riscvadventures</slug>
        <title>A year of RISC-V adventures: embracing chaos in your software journey</title>
        <subtitle>How I started from zero and ended up porting a JIT compilation library and assembling files by hand</subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this presentation I share my 1-year journey with RISC-V and how I started from nearly zero and I ended up porting Guile's JIT library to RISC-V and starting the RISC-V port of Stage0.
This journey is full of uncertainties and chaos but that's what finally made this happen. During this talk we'll discuss how embracing chaos can lead to great change and how we can become the source of positive chaos in people around us.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;&lt;em&gt;This talk is not fully technical but many technical aspects are discussed as they are fundamental in the journey: instruction sets, assembly, debuggers, hexadecimal... and all sorts of low level wizardry will be mentioned and explained. I'll try to make my best to make all of it accessible to anyone with no previous knowledge about them, though.&lt;/em&gt;&lt;/p&gt;</description>
        <persons>
          <person id="8473">Ekaitz Zarraga</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/riscvadventures/attachments/slides/4815/export/events/attachments/riscvadventures/slides/4815/Slides.pdf">A year of RISC-V</attachment>
        </attachments>
        <links>
          <link href="https://ekaitz.elenq.tech/">My blog</link>
          <link href="http://riscvbook.com/">A RISC-V book I recommend</link>
          <link href="https://github.com/oriansj/stage0">Stage0 project</link>
          <link href="https://gitlab.com/wingo/lightening/-/merge_requests/14/commits">Guile's JIT library migration</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/riscvadventures.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/riscvadventures.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-riscvadventures:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-riscvadventures:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12363.php">Submit feedback</link>
        </links>
      </event>
      <event id="12741">
        <start>11:15</start>
        <duration>00:30</duration>
        <room>D.minimalistic</room>
        <slug>designdsl</slug>
        <title>How to design powerful DSLs for users</title>
        <subtitle>Decisions, decisions, decisions...</subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;How can we use DSLs in our applications as a replacement for databases? CSVs? configuration files?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk I will explain how we designed and developed several DSLs for usage in the Nyxt browser. I will also explain how we designed our DSLs and what our constraints were. What were we trying to achieve with our DSLs? How can you too leverage DSLs in your applications to empower your users?&lt;/p&gt;</description>
        <persons>
          <person id="7638">John Mercouris</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.minimalistic/designdsl.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/designdsl.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-designdsl:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-designdsl:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12741.php">Submit feedback</link>
        </links>
      </event>
      <event id="12429">
        <start>11:45</start>
        <duration>00:30</duration>
        <room>D.minimalistic</room>
        <slug>guixdeclare</slug>
        <title>Declare All Your Needs</title>
        <subtitle>Managing computing environment declaratively using GNU Guix</subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Functional programming becomes more popular and widespread, it allows to make simplier, and more robust software, which is easier to maintain. Similar patterns and approaches are applicable for deploying or distributing software, managing infrastructures or even personal computers.&lt;/p&gt;

&lt;p&gt;We will discuss how to treat your computing environment as a simple software project written in functional language and how to manage operating system, services, configurations, user software, dotfiles in a declarative and reproducible fashion.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;We will be using a quite minimalistic language called Guile Scheme (Lisp dialect), GNU Guix package manager built on top of that language and Guix System, Guix Home and rde projects, which will help to bring all things together and create a fully-working operating system with all needed software available and configured in a few minutes.&lt;/p&gt;</description>
        <persons>
          <person id="8519">Andrew Tropin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.minimalistic/guixdeclare.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/guixdeclare.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-guixdeclare:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-guixdeclare:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12429.php">Submit feedback</link>
        </links>
      </event>
      <event id="12343">
        <start>12:15</start>
        <duration>00:25</duration>
        <room>D.minimalistic</room>
        <slug>gnuguixci</slug>
        <title>GNU Guix behind the scene</title>
        <subtitle>Continuous integration for the GNU Guix project</subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;GNU Guix is a transactional package manager and an advanced distribution based
on a minimalistic language: GNU Guile.&lt;/p&gt;

&lt;p&gt;While users can choose to build everything from sources, the project is providing binary
substitutes. Building and distributing those substitutes is a real challenge, involving
a 20 GiB database and more than thirty machines.&lt;/p&gt;

&lt;p&gt;In this talk I will present the architecture of the continuous integration
system, how it is maintained, the current limitations as well as the possible
improvements.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The GNU Guix build farm is composed of more than thirty machines. Most of them
are hosted in the same datacenter in Berlin, while others, hosted by
individuals are made available through a Wireguard tunnel. Those machines are
managed using the GNU Guix deploy mecanism, which will be presented.&lt;/p&gt;

&lt;p&gt;The software managing the evaluation and the distributed builds on those
machines, Cuirass is also written in GNU Guile. This tool that is obviously
relying on GNU Guix will be introduced.&lt;/p&gt;</description>
        <persons>
          <person id="6927">Mathieu Othacehe</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/gnuguixci/attachments/slides/4822/export/events/attachments/gnuguixci/slides/4822/talk_minimalistic_2022.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.minimalistic/gnuguixci.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/gnuguixci.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-gnuguixci:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-gnuguixci:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12343.php">Submit feedback</link>
        </links>
      </event>
      <event id="12364">
        <start>12:40</start>
        <duration>00:25</duration>
        <room>D.minimalistic</room>
        <slug>langdesert</slug>
        <title>Designing a programming language for the desert</title>
        <subtitle/>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;You need a lot of hubris to design your own programming language.  As a result, new languages are often engineered (or "over-engineered") for that glorious future where millions of programmers spend their lives working with the language, and a small army is maintaining the compiler and related tools.  But how would you design a language that assumes this bountiful future will never arrive?  A language that, even in the best of circumstances, will always be obscure and secondary?  Futhark is a programming language designed for a very specific domain: high-level, deterministic, data-parallel number crunching.  It explicitly disavows general-purpose use, and it is absolutely not possible to write full applications in it.  Thus, even if Futhark somehow managed to become the largest conceivable success and completely dominate its domain, that would not translate into very many programmers.  And even then, it would at best be a secondary or third language for most of its users.&lt;/p&gt;

&lt;p&gt;In this talk I will talk about how such a perspective has affected the design of the Futhark language and its tools.  To a first approximation, this is just the "principle of least surprise" applied to every part of the language and ecosystem.  As a niche language, Futhark's novelty budget is quite limited, and its users will not have the inclination to learn about syntactical subtleties, elaborate package managers or build systems.  At the same time, it's trying to innovate in a challenging domain, so some things definitely will have to be novel.  Balancing these concerns has been interesting, and my experiences are perhaps even useful for designers of languages, tools, or systems in similar situations.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8492">Troels Henriksen</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/langdesert/attachments/slides/5050/export/events/attachments/langdesert/slides/5050/presentation.pdf">The slides</attachment>
        </attachments>
        <links>
          <link href="https://futhark-lang.org">Futhark website</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/langdesert.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/langdesert.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-langdesert:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-langdesert:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12364.php">Submit feedback</link>
        </links>
      </event>
      <event id="12525">
        <start>13:05</start>
        <duration>00:30</duration>
        <room>D.minimalistic</room>
        <slug>tinyscheme</slug>
        <title>From tinyscheme to tr7</title>
        <subtitle>how to loose time for glory</subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I'm going to present a scheme R7RS compliant interpreter only named "TR7", a far successor of tinyscheme, meant to be included in other programs for scripting.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;As I was searching a tiny scripting language for some project, I found tinyscheme. It is really venerable but old.&lt;/p&gt;

&lt;p&gt;So I searched for a modern replacement in the existing one, browsing the very long list at http://community.schemewiki.org/?scheme-faq-standards#implementations.&lt;/p&gt;

&lt;p&gt;And you what? I have not found one matching my criteria: r7rs compatible, only C, light, easy to add in C programs.&lt;/p&gt;

&lt;p&gt;So I started to modify tiny-scheme to fit my requirement.&lt;/p&gt;

&lt;p&gt;Before work, at noon rest, late in the evening, ... A long effort still not achieved.&lt;/p&gt;

&lt;p&gt;I'd like to get a short time slot to present it.&lt;/p&gt;</description>
        <persons>
          <person id="1784">José Bollo</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/tinyscheme/attachments/slides/4865/export/events/attachments/tinyscheme/slides/4865/tr7_slides">from tinyscheme to tr7</attachment>
        </attachments>
        <links>
          <link href="https://gitlab.com/jobol/tr7">sources</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/tinyscheme.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/tinyscheme.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-tinyscheme:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-tinyscheme:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12525.php">Submit feedback</link>
        </links>
      </event>
      <event id="12607">
        <start>13:35</start>
        <duration>00:30</duration>
        <room>D.minimalistic</room>
        <slug>fuzionlang</slug>
        <title>Fuzion Language Update</title>
        <subtitle>The marathon run 🏃🏃‍♀️ 🏃‍♂️ from a language prototype to a full implementation and toolchain.</subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Fuzion is a modern general purpose programming language that unifies concepts
found in structured, functional and object-oriented programming languages into
the concept of a Fuzion feature.  It combines a powerful syntax and safety
features based on the design-by-contract principle with a simple intermediate
representation that enables powerful optimizing compilers and static analysis
tools to verify correctness aspects.&lt;/p&gt;

&lt;p&gt;This talk will present the advances in the Fuzion languages since its first
public announcement at FOSDEM 2021.  This includes a simplified and cleaned-up
syntax, improved type inference, its safety features, foreign language
interface to Java and an overview of the existing and planned toolchain.&lt;/p&gt;

&lt;p&gt;Fuzion is not only about the language itself, but just as well about the
intermediate representation that is the basis for static analysis, optimization
and back-ends. The talk will give an overview of the format of intermediate code.&lt;/p&gt;</abstract>
        <description>&lt;h1&gt;Introduction&lt;/h1&gt;

&lt;p&gt;Fuzion is a modern general purpose programming language that unifies concepts
found in structured, functional and object-oriented programming languages into
the concept of a Fuzion feature.  It combines a powerful syntax and safety
features based on the design-by-contract principle with a simple intermediate
representation that enables powerful optimizing compilers and static analysis
tools to verify correctness aspects.&lt;/p&gt;

&lt;p&gt;Fuzion was influenced by many other languages including Java, Python, Eiffel,
Rust, Go, Lua, Kotlin, C#, F#, Nim, Julia, Clojure, C/C++, and many more.  The
goal of Fuzion is to define a language that has the expressive power present in
these languages and allow high-performance implementations and powerful analysis
tools.  Furthermore, Fuzion addresses requirements for safety-critical
applications by adding support for contracts that enable formal specification and
enable detailed control over run-time checks.&lt;/p&gt;

&lt;p&gt;Many current programming language are getting more and more overloaded with new
concepts and syntax to solve particular development or performance issues.
Languages like Java/C# provide classes, interfaces, methods, packages, anonymous
inner classes, local variables, fields, closures, etc.  And these languages are
currently further extended by the introductions of records/structs, value types,
etc.  The possibility of nesting these different concepts results in
complexity for the developer and the tools (compilers, VMs) that process and
execute the code.&lt;/p&gt;

&lt;p&gt;For example, the possibility to access a local variable as part of the closure
of a lambda expression may result in the compiler allocating heap space to hold
the contents of that local variable.  Hence, the developer has lost control over
the allocation decisions made by the compiler.&lt;/p&gt;

&lt;p&gt;In Fuzion, the concepts of classes, interfaces, methods, packages, fields and
local variables are unified in the concept of a Fuzion feature. The decision
where to allocate the memory associated with a feature (on the heap, the stack
or in a register) is left to the compiler just as well as the decision if
dynamic type information is needed.  The developer is left with the single
concept of a feature, the language implementation takes care of all the rest.&lt;/p&gt;

&lt;h1&gt;Fuzion Feature Declarations&lt;/h1&gt;

&lt;p&gt;A Fuzion feature has a name, similar to the name of a class or a function.
The main operation that can be performed on a feature is a feature call.  The
constituents of a feature declaration are as follows:&lt;/p&gt;

&lt;h2&gt;Formal Arguments&lt;/h2&gt;

&lt;p&gt;Features may have a list of formal arguments, which are themselves features
implemented as fields.  On a call to a feature with formal arguments, actual
arguments have to be provided to the call, unless the list of formal arguments
is empty.&lt;/p&gt;

&lt;h2&gt;Feature Result&lt;/h2&gt;

&lt;p&gt;The result of a feature call is an instance of the feature.  Alternatively, a
feature may declare a different result type, then it must return a value of that
type on a call.&lt;/p&gt;

&lt;h2&gt;Closures&lt;/h2&gt;

&lt;p&gt;Features are nested, i.e., every feature is declared within the context of an
outer feature.  The only exception is the universe, which is the outermost
feature in Fuzion.  A feature can access features declared in its
outer feature or, recursively, any outer feature of these outer features.  This
means, a feature declaration also defines a closure of the feature and its
context.&lt;/p&gt;

&lt;p&gt;When calling a feature &lt;em&gt;f1&lt;/em&gt; declared as an inner feature of &lt;em&gt;f2&lt;/em&gt;, the call must
include a target value which is the result of a call to &lt;em&gt;f2&lt;/em&gt;, e.g., &lt;em&gt;f2.f1&lt;/em&gt;.&lt;/p&gt;

&lt;h2&gt;Generics&lt;/h2&gt;

&lt;p&gt;Features may have generic type parameters. E.g. a feature declaration may leave
the actual type used within that feature open and to be defined by the user of
the feature.&lt;/p&gt;

&lt;p&gt;The list of generic type parameters may be open, i.e., the number of actual
generic type parameters is not fixed at feature declaration.  This turns out to
be useful in the declaration of choice types and functions as explained below.&lt;/p&gt;

&lt;h2&gt;Inheritance&lt;/h2&gt;

&lt;p&gt;Fuzion features can inherit from one or several other features.  When inheriting
from an existing features, all inner features of the parent automatically become
inner features of the heir feature.  It is possible to redefine inherited
features.  In particular, when inheriting from a feature with abstract inner
features, one can implement the inherited abstract features.&lt;/p&gt;

&lt;p&gt;A redefinition of an inherited feature may implement an inherited feature as a
routine or as a field.  An inherited feature that is implemented as a field,
however, cannot be redefined as something else since fields might be mutable.&lt;/p&gt;

&lt;p&gt;Inheritance may result in conflicts. An example would be two features with the
same name that are inherited from two different parents.  In this case, the heir
must resolve the conflict either by redefining the inherited features and
providing a new implementation or by renaming the inherited features resulting
in two inner features in the heir feature.&lt;/p&gt;

&lt;p&gt;Inheritance and redefinition in Fuzion does not require dynamic binding.  By
default, the types defined by features are value types and no run-time overhead
for dynamic binding is imposed by inheritance.&lt;/p&gt;

&lt;h2&gt;A Contract&lt;/h2&gt;

&lt;p&gt;A feature may declare a contract that specifies what the features does and under
which conditions the feature may be called.&lt;/p&gt;

&lt;h2&gt;An implementation&lt;/h2&gt;

&lt;p&gt;Features must have one of the following implementations&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;a routine is a feature implementation with code that is executed on a call&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;a field is a memory slot that stores a value and whose contents are returned on a call&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;an abstract feature has no implementation and cannot be called directly, but can be implemented by heir features&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;an intrinsic feature is a low-level feature implemented by the compiler or
run-time system, e.g., the infix + operator to add two 32-bit integer values
may be an intrinsic operation.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;A feature implemented as a routine can contain inner feature declarations.&lt;/p&gt;

&lt;h1&gt;Feature examples&lt;/h1&gt;

&lt;p&gt;Here is an example that declares a feature &lt;em&gt;point&lt;/em&gt; that functions similar to a
struct or record in other languages:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;point(x, y i32) is # empty
p1 := point 3 4
say "p1.x is {p1.x}"    # will print "p1.x is 3"
say "p1.y is {p1.y}"    # will print "p1.y is 4"
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The next example shows a feature &lt;em&gt;base&lt;/em&gt; that provides an inner feature &lt;em&gt;plus&lt;/em&gt;
that adds its argument to the value passed to the enclosing base:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;base(v i32) is
  plus(w i32) =&amp;gt; v + w

b1 := base 30
b2 := base 100
say (b1.plus 23)    # will print "53"
say (b2.plus 23)    # will print "123"
&lt;/code&gt;&lt;/pre&gt;

&lt;h1&gt;Fuzion Syntax Evolution&lt;/h1&gt;

&lt;p&gt;Fuzion provides two main syntax alternatives, a classic once using semicolons,
braces and parentheses and a modern one using white-space and indentation.  Both
are equivalent, there should be tools between these two representations of
source code.  The following explains the main ideas how white-space is used
instead of special symbols&lt;/p&gt;

&lt;h2&gt;Separating Statements&lt;/h2&gt;

&lt;h3&gt;Flat line feeds instead of semicolons&lt;/h3&gt;

&lt;p&gt;The classic way to separate statements is by using a semicolon as in&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;stmt1; stmt2; stmt3
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;or&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;stmt1;
stmt2;
stmt3;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The Fuzion grammar knows a symbol called 'flat line feed', which is a line feed
with the next line starting with white space up to the previous line's
indentation level. A 'flat line feed' is considered equivalent to a semicolon,
so the sequence of three statements above can be written without semicolons as
follows:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;stmt1
stmt2
stmt3
&lt;/code&gt;&lt;/pre&gt;

&lt;h3&gt;Indenting line feeds to form blocks&lt;/h3&gt;

&lt;p&gt;Code blocks in Fuzion can be build using braces similar to many other languages&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;if cond { stmnt1 } else { stmnt2 }

if cond {
  stmnt1
} else {
  stmnt2
}

if cond
  {
    stmnt1
  }
else
  {
    stmnt2
  }
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;An 'indenting line feed' in Fuzion is a line feed with the next line starting at
a higher indentation level.  The parser treats an 'indenting line feed' like a
left brace '{'. Correspondingly, a linefeed that reduces the indentation level
back to the original level is treated like a right brace '}'. The example above
is hence equivalent to&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;if cond
  stmnt1
else
  stmnt2
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Finally, an optional keyword 'then' may as well be used to separate an
expression like the condition in an 'if' from a following expression without the
need of braces:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;if cond then stmnt1 else stmnt2
&lt;/code&gt;&lt;/pre&gt;

&lt;h2&gt;Separating calls, arguments and operator expressions&lt;/h2&gt;

&lt;h3&gt;calls without parentheses&lt;/h3&gt;

&lt;p&gt;Fuzion calls do not need parentheses or commas to separate the called feature
and its arguments, i.e., a call&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f(a, b, c)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;can be written as&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f a b c
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Parameters are then separated by white space. Line breaks, either flat or
indenting as explained above, end the argument list.&lt;/p&gt;

&lt;p&gt;Parentheses may be needed for nesting calls with arguments, e.g., the code&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f (g x y) (h z)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;is equivalent to&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f(g(x, y), h(z))
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;If placed in parentheses, operator expressions may extend over several lines
using an indenting line feed followed by additional flat line feeds, e.g.,&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f (1 + 2 + 3 + 4 +
   5 + 6 + 7 + 8 +
   9 + 10 + 11 + 12)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Tuples of values such as '(a, b)' syntactically look like argument lists.  A list
of expressions enclosed in parentheses is treated as an argument list only if it
immediately follows the name of a called feature. The code&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f(a, b)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;hence calls 'f' with two arguments 'a' and 'b'. In case there is white space
after the name of the called feature as in&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f (a, b)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;the expression in parentheses is passed as an argument, so, in this case 'f'
will be called with a single argument: the tuple '(a, b)'.&lt;/p&gt;

&lt;h3&gt;Array indexing vs. array creation&lt;/h3&gt;

&lt;p&gt;The square brackets '[' and ’]’ are used in Fuzion for two purposes: A
pre-initialized array of fixed size can be created using an expression like
'[x, y, z]', while an array can be indexed using 'a[i]'.  Again, white space can
be used to distinguish these two cases:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;a[i]
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;read an element from an array while&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f [x, y, z]
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;create array with elements x, y and z and passes it as an argument in a call to
'f'.&lt;/p&gt;

&lt;h3&gt;Operator expressions&lt;/h3&gt;

&lt;p&gt;Operators are parsed as prefix- or postfix operators if the are not separated by
white space from their target operand, but they are separated by white space on
the other side.  This means that the call&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f -x
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;is equivalent to&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f (-x)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;while&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f - x
f-x
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;both subtract 'x' from 'f'. Furthermore,&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f- x
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;is parsed as&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;(f-) x
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;i.e., it calls 'postfix -' on 'f' and, assuming the result is a function, calls
this result with one argument 'x'.&lt;/p&gt;

&lt;p&gt;The precedence of operators that are not separated by white space is stronger
than that of a call, so&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f a-b
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;is equivalent to&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f (a-b)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;while the precedence of calls is higher than that of operators separated by
white space, i.e,&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f a -b
f a - b
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;are equivalent to&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;f (a) (-b)
(f a) - b
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;respectively.&lt;/p&gt;

&lt;h2&gt;White space vs. explicit tokens&lt;/h2&gt;

&lt;p&gt;Attaching semantics to white space might appear dangerous and error-prone to
those not used to it.  However, more and more languages (Python, Scala-3, Nim,
Raku, ...) make use of white-space and the experience is generally very positive,
the code is cleaner, easier to read an even easier to maintain.  Compiler errors
complaining about unbalanced parentheses or braces are gone and mismatch between
indentation and semantics may no longer occur.&lt;/p&gt;

&lt;p&gt;Furthermore, even languages like Java allow code to have hugely different
semantics if just a single white space is added, e.g., the Java code&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;if (cc) x(); elsey();
if (cc) x(); else y();
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;changes completely by insertion of a single space character.&lt;/p&gt;

&lt;h1&gt;Fuzion Type Inference&lt;/h1&gt;

&lt;p&gt;Fuzion is statically typed, every expression, every field, every routine result
has a static type known at compile time.  Type inference is used to avoid the
need to specify these types explicitly in many situations, reducing the
boilerplate code while keeping the safety of a statically types language.&lt;/p&gt;

&lt;p&gt;Type inference in Fuzion occurs at explicit or implicit assignments. An explicit
assignment is a field declaration with an initial value such as&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;v := expr
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;while an implicit assignment occurs, e.g., when a routine returns the value of
its last expression as its result&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;sum (x, y u32) =&amp;gt;
  x + y
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;or when an argument is passed to a function&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;sum 1.234e6 567890
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Type inference occurs in two directions: From the value to the field that the
value is assigned to and from the type of the assigned field to the value.
Field declarations using ':=' without an explicit type use the type inferred
from the value, the same holds for routines defined using '=&gt;'.&lt;/p&gt;

&lt;p&gt;On the other hand, the type of expressions such as lambdas or numeric literals are
inferred from what they are assigned to.&lt;/p&gt;

&lt;h2&gt;Type inference from expressions to feature result type&lt;/h2&gt;

&lt;p&gt;When declaring either a field using ':=' or a routine using '=&gt;', the result
type is inferred from the expression that is assigned or returned, respectively:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;v := 123                    # type i32, default type for integer literal
v := "hello"                # type string
highNibble(b u8) =&amp;gt; b &amp;gt;&amp;gt; 4  # type u8
origin =&amp;gt; point 0 0         # type point
&lt;/code&gt;&lt;/pre&gt;

&lt;h2&gt;Type inference from expressions to type arguments&lt;/h2&gt;

&lt;p&gt;Type arguments are inferred from actual arguments as shown by the following
example: Imagine a generic routine &lt;em&gt;square&lt;/em&gt; as follows&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;square&amp;lt;T: integer&amp;lt;T&amp;gt;&amp;gt; (a T) =&amp;gt; a * a
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This could be called using explicit type arguments as in&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;say (square&amp;lt;i32&amp;gt; 23)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;or the type can be inferred from the argument type&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;say (square 23)
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;As a consequence, type arguments can be omitted in many cases.&lt;/p&gt;

&lt;h2&gt;Type inference for lambdas&lt;/h2&gt;

&lt;p&gt;In Fuzion, inline functions (lambdas) are defined using '-&gt;' with the input
variables on the left and the expression on the right.  Types for a lambda are
implicitly taken from the target the lambda is assigned to. E.g., the following
example takes a function argument&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;print(s string, f (string, i32) -&amp;gt; string) =&amp;gt;
  say (f s 3)

print(f (i32, i32) -&amp;gt; i32) =&amp;gt;
  say (f 10 3)

print "Alice" (s,i -&amp;gt; s * i)   # lambda type is (string, i32) -&amp;gt; string
print "Bob"   (s,i -&amp;gt; s + i)
print (s,i -&amp;gt; s * i)           # lambda type is (i32, i32) -&amp;gt; i32
print (s,i -&amp;gt; s + i)
&lt;/code&gt;&lt;/pre&gt;

&lt;h2&gt;Type inference for numeric constants&lt;/h2&gt;

&lt;p&gt;Numeric constants that are assigned to a given type inherit that type.  There is
no immediate distinction between plain numeric literals like '123' or ones using
a fractional parts and exponents such as '-0.1234E4'. The target type determines
the type of the constant.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;v1 u32 := 123456
v2 i8 := -128
v3 i16 := 32000
v4 u64 := 1000000000000000000
v5 i64 := -1000000000000000000
v6 u16 := 4711
v7 f32 := 123456
v8 f64 := 123.456E6
v9 f64 := 1.0E3
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;In case the constant is too large for the target
type, or it has a fractional part not representable by the type, a compile-time
error occurs:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;v1 u32 := -123456       # error: negative value assigned to unsigned
v2 i32 := 3000000000    # error: value too large
v3 i8  := 128           # error: value too large
v4 u16 := 65536         # error: value too large
v5 f32 := 123.456E39    # error: overflow
v7 f64 := 123.456E309   # error: overflow
v8 f32 := 7E-46         # error: underflow
&lt;/code&gt;&lt;/pre&gt;

&lt;h1&gt;Fuzion Intermediate Files&lt;/h1&gt;

&lt;p&gt;Fuzion uses intermediate files during different stages of compilation: module
files that contain library code, application files for whole applications and
Fuzion intermediate representation files that serve as input to the back ends.&lt;/p&gt;

&lt;p&gt;Fuzion uses a simple intermediate code to represent pre-compiled modules and
whole applications. This intermediate code serves as the input for static
analysis tools, optimizers and for different back-ends that produce executable
applications.  The goal in the design of the intermediate file format was high
performance and simplicity for tools using this code.&lt;/p&gt;

&lt;p&gt;The intermediate code is a binary format containing features and types in a way
that may be mapped to memory and used directly, so overhead of parsing this
format into an in-memory representation is avoided.  In particular, if only parts
of a pre-compiled module are used by an application, there is no need to read and
unpack parts of the module intermediate representation that are not used.&lt;/p&gt;

&lt;p&gt;For features containing code, a very simple stack-based format is used. There
are currently only ten different instructions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Unit -- produce a value of unit type&lt;/li&gt;
&lt;li&gt;Current -- produce the current instance as a value&lt;/li&gt;
&lt;li&gt;Constant -- produce a constant value&lt;/li&gt;
&lt;li&gt;Assign -- perform an assignment to a field&lt;/li&gt;
&lt;li&gt;Call -- perform a call to a given feature&lt;/li&gt;
&lt;li&gt;Tag -- convert a value into a tagged value of a choice type&lt;/li&gt;
&lt;li&gt;Match -- match a choice type&lt;/li&gt;
&lt;li&gt;Box -- convert a value type to a ref type&lt;/li&gt;
&lt;li&gt;Unbox -- extract the value from a ref type&lt;/li&gt;
&lt;li&gt;Pop -- drop the top element from the stack&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The intermediate code uses indices to refer to features and types within
intermediate files.  This means that lookup is very efficient, but it also means
that a change in a library module requires recompilation of all dependent
modules.  Any incompatibilities would be found at compile time instead of
resulting in something like Java's 'IncompatibleClassChangeError' at run-time.&lt;/p&gt;

&lt;h1&gt;Foreign language interface&lt;/h1&gt;

&lt;p&gt;Fuzion provides a tool 'fzjava' that takes a Java module file and converts it
into Fuzion features.  In the spirit of Fuzion, Java's packages, classes,
interfaces, methods, constructors, static methods and fields are all converted
into Fuzion features.  Java methods that may throw an exception are
converted into features resulting in a choice type that is either the exception
type or the result type of that method.&lt;/p&gt;

&lt;p&gt;A few intrinsic functions in the Java interpreter back-end use Java's reflection
API to access the corresponding Java code.&lt;/p&gt;

&lt;p&gt;Here is a example how Java code can be used from Fuzion:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;javaString := java.lang.String.new "Hello Java 🌍!"                          # create Java string, type Java.java.lang.String
javaBytes  := javaString.getBytes "UTF8"                                     # get its UTF8 bytes, type is fuzion.java.Array&amp;lt;i8&amp;gt;
match javaBytes
  err error =&amp;gt; say "got an error: $err"
  bytes fuzion.java.Array =&amp;gt;
    say "string has {bytes.count} bytes: $bytes"
    javaString2 := java.lang.String.new bytes 6 bytes.count-6                # create Java string from bytes subset,
    say "Hello "+javaString2                                                 # append Java string to Fuzion string and print it
&lt;/code&gt;&lt;/pre&gt;

&lt;h1&gt;C back-end&lt;/h1&gt;

&lt;p&gt;Fuzion now has a back-end that produces C source code to be compiled to machine
code using clang and LLVM.&lt;/p&gt;

&lt;h1&gt;Fuzion safety&lt;/h1&gt;

&lt;p&gt;A main goal of Fuzion is to provide a development tool for safety-critical
applications.  Fuzion brings a number of features that address safety issues at
different levels:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Language features&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;static typing&lt;/li&gt;
&lt;li&gt;language simplicity&lt;/li&gt;
&lt;li&gt;pre- and post-conditions for design by contract&lt;/li&gt;
&lt;li&gt;no wrap-around for standard operations +, -, *, /, etc.&lt;/li&gt;
&lt;li&gt;mutability restricted to local contexts&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Run-time features&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;dynamic checks where static checks are not sufficient&lt;/li&gt;
&lt;li&gt;(real-time) garbage collection&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Environment features&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;static linking to specific library versions&lt;/li&gt;
&lt;li&gt;static analysis tools&lt;/li&gt;
&lt;li&gt;no dynamic code loading&lt;/li&gt;
&lt;li&gt;simple intermediate representation, simpler tools&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;


&lt;h1&gt;Conclusion and Next Steps&lt;/h1&gt;

&lt;p&gt;The Fuzion language definition and implementation are far from stable, but are
getting closer to become useful.  Big improvements come from the ability to
pre-compile modules and from the foreign language interface for Java, which
makes a giant code base accessible for Fuzion applications to build on.&lt;/p&gt;

&lt;p&gt;Additionally, new projects such as the language server implementation for Fuzion
by Michael Lill help by integrating Fuzion support in popular IDEs and editors.&lt;/p&gt;

&lt;p&gt;Main points that are missing right now are&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a powerful standard library&lt;/li&gt;
&lt;li&gt;additional library modules for all sorts of application needs&lt;/li&gt;
&lt;li&gt;low-level foreign language interface for C&lt;/li&gt;
&lt;li&gt;actual implementations of static analyzers and optimizers&lt;/li&gt;
&lt;li&gt;highly optimizing back-ends&lt;/li&gt;
&lt;li&gt;garbage collection for the C back-end&lt;/li&gt;
&lt;li&gt;documentation, tutorials&lt;/li&gt;
&lt;li&gt;enthusiastic contributors and users!&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Please feel free to contact me in case you want to use Fuzion or want to help
making it a success!&lt;/p&gt;</description>
        <persons>
          <person id="7627">Fridtjof Siebert</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/fuzionlang/attachments/slides/5173/export/events/attachments/fuzionlang/slides/5173/fosdem_2022_fuzion_update_slides.pdf">Fuzion Language Update</attachment>
        </attachments>
        <links>
          <link href="https://flang.dev">Fuzion portal website</link>
          <link href="https://github.com/tokiwa-software/fuzion">Fuzion Sources on GitHub</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/fuzionlang.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/fuzionlang.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-fuzionlang:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-fuzionlang:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12607.php">Submit feedback</link>
        </links>
      </event>
      <event id="12946">
        <start>14:05</start>
        <duration>00:30</duration>
        <room>D.minimalistic</room>
        <slug>adventuresindataflow</slug>
        <title>Adventures in Dataflow</title>
        <subtitle/>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;"How can we democratize computing?" — that is a sentiment echoed by many people, especially those of us in tech who realize what the general audience is missing out from computing devices, when they use them as passive consumers. If we think of computing devices as programmable tools for active exploration, how should they look like? What programming model should they be based on? It's fair to assume that it shouldn't look like what passes for regular programming nowadays, since that is clearly out of touch with users. Perhaps something more... declarative? ...minimalistic? So, how can we bring declarative and minimalistic computing to the masses? And... maybe we have already?&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2352">Hisham Muhammad</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.minimalistic/adventuresindataflow.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/adventuresindataflow.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-adventuresindataflow:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-adventuresindataflow:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12946.php">Submit feedback</link>
        </links>
      </event>
      <event id="12617">
        <start>14:35</start>
        <duration>00:30</duration>
        <room>D.minimalistic</room>
        <slug>minimalsyntaxes</slug>
        <title>Knowledge Management Through Minimal Syntaxes</title>
        <subtitle>Appreciating How Terse Syntaxes Are Capable of Being Combined In Unexpected Ways</subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Presentation of the main components behind gLean - a knowledge-management application which treats problem-domains as a collection of blocks. gLeans USP is in choosing terse components which syntactically do not impede each-other - permitting collections of block to be parsed and interpreted with minimal concerns for complexity. The hope is that gLean will be able to provide YahooPipes style functionality through combining blocks of references; content; annotations; and parsing-logic.&lt;/p&gt;

&lt;p&gt;The following areas are covered:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The talk extols the virtue of the individual components (Gemini protocol's GemText; Emacs-Hyperbole's Kotl; the parser and Lisp, TXR; Jonathan McHugh's Qiuy (a 'Recursive Modelling Language')) as exemplary specialist utilities.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Examples for how Kotl format and GemText markdown can interoperate (to for instance turning a file into representative Kotl blocks; or export Kotl blocks into GemText)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The beautiful/unholy ability for TXR to read a 'raw' GemText file containing TXR syntax and for a 'compiled' GemText file to emerge (given this unintended behaviour requires no additional coding and was not designed I consider this particularly special)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The use of annotations leading blocks to provide logical structures for how a document or a collection of documents should be treated&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description>&lt;p&gt;The attached slide of the talk is a Gemini compatible rendition.&lt;/p&gt;

&lt;p&gt;Infact the recording is made within Emacs, rather than a Gemini compatible browser.&lt;/p&gt;

&lt;p&gt;If a user has Emacs-Hyperbole installed seek areas featuring the lisp reference that starts with:
&amp;lt;highlight-rexexp ...&lt;/p&gt;

&lt;p&gt;With the cursor on highlight press the ACTION key (usually the modifier (ALT) and the return button simultaneously).&lt;/p&gt;

&lt;p&gt;This should enact the relevant colourscheme that was used for the official presentation.&lt;/p&gt;

&lt;p&gt;Multiple such buttons are positioned throughout the document.&lt;/p&gt;

&lt;p&gt;Enjoy....&lt;/p&gt;</description>
        <persons>
          <person id="8661">Jonathan McHugh</person>
        </persons>
        <attachments>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/minimalsyntaxes/attachments/other/4784/export/events/attachments/minimalsyntaxes/other/4784/uw_the_trouble_with_glichen.gmi">Output of compiling 'raw' GemText file with TXR content - using TXR Lisp parser</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/minimalsyntaxes/attachments/other/4785/export/events/attachments/minimalsyntaxes/other/4785/rq_the_trouble_with_glichen.gmi">'raw' Raw GemText file featuring TXR syntax which can be compiled in TXR Lisp parser</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/minimalsyntaxes/attachments/slides/5275/export/events/attachments/minimalsyntaxes/slides/5275/oqo_glean.gmi">Slide presentation - adapted for Gemini compatibility</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.minimalistic/minimalsyntaxes.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/minimalsyntaxes.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-minimalsyntaxes:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-minimalsyntaxes:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12617.php">Submit feedback</link>
        </links>
      </event>
      <event id="12681">
        <start>15:05</start>
        <duration>00:40</duration>
        <room>D.minimalistic</room>
        <slug>lispforeveryone</slug>
        <title>Lisp, but Beautiful; Lisp for Everyone</title>
        <subtitle/>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The old joke goes that LISP stands for "Lots of Irritating Superfluous Parentheses", but another spin could be "LISP Isn't Structurally Parenthetical".  Lispers seem to come to like parentheses eventually and defend them, and newcomers with no preconceptions seem to not have problems as much as existing programmers do, but the fear of lisp in the general programming world remains strong.  But is parenthetical notation really the best way to represent lisp?  In this talk we explore several alternate representations and their practical use, and speculate on a future where everyone could benefit from lisp's unique properties without fear.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1062">Christine Lemmer-Webber</person>
          <person id="8682">Morgan Lemmer-Webber</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.minimalistic/lispforeveryone.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/lispforeveryone.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-lispforeveryone:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-lispforeveryone:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12681.php">Submit feedback</link>
        </links>
      </event>
      <event id="12680">
        <start>15:45</start>
        <duration>00:40</duration>
        <room>D.minimalistic</room>
        <slug>spritelygoblins</slug>
        <title>Spritely Goblins comes to Guile</title>
        <subtitle>Distributed, secure, asynchronous programming</subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;&lt;a href="https://spritelyproject.org/#goblins"&gt;Goblins&lt;/a&gt; is the core secure distributed programming layer of &lt;a href="https://spritelyproject.org/"&gt;Spritely&lt;/a&gt;, a project to research and develop the future of networked communication.  Goblins was originally written &lt;a href="https://docs.racket-lang.org/goblins/index.html"&gt;on top of Racket&lt;/a&gt;, but has recently been &lt;a href="https://gitlab.com/spritely/guile-goblins"&gt;ported to Guile&lt;/a&gt;.  See a live demonstration of using the system in action, and learn about its history!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1062">Christine Lemmer-Webber</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.minimalistic/spritelygoblins.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/spritelygoblins.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-spritelygoblins:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-spritelygoblins:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12680.php">Submit feedback</link>
        </links>
      </event>
      <event id="12600">
        <start>16:25</start>
        <duration>00:35</duration>
        <room>D.minimalistic</room>
        <slug>commonworkflowlang</slug>
        <title>Concise Common Workflow Language</title>
        <subtitle>Concision and elegance in a workflow language using lisp</subtitle>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Scientific workflows are readily and most easily expressed as shell scripts. However, shell scripts are notorious for being "duct tape", and are hard to adapt to different hardware and software environments. Workflow languages such as the Common Workflow Language (CWL) were developed to address this pain point. However, CWL does come at the cost of increased verbosity and reduced readability. Even seasoned scientists shy away from writing CWL, and fall back to the familiarity of shell scripts.&lt;/p&gt;

&lt;p&gt;This need not be. There is no reason to inflict the behind-the-scenes complexity of workflow languages on the user. It should be possible to automatically translate (in other words, compile) a simple shell-like script into a workflow language specification. In effect, we create a new domain specific language that is almost as easy to write as a shell script, but compiles to CWL. No other language is better suited to this task of creating domain specific languages than lisp. The lisps with their homoiconicity and unique macro system empower the programmer to use ordinary code to hack the compiler itself.&lt;/p&gt;

&lt;p&gt;In this talk, I will present the Concise Common Workflow Language (ccwl). The Concise Common Workflow Language (ccwl) is a concise syntax to express CWL workflows. It is a compiler that compiles a simple lispy shell-like workflow specification into a CWL workflow. It is implemented in the Scheme programming language, a minimalist dialect of lisp. I will discuss the considerations that went into the design of ccwl, and demonstrate its expressive power with illustrative examples.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7664">Arun Isaac</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/commonworkflowlang/attachments/slides/4890/export/events/attachments/commonworkflowlang/slides/4890/slides.pdf">Talk slides</attachment>
        </attachments>
        <links>
          <link href="https://ccwl.systemreboot.net/">ccwl website</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/commonworkflowlang.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/commonworkflowlang.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-commonworkflowlang:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-commonworkflowlang:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12600.php">Submit feedback</link>
        </links>
      </event>
      <event id="12746">
        <start>17:00</start>
        <duration>00:40</duration>
        <room>D.minimalistic</room>
        <slug>relationalexplorationofmccarthysamb</slug>
        <title>A Relational Exploration of McCarthy's 'Amb'</title>
        <subtitle/>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We will investigate what weirdness occurs when John McCarthy's non-deterministic 'amb' operator is added to a LISP interpreter written in a relational style, in the miniKanren constraint logic programming language.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The code for this talk can be found at https://github.com/webyrd/relational-amb&lt;/p&gt;</description>
        <persons>
          <person id="7829">William Byrd</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.minimalistic/relationalexplorationofmccarthysamb.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/relationalexplorationofmccarthysamb.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-relationalexplorationofmccarthysamb:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-relationalexplorationofmccarthysamb:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12746.php">Submit feedback</link>
        </links>
      </event>
      <event id="12444">
        <start>17:40</start>
        <duration>00:20</duration>
        <room>D.minimalistic</room>
        <slug>lastmilesandboxing</slug>
        <title>Why everyone needs to know some coding: last-mile sandboxing</title>
        <subtitle/>
        <track>Declarative and Minimalistic Computing</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We'd all like to use computers to their fullest capability. However, we'd also like to restrict the capability of computers to do things we don't intend. These constraints present a problem: how our computers should determine our intention, when the software we use is written by others. Most programming languages ignore this problem, by running untrusted programs with completely open doors. Browsers run programs with a single policy that is mostly hard-coded (no file system access) but also complex, so that it's often unclear what is protected. In this talk I'll describe my attempts to come up with a model that is both flexible and easy to understand.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This talk will:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;elaborate on what makes sandboxing difficult (code is data),&lt;/li&gt;
&lt;li&gt;outline past approaches to sandboxing (web browsers), and&lt;/li&gt;
&lt;li&gt;summarize the problems of past approaches (who watches the watchers?)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;It will describe a new approach that replaces the hard-coded coarse-grained protections of browsers with declarative fine-grained protections organized by the real-world effects of computers (syscalls). In outline, the approach separates untrusted software in apps from a tiny set of programmable policies. Each policy is advice that applies to a single syscall and decides whether to permit the syscall or not.&lt;/p&gt;

&lt;p&gt;This approach is implemented in a fork of Lua for purely text-mode apps. The browser provides default policies, but tries to gradually empower each person over time to take ownership of the policies on their browser without any mediation from others. In the process, it hopes to educate people on some basic aspects of programming.&lt;/p&gt;

&lt;p&gt;The talk will describe the new challenges posed by this approach, including:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;educating people to never paste in code into policies without understanding it&lt;/li&gt;
&lt;li&gt;educating people on the value of minimalism in policy code (and indeed all code)&lt;/li&gt;
&lt;li&gt;educating people on the need for policy code to itself be side-effect-free&lt;/li&gt;
&lt;li&gt;coaching people on good and poor changes to policy code when intended uses are disallowed by policies&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="8477">Kartik Agaram</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lastmilesandboxing/attachments/slides/5110/export/events/attachments/lastmilesandboxing/slides/5110/Why_Everyone_Needs_to_Know_Some_Coding_Kartik_Agaram_FOSDEM_2022.pdf">Why Everyone Needs to Know Some Coding</attachment>
        </attachments>
        <links>
          <link href="https://github.com/akkartik/teliva">Project repo</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/lastmilesandboxing.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.minimalistic/lastmilesandboxing.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#minimalistic-lastmilesandboxing:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#minimalistic-lastmilesandboxing:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12444.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.distributions">
      <event id="12348">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.distributions</room>
        <slug>unify_your_distributions</slug>
        <title>Unify your distributions</title>
        <subtitle>How GNU Guix can run on any of your hardware</subtitle>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Like most developers, I'm against my will a volunteer system administrator. I
take care of my personal and professional notebooks. I also maintain a
powerful build server at home and a remote VPS hosting my blog. From times to
times I even use a single board computer to host some services.&lt;/p&gt;

&lt;p&gt;A few years ago, all those machines ran different, dedicated Linux
distributions: Ubuntu, ArchLinux, Debian, Raspbian, making the maintenance a
nightmare. That was before diving into GNU Guix.&lt;/p&gt;

&lt;p&gt;In this talk, I'll expose how GNU Guix, as an advanced package manager and
Linux distribution can be advantageously used on any kind of machine from
single board computers to VPS machines.&lt;/p&gt;

&lt;p&gt;The declarative aspect of GNU Guix allows to have various operating system
definitions inheriting from each other while the associate tooling such as
"guix system" and "guix deploy" ease the deployment and upgrade tasks.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6927">Mathieu Othacehe</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/unify_your_distributions/attachments/slides/4825/export/events/attachments/unify_your_distributions/slides/4825/talk_distribution_2022.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-unify_your_distributions:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-unify_your_distributions:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12348.php">Submit feedback</link>
        </links>
      </event>
      <event id="12659">
        <start>10:30</start>
        <duration>00:30</duration>
        <room>D.distributions</room>
        <slug>overview_of_flatcar_container_linux_test_framework</slug>
        <title>All's well that tests well</title>
        <subtitle>An overview of Flatcar Container Linux test framework</subtitle>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Flatcar Container Linux is a community driven Linux OS designed to run container workloads: let's see how the community can run the tests and how the Flatcar Team schedules the test before releasing the OS.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Testing an OS, it's quite challenging: defining use-cases is required but since the OS is the base of application workloads, it's not easy to target &lt;em&gt;all&lt;/em&gt; the different use-cases. Let's see in this lecture, how we define, write and run tests for Flatcar Container Linux - a community driven OS designed to run container workloads. We will cover the logic of the Kola test framework but also how they integrate in the release cycle of Flatcar. Finally, we will provide some example to run the tests locally and we hope to share some ideas with OS maintainers in order to improve in a global way the way we test Open-Source OS.&lt;/p&gt;</description>
        <persons>
          <person id="8671">Mathieu Tortuyaux</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.distributions/overview_of_flatcar_container_linux_test_framework.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.distributions/overview_of_flatcar_container_linux_test_framework.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-overview_of_flatcar_container_linux_test_framework:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-overview_of_flatcar_container_linux_test_framework:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12659.php">Submit feedback</link>
        </links>
      </event>
      <event id="12629">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>D.distributions</room>
        <slug>modding_the_immutable_how_to_extend_flatcar</slug>
        <title>Modding the Immutable – how to extend Flatcar, an immutable image-based OS</title>
        <subtitle/>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Flatcar Container Linux is a fully open source, minimal-footprint, secure by default and always up-to-date Linux distribution for running containers at scale. It is shipped as an image and does not include any package management. OS binaries and libraries reside on a read-only partition. This talk will briefly introduce Flatcar’s core concepts before diving into a detailed discussion on modifying, testing, and vending your own OS images using the SDK.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This talk will discuss building, modifying, and testing Flatcar Container Linux OS images. It will introduce the innerworks of the OS image building process and will enable the audience to craft their own images. While running (release-)tests will also be briefly covered the focus is on modifying and building. Target audience are engineers and tinkerers interested in OS building and in vending immutable OS images that fit their own needs.&lt;/p&gt;

&lt;p&gt;Flatcar Container Linux is a minimal Linux distribution optimised for running containers at scale. It ships OS images – both for installation and update – and lacks a package manager. Binaries in the OS partition (at “/usr”) are immutable after installation. Therefore, modifying the OS to suit one’s needs can be challenging, and deeper changes to the OS will require vending one’s own images.&lt;/p&gt;

&lt;p&gt;After a brief intro to Flatcar’s Gentoo roots, build process, and SDK, this talk will dive into understanding sources and repository structure, running builds, smoke-testing custom images, and running full-blown release tests. We will include a number of pre-recorded CLI demos in the talk to aid understanding. The talk will close with an outlook of how to bring your custom images to production.&lt;/p&gt;</description>
        <persons>
          <person id="8667">Thilo Fromm</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/modding_the_immutable_how_to_extend_flatcar/attachments/slides/5091/export/events/attachments/modding_the_immutable_how_to_extend_flatcar/slides/5091/FOSDEM_distributions_modifying_flatcar.pdf"/>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/modding_the_immutable_how_to_extend_flatcar/attachments/slides/5092/export/events/attachments/modding_the_immutable_how_to_extend_flatcar/slides/5092/FOSDEM_distributions_modifying_flatcar.pptx"/>
        </attachments>
        <links>
          <link href="https://github.com/flatcar-linux/Flatcar">Flatcar project on Github</link>
          <link href="https://twitter.com/flatcar">Flatcar Linux twitter account</link>
          <link href="https://video.fosdem.org/2022/D.distributions/modding_the_immutable_how_to_extend_flatcar.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.distributions/modding_the_immutable_how_to_extend_flatcar.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-modding_the_immutable_how_to_extend_flatcar:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-modding_the_immutable_how_to_extend_flatcar:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12629.php">Submit feedback</link>
        </links>
      </event>
      <event id="12954">
        <start>11:30</start>
        <duration>00:40</duration>
        <room>D.distributions</room>
        <slug>securing_and_hardening_a_container_host</slug>
        <title>Securing and Hardening a container host</title>
        <subtitle/>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In the age where customer data is turning out to be a new valuable resource for companies, and the increasing data breaches safeguarding the infrastructure is becoming more and more important. We the maintainers of Flatcar Container Linux, an operating system that thrives for security first will present the best practices to harden and secure your container hosts from the delivery to the different environments to ensure reliability, security and performance.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Even the most secured Kubernetes cluster can have security issues in case the underlying OS is not correctly hardened.
In this talk, we will present the best practices to harden and secure your container hosts from the delivery to the different environments to ensure reliability, security and performance. Through an actual live example, we will introduce how Flatcar Container Linux is first built around security, and uses the hardening practices. From SELinux configuration to audit logs passing by its package management - let's see how this container optimized OS distro can contribute to reduce the surface attack and mitigating threats.&lt;/p&gt;</description>
        <persons>
          <person id="6245">Sayan Chowdhury</person>
        </persons>
        <attachments>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/securing_and_hardening_a_container_host/attachments/paper/5222/export/events/attachments/securing_and_hardening_a_container_host/paper/5222/Securing_and_hardening_container_hosts.pdf">Securing and Hardening Container Host</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.distributions/securing_and_hardening_a_container_host.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.distributions/securing_and_hardening_a_container_host.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-securing_and_hardening_a_container_host:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-securing_and_hardening_a_container_host:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12954.php">Submit feedback</link>
        </links>
      </event>
      <event id="12693">
        <start>12:30</start>
        <duration>01:00</duration>
        <room>D.distributions</room>
        <slug>how_the_distro_needs_change_to_help_foss_on_embedded_linux</slug>
        <title>How The Distro Needs Change to Help FOSS on Embedded Linux</title>
        <subtitle/>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Distros have been the backbone of Linux for the past two decades, but with the advances made in cloud technology and infrastructure, they have started to become less relevant as a solution and product in itself. To be specific: Distros have been reduced from being the universal FOSS product that delivers a complete solution to the user, to a set of very nicely maintained “free beer” types of repos full of packages that make up application building blocks for custom stacks packaged with Docker. The good news is that distros did not fail to deliver the spirit of FOSS as badly on the desktop and server side as they have for embedded Linux.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Distros were never focused on enabling the product builder using FOSS to make great products for embedded Linux. This lack of FOSS support for embedded has caused proprietary OS Dinosaurs like Broadcom and Qualcomm to not only survive, but to this day are still the primary choice of SDKs for the majority of embedded Linux devices that leave the factory. What has gone wrong?&lt;/p&gt;

&lt;p&gt;In this session, Alexander Sack will explore how FOSS has failed embedded Linux. He will also present ideas on how a Distro 2.0 can focus on being more than just a packaging repo and can ultimately help FOSS also win embedded Linux.&lt;/p&gt;</description>
        <persons>
          <person id="7193">Alexander Sack</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://pantavisor.io">Pantavisor project website</link>
          <link href="https://github.com/pantavisor">Pantavisor project repo</link>
          <link href="https://video.fosdem.org/2022/D.distributions/how_the_distro_needs_change_to_help_foss_on_embedded_linux.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.distributions/how_the_distro_needs_change_to_help_foss_on_embedded_linux.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-how_the_distro_needs_change_to_help_foss_on_embedded_linux:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-how_the_distro_needs_change_to_help_foss_on_embedded_linux:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12693.php">Submit feedback</link>
        </links>
      </event>
      <event id="12718">
        <start>13:30</start>
        <duration>00:45</duration>
        <room>D.distributions</room>
        <slug>eclipse_oniro_a_production_os</slug>
        <title>Eclipse Oniro: A production OS</title>
        <subtitle>Focus on your applications again</subtitle>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Imagine you're an engineer at an ODM or OEM working on a IoT product for
the smarthome - from a simple thermostat to security alarms, from set top
boxes to internet gateways.&lt;/p&gt;

&lt;p&gt;Linux is a fairly obvious choice to build these product that have greater
than 128MB of RAM and storage. On resource-constrained devices, an RTOS
such as Zephyr is able to even run on devices with as little as a few
hundred KB of RAM and storage.&lt;/p&gt;

&lt;p&gt;However, the kernel is a small part of the device's software stack - there
is middleware, application frameworks, security policies, key management,
OTA and multi-year maintenance that the company needs to budget into the
device's engineering support costs.&lt;/p&gt;

&lt;p&gt;Viewing the Linux and RTOS ecosystems as two parts of a single product
platform allows for a coherent view of both ecosystems by developers. You
want to make sure that you can apply the same set of software
configurations and policies across both ecosystems e.g. library versions,
compatible protocol suites, security configurations, OTA mechanisms and
even a single set of IP compliance tools.&lt;/p&gt;

&lt;p&gt;As an example, when you decide you want to secure all your network
communications out-of-the-box in your product platform, you need to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Find an SSL library that'll fit both footprints&lt;/li&gt;
&lt;li&gt;Configure it to have a coherent set of modern ciphers compatible across
the two ecosystems&lt;/li&gt;
&lt;li&gt;Get the various protocol libraries to build against the chosen SSL
library&lt;/li&gt;
&lt;li&gt;Create key provisioning tools that can work across the two ecosystems&lt;/li&gt;
&lt;li&gt;Perform interoperability tests&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Now repeat this exercise across every key component of the OS - security
policy, networking features, OTA, toolchain hardening, IP compliance tools
and you end up with a meta-project that spans and contributes to both
ecosystems.&lt;/p&gt;

&lt;p&gt;We've started to build such a open product platform with opinionated
defaults that follow community best practices with Eclipse Oniro. And
this is our story about our plans for the future.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8691">Amit Kucheria</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/eclipse_oniro_a_production_os/attachments/slides/5040/export/events/attachments/eclipse_oniro_a_production_os/slides/5040/Amit_Kucheria_Oniro_Slides.pdf">Eclipse Oniro: A production OS - Focus on your applications again</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.distributions/eclipse_oniro_a_production_os.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.distributions/eclipse_oniro_a_production_os.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-eclipse_oniro_a_production_os:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-eclipse_oniro_a_production_os:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12718.php">Submit feedback</link>
        </links>
      </event>
      <event id="12596">
        <start>14:15</start>
        <duration>00:40</duration>
        <room>D.distributions</room>
        <slug>tailored_build_and_release_tools_for_linux_distro_and_forks</slug>
        <title>Build and release tools tailored to building, releasing and maintaining Linux distributions and forks</title>
        <subtitle/>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Maintaining a Linux distribution in a consistent and secure manner is challenging. Maintaining a one-to-one clone, can be even more challenging. Rocky Linux maintains a number of in-house tools to aid in this process and makes it as transparent and auditable as possible.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Rocky Linux is aiming to be an exact RHEL clone. When the project first started out, the landscape of tools to automate imports and orchestrate builds across package types were not widespread. First challenge to tackle was imports and patches. Srpmproc was introduced to facilitate upstream imports with consistent automated patching. Distrobuild was later introduced as a meta-orchestration layer for already existing build tools within the EL ecosystem. We're now introducing Peridot, the next generation cloud-native build and release tools for RPM distributions.&lt;/p&gt;</description>
        <persons>
          <person id="8653">Mustafa Gezen</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://rockylinux.org">Rocky Linux website</link>
          <link href="https://video.fosdem.org/2022/D.distributions/tailored_build_and_release_tools_for_linux_distro_and_forks.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.distributions/tailored_build_and_release_tools_for_linux_distro_and_forks.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-tailored_build_and_release_tools_for_linux_distro_and_forks:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-tailored_build_and_release_tools_for_linux_distro_and_forks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12596.php">Submit feedback</link>
        </links>
      </event>
      <event id="12373">
        <start>15:00</start>
        <duration>00:40</duration>
        <room>D.distributions</room>
        <slug>centos_stream_stable_and_continuous</slug>
        <title>CentOS Stream: stable and continuous</title>
        <subtitle/>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;CentOS Stream was introduced in September 2019. In December 2020 it made news, raised a lot of questions and created long hand-wavy discussions and confusing arguments. During 2021 CentOS Stream 9 finally has found its place in the RHEL 9 development process. And now, in early 2022, we can take a good look at how it actually works.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This talk is focused on the development process of the CentOS Stream distribution. We are going to talk about bootstrap, package updates, continuous integration, testing and contribution.&lt;/p&gt;

&lt;p&gt;We welcome distribution developers, but also users which are interested to know what's hidden under the hood of a typical enterprise-level system.&lt;/p&gt;</description>
        <persons>
          <person id="2738">Aleksandra Fedorova</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/centos_stream_stable_and_continuous/attachments/slides/5182/export/events/attachments/centos_stream_stable_and_continuous/slides/5182/centos_stream_slides.pdf">CentOS Stream: stable and continuous</attachment>
        </attachments>
        <links>
          <link href="https://blog.centos.org/2020/12/centos-stream-is-continuous-delivery/">CentOS Stream is continuous delivery</link>
          <link href="https://video.fosdem.org/2022/D.distributions/centos_stream_stable_and_continuous.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.distributions/centos_stream_stable_and_continuous.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-centos_stream_stable_and_continuous:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-centos_stream_stable_and_continuous:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12373.php">Submit feedback</link>
        </links>
      </event>
      <event id="12687">
        <start>15:45</start>
        <duration>00:25</duration>
        <room>D.distributions</room>
        <slug>dos_and_donts_when_building_yocto_based_distro</slug>
        <title>DOs and DON'Ts when building a Yocto based distribution</title>
        <subtitle>What we have learned in a year of building Oniro</subtitle>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;After approximately a year of work, Oniro - the Eclipse Foundation's embedded operating system - has been released
to the public, and is open to bigger changes like rebasing
to a newer Yocto branch and updating toolchains. Now we're
seeing - and can share - what we did well and what we will
have to do differently in the future.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;After approximately a year of work, Oniro (https://oniroproject.org/) - the Eclipse
Foundation's embedded operating system - has been released
to the public, and is open to bigger changes like rebasing
to a newer Yocto branch and updating toolchains. Now we're
seeing - and can share - what we did well and what we will
have to do differently in the future.&lt;/p&gt;

&lt;p&gt;We updated a number of packages from dunfell - can this be
avoided or done in a better way?
What can we do about packages that don't have an LTS policy?&lt;/p&gt;

&lt;p&gt;An important goal must be to make rebasing to newer upstream
releases as quick and painless as possible - accumulating
￼as little technical debt as we can.&lt;/p&gt;</description>
        <persons>
          <person id="2501">Bernhard Rosenkränzer</person>
          <person id="8955">Andrei Gherzan</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://oniroproject.org/">The Oniro Project</link>
          <link href="https://video.fosdem.org/2022/D.distributions/dos_and_donts_when_building_yocto_based_distro.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.distributions/dos_and_donts_when_building_yocto_based_distro.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-dos_and_donts_when_building_yocto_based_distro:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-dos_and_donts_when_building_yocto_based_distro:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12687.php">Submit feedback</link>
        </links>
      </event>
      <event id="12344">
        <start>16:15</start>
        <duration>00:45</duration>
        <room>D.distributions</room>
        <slug>chimera_linux</slug>
        <title>Chimera Linux</title>
        <subtitle>A BSD/LLVM distro from scratch</subtitle>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Chimera Linux is a new distribution I started in the middle of 2021, after years of thinking and vague planning. After getting a bunch of real world maintenance experience managing the POWER architecture support in Void Linux, I have decided to make those ideas a reality - a distribution with the Linux kernel, but FreeBSD userland, LLVM/Clang system toolchain and core runtime, musl libc and a fair amount of custom tooling. Right now, it is a bootable system targeting a variety of CPU architectures (aarch64, ppc64le, riscv64, x86_64...) that is easily bootstrappable (and capable of building itself), testable, lightweight and fast (but still in heavy development). It uses the apk package manager (of Alpine Linux) and a completely custom source packages collection and build system written in Python, allowing for sandboxed, fully unprivileged package builds.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The distribution follows a rolling release model for its simplicity and ease of release management, but without insisting on bleeding edge versions. The build tooling is capable of bringing the system up from scratch using any other musl-based distribution as a base (and without requiring any GNU components beyond currently their make implementation) - the system rebuilds itself 3 times for that purpose. Link-time optimization (specifically Clang's thin LTO) is enabled for nearly all packages. The lightweight, dependency-based, supervising 'dinit' service manager takes care of boot, and Wayland is the preferred display server. The system aims to be general purpose, not niche; a primary goal is breaking up some status quos in the Linux ecosystem and provide a truly viable alternative. It should be community driven, open, welcoming and unorthodox, without any pointless dogmatism.&lt;/p&gt;

&lt;p&gt;In the talk I will cover my journey towards having a system capable of boot, what it took to bring up a distribution from scratch and how I dealt with various obstacles, and what I learned on the way, as well as the future of the project. Some basic Linux administration knowledge will be required from the audience, but any somewhat tech-savvy person should be able to follow.&lt;/p&gt;</description>
        <persons>
          <person id="2589">Daniel Kolesa</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/chimera_linux/attachments/slides/4838/export/events/attachments/chimera_linux/slides/4838/chimera_linux_fosdem2022.pdf">Chimera Linux</attachment>
        </attachments>
        <links>
          <link href="https://chimera-linux.org">Website</link>
          <link href="https://video.fosdem.org/2022/D.distributions/chimera_linux.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.distributions/chimera_linux.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-chimera_linux:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-chimera_linux:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12344.php">Submit feedback</link>
        </links>
      </event>
      <event id="12383">
        <start>17:00</start>
        <duration>00:45</duration>
        <room>D.distributions</room>
        <slug>collaboration_instead_of_competition</slug>
        <title>Collaboration instead of Competition</title>
        <subtitle>The Linux Distributions Working Group at the Open Mainframe Project</subtitle>
        <track>Distributions</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Default community distributions are running in the same issues for special architectures. Every Linux distribution has got mostly separate maintainers and hardware distributors are handling these communities really often disconnected. That has been identified also for the architecture s390x. Therefore, openSUSE, Fedora and Debian have established together with IBM a  Linux Distributions Working Group for a better collaboration together and with the goal to receive better support. In this presentation you should receive an overview about a good collaboration between Linux distributions and what you can achieve together with such a Working Group.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8504">Sarah Julia Kriesch</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/collaboration_instead_of_competition/attachments/slides/5243/export/events/attachments/collaboration_instead_of_competition/slides/5243/CollaborationInsteadOfCompetition_SarahJuliaKriesch.pdf">Collaboration instead of Competition</attachment>
        </attachments>
        <links>
          <link href="https://wiki.openmainframeproject.org/display/LinuxDistrosWG/Linux+Distributions+Working+Group?desktop=true&amp;macroName=contributors">Linux Distributions Working Group</link>
          <link href="https://www.openmainframeproject.org/">Open Mainframe Project</link>
          <link href="https://video.fosdem.org/2022/D.distributions/collaboration_instead_of_competition.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.distributions/collaboration_instead_of_competition.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#distributions-collaboration_instead_of_competition:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#distributions-collaboration_instead_of_competition:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12383.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.embedded">
      <event id="12527">
        <start>13:00</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>eclipse_mqtt</slug>
        <title>Eclipse Amlen: Messaging for IoT/Web/Mobile</title>
        <subtitle>MQTT Messaging for Fun &amp; Profit</subtitle>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Eclipse Amlen is a newly available message broker that focuses on publish/subscribe messaging for IoT/Web/Mobile use-cases.
It has full support for the widely used MQTTv5 and MQTTv3.1.1 protocols.
It is easy to set up and manage and has support for high availability pairs and clusters of brokers.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Amlen is based on an initial contribution of IBM's WIoTP Message Gateway message broker (formerly called MessageSight) so
it has a mature codebase with a long pedigree of use in large deployments, e.g. in the Automotive industry.&lt;/p&gt;

&lt;p&gt;Jon is the project lead for Eclipse Amlen, he is on the OASIS MQTT standards committee and has been the lead architect
for IBM's Message Gateway product as well as one of the initial developers on the codebase.&lt;/p&gt;</description>
        <persons>
          <person id="8468">Jon Levell</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.eclipse.org/amlen">Official Project website</link>
          <link href="https://amlen.org">Amlen Contributor Blog</link>
          <link href="https://video.fosdem.org/2022/D.embedded/eclipse_mqtt.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/eclipse_mqtt.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-eclipse_mqtt:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-eclipse_mqtt:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12527.php">Submit feedback</link>
        </links>
      </event>
      <event id="12673">
        <start>13:30</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>oniro_blueprints</slug>
        <title>Oniro Blueprints for IoT devices</title>
        <subtitle>From open-source seeds to products</subtitle>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In the Eclipse Oniro project, a distributed OS for consumer electronics,
we're proposing a collection of "blueprints" use cases and their implementations
using embedded software on reference hardware.&lt;/p&gt;

&lt;p&gt;Today, we are going to explain our motivations for the blueprints' approach
and of course how to replicate and deploy firmware from sources and
why Oniro can be flexible to create the device of your dream.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Oniro is an ambitious Eclipse project,
one of its challenges is to defragment existing IoT ecosystems.&lt;/p&gt;

&lt;p&gt;To target a bigger heterogeneous range of IoT devices,
openness, flexibility, and interoperability,
should be enabled at the Operating System level.&lt;/p&gt;

&lt;p&gt;Since the beginning of this versatile OS development,
a complementary blueprint concept was introduced
to be more aligned with different aspects of the software and hardware industry.&lt;/p&gt;

&lt;p&gt;Blueprints are standalone projects that are addressing specific uses cases
by providing "semi final integration" that would make use of the underneath technology.&lt;/p&gt;

&lt;p&gt;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.
Blueprints also could inspire devices makers to address similar or more sophisticated use cases.&lt;/p&gt;

&lt;p&gt;Today as we speak, our reference blueprints include
a vending machine, an IoT gateway, a door lock, keypad and more.&lt;/p&gt;

&lt;p&gt;The results of our work are going to be demonstrated and we will be presenting
what is common and what differs.&lt;/p&gt;

&lt;p&gt;Each of those achievements are targeting different uses case and different environments,
but many steps can be factorized from building process, customization to
security or IP compliance scanning.&lt;/p&gt;

&lt;p&gt;Expect to see demos on how our Oniro project leverages other opensource projects
like Yocto/OE Embedded distribution, Linux and Zephyr Kernel, LVGL UI toolkit,
OpenThread mesh networking, Web of Things and more.&lt;/p&gt;</description>
        <persons>
          <person id="1773">Philippe Coval</person>
          <person id="8955">Andrei Gherzan</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/oniro_blueprints/attachments/slides/5281/export/events/attachments/oniro_blueprints/slides/5281/oniro_blueprints_fosdem2022.pdf">oniro-blueprints-fosdem2022.pdf</attachment>
        </attachments>
        <links>
          <link href="https://oniroproject.org/">Oniro: The Distributed Operating System That Connects Consumer Devices Big and Small</link>
          <link href="https://booting.oniroproject.org/">Oniro sources</link>
          <link href="https://www.youtube.com/watch?v=p-gSvehb-As&amp;list=PLy7t4z5SYNaQBDReZmeHAknEchYmu0LLa#OniroPlaylist">Oniro Videos</link>
          <link href="https://oniroproject.org/join-us/#fosdem2022">Join Eclipse's Oniro Project</link>
          <link href="https://fosdem.org/2022/schedule/event/welcome_oniro/">Welcome to FOSDEM2022's Oniro online stand </link>
          <link href="https://fosdem.org/2022/schedule/event/openthread_mesh_network/">Oniro IoT Gateway FOSDEM2022 presentation</link>
          <link href="https://rzr.github.io/rzr-presentations/docs/oniro-blueprints#FOSDEM2022">Oniro Blueprints FOSDEM2022 Presentation slides (Web with videos)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/oniro_blueprints.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/oniro_blueprints.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-oniro_blueprints:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-oniro_blueprints:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12673.php">Submit feedback</link>
        </links>
      </event>
      <event id="12671">
        <start>14:00</start>
        <duration>01:00</duration>
        <room>D.embedded</room>
        <slug>astarte_data_collection</slug>
        <title>Astarte: from data collection to fleet management</title>
        <subtitle>How Astarte evolved from a broker plugin to an IoT ecosystem</subtitle>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Astarte is an Open Source IoT framework focused on data management and processing.
The talk will illustrate its concepts, its architecture and it will present a fleet management system developed on top of it.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;By providing all the building blocks needed for an IoT project, the Astarte platform has quickly become a turnkey solution able to provide IoT and AI services while also allowing to save time and avoiding reinventing the wheel for any given new IoT usecase.
Its features enabled Astarte to grow into a larger ecosystem, providing integrations with a wider community such as Eclipse Oniro. The Edgehog device manager is the latest addition to this ecosystem: it's a multitenant device manager, built on top of Astarte.
After an introduction on Astarte, the talk will showcase how the platform can be used to provide all the operations expected from a modern device manager, like OTA updates, geolocation, etc. The talk will end sharing further info about the integration with Eclipse Oniro and its roadmap.&lt;/p&gt;</description>
        <persons>
          <person id="6474">rbino</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/astarte_data_collection/attachments/slides/5151/export/events/attachments/astarte_data_collection/slides/5151/AstarteFOSDEM2022.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/astarte-platform/astarte">Astarte Github</link>
          <link href="https://github.com/edgehog-device-manager/edgehog/">Edgehog Github</link>
          <link href="https://astarte.cloud">Astarte Website</link>
          <link href="https://video.fosdem.org/2022/D.embedded/astarte_data_collection.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/astarte_data_collection.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-astarte_data_collection:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-astarte_data_collection:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12671.php">Submit feedback</link>
        </links>
      </event>
      <event id="12533">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>openthread_mesh_network</slug>
        <title>Running an OpenThread Mesh Network with Linux and Zephyr</title>
        <subtitle>Transparent IoT Gatway Blueprint of the Oniro Project</subtitle>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Thread protocol specifies a low-power IoT mesh network. It offers
self-healing, low latency and IPv6 connectivity without a single point of
failure. In addition to the lower layer mesh functionality it also
offers mesh network management, as well as secure onboarding of headless
devices.&lt;/p&gt;

&lt;p&gt;OpenThread is an open source project implementing the Thread protocol and its
components. The focus of this talk is to demonstrate a Linux based OpenThread
border router and Zephyr based mesh nodes. Tight together by a Yocto based
build system this talk shows all components you need to have an IPv6 enabled
micro-processor on a low-power wireless link. The used power is small enough
to allow operating a small sensor for months or years on a coin cell battery in such a
scenario. All served by a Linux based border router to allow for internet
access and end-to-end IPv6 connectivity.&lt;/p&gt;

&lt;p&gt;All of the above is bundled together in an Eclipse Oniro Project blueprint
for a transparent IoT gateway.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1814">Stefan Schmidt</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/openthread_mesh_network/attachments/slides/4908/export/events/attachments/openthread_mesh_network/slides/4908/2022_02_06_FOSDEM_Running_an_OpenThread_network.pdf">2022-02-06-FOSDEM-Running-an-OpenThread-network</attachment>
        </attachments>
        <links>
          <link href="https://docs.oniroproject.org/projects/blueprints/en/latest/transparent-gateway.html">Blueprint documentaion:</link>
          <link href="https://www.youtube.com/watch?v=o_3ITbSAvNg">Demonstration video:</link>
          <link href="https://oniroproject.org">Eclipse Oniro Project:</link>
          <link href="https://video.fosdem.org/2022/D.embedded/openthread_mesh_network.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/openthread_mesh_network.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-openthread_mesh_network:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-openthread_mesh_network:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12533.php">Submit feedback</link>
        </links>
      </event>
      <event id="12663">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>r155_compliance</slug>
        <title>Towards UN R155 compliance with open source stack</title>
        <subtitle/>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;After presenting key constraints of new cybersecurity standards UN R155/R156 regulations, the session presents how redpesk open source stack helps to address those concerns, especially with it secured-by-design architecture.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The UNECE WP.29 regulation R155 for Cyber Security Management and R156 for Software Updates have been adopted in 2021 by UNECE’s World Forum for Harmonization of Vehicle Regulations. This means that cybersecurity is now non-negotiable for accessing the market in more than 60 countries, starting in July 2022.&lt;/p&gt;

&lt;p&gt;The open source secured-by-design stack redpesk helps to fulfill regulatory requirements by providing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;MAC-enabled Linux distribution (SMACK/SELinux)&lt;/li&gt;
&lt;li&gt;secure microservices architecture&lt;/li&gt;
&lt;li&gt;integration with RTOS for safety&lt;/li&gt;
&lt;li&gt;Innovative container engine fitted for embedded&lt;/li&gt;
&lt;li&gt;LTS on full car life (approx. 20 years)&lt;/li&gt;
&lt;li&gt;SOTA support&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="1784">José Bollo</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.embedded/r155_compliance.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/r155_compliance.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-r155_compliance:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-r155_compliance:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12663.php">Submit feedback</link>
        </links>
      </event>
      <event id="12696">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>container_manager_in_c</slug>
        <title>Why Embedded Linux Needs a Container Manager Written in C</title>
        <subtitle/>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Container technology has always been part of the cloud domain, and as such, its roadmap has usually been dictated by the use cases and requirements of that world. In the servers’ domain, resource utilization is nowhere near as relevant as it is in the embedded domain. The different languages and technologies that power the tools and mechanisms through which containers are leveraged in the bare metal server and /cloud worlds just don’t fit into the requirements of embedded.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Despite the above, these past couple of years have seen an aggressive push from cloud-centric companies trying to tell the Embedded Linux ecosystem and its development community that we should make do with Golang, NodeJS and similar solutions and tools. Most are unaware of the challenges when you cram cloud tools into a resource constrained embedded system. Even though the architecture of some of these frameworks have the right intention (LXD), most just lack the interest in understanding the specific requirements of embedded.&lt;/p&gt;

&lt;p&gt;In this talk, we’ll explore how using containers for embedded systems modelling can help facilitate development cycles by enabling modular software architectures. We’ll deep dive into what the real requirements of embedded systems are and how modern container technology can help us meet the actual needs of this world. And lastly, we’ll walk through an example with Pantavisor, an open source container framework implemented for embedded systems.&lt;/p&gt;</description>
        <persons>
          <person id="4654">Ricardo Mendoza</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://pantavisor.io">Pantavisor Project</link>
          <link href="https://github.com/pantavisor">Pantavisor Repo</link>
          <link href="https://video.fosdem.org/2022/D.embedded/container_manager_in_c.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/container_manager_in_c.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-container_manager_in_c:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-container_manager_in_c:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12696.php">Submit feedback</link>
        </links>
      </event>
      <event id="12552">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.embedded</room>
        <slug>jetson_ota</slug>
        <title>Over-the-air (OTA) software updates with NVIDIA Jetson</title>
        <subtitle/>
        <track>Embedded, Mobile and Automotive</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;With over half a million developers worldwide, NVIDIA® JetsonTM is one of the most popular embedded computing platforms that brings AI performance to the Edge in a power-efficient and compact form factor&lt;/p&gt;

&lt;p&gt;In this talk, we will cover in detail a unique way of integrating a robust and secure over-the-air software (OTA) updates with the NVIDIA JetPack 4.6 production release that works for all Jetson System-on-Modules (SoMs) with support for the official L4T (Ubuntu-based) operating system, running JetPack 4.6 or later. As it is built on top of the latest JetPack SDK release, there is no need to have separate integrations when building and deploying applications on different Jetson SoMs. This has the benefit of enormously cutting down the bringup time of an OTA solution to do all types of OTA updates. It has low maintenance costs since it does not involve modifying the boot process and rather relying on officially supported tools by NVIDIA which should not “break” with new L4T releases or board changes. We will cover the details of the integration with the high-level user flow as outline below, which “clones” the running image of a golden device and deploys it in a robust manner to the entire fleet of devices:&lt;/p&gt;

&lt;p&gt;-Download L4T image from NVIDIA
-Use NVIDIA tools to flash A/B setup with L4T image
-Install Mender as deb package, plus integration layer
-Run Mender snapshot to create Artifact
-Deploy Artifact snapshot to fleet&lt;/p&gt;</abstract>
        <description>&lt;p&gt;With over half a million developers worldwide, NVIDIA® JetsonTM is one of the most popular embedded computing platforms that brings AI performance to the Edge in a power-efficient and compact form factor&lt;/p&gt;

&lt;p&gt;In this talk, we will cover in detail a unique way of integrating a robust and secure over-the-air software (OTA) updates with the NVIDIA JetPack 4.6 production release that works for all Jetson System-on-Modules (SoMs) with support for the official L4T (Ubuntu-based) operating system, running JetPack 4.6 or later. As it is built on top of the latest JetPack SDK release, there is no need to have separate integrations when building and deploying applications on different Jetson SoMs. This has the benefit of enormously cutting down the bringup time of an OTA solution to do all types of OTA updates. It has low maintenance costs since it does not involve modifying the boot process and rather relying on officially supported tools by NVIDIA which should not “break” with new L4T releases or board changes.
We will cover the details of the integration with the high-level user flow as outline below, which “clones” the running image of a golden device and deploys it in a robust manner to the entire fleet of devices:&lt;/p&gt;

&lt;p&gt;-Download L4T image from NVIDIA
-Use NVIDIA tools to flash A/B setup with L4T image
-Install Mender as deb package, plus integration layer
-Run Mender snapshot to create Artifact
-Deploy Artifact snapshot to fleet&lt;/p&gt;</description>
        <persons>
          <person id="8626">Luis Ramirez  Vargas</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.embedded/jetson_ota.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.embedded/jetson_ota.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#embedded-jetson_ota:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#embedded-jetson_ota:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12552.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.emulator">
      <event id="13134">
        <start>10:00</start>
        <duration>00:45</duration>
        <room>D.emulator</room>
        <slug>grog</slug>
        <title>Testing Macromedia director in ScummVM</title>
        <subtitle/>
        <track>Emulator Development</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;ScummVM reached a milestone with the release of 2.5.0. Version 0.0.1 was released 20 years ago. The latest release was also the first release that included support for a few Director games.&lt;/p&gt;

&lt;p&gt;MacroMedia Director, later Adobe Director, was a multimedia application authoring platform. Its ease of use led to a huge number of graphic adventure games being written with it. This was the late 90's. Some well known games are the Journeyman Project, Total Distortion and Spaceship Warlock.&lt;/p&gt;

&lt;p&gt;One challenge to over come was to work on the code without breaking other parts.
We'll go over the architecture of ScummVM, dive deeper into the Director Engine and land on how tests improved the code.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8866">Roland van Laar</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.emulator/grog.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.emulator/grog.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-grog:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-grog:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13134.php">Submit feedback</link>
        </links>
      </event>
      <event id="12624">
        <start>10:45</start>
        <duration>00:45</duration>
        <room>D.emulator</room>
        <slug>z80</slug>
        <title>Z80: the last secrets</title>
        <subtitle>Microarchitectural leaks, 45 years later</subtitle>
        <track>Emulator Development</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;While writing a Z80 emulator, you might ask yourself: should it be 100% accurate ? Maybe not, if you just want to run old software. But what if you're not and this old software accidentally depends on undocumented behavior ?
In this talk we'll explore how, 30 years after its design, a few people on a Russian retro-computing forum reverse engineered an undocumented Z80 register: MEMPTR. And how 6 years later, another even less known secret register was discovered.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6106">Anisse Astier</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/z80/attachments/slides/5207/export/events/attachments/z80/slides/5207/z80_last_secrets.pdf">Z80 last secrets slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.emulator/z80.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.emulator/z80.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-z80:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-z80:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12624.php">Submit feedback</link>
        </links>
      </event>
      <event id="13081">
        <start>11:30</start>
        <duration>00:30</duration>
        <room>D.emulator</room>
        <slug>bugs_life</slug>
        <title>CANCELLED Debugging Strategies for Emulator Developers</title>
        <subtitle>Are bugs a form of artificial life?</subtitle>
        <track>Emulator Development</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Emulators, especially ones targeting real time performance, can become very complex, and can present unique debugging challenges - more akin to cpu, operating system and compilers than typical software projects.&lt;/p&gt;

&lt;p&gt;In this talk I will cover common and not-so-common classes of bugs that manifest themselves in a vast range of emulators (gameboy, dreamcast, x86/64 usermode will be used as examples), and strategies and heuristics I've used over the years to identify, prevent, mitigate, fix and prevent them from reappearing.&lt;/p&gt;

&lt;p&gt;Both theoretical concepts and background, as well as concrete examples of past bug hunts will be included.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8732">Stefanos Kornilios Mitsis Poiitidis</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#emulator-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-bugs_life:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-bugs_life:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13081.php">Submit feedback</link>
        </links>
      </event>
      <event id="12987">
        <start>12:00</start>
        <duration>02:00</duration>
        <room>D.emulator</room>
        <slug>ps3</slug>
        <title>PlayStation 3 Emulation</title>
        <subtitle>(Re)implementing the impossible</subtitle>
        <track>Emulator Development</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The PlayStation 3 features one of the most ambitious and fascinating architectures among video game consoles. Once deemed near-impossible to emulate in real-time, we now celebrate the 10th anniversary of its most popular emulator: RPCS3, a free and open-source software capable of running two thirds of the console's catalogue on PC.&lt;/p&gt;

&lt;p&gt;This talk describes the hardware and software stack of the PlayStation 3, covering the IBM Cell/B.E. CPU, Nvidia RSX GPU and Sony's CellOS operating system in detail. We compare these against earlier and later consoles, explaining how their design and complexity has shaped a new generation of emulators and binary translators, before delving into the history and internals of RPCS3 and other PlayStation 3 emulators.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8812">Alexandro Sanchez Bach</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/ps3/attachments/slides/5257/export/events/attachments/ps3/slides/5257/slides.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://rpcs3.net/">RPCS3</link>
          <link href="https://www.copetti.org/writings/consoles/playstation-3/">PlayStation 3 Architecture</link>
          <link href="https://video.fosdem.org/2022/D.emulator/ps3.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.emulator/ps3.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-ps3:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-ps3:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12987.php">Submit feedback</link>
        </links>
      </event>
      <event id="12339">
        <start>14:00</start>
        <duration>00:30</duration>
        <room>D.emulator</room>
        <slug>fuzz</slug>
        <title>Fuzzing, or How I Generated 1,000,000 New Processor Test Cases in an Afternoon</title>
        <subtitle>Fill your boots. Then fill somebody else's.</subtitle>
        <track>Emulator Development</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Most emulator authors will have encountered a test suite; a series of compliance tests that indicate whether their implementation matches original hardware. But these suites tend to assume a lot of working functionality beyond the part they are specifically testing, often being designed by an intelligent human being to test finished emulators.&lt;/p&gt;

&lt;p&gt;This presentation covers an alternative source and target of tests: random numbers, to test individual processor instructions, so that future emulator authors can test from day one.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7577">Thomas Harte</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/TomHarte/ProcessorTests">https://github.com/TomHarte/ProcessorTests</link>
          <link href="https://video.fosdem.org/2022/D.emulator/fuzz.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.emulator/fuzz.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-fuzz:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-fuzz:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12339.php">Submit feedback</link>
        </links>
      </event>
      <event id="12927">
        <start>14:30</start>
        <duration>01:00</duration>
        <room>D.emulator</room>
        <slug>squirrel</slug>
        <title>SquirrelJME, Java Flip Phone Emulation</title>
        <subtitle>Preserving the history of obsolete cellular devices</subtitle>
        <track>Emulator Development</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;SquirrelJME is a from-scratch and clean-room built Java Virtual Machine implementation which targets the J2ME/Java ME runtimes which have been historically used for mobile applications such as those running on flip phones. The presentation will go over the unique challenges of implementing a JVM along with differences compared to traditional CPUs. Additionally due to the rapidly changing nature of traditional desktop Java Virtual Machines, backwards compatibility with older byte codes is not a guarantee, therefor there is a specific need for a non-changing run-time environment for these older applications.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8787">Stephanie Gawroriski</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/squirrel/attachments/slides/5109/export/events/attachments/squirrel/slides/5109/SquirrelJME_Java_Flip_Phone_Emulation.pptx">SquirrelJME, Java Flip Phone Emulation</attachment>
        </attachments>
        <links>
          <link href="https://squirreljme.cc/">Main Website</link>
          <link href="https://github.com/SquirrelJME/SquirrelJME">GitHub Repository</link>
          <link href="https://video.fosdem.org/2022/D.emulator/squirrel.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.emulator/squirrel.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-squirrel:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-squirrel:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12927.php">Submit feedback</link>
        </links>
      </event>
      <event id="12338">
        <start>15:30</start>
        <duration>01:00</duration>
        <room>D.emulator</room>
        <slug>emu_config</slug>
        <title>Static and Dynamic Analysis for Automatic Emulator Configuration</title>
        <subtitle>Or: Not asking the user so many damn questions.</subtitle>
        <track>Emulator Development</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A disadvantage of many emulators is that they require the user to know how they should configure a machine — which model, which expansions and peripherals — and what they need to type before they can use their desired classic software. Wouldn't it be nice if the emulator could just figure all that stuff out for you?&lt;/p&gt;

&lt;p&gt;This presentation covers three means of doing so: ahead-of-time static analysis, runtime dynamic analysis, and brute-force try-them-all parallel execution.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7577">Thomas Harte</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.emulator/emu_config.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.emulator/emu_config.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-emu_config:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-emu_config:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12338.php">Submit feedback</link>
        </links>
      </event>
      <event id="12334">
        <start>16:30</start>
        <duration>00:45</duration>
        <room>D.emulator</room>
        <slug>venix</slug>
        <title>A Venix/86 emulator</title>
        <subtitle>A step in recreating Venix/86 Sources</subtitle>
        <track>Emulator Development</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Venix/86 was the first commercially available Unix for the IBM PC. PC/IX was the first one that IBM supported, but VentureCom created released this port about the time PC/IX was announced. They ported it to a number of the 'near compatible' systems as well, so for many people the first Unix available on those early 8086/8088 machines was Venix. This included the DEC Rainbow 100B with Venix/86R.&lt;/p&gt;

&lt;p&gt;A companion project to recreate the sources for Venix/86 from 7th edition tapes now available was hampered by the slow speed of the DEC Rainbow, so I wrote the emulator to seed that along.&lt;/p&gt;

&lt;p&gt;This talk will be about the emulator's structure, system call interface and portability to other ancient 8088/8086 Unixes. It will also discuss how many of the early ports coped with lack of a MMU in clever ways. It will touch on the path here, and then focus on the current implementation.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The author had a DEC Rainbow which was supported with Venix/86R. By the time the author was employed post college, copies of it had become impossible to find.&lt;/p&gt;

&lt;p&gt;Recently, A copy surfaced and I started working with it. A number of interesting challenges for creating this port will be discussed. I took the hard path to decompile parts of libc to discover the system call interface, and went through a few preliminary implementations of Venix/86 emulation before arriving at what we have today. After the initial decompile, documentation surfaced, other incomplete copies were found along with some source, all of which confirmed most of the details that had been guessed.&lt;/p&gt;

&lt;p&gt;This has been a labor of love for me, using 4 different x86 emulators, a number of deep searches online to find as much info as I can, disassembly, etc. I'll touch on some of these aspects as well. It's currently running using vm86 on a FreeBSD/i386 bhyve instance hosted on a FreeBSD/amd64 machine nicely... A port to qemu user-* might be possible too.&lt;/p&gt;

&lt;p&gt;This goes hand in hand with another project: recreate the sources that can create a Venix kernel using the now-available 7th Edition sources, which may be a future submission.&lt;/p&gt;</description>
        <persons>
          <person id="6482">Warner Losh</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/bsdimp/venix/">Venix Repo for this project</link>
          <link href="https://github.com/bsdimp/venix/tree/master/tools/vm86venix">vm86 venix emulator for this talk</link>
          <link href="http://bitsavers.trailing-edge.com/pdf/dec/pdp11/pro3xx/Pro_VENIX/AA-CM95A-XH_Pro_VENIX_Programmer_Reference_Manual_1984.pdf">Venix System Call Docs</link>
          <link href="https://docs.google.com/presentation/d/1aAxBk6ODGA28H32cH1GNghGJ4O-fSyam5faNFWVSrdI/edit?usp=sharing">Slides</link>
          <link href="https://video.fosdem.org/2022/D.emulator/venix.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.emulator/venix.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-venix:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-venix:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12334.php">Submit feedback</link>
        </links>
      </event>
      <event id="12886">
        <start>17:15</start>
        <duration>00:45</duration>
        <room>D.emulator</room>
        <slug>fex</slug>
        <title>FEX-Emu: Fast(-er) x86 emulation for AArch64</title>
        <subtitle>How we're creating a better gaming experience on ARM</subtitle>
        <track>Emulator Development</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;QEmu is a great project but it isn't really designed around high performance gaming.
Let's create a new project that is specifically designed for running x86 and x86-64 games on AArch64.
With FEX-Emu now off the ground let's talk about the problems of translating x86 and x86-64 to AArch64. Translating 32-bit games to a 64-bit process encounter a bunch of fun issues. On top of that, translating x86/x64 to Arm has issues that you wouldn't really expect.
Come along for the ride with all the problems we encountered and where our future plans lie with FEX-Emu.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8779">Ryan Houdek</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/fex/attachments/slides/4961/export/events/attachments/fex/slides/4961/FEX_Emu_FOSDEM_2022.odp">Slides (odp)</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/fex/attachments/slides/4962/export/events/attachments/fex/slides/4962/FEX_Emu_FOSDEM_2022.pptx">Slides (pptx)</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/fex/attachments/slides/4963/export/events/attachments/fex/slides/4963/FEX_Emu_FOSDEM_2022.pdf">Slides (pdf)</attachment>
        </attachments>
        <links>
          <link href="https://fex-emu.org/">FEX-Emu Website</link>
          <link href="https://github.com/FEX-Emu/FEX">FEX-Emu Github</link>
          <link href="https://video.fosdem.org/2022/D.emulator/fex.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.emulator/fex.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#emulator-fex:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#emulator-fex:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12886.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.mobile">
      <event id="12756">
        <start>10:15</start>
        <duration>00:30</duration>
        <room>D.mobile</room>
        <slug>mobile_kernel_snapdragon_410</slug>
        <title>Running Mainline Linux on Snapdragon 410</title>
        <subtitle>How we support over 25 devices in postmarketOS</subtitle>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Qualcomm Snapdragon 410 (msm8916) is a SoC that was used in many smartphones and
tablets around 2015. It is the most mature "aftermarket" platform postmarketOS can offer
at the time of writing. Many of the supported devices are quite usable and have
most of the expected features like phone calls and mobile data working.&lt;/p&gt;

&lt;p&gt;The talk goes over some of the most important challenges that we have faced while
supporting those devices and describes the ways in which we have solved them.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Apart from the Linux kernel, we focus on various other tools and projects like
lk2nd - a shim bootloader that prepares the environment for booting Linux and
hides some device-specific quirks from the kernel. It also unifies the boot and
installation process on all devices.&lt;/p&gt;

&lt;p&gt;We also have other tools and resources to make porting easier. Those include
various documentation or even a fully automated display driver generator
that helps with the fact that each display requires unique initialization.&lt;/p&gt;</description>
        <persons>
          <person id="8721">Nikita Travkin</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_kernel_snapdragon_410/attachments/slides/5212/export/events/attachments/mobile_kernel_snapdragon_410/slides/5212/FOSDEM22_msm8916.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_snapdragon_410.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_snapdragon_410.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_kernel_snapdragon_410:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_kernel_snapdragon_410:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12756.php">Submit feedback</link>
        </links>
      </event>
      <event id="12846">
        <start>11:00</start>
        <duration>00:40</duration>
        <room>D.mobile</room>
        <slug>mobile_graphical_lisp</slug>
        <title>Portable Parens: Graphical Lisp programs for mobile devices</title>
        <subtitle>Techniques for building responsive, touch-friendly GUI applications with functional programming paradigms</subtitle>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Lisp, the second-oldest programming language, has led the way in
advanced programming techniques through decades of variants and
dialects. This talk will show how Lisp is relevant even in the
burgeoning field of mobile Linux distributions, covering four distinct
techniques for writing touch-friendly, responsive GUI applications in
various Lisp implementations:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Embedding&lt;/li&gt;
&lt;li&gt;Transpilation&lt;/li&gt;
&lt;li&gt;Foreign function interfaces&lt;/li&gt;
&lt;li&gt;Networked microservicing&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;With fully open source examples for each of the methods, written in
Lisp dialects including Clojure, Scheme and Fennel, this talk will
weigh up the pros and cons of the different techniques with regard to
reliability, performance and long-term sustainability in the software
supply chain.&lt;/p&gt;

&lt;p&gt;Finally, the talk will conclude with a proof-of-concept for a
declarative graphical application with GTK4, showcasing the advanced
functional programming features offered by Lisp, and demonstrated on a
physical PinePhone device running PostmarketOS!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8650">Sebastian Crane</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_graphical_lisp.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_graphical_lisp.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_graphical_lisp:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_graphical_lisp:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12846.php">Submit feedback</link>
        </links>
      </event>
      <event id="12482">
        <start>12:00</start>
        <duration>00:35</duration>
        <room>D.mobile</room>
        <slug>mobile_kernel_snapdragon_845</slug>
        <title>From Android to mainline on the Snapdragon 845</title>
        <subtitle>Extending the life of Android devices with upstream kernels and postmarketOS</subtitle>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Explaining a brief history of Linux on Qualcomm devices, how we got to where we are today and what will come in the future. With a specific focus on the OnePlus 6 and other SDM845 devices with mainline Linux support. As well as what exciting things the future holds!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8565">caleb Connolly</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_kernel_snapdragon_845/attachments/slides/5276/export/events/attachments/mobile_kernel_snapdragon_845/slides/5276/from_android_to_mainline_on_sdm845.pdf">SDM845 mainline slides</attachment>
        </attachments>
        <links>
          <link href="https://postmarketOS.org">postmarketOS website</link>
          <link href="https://gitlab.com/sdm845-mainline/linux">our close to mainline kernel fork for SDM845 devices</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_snapdragon_845.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_kernel_snapdragon_845.mp4">Video recording(mp4)</link>
          <link href="https://not.mainline.space/from-android-to-mainline-on-sdm845.pdf">Slides</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_kernel_snapdragon_845:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_kernel_snapdragon_845:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12482.php">Submit feedback</link>
        </links>
      </event>
      <event id="12599">
        <start>13:00</start>
        <duration>00:40</duration>
        <room>D.mobile</room>
        <slug>mobile_social_dilemma</slug>
        <title>Linux Mobile vs. The Social Dilemma</title>
        <subtitle/>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As FOSS on mobile community, let's do our part to fix the many negative effects of social media and its hostile design patterns. We could become the prime example of how to treat users with respect. To not only give them control over their phone, but also over their attention. From design choices in the operating systems and apps to the platforms we choose to communicate about development.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8655">OIiver Smith</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_social_dilemma.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_social_dilemma.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_social_dilemma:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_social_dilemma:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12599.php">Submit feedback</link>
        </links>
      </event>
      <event id="12430">
        <start>13:50</start>
        <duration>00:35</duration>
        <room>D.mobile</room>
        <slug>mobile_modemmanager</slug>
        <title>ModemManager in your phone</title>
        <subtitle/>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;ModemManager provides a general purpose WWAN management stack, which has served as default WWAN management system for standard GNU/Linux distributions for the last 10 years, primarily focused on providing data connectivity to laptops and desktops. In addition to that, different teams building phones with FOSS operating systems have also considered ModemManager as a good tool to take responsibility for the full data and voice call management in phones, primarily because it supports a broad range of devices and systems: not only standalone WWAN modules, but also WWAN stacks integrated in Qualcomm SoCs.&lt;/p&gt;

&lt;p&gt;This talk will provide an overview of the current state of integration of ModemManager in phones, and what's expected in future releases.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8520">Aleksander Morgado</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_modemmanager/attachments/slides/5244/export/events/attachments/mobile_modemmanager/slides/5244/20220110_FOSDEM_2022_ModemManager_in_your_phone.pdf">FOSDEM 2022 - ModemManager in your phone</attachment>
        </attachments>
        <links>
          <link href="https://modemmanager.org">https://modemmanager.org</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_modemmanager.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_modemmanager.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_modemmanager:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_modemmanager:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12430.php">Submit feedback</link>
        </links>
      </event>
      <event id="12698">
        <start>14:45</start>
        <duration>00:35</duration>
        <room>D.mobile</room>
        <slug>mobile_adwaita</slug>
        <title>Welcome to Libadwaita</title>
        <subtitle/>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;GTK4 is finally ready for production, and with it comes Libadwaita, the next generation of the GNOME app development platform. This new library builds on what Libhandy did for GTK3 but takes it even further, streamlining many of the most common things app developers need to build great apps for GNOME, across both desktop and mobile.&lt;/p&gt;

&lt;p&gt;This includes standardized patterns and widgets for basic layout elements like lists and cards, adaptive navigation, touch/touchpad gestures, easier ways of using color in apps, and much more.&lt;/p&gt;

&lt;p&gt;This talk will give a quick overview of the current capabilities of the platform, and show how app developers are making use of it to build apps that work well on computers of all shapes and sizes.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4787">Tobias Bernard</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_adwaita/attachments/slides/5232/export/events/attachments/mobile_adwaita/slides/5232/fosdem2022_libadwaita.pdf">Welcome to Libadwaita</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_adwaita.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_adwaita.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_adwaita:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_adwaita:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12698.php">Submit feedback</link>
        </links>
      </event>
      <event id="13209">
        <start>15:30</start>
        <duration>00:25</duration>
        <room>D.mobile</room>
        <slug>mobile_calls</slug>
        <title>Anatomy of GNOME Calls</title>
        <subtitle>What goes into making a call in GNOME Calls</subtitle>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk we will take a look at the anatomy of GNOME Calls.
We will cover libraries used and how Calls interacts with them to provide
call functionality and other things you'd expect from a dialer application.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8437">Evangelos Ribeiro Tzaras</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mobile_calls/attachments/slides/4978/export/events/attachments/mobile_calls/slides/4978/talk.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://gitlab.gnome.org/GNOME/calls">Gitlab Repository</link>
          <link href="https://puri.sm">Purism</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_calls.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_calls.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_calls:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_calls:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13209.php">Submit feedback</link>
        </links>
      </event>
      <event id="13130">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.mobile</room>
        <slug>mobile_phosh</slug>
        <title>Phosh Contributors Get Together</title>
        <subtitle>Get to meet the other Phosh contributors</subtitle>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Get to meet the other Phosh contributors&lt;/p&gt;</abstract>
        <description>&lt;p&gt;You're contributing to Phosh or its wider ecosystems as designer, translator, distribution packager, tester or developer (or intend to do so)? Then join us at this get together. There's no formal schedule, it's just about meeting other people since we can't have a RL meeting.&lt;/p&gt;</description>
        <persons>
          <person id="8441">Guido Günther</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://gitlab.gnome.org/World/Phosh/phosh">Phosh</link>
          <link href="https://gitlab.gnome.org/World/Phosh/phosh/-/wikis/Phosh-Hackfests,-Get-Togethers,-%E2%80%A6">Signup</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_phosh.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_phosh.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_phosh:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_phosh:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13130.php">Submit feedback</link>
        </links>
      </event>
      <event id="13217">
        <start>16:30</start>
        <duration>01:30</duration>
        <room>D.mobile</room>
        <slug>mobile_closing_session</slug>
        <title>Closing session</title>
        <subtitle/>
        <track>FOSS on Mobile Devices</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Closing session for the FOSS on mobile devices devroom.
We reserve the right to have the "Phosh contributors meeting" bleed into this session.&lt;/p&gt;

&lt;p&gt;Come and join us as we're looking back at FOSDEM22, reflect on how our quest for world domination is going
and talk about anything and everything (tangentially) related to FOSS on mobile devices.
While not mandatory grabbing a refreshing (rejuvenating even!) beverages of your choice is highly recommended
as we're closing this years event.&lt;/p&gt;

&lt;p&gt;No dresscode :)&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8437">Evangelos Ribeiro Tzaras</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_closing_session.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mobile/mobile_closing_session.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mobile-mobile_closing_session:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mobile-mobile_closing_session:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13217.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.radio">
      <event id="13083">
        <start>13:00</start>
        <duration>00:10</duration>
        <room>D.radio</room>
        <slug>radio_welcome</slug>
        <title>Welcome to the Free Software Radio Devroom</title>
        <subtitle/>
        <track>Free Software Radio</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This presentation will give you an overview what to expect in the Free Software Radio devroom at FOSDEM 2022.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5297">Andrej Rode</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.radio/radio_welcome.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_welcome.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#radio-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-radio_welcome:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#radio-radio_welcome:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13083.php">Submit feedback</link>
        </links>
      </event>
      <event id="12327">
        <start>13:10</start>
        <duration>00:30</duration>
        <room>D.radio</room>
        <slug>radio_openwifi</slug>
        <title>Opensource WiFi chip (openwifi) progress and future plan</title>
        <subtitle/>
        <track>Free Software Radio</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The &lt;a href="https://github.com/open-sdr/openwifi"&gt;openwifi&lt;/a&gt; project (opensource WiFi chip) was firstly introduced in the fsr dev room of FOSDEM2020, Brussels. So it would be our honor to give the annual update of the project in the same event!&lt;/p&gt;

&lt;p&gt;This year we will bring these contents:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Features added in 2021&lt;/li&gt;
&lt;li&gt;Bug fixes in 2021&lt;/li&gt;
&lt;li&gt;Some initial test results by the R&amp;amp;S CMW270 WiFi tester&lt;/li&gt;
&lt;li&gt;The community growth we saw in 2021: the new cheaper hardware; the new applications/papers; etc.&lt;/li&gt;
&lt;li&gt;Our current focus and future plan: the progress of WiFi6/802.11ax development; etc.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Related event:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Feb 6 11:20 (Brussels time): &lt;a href="https://fosdem.org/2022/schedule/event/openwifipynqz1/"&gt;Bring openwifi to PYNQ-Z1 with ultra low cost&lt;/a&gt; in &lt;a href="https://fosdem.org/2022/schedule/track/libre_open_vlsi_and_fpga/"&gt;Libre-Open VLSI and FPGA devroom&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;a href="/2022/stands.fosdem.org/stands/openwifi/"&gt;openwifi stand&lt;/a&gt; welcome you the whole weekend.&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="6450">Xianjun Jiao</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/radio_openwifi/attachments/slides/5181/export/events/attachments/radio_openwifi/slides/5181/openwifi_fosdem2022_simple.pdf">openwifi project slides for free software radio devroom</attachment>
        </attachments>
        <links>
          <link href="https://github.com/open-sdr/openwifi">The openwifi Linux driver and user space tools</link>
          <link href="https://github.com/open-sdr/openwifi-hw">The openwifi chip/FPGA design</link>
          <link href="https://github.com/open-sdr">The main openwifi github site</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_openwifi.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_openwifi.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#radio-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-radio_openwifi:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#radio-radio_openwifi:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12327.php">Submit feedback</link>
        </links>
      </event>
      <event id="12677">
        <start>13:40</start>
        <duration>00:20</duration>
        <room>D.radio</room>
        <slug>radio_litex</slug>
        <title>Implementing a GNU Radio/LiteX accelerator using a FPGA-based PCIe co-processor</title>
        <subtitle/>
        <track>Free Software Radio</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Processing tools such as RFNoC by Ettus Research allow for FPGA processing &amp;amp; acceleration however, this can only be used achieved by using USRP devices. gr-litex is an open-source tool that uses GNU Radio with LiteX and allows for different boards by a variety of vendors to achieve processing and acceleration. The project currently uses an Acorn CLE-215+, a cryptocurrency mining accelerator card repurposed as an FPGA for the project.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8680">Victor Omoniyi</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/Victoromoniyi/gr-litex">gr-litex</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_litex.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_litex.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#radio-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-radio_litex:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#radio-radio_litex:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12677.php">Submit feedback</link>
        </links>
      </event>
      <event id="12355">
        <start>14:00</start>
        <duration>00:30</duration>
        <room>D.radio</room>
        <slug>radio_hellschreiber</slug>
        <title>Emitting Hellschreiber from a Raspberry Pi GPIO: combining gr-hellschreiber with gr-rpitx</title>
        <subtitle>GNU Radio running on an embedded board as emitter</subtitle>
        <track>Free Software Radio</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Hellschreiber is a morse-like graphical transmission of digital data reminiscent of fax over wireless communication media designed in the 1930s and used during the second world war by the German military. Now used by the ham radio community, we consider how hellschreiber is emitted using a Raspberry Pi GPIO pin configured as radiofrequency emitter, an approach made popular by rpitx and generalized to GNU Radio with our gr-rpitx OOT sink block (https://github.com/jmfriedt/gr-rpitx). The transmitted signal is recorded by a RTL-SDR DVB-T receiver and decoded using gr-hellschreiber (https://github.com/tlavarenne/gr-hellschreiber).
Preparing this presentation was an opportunity to become familiar with GNU Radio 3.9 and the presentation concludes with some of the challenges (and solutions) met when porting gr-acars
(https://sourceforge.net/projects/gr-acars/) to this new version of the signal processing framework.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1813">Jean-Michel Friedt,  Thomas Lavarenne</person>
        </persons>
        <attachments>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/radio_hellschreiber/attachments/other/4794/export/events/attachments/radio_hellschreiber/other/4794/fosdem2022.png">full image of the experimental setup</attachment>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/radio_hellschreiber/attachments/paper/4819/export/events/attachments/radio_hellschreiber/paper/4819/QEX_jmfriedt.pdf">proceeding manuscript</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/radio_hellschreiber/attachments/slides/4827/export/events/attachments/radio_hellschreiber/slides/4827/fosdem2022.pdf">slides of the presentation</attachment>
        </attachments>
        <links>
          <link href="https://www.youtube.com/watch?v=Yb5VEgKdnAk">short video of a demonstration</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_hellschreiber.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_hellschreiber.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#radio-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-radio_hellschreiber:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#radio-radio_hellschreiber:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12355.php">Submit feedback</link>
        </links>
      </event>
      <event id="12977">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.radio</room>
        <slug>radio_ofdmradar</slug>
        <title>gr-ofdmradar: OFDM Radar in GNU Radio</title>
        <subtitle/>
        <track>Free Software Radio</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;All radar is dominated by high-bandwidth, fixed waveforms.  All radar? No! A little domain combines communications and sensing, introducing OFDM Radar:&lt;/p&gt;

&lt;p&gt;gr-ofdmradar is a GNU Radio out of tree (OOT) module, providing an OFDM Radar implementation that can be used in simulations and, potentially, hardware. In this talk I will introduce the motivations and theory behind OFDM Radar as described by Martin Braun, present gr-ofdmradar and how it can be used in simulations and conclude with a small outlook at how this module can be used for hardware implementations.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8668">David Winter</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/analogdevicesinc/gr-ofdmradar">GitHub: gr-ofdmradar</link>
          <link href="https://wiki.analog.com/resources/eval/user-guides/ad9081_fmca_ebz/radar">Hardware Implementation of OFDM Radar using gr-ofdmradar</link>
          <link href="https://publikationen.bibliothek.kit.edu/1000038892">Martin Braun, OFDM Radar Algorithms in Mobile Communication Networks</link>
          <link href="https://www.youtube.com/watch?v=gtTILs929aU">[YouTube] Recording of unprocessed radar return in hardware setup</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_ofdmradar.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_ofdmradar.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#radio-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-radio_ofdmradar:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#radio-radio_ofdmradar:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12977.php">Submit feedback</link>
        </links>
      </event>
      <event id="12443">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.radio</room>
        <slug>radio_voyager1</slug>
        <title>Voyager 1 adventures</title>
        <subtitle/>
        <track>Free Software Radio</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Voyager 1 is the furthest spacecraft and the first ever to exit the solar system. Fueled by its radioisotope generators, after more than 40 years of flight it is still sending us data about the interstellar medium using its 3.7 metre dish antenna and 8.4 GHz transmitter. In this talk we report two adventures regarding the reception of the Voyager 1 signal.&lt;/p&gt;

&lt;p&gt;In the first part, we show the successful detection of the Voyager 1 signal using one of the 6.1 metre dishes at the Allen Telescope Array in November 2020. Calculations show that using stable frequency references and accurate Doppler correction, this feat might also be possible for amateurs with smaller dishes if they integrate several hours of data to pull out the very weak signal from the noise. In the second part, we use some recordings done by the 100 metre Green Bank Telescope in 2015 and 2020 to decode the data transmitted by Voyager 1. The spacecraft predates the modern CCSDS standards, so its data has some interesting aspects.&lt;/p&gt;

&lt;p&gt;All this work has been done using GNU Radio, Python, and other open source tools. The data and results are publicly available.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7088">Daniel Estévez</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/radio_voyager1/attachments/slides/5233/export/events/attachments/radio_voyager1/slides/5233/destevez_fosdem2022.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.radio/radio_voyager1.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_voyager1.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#radio-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-radio_voyager1:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#radio-radio_voyager1:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12443.php">Submit feedback</link>
        </links>
      </event>
      <event id="13516">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.radio</room>
        <slug>radio_gr3_10</slug>
        <title>GR 3.10 </title>
        <subtitle>Update and examples of new features</subtitle>
        <track>Free Software Radio</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;3.10 is the latest release of GNU Radio and includes some powerful features and new modules.  We will step through the new features and what they enable before going further in depth with some examples of the upstreamed  Hardware Accelerator Support that was presented last year at FOSDEM.  This feature provides streamlined data movement via support of "custom buffers" which allow a device-compatible mapping of the memory presented to a block's work function, eliminating additional ingress/egress in and out of device memory.  We will show how this impacts specifically flowgraphs that have CUDA enabled blocks as a concrete example.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7100">Josh Morman</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/radio_gr3_10/attachments/slides/4996/export/events/attachments/radio_gr3_10/slides/4996/GR_3_10_FOSDEM_2022.pdf">GR 3.10 Update Slides v2</attachment>
        </attachments>
        <links>
          <link href="https://www.gnuradio.org/">GNU Radio project website</link>
          <link href="https://github.com/gnuradio/gnuradio">GNU Radio project repository</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_gr3_10.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_gr3_10.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#radio-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-radio_gr3_10:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#radio-radio_gr3_10:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13516.php">Submit feedback</link>
        </links>
      </event>
      <event id="13521">
        <start>16:00</start>
        <duration>00:10</duration>
        <room>D.radio</room>
        <slug>radio_m17</slug>
        <title>Introducing the M17 Project</title>
        <subtitle/>
        <track>Free Software Radio</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A six minute talk on the M17 Project, an open source digital communications protocol suitable for VHF/UHF and more. Intended for amateur radio terrestrial and space application, many exciting things are possible with this 4-ary FSK layered protocol from a dynamic and motivated international team. This talk will introduce the audience to the project and the purpose, goals, products, opportunities, and enjoyment possible with M17. M17 is not encumbered by US patents.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8934">Michelle Thompson</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://m17project.org/">M17 Project Homepage</link>
          <link href="https://openrtx.org">OpenRTX FOSS Firmware Homepage</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_m17.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_m17.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#radio-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-radio_m17:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#radio-radio_m17:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13521.php">Submit feedback</link>
        </links>
      </event>
      <event id="13522">
        <start>16:10</start>
        <duration>00:30</duration>
        <room>D.radio</room>
        <slug>radio_julia_litex</slug>
        <title>P2P SDR to GPU Streaming with Julia and LiteX</title>
        <subtitle>High throughput PCIe P2P communication for SDR</subtitle>
        <track>Free Software Radio</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk, we report early results in the development of a hardware/software stack enabling direct P2P communication between a Fairwaves XTRX / XYNC SDR and an Nvidia GPU. We are able to saturate a PCIe link (7 Gbps) in loopback mode. IQ samples are streamed from the RF IC at more than 350 Mbps. Implementation of this architecture required the development of a new LiteX-based Artix FPGA gateware, and a new SDR framework written in the Julia programming language. The combination of extremely high throughput, GPU computing power, and efficient Julia code will open the doors to a new generation of phased-array and machine-learning experimentation.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8927">Steve Kelly</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.radio/radio_julia_litex.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.radio/radio_julia_litex.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#radio-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#radio-radio_julia_litex:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#radio-radio_julia_litex:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13522.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.openjdk">
      <event id="12786">
        <start>10:00</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>diversity</slug>
        <title>Fundamentals Of Diversity &amp; Inclusion For Technologists</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Enhancing diversity and inclusion in every aspect of technology is an essential conversation everyone should be a part of. In an increasingly interconnected world, we have a shared responsibility to ensure technology is a force that works to benefit everyone, countering structural sources of inequity where needed.&lt;/p&gt;

&lt;p&gt;This session aims to jump start your personal diversity and inclusion journey by explaining the basics in simple terms with relevant examples for technologists. Concepts covered will include unconscious bias, privilege, equity, allyship, covering and microaggressions.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7863">Reza Rahman</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/diversity.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/diversity.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-diversity:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-diversity:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12786.php">Submit feedback</link>
        </links>
      </event>
      <event id="13000">
        <start>10:40</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>openjfx</slug>
        <title>OpenJFX: An Update on Java on the Client</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;JavaFX allows Java developers to create cross-platform user interfaces using their existing Java skills.&lt;/p&gt;

&lt;p&gt;In this session, we give an update about the OpenJFX project where the core development of JavaFX is happening.&lt;/p&gt;</abstract>
        <description>&lt;ul&gt;
&lt;li&gt;&lt;p&gt;OpenJFX: development in the open. The specification and implementation is done in a very open, community-friendly approach on GitHub. Topics are discussed on a mailinglist, and issues can be created in the Java Bug System.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Cross Platform: the same Java code that is used to create a user interface on desktop (windows/mac/linux) works on mobile (android/ios) and embedded devices as well. This also allows for a convenient development cycle: development and debugging is typically done using the developers favorite platform and IDE, and the result will work on other systems as well.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Modern graphical stack: the low-level implementations are shielded from the high-level JavaFX API's. This allows JavaFX implementations to take advantage of modern hardware and drivers, and developers don't have to worry about these implementation details.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="6274">Johan Vos</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/openjfx.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/openjfx.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-openjfx:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-openjfx:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13000.php">Submit feedback</link>
        </links>
      </event>
      <event id="12350">
        <start>11:20</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>fxgl</slug>
        <title>AI Pathfinding In FXGL Game Engine</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;FXGL 11 has been a success among JavaFX developers, leveraging high-performance cross-platform support for games and applications. FXGL seamlessly extends JavaFX to bring support for real-world game and application development concepts and techniques, which can be used in both Java and Kotlin.&lt;/p&gt;

&lt;p&gt;In this session, developers will dive deeper into the FXGL AI capabilities and learn how to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;create a 2D navigation grid from a game level,&lt;/li&gt;
&lt;li&gt;use A* pathfinding with game objects.&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="7949">Almas Baimagambetov</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/AlmasB/FXGL">FXGL game engine source</link>
          <link href="https://github.com/AlmasB/FOSDEM22-FXGL">Workshop source</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/fxgl.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/fxgl.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-fxgl:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-fxgl:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12350.php">Submit feedback</link>
        </links>
      </event>
      <event id="12352">
        <start>12:00</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>pi</slug>
        <title>Update On Java On The Raspberry Pi</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;An overview of Java projects running on the Raspberry Pi.&lt;/p&gt;

&lt;p&gt;In 2021 the Pi4J project released a completely new second version of its object-oriented GPIO API and implementation library for the Raspberry Pi. Let's take a look at the new documentation site and example projects to get you started with Java development on the Raspberry Pi.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Getting started with Java in a new area - like controlling electronic components - can be challenging, but the Pi4J project aims to make this an easy and fun experience. Thanks to a lot of getting-started tutorials and example projects, different use-cases are handled. The experience of your first "blinking LED" is a really amazing experience for a lot of software developers who never interfaced with electronics before. In this presentation, we will take a look at a few of these examples.&lt;/p&gt;</description>
        <persons>
          <person id="7598">Frank Delporte</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://pi4j.com/">Pi4J documentation website</link>
          <link href="https://webtechie.be/presentations/">Presentations by Frank Delporte</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/pi.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/pi.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-pi:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-pi:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12352.php">Submit feedback</link>
        </links>
      </event>
      <event id="13098">
        <start>12:40</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>mqtt</slug>
        <title>Benefits Of MQTT For IoT Apps And Beyond</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A quick study on several popular MQTT brokers!&lt;/p&gt;

&lt;p&gt;We will learn about the benefits of MQTT, which has become the de facto standard for IoT messaging.  The MQTT protocol has in fact undergone a major transformation from its early days as a protocol for handling data transmission in oil pipelines via satellite, to now being able to manage devices operating in the current internet and cloud native environments that are often constrained.  We'll take a look at some of the popular implementations of the MQTT broker, such as the Java-based HiveMQ  and the C/C++ Eclipse Mosquitto.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;IoT applications run on IoT devices and can be created to be specific to almost every industry and vertical, from small devices to large ones, including healthcare, industrial automation, smart homes and buildings, automotive, and wearable technology. The possibilities are limitless. Increasingly, IoT applications are using AI and machine learning to add intelligence to devices. Among all of the variables in the IoT ecosystem, one common theme is the need to be able to handle the constrained operating environment, such as unreliable network connectivity, limited bandwidth, low battery power, and so on. We will take a look into the MQTT protocol, how it has evolved from its early days which was intended for the connection of oil pipelines via satellite, to now the ever-increasing demand in IoT and M2M applications, to how this protocol will evolve to meet the modern needs especially in the current cloud computing era. We will study a few outstanding MQTT libraries that are available in the market, such as the Java-based HiveMQ, and open source libraries such as Eclipse Mosquitto and Apache licensed VerneMQ.&lt;/p&gt;</description>
        <persons>
          <person id="5562">Mary Grygleski</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/mqtt.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/mqtt.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-mqtt:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-mqtt:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13098.php">Submit feedback</link>
        </links>
      </event>
      <event id="12781">
        <start>13:20</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>jakartaee</slug>
        <title>Jakarta EE: Present &amp; Future</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Java EE has been re-branded to Jakarta EE and moved to truly open source governance under the Eclipse Foundation. This session overviews what this means, offers a brief tour of the initial releases - Jakarta EE 8/Jakarta EE 9, explores current state and looks to what the future might bring including some key challenges. We will also discuss how these challenges can be overcome through active community engagement.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The technical contents of Jakarta EE 8 is mostly the same as Java EE 8. Jakarta EE 9 further brings the platform into the open by decoupling from the javax namespace to the jakarta namespace. Jakarta EE 10 opens the possibilities for many long pending innovations in key technologies like Jakarta Security, Concurrency, Messaging, REST, Persistence, Batch, NoSQL, MVC and Configuration.&lt;/p&gt;

&lt;p&gt;You should come to this session with your thinking caps on and your sleeves rolled up. There is much to help move forward together that really matters.&lt;/p&gt;</description>
        <persons>
          <person id="7863">Reza Rahman</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/jakartaee.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/jakartaee.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-jakartaee:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-jakartaee:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12781.php">Submit feedback</link>
        </links>
      </event>
      <event id="12911">
        <start>14:00</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>deeplearning</slug>
        <title>Deep Learning for Java Developers</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;For most software developers, mastering AI/machine learning can take months or even years.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Also, there are many technical challenges with integration and putting AI models in production.&lt;/p&gt;

&lt;p&gt;Deep Netts is a Java native Deep Learning Toolkit that solves these problems for Java developers.&lt;/p&gt;

&lt;p&gt;In this session, you will learn how to quickly create more powerful Java applications with AI/Machine Learning by using your Java skills.&lt;/p&gt;</description>
        <persons>
          <person id="7839">Zoran Sevarac</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/deeplearning.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/deeplearning.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-deeplearning:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-deeplearning:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12911.php">Submit feedback</link>
        </links>
      </event>
      <event id="12901">
        <start>14:40</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>maven</slug>
        <title>Faster Apache Maven Builds</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Builds require a few properties, chief among them reproducibility. I would consider speed to be low on the order of priorities. However, it’s also one of the most limiting factors to your release cycle: if your build takes T, you cannot release faster than each T. Hence, you’ll probably want to speed up your builds after you’ve reached a certain maturity level to enable more frequent releases.&lt;/p&gt;

&lt;p&gt;I want to detail some techniques you can leverage to make your Maven builds faster.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5584">Nicolas Frankel</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/maven.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/maven.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-maven:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-maven:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12901.php">Submit feedback</link>
        </links>
      </event>
      <event id="12789">
        <start>15:20</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>vaadin</slug>
        <title>Modern Web Apps, 100% Java: Building Web Apps With Vaadin</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;If you're like most people, the words "Java web app" may conjure up memories of ancient Applets or make you think of multi-page apps built with JSPs or Spring MVC with a "little" jQuery sprinkled in for interactivity.&lt;/p&gt;

&lt;p&gt;In this presentation, we'll take a look at a radically different approach to building web apps in Java.&lt;/p&gt;

&lt;p&gt;Vaadin Flow is a unique web framework that lets you build apps in plain Java using an extensive library of included UI components. The resulting app is a highly-interactive single-page app based on the latest web technologies.&lt;/p&gt;

&lt;p&gt;You'll learn the basics of building apps using this open-source framework and be ready to start turning your idea into an app.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8739">Marcus Hellberg</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/vaadin.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/vaadin.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-vaadin:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-vaadin:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12789.php">Submit feedback</link>
        </links>
      </event>
      <event id="12562">
        <start>16:00</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>debugger</slug>
        <title>Polyglot Cloud Native Debugger: Going Beyond APM</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;It's 2022 and we still use logs to debug production issues?&lt;/p&gt;

&lt;p&gt;All the unit tests in the world, the largest QA team still can’t stop bugs from slithering into production. With a distributed microservice architecture debugging becomes much harder. Especially across language &amp;amp; machine boundaries. APMs/Logs have limits. There’s a new generation of tools in town…&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Production bugs are the WORST bugs. They got through unit tests, integration tests, QA and staging… They are the spores of software engineering. Yet the only tools most of us use to attack that vermin is quaint little log files and APMs. We cross our fingers and put on the Sherlock Holmes hat hoping that maybe that bug has somehow made it into the log… When it isn’t there our only remedy is guesswork of more logging (which bogs performance for everyone and makes the logs damn near unreadable). But we have no choice other than crossing our fingers and going through CI/CD again.&lt;/p&gt;

&lt;p&gt;This is 2021. There are better ways. With modern debugging tools we can follow a specific process as it goes through several different microservices and “step into” as if we were using a local debugger without interrupting the server flow. Magic is possible.&lt;/p&gt;</description>
        <persons>
          <person id="8631">Shai Almog</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/debugger.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/debugger.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-debugger:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-debugger:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12562.php">Submit feedback</link>
        </links>
      </event>
      <event id="12388">
        <start>16:40</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>jreleaser</slug>
        <title>Releasing  Fast, Easy, and Consistently</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;When a  project has reached that stage when it’s a good idea to post binaries,  new questions arise such as where should they be posted? How do make it easier for users to install and discover binaries? Where should releases be shared? Most importantly,  can it be automated?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;There are so many requirements and considerations depending on the  distribution channels, wouldn't be great to have a tool to make it easier?  JReleaser is a tool that provides answers to these questions and more., it may be used to create GiHub/GitLab/Gitea releases and publish binaries that can be consumed from different distribution channels such as Homebrew, Snap, Scoop, and more. Once published, the release cab be automatically announced on Twitter, Slack, Gitter, Discord, and other communication channels.&lt;/p&gt;</description>
        <persons>
          <person id="8512">Ixchel Ruiz</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/jreleaser.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/jreleaser.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-jreleaser:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-jreleaser:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12388.php">Submit feedback</link>
        </links>
      </event>
      <event id="12918">
        <start>17:20</start>
        <duration>00:40</duration>
        <room>D.openjdk</room>
        <slug>process</slug>
        <title>An Infallible Process to Fix Production Java Apps</title>
        <subtitle/>
        <track>Friends of OpenJDK</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Your production Java application stops working. An angry customer is waiting for a fix. Your boss is on the line asking what's going on...&lt;/p&gt;

&lt;p&gt;We have all been there. In such situations solving problems quickly makes you trusted and shows your maturity as a developer. That's what being a senior developer looks like.&lt;/p&gt;

&lt;p&gt;This presentation will guide you through a little-known infallible process used by the top Java experts that can get you out of very hard situations!  Troubleshoot any problem in your Java applications by using free and open-source tools available in the JDK -- jps, jinfo, jmap, jstack, jcmd, jhsdb, and jdb.&lt;/p&gt;

&lt;p&gt;Be the go-to person in your team to solve hard problems! Understand the common problems professional Java developers face and how to diagnose and solve them quickly.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7917">Vipin Sharma</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.openjdk/process.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.openjdk/process.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#openjdk-process:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#openjdk-process:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12918.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.geospatial">
      <event id="12738">
        <start>10:30</start>
        <duration>00:50</duration>
        <room>D.geospatial</room>
        <slug>geospatial_jswebgl</slug>
        <title>Introducing a new JS+WebGL map library</title>
        <subtitle>Or «why neither Leaflet, OpenLayers nor MapLibreGL meet my needs»</subtitle>
        <track>Geospatial</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;When putting a map on the web, Leaflet, OpenLayers and MaplibreGL (formerly MapboxGL) are popular Javascript FLOSS libraries to do so. This talk will explore some of their features, architectures and shortcomings; and a brand new JS+WebGL library will be introduced, demoing some of its features.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8706">Iván Sánchez Ortega</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/geospatial_jswebgl/attachments/slides/4969/export/events/attachments/geospatial_jswebgl/slides/4969/introducing_gleo.odp">Introducing Gleo</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_jswebgl.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_jswebgl.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-geospatial_jswebgl:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-geospatial_jswebgl:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12738.php">Submit feedback</link>
        </links>
      </event>
      <event id="12528">
        <start>11:20</start>
        <duration>00:40</duration>
        <room>D.geospatial</room>
        <slug>geospatial_arlas</slug>
        <title>Explore OSM data with ARLAS</title>
        <subtitle>Get instant geo-analytic view of billions OSM data entries</subtitle>
        <track>Geospatial</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;ARLAS Exploration is geo-analytic solution based on big-data technologies. It helps users who have big volumes of spatio-temporal data, to explore it through analytics and geo-analytics views.&lt;/p&gt;

&lt;p&gt;In this devroom we will use ARLAS to explore OSM data with an Analytic perspective. We will go through the following steps:
- Download and index OSM data in a search engine (Elasticsearch) and make it available to exploration by ARLAS stack
- Configure ARLAS dashboards based on this data and create analytical and geo-analytical views&lt;/p&gt;

&lt;p&gt;We will be able to answer questions such as:
- How many buildings are in the downloaded dataset? And how are they distributed geographically ?
- What are the different existing types of buildings? With what proportions ?
- When this data has been created/edited and with what frequency ?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Gisaïa is a geospatial intelligence company based in France. Gisaïa developed ARLAS Exploration, and has built a robust geo-big data ecosystem to continuously update and run it. ARLAS Exploration is open-source and OGC compliant allowing users to integrate it with GIS platforms lending it to high interoperability. This promotes full access to all types of geospatial data.&lt;/p&gt;

&lt;p&gt;ARLAS Exploration is a powerful geoanalytics platform that developers can build on and data scientists can deploy immediately to go into the depths of their geo-big data. With this devroom, Gisaïa will provide a future-centric geoanalytics tool for participants to easily conduct geo-big data analytics.&lt;/p&gt;

&lt;p&gt;As an example, we will show how to use ARLAS with OSM data and get instantly Geo-analytic insights of it.&lt;/p&gt;</description>
        <persons>
          <person id="8609">Mohamed Hamou</person>
        </persons>
        <attachments>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/geospatial_arlas/attachments/other/4775/export/events/attachments/geospatial_arlas/other/4775/OSM_AGG.png">Geo-analytic view of OSM data using ARLAS</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/geospatial_arlas/attachments/other/4776/export/events/attachments/geospatial_arlas/other/4776/OSM_RAW.png">Raw OSM buildings viewed with ARLAS</attachment>
        </attachments>
        <links>
          <link href="https://docs.arlas.io/arlas-birdtracking-tutorial/">Tutorials of how to use ARLAS</link>
          <link href="https://github.com/gisaia/ARLAS-workshop/blob/master/explore_osm_data/tutorial.md">ARLAS-stack-OSM-tutorial</link>
          <link href="https://">https://</link>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_arlas.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_arlas.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-geospatial_arlas:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-geospatial_arlas:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12528.php">Submit feedback</link>
        </links>
      </event>
      <event id="12439">
        <start>12:00</start>
        <duration>00:30</duration>
        <room>D.geospatial</room>
        <slug>geospatial_digital</slug>
        <title>Open Geodata Digital Spaces</title>
        <subtitle>Exploring the digital spaces of OpenStreetMap</subtitle>
        <track>Geospatial</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Open Source Geotechnologies are developed using various socio-technical systems. Understanding of these systems can help us understand the genealogy of the data generation. There are various applications that transcend from the basic understanding of geospatial as technological systems. I am analyzing OpenStreetMap and trying to define its digital spaces to understand what forms of plurality exist in data production. Conceptualization of Digital spaces of OpenStreetMap is important in order to visualise how we can define ethical boundaries and to answer the underlying question of “what is quality?”. I am currently interviewing, sending out questionnaires to OpenStreetMap users and conducting texture analysis of previous conference talks related to OpenStreetMap. In this talk I would like to present my ongoing progress on the research project OSM Utopia and present the small part in which I would like to increase the support from different researchers and practitioners, which is conceptualizing OpenStreetMap digital spaces.
Furthermore, In this talk I explain how I planned to explore the interconnection and interdependence of analogue and digital spatiality of OSM and different research paradigms that needed to be explored. Also, will share the current progress on the way of defining digital spaces of OpenStreetMap and how we can categorise different analogues and digital assemblages that form these digital spaces. Limitations of these methods are also addressed. End goal that is targeted is that the data quality for OpenStreetMap requires a certain level of rethinking.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8526">Muhammad  Saleem</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/geospatial_digital/attachments/slides/4994/export/events/attachments/geospatial_digital/slides/4994/Presentation.pdf"/>
        </attachments>
        <links>
          <link href="https://youtu.be/HOi1n9OQ934">Connected project OSM Utopia</link>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_digital.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_digital.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-geospatial_digital:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-geospatial_digital:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12439.php">Submit feedback</link>
        </links>
      </event>
      <event id="12889">
        <start>12:30</start>
        <duration>00:45</duration>
        <room>D.geospatial</room>
        <slug>geospatial_fast</slug>
        <title>Fast, robust predicates for geometric algorithms</title>
        <subtitle>A C++ metaprogramming implementation of fast, robust floating-point arithmetics for geometric predicates</subtitle>
        <track>Geospatial</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Many algorithms, such as geospatial predicates or the construction of Delaunay Triangulations, make use of geometric predicates. Common examples of such predicates are orientation tests for 2D or 3D points. If these predicates are evaluated for floating-point coordinates, they can yield incorrect results due to round-off errors, which can cause algorithms to fail or to return invalid constructions. This talk presents a C++ template metaprogramming implementation of fast, robust floating-point predicates, which guarantee correct results without severe performance penalties.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8777">Tinko Sebastian Bartels</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/geospatial_fast/attachments/slides/5191/export/events/attachments/geospatial_fast/slides/5191/Slides.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_fast.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_fast.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-geospatial_fast:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-geospatial_fast:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12889.php">Submit feedback</link>
        </links>
      </event>
      <event id="12705">
        <start>13:15</start>
        <duration>00:25</duration>
        <room>D.geospatial</room>
        <slug>geospatial_transport</slug>
        <title>A Better Public Transport App</title>
        <subtitle/>
        <track>Geospatial</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk I show the app that I've made in two months while learning the Flutter framework. It was built on open data and open source libraries. But what separates it from the rest is not code - but experience. Maps on mobile screens are hard to do properly, and there's always a temptation to add another screen, another button. Turns out you need a bit more than skills to make a perfect app: at least you need to use it daily.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Last year I moved to Tallinn, Estonia, which is known also by it's public transport system - free for city residents. It is so good, reliable and optimized, that I sold my car and use buses and trams exclusively for all my city travels.&lt;/p&gt;

&lt;p&gt;While planning a transit route is pretty straightforward with an official website, usually I need some transit-related information on the go. On a phone. And that's where both the website and many big and small apps show their imperfections. Download sizes, ads, user interface. Instead of focusing on my problems, I have to learn and work around apps' issues.&lt;/p&gt;

&lt;p&gt;As an open source developer, that seemed not an issue - but a challenge. I've made interactive maps for the past ten years, and I know one should not use these libraries with default settings. Nor one should ever rely on zooming. Could I made a map with apps that doesn't require more than a couple of taps to get all the needed information? How hard would it be to keep number of buttons and other interactive elements to minimum, while not sacrificing functions I need every day?&lt;/p&gt;</description>
        <persons>
          <person id="3485">Ilya Zverev</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/Zverik/quick_bus">GitHub Repository</link>
          <link href="https://play.google.com/store/apps/details?id=info.zverev.ilya.quick_bus">Google Play Store</link>
          <link href="https://easytransit.app/">App Website</link>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_transport.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_transport.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-geospatial_transport:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-geospatial_transport:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12705.php">Submit feedback</link>
        </links>
      </event>
      <event id="12898">
        <start>13:40</start>
        <duration>00:35</duration>
        <room>D.geospatial</room>
        <slug>geospatial_grass</slug>
        <title>Spatial query of coordinate reference systems and its integration with GRASS GIS</title>
        <subtitle/>
        <track>Geospatial</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I introduce a new open-source geospatial project called ProjPicker (Projection Picker). ProjPicker is a Python module that allows the user to select all coordinate reference systems (CRSs) whose extent completely contains given points, polygons, and bounding boxes using set-theoretic logical operators in a postfix notation. The goal of this project is to make it easy and visual to select a desired projection by location. This project was motivated by a GRASS GIS feature request. A new GRASS GIS module g.projpicker that wraps around this project is already available. As part of its integration with GRASS GIS, this new feature will be added to the GRASS location wizard.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7868">Huidae Cho</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/HuidaeCho/projpicker">ProjPicker GitHub Repository</link>
          <link href="https://projpicker.readthedocs.io/">ProjPicker Documentation</link>
          <link href="https://projpicker.pythonanywhere.com/">ProjPicker Web</link>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_grass.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.geospatial/geospatial_grass.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#geospatial-geospatial_grass:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#geospatial-geospatial_grass:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12898.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.go">
    </room>
    <room name="D.graphics">
      <event id="12689">
        <start>10:00</start>
        <duration>00:45</duration>
        <room>D.graphics</room>
        <slug>lvgl</slug>
        <title>LVGL: A versatile UI toolkit for MCU &amp; CPU</title>
        <subtitle>An UI framework for Eclipse Oniro a cross kernel OS</subtitle>
        <track>Graphics</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;LVGL is an open-source graphics library to create embedded GUI.&lt;/p&gt;

&lt;p&gt;By its flexibility, this toolkit is well matching Oniro project's requirements to build a multiple kernel OS for IoT devices or enable interactions in a multiple devices environment.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;UI toolkits are well established in CPU world (desktop, mobile), but what about in more constrained system ?&lt;/p&gt;

&lt;p&gt;Often tied to one vendor, the choice is often limited. However OpenSource project LVGL provides everything developers need to create embedded GUI with easy-to-use graphical elements, beautiful visual effects and low memory footprint.&lt;/p&gt;

&lt;p&gt;This library is compact and flexible enough to be thread through a regular Linux system. Of course this will not compete with other popular frameworks like Qt or GTK, but it has some advantages worth sharing: where portability matters more than eye candy features.&lt;/p&gt;

&lt;p&gt;Oniro's Bitbake recipes enable makers to build products with user interface in a Yocto environment that can target different kernels or graphics systems.&lt;/p&gt;

&lt;p&gt;Oniro's blueprints will illustrate integration details to match a product requirement.&lt;/p&gt;

&lt;p&gt;Demos of vending machine (running on Linux+Wayland) or keypad (on Zephyr MCU OS) will be shown too.&lt;/p&gt;</description>
        <persons>
          <person id="1773">Philippe Coval</person>
          <person id="8905">Gabor Kiss-Vamosi</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lvgl/attachments/slides/5280/export/events/attachments/lvgl/slides/5280/oniro_lvgl_fosdem2022.pdf">oniro-lvgl-fosdem2022.pdf</attachment>
        </attachments>
        <links>
          <link href="https://lvgl.io">LVGL : Light and Versatile Graphics Library</link>
          <link href="https://github.com/lvgl/lvgl">LVGL Sources:</link>
          <link href="https://oniroproject.org/">Oniro: The Distributed Operating System That Connects Consumer Devices Big and Small</link>
          <link href="https://oniroproject.org/join-us/#fosdem2022">Join Eclipse's Oniro Project</link>
          <link href="https://rzr.github.io/rzr-presentations/docs/oniro-lvgl/">LVGL on Oniro FOSDEM2022 Presentations Slides (Web with videos) </link>
          <link href="https://video.fosdem.org/2022/D.graphics/lvgl.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.graphics/lvgl.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#graphics-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#graphics-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#graphics-lvgl:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#graphics-lvgl:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12689.php">Submit feedback</link>
        </links>
      </event>
      <event id="13053">
        <start>12:00</start>
        <duration>00:45</duration>
        <room>D.graphics</room>
        <slug>turnip</slug>
        <title>The status of turnip driver development.</title>
        <subtitle>What happened in 2021 and will happen in 2022 for turnip.</subtitle>
        <track>Graphics</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;ul&gt;
&lt;li&gt;Explain what turnip driver is about and who are working on it.&lt;/li&gt;
&lt;li&gt;Explain what is achieved in 2021 on turnip.&lt;/li&gt;
&lt;li&gt;Brief plan for turnip development for 2022.&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="8835">Hyunjun Ko</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/turnip/attachments/slides/5107/export/events/attachments/turnip/slides/5107/fosdem_zzoon_turnip_driver_status.pdf">The status of Turnip driver development</attachment>
        </attachments>
        <links>
          <link href="https://gitlab.freedesktop.org/mesa/mesa">https://gitlab.freedesktop.org/mesa/mesa</link>
          <link href="https://video.fosdem.org/2022/D.graphics/turnip.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.graphics/turnip.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#graphics-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#graphics-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#graphics-turnip:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#graphics-turnip:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13053.php">Submit feedback</link>
        </links>
      </event>
      <event id="12712">
        <start>13:00</start>
        <duration>01:00</duration>
        <room>D.graphics</room>
        <slug>v3dv</slug>
        <title>v3dv: Status Update for Open Source Vulkan Driver for Raspberry Pi 4</title>
        <subtitle/>
        <track>Graphics</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Igalia has been developing a new open source Mesa driver for the Raspberry Pi 4 since December 2019, and FOSDEM 2021 had a presentation with the status of the driver at that point. This talk will describe the current status of the driver, and discuss the improvements on the driver since last year presentation, focusing on all the work that was done to improve the driver performance, and a high level overview of the path that got the driver Vulkan 1.1 conformant. Finally, we will talk about future plans and how to contribute to the on-going development effort.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5180">Alejandro Piñeiro</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/v3dv/attachments/slides/5267/export/events/attachments/v3dv/slides/5267/v3dv_fosdem_2022">v3dv: Status Update for Open Source Vulkan Driver for Raspberry Pi 4</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.graphics/v3dv.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.graphics/v3dv.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#graphics-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#graphics-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#graphics-v3dv:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#graphics-v3dv:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12712.php">Submit feedback</link>
        </links>
      </event>
      <event id="13004">
        <start>15:00</start>
        <duration>00:45</duration>
        <room>D.graphics</room>
        <slug>vulkan_borders</slug>
        <title>Fun with border colors in Vulkan</title>
        <subtitle>An overview of the story behind VK_EXT_border_color_swizzle</subtitle>
        <track>Graphics</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The talk will give an overview of texel input operations according to the Vulkan specification text and how border colors, specified when creating Vulkan samplers, are supposed to fit in them. Then, the VK&lt;em&gt;EXT&lt;/em&gt;custom&lt;em&gt;border&lt;/em&gt;color extension will be explained together with the problems that were found in it thanks to Mesa's Zink OpenGL-on-Vulkan driver. This lead to the creation of the complementary VK&lt;em&gt;EXT&lt;/em&gt;border&lt;em&gt;color&lt;/em&gt;swizzle extension recently, which will be explained as well.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7693">Ricardo Garcia</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/vulkan_borders/attachments/slides/5072/export/events/attachments/vulkan_borders/slides/5072/fosdem_2022_vulkan_border_colors.pdf">Fun with border colors in Vulkan</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.graphics/vulkan_borders.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.graphics/vulkan_borders.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#graphics-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#graphics-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#graphics-vulkan_borders:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#graphics-vulkan_borders:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13004.php">Submit feedback</link>
        </links>
      </event>
      <event id="12732">
        <start>16:00</start>
        <duration>01:00</duration>
        <room>D.graphics</room>
        <slug>dmabuffeedback</slug>
        <title>Optimal buffer allocation on Wayland</title>
        <subtitle>linux-dmabuf feedback</subtitle>
        <track>Graphics</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Wayland compositors try to make of most of the hardware by displaying directly without any copy pixel buffers coming from clients such as games, browsers and video players. This lowers battery usage, improves latency and leaves the 3D engine free for clients to use. The display engines found in modern GPUs often can support this zero-copy mechanism only if the buffers have been allocated in a special fashion. However, buffers allocated this way won't be optimal for rendering, and only a handful of buffers can be directly displayed.&lt;/p&gt;

&lt;p&gt;As a result, a trade-off between zero-copy display and optimal rendering needs to be made. The compositor is the natural place where a decision can be made, because it has a global view of all apps which need to be presented. Once the compositor has taken a decision, it needs to be communicated to the clients. The brand new linux-dmabuf feedback protocol enables this negotiation between the compositor and the clients.&lt;/p&gt;

&lt;p&gt;If you're up for some window system integration madness, grab some popcorn and come enjoy the show!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6347">Simon Ser</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://fs.emersion.fr/protected/presentations/present.html?src=dmabuf-feedback-fosdem/index.md#1">Slides</link>
          <link href="https://video.fosdem.org/2022/D.graphics/dmabuffeedback.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.graphics/dmabuffeedback.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#graphics-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#graphics-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#graphics-dmabuffeedback:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#graphics-dmabuffeedback:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12732.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.trusted-hardware">
    </room>
    <room name="D.hpc">
      <event id="12851">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>big_data_police_crime</slug>
        <title>HPC for Social &amp; Crime Science</title>
        <subtitle>Big Data in Police and Crime Research</subtitle>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Many scientific disciplines have benefitted from the availability of big datasets to develop algorithm supported solutions. Recently, this trend has penetrated the fields of crime and police research. The presentation highlights use cases of big data computation and HPC for typical datasets in crime science: crime records, emergency call data, and police GPS data. The focus lies on spatiotemporal applications (i.e., geocoding, map matching, spatial and temporal algorithms). The datasets come from a collaborative project with a Belgian police force and encompass approximately 200,000 crime records and 400 million individual GPS datapoints (x and y coordinates + timestamp). The project aims at establishing the crime preventive effect of police patrols through a longitudinal research design. Besides offering novel computational solutions for crime scientist, these kinds of datasets introduce important ethical considerations as well as potential biases in human-led data entry and collection. These considerations underline the need for social scientists to become more literate in the computational sciences and support the framework of ‘crime science’ as a discipline of exact methods and data sources.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Many scientific disciplines have benefitted from the availability of big datasets to develop algorithm supported solutions. Recently, this trend has penetrated the fields of crime and police research. The presentation highlights use cases of big data computation and HPC for typical datasets in crime science: crime records, emergency call data, and police GPS data. The focus lies on spatiotemporal applications (i.e., geocoding, map matching, spatial and temporal algorithms). The datasets come from a collaborative project with a Belgian police force and encompass approximately 200,000 crime records and 400 million individual GPS datapoints (x and y coordinates + timestamp). The project aims at establishing the crime preventive effect of police patrols through a longitudinal research design. Besides offering novel computational solutions for crime scientist, these kinds of datasets introduce important ethical considerations as well as potential biases in human-led data entry and collection. These considerations underline the need for social scientists to become more literate in the computational sciences and support the framework of ‘crime science’ as a discipline of exact methods and data sources.&lt;/p&gt;</description>
        <persons>
          <person id="8764">Philipp M. Dau</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/big_data_police_crime/attachments/slides/4929/export/events/attachments/big_data_police_crime/slides/4929/Slides">HPC_DEV_CRI_SLIDES</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.hpc/big_data_police_crime.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/big_data_police_crime.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-big_data_police_crime:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-big_data_police_crime:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12851.php">Submit feedback</link>
        </links>
      </event>
      <event id="12774">
        <start>10:30</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>scip_scalable_cytometry_image_processing_dask</slug>
        <title>SCIP: scalable cytometry image processing using Dask in a high performance computing environment</title>
        <subtitle>A software for distributed processing of bioimaging datasets</subtitle>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Bioimage analysis is the process of extracting novel insights from microscopy images of tissues, cells or other biological entities. Many tools, such as ImageJ, QuPath or CellProfiler are heavily used by researchers to quantitatively interpret those complex images. These tools perform tasks such as normalization, image segmentation, image masking or feature extraction. However, these tools are designed for usage on local workstations with a GUI and for the most part only allow vertical scaling to deal with an increase in dataset size. This limited scalability poses a problem as bioimaging datasets keep growing in volume.&lt;/p&gt;

&lt;p&gt;Here, we introduce Scalable Cytometry Image Processing (SCIP). SCIP is an open-source tool that implements single-cell bioimage processing on top of Dask, a framework for distributed computing written in Python. By utilizing Dask to execute all computations, scalability is integral to the software allowing it to be executed on high performance computing clusters. Dask's smart task scheduling ensures computational resources are used efficiently. SCIP also takes advantage of Dask features such as fault tolerance, load balancing or data locality. This allows SCIP to process large datasets more efficiently and more robustly compared to other tools.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;SCIP was written in Python, and all code is freely available. It can run in local (single-node) or distributed mode. In the latter, Dask's components communicate efficiently using the MPI standard. SCIP can be used as a stand-alone command line tool, or integrated into existing Python scripts using the API.&lt;/p&gt;

&lt;p&gt;For a similar setup, SCIP showed a 4-fold decrease in runtime compared to CellProfiler. SCIP needed considerably less manual work to prepare the dataset for processing thanks to more efficient data input. Comparisons were executed on the Flemish Supercomputer Center Tier-1 high performance cluster. We processed two cytometry datasets containing images of human blood cells: an imaging flow cytometry dataset containing 270,000 6-channel images of 90 by 90 pixels, and a confocal microscopy dataset containing 869 5-channel images of 1600 by 900 pixels.&lt;/p&gt;

&lt;p&gt;The imaging flow cytometry dataset is processed by SCIP in 484 seconds using 80 workers running on 3 compute nodes. Each node has 24 cores (Intel Xeon E5-2680v4 @ 2.4GHz) and 120GB of memory, which is divided over the workers.&lt;/p&gt;

&lt;p&gt;The microscopy dataset is processed by SCIP in 2187 seconds using 16 workers running on 1 compute node. This node has 32 cores (Intel Xeon Silver 4110 CPU @ 2.10GHz) and 364GB memory, which is divided over the workers. This workflow also uses a GPU (Nvidia GeForce RTX 3090) for identifying the cells in the microscopy images.&lt;/p&gt;</description>
        <persons>
          <person id="8736">Maxim Lippeveld</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/scip_scalable_cytometry_image_processing_dask/attachments/slides/4928/export/events/attachments/scip_scalable_cytometry_image_processing_dask/slides/4928/SCIP_for_FOSDEM_22.pdf">Video slide deck</attachment>
        </attachments>
        <links>
          <link href="https://github.com/ScalableCytometryImageProcessing/SCIP">Github repository</link>
          <link href="https://video.fosdem.org/2022/D.hpc/scip_scalable_cytometry_image_processing_dask.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/scip_scalable_cytometry_image_processing_dask.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-scip_scalable_cytometry_image_processing_dask:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-scip_scalable_cytometry_image_processing_dask:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12774.php">Submit feedback</link>
        </links>
      </event>
      <event id="12751">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>distributed_join_cratedb</slug>
        <title>Distributed Join Algorithms in CrateDB</title>
        <subtitle>How We Made Distributed Joins 23 Thousand Times Faster</subtitle>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Join operator is one of the standard operations available in relational databases. In a large-scale distributed scenario, efficiently implementing joins poses unique challenges as the data is usually spread around a cluster of machines instead of stored on a single machine. The goal of this talk is to illustrate the approach to implementing distributed joins in the CrateDB database that exhibits significant performance improvements compared to the existing algorithms. In the first part of the talk, we will cover the limitations of the nested loop and block nested loop join algorithms. The second part will show how the hash algorithm can work in distributed settings by addressing some of its memory limitations. Finally, we will introduce the distributed block hash join algorithm and how it enables CrateDB to analyze massive amounts of data 23 thousand times faster compared to the initial nested loop implementation.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In relational databases, join operators are usually implemented with nested or block nested loop algorithms. However, in a large-scale distributed scenario, the ability to efficiently query massive amounts of data can be challenging. Traditional approaches in implementations of join operators are no longer enough to achieve the high performance of complex joins in distributed data processing systems. For instance, a nested loop algorithm is relatively simple to implement and could be easily adjusted to execute distributed joins. Unfortunately,  it comes with a high-performance cost that equals quadratic time complexity with respect to the number of rows of the two tables joined.&lt;/p&gt;

&lt;p&gt;This talk will show our approach to implementing distributed equi-join operator in CrateDB that exhibits significant performance improvements compared to the original nested loop algorithm. CrateDB is an open-source, distributed SQL database that runs queries on millions of data records daily. It scales up to hundreds of nodes and PBs of indexed data making the performance of join operators highly important: it is required to have efficient algorithms that can scale with the input size.&lt;/p&gt;

&lt;p&gt;More specifically, we explore the implementation of the distributed block hash join algorithm. First, we address the memory limitations of the basic hash join algorithm with a switch to block-based processing. Block-based processing refers to a procedure of dividing a large dataset up into smaller blocks that can be worked on separately. As those blocks can be distributed across the CrateDB cluster the join can be executed in parallel using multiple nodes for increased performance and load distribution. Second, we illustrate the changes in the single node block hash join algorithm to enable its distributed execution.&lt;/p&gt;

&lt;p&gt;To evaluate the performance of distributed block hash join algorithm, we run CrateDB benchmarks against two algorithms: the original nested loop algorithm and the single node block hash join algorithm. The benchmark consists of queries with join operators and runs on tables of various sizes, up to 50 million rows. The final result illustrates that the distributed block hash join algorithm enables CrateDB to analyze massive amounts of data 23 thousand times faster than the initial nested loop implementation.&lt;/p&gt;</description>
        <persons>
          <person id="8537">Marija Selakovic</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/distributed_join_cratedb/attachments/slides/5171/export/events/attachments/distributed_join_cratedb/slides/5171/Distributed_Join_Algorithms_in_CrateDB"/>
        </attachments>
        <links>
          <link href="https://github.com/crate/crate">CrateDB source code</link>
          <link href="https://video.fosdem.org/2022/D.hpc/distributed_join_cratedb.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/distributed_join_cratedb.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-distributed_join_cratedb:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-distributed_join_cratedb:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12751.php">Submit feedback</link>
        </links>
      </event>
      <event id="12398">
        <start>11:30</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>multidimensional_bloom_filters</slug>
        <title>Multidimensional Bloom Filters</title>
        <subtitle>A Survey of What, When, Why</subtitle>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Claude Warren will present an overview of his recent work to implementing multidimensional Bloom filters.  This talk will focus on the implementation of the multidimensional Bloom filters, their current use in modern software, and how they are applicable as a multi-column index, an index into large document collections, or an index to encrypted data.  The talk will briefly describe Bloom filters and their construction before discussing strategies for the management of multiple Bloom filters; also known as multidimensional Bloom filters.  Data from a comparative analysis of several multidimensional Bloom filter strategies will be presented along with discussion of when to select one implementation over another.&lt;/p&gt;

&lt;p&gt;All source code referenced is under the Apache 2 or similar open source license and is available on Github.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3098">Claude Warren</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/multidimensional_bloom_filters/attachments/slides/4913/export/events/attachments/multidimensional_bloom_filters/slides/4913/Multidimensional_Bloom_Filters.pdf">Multidimensional Bloom Filters</attachment>
        </attachments>
        <links>
          <link href="https://github.com/Claude-at-Instaclustr/blooming_cassandra">Cassandra Index Code</link>
          <link href="https://github.com/Claudenw/commons-collections">Proposed commons-collectons4 Bloom filter code</link>
          <link href="https://github.com/Claudenw/BloomTest">Multidimensional Bloom filter evaluation suite</link>
          <link href="https://video.fosdem.org/2022/D.hpc/multidimensional_bloom_filters.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/multidimensional_bloom_filters.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-multidimensional_bloom_filters:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-multidimensional_bloom_filters:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12398.php">Submit feedback</link>
        </links>
      </event>
      <event id="12649">
        <start>12:00</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>utilizing_amd_gpus</slug>
        <title>Utilizing AMD GPUs: Tuning, programming models, and roadmap</title>
        <subtitle/>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;During FOSDEM 2021, we presented in the same event the LUMI supercomputer and we discussed about the Open Software Platform for GPU-accelerated Computing by AMD (ROCm) ecosystem, how to port CUDA codes to Heterogeneous Interface for Portability (HIP), and some performance results based on the utilization of NVIDIA V100 GPU. In this talk we assume the audience is familiar with the content of the previous presentation.
  One year later, we have executed many codes on AMD MI100 GPU, tuned the performance on various codes and benchmarks, utilized and tuned a few programming models such as HIP, OpenMP offloading, Kokkos, and hipSYCL on AMD MI100 and compared their performance additionally with NVIDIA V100 and NVIDIA A100 (including CUDA). Furthermore, a new open source software is released by AMD, called GPUFort, to port Fortran+CUDA/OpenACC codes to Fortran+HIP for AMD GPUs. In this talk we present what we learned through our experience, how we tune the codes for MI100, how we expect to tune them in the future for LUMI GPU, the AMD MI250X, compare the previously mentioned programming models on some kernels across the GPUs, present a performance comparison for single precision benchmark, discuss the updated software roadmap, and a brief update for the porting workflow.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7650">Georgios Markomanolis</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/utilizing_amd_gpus/attachments/slides/5163/export/events/attachments/utilizing_amd_gpus/slides/5163/fosdem22_hpc_amd_gpus_markomanolis.pdf">Utilizing AMD GPUs: Tuning, programming models, and roadmap</attachment>
        </attachments>
        <links>
          <link href="https://github.com/ROCmSoftwarePlatform/gpufort">GPUFort</link>
          <link href="https://video.fosdem.org/2022/D.hpc/utilizing_amd_gpus.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/utilizing_amd_gpus.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-utilizing_amd_gpus:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-utilizing_amd_gpus:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12649.php">Submit feedback</link>
        </links>
      </event>
      <event id="12827">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>exascale_pmi</slug>
        <title>Exascale PMI on a heterogeneous sub-exascale Slurm cluster</title>
        <subtitle/>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;PMIx (Process Management Interface exascale) is a de-facto standard providing a very efficient interface to launch and control distributed tasks. It was created for exascale HPC systems, where launching a computational job can involve tens of thousands of nodes and bootstrapping MPI (Message Passing Interface) becomes cumbersome. PMIx reduces launch times in such systems from minutes to a few seconds.&lt;/p&gt;

&lt;p&gt;Even though the lower launch times are less critical in smaller clusters (but always welcome), the high efficiency of PMIx is also desirable at sub-exascale. The low data footprint and data exchange, as well as leveraging fast interconnects is useful on systems with lower-end network fabrics. Moreover, its tight integration with the resource manager is very helpful to minimize idling on clusters with limited resources.&lt;/p&gt;

&lt;p&gt;At VUB (Vrije Universiteit Brussel), we have recently transitioned our tier-2 HPC cluster to Slurm and enabled PMIx in a mixture of TCP and InfiniBand networks. We will share the lessons learned in the process and practical tips to deploy a reliable setup with open source software.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8752">Alex Domingo</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/exascale_pmi/attachments/slides/5189/export/events/attachments/exascale_pmi/slides/5189/FOSDEM22_DOMINGO_Exascale_PMI.pdf">Exascale PMI on a heterogeneous sub-exascale Slurm cluster</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.hpc/exascale_pmi.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/exascale_pmi.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-exascale_pmi:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-exascale_pmi:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12827.php">Submit feedback</link>
        </links>
      </event>
      <event id="12875">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>signal_processing_cupy</slug>
        <title>Porting Signal processing algorithms to CuPy for precision measurement</title>
        <subtitle/>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;At European Organization for Nuclear Research(CERN), for the alignment of large superconducting magnets and cryogenics, an interferometry based system is being devised to identify the position of their elements.
This technique uses interferometry principle and uses sweeping laser to identify the distance of multiple points using Fourier Analysis. The data acquired from photo-detection module, received after a sweep of laser source, needs to undergo sophisticated post processing to obtain the final results. The system must monitor position of a large number of elements every second. Dealing with 1000s of target points in less than 1 second required time-optimized and precise calculation. Thus, GPU was employed to provide faster and precise results. This required to use signal processing algorithms like: Butterworth Filter, Hilbert Transform, Savitzky-Golay smoothing Filter in GPU.
This talk will cover steps involved in adopting signal processing algorithm to GPU to achieve better performance and understand the effects of parallelism achieved. For the initial development, CuPy library for NVIDIA GPUs is used and later moved to implementation in C. CuPy provides wrapper for most of the CUDA toolkit in Python. We will also provide highlight about performance metrics with respect to increase in the data size and possible optimizations of its processing.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8774">Mamta Shukla</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/signal_processing_cupy/attachments/slides/5210/export/events/attachments/signal_processing_cupy/slides/5210/Signal_Processing_CuPy.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.hpc/signal_processing_cupy.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/signal_processing_cupy.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-signal_processing_cupy:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-signal_processing_cupy:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12875.php">Submit feedback</link>
        </links>
      </event>
      <event id="12841">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>pira_performance_instrumentation</slug>
        <title>PIRA: Performance Instrumentation Refinement Automation</title>
        <subtitle/>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;PIRA is a tool to automatically filter and focus Score-P's profiling to relevant program regions.
This involves both static, i.e., source-code feature, and dynamic, i.e., runtime information, analysis.
It uses the whole-program call-graph representation MetaCG for its analyses and has been used for automatic (a) hot-spot detection and refinement, (b) scalability analysis, (c) kernel identification, and (d) MPI load-imbalance detection.&lt;/p&gt;

&lt;p&gt;In this talk, we present an overview of MetaCG and PIRA together with its analyses and a focus on the most recent addition of automatic (MPI) load-imbalance detection.
Our experiments on the SPEC CPU 2006 suite show that PIRA automatically constructs overview measurements with runtime overhead &amp;lt; 10%.
For the load-imbalance detection, our experiments on MPI-parallel LULESH and the Ice-sheet and Sea-level System Model~(ISSM) show that PIRA keeps the runtime overhead below 15%, while correctly identifying the existing load imbalances.&lt;/p&gt;

&lt;p&gt;PIRA and MetaCG are available under BSD 3-clause license at https://github.com/tudasc/pira and https://github.com/tudasc/metacg.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7509">Jan-Patrick Lehr</person>
        </persons>
        <attachments>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/pira_performance_instrumentation/attachments/paper/4793/export/events/attachments/pira_performance_instrumentation/paper/4793/2022_PIRA_FOSDEM.pdf">PIRA - FOSDEM Abstract</attachment>
        </attachments>
        <links>
          <link href="https://github.com/tudasc/pira">PIRA Repository</link>
          <link href="https://github.com/tudasc/metacg">MetaCG Repository</link>
          <link href="https://video.fosdem.org/2022/D.hpc/pira_performance_instrumentation.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/pira_performance_instrumentation.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-pira_performance_instrumentation:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-pira_performance_instrumentation:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12841.php">Submit feedback</link>
        </links>
      </event>
      <event id="12480">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>woods_ood_generalization_benchmarks</slug>
        <title>WOODS</title>
        <subtitle>A set of Benchmarks for Out-of-Distribution Generalization in Time Series Tasks</subtitle>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In the last decade, the field of AI has seen a significant surge in capabilities in machine learning techniques. Nowadays, models with up to billions of parameters are trained for vast arrays of downstream tasks and obtain performance that defies what a lot considered possible 20 years ago. However, the reliance of machine learning models on the spurious correlations often prevents them from learning the intrinsic and invariant features of data, leading to their failure to generalize to Out-Of-Distribution (OOD) data. Understanding and overcoming these failures have led to a research program on OOD generalization.&lt;/p&gt;

&lt;p&gt;The field has been extensively explored in the static computer vision tasks (Domainbed, WILDS) but has been severely underexplored for time series tasks essential for multiple areas of applied machine learning, e.g., medical, finance, communication. We propose a set of new open source out-of-distribution generalization datasets for sequential prediction tasks spanning multiple modalities that act as benchmarks for potential algorithms that promote invariant learning. Along with the datasets, we provide a fair and systematic open-source platform for evaluating the performance of existing and potential algorithms on these datasets. We also provide a leaderboard that currently consists of popular algorithms' performance in the field of OOD generalization.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8558">Jean-Christophe Gagnon-Audet</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://woods-benchmarks.github.io/">Project page</link>
          <link href="https://github.com/jc-audet/WOODS">Github page</link>
          <link href="https://video.fosdem.org/2022/D.hpc/woods_ood_generalization_benchmarks.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/woods_ood_generalization_benchmarks.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-woods_ood_generalization_benchmarks:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-woods_ood_generalization_benchmarks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12480.php">Submit feedback</link>
        </links>
      </event>
      <event id="12876">
        <start>17:00</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>hpc_knowledge_base</slug>
        <title>Bringing together open source scientific software development for HPC and beginners</title>
        <subtitle/>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In the scope of the National Research Data Infrastructure Germany (NFDI) we develop and maintain a knowledge-base with guides and best practices about scientific software development – availabe at https://nfdi4ing.pages.rwth-aachen.de/knowledge-base/.&lt;/p&gt;

&lt;p&gt;With the knowledge-base we pursue the goal to make sustainable software development possible for everybody. Most importantly, we want to encourage people without strong computer science background to apply fundamental best practices, e.g., version control, from the start. We believe this is necessary since many engineers – and not computer scientists – write scientific code. Starting from version control, the topics range to fully automated experiments using CI/CD workflows. Many of the existing examples concern OpenFOAM development due to the knowledge-base’s heritage in TU Darmstadt’s CRC 1194. Since then, we also are working with the Lehrstuhl für Hydromechanik und Hydrosystemmodellierung (LH²) as well as with the Institute of Wasserbau and the Institute of Fluidsystemtechnik at TU Darmstadt.&lt;/p&gt;

&lt;p&gt;While curating the content, which we maintain in a Gitlab repository using the HUGO website generator, we realized that one of the most important additions that we provide is an actively maintained and simple glossary. Especially for people not yet very familiar with the technologies used, the pure number of terms can be intimidating and confusing. Our glossary helps by providing brief explanations of relevant terms used throughout the articles. An addition for which we modified the actual HUGO template is that we provide a taxonomy of articles rather than a pure folder structure to ease the navigation.&lt;/p&gt;

&lt;p&gt;The knowledge-base is an on-going effort in which we appreciate feedback and contributions. In the presentation, we will take a closer look on the different materials provided for people developing software, people using software, and how people can actively contribute to the knowledge base through our peer-review process and material creation.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7509">Jan-Patrick Lehr</person>
          <person id="8855">Moritz Schwarzmeier</person>
        </persons>
        <attachments>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/hpc_knowledge_base/attachments/paper/4796/export/events/attachments/hpc_knowledge_base/paper/4796/FOSDEM22_Abstract_01.pdf">NFDI4Ing Knowledge Base Abstract</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/hpc_knowledge_base/attachments/slides/5251/export/events/attachments/hpc_knowledge_base/slides/5251/FOSDEM22_KB.odp">Presentation Slides</attachment>
        </attachments>
        <links>
          <link href="https://nfdi4ing.pages.rwth-aachen.de/knowledge-base/">Knowledge Base presented in the talk</link>
          <link href="https://video.fosdem.org/2022/D.hpc/hpc_knowledge_base.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/hpc_knowledge_base.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-hpc_knowledge_base:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-hpc_knowledge_base:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12876.php">Submit feedback</link>
        </links>
      </event>
      <event id="12872">
        <start>17:30</start>
        <duration>00:30</duration>
        <room>D.hpc</room>
        <slug>open_source_hep</slug>
        <title>Open source tooling in High-Energy Physics Software</title>
        <subtitle/>
        <track>HPC, Big Data, and Data Science</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Particle physics experiments have often had a pioneering role in the use of open source software. In this talk we review the current scientific software ecosystem, with particular  emphasis on the tooling to  build and deploy the typical software stack of an experiment.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Particle colliders are powered by software, from the simulations supporting their design to the systems controlling the running experiment, and would not be feasible without organizing community efforts into open source projects like Geant4 (simulation of the passage of  particles through matter), ROOT (general I/O and analysis toolkit), CVMFS (software deployment) and Indico (event organization) and the python tools of the Scikit-HEP project.
However, the numerous libraries have exploded the software stack of new experiments and require often complex dependency management and build tooling. We show how the Spack package manager can adress these problems and  make building complex experiment stacks easy and accessible to everyone.&lt;/p&gt;</description>
        <persons>
          <person id="8767">Valentin Volkl</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/open_source_hep/attachments/slides/5256/export/events/attachments/open_source_hep/slides/5256/FOSDEM_heptooling.pdf">FOSDEM_heptooling Slides</attachment>
        </attachments>
        <links>
          <link href="https://">https://</link>
          <link href="https://video.fosdem.org/2022/D.hpc/open_source_hep.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.hpc/open_source_hep.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#hpc-open_source_hep:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#hpc-open_source_hep:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12872.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.infra">
    </room>
    <room name="D.javascript">
      <event id="13225">
        <start>12:15</start>
        <duration>00:15</duration>
        <room>D.javascript</room>
        <slug>javascript_welcome_day_2</slug>
        <title>JavaScript welcome session - day #2</title>
        <subtitle/>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A short introduction about JavaScript Devroom with some interesting resources about JavaScript and a presentation about this special second day for the FOSDEM JS Devroom.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1687">Ludovic Gasc</person>
          <person id="4435">Fabien Benetou (@Utopiah)</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.javascript/javascript_welcome_day_2.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/javascript_welcome_day_2.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-javascript_welcome_day_2:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-javascript_welcome_day_2:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13225.php">Submit feedback</link>
        </links>
      </event>
      <event id="12622">
        <start>12:30</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>react</slug>
        <title>React</title>
        <subtitle>React Virtual Dom</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The talk would center on React Virtual Dom&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;How React Works&lt;/li&gt;
&lt;li&gt;How to handle React Logic&lt;/li&gt;
&lt;li&gt;The difference between Virtual Dom and Browser Dom&lt;/li&gt;
&lt;li&gt;React Architecture.&lt;/li&gt;
&lt;/ol&gt;
</abstract>
        <description>&lt;p&gt;Talking about React Architecture, give detail information about how react works&lt;/p&gt;</description>
        <persons>
          <person id="8664">Gabriel Soft</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://GitHub.com/iamgabrielsoft">My GitHub repository for reference to some react project</link>
          <link href="https://react.org">Reference to react project</link>
          <link href="https://video.fosdem.org/2022/D.javascript/react.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/react.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-react:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-react:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12622.php">Submit feedback</link>
        </links>
      </event>
      <event id="12611">
        <start>13:00</start>
        <duration>01:00</duration>
        <room>D.javascript</room>
        <slug>writing_less_insecure_javascript</slug>
        <title>Writing less insecure JavaScript</title>
        <subtitle>Practical tips to rule out common mistakes</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In 2021 we saw several security incidents. Looking closer at it, some patterns emerge, that could help prevent them in the future.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk, you will learn about some precautions you can take for your code, but also what you can do in your team, your company or as part of a community.
Thinking about code as a communication medium means, we also should look at the people to prevent security incidents.&lt;/p&gt;

&lt;p&gt;You will get practical tips that you can realise today.
There are also some recommendations you should bring up in your team to help you stay safer in the future.&lt;/p&gt;

&lt;p&gt;Since there is so much to talk about, the slides are designed as choose-your-own-adventure, but the presentation itself is following a single path.&lt;/p&gt;</description>
        <persons>
          <person id="6670">André Jaenisch</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/writing_less_insecure_javascript/attachments/slides/5225/export/events/attachments/writing_less_insecure_javascript/slides/5225/slides_export.pdf">Writing less insecure JavaScript (Export)</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/writing_less_insecure_javascript/attachments/other/5274/export/events/attachments/writing_less_insecure_javascript/other/5274/subtitles.srt">Subtitles (without Q+A)</attachment>
        </attachments>
        <links>
          <link href="https://jaenis.ch/hobbies/speaking/fosdem-2022-writing-less-insecure-javascript/">Reveal.js presentation with speaker notes</link>
          <link href="https://twitter.com/AndreJaenisch">My Twitter Account</link>
          <link href="https://jaenis.ch/">My Homepage</link>
          <link href="https://snyk.io/blog/ten-npm-security-best-practices/">10 npm Security Best Practices by Snyk</link>
          <link href="https://cheatsheetseries.owasp.org/cheatsheets/HTML5_Security_Cheat_Sheet.html">OWASP HTML5 Security Cheat Sheet</link>
          <link href="https://wiki.videolan.org/Documentation:Subtitles/#Subtitles_files">How to load subtitle file in VLC</link>
          <link href="https://video.fosdem.org/2022/D.javascript/writing_less_insecure_javascript.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/writing_less_insecure_javascript.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-writing_less_insecure_javascript:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-writing_less_insecure_javascript:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12611.php">Submit feedback</link>
        </links>
      </event>
      <event id="12903">
        <start>14:00</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>somebody_set_up_us_the_bomb</slug>
        <title>Somebody set up us the bomb</title>
        <subtitle>Expansion attacks in Node.js</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Denial of Service (DoS) bombs are a rudimentary, yet effective, type of attack that's often easy to understand but hard to protect from.&lt;/p&gt;

&lt;p&gt;In this talk I'll cover some common "bombs" such as XML Bombs, YAMLs Bombs and Fork Bombs, and some basic techniques that can help defend from them.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1828">Allon Mureinik</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/somebody_set_up_us_the_bomb/attachments/slides/4868/export/events/attachments/somebody_set_up_us_the_bomb/slides/4868/Somebody_set_up_us_the_bomb_Allon_Mureinik_FOSDEM_2022.pdf">Slides from the session</attachment>
        </attachments>
        <links>
          <link href="https://github.com/mureinik/somebody-set-up-us-the-bomb">Source code for benchmarks shared in the session</link>
          <link href="https://video.fosdem.org/2022/D.javascript/somebody_set_up_us_the_bomb.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/somebody_set_up_us_the_bomb.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-somebody_set_up_us_the_bomb:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-somebody_set_up_us_the_bomb:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12903.php">Submit feedback</link>
        </links>
      </event>
      <event id="13066">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>shedding_light_on_the_shadow_dom</slug>
        <title>Shedding Light on the Shadow DOM</title>
        <subtitle>Learning how, when, and why to use the shadow DOM</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In the world of design systems and component libraries, developers need to build encapsulated components so they can confidently use them anywhere in an application. The shadow DOM serves to provide this encapsulation, and ensure that a component’s styles and functionality are not affected in the context of a complete application. In this talk, we’ll learn what the shadow DOM is and how to use it when building reusable components. We’ll use Stencil, a web components compiler, to demonstrate the common use cases of the shadow DOM, and where it fits in the context of a design system.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Using the shadow DOM effectively requires a few strategies that may not be well known to developers who only use the light DOM. In this talk, we’ll see how to take advantage of all kinds of common styling paradigms, from using CSS frameworks to global styles for multiple components, all while maintaining style encapsulation. The shadow DOM, like any tool, should only be used for certain situations, and so we’ll look at when to use and when not to use the shadow DOM. For the times when we can’t use the shadow DOM, we’ll see what other strategies we can use to still achieve encapsulation.&lt;/p&gt;</description>
        <persons>
          <person id="8755">Anthony Giuliano</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/shedding_light_on_the_shadow_dom/attachments/slides/5278/export/events/attachments/shedding_light_on_the_shadow_dom/slides/5278/Presentation_Slides"/>
        </attachments>
        <links>
          <link href="https://stenciljs.com/">Stencil Documentation</link>
          <link href="https://video.fosdem.org/2022/D.javascript/shedding_light_on_the_shadow_dom.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/shedding_light_on_the_shadow_dom.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-shedding_light_on_the_shadow_dom:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-shedding_light_on_the_shadow_dom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13066.php">Submit feedback</link>
        </links>
      </event>
      <event id="12931">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>building_a_tiny_javascript_runtime_with_quickjs</slug>
        <title>Building a tiny JavaScript runtime with QuickJS</title>
        <subtitle>How I built a runtime with Duktape and then rebuilt it with QuickJS</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;QuickJS is a (small) JavaScript engine by Fabrice Bellard.&lt;/p&gt;

&lt;p&gt;Over the past 6 years I've built a couple of small JS runtimes, first using Duktape, then using QuickJS. The premise was to always use existing libraries to add functionality, including WASM support.&lt;/p&gt;

&lt;p&gt;This presentation will go through the differences of both libraries and the 2 projects I built leveraging them.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;There are many libraries out there which one can use to build a JS runtime these days, with the most well known one being V8.&lt;/p&gt;

&lt;p&gt;Node and Deno are both using V8, but how would a different take at building a JS runtime look like?&lt;/p&gt;

&lt;p&gt;I asked myself this question some years ago and started building a small project with Duktape. That project was ultimately a failure, but I learned very valuable lessons in runtime design and always wanted to revisit that project.&lt;/p&gt;

&lt;p&gt;Fast forward a few years, QuickJS was released by Fabrice Bellard, and I was excited! It was so easy to integrate that I began to implement a new runtime using it. This runtime is called txiki.js and while it's a small project it already integrates libuv for fast networking and the event loop, curl for making HTTP requests and wasm3 for WASM (and WASI!) support.&lt;/p&gt;</description>
        <persons>
          <person id="186">Saúl Ibarra Corretgé</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/building_a_tiny_javascript_runtime_with_quickjs/attachments/slides/5012/export/events/attachments/building_a_tiny_javascript_runtime_with_quickjs/slides/5012/txikijs.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://duktape.org/">Duktape JS engine</link>
          <link href="https://bellard.org/quickjs/">QuickJS engine</link>
          <link href="https://github.com/saghul/txiki.js">txiki.js runtime</link>
          <link href="https://github.com/saghul/sjs">Skookum JS runtime</link>
          <link href="https://video.fosdem.org/2022/D.javascript/building_a_tiny_javascript_runtime_with_quickjs.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/building_a_tiny_javascript_runtime_with_quickjs.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-building_a_tiny_javascript_runtime_with_quickjs:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-building_a_tiny_javascript_runtime_with_quickjs:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12931.php">Submit feedback</link>
        </links>
      </event>
      <event id="12932">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>from_microrepos_to_monorepo</slug>
        <title>From microrepos to monorepo: thrilling adventures in refactoring</title>
        <subtitle>On how to tame, and accelerate, builds and tests in a 25 module monorepo</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Building a monorepo composed of more than 25 modules, internal dependencies and iOS and Android app to boot is a challenge. Doing so fast and under a certain cost threshold might seem daunting. However, in polypoly we’ve tried to do it for the past few months, creating our own build/test tool with 0 dependencies and a straightforward approach to what a monorepo needs, when it needs.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Testing needs to follow the F.I.R.S.T. principles, of which the first one, Fast, is possibly the most important. Fast testing ensures that developers respond quickly to all kind of testing errors, and of course it keeps the cost of testing low.&lt;/p&gt;

&lt;p&gt;Monorepos have additional challenges: dependencies cross language boundaries, dependence graphs are not explicit, and there's the risk of centralising some, none, or all the submodule upstream dependencies.&lt;/p&gt;

&lt;p&gt;At polypoly we have been using a monorepo since May 2021. In this talk we will show how we have tackled this challenge with a series of GitHub actions, as well as creating a tool, build.js, which is geared towards dealing with monorepos.&lt;/p&gt;

&lt;p&gt;We will show how this tool partially solves the speed issue, and what are our plans, going forward, to make tests faster and deal with implicit dependency graphs. We will also examine best practices in the area of monorepo builds for projects whose majority is written in Javascript/Typescript.&lt;/p&gt;</description>
        <persons>
          <person id="1263">Juan Julián Merelo</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/polypoly-eu/polyPod">The polyPod, bringing data sovereignity to the people</link>
          <link href="https://video.fosdem.org/2022/D.javascript/from_microrepos_to_monorepo.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/from_microrepos_to_monorepo.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-from_microrepos_to_monorepo:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-from_microrepos_to_monorepo:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12932.php">Submit feedback</link>
        </links>
      </event>
      <event id="13058">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>web_application_localization_without_tears</slug>
        <title>Web Application Localization Without Tears</title>
        <subtitle>Learn how to translate your JS web app fast</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;“The more languages your software knows, the more of a satisfied users you have". However, current software localization in modern JS frameworks and other software is complicated and fairly time-consuming for all involved participants. Thanks to the in-context localization feature of open-source project Tolgee, this tool offers easier localization process, more relevant translations delivery and finally less work for developers.&lt;/p&gt;

&lt;p&gt;The workshop will contain live demo where I would like to describe using Tolgee JavaScript software development kits on simple React.js web application example. However, Tolgee is currently compatible with other frameworks such as Angular, Svelte, Vue.js or Next.js.&lt;/p&gt;

&lt;p&gt;Participants will learn easy localization workflow using by Tolgee tool, simple localization texts management, how to integrate Tolgee into web app in less than one minute, how to take advantage of different Tolgee features as e.g. automatic generation of screenshots or in-context localization.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8838">Jan Cizmar</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://tolgee.io">Docs</link>
          <link href="https://github.com/tolgee/server">Tolgee Platform Github Repo</link>
          <link href="https://github.com/tolgee/tolgee-js">Tolgee JS packages monorepo</link>
          <link href="https://video.fosdem.org/2022/D.javascript/web_application_localization_without_tears.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/web_application_localization_without_tears.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-web_application_localization_without_tears:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-web_application_localization_without_tears:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13058.php">Submit feedback</link>
        </links>
      </event>
      <event id="13119">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>symbols_symbols_everywhere</slug>
        <title>Symbols Symbols everywhere</title>
        <subtitle/>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As part of javascript ES6  (ECMAScript 2015) a new primitive type called symbols was added to the programming language. It is not a widely talked about feature but useful for certain scenarios.&lt;/p&gt;

&lt;p&gt;The talk will explain the following new features and demo how they are used.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What are symbols and why they were introduced&lt;/li&gt;
&lt;li&gt;Use cases for symbols&lt;/li&gt;
&lt;li&gt;Why would you use them&lt;/li&gt;
&lt;li&gt;Creating and Overwriting symbol methods&lt;/li&gt;
&lt;li&gt;Well known symbols&lt;/li&gt;
&lt;li&gt;Explore core source code of symbols&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="7081">Martin Naughton</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.martinnaughton.com">Personal website that i should start updating more</link>
          <link href="https://galviadigital.com">A company i started building software applications</link>
          <link href="https://video.fosdem.org/2022/D.javascript/symbols_symbols_everywhere.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/symbols_symbols_everywhere.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-symbols_symbols_everywhere:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-symbols_symbols_everywhere:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13119.php">Submit feedback</link>
        </links>
      </event>
      <event id="12812">
        <start>17:00</start>
        <duration>00:30</duration>
        <room>D.javascript</room>
        <slug>micro_lc</slug>
        <title>micro-lc: a new micro-frontend orchestrator</title>
        <subtitle>The easiest way to micro-frontend</subtitle>
        <track>JavaScript</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;micro-lc enables you to create modular applications composed by multiple, independent micro frontends called plugins integrated at runtime. micro-lc consists of a core interface that loads, embeds, and orchestrates plugins, while providing configuration options and useful out-of-the-box features.&lt;/p&gt;

&lt;p&gt;The core components are written in Typescript and React, micro-lc is technology-agnostic, which means that it integrates seamlessly with your favourite toolkit, being it Angular, React, Vue, or anything else you like.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8603">Matteo Pietro Dazzi</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/micro_lc/attachments/slides/4925/export/events/attachments/micro_lc/slides/4925/micro_lc_presentation">micro-lc presentation</attachment>
        </attachments>
        <links>
          <link href="https://microlc.io/">Official website</link>
          <link href="https://github.com/micro-lc/micro-lc">Source code</link>
          <link href="https://video.fosdem.org/2022/D.javascript/micro_lc.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.javascript/micro_lc.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#javascript-micro_lc:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#javascript-micro_lc:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12812.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.kotlin">
      <event id="13518">
        <start>10:00</start>
        <duration>00:10</duration>
        <room>D.kotlin</room>
        <slug>kotlin_devroom_welcome</slug>
        <title>Kotlin DevRoom Welcoming Remarks</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Welcoming participants to the virtual edition of the Kotlin DevRoom @ FOSDEM&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6477">Nicola Corti</person>
          <person id="7079">Martin Bonnin</person>
          <person id="7925">Marco Gomiero</person>
          <person id="7934">Holger Steinhauer</person>
          <person id="7953">Julien Salvi</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/kotlin_devroom_welcome.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/kotlin_devroom_welcome.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-kotlin_devroom_welcome:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-kotlin_devroom_welcome:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13518.php">Submit feedback</link>
        </links>
      </event>
      <event id="13192">
        <start>10:10</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>the_state_of_kotlin</slug>
        <title>The State of Kotlin</title>
        <subtitle>Q1 2022 Edition</subtitle>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In 2021 Kotlin turned 10 and the team delivered 2 major releases (1.5.0 and 1.6.0) and a few minors. The main themes of those releases were Java interoperability and consistency of the language features. Meanwhile, Kotlin/JS has been promoted to Beta and KMM is on its path to reaching Beta status as well. However, one long-running project in Kotlin is the development of the new compiler, K2, which should set a solid foundation for the language and the ecosystem for the years ahead.&lt;/p&gt;

&lt;p&gt;This session is an overview of the latest developments in Kotlin: the language, tools, compiler, and the ecosystem around it. We're also going to take a look at Kotlin's roadmap to see where are we heading. Come and learn what's new and exciting!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8879">Anton Arhipov</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/the_state_of_kotlin.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/the_state_of_kotlin.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-the_state_of_kotlin:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-the_state_of_kotlin:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13192.php">Submit feedback</link>
        </links>
      </event>
      <event id="13205">
        <start>10:40</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>advanced_multiplatform_dependency_injection</slug>
        <title>Advanced multi-platform dependency injection with Kotlin</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Dependency Injection is a complicated topic, and when used in a project that compiles to multiple targets through different compilers &amp;amp; runtimes, it can lead to serious headaches. However, the Inversion of Control pattern brings a lot of architecture features and safety.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk, we will see how to use all the power of Kodein-DI, a popular dependency injection library that works everywhere Kotlin can compile to, in a mobile multi-platform project targeting Android, iOS and the mobile Web.&lt;/p&gt;

&lt;p&gt;We will start by using the dependency injection pattern to abstract and test the behavior of multi-platform business modules. We will then see how to debug common dependency management errors.&lt;/p&gt;

&lt;p&gt;Finally, we will enhance our common code using advanced features of Kodein-DI such as set bindings, lazy access, context, and scopes.&lt;/p&gt;</description>
        <persons>
          <person id="7816">Romain Boisselle</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/advanced_multiplatform_dependency_injection.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/advanced_multiplatform_dependency_injection.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-advanced_multiplatform_dependency_injection:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-advanced_multiplatform_dependency_injection:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13205.php">Submit feedback</link>
        </links>
      </event>
      <event id="13219">
        <start>11:10</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>the_beauty_of_kotlin_typing_system</slug>
        <title>The beauty of Kotlin typing system</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Kotlin typing system is amazingly designed. It was designed and constantly improved for years, and it was built based on experiences from other typing systems. As a result it gives us very comfortable nullability support, type inference, universal guards, and much more. In this presentation, we’ll dive deep into Kotlin typing systems and how small design choices lead to a better programming experience.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The Kotlin typing system is amazingly designed. It was designed and constantly improved for years, and it was built based on experiences from other typing systems. As a result it gives us very comfortable nullability support, type inference, universal guards, and much more. In this presentation, we’ll dive deep into Kotlin typing systems and how small design choices lead to a better programming experience.&lt;/p&gt;</description>
        <persons>
          <person id="8900">Marcin Moskala</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/the_beauty_of_kotlin_typing_system.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/the_beauty_of_kotlin_typing_system.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-the_beauty_of_kotlin_typing_system:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-the_beauty_of_kotlin_typing_system:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13219.php">Submit feedback</link>
        </links>
      </event>
      <event id="12508">
        <start>11:40</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>kotlin_code_first_process_modelling_kalasim</slug>
        <title>Code-first process modeling and analysis with kalasim</title>
        <subtitle>Understand and optimize real-world processes at ease</subtitle>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;kalasim is a discrete event simulator written in pure Kotlin that enables complex, performant, dynamic process models. It provides a statically typed API, dependency injection, modern persistence, structured logging and automation capabilities.&lt;/p&gt;

&lt;p&gt;kalasim is designed for simulation practitioners, process analysts and industrial engineers, who need to go beyond the limitations of existing simulation tools to model and optimize their business-critical use-cases. In contrast to many other simulation tools, kalasim is neither low-code nor no-code. It is code-first to enable change tracking, scaling, refactoring, CI/CD, unit-tests, and the rest of the gang that makes simulation development fun.&lt;/p&gt;

&lt;p&gt;In the talk, we will learn about its core concepts and study several examples from different application domains.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8595">Holger Brandl</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/holgerbrandl/kalasim">Repo</link>
          <link href="https://www.kalasim.org/">Documentation</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/kotlin_code_first_process_modelling_kalasim.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/kotlin_code_first_process_modelling_kalasim.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-kotlin_code_first_process_modelling_kalasim:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-kotlin_code_first_process_modelling_kalasim:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12508.php">Submit feedback</link>
        </links>
      </event>
      <event id="13146">
        <start>12:10</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>kotlin_plus_maths</slug>
        <title>Kotlin + Maths</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Grab your notebook cause in this talk, we are gonna talk about Math and Kotlin! Especially in the power that Kotlin has to run long operations and the power to perform some calculations like computing min, max, an average of numbers stored in a list! - from sumOf {} to multi-dimensional arrays to charts!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8873">Dinorah Tovar</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/kotlin_plus_maths.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/kotlin_plus_maths.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-kotlin_plus_maths:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-kotlin_plus_maths:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13146.php">Submit feedback</link>
        </links>
      </event>
      <event id="12906">
        <start>12:40</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>kotlin_clis_and_starwars</slug>
        <title>Kotlin, CLIs and StarWars! </title>
        <subtitle>An introduction to creating CLI applications with Kotlin using Picocli</subtitle>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;picoCLI is a small library that can be used to create JVM based command line interface applications. Within 30 minutes, we'll look at how to setup a project, create a small application and package it for others to use.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;picoCLI is a small library that can be used to create JVM based command line interface applications.&lt;/p&gt;

&lt;p&gt;Within 30 minutes, we'll look at how to setup a project, create a small application and package it for others to use.&lt;/p&gt;

&lt;p&gt;picoCLI is nice for several reasons : CLIs are a great way to automate some commands we run every day. And because it supports Java and Kotlin, we can keep using our main language of choice rather than having to dive into bash or node. Finally, pico applications can be turned into native images using GraalVM, which allows for a nice end user experience.&lt;/p&gt;

&lt;p&gt;By the end of this talk, you'll have a basic knowledge of what picoCLI can do, how to set it up and hopefully ideas of use cases to run it with!&lt;/p&gt;

&lt;p&gt;This is a byte size presentation so it'll have to go fast!&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;I'll introduce the project in 5 minutes.&lt;/li&gt;
&lt;li&gt;Then jump into a starter project and the basic features of the library around. We will compile and test it live. - 20 minutes&lt;/li&gt;
&lt;li&gt;Finally, we will look into some of the advanced features, and check at packaging options for end users - 5 minutes&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="8783">Julien Lengrand-Lambert</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/kotlin_clis_and_starwars.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/kotlin_clis_and_starwars.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-kotlin_clis_and_starwars:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-kotlin_clis_and_starwars:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12906.php">Submit feedback</link>
        </links>
      </event>
      <event id="12584">
        <start>13:10</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>ksp_and_plugins</slug>
        <title>KSP and Plugins. Optimizing Kotlin Multiplatform common code</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;KSP (Kotlin Symbol Processing) is an API from Google for writing Kotlin compiler plugins. Using KSP we can write annotation processors to reduce boilerplate and solve cross-cutting concerns. Also KSP is more effective than KAPT. Among the advantages of using it is the support of Kotlin Multiplatform.
Another way to optimize common code is to use Kotlin plugins.
In my talk I would to like to show some samples how to use own plugins and KSP processing in Kotlin Multiplatform app supporting both iOS and Android.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8590">Anna Zharkova</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/ksp_and_plugins.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/ksp_and_plugins.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-ksp_and_plugins:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-ksp_and_plugins:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12584.php">Submit feedback</link>
        </links>
      </event>
      <event id="13215">
        <start>13:40</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>dataclassgenerate_shrinking_kotlin_data_classes</slug>
        <title>DataClassGenerate. Shrinking Kotlin data classes</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk is a deep dive into Kotlin data classes optimisations. We will find what optimisations are possible, and how to apply them with Kotlin compiler plugins and Android optimisers.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk:
1. We quantify data classes impact on App size
2. Apply general purpose DEX-code optimizations to data classes
3. Introduce DataClassGenerate (DCG), a Kotlin-specific optimisation fod data classes
4. Observe Kotlin Compiler Plugin API and DCG implementation&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;- Describes DataClassGenerate approach
    1. @DataClassGenerate annotation
    2. DataClassGenerate compiler plugin
    3. Kotlin Compiler plugin interaction with Redex
&lt;/code&gt;&lt;/pre&gt;</description>
        <persons>
          <person id="8899">Sergei Rybalkin</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/dataclassgenerate_shrinking_kotlin_data_classes/attachments/slides/5215/export/events/attachments/dataclassgenerate_shrinking_kotlin_data_classes/slides/5215/Slides">Slides</attachment>
        </attachments>
        <links>
          <link href="https://speakerdeck.com/colriot/kotlin-adoption-at-scale-kodeinkoders-2021">Related slides</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/dataclassgenerate_shrinking_kotlin_data_classes.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/dataclassgenerate_shrinking_kotlin_data_classes.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-dataclassgenerate_shrinking_kotlin_data_classes:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-dataclassgenerate_shrinking_kotlin_data_classes:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13215.php">Submit feedback</link>
        </links>
      </event>
      <event id="13190">
        <start>14:10</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>mocking_without_reflection_for_kotlin_multiplatform</slug>
        <title>Mocking without reflection for Kotlin/Multiplatform</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Mocking typically involves reflection: an efficient mocker can create implementations of interfaces or even concrete classes on the go by reflecting on their methods and properties.
These required capabilities do not exist in Kotlin/Multiplatform, so we will explore an alternative method to runtime reflection: a compile-time symbol processor.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Using Mocking as an excuse, we will explore how we can use KSP (Kotlin Symbol Processor) to circumvent the absence of reflection and generate efficient mocks at compile time. We will also see the limitations that multiplatform brings to both the KSP Mocker generator and its associated runtime. We will explain the choices that we made when developing the MocKMP multiplatform mocking library, and why they were needed. We will then demonstrate the clean DSL API we offer to describe and verify your mocks.
Finally, we will demonstrate how to architecture all these moving parts (KSP plugin, mocker generator, mocker runtime) using a custom Gradle Plugin to make using MocKMP as easy as it gets.&lt;/p&gt;</description>
        <persons>
          <person id="8870">Salomon BRYS</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/mocking_without_reflection_for_kotlin_multiplatform.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/mocking_without_reflection_for_kotlin_multiplatform.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-mocking_without_reflection_for_kotlin_multiplatform:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-mocking_without_reflection_for_kotlin_multiplatform:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13190.php">Submit feedback</link>
        </links>
      </event>
      <event id="13133">
        <start>14:40</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>from_mobile_to_backend</slug>
        <title>From Mobile to Backend with Kotlin and Ktor</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As mobile developers, we often see the backend world as something magical that "does things". But what if I tell you that you can easily build a backend even if mobile is your thing?&lt;/p&gt;

&lt;p&gt;With this talk, I want to show how it is possible to bring your mobile knowledge (and shift it a little bit) to build a backend with Kotlin and Ktor. I will show how to structure the project, set up Dependency Injection, connect to a database and test everything to have a working backend ready to be deployed.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7925">Marco Gomiero</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/from_mobile_to_backend.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/from_mobile_to_backend.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-from_mobile_to_backend:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-from_mobile_to_backend:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13133.php">Submit feedback</link>
        </links>
      </event>
      <event id="13211">
        <start>15:10</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>navigating_between_composables</slug>
        <title>Navigating between Composables</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This session will be about how to use Jetpack Compose navigation in your Compose app. It will include the topic of passing arguments through navigation.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8894">Maryam Alhuthayfi</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/navigating_between_composables.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/navigating_between_composables.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-navigating_between_composables:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-navigating_between_composables:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13211.php">Submit feedback</link>
        </links>
      </event>
      <event id="12963">
        <start>15:40</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>not_only_python_kotlin_for_scripts</slug>
        <title>Not only Python: Kotlin for scripts</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Python is ubiquitous in scripts, and it has definite benefits. However, Kotlin developers don't need to migrate to another stack to create scripts.&lt;/p&gt;

&lt;p&gt;In this talk, I'll show you how I use Kotlin to have an always up-to-date GitHub profile.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5584">Nicolas Frankel</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/not_only_python_kotlin_for_scripts.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/not_only_python_kotlin_for_scripts.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-not_only_python_kotlin_for_scripts:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-not_only_python_kotlin_for_scripts:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12963.php">Submit feedback</link>
        </links>
      </event>
      <event id="12582">
        <start>16:10</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>gradle_a_deeper_look_at_the_kotlin_dsl</slug>
        <title>Gradle: a deeper look at the Kotlin DSL</title>
        <subtitle>Everything you didn't want to know about Gradle Kotlin APIs</subtitle>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Originally designed for Groovy, Gradle now supports writing scripts in Kotlin. Writing your scripts in Kotlin brings more compile-type safety and IDE features but also has a few drawbacks.&lt;/p&gt;

&lt;p&gt;In this talk, we will take a look some widely used Groovy constructs, their Kotlin equivalent and what’s happening under the hood. We will explore how Gradle loads scripts and uses Kotlin compiler flags to allow a the Kotlin DSL syntax.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7079">Martin Bonnin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.kotlin/gradle_a_deeper_look_at_the_kotlin_dsl.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/gradle_a_deeper_look_at_the_kotlin_dsl.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-gradle_a_deeper_look_at_the_kotlin_dsl:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-gradle_a_deeper_look_at_the_kotlin_dsl:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12582.php">Submit feedback</link>
        </links>
      </event>
      <event id="13144">
        <start>16:40</start>
        <duration>00:30</duration>
        <room>D.kotlin</room>
        <slug>livecoding_a_web_server_with_ktor</slug>
        <title>Live-coding a web server with Ktor</title>
        <subtitle>Set up a web server and a client with Ktor in a live coding session.</subtitle>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Ktor is a Kotlin framework dedicated to building asynchronous servers and clients in connected systems.
In this session, I will explain and demo the core concepts of Ktor 2 by live coding an HTTP server from scratch using Ktor Server.
Also, we'll take an overview of Ktor Client, from setting it up to making requests and installing plugins.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8871">Renaud Mathieu</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://innovorder.dev/deploy-a-microservice-in-kotlin-with-ktor-part-1-2691fef75e1d">Deploy a microservice in Kotlin with Ktor — Part 1</link>
          <link href="https://innovorder.dev/deploy-a-microservice-in-kotlin-with-ktor-part-2-8c431b56dc51">Deploy a microservice in Kotlin with Ktor — Part 2</link>
          <link href="https://innovorder.dev/deploy-a-microservice-in-kotlin-with-ktor-part-3-e99312f0e7f8">Deploy a microservice in Kotlin with Ktor — Part 3</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/livecoding_a_web_server_with_ktor.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/livecoding_a_web_server_with_ktor.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-livecoding_a_web_server_with_ktor:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-livecoding_a_web_server_with_ktor:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13144.php">Submit feedback</link>
        </links>
      </event>
      <event id="12869">
        <start>17:10</start>
        <duration>00:35</duration>
        <room>D.kotlin</room>
        <slug>refactoring_glided_rose_kata</slug>
        <title>Refactoring Gilded Rose Kata</title>
        <subtitle/>
        <track>Kotlin</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Gilded Rose refactoring kata is a coding exercise designed to practice your refactoring and test cases writing skills. In this live coding session I will use the Kotlin version of the kata to show how a sequence of small improvements can make a difference taking program design to a better and more functional place. You will see a few refactoring heuristics, IntelliJ tips and tricks and design emerging from seemingly chaotic code.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7537">Dmitry Kandalov</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.youtube.com/watch?v=GcYa4lMRta0">The Easy Way to Create IntelliJ Plugins at VKUG</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/refactoring_glided_rose_kata.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.kotlin/refactoring_glided_rose_kata.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#kotlin-refactoring_glided_rose_kata:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#kotlin-refactoring_glided_rose_kata:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12869.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.legal">
    </room>
    <room name="D.open-hardware">
      <event id="13007">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.open-hardware</room>
        <slug>corundum</slug>
        <title>corundum</title>
        <subtitle>From a NIC to a Platform for In-Network Compute</subtitle>
        <track>Libre-Open VLSI and FPGA</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The talk provides an introduction to the corundum project, implementing a 100 GbE NIC based on Commercial-off-the-shelf (COTS) FPGA cards, e.g. Xilinx Alveo Cards. The project consists of all necessary RTL components, e.g. PCIe DMA engine, NIC datapath, MAC, PHY and integration of vendor specific IP cores, such as transceivers and PCIe hard-IP cores. In combination with the provided driver and debugging utility the ready-to-experiment state just requires a supported FPGA card + compiler to kick-off playing with the project.&lt;/p&gt;

&lt;p&gt;The existing state provides the platform for future In-Network Compute platform research, allowing for application logic to be balanced across hardware acceleration and software flexibility. The platform uniquely allows for experiments with lower layer protocols, e.g. PHY layer coding.&lt;/p&gt;

&lt;p&gt;The talk concludes with an overview about short term and mid term goals of the project.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8542">Ulrich Langenbach</person>
          <person id="8959">Alex Forencich</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/corundum/attachments/slides/4990/export/events/attachments/corundum/slides/4990/fosdem_2022_d_open_hardware_corundum.pdf">Corundum - From a NIC to a Platform for In-Network Compute</attachment>
        </attachments>
        <links>
          <link href="https://github.com/corundum/corundum">corundum github repository</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/corundum.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/corundum.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-corundum:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-corundum:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13007.php">Submit feedback</link>
        </links>
      </event>
      <event id="13194">
        <start>10:30</start>
        <duration>00:50</duration>
        <room>D.open-hardware</room>
        <slug>coriolis2</slug>
        <title>Coriolis RTL-to-GDSII Toolchain</title>
        <subtitle>State of advancement and planned improvements</subtitle>
        <track>Libre-Open VLSI and FPGA</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Sorbonne  Université,  in  collaboration  with Chips4Makers  and  LibreSOC  are
working  to  provide  a  complete  FOSS  toolchain  to  make  ASICs  in  mature
technological  nodes,  that is,  no  smaller  than  130nm.  We take  a  circuit
description in HDL, synthetize with Yosys but instead of targetting a FPGA, use
an ASIC  standard cell library  to get the  RTL description.  From  there, with
Coriolis2, we  perform the  classical steps of  a RTL to  GDSII flow,  that is,
placement, routage  along with very  basic timing  closure.&lt;/p&gt;

&lt;p&gt;We will  particularly focus  on last  year progresses  and present  the planned
improvements and new features for 2022.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8880">Jean-Paul Chaput</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="http://coriolis.lip6.fr">The Coriolis Documentation</link>
          <link href="https://gitlab.lip6.fr/vlsi-eda/coriolis">Coriolis repository</link>
          <link href="https://gitlab.lip6.fr/vlsi-eda/alliance-check-toolkit">Checking/examples toolkit</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/coriolis2.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/coriolis2.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-coriolis2:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-coriolis2:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13194.php">Submit feedback</link>
        </links>
      </event>
      <event id="12427">
        <start>11:20</start>
        <duration>00:30</duration>
        <room>D.open-hardware</room>
        <slug>openwifipynqz1</slug>
        <title>Bring openwifi to PYNQ-Z1 with ultra low cost</title>
        <subtitle/>
        <track>Libre-Open VLSI and FPGA</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Both software-defined radio and FPGA are interesting. Especially, the combination of AD936X RF transceiver and ZYNQ 7020 level FPGA SoC is capable of running openwifi. Price has been keeping average DIYers away from this kind of platform as evaluation boards from ADI and Xilinx are both extremely expensive. Cheaper ones like ANTSDR exist, but seems all of them have tied the RF and ZYNQ chip together, so these are not suitable for generic ZYNQ development anymore.&lt;/p&gt;

&lt;p&gt;In this talk, I want to introduce an openwifi capable low-cost AD936X extension board design and realization for the wildly available PYNQ-Z1 board by Digilent. This provides openwifi and PlutoSDR functionalities meanwhile keeping the major if not all functions of PYNQ-Z1 intact, with summed price potentially lower than all currently available openwifi capable platforms. Similar designs may also be applicable to other ZYNQ boards like ZYBO Z7-20 or Arty Z7-20, thus these could make openwifi available to much more people, especially those who already have a ZYNQ board. Besides this extension board, I'll also touch on tools and workflows for "modern" circuit board DIY, which enabled me to build this 4-layer board with BGA chip comfortably at home.&lt;/p&gt;

&lt;p&gt;For more about openwifi, please visit the Free Software Radio devroom for "Opensource WiFi chip (openwifi) progress and future plan" on Sunday afternoon.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8456">Yimin Gu</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/openwifipynqz1/attachments/slides/5252/export/events/attachments/openwifipynqz1/slides/5252/openwifi_pynqz1_yimin_gu.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/regymm/PYNQSDR">Board files and introduction</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/openwifipynqz1.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/openwifipynqz1.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-openwifipynqz1:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-openwifipynqz1:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12427.php">Submit feedback</link>
        </links>
      </event>
      <event id="12979">
        <start>11:50</start>
        <duration>00:20</duration>
        <room>D.open-hardware</room>
        <slug>gtkwavecss</slug>
        <title>Writing GTKWave documents, with style</title>
        <subtitle>A Python-based CSS-like mini language for generating GTKWave documents</subtitle>
        <track>Libre-Open VLSI and FPGA</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;GTKWave is a nice tool for displaying signal traces, while developing with Hardware Description Languages, and has many formatting features like changing signal color, grouping signals in a hierarchy, etc. However, it can become tedious to manually edit through the GUI. Also, its document format, while ASCII, is a bit cryptic, and contains extra information pertaining to the GUI (window and panel sizes, last modification date, etc.), making it inconvenient for placing in revision control.&lt;/p&gt;

&lt;p&gt;A Domain Specific Language for generating GTKWave documents was developed, separating signal description and structure from style, not unlike HTML+CSS, but described using Python Lists and Dictionaries. This makes it especially suitable for embedding in Python-based Hardware Description Languages and Simulators.&lt;/p&gt;

&lt;p&gt;While it fits my own needs, I'm hopping to gather some feedback on this tiny library, so it could be made more generally useful.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8807">Cesar Strauss</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/gtkwavecss/attachments/slides/5059/export/events/attachments/gtkwavecss/slides/5059/gtkwavecss.pdf">Writing GTKWave documents, with style</attachment>
        </attachments>
        <links>
          <link href="https://libre-soc.org/docs/gtkwave_tutorial/">Tutorial</link>
          <link href="https://git.libre-soc.org/?p=nmutil.git;a=blob;f=src/nmutil/gtkw.py;h=f26fc00cf17b1e0be1977f1c699aff5a37eb35d7;hb=HEAD">Source code</link>
          <link href="https://docs.libre-soc.org/nmutil/src/gen/nmutil.html#module-nmutil.gtkw">API documentation</link>
          <link href="https://git.libre-soc.org/?p=nmutil.git;a=blob;f=src/nmutil/test/example_gtkwave.py;h=1b8c3b9c1b0bb5cde23c6896fc5cbde991790384;hb=HEAD#l203">Example usage</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/gtkwavecss.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/gtkwavecss.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-gtkwavecss:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-gtkwavecss:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12979.php">Submit feedback</link>
        </links>
      </event>
      <event id="13509">
        <start>12:10</start>
        <duration>01:00</duration>
        <room>D.open-hardware</room>
        <slug>nmigen</slug>
        <title>nMigen HDL</title>
        <subtitle>a way to create hardware in python</subtitle>
        <track>Libre-Open VLSI and FPGA</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;nmigen™ is a tool for creating hardware, whether for ASICs or for FPGAs. it is not itself an actual language (like Verilog or VHDL), and it is not like MyHDL which allows translation of a limited subset of python source code into verilog.  Instead, nmigen allows you - in python - to create HDL constructs, and to mix those in with the full power of python OO techniques: objects, classes, even multiple inheritance, which is sorely lacking in the Hardware world.&lt;/p&gt;

&lt;p&gt;this talk will go through the background and origins of nmigen, present a short worked-example, present some best-practices for people wishing to transfer over from another HDL, and cover some of the planned advancements.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3743">Luke Kenneth Casson Leighton</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://gitlab.com/nmigen">nmigen 1.0 repository</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/nmigen.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/nmigen.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-nmigen:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-nmigen:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13509.php">Submit feedback</link>
        </links>
      </event>
      <event id="13513">
        <start>13:45</start>
        <duration>00:40</duration>
        <room>D.open-hardware</room>
        <slug>efabless</slug>
        <title>Efabless Open ASICs</title>
        <subtitle>an update from Mohamed Kassem</subtitle>
        <track>Libre-Open VLSI and FPGA</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This presentation by Mohammed Kaseem, the CTO of e-Fabless, will outline how e-Fabless is empowering Libre/Open VLSI Hardware development.  There are two initiatives: ChipIgnite which provides significantly-reduced cost Shuttle runs, and the Google-sponsored Skywater 130nm Programme.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8914">Mohamed Kassem</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://efabless.com/chipignite/">Chipignite</link>
          <link href="https://efabless.com/open_shuttle_program/">efabless Open MPW</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/efabless.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/efabless.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-efabless:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-efabless:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13513.php">Submit feedback</link>
        </links>
      </event>
      <event id="13037">
        <start>14:30</start>
        <duration>01:00</duration>
        <room>D.open-hardware</room>
        <slug>libresilicon</slug>
        <title>Using LibreSilicon</title>
        <subtitle>How to actually use the process and scaling it</subtitle>
        <track>Libre-Open VLSI and FPGA</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;ul&gt;
&lt;li&gt;An overview of the minimal process flow&lt;/li&gt;
&lt;li&gt;Talking about ways to implement it in a garage/shipping container environment.&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="8487">David Lanzendörfer</person>
        </persons>
        <attachments>
          <attachment type="audio" href="https://fosdem.org/2022/schedule/event/libresilicon/attachments/audio/5266/export/events/attachments/libresilicon/audio/5266/slides.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.open-hardware/libresilicon.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.open-hardware/libresilicon.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#open-hardware-libresilicon:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#open-hardware-libresilicon:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13037.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.libreoffice">
      <event id="12817">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_libreoffice73</slug>
        <title>LibreOffice 7.3 New Features</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A summary of LibreOffice 7.3 Community new features, with a specific focus on interoperability with Microsoft Office documents&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="312">Italo Vignoli</person>
        </persons>
        <attachments>
          <attachment type="audio" href="https://fosdem.org/2022/schedule/event/lotech_libreoffice73/attachments/audio/5228/export/events/attachments/lotech_libreoffice73/audio/5228/libreoffice73newfeatures.pdf">LibreOffice 7.3 New Features</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_libreoffice73.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_libreoffice73.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_libreoffice73:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_libreoffice73:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12817.php">Submit feedback</link>
        </links>
      </event>
      <event id="12923">
        <start>10:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_devexperience</slug>
        <title>Improving Developer Experience at LibreOffice</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;During the previous years, there has been a lot of efforts to improve developer experence (DX) at LibreOffice with the code that has a long history. In this presentation, I talk about various aspects of these improvements, and also the road ahead.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8654">Hossein Nourikhah</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_devexperience/attachments/slides/4970/export/events/attachments/lotech_devexperience/slides/4970/libreoffice_dx.pdf">Improving Developer Experience at LibreOffice</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_devexperience.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_devexperience.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_devexperience:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_devexperience:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12923.php">Submit feedback</link>
        </links>
      </event>
      <event id="12794">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_operationalcode</slug>
        <title>Towards an Operational Code Aesthetics</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Towards an Operational Code Aesthetics&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="780">Stephan Bergmann</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_operationalcode/attachments/slides/5053/export/events/attachments/lotech_operationalcode/slides/5053/FOSDEM22.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_operationalcode.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_operationalcode.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_operationalcode:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_operationalcode:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12794.php">Submit feedback</link>
        </links>
      </event>
      <event id="12802">
        <start>11:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_curlbased</slug>
        <title>Curl based HTTP/WebDAV UCP</title>
        <subtitle>How we deleted lots of code</subtitle>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;LibreOffice uses &lt;em&gt;Universal Content Provider&lt;/em&gt;s to access files via various protocols. Due to accidents of history, LibreOffice contained 2 different &lt;em&gt;UCP&lt;/em&gt;s for WebDav and HTTP, one based on &lt;em&gt;neon&lt;/em&gt; and the other on &lt;em&gt;Apache Serf&lt;/em&gt;, each with different bugs and bugfixes.&lt;/p&gt;

&lt;p&gt;For LibreOffice 7.3, thanks to a tender from The Document Foundation, we have replaced both of them with a new &lt;em&gt;UCP&lt;/em&gt; based on &lt;em&gt;libcurl&lt;/em&gt;, which is designed to meet all currently known requirements, and is able to use the operating system's TLS stack on Windows and macOS.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6306">Michael Stahl</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_curlbased/attachments/slides/5208/export/events/attachments/lotech_curlbased/slides/5208/FOSDEM2022_curl_http_webdav.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_curlbased.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_curlbased.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_curlbased:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_curlbased:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12802.php">Submit feedback</link>
        </links>
      </event>
      <event id="12805">
        <start>12:00</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_editingsimulation</slug>
        <title>Editing Simulation</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Performance measurements are really challenging when it comes to real life situations. One of them was a user experience while typing on a document. This presentation covers that how we can achieve reliable and repeatable performance tests by implementing clever tools. These tools allow us to find out what happens in the background when a lot of people are typing rapidly and what we can optimize out of it.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8696">Mert Tümer</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_editingsimulation.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_editingsimulation.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_editingsimulation:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_editingsimulation:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12805.php">Submit feedback</link>
        </links>
      </event>
      <event id="12881">
        <start>12:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_improvedcoverage</slug>
        <title>Improved coverage analysis for LibreOffice's CI</title>
        <subtitle>Our journey towards deeper integration of coverage analysis tools into Jenkins CI - a PrototypeFund project</subtitle>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Improved coverage analysis for LibreOffice's CI. Our journey towards deeper integration of coverage analysis tools into Jenkins CI - a PrototypeFund project&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2006">Thorsten Behrens</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_improvedcoverage/attachments/slides/5217/export/events/attachments/lotech_improvedcoverage/slides/5217/fosdem_2022_talk2.pdf">talk slides as PDF</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_improvedcoverage.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_improvedcoverage.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_improvedcoverage:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_improvedcoverage:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12881.php">Submit feedback</link>
        </links>
      </event>
      <event id="12707">
        <start>13:00</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_libreofficekit</slug>
        <title>LibreOfficeKit recent developments</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Come and hear about how LibreOffice can be used by other applications via its C++ API called LibreOfficeKit. Its primary use is for document conversion or editing the documents in Collabora Online.&lt;/p&gt;

&lt;p&gt;We are extending the LibreOfficeKit as necessary, and this presentation will talk about the recent developments there.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="317">Jan Holesovsky</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_libreofficekit.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_libreofficekit.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_libreofficekit:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_libreofficekit:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12707.php">Submit feedback</link>
        </links>
      </event>
      <event id="12762">
        <start>13:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_libreofficegtk4</slug>
        <title>LibreOffice GTK4 Port</title>
        <subtitle>A status update</subtitle>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Update on of the current state of the GTK4 port of LibreOffice with walk-through.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2068">Caolán McNamara</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_libreofficegtk4/attachments/slides/5187/export/events/attachments/lotech_libreofficegtk4/slides/5187/FOSDEM_2022_Gtk4">slides</attachment>
        </attachments>
        <links>
          <link href="https://">https://</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_libreofficegtk4.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_libreofficegtk4.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_libreofficegtk4:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_libreofficegtk4:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12762.php">Submit feedback</link>
        </links>
      </event>
      <event id="12764">
        <start>14:00</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_onlineperformance</slug>
        <title>Online performance</title>
        <subtitle>making collaborative editing quicker</subtitle>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Online performance wins making collaborative editing in your browser quicker.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Collabora Online has a novel model that allows re-using the core LibreOffice Technology to provide rich collaborative editing.  Recently we have been been focusing our development on improving the 'feel' and slickness of document editing as a key part of user experience. We have also been working on improving editing performance with larger numbers of concurrent active editors.&lt;/p&gt;

&lt;p&gt;Come and hear about the things that we've found and fixed, both in COOL and also in the LibreOffice core to improve interactivity and to make collaborative editing fly.&lt;/p&gt;</description>
        <persons>
          <person id="425">Michael Meeks</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_onlineperformance.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_onlineperformance.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_onlineperformance:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_onlineperformance:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12764.php">Submit feedback</link>
        </links>
      </event>
      <event id="12880">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_lowa</slug>
        <title>LOWA - LibreOffice WebAssembly</title>
        <subtitle>Most recent updates, working code, and ample stories of how we got to have LibreOffice run natively in a browser</subtitle>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;LOWA - LibreOffice WebAssembly. Most recent updates, working code, and ample stories of how we got to have LibreOffice run natively in a browser.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2006">Thorsten Behrens</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_lowa/attachments/slides/5218/export/events/attachments/lotech_lowa/slides/5218/fosdem_2022_wasm.pdf">talk slides as PDF</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_lowa.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_lowa.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_lowa:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_lowa:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12880.php">Submit feedback</link>
        </links>
      </event>
      <event id="12947">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_buildingcoolui</slug>
        <title>Building Collabora Online UI based on the LibreOffice components</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;JSDialog is a "framework" for sharing UI components between Collabora Online and LibreOffice. It was used to bring sidebar, notebookbar and dialogs to the web. It provides native HTML widgets connected to the original LibreOffice code, giving the user rich editing options even on a mobile devices. This talk is a short summary - briefly describing how it works and what is already done.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8794">Szymon Kłos</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_buildingcoolui/attachments/slides/5250/export/events/attachments/lotech_buildingcoolui/slides/5250/fosdem2022_building_ui">Building Collabora UI based on LibreOffice components</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_buildingcoolui.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_buildingcoolui.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_buildingcoolui:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_buildingcoolui:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12947.php">Submit feedback</link>
        </links>
      </event>
      <event id="12489">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_coolkubernetes</slug>
        <title>Collabora Online on kubernetes</title>
        <subtitle>Kubernetes setup &amp; deployment</subtitle>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Demonstration of how to deploy the online using kubernetes.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8574">Pranam Lashkari</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_coolkubernetes/attachments/slides/5246/export/events/attachments/lotech_coolkubernetes/slides/5246/Collabora_on_kubernetes_slides"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_coolkubernetes.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_coolkubernetes.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_coolkubernetes:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_coolkubernetes:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12489.php">Submit feedback</link>
        </links>
      </event>
      <event id="12862">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_coolasyncsaving</slug>
        <title>Collabora Online: Async-Saving Design and Testing</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Collabora Online enables viewing, editing, and the collaboration on documents, presentations, and spreadsheets from the convenience of a browser. This talk will explore the challenge of saving and uploading documents to the storage server in an asynchronous way, to improve user experience, better performance, and higher reliability and resiliency. The talk will cover both the design and the challenges of testing a highly critical component of a production product.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8763">Ashod Nakashian</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_coolasyncsaving/attachments/slides/5247/export/events/attachments/lotech_coolasyncsaving/slides/5247/Ash_Fosdem_2022_Dev_AsyncSave_Design.pdf">Collabora Online AsyncSave Design Ashod FOSDEM 2022</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_coolasyncsaving.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_coolasyncsaving.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_coolasyncsaving:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_coolasyncsaving:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12862.php">Submit feedback</link>
        </links>
      </event>
      <event id="12922">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.libreoffice</room>
        <slug>lotech_somethingaboutqa</slug>
        <title>Things you can test in a UITest</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Something about QA&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4341">Xisco Fauli</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_somethingaboutqa/attachments/slides/4938/export/events/attachments/lotech_somethingaboutqa/slides/4938/slides">slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_somethingaboutqa.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_somethingaboutqa.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_somethingaboutqa:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_somethingaboutqa:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12922.php">Submit feedback</link>
        </links>
      </event>
      <event id="12739">
        <start>17:00</start>
        <duration>00:20</duration>
        <room>D.libreoffice</room>
        <slug>lotech_macrodialog</slug>
        <title>Macro Dialog feature</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The implementation of a Macro Selector Dialog on client side to execute VBA macros on the server side.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8713">Henry Castro</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_macrodialog/attachments/slides/5254/export/events/attachments/lotech_macrodialog/slides/5254/Fosdem_macro_dialog_feature.odp">Macro Dialog feature</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_macrodialog.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_macrodialog.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_macrodialog:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_macrodialog:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12739.php">Submit feedback</link>
        </links>
      </event>
      <event id="12763">
        <start>17:20</start>
        <duration>00:40</duration>
        <room>D.libreoffice</room>
        <slug>lotech_odftoolkit</slug>
        <title>News from the ODF Toolkit</title>
        <subtitle/>
        <track>LibreOffice Technology</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;New ODF Toolkit releases have been released.
How can it help you? Where are we striving for?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;New ODF Toolkit releases have been published.
What's missing from the 1.0?
How can it help you? Where are we striving for?
What will be next? What are the synergies between ODF TC?
No incident having ODF Toolkit Co-maintainers and ODF TC Co-editors Michael Stahl and Svante Schubert lined up!&lt;/p&gt;</description>
        <persons>
          <person id="1853">Svante Schubert</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lotech_odftoolkit/attachments/slides/5263/export/events/attachments/lotech_odftoolkit/slides/5263/2022_FOSDEM_News_from_the_ODF_Toolkit_with_Notes.odp"/>
        </attachments>
        <links>
          <link href="https://tdf.github.io/odftoolkit/">ODF Toolkit website</link>
          <link href="https://github.com/tdf/odftoolkit">ODF Toolkit GitHub page</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_odftoolkit.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.libreoffice/lotech_odftoolkit.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#libreoffice-lotech_odftoolkit:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#libreoffice-lotech_odftoolkit:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12763.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.llvm">
    </room>
    <room name="D.mariadb">
    </room>
    <room name="D.matrix">
      <event id="12648">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.matrix</room>
        <slug>matrix_state_of_the_union</slug>
        <title>The Matrix State of the Union</title>
        <subtitle>What's the Matrix Core Team up to?</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Matrix core team is busier than ever, juggling hundreds of Matrix Spec Core Proposals and undergoing some major techtonic shifts as Matrix evolves into the ultimate secure decentralised communication network.  In this talk, we'll give a high-level survey of the state of the core project, including:
 * How we're ensuring that flagship clients are as attractive as possible to a mainstream audience - and why we will fail if we don't.
 * How we're making Matrix go &lt;em&gt;fast&lt;/em&gt; via v3 sync and fast room joins
 * How matrix-rust-sdk is becoming a flagship client SDK
 * How we're getting a full end-to-end security of the reference Matrix stack
 * How we're tackling abuse on the public Matrix network
 * How Matrix is evolving to use cases beyond chat.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="2951">Matthew Hodgson</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://matrix.org">Matrix.org</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_state_of_the_union.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_state_of_the_union.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_state_of_the_union:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_state_of_the_union:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12648.php">Submit feedback</link>
        </links>
      </event>
      <event id="12553">
        <start>10:30</start>
        <duration>00:20</duration>
        <room>D.matrix</room>
        <slug>matrix_next_gen_interfaces</slug>
        <title>The next generation of Matrix interfaces</title>
        <subtitle>How we're changing the face of bridge and bot integrations in Matrix</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Matrix has already got the solid framework of many bridge and bot implementations, but has always been missing that polish to make the bridges more accessible.&lt;/p&gt;

&lt;p&gt;In this talk, Will will explain how we're going to build our bridges with an all-new interactive interface and replacing old bot command interfaces with widget based interfaces.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7439">Will Hunt</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_next_gen_interfaces.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_next_gen_interfaces.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_next_gen_interfaces:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_next_gen_interfaces:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12553.php">Submit feedback</link>
        </links>
      </event>
      <event id="12396">
        <start>10:50</start>
        <duration>00:20</duration>
        <room>D.matrix</room>
        <slug>matrix_opsdroid</slug>
        <title>Opsdroid</title>
        <subtitle>Building a bot using Python3</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Opsdroid makes building bots easy with it's modular concept of Connectors, Matchers &amp;amp; Skills.
In this talk I want to showcase how easy it's to build bots using Opsdroid.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;We start with a simple "hello bot" and end with a Bot, which uses Rasa NLU (Natural Language Understanding), an AI based platform, to recognize the intent of a message.&lt;/p&gt;</description>
        <persons>
          <person id="7592">Oleg Fiksel</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/matrix_opsdroid/attachments/slides/4826/export/events/attachments/matrix_opsdroid/slides/4826/Opsdroid_at_FOSDEM_22.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://opsdroid.dev">Opsdroid Home</link>
          <link href="https://gitlab.com/olegfiksel/opsdroid-at-fosdem-22">Code</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_opsdroid.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_opsdroid.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_opsdroid:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_opsdroid:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12396.php">Submit feedback</link>
        </links>
      </event>
      <event id="12509">
        <start>11:10</start>
        <duration>00:30</duration>
        <room>D.matrix</room>
        <slug>matrix_events_uninitiatied</slug>
        <title>Events for the Uninitiated</title>
        <subtitle>A Junior's Guide to Events in Matrix</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Events are at the heart of the Matrix Protocol, but what are they? And how does the Protocol build on them to create rooms, room graphs, and other data structures? This talk aims to demystify some of these concepts, giving an overview of events, room event graphs, and associated structures. In the spirit of accessiblity, there will be an attempt to make the talk as approachable as possible for those without a ton of programming experience (although some basic knowledge will be helpful!). We will look at the Matrix specification and if time permits, may even dig into some code in Synapse. If you're interested in hacking on Matrix/Synapse but are newish to programming or intimidated by the core spec, or are just curious, this talk is for you!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8592">H. Shay</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_events_uninitiatied.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_events_uninitiatied.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_events_uninitiatied:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_events_uninitiatied:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12509.php">Submit feedback</link>
        </links>
      </event>
      <event id="12467">
        <start>11:40</start>
        <duration>00:30</duration>
        <room>D.matrix</room>
        <slug>matrix_fast_sync</slug>
        <title>Making /sync go fast</title>
        <subtitle>A deep-dive into Sync v3</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A deep-dive into Sync v3: a super-fast API to sync Matrix clients with their homeserver. The talk is broken up into a brief history of syncing in Matrix to set the scene before we dive into the problem space and explore how Sync v3 is different and how it addresses one of the most important and complex parts of the Client-Server API: syncing.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Sync v3 is the third iteration of the syncing protocol in Matrix. The first was the now-deprecated /initialSync + /events and the second, still in use today, is /sync. We'll explore why the protocol needed to change then and why the protocol needs to change again now. As part of this, we'll look at &lt;em&gt;how&lt;/em&gt; servers implement the /sync v2 API and the constraints they have to work with to explain why /sync can be so slow.&lt;/p&gt;

&lt;p&gt;Armed with this knowledge, we'll work out the aims/goals of a new hypothetical syncing protocol, along with the competing concerns around complexity, speed, bandwidth and flexibility. We'll then look at the Sync v3 proposal and explore the tradeoffs that were made in its design. This will be complemented with demos and diagrams throughout.&lt;/p&gt;</description>
        <persons>
          <person id="8517">Kegan Dougal</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/matrix-org/sliding-sync">Sync v3 proxy server</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_fast_sync.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_fast_sync.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_fast_sync:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_fast_sync:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12467.php">Submit feedback</link>
        </links>
      </event>
      <event id="12534">
        <start>12:10</start>
        <duration>01:00</duration>
        <room>D.matrix</room>
        <slug>matrix_rust_sdk</slug>
        <title>The matrix-rust-sdk</title>
        <subtitle>One SDK to rule them all</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Matrix (https://matrix.org) is an open protocol for secure, decentralised communication - defining an end-to-end-encrypted real-time communication layer for the open Web. Historically the network has been made up of newly written native Matrix clients, or bridges to 3rd party existing chat systems (e.g. Slack, Discord, Telegram).&lt;/p&gt;

&lt;p&gt;The matrix-rust-sdk is a modular Matrix client library, meant to be a robust implementation of the protocol, and to make even the most advanced features such as E2EE easy to use.
This talk will walk you through the design decisions and the tradeoffs that come with it, give you an overview of where we're at and where we're going with Web-Assembly, and finally what the future holds for the matrix-rust-sdk. Finally it will be connected to a real-life example of software using the matrix-rust-sdk: Fractal-Next.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Matrix (https://matrix.org) is an open protocol for secure, decentralised communication - defining an end-to-end-encrypted real-time communication layer for the open Web. Historically the network has been made up of newly written native Matrix clients, or bridges to 3rd party existing chat systems (e.g. Slack, Discord, Telegram).&lt;/p&gt;

&lt;p&gt;The matrix-rust-sdk is a modular Matrix client library, meant to be a robust implementation of the protocol, and to make even the most advanced features such as E2EE easy to use.&lt;/p&gt;

&lt;p&gt;It's a flexible library which can be used both to extend existing projects or to create new ones. It is notably used in the 18 years old IRC client WeeChat to teach it to speak Matrix. It has also been used as base for the re-write of GNOME's Matrix client Fractal.&lt;/p&gt;

&lt;p&gt;Thanks to its very modular nature, clients can either use the whole SDK, like WeeChat and Fractal do, or a sub-component. Element R uses matrix-rust-sdk's crypto crate via Kotlin bindings.&lt;/p&gt;

&lt;p&gt;This talk will walk you through the design decisions and the tradeoffs that come with it, give you an overview of where we're at and where we're going with Web-Assembly, and finally what the future holds for the matrix-rust-sdk. Finally it will be connected to a real-life example of software using the matrix-rust-sdk: Fractal-Next.&lt;/p&gt;

&lt;p&gt;Fractal is a popular Matrix chat client for the GNOME desktop which has been in development since 2017. Fractal was designed to work well for collaboration in large groups, such as free software projects.
For a long time there were two main areas that needed improvements: performance and maintainability were limited. What’s more, it lacked end-to-end encryption (E2EE) support.&lt;/p&gt;

&lt;p&gt;Over the course of 2021 we spent countless hours rewriting Fractal from scratch and now we are close to the first release. Fractal-next is built on top of the matrix-rust-sdk, a set of libraries that help to build Matrix clients. The client, still written in Rust, now uses GTK4. During development, the focus was on performance, maintainability and E2EE. And of course, we kept mobile support.&lt;/p&gt;</description>
        <persons>
          <person id="4974">Julian Sparber</person>
          <person id="8578">Damir Jelić</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_rust_sdk.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_rust_sdk.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_rust_sdk:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_rust_sdk:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12534.php">Submit feedback</link>
        </links>
      </event>
      <event id="12574">
        <start>13:10</start>
        <duration>00:05</duration>
        <room>D.matrix</room>
        <slug>matrix_mmo_browser</slug>
        <title>Building an MMO browser game on Matrix</title>
        <subtitle>Managing auth and saves in Matrix</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I'm working on a Massive Multiplayer Online (MMO) browser game which uses Matrix for authentication, authorization and storing save states.
Lobbies and characters are managed as Matrix rooms which allows players to have a copy of their character's data at all times, migrate it to other Matrix accounts or share a character with friends.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;What if games allowed you to really own your online characters?
If an online video game shuts down, your character is gone.
All progress, all contacts, all items – lost to you and not available for migration.&lt;/p&gt;

&lt;p&gt;I'm building a tiny proof of concept browser game where you log in with your Matrix account.
All your characters are represented by Matrix rooms and you can migrate them to other Matrix accounts and other gaming servers.&lt;/p&gt;

&lt;p&gt;Instead of sending all communication via Matrix this concept uses a public server software and central gaming servers (HTTP and websockets in this case).
Upon character creation, a game server invites you to your character's room. Every time your character changes the server updates a state event.
If the server gets shutdown, it's easy to set up a new server which allows to migrate character rooms from the old server.
Furthermore, players can analyze their characters without the need to contact the gaming server.&lt;/p&gt;</description>
        <persons>
          <person id="6668">Christian Paul</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://city.chrpaul.de">Demo server</link>
          <link href="https://gitlab.com/jaller94/hacker-town">Source code</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_mmo_browser.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_mmo_browser.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_mmo_browser:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_mmo_browser:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12574.php">Submit feedback</link>
        </links>
      </event>
      <event id="12570">
        <start>13:15</start>
        <duration>00:05</duration>
        <room>D.matrix</room>
        <slug>matrix_chat_stat</slug>
        <title>ChatStat - An R package for Matrix stats</title>
        <subtitle>Shiny stats for your community goodness</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Remarkably, the Matrix community still does not seem to have a equivalent to things like the venerable mIRCstats or PISG packages (which generate data based on a local IRC log). In this lightning talk, I'll present a new package I'm working on to present similar data for Matrix rooms. We'll have a quick demo and lots of pretty graphs to look at.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;ChatStat aims initially to replicate the same kind of HTML report that these older packages created, and we'll show how to use it on your own host to generate stats for your rooms using the Matrix API.&lt;/p&gt;

&lt;p&gt;Since Matrix has bridges, we can also directly gather data on these from connected rooms (e.g. the screenshot shows the split between Matrix and IRC users over a 2 week period) and we will show how to accomplish this too.&lt;/p&gt;

&lt;p&gt;Lastly we'll talk about the underlying data structure and how to use it to build new graphs that ChatStat does not yet do itself.&lt;/p&gt;

&lt;p&gt;Who is this talk for: Anyone who runs one or more Matrix rooms and wishes to generate visualisations of them. Or anyone who likes pretty graphs :)&lt;/p&gt;</description>
        <persons>
          <person id="1309">Greg Sutcliffe</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/GregSutcliffe/ChatStat">GitHub page</link>
          <link href="https://matrix.to/#/#rmatrixstats:matrix.org">Matrix Discussion Room</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_chat_stat.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_chat_stat.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_chat_stat:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_chat_stat:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12570.php">Submit feedback</link>
        </links>
      </event>
      <event id="12511">
        <start>13:20</start>
        <duration>00:05</duration>
        <room>D.matrix</room>
        <slug>matrix_cinny</slug>
        <title>Cinny</title>
        <subtitle>elegant, modern and secure matrix client</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk is about a Matrix client called &lt;a href="https://cinny.in/"&gt;Cinny&lt;/a&gt;. It is built using reactjs on the top of matrix-js-sdk.&lt;/p&gt;

&lt;p&gt;The main focus behind making Cinny is to have a client that is simple, elegant and doesn't feel heavy on end user. Cinny was launched publicly in end of July 2021 and since then it has matured a lot. Cinny has support for end-to-end encryption with options to import and export encryption keys. It also has basic support for Spaces (coolest feature of Matrix). Cinny also has ton of other features most notably full UIAA (User-Interactive Authentication API including SSO Login), carefully crafted themes, Rich replies, Reactions, Markdown and the list goes on.&lt;/p&gt;

&lt;p&gt;Our roadmap also includes some other great features in near future; such as room settings, full support for spaces and later a responsive interface that also support mobile screens. We are also working on standalone app of Cinny using Tauri (exciting thing here is that app size is considerably less and doesn't require to have chromium to work).&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8555">Ajay Bura</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/matrix_cinny/attachments/slides/4899/export/events/attachments/matrix_cinny/slides/4899/cinny_slides.pptx">Slides</attachment>
        </attachments>
        <links>
          <link href="https://cinny.in">Project website </link>
          <link href="https://github.com/ajbura/cinny">Github repository</link>
          <link href="https://matrix.to/#/#cinny:matrix.org">Matrix room</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_cinny.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_cinny.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_cinny:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_cinny:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12511.php">Submit feedback</link>
        </links>
      </event>
      <event id="12543">
        <start>13:25</start>
        <duration>00:05</duration>
        <room>D.matrix</room>
        <slug>matrix_collabs</slug>
        <title>Collaborative Apps over Matrix using the Collabs Library</title>
        <subtitle/>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;I will demo Google Docs-style collaborative apps that communicate entirely through Matrix. This means they inherit Matrix's nice properties, including E2EE, decentralization, and user control.&lt;/p&gt;

&lt;p&gt;Under the hood, the apps use Collabs, a TypeScript library I'm developing. Collabs provides collaborative data structures - specifically CRDTs. These are classes that have APIs like ordinary data structures (Map, Array, etc.) but also automatically sync between clients, guaranteeing eventual consistency. I will briefly describe the unique features of Collabs and show what it's like to program an app using the library.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8563">Matthew Weidner</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/matrix_collabs/attachments/slides/5190/export/events/attachments/matrix_collabs/slides/5190/fosdem_22_matrix_collabs.pdf">Collabs Slides PDF (no GIFs)</attachment>
        </attachments>
        <links>
          <link href="https://www.npmjs.com/package/@collabs/collabs">Collabs npm package</link>
          <link href="https://compoventuals-tests.herokuapp.com/">Demo site</link>
          <link href="https://docs.google.com/presentation/d/12mk5mmtri69orMBB3sdho5pXUltDXFpOn-44bcY9aaI/edit?usp=sharing">Slides (with GIFs)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_collabs.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_collabs.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_collabs:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_collabs:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12543.php">Submit feedback</link>
        </links>
      </event>
      <event id="12537">
        <start>13:30</start>
        <duration>00:05</duration>
        <room>D.matrix</room>
        <slug>matrix_diy_photoframe</slug>
        <title>Create a DIY photoframe using matrix</title>
        <subtitle>How to create a DIY photoframe with a raspi and transfer the photos via matrix</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this presentation I'd like to show you how I created a little DIY photoframe with a raspberry pi and an old TV-screen and how I extended the photo transfer using matrix.
There is already a nice project "photOS" which is a lightweight linux for a DIY photoframe.
Thanks to opensource software I was able to extend it in order to transfer the files not via WebDAV but with matrix having end-to-end encryption as well.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8618">dirk</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/avanc/photOS">The photOS linux repo</link>
          <link href="https://github.com/avanc/photOS-matrix">The photOS fork which supports matrix</link>
          <link href="https://github.com/universalappfactory/matrix-photos">The photOS matrix client</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_diy_photoframe.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_diy_photoframe.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_diy_photoframe:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_diy_photoframe:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12537.php">Submit feedback</link>
        </links>
      </event>
      <event id="12581">
        <start>13:35</start>
        <duration>00:05</duration>
        <room>D.matrix</room>
        <slug>matrix_custom_stickers</slug>
        <title>Custom Stickers and Emotes in Matrix!</title>
        <subtitle>MSC2545 Demo</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;To some stickers and emotes might look nonsensical and disrupting conversations. For others it is a tool to build a community around. In this talk I will present a &lt;a href="https://github.com/matrix-org/matrix-doc/pull/2545"&gt;Matrix Spec Change proposal&lt;/a&gt;, that allows you to provide your own sticker and emote packs for your community  and will compare it to the other proposals. I'll describe how you can share them and create your own. I'll demo the implementation in 1 (or maybe 2?) clients, give an explanation of how they work and how they might evolve in the future.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8569">Nicolas Werner</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/matrix-org/matrix-doc/pull/2545">The MSC</link>
          <link href="https://fosstodon.org/web/@deepbluev7/106709661475400641">Old and bad demo I did</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_custom_stickers.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_custom_stickers.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_custom_stickers:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_custom_stickers:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12581.php">Submit feedback</link>
        </links>
      </event>
      <event id="12548">
        <start>13:40</start>
        <duration>00:05</duration>
        <room>D.matrix</room>
        <slug>matrix_decentralized_annotations</slug>
        <title>Decentralized Collaborative Annotations using Matrix</title>
        <subtitle/>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk showcases Matrix Highlight, a tool built on top of the Matrix protocol to collaboratively annotate and comment on pages on the internet. By building on top of Matrix, we get decentralized, federated, and open web (or more) annotation. This talk will cover a demonstration, using Matrix events for non-messaging purposes, and the benefits of building on Matrix.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8625">Daniel Fedorin</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/DanilaFe/matrix-highlight/">GitHub link for the project</link>
          <link href="https://danilafe.com/blog/introducing_highlight/">Introductory blog post</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_decentralized_annotations.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_decentralized_annotations.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_decentralized_annotations:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_decentralized_annotations:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12548.php">Submit feedback</link>
        </links>
      </event>
      <event id="12532">
        <start>13:45</start>
        <duration>00:05</duration>
        <room>D.matrix</room>
        <slug>matrix_fluffychat</slug>
        <title>FluffyChat</title>
        <subtitle>Little showcase of the cutest messenger in the [matrix]</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;FluffyChat is a cute and easy to use matrix client for all platforms. The app has a Telegram/Signal-like design and user experience and is published as free software. In this lighting talk I would like to show the features and how it is possible to write an open source app, which makes fun.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8615">krille</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://fluffychat.im">FluffyChat website</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_fluffychat.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_fluffychat.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_fluffychat:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_fluffychat:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12532.php">Submit feedback</link>
        </links>
      </event>
      <event id="12536">
        <start>13:50</start>
        <duration>00:05</duration>
        <room>D.matrix</room>
        <slug>matrix_command_control</slug>
        <title>Matrix for Command and Control Information Systems</title>
        <subtitle/>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;To enable collaborative work, we will extend our Command and Control Informations System ODIN (https://github.com/syncpoint/ODIN) with the ability to share its data by employing Matrix spaces and rooms&lt;/p&gt;</abstract>
        <description>&lt;p&gt;ODIN uses the concepts of projects and layers that contain geo-features. We will show how we map these concepts to spaces and rooms in order to enable collaboration between an arbitrary number of users. Whenever a feature gets changed by one user, we publish a message that contains an action in the corresponding room so other users can apply these actions to their local copy.&lt;/p&gt;</description>
        <persons>
          <person id="8611">Thomas Halwax</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/matrix_command_control/attachments/slides/5147/export/events/attachments/matrix_command_control/slides/5147/ODIN_and_Matrix_FOSDEM22.pdf">ODIN Open source C2IS Replication with Matrix</attachment>
        </attachments>
        <links>
          <link href="https://github.com/syncpoint/ODIN">ODIN project page on GitHub</link>
          <link href="https://odin.syncpoint.io">ODIN project page</link>
          <link href="https://matrix.to/#/#odin_c2is:matrix.org">ODIN matrix space</link>
          <link href="https://">https://</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_command_control.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_command_control.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_command_control:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_command_control:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12536.php">Submit feedback</link>
        </links>
      </event>
      <event id="12502">
        <start>13:55</start>
        <duration>00:05</duration>
        <room>D.matrix</room>
        <slug>matrix_power_worker</slug>
        <title>Matrix for Worker Power</title>
        <subtitle>Introduction to Wobbly</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;How a movement communicates determines the structure and success of that movement. It could even be said that a movement is the way that it communicates. The labour movement has existed for centuries. Can Matrix increase the movement's power in the next decade and beyond?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Wobbly is a chat app built on Matrix designed for bottom-up worker organising to build a democratic economy and society.&lt;/p&gt;

&lt;p&gt;We're excited about the potential of the Spaces API and the custom JSON events system to build a very powerful tool for democratic self-organising spaces.&lt;/p&gt;

&lt;p&gt;While the project has existed in some form since 2015, we started using Matrix at the start of 2020 and have made much more progress in that time.&lt;/p&gt;</description>
        <persons>
          <person id="8583">John Evans</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/King-Mob/wobbly-pwa">Wobbly matrix app</link>
          <link href="https://wobbly.app">Wobbly site</link>
          <link href="https://web.wobbly.app">Deployed version of wobbly matrix app</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_power_worker.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_power_worker.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_power_worker:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_power_worker:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12502.php">Submit feedback</link>
        </links>
      </event>
      <event id="12578">
        <start>14:10</start>
        <duration>00:30</duration>
        <room>D.matrix</room>
        <slug>matrix_ansible</slug>
        <title>Ansible + Matrix: Through The Looking Glass</title>
        <subtitle>A 6 month reflection on the Ansible Community's journey with Matrix</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In August 2021, the Ansible community &lt;a href="https://github.com/ansible-community/community-topics/issues/36"&gt;voted&lt;/a&gt; to accept Matrix as an official chat platform (alongside and equal to IRC). This marked a major evolution in the communication of the project, and opened the door to more ways for us to connect with each other. It also followed a substantial amount of planning from the community team, in terms of architecture we had in mind. In this talk, we'll take a look back over our original architecture &amp;amp; proposal, how the rollout has gone, and where we think we're going next.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;There's much we &lt;em&gt;could&lt;/em&gt; cover in this talk, but we'll definitely have content on the 2-homesever architecture we used (and why), on how adoption is going with our community (bridges will feature here,  at least) and community building &amp;amp; promotion (expect armchair-sociology while I talk about rich interaction mediums, but also things like newsrooms, interaction fragmentation, etc). I'll also be attempting to gather some feedback from our community to present as well.&lt;/p&gt;

&lt;p&gt;Who is this talk for: We hope it'll be of interest to anyone thinking of recommending Matrix for their community - whether a FOSS community, or more generally, there's things to think about first and arguments that can be re-used. There will also be interest for existing Matrix users too, in terms of lessons learned and wishlist features for the future.&lt;/p&gt;</description>
        <persons>
          <person id="1309">Greg Sutcliffe</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://matrix.to/#/#space:ansible.com">Ansible Community Space</link>
          <link href="https://docs.ansible.com/ansible/latest/community/communication.html#ansible-community-on-matrix">Ansible Community Docs</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_ansible.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_ansible.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_ansible:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_ansible:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12578.php">Submit feedback</link>
        </links>
      </event>
      <event id="12361">
        <start>14:40</start>
        <duration>00:30</duration>
        <room>D.matrix</room>
        <slug>matrix_moderation</slug>
        <title>All things with moderation</title>
        <subtitle>All about moderation in Matrix</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;So you want to moderate your Matrix room, or perhaps your homeserver? You're in the right place.
In this presentation, we'll talk about both the core concepts of federated moderation in Matrix and the main moderation tools. Expect to hear about power levels, redactions, quarantine, abuse reports, Mjölnir and plans for the near future!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3210">David Teller</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_moderation.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_moderation.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_moderation:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_moderation:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12361.php">Submit feedback</link>
        </links>
      </event>
      <event id="12463">
        <start>15:10</start>
        <duration>00:30</duration>
        <room>D.matrix</room>
        <slug>matrix_p2p_pinecone</slug>
        <title>Growing Pinecones for P2P Matrix</title>
        <subtitle>The journey so far of building an overlay network</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The success of P2P Matrix depends on an overlay network which can provide good connectivity between users, and scale appropriately. For that we built Pinecone, an implementation of a new routing scheme called "SNEK", along with tools to simulate and to measure various properties such as routing table size and convergence times. This talk will explore some of the core design elements and the challenges of building a decentralised routing protocol.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8015">Neil Alexander</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_p2p_pinecone.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_p2p_pinecone.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_p2p_pinecone:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_p2p_pinecone:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12463.php">Submit feedback</link>
        </links>
      </event>
      <event id="12391">
        <start>15:40</start>
        <duration>00:30</duration>
        <room>D.matrix</room>
        <slug>matrix_filesystem</slug>
        <title>Self-sovereign end-to-end encrypted file storage on Matrix</title>
        <subtitle>How we built a file system on top of Matrix</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Matrix is an open source project run by the non-profit Matrix.org Foundation dedicated to building an open protocol and communication network for decentralised, encrypted communication - providing a viable open alternative to WhatsApp, Slack, Discord and other proprietary communication silos.&lt;/p&gt;

&lt;p&gt;During 2021 we have been exploring how the Matrix protocol can be used for decentralised, end-to-end encrypted online document storage and collaboration as an alternative to centralised proprietary services such as Dropbox and Box. In this talk we will show off our progress so far and the further work that we have planned.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Matrix is essentially a generic mechanism for replicating structured data over a decentralised network of untrusted servers.  The first use cases of Matrix have focused on instant messaging and VoIP, but during 2021 we’ve been experimenting with replicating different types of structured data - such as MSC3089 (https://github.com/matrix-org/matrix-doc/blob/travis/msc/trees/proposals/3089-file-tree-structures.md), which models each Matrix room as a directory, which can contain subdirectories by acting as a Matrix Space, which in turn can contain files as normal Matrix file uploads described by appropriate state events.  We’ve also been looking at further expressing the file data as structured trees of Matrix events.&lt;/p&gt;

&lt;p&gt;Meanwhile, the need for self-sovereign file-storage and collaboration systems is growing ever more obvious, given the risks of trusting your data unilaterally to a proprietary and typically unencrypted 3rd party cloud service. However, there is currently a trade off between the typical productivity gains from non-privacy centric online collaboration versus the more limited pro-privacy solutions currently available.&lt;/p&gt;

&lt;p&gt;Can Matrix support the next generation of privacy-centric collaboration applications? Providing document and file storage capabilities is one of the areas we’re looking at.&lt;/p&gt;

&lt;p&gt;Topics that we will cover:
* File and folder semantics
* Version history
* Sharing and access control
* Document editing
* Use cases: demos
* Matrix protocol specification work to standardise approach and support interoperability
* Files SDK for JavaScript to make it easy to get started
* Next steps&lt;/p&gt;</description>
        <persons>
          <person id="8514">Hugh Nimmo-Smith</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://matrix.org">Matrix</link>
          <link href="https://github.com/matrix-org/matrix-doc/pull/3089">MSC3089: File tree structures</link>
          <link href="https://github.com/matrix-org/matrix-files-sdk">matrix-files-sdk npm</link>
          <link href="https://github.com/vector-im/files-sdk-demo">Web demo using matrix-files-sdk</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_filesystem.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_filesystem.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_filesystem:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_filesystem:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12391.php">Submit feedback</link>
        </links>
      </event>
      <event id="12572">
        <start>16:10</start>
        <duration>00:30</duration>
        <room>D.matrix</room>
        <slug>matrix_threading</slug>
        <title>Mission: threading for all</title>
        <subtitle/>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Our mission,  if we choose to accept it, is to expand the capabilities of Matrix and Element. Driven by user needs and a desire to deliver threads through teamwork...&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In the past few months we were on a mission to bring threading to Matrix.
We first wanted to discover how suited to this problem the current protocol is, and to better understand the users' expectations.
It soon became clear that we would have to make updates to the specification in order to deliver the experience we think will make this feature successful&lt;/p&gt;</description>
        <persons>
          <person id="8630">Germain Souquet</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_threading.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_threading.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_threading:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_threading:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12572.php">Submit feedback</link>
        </links>
      </event>
      <event id="12370">
        <start>16:40</start>
        <duration>00:30</duration>
        <room>D.matrix</room>
        <slug>matrix_extend_synapse</slug>
        <title>Beyond the Matrix: Extend the capabilities of your Synapse homeserver</title>
        <subtitle>How to add custom features to Synapse with modules</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Synapse is the main Matrix homeserver implementation, and is maintained by the Matrix.org Foundation. One of the lesser-known features of Synapse is its module system, which allows any developer to write custom functionalities for it, and to extend its capabilities beyond the scope of the Matrix specification.&lt;/p&gt;

&lt;p&gt;In this talk, I will cover the current state of Synapse's module system, which has recently been subject to a big overhaul, as well as how to write and use a simple module.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7518">Brendan Abolivier</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/matrix_extend_synapse/attachments/slides/4881/export/events/attachments/matrix_extend_synapse/slides/4881/FOSDEM_2022_Beyond_the_Matrix.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://matrix-org.github.io/synapse/latest/modules/index.html">Documentation</link>
          <link href="https://github.com/matrix-org/synapse/blob/master/synapse/module_api/__init__.py">ModuleApi class and documentation</link>
          <link href="https://github.com/matrix-org/synapse-module-cookiecutter-template">Module template</link>
          <link href="https://www.youtube.com/watch?v=c6s7O3j5998">Matrix Live on Synapse modules</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_extend_synapse.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_extend_synapse.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_extend_synapse:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_extend_synapse:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12370.php">Submit feedback</link>
        </links>
      </event>
      <event id="12510">
        <start>17:10</start>
        <duration>00:30</duration>
        <room>D.matrix</room>
        <slug>matrix_mls</slug>
        <title>MLS meets Matrix</title>
        <subtitle/>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;MLS (Messaging Layer Security) is an upcoming IETF standard for messaging systems.  In this talk, I will discuss some of the work in integrating MLS with Matrix.  This will include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;why we would want to use MLS&lt;/li&gt;
&lt;li&gt;making MLS work in a decentralised messaging system&lt;/li&gt;
&lt;li&gt;how MLS concepts can fit into Matrix&lt;/li&gt;
&lt;li&gt;what will be needed to migrate to MLS&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="8495">Hubert Chathi</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.youtube.com/watch?v=xOMUG__uEjc">Introduction to how MLS works</link>
          <link href="https://gitlab.matrix.org/matrix-org/mls-ts/-/blob/decentralised2/decentralised.org">Notes on how to use MLS in a decentralised setting</link>
          <link href="https://gitlab.matrix.org/matrix-org/mls-ts">My TypeScript implementation of MLS (Decentralised version in decentralised2 branch)</link>
          <link href="https://www.uhoreg.ca/documents/fosdem-2022/__/index.html">Slides</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_mls.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_mls.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_mls:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_mls:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12510.php">Submit feedback</link>
        </links>
      </event>
      <event id="12650">
        <start>17:40</start>
        <duration>00:20</duration>
        <room>D.matrix</room>
        <slug>matrix_metaverse</slug>
        <title>Native Group VoIP and Metaverse on Matrix</title>
        <subtitle>Building the Matrix with Matrix</subtitle>
        <track>Matrix.org Foundation &amp; Community</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk we'll explain how we've added native decentralized E2E encrypted group video calling to Matrix via MSC3401 (https://github.com/matrix-org/matrix-doc/blob/matthew/group-voip/proposals/3401-group-voip.md), and how this not only provides "decentralized Zoom" style functionality for Matrix, but can also be used as the voice, video and realtime gameplay backbone for building a genuinely decentralized, equitable, free and open piece of the Metaverse on top of Matrix.&lt;/p&gt;

&lt;p&gt;We'll go over how 1 to 1 calls work in Matrix today, our Jitsi widget we've used for group calls so far, and the changes we've made to support native group calls in Matrix. We'll also show off some early concepts for our "Metaverse on Matrix" project, Third Room. Which uses this group call work as well as many other open standards to build a platform for virtual worlds on top of Matrix rooms.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8561">Robert Long</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://matrix.org">Matrix.org</link>
          <link href="https://github.com/matrix-org/matrix-doc/blob/matthew/group-voip/proposals/3401-group-voip.md">MSC3401</link>
          <link href="https://omigroup.org">Open Metaverse Interoperability Group</link>
          <link href="https://github.com/vector-im/matrix-video-chat">Matrix Video Chat Repo</link>
          <link href="https://github.com/thirdroom/thirdroom">Third Room Repo</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_metaverse.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.matrix/matrix_metaverse.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#matrix-matrix_metaverse:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#matrix-matrix_metaverse:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12650.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.microkernel">
    </room>
    <room name="D.monitoring">
      <event id="13551">
        <start>10:00</start>
        <duration>00:10</duration>
        <room>D.monitoring</room>
        <slug>moniobserv2022open</slug>
        <title>Monitoring and Observability devroom: Opening</title>
        <subtitle/>
        <track>Monitoring and Observability</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Opening!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="497">Richard Hartmann</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.monitoring/moniobserv2022open.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/moniobserv2022open.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-moniobserv2022open:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-moniobserv2022open:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13551.php">Submit feedback</link>
        </links>
      </event>
      <event id="12803">
        <start>10:10</start>
        <duration>00:40</duration>
        <room>D.monitoring</room>
        <slug>adapting_otel</slug>
        <title>Adopting OpenTelemetry and its collector</title>
        <subtitle/>
        <track>Monitoring and Observability</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this session, we’ll see why we adopted OpenTelemetry &amp;amp; its collector for an internal platform at Ubisoft - to collect/process/export all our logs, metrics, and traces.
We’ll explain how we handled the required mindset change: why people should instrument more their code, and how to onboard them.
And of course, we’ll talk about the benefits of fully adopting OpenTelemetry.&lt;/p&gt;

&lt;p&gt;The intended audience is people who want to adopt OpenTelemetry, or who are already using part of it - for example the SDK for tracing - and are considering a full switch.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6553">Vincent Behar</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/adapting_otel/attachments/slides/4975/export/events/attachments/adapting_otel/slides/4975/adopting_opentelemetry.pdf">slides</attachment>
        </attachments>
        <links>
          <link href="https://opentelemetry.io/">The OpenTelemetry project</link>
          <link href="https://github.com/open-telemetry/opentelemetry-collector">The OpenTelemetry Collector</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/adapting_otel.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/adapting_otel.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-adapting_otel:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-adapting_otel:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12803.php">Submit feedback</link>
        </links>
      </event>
      <event id="12400">
        <start>10:50</start>
        <duration>00:40</duration>
        <room>D.monitoring</room>
        <slug>multi_dc_cloud_native_observability</slug>
        <title>Bootstrapping a multi dc cloud native observability stack</title>
        <subtitle/>
        <track>Monitoring and Observability</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A gentle introduction to Observability and how to setup a highly available monitoring platform across multiple datacenters.&lt;/p&gt;

&lt;p&gt;During this talk we will investigate how we can setup and monitor an monitoring setup across 2 DCs using Prometheus, Loki, Tempo, Alertmanager and Grafana. monitoring some services with some lessons learned along the way.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6629">Bram Vogelaar</person>
        </persons>
        <attachments>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/multi_dc_cloud_native_observability/attachments/paper/5085/export/events/attachments/multi_dc_cloud_native_observability/paper/5085/BootstrappingMultiDCObservabilityStack_fosdem.pdf">Bootstrapping a multi-DC Observability Stack</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.monitoring/multi_dc_cloud_native_observability.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/multi_dc_cloud_native_observability.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-multi_dc_cloud_native_observability:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-multi_dc_cloud_native_observability:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12400.php">Submit feedback</link>
        </links>
      </event>
      <event id="12768">
        <start>11:30</start>
        <duration>00:40</duration>
        <room>D.monitoring</room>
        <slug>pyroscope</slug>
        <title>Introduction to Continuous Profiling using Pyroscope</title>
        <subtitle>How to debug performance issues using profilers</subtitle>
        <track>Monitoring and Observability</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Profiling is an effective way of understanding which parts of your application are consuming the most resources. Traditionally, logs, metrics and traces have been considered the three pillars of observability, but more recently profiling has emerged as a fourth pillar to be used alongside these other observability tools.&lt;/p&gt;

&lt;p&gt;Continuous Profiling, in particular, adds a dimension of time that allows you to understand your system’s resource usage (i.e. CPU, Memory, etc.) over time and gives you the ability to locate, debug, and fix issues related to performance.&lt;/p&gt;

&lt;p&gt;In this talk, we'll present Pyroscope, an Open Source Continuous Profiling platform, explain the particular challenges it needs to tackle and showcase how it can be used to analyze and fix performance bottlenecks:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Describe what Continuous Profiling is and what it brings to the observability universe.&lt;/li&gt;
&lt;li&gt;Present Pyroscope, an Open Source Continuous Profiling platform, on a high level.&lt;/li&gt;
&lt;li&gt;Dig deeper into Pyroscope's internals, explaining the particularities of its storage engine and how it allows doing Continuous Profiling at scale.&lt;/li&gt;
&lt;li&gt;Showcase specific use cases and examples where profiling can be and has been used to detect, analyze and fix performance bottlenecks.&lt;/li&gt;
&lt;/ul&gt;
</abstract>
        <description></description>
        <persons>
          <person id="8709">Ryan Perry</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/pyroscope-io/pyroscope">Pyroscope github repo</link>
          <link href="https://docs.google.com/presentation/d/1UTrt9OyCgC8t1dk2x_m3h9nXMdXQt8_iDNj24UomClU/edit#slide=id.p">Presentation Slides</link>
          <link href="https://github.com/pyroscope-io/pyroscope/blob/main/docs/storage-design.md">Pyroscope storage design</link>
          <link href="https://www.brendangregg.com/flamegraphs.html">Brendan greg flamegraph post</link>
          <link href="https://github.com/parca-dev/parca">Parca github repo</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/pyroscope.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/pyroscope.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-pyroscope:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-pyroscope:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12768.php">Submit feedback</link>
        </links>
      </event>
      <event id="12754">
        <start>13:00</start>
        <duration>00:40</duration>
        <room>D.monitoring</room>
        <slug>monitoring_kafka_using_ebpf</slug>
        <title>Monitoring Kafka without instrumentation using eBPF</title>
        <subtitle>A talk about Pixie, Kafka and what's next in observability</subtitle>
        <track>Monitoring and Observability</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this session, we’ll see eBPF monitoring in action applied to the Kafka world as an example of a complex Java application: identify Kafka consumers, producers, and brokers, see how they interact with each other and how many resources they consume. We'll even show how to measure consumer lag without external components. If you want to know what’s next in Java and Kafka observability in Kubernetes, this session is for you.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Imagine a world where you can access metrics, events, traces, and logs in seconds without changing code. Even more, a world where you can run scripts to debug metrics as code. In this session, you will learn about eBPF, a powerful technology with origins in the Linux kernel that holds the potential to fundamentally change how Networking, Observability, and Security are delivered.&lt;/p&gt;

&lt;p&gt;We’ll see eBPF in action applied to the Kafka world using Pixie: we’ll identify Kafka consumers, producers, and brokers, see how they interact with each other and how many resources they consume. We'll even learn how to measure consumer lag without external components. If you want to know what’s next in Kafka observability, this session is for you.&lt;/p&gt;</description>
        <persons>
          <person id="8722">Anton Rodriguez</person>
          <person id="8951">Ruizhe Cheng</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.monitoring/monitoring_kafka_using_ebpf.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/monitoring_kafka_using_ebpf.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-monitoring_kafka_using_ebpf:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-monitoring_kafka_using_ebpf:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12754.php">Submit feedback</link>
        </links>
      </event>
      <event id="13214">
        <start>13:40</start>
        <duration>00:40</duration>
        <room>D.monitoring</room>
        <slug>periskop</slug>
        <title>Periskop: Exception Monitoring at Scale</title>
        <subtitle>A pull-based exception monitoring service inspired by Prometheus</subtitle>
        <track>Monitoring and Observability</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk is aimed for engineers operating in distributed environments (or microservices) interested in  monitoring exceptions at scale. We introduce the open source project "Periskop", a pull-based exception monitoring service built at SoundCloud and inspired by Prometheus.&lt;/p&gt;</abstract>
        <description>&lt;ul&gt;
&lt;li&gt;What problems did we encounter with the traditional push-based model for exception monitoring.

&lt;ul&gt;
&lt;li&gt;Thundering herd issues with bad deployments&lt;/li&gt;
&lt;li&gt;Difficulty navigating large volumes of logs for identifying exceptions&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;An alternative pull-based model that scales well with the number of exceptions and instances.

&lt;ul&gt;
&lt;li&gt;Aggregation + sampling for concrete occurrences&lt;/li&gt;
&lt;li&gt;Limitations and trade-offs (short lived processes and fork-based application servers)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;An implementation of such model into the open source project "Periskop"

&lt;ul&gt;
&lt;li&gt;Initial Development&lt;/li&gt;
&lt;li&gt;Server and client-libraries&lt;/li&gt;
&lt;li&gt;Newly added features and roadmap (push-gateway, federation, time series visualization, integrations)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="8853">Jorge Creixell</person>
          <person id="8898">Marc Tuduri</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/periskop/attachments/slides/5129/export/events/attachments/periskop/slides/5129/Periskop_2022_FOSDEM_Slides.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/periskop-dev">Periskop-Dev Org</link>
          <link href="https://periskop-dev.github.io/periskop/">Main Project</link>
          <link href="https://developers.soundcloud.com/blog/periskop-exception-monitoring-service">Original Blog Post</link>
          <link href="https://developers.soundcloud.com/blog/periskop-in-2022">What's New with Periskop in 2022 Blog Post</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/periskop.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/periskop.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-periskop:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-periskop:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13214.php">Submit feedback</link>
        </links>
      </event>
      <event id="13524">
        <start>14:20</start>
        <duration>00:40</duration>
        <room>D.monitoring</room>
        <slug>cloud_native_profiling</slug>
        <title>Profiling in the cloud-native era</title>
        <subtitle/>
        <track>Monitoring and Observability</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Continuous profiling is a widely used practice at Google but has only recently started gaining popularity in the Observability space, however, resources on this topic are still rare compared to other observability signals especially on open source projects.
This talk intends to educate the wider community about the possibilities of continuous profiling, and give a glimpse into open-source tooling allowing everyone to join in on the practice and enabling everyone to build better software.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;For years Google has consistently been able to cut down multiple percentage points in their fleet-wide resource usage every quarter, using techniques described in their “Google-Wide Profiling” paper. Ad-hoc profiling has long been part of the developer’s toolbox to analyze CPU and memory usage of a running process, however, through continuous profiling, the systematic collection of profiles, entirely new workflows suddenly become possible.&lt;/p&gt;

&lt;p&gt;Matthias will start this talk with an introduction to profiling with Go and demonstrate via Parca - an open-source continuous profiling project - how continuous profiling allows for an unprecedented fleet-wide understanding of code at production runtime.&lt;/p&gt;

&lt;p&gt;Attendees will learn how to continuously profile code to help guide building robust, reliable, and performant software and reduce cloud spend systematically in various languages.&lt;/p&gt;</description>
        <persons>
          <person id="5942">Matthias Loibl</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://research.google/pubs/pub36575/">Google-Wide Profiling: A Continuous Profiling Infrastructure for Data Centers</link>
          <link href="https://www.parca.dev/">Parca - Open Source infrastructure-wide continuous profiling</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/cloud_native_profiling.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/cloud_native_profiling.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-cloud_native_profiling:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-cloud_native_profiling:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13524.php">Submit feedback</link>
        </links>
      </event>
      <event id="12900">
        <start>15:40</start>
        <duration>00:40</duration>
        <room>D.monitoring</room>
        <slug>unikraft</slug>
        <title>Unikraft Performance Monitoring with Prometheus</title>
        <subtitle/>
        <track>Monitoring and Observability</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Unikraft, and similar unikernels, offer isolation by running a single application inside a separated virtual machine. As such, extracting information from the machine can prove difficult. Moreover, because Unikraft offers support for running a single process at a time, alternate solutions had to be found for exporting data. Prometheus is a common tool used to collect and visualize data that offers decoupling from the observed system, as such, we saw it as a prime candidate for exporting information.&lt;/p&gt;

&lt;p&gt;Our solution was to port a Prometheus exporter inside Unikraft as a separate library and run it on a separate thread. Information from the unikernel is extracted by Prometheus through an intermediary library, named ukstore, that behaves like a simplified ProcFS. ukstore offers an easy method for accessing information and metrics from the system. Using Prometheus with Unikraft, we are thus able to extract performance metrics from highly-specialized virtual machines, store them in a time series database and display them using plots.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The main interface between configuration and statistics data from Unikraft and applications is ukstore. It is based on ProcFS and offers easy “folder/data” access. This solves the problem of searching through headers to find functions that offer information. The main advantage of ukstore is that all of its setup is done at build-time so there is no impact on the boot-time. Furthermore, it has flexibility, by offering the possibility to create both static entries (created at build-time) and dynamic entries (created at run-time).&lt;/p&gt;

&lt;p&gt;Metrics inside Unikraft are provided by the libraries that generate them. As such, every library can contain functions that offer usage data. At the moment, work was done to offer metrics related to memory, networking, and thread-locking, with metrics related to file systems and the CPU underway. The end goal is to cover as much of the known metrics from Linux, offered through ProcFS, and expose them through ukstore.&lt;/p&gt;

&lt;p&gt;Porting a Prometheus exporter came with the challenge of finding one with the least amount of dependencies, whilst still retaining the usual format. We chose an exporter and adapted it through patches to successfully interact with Unikraft and exposed available performance metrics through it. With all the above puzzle pieces put together, Unikraft instances can be monitored reliably with a minimal impact on the performance of the instances themselves.&lt;/p&gt;</description>
        <persons>
          <person id="8782">Cezar Craciunoiu</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/unikraft/attachments/slides/5070/export/events/attachments/unikraft/slides/5070/Unikraft_Performance_Monitoring_with_Prometheus">Unikraft Performance Monitoring with Prometheus</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.monitoring/unikraft.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/unikraft.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-unikraft:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-unikraft:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12900.php">Submit feedback</link>
        </links>
      </event>
      <event id="12740">
        <start>16:20</start>
        <duration>00:40</duration>
        <room>D.monitoring</room>
        <slug>learn_from_otel_traces</slug>
        <title>What More Can I Learn From My OpenTelemetry Traces?</title>
        <subtitle/>
        <track>Monitoring and Observability</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Of the three observability data types supported by OpenTelemetry (metrics, logs, and traces) the latter is the one with most potential. Tracing gives users insights into how requests are processed by microservices in a modern, cloud-native architecture.&lt;/p&gt;

&lt;p&gt;Jaeger and Grafana can visualize a single trace, showing how an individual request traversed your entire system. This helps for distributed debugging and analysis, but using traces only this way is limiting.&lt;/p&gt;

&lt;p&gt;What if you stored tracing data in a SQL database? You could ask global questions about your system. You could find slow communication paths, where the error rate spiked since the last deployment, or where the request rate suddenly dropped. Thus, tracing can be used proactively to help you spot issues before your customers do.&lt;/p&gt;

&lt;p&gt;This talk will show you how to do all the above by ingesting OpenTelemetry traces into a PostgreSQL/TimescaleDB database, and building custom dashboards using SQL to make the most out of your tracing data.&lt;/p&gt;</abstract>
        <description>&lt;ul&gt;
&lt;li&gt;What is a trace?&lt;/li&gt;
&lt;li&gt;What is OpenTelemetry?&lt;/li&gt;
&lt;li&gt;View an OpenTelemetry trace in Jaeger&lt;/li&gt;
&lt;li&gt;Overview of OpenTelemetry trace data model&lt;/li&gt;
&lt;li&gt;How it might be represented in a relational-database model - PostgreSQL&lt;/li&gt;
&lt;li&gt;Demonstrate a variety of SQL queries which provide insights into a system explaining the value&lt;/li&gt;
&lt;li&gt;View these queries in a Grafana dashboard&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="8714">John Pruitt</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.monitoring/learn_from_otel_traces.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.monitoring/learn_from_otel_traces.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#monitoring-learn_from_otel_traces:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#monitoring-learn_from_otel_traces:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12740.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.mozilla">
    </room>
    <room name="D.mysql">
      <event id="13065">
        <start>10:00</start>
        <duration>00:25</duration>
        <room>D.mysql</room>
        <slug>mysql_flame</slug>
        <title>Flame Graphs for MySQL DBAs</title>
        <subtitle>Yet another way to visualize performance data</subtitle>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Flame graph is way to visualize profiling data that allows the most frequent code paths to be identified quickly and accurately. They can be generated using Brendan Gregg's open source programs on github.com/brendangregg/FlameGraph, which create interactive SVG files to be checked in browser. The source of profiling data does not really matter - it can be perf profiler, bpftrace, Performance Schema, EXPLAIN output or any other source that allows to convert the data into the expected format of comma-separated "path" plus metric per line.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Different types of Flame Graphs (CPU, Off-CPU, Memory, Differential etc) are presented. Various tools and approaches to collect profile information of different aspects of MySQL server internal working are presented Several real-life use cases where Flame Graphs helped to understand and solve the problem are discussed.&lt;/p&gt;</description>
        <persons>
          <person id="2718">Valerii Kravchuk</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mysql_flame/attachments/slides/4943/export/events/attachments/mysql_flame/slides/4943/Flame_Graphs_for_MySQL_DBAs_FOSDEM_2022_MySQL_Devroom.pdf"/>
        </attachments>
        <links>
          <link href="https://www.youtube.com/watch?v=0JgapAI6LvQ">My talk on similare subject at recent Percona Live</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_flame.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_flame.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_flame:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_flame:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13065.php">Submit feedback</link>
        </links>
      </event>
      <event id="12976">
        <start>10:30</start>
        <duration>00:25</duration>
        <room>D.mysql</room>
        <slug>relational_model_dev</slug>
        <title>The relational model in the modern development age</title>
        <subtitle>Towards an improved operational paradigm, illustrated by Vitess</subtitle>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Relational databases have invested in the performance of the relational model, but not as much in developer flows, creating an operational barrier driving developers away. We present an improved paradigm that brings back ownership into developers hands, illustrated by recent developments in Vitess.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The relational model is one of the oldest surviving models in computer science. But while relational databases have evolved to meet modern load, throughput and scalability needs, they have not evolved as much to meet developers' needs.&lt;/p&gt;

&lt;p&gt;The schema, at the heart of the relational model, remain a major operational blocker in modern development flows. Developing and deploying schema changes is unlike any other development and deployment flow in practice today. Operational complexity and constraints, lack of conflict resolution, difficulty or inability to undeploy, and the need to understand database internals, all make relational schema development deter developers, who look for other solutions elsewhere.&lt;/p&gt;

&lt;p&gt;In this session we will review these impediments and how they came to be, and offer a modern take, that gives developers back their ownership of their data and flows. Recent developments in Vitess, an open source CNCF project, introduce new capabilities that change the relational development paradigm. We will discuss:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Development flow: hiding the operational complexity&lt;/li&gt;
&lt;li&gt;Deployments and scheduled schema migrations&lt;/li&gt;
&lt;li&gt;Undeploy: revertible changes&lt;/li&gt;
&lt;li&gt;Align schema and code: declarative schemas, idempotent deployments, and version control&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="2443">Shlomi Noach</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://vitess.io/">Vitess project page</link>
          <link href="https://video.fosdem.org/2022/D.mysql/relational_model_dev.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/relational_model_dev.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-relational_model_dev:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-relational_model_dev:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12976.php">Submit feedback</link>
        </links>
      </event>
      <event id="13095">
        <start>11:00</start>
        <duration>00:25</duration>
        <room>D.mysql</room>
        <slug>proxysql_cluster</slug>
        <title>ProxySQL Cluster: challenges and solutions to synchronizeconfigurationacross multiple decentralized cluster nodes</title>
        <subtitle/>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As a reverse proxy for MySQL databases, ProxySQL is being used in various infrastructure sizes and it is not surprising to see deployments with thousands of nodes running. Such large deployments introduce some interesting challenges because nodes can be initialized or destroyed at any time.
This session will describe the challenges in configuring such large deployments of nodes, the most common external tools to configure ProxySQL, and then focus on improved ProxySQL native clustering solutions that allows auto-discovery, bootstrap, and a distributed decentralized reconfiguration.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1992">René Cannaò</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/proxysql_cluster.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/proxysql_cluster.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-proxysql_cluster:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-proxysql_cluster:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13095.php">Submit feedback</link>
        </links>
      </event>
      <event id="12471">
        <start>11:30</start>
        <duration>00:25</duration>
        <room>D.mysql</room>
        <slug>pxc_non_blocking</slug>
        <title>Percona XtraDB Cluster(PXC) Non blocking operations, what you need to know to avoid pitfalls </title>
        <subtitle/>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Performing simple DDL operations as ADD/DROP INDEX in a tightly connected cluster as PXC, can become a nightmare.
Metalock will prevent Data modifications for long period of time and to bypass this, we need to become creative, like using Rolling schema upgrade or Percona online-schema-change.
With NBO, we will be able to avoid such craziness at least for a simple operation like adding an index.
In this brief talk I will illustrate what you should do to see the negative effect of NON using NBO, as well what you should do to use it correctly and what to expect out of it.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4696">Marco Tusa (the Grinch)</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/pxc_non_blocking.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/pxc_non_blocking.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-pxc_non_blocking:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-pxc_non_blocking:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12471.php">Submit feedback</link>
        </links>
      </event>
      <event id="12697">
        <start>12:00</start>
        <duration>01:00</duration>
        <room>D.mysql</room>
        <slug>mysql_clusterset</slug>
        <title>MySQL InnoDB ClusterSet</title>
        <subtitle>The integrated solution for disaster recovery of InnoDB Clusters</subtitle>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;MySQL InnoDB ClusterSet brings multi-datacenter capabilities to our High Availability solutions and makes it very easy to set up a disaster recovery architecture. Think multiple MySQL InnoDB Clusters into one single database architecture, fully managed from MySQL Shell, and with full MySQL Router integration to make it easy to access the entire architecture.&lt;/p&gt;

&lt;p&gt;In this session, we will cover the various use-cases and features of InnoDB ClusterSet while guiding you on how to set it up from an existing InnoDB Cluster, extend it, manage it, and deal with the various possible failures, all using Shell's AdminAPI. We will also cover each individual feature of MySQL Router integration which makes connections to the database architecture easy.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1990">Kenny Gryp</person>
          <person id="4686">Miguel Araújo</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mysql_clusterset/attachments/slides/4959/export/events/attachments/mysql_clusterset/slides/4959/MySQL_InnoDB_ClusterSet.pdf">MySQL InnoDB ClusterSet</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_clusterset.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_clusterset.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_clusterset:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_clusterset:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12697.php">Submit feedback</link>
        </links>
      </event>
      <event id="12470">
        <start>13:00</start>
        <duration>00:25</duration>
        <room>D.mysql</room>
        <slug>mysql_k8s_demystified</slug>
        <title>MySQL on Kubernetes demystified</title>
        <subtitle>How foolishness can lead you to fell in a very dangerous trap</subtitle>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The constant pressure to move DATA in containers and Kubernetes is creating a lot of confusion and misunderstanding. &lt;br/&gt;
This is particularly dangerous when talking about Relational Database Management System.&lt;br/&gt;
MySQL, as well as Oracle, Postgres or SQL Server, is a RDBM, as such subject to the erroneous interpretation caused by this new crazy shining things that will solve all.
In this short talk we will clarify, that first of all, we are not looking to something new and second why we need to be very careful when talking about using Kubernetes and containers for RDBMS.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4696">Marco Tusa (the Grinch)</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_k8s_demystified.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_k8s_demystified.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_k8s_demystified:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_k8s_demystified:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12470.php">Submit feedback</link>
        </links>
      </event>
      <event id="12456">
        <start>13:30</start>
        <duration>01:00</duration>
        <room>D.mysql</room>
        <slug>mysql_operator_k8s</slug>
        <title>MySQL Operator for Kubernetes</title>
        <subtitle/>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;On both, public and private clouds, Kubernetes is the most commonly used Orchastration framework for managing cloud services. Aside from management of microscervices it can be extended with operators for managing more complex services. The new MySQL Operator for Kubernetes is such an operator, automating MySQL InnoDB Cluster Management inside Kubernetes and integrated product of the MySQL product family.
 In this session lead developer Johannes Schlüter will discuss how the MySQL Operator works and how it can automate deployment and management of InnoDB Cluster inside Kubernetes.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8543">Johannes Schlüter</person>
        </persons>
        <attachments>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/mysql_operator_k8s/attachments/other/5192/export/events/attachments/mysql_operator_k8s/other/5192/fosdem_runbook.md">Demo Runbook</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mysql_operator_k8s/attachments/slides/5193/export/events/attachments/mysql_operator_k8s/slides/5193/mysql_operator.pdf">MySQL Operator</attachment>
        </attachments>
        <links>
          <link href="https://github.com/mysql/mysql-operator/">GitHub</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_operator_k8s.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_operator_k8s.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_operator_k8s:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_operator_k8s:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12456.php">Submit feedback</link>
        </links>
      </event>
      <event id="12940">
        <start>14:30</start>
        <duration>00:45</duration>
        <room>D.mysql</room>
        <slug>mysql_component</slug>
        <title>Newest MySQL component services features</title>
        <subtitle>or how to make an HTTP server accessing table data in a component</subtitle>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We will explore the latest component services offered by the server. And then we will check how one can use the table access service to make a HTTP server component that allows access to table data via HTTP without a middle-man.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The MySQL development team is constantly adding new and very useful component services. These can be leveraged by creative component authors to produce useful MySQL server add-ons. Check the latest additions to the service list and see some of them in action through a HTTP server component that serves table data.&lt;/p&gt;</description>
        <persons>
          <person id="5531">Joro Kodinov</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mysql_component/attachments/slides/4930/export/events/attachments/mysql_component/slides/4930/FOSDEM22_Newest_MySQL_Component_Services_Features.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_component.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_component.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_component:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_component:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12940.php">Submit feedback</link>
        </links>
      </event>
      <event id="12713">
        <start>15:15</start>
        <duration>00:35</duration>
        <room>D.mysql</room>
        <slug>mysql_pitr_rockstar</slug>
        <title>MySQL 8.0: Logical Backups, Snapshots and PITR like a rockstar</title>
        <subtitle/>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Logical dumps are becoming popular again. MySQL Shell parallel dump &amp;amp; load utility changed to way to deal with logical dumps, certainly when using instances in the cloud.
MySQL 8.0 released also an awesome physical snapshot feature with CLONE.&lt;/p&gt;

&lt;p&gt;In this session, I will show how to use these two ways of saving your data and how to use the generated backup to perform point-in-time recovery like a rockstar with MySQL 8.0 in 2022 !&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="580">Frédéric Descamps</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mysql_pitr_rockstar/attachments/slides/4956/export/events/attachments/mysql_pitr_rockstar/slides/4956/FOSDEM_2022_MySQL_Devroom_Backup_and_Point_in_time_Recovery.pdf">MySQL 8.0 - Backup and Point-in-time Recovery like a rockstar</attachment>
        </attachments>
        <links>
          <link href="https://dev.mysql.com/downloads/mysql/">MySQL Community Server</link>
          <link href="https://lefred.be">lefred's blog: tribulations of a MySQL Evangelist </link>
          <link href="https://blogs.oracle.com/mysql/">The Oracle MySQL Blog</link>
          <link href="https://planet.mysql.com/">Planet MySQL</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_pitr_rockstar.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_pitr_rockstar.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_pitr_rockstar:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_pitr_rockstar:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12713.php">Submit feedback</link>
        </links>
      </event>
      <event id="13069">
        <start>15:55</start>
        <duration>00:10</duration>
        <room>D.mysql</room>
        <slug>mysql_backup</slug>
        <title>Why your backup strategy is wrong?</title>
        <subtitle>A brief overview of MySQL backup concepts</subtitle>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;"If you have a hammer, all you see is nails." also known as the Law of the Instrument describes the cognitive bias that involves over-reliance on a familiar tool. To protect MySQL data, a DBA must have a toolbox full of the proper utensils. To know only one approach is not enough.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk, we will cover the following topics:
- Why your backup strategy is probably wrong?
- The Schröendinger Backup
- Backups: Cold, hot... and warm?
- The right answer is not always the logical one.
- Replication is not the solution.
- Point-in-time recovery.
- Don't try this at prod: Test your backups.&lt;/p&gt;</description>
        <persons>
          <person id="5015">Pep Pla</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/mysql_backup/attachments/slides/5185/export/events/attachments/mysql_backup/slides/5185/Why_your_backup_strategy_is_wrong.pdf">Why your backup strategy is wrong?</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_backup.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_backup.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_backup:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_backup:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13069.php">Submit feedback</link>
        </links>
      </event>
      <event id="13032">
        <start>16:10</start>
        <duration>00:50</duration>
        <room>D.mysql</room>
        <slug>efficient_mysql</slug>
        <title>Efficient MySQL Performance</title>
        <subtitle>A Book in 40 Minutes</subtitle>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This presentation introduces the major topics and most important points of the new book &lt;a href="https://oreil.ly/efficient-mysql-performance"&gt;Efficient MySQL Performance&lt;/a&gt; published by O’Reilly (Dec. 2021). And like the book, this presentation is intended for software engineers using MySQL, not managing it (but DBAs are gladly welcomed). In 40 minutes, we’ll quickly cover topics including query metrics, indexes and indexing, data access patterns, server metrics, and more. At the end, you’ll have a “lay of the land” for understanding the aspects of MySQL that affect performance, and you’ll understand where to go and what to learn next to increase performance.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8832">Daniel Nichter</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://oreil.ly/efficient-mysql-performance">Efficient MySQL Performance (O’Reilly)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/efficient_mysql.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/efficient_mysql.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-efficient_mysql:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-efficient_mysql:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13032.php">Submit feedback</link>
        </links>
      </event>
      <event id="12640">
        <start>17:00</start>
        <duration>00:25</duration>
        <room>D.mysql</room>
        <slug>mysql_cpu</slug>
        <title>MySQL Performance on Modern CPU:  Intel vs AMD vs ARM</title>
        <subtitle/>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;For years CPU choice for MySQL was pretty boring - just chose what Intel Made CPU you want. In recent years the situation changed with AMD producing very competitive Server grade CPUs and ARM going from being the leading CPU manufacturers for low-power gadgets to being inside some of the highest performance server chips.&lt;/p&gt;

&lt;p&gt;In this presentation, we will look into current CPU choices through MySQL Lense - which CPUs provide the best performance for single threaded and high concurrency workloads and which help to achieve the best price/performance.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7756">Peter Zaitsev</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_cpu.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_cpu.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_cpu:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_cpu:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12640.php">Submit feedback</link>
        </links>
      </event>
      <event id="12695">
        <start>17:30</start>
        <duration>00:25</duration>
        <room>D.mysql</room>
        <slug>mysql_recap</slug>
        <title>Release Note Highlights from 2021</title>
        <subtitle>Recap '23 to '27</subtitle>
        <track>MySQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The new releases of MySQL Server in 2021 had some very interesting changes. This session covers the highlights, the contributions, and changes made during the last year.  After 25 years of MySQL, there are still plenty of new features in the code.  This is a quick catchup for those who have not perused the release notes.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The new releases of MySQL Server in 2021 had some very interesting changes. This session covers the highlights, the contributions, and changes made during the last year.  After 25 years of MySQL, there are still plenty of new features in the code.  This is a quick catchup for those who have not perused the release notes.&lt;/p&gt;</description>
        <persons>
          <person id="3258">Dave Stokes</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_recap.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.mysql/mysql_recap.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#mysql-mysql_recap:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#mysql-mysql_recap:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12695.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.network">
      <event id="12428">
        <start>13:00</start>
        <duration>00:30</duration>
        <room>D.network</room>
        <slug>using_ndpi_to_efficiently_classify_network_traffic</slug>
        <title>Network Traffic Classification for Cybersecurity and Monitoring</title>
        <subtitle/>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Security and monitoring applications need to classify traffic in order to identify applications protocols, misuses, similarities, communications patterns not easily identifiable by hand. nDPI is a library that implements various algorithms for traffic analysis able to detect outliers, anomalies, traffic clusters, behavioural changes efficiently in streaming (i.e. while traffic is flowing). Goal of this presentation is to show how nDPI can be used in real life to inspect network traffic and spot patterns worth to be analysed in detail.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Modern network security and monitoring applications need to analyse traffic efficiently in streaming fashion (i.e. while traffic is flowing). This is in order to detect interesting traffic patterns in realtime without dumping data on a database and performing computationally expensive queries in batches. Many network developers do not have skills for efficiently analyse traffic, and data scientists often do not have skills to understand the complex nature of network traffic. For this reason nDPI, a popular open-source deep packet inspection library, has been enhanced with various algorithms and techniques that dramatically simplify traffic analysis and that should ease the creation of applications able to efficiently spot traffic patterns and anomalies.
This talk will introduce some of these algorithms present in nDPI and show how they can be used in real-life at high-speed, contrary to many applications that are inefficient and often based on languages (e.g. Python and R) that are not designed to analyse traffic in streaming at 10 Gbit+ on commodity hardware.&lt;/p&gt;</description>
        <persons>
          <person id="4993">Luca Deri</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/using_ndpi_to_efficiently_classify_network_traffic/attachments/slides/4914/export/events/attachments/using_ndpi_to_efficiently_classify_network_traffic/slides/4914/nDPI_Fosdem_2022.pdf">Presentation slides</attachment>
        </attachments>
        <links>
          <link href="https://www.ntop.org/products/deep-packet-inspection/ndpi/">nDPI - Open and Extensible LGPLv3 Deep Packet Inspection Library.</link>
          <link href="https://video.fosdem.org/2022/D.network/using_ndpi_to_efficiently_classify_network_traffic.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/using_ndpi_to_efficiently_classify_network_traffic.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-using_ndpi_to_efficiently_classify_network_traffic:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-using_ndpi_to_efficiently_classify_network_traffic:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12428.php">Submit feedback</link>
        </links>
      </event>
      <event id="12442">
        <start>13:30</start>
        <duration>00:30</duration>
        <room>D.network</room>
        <slug>why_rule_based_monitoring_is_still_great</slug>
        <title>Why rule-based monitoring is (still) great</title>
        <subtitle/>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A rules-based approach has been the standard in network monitoring for many years, for a good reason. In this talk, we'll recap the advantages of a rule-based approach and how it's still relevant to this day. The speaker will also show how you can implement rules using &lt;a href="https://checkmk.com/"&gt;Checkmk&lt;/a&gt;, an open source IT monitoring software and discuss the entry of AI technology into infrastructure monitoring.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7669">Faye Tandog</person>
          <person id="8531">Robin Gierse</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://checkmk.com/">Checkmk - Everything monitored</link>
          <link href="/2022/stands.fosdem.org/stands/checkmk/">Checkmk FOSDEM Stand</link>
          <link href="https://chat.fosdem.org/#/room/#checkmk-stand:fosdem.org">Checkmk Stand Matrix Room</link>
          <link href="https://video.fosdem.org/2022/D.network/why_rule_based_monitoring_is_still_great.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/why_rule_based_monitoring_is_still_great.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-why_rule_based_monitoring_is_still_great:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-why_rule_based_monitoring_is_still_great:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12442.php">Submit feedback</link>
        </links>
      </event>
      <event id="12436">
        <start>14:00</start>
        <duration>00:20</duration>
        <room>D.network</room>
        <slug>peer_to_peer_hole_punching_without_centralized_infrastructure</slug>
        <title>Peer-to-peer hole punching without centralized infrastructure</title>
        <subtitle>How libp2p can traverse NATs and firewalls without coordination through central STUN and TURN servers.</subtitle>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;&lt;a href="https://libp2p.io"&gt;libp2p&lt;/a&gt; is a universal, cross-platform, multi-language, modular peer-to-peer networking library powering multiple large-scale networks, for example IPFS.&lt;/p&gt;

&lt;p&gt;In the first part of the talk we’ll present the basic building blocks of the library and explain how they fit together. In the second part, we’ll take a closer look at the recently added decentralized hole punching feature, allowing NAT and firewall traversal without the need for any central coordination servers (STUN and TURN).&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4670">Max Leonard Inden</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/peer_to_peer_hole_punching_without_centralized_infrastructure/attachments/slides/4916/export/events/attachments/peer_to_peer_hole_punching_without_centralized_infrastructure/slides/4916/slides.pdf">slides.pdf</attachment>
        </attachments>
        <links>
          <link href="https://libp2p.io/">libp2p - Official Website</link>
          <link href="https://github.com/libp2p/specs/">libp2p - Specifications</link>
          <link href="https://video.fosdem.org/2022/D.network/peer_to_peer_hole_punching_without_centralized_infrastructure.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/peer_to_peer_hole_punching_without_centralized_infrastructure.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-peer_to_peer_hole_punching_without_centralized_infrastructure:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-peer_to_peer_hole_punching_without_centralized_infrastructure:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12436.php">Submit feedback</link>
        </links>
      </event>
      <event id="12434">
        <start>14:20</start>
        <duration>00:20</duration>
        <room>D.network</room>
        <slug>keep_appetite_for_the_stats</slug>
        <title>Keep appetite for the stats, it costs nothing</title>
        <subtitle>Presentation of the statistics consumption model in VPP from the costless low-level design to their exploitation in userspace</subtitle>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;&lt;a href="https://fd.io/"&gt;VPP (aka Vector Packet Processing)&lt;/a&gt; is a fast network stack running in Linux userspace.
It is designed to handle packets with high performance, which makes gathering statistics efficiently a must have.&lt;/p&gt;

&lt;p&gt;The model that has been chosen in &lt;a href="https://fd.io/"&gt;VPP&lt;/a&gt; to provide up to date statistics is built upon shared memory and optimistic locking.
The counters are updated in this shared memory at a rather low cost by the data plane and can be read out at almost any time by all the consumers.
We will first describe this model in more details.&lt;/p&gt;

&lt;p&gt;The consumption of these stats may take various forms depending on the use case and the application needs.
That's why we have developed different high-level components to access them:&lt;/p&gt;

&lt;p&gt;1) A filesystem in userspace: thanks to &lt;a href="https://github.com/hanwen/go-fuse"&gt;go-fuse&lt;/a&gt;, we can mount a filesystem ordering statistics in folders and files, in a similar fashion to '/proc' in Linux&lt;/p&gt;

&lt;p&gt;2) A &lt;a href="https://prometheus.io/"&gt;Prometheus&lt;/a&gt; agent: applied to &lt;a href="https://github.com/calico-vpp"&gt;Calico/VPP&lt;/a&gt;, a new dataplane for &lt;a href="https://www.tigera.io/project-calico/"&gt;Calico&lt;/a&gt; - the popular cloud native &lt;a href="https://kubernetes.io/"&gt;Kubernetes&lt;/a&gt; network plugin - based on &lt;a href="https://fd.io/"&gt;VPP&lt;/a&gt;. Prometheus is integrated as a monitoring tool in order to export our statistics in the form of real-time metrics collected from targets. Metrics come from our pod interfaces statistics, and targets are &lt;a href="https://github.com/calico-vpp"&gt;Calico/VPP&lt;/a&gt; agents running on our &lt;a href="https://kubernetes.io/"&gt;Kubernetes&lt;/a&gt; cluster nodes.&lt;/p&gt;

&lt;p&gt;During the presentation, you will have a quick demo of these components.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8505">Arthur de Kerhor</person>
          <person id="8920">Hedi Bouattour</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/keep_appetite_for_the_stats/attachments/slides/4991/export/events/attachments/keep_appetite_for_the_stats/slides/4991/Fosdem_VPP_stats.pptx">VPP stats segment &amp; consumers</attachment>
        </attachments>
        <links>
          <link href="https://fd.io/">FD.io VPP dataplane</link>
          <link href="https://github.com/hanwen/go-fuse">go-fuse Github repo</link>
          <link href="https://prometheus.io/">Prometheus</link>
          <link href="https://kubernetes.io/">Kubernetes</link>
          <link href="https://www.tigera.io/project-calico/">Calico project</link>
          <link href="https://github.com/calico-vpp">calico-vpp Github project</link>
          <link href="https://video.fosdem.org/2022/D.network/keep_appetite_for_the_stats.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/keep_appetite_for_the_stats.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-keep_appetite_for_the_stats:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-keep_appetite_for_the_stats:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12434.php">Submit feedback</link>
        </links>
      </event>
      <event id="12541">
        <start>14:40</start>
        <duration>00:20</duration>
        <room>D.network</room>
        <slug>comparing_dpdk_rcu_and_user_space_rcu_library</slug>
        <title>Faster memory reclamation with DPDK RCU</title>
        <subtitle>Comparing the DPDK and Userspace RCU libraries</subtitle>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;&lt;a href="https://www.dpdk.org"&gt;DPDK&lt;/a&gt; added a RCU library with a novel method to reclaim resources. We have been running tests to understand the performance differences between the &lt;a href="https://www.dpdk.org"&gt;DPDK&lt;/a&gt; RCU and the &lt;a href="https://liburcu.org/"&gt;user space RCU library&lt;/a&gt;. In our tests, we find that &lt;a href="https://www.dpdk.org"&gt;DPDK&lt;/a&gt; RCU can perform reclamation faster and perform significantly better when pre-emptive readers are involved. Other than the performance, &lt;a href="https://www.dpdk.org"&gt;DPDK&lt;/a&gt; RCU has several advantages such as not requiring a background thread for reclaiming resources and the ability to integrate with existing libraries without having to modify the application.&lt;/p&gt;

&lt;p&gt;This talk will present various testing done on &lt;a href="https://www.dpdk.org"&gt;DPDK&lt;/a&gt; RCU and the &lt;a href="https://liburcu.org/"&gt;user space RCU library&lt;/a&gt; and their results. It will go into the details of pre-emptive reader problem, which affects use cases beyond &lt;a href="https://www.dpdk.org"&gt;DPDK&lt;/a&gt;, and show that &lt;a href="https://www.dpdk.org"&gt;DPDK&lt;/a&gt; RCU library can reduce the reclamation time significantly.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8617">Nathan Brown</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/comparing_dpdk_rcu_and_user_space_rcu_library/attachments/slides/5273/export/events/attachments/comparing_dpdk_rcu_and_user_space_rcu_library/slides/5273/Slides">Faster Memory Reclamation with DPDK RCU- Slides</attachment>
        </attachments>
        <links>
          <link href="https://doc.dpdk.org/guides/prog_guide/rcu_lib.html">DPDK RCU Programmer's Guide</link>
          <link href="https://www.dpdk.org/">DPDK Homepage</link>
          <link href="https://video.fosdem.org/2022/D.network/comparing_dpdk_rcu_and_user_space_rcu_library.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/comparing_dpdk_rcu_and_user_space_rcu_library.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-comparing_dpdk_rcu_and_user_space_rcu_library:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-comparing_dpdk_rcu_and_user_space_rcu_library:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12541.php">Submit feedback</link>
        </links>
      </event>
      <event id="12329">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.network</room>
        <slug>evolution_of_vpp</slug>
        <title>BGP/OSPF with VPP at &gt;100Mpps</title>
        <subtitle>Introducing the Linux Controlplane</subtitle>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk, we will demonstrate high performance routing using open-source &lt;a href="https://fd.io"&gt;VPP&lt;/a&gt; and it's underlying &lt;a href="https://dpdk.org"&gt;Data Plane Development Kit&lt;/a&gt;. This talk highlights the authors work on integrating the Linux ControlPlane which makes BGP, OSPF, etc available with VPP. We'll then turn to a popular DPDK based loadtesting tool &lt;a href="https://trex-tgn.cisco.com"&gt;TRex&lt;/a&gt;, and discuss performance benchmarking results from the field using the author's &lt;a href="https://ipng.ch/"&gt;AS8298&lt;/a&gt; as practical example.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8448">Pim van Pelt</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/evolution_of_vpp/attachments/slides/5037/export/events/attachments/evolution_of_vpp/slides/5037/IPng_Networks_FOSDEM22.pdf">IPng Networks - VPP</attachment>
        </attachments>
        <links>
          <link href="https://ipng.ch/s/articles/">Articles describing VPP work</link>
          <link href="https://fd.io/">VPP homepage</link>
          <link href="https://video.fosdem.org/2022/D.network/evolution_of_vpp.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/evolution_of_vpp.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-evolution_of_vpp:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-evolution_of_vpp:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12329.php">Submit feedback</link>
        </links>
      </event>
      <event id="12357">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.network</room>
        <slug>predictable_network_traffic_in_kubernetes</slug>
        <title>Predictable Network Traffic in Kubernetes</title>
        <subtitle/>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The software applications of the Cloud Native era have a huge dependency on the network, these microservices are bound to a single concern and utilize the network to communicate with each other. The dependency on the network continues to grow as more and more microservices depend on it. However, there is no way to predictably leverage the network for the specific demands of your application. What if we could tag certain applications as needing a priority from the network. This would enhance the networking capabilities offered from Kubernetes and compliment the deployment of applications that require predictable behavior of the network.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;More industries are migrating to Kubernetes and evolving their knowledge of the Cloud Native ecosystem. As this trend accelerates, apps with specialized requirements are emerging, such as high-priority apps. High-priority apps require predictable high performance, which can be difficult to achieve in clusters with 100s or 1000s of containers. They require and expect platform capabilities such as dedicated resources, less context switching, and efficient packet processing. In the context of the network, high-priority apps need to execute predictably, leaving no room for extra jitter. Pinning CPU cores may help with determinism but introduces a platform-specific mechanism that fails to embrace the abstraction of Cloud Native deployments. This presentation will cover application-specific queuing and steering technology that dedicates hardware NIC queues to application-specific threads of execution.&lt;/p&gt;</description>
        <persons>
          <person id="7148">Dave Cremins</person>
          <person id="8490">Abdul Halim</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/predictable_network_traffic_in_kubernetes/attachments/slides/5241/export/events/attachments/predictable_network_traffic_in_kubernetes/slides/5241/Predictable_Network_Traffic_in_Kubernetes.pdf">Predictable Network Traffic in Kubernetes</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.network/predictable_network_traffic_in_kubernetes.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/predictable_network_traffic_in_kubernetes.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-predictable_network_traffic_in_kubernetes:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-predictable_network_traffic_in_kubernetes:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12357.php">Submit feedback</link>
        </links>
      </event>
      <event id="12468">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.network</room>
        <slug>contour_kubernetes_ingress_controller_and_much_more_101</slug>
        <title>Contour - Kubernetes Ingress Controller and much more 101</title>
        <subtitle>Introduction to Contour and Contour community!</subtitle>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Contour is an open source Kubernetes Ingress controller providing the Control Plane for the Envoy Edge and Service proxy. Contour supports dynamic configuration updates and multi-team Ingress delegation out of the box while maintaining a lightweight profile. Contour is currently CNCF Incubating project!&lt;/p&gt;

&lt;h1&gt;In this talk:&lt;/h1&gt;

&lt;p&gt;We will do a Contour 101 intro, do a short demo of some of the deployment methods for Contour inside a Kubernetes cluster, demonstrate some of Contour's main features, and highlight the benefits Contour can bring to your setup. Along the way, we will walk though Contour's architecture we will also touch base on the Contour community, including how the community works and why we think you will want to join us!&lt;/p&gt;

&lt;h1&gt;&lt;strong&gt;Come and joins us!&lt;/strong&gt;&lt;/h1&gt;</abstract>
        <description>&lt;p&gt;Orlin Vasilev aka Orlin - Community Manager for Contour - past life: +15 years of SysAdmin/Infra Engineer/Cloud Engineer/DevOps/SRE&lt;/p&gt;</description>
        <persons>
          <person id="8461">Orlin Vasilev</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/contour_kubernetes_ingress_controller_and_much_more_101/attachments/slides/5216/export/events/attachments/contour_kubernetes_ingress_controller_and_much_more_101/slides/5216/OrlinVasilev_Contour_FOSDEM_2022.pdf">Slides</attachment>
        </attachments>
        <links>
          <link href="https://github.com/projectcontour">Project's GitHub</link>
          <link href="https://projectcontour.io/">Project's Home Page</link>
          <link href="https://kind.sigs.k8s.io/">Kind's Home Page</link>
          <link href="https://kubernetes.io">Kubernetes' Page</link>
          <link href="https://github.com/OrlinVasilev/contour-fosdem22">Demo and Slide deck</link>
          <link href="https://video.fosdem.org/2022/D.network/contour_kubernetes_ingress_controller_and_much_more_101.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/contour_kubernetes_ingress_controller_and_much_more_101.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-contour_kubernetes_ingress_controller_and_much_more_101:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-contour_kubernetes_ingress_controller_and_much_more_101:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12468.php">Submit feedback</link>
        </links>
      </event>
      <event id="12386">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.network</room>
        <slug>kubernetes_networking_is_there_a_cheetah</slug>
        <title>Kubernetes networking : is there a cheetah within your Calico?</title>
        <subtitle>Even faster kubernetes clusters with Calico, VPP and memif</subtitle>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Kubernetes is great, containers are lightweight &amp;amp; disposable, networking is simple yet powerful. But when
it comes to network oriented applications, oh that can be slow !&lt;/p&gt;

&lt;p&gt;That's how the Calico/VPP integration first came up, as a way to address performance bottlenecks, making
VPP's performance the motor of Calico's functionalities in Kubernetes. It speeds up container
networking, but also allows us to expose even faster functionalities directly to the applications.
So with this in place, how can we go even faster, while still preserving the Kubernetes abstractions ?&lt;/p&gt;

&lt;p&gt;We'll present how applications can leverage userspace interfaces, what this allows regarding
network performance &amp;amp; additional functionalities and how the Calico/VPP integration makes this happen
under the hood.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6508">Nathan Skrzypczak</person>
          <person id="8494">Christopher Tomkins</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/kubernetes_networking_is_there_a_cheetah/attachments/slides/5080/export/events/attachments/kubernetes_networking_is_there_a_cheetah/slides/5080/FOSDEM_2022_Calico_VPP_is_there_a_cheetah_within_your_Calico.pdf">FOSDEM 2022 Calico_VPP is there a cheetah within your Calico</attachment>
        </attachments>
        <links>
          <link href="https://github.com/projectcalico/vpp-dataplane">Calico-VPP dataplane</link>
          <link href="https://www.tigera.io/project-calico/">Project Calico</link>
          <link href="https://fd.io">VPP fd.io</link>
          <link href="https://video.fosdem.org/2022/D.network/kubernetes_networking_is_there_a_cheetah.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/kubernetes_networking_is_there_a_cheetah.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-kubernetes_networking_is_there_a_cheetah:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-kubernetes_networking_is_there_a_cheetah:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12386.php">Submit feedback</link>
        </links>
      </event>
      <event id="12346">
        <start>17:00</start>
        <duration>00:30</duration>
        <room>D.network</room>
        <slug>challenges_and_opportunities_in_performance_benchmarking_of_service_mesh_for_the_edge</slug>
        <title>Challenges and Opportunities in Performance Benchmarking of Service Mesh for the Edge</title>
        <subtitle/>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As Edge deployments move closer towards the end devices, low latency communication among Edge aware applications is one of the key tenants of Edge service offerings. In order to simplify application development, service mesh architectures have emerged as the evolutionary architectural paradigms for taking care of bulk of application communication logic such as health checks, circuit breaking, secure communication, resiliency (among others), thereby decoupling application logic with communication infrastructure. The latency to throughput ratio needs to be measurable for high performant deployments at the Edge. Providing benchmark data for various edge deployments with Bare Metal and virtual machine-based scenarios, this paper digs into architectural complexities of deploying service mesh at edge environment, performance impact across north-south and east-west communications in and out of a service mesh leveraging popular open-source service mesh Istio/Envoy using a simple on-prem Kubernetes cluster. The performance results shared indicate performance impact of Kubernetes network stack with Envoy data plane. Microarchitecture analyses indicate bottlenecks in Linux based stacks from a CPU micro-architecture perspective and quantify the high impact of Linux’s Iptables rule matching at scale. We conclude with the challenges in multiple areas of profiling and benchmarking requirement and a call to action for deploying a service mesh, in latency sensitive environments at Edge.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The pervasiveness of Edge computing and Service Mesh constructs within a cloud native environment have almost been at the same time during last few years. Requirements of Edge compute to be able to unify both Information &amp;amp; Communication Technology (ICT) and Operational Technology (OT) have brought together cloud native deployments and microservice based service offerings to the Edge infrastructure]. While Kubernetes been the most popular model of deploying cloud native infrastructure to offer software services, service mesh is the emergent application deployment paradigm that decouples application from developing most of the software defined networking aspects of microservice interactions. This paper introduces features of service mesh that are architecturally suitable for Edge compute service offerings and application development principles. To understand applicability of service mesh, architectural principles need to be understood to figure out suitability of various benefits mesh benefits to customized Edge deployments. This talk introduces and correlates various Edge requirements to the service mesh’s architectural guidelines. Then further dig into deployment considerations of service mesh with Edge deployment types to provide practical communication challenges between the two. This talk:
- Provides benchmark tests and their results that provides the impact of service mesh on simple Kubernetes based deployments using Istio &amp;amp; Envoy as service mesh and its sidecar proxy, that can be leveraged for Edge environments.
- Provides detailed analysis of the software used to identify bottlenecks using Top-Down Microarchitectural Analysis and CPU Hot Spot analysis.
- Summarizes the gaps identified during the detailed testing of these open-source components
- Showcases the impact of utilizing service mesh for edge computing.&lt;/p&gt;</description>
        <persons>
          <person id="5609">Sunku Ranganath</person>
          <person id="8923">Mrittika Ganguli</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/challenges_and_opportunities_in_performance_benchmarking_of_service_mesh_for_the_edge/attachments/slides/5062/export/events/attachments/challenges_and_opportunities_in_performance_benchmarking_of_service_mesh_for_the_edge/slides/5062/ChallengesandOpportunities_in_Performance_Benchmarking_ofService_Mesh_for_the_Edge.pdf">ChallengesandOpportunities in Performance Benchmarking ofService Mesh for the Edge</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.network/challenges_and_opportunities_in_performance_benchmarking_of_service_mesh_for_the_edge.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/challenges_and_opportunities_in_performance_benchmarking_of_service_mesh_for_the_edge.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-challenges_and_opportunities_in_performance_benchmarking_of_service_mesh_for_the_edge:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-challenges_and_opportunities_in_performance_benchmarking_of_service_mesh_for_the_edge:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12346.php">Submit feedback</link>
        </links>
      </event>
      <event id="12366">
        <start>17:30</start>
        <duration>00:30</duration>
        <room>D.network</room>
        <slug>2_cluster_kubernetes_with_calico_bgp_interconnect_and_wireguard_all_without_leaving_your_laptop</slug>
        <title>2-cluster Kubernetes, with Calico, BGP Interconnect and WireGuard... All Without Leaving Your Laptop!</title>
        <subtitle/>
        <track>Network</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Wouldn’t it be great to be able to dabble with Kubernetes, Calico, BGP, and WireGuard in a totally safe, totally zero-cost, and easily (!!) reproducible local laptop or workstation environment?&lt;/p&gt;

&lt;p&gt;If you agree, I’m here for you. In this engaging, hands-on and fun session I’ll share with you how I built two four-node Kubernetes clusters, peering with BGP, forwarding with WireGuard, all inside my laptop, and how you can do the same, for fun, learning, and profit. Or, well, just fun and learning, actually.&lt;/p&gt;

&lt;p&gt;When working with these technologies (especially BGP), cost, risk and complexity are the usual barriers to learning. Let's remove them and get back to enjoying our learning.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8494">Christopher Tomkins</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.network/2_cluster_kubernetes_with_calico_bgp_interconnect_and_wireguard_all_without_leaving_your_laptop.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.network/2_cluster_kubernetes_with_calico_bgp_interconnect_and_wireguard_all_without_leaving_your_laptop.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#network-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#network-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#network-2_cluster_kubernetes_with_calico_bgp_interconnect_and_wireguard_all_without_leaving_your_laptop:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#network-2_cluster_kubernetes_with_calico_bgp_interconnect_and_wireguard_all_without_leaving_your_laptop:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12366.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.nim">
    </room>
    <room name="D.research">
    </room>
    <room name="D.design">
      <event id="13548">
        <start>13:10</start>
        <duration>00:45</duration>
        <room>D.design</room>
        <slug>osd_how_do_we_design_open_source_communities_to_be_more_diverse_equitable_and_inclusive</slug>
        <title>How do we design open source communities to be more diverse, equitable, and inclusive? </title>
        <subtitle/>
        <track>Open Source Design</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The CHAOSS project represents a potential force for power and good in open source and is demonstrating significant progress toward its stated aims during its first four years. In particular, the CHAOSS project advances the development of metrics and programs that can help other projects to first understand their own diversity, equity, and inclusion and second work to improve their project in these areas. This roundtable includes speakers who took part in a year-long reflection on DEI practices within the CHAOSS project. The roundtable talk will help other open source projects in their work towards improving diversity, equity, and inclusion by exploring practices within the CHAOSS project first, then using those examples as points of reference for other projects. In particular, the roundtable talk will advance these goals, aimed at answering the question of: How do we design open source communities to be more diverse, equitable, and inclusive?&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8988">matt.germonprez</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chaoss.community/ ">CHAOSS community</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_how_do_we_design_open_source_communities_to_be_more_diverse_equitable_and_inclusive.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.design/osd_how_do_we_design_open_source_communities_to_be_more_diverse_equitable_and_inclusive.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#design-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#design-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#design-osd_how_do_we_design_open_source_communities_to_be_more_diverse_equitable_and_inclusive:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#design-osd_how_do_we_design_open_source_communities_to_be_more_diverse_equitable_and_inclusive:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13548.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.firmware">
    </room>
    <room name="D.openpower">
    </room>
    <room name="D.postgresql">
      <event id="12393">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>D.postgresql</room>
        <slug>postgresql_solving_the_knapsack_problem_with_recursive_queries_and_postgresql</slug>
        <title>Solving the knapsack problem with recursive queries and PostgreSQL</title>
        <subtitle/>
        <track>PostgreSQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Optimization problems are everywhere, from deciding which clothes to pack in our luggage (aka the knapsack problem), to selecting the tasks that will be worked during a sprint. Trying to solve these type of problems by hand is a tedious task often resulting in sub-optimal decisions.&lt;/p&gt;

&lt;p&gt;In this talk, we'll understand how PostgreSQL recursive queries can help. Starting from the proper problem definition, we'll then explore how to build queries that call themselves recursively, what are the risks associated with this approach and safeguards we can set to optimise performances. Finally we'll demonstrate how two new features released in PostgreSQL 14 enable an easier handling of the recursive statements.&lt;/p&gt;

&lt;p&gt;If you're into PostgreSQL and eager to understand how recursion works, this session is for you!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8515">Francesco Tisiot</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/postgresql_solving_the_knapsack_problem_with_recursive_queries_and_postgresql/attachments/slides/5031/export/events/attachments/postgresql_solving_the_knapsack_problem_with_recursive_queries_and_postgresql/slides/5031/Knapsack_Slides">Knapsack Slides</attachment>
        </attachments>
        <links>
          <link href="https://aiven.io/blog/solving-the-knapsack-problem-in-postgresql">original blog post</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_solving_the_knapsack_problem_with_recursive_queries_and_postgresql.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_solving_the_knapsack_problem_with_recursive_queries_and_postgresql.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-postgresql_solving_the_knapsack_problem_with_recursive_queries_and_postgresql:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-postgresql_solving_the_knapsack_problem_with_recursive_queries_and_postgresql:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12393.php">Submit feedback</link>
        </links>
      </event>
      <event id="12893">
        <start>11:00</start>
        <duration>01:00</duration>
        <room>D.postgresql</room>
        <slug>postgresql_json_in_postgresql_learning_with_a_case_study</slug>
        <title>JSON in PostgreSQL - Learning with a case study</title>
        <subtitle/>
        <track>PostgreSQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;PostgreSQL provides great support for JSON objects and every developer working
with this data type should learn how to take advantage of it. Instead of going
through the documentation on how to use JSON in PostgreSQL, in this talk we will
use a case study to learn by example. We will also complement the usage of JSON
by introducing other data types such as ARRAY. We will also review some design
decisions to turn JSON objects into columns and vice versa when it's convenient.
This talk will help you to axe the archaic Entity-Attribute-Value (EAV) pattern
from your database.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3454">Boriss Mejias</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_json_in_postgresql_learning_with_a_case_study.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_json_in_postgresql_learning_with_a_case_study.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-postgresql_json_in_postgresql_learning_with_a_case_study:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-postgresql_json_in_postgresql_learning_with_a_case_study:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12893.php">Submit feedback</link>
        </links>
      </event>
      <event id="12921">
        <start>12:00</start>
        <duration>00:30</duration>
        <room>D.postgresql</room>
        <slug>postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series</slug>
        <title>How to create (lots!) of sample time-series data with PostgreSQL generate_series()</title>
        <subtitle/>
        <track>PostgreSQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Exploring new features in PostgreSQL or reproducing an unusual query plan can be tricky without representative data to utilize. While there are a plethora of sources for sample data and tools to import it, you can end up spending too much time finding representative data to work with. In our day-to-day work at Timescale, we often need to quickly create lots of sample time-series data to demonstrate new features, run a benchmark, or help community members with examples as they learn.&lt;/p&gt;

&lt;p&gt;Although using real application data would be ideal, PostgreSQL provides the generate_series() function which makes it easy to create a  representative time-series dataset using varying cardinalities and different lengths of time.&lt;/p&gt;

&lt;p&gt;In this talk we'll introduce generate_series() and demonstrate how to use it to create realistic-looking time-series data of all shapes and sizes, using custom PostgreSQL user-defined functions. Once we've mastered the basics, we'll dial it up a notch by incorporating PostgreSQL math functions and relational data to create realistic time-series patterns of data for various use cases like sales or website visits.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8781">Ryan Booz</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series/attachments/slides/5194/export/events/attachments/postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series/slides/5194/FOSDEM_Generate_Series.pdf"/>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series/attachments/other/5195/export/events/attachments/postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series/other/5195/FOSDEM_part_1_and_2.sql"/>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series/attachments/other/5196/export/events/attachments/postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series/other/5196/generate_series_demo.ipynb"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-postgresql_how_to_create_lots_of_sample_time_series_data_with_postgresql_generate_series:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12921.php">Submit feedback</link>
        </links>
      </event>
      <event id="12416">
        <start>12:30</start>
        <duration>00:30</duration>
        <room>D.postgresql</room>
        <slug>postgresql_future_postgres_challenges</slug>
        <title>Future Postgres Challenges</title>
        <subtitle/>
        <track>PostgreSQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Postgres has been a vibrant project for decades, and probably will be popular for decades to come. However, as with any complex endeavor, challenges are always lurking. This talk explores the many project, competitive, and technical challenges in the future that could derail its success. By exploring these challenges, we will be better able to avoid them.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3126">Bruce Momjian</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://momjian.us/main/writings/pgsql/challenges.pdf">slides</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_future_postgres_challenges.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_future_postgres_challenges.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-postgresql_future_postgres_challenges:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-postgresql_future_postgres_challenges:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12416.php">Submit feedback</link>
        </links>
      </event>
      <event id="12521">
        <start>13:00</start>
        <duration>00:30</duration>
        <room>D.postgresql</room>
        <slug>postgresql_postgresql_distributed_secure_database_ecosystem_building</slug>
        <title>PostgreSQL Distributed &amp; Secure Database Ecosystem Building</title>
        <subtitle>This session will focus on introducing how to empower PostgreSQL thanks to the ecosystem provided by Apache ShardingSphere - an open source distributed database, plus an ecosystem users and developers need for their database to provide a customized and cloud-native experience.</subtitle>
        <track>PostgreSQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As the most popular open source relational database in the world, PostgreSQL keeps attracting the significant attention it deserves. With the ever increasing data storage and query requirements, new challenges are brought forward for horizontal elastic expansion and security of the PostgreSQL database.
How to provide existing PostgreSQL databases with incremental capabilities such as data sharding, data encryption and other functions is of great concern to many PostgreSQL users.
This session will focus on introducing how to empower PostgreSQL thanks to the ecosystem provided by Apache ShardingSphere - an open source distributed database, plus an ecosystem users and developers need for their database to provide a customized and cloud-native experience. ShardingSphere doesn't quite fit into the usual industry mold of a simple distributed database middleware solution. ShardingSphere recreates the distributed pluggable system, enabling actual user implementation scenarios to thrive and contributing valuable solutions to the community and the database industry.
The aim of ShardingSphere is the Database Plus concept.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Database Plus sets out to build a standard layer and an ecosystem layer above the fragmented database's basic services. A unified and standardized database usage specification provides for upper-level applications, and the challenges faced by businesses due to underlying databases fragmentation get minimized as much as possible. To link databases and applications, it uses traffic and data rendering and parsing. It provides users with enhanced core features, such as a distributed database, data security, database gateway, and stress testing.
ShardingSphere uses a pluggable kernel architecture for Database Plus. That means there's modularity, which provides flexibility for the user.  Demos and notable use cases in production environments that are from the Asia equivalents of FAANG (Facebook, Amazon etc.) will be used to introduce the use and implementation of these functions for PostgreSQL databases.&lt;/p&gt;</description>
        <persons>
          <person id="8601">Juan  Pan</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/postgresql_postgresql_distributed_secure_database_ecosystem_building/attachments/slides/5209/export/events/attachments/postgresql_postgresql_distributed_secure_database_ecosystem_building/slides/5209/PostgreSQL_Distributed_Secure_Database_Ecosystem_Building"/>
        </attachments>
        <links>
          <link href="https://twitter.com/ShardingSphere">Twitter </link>
          <link href="https://github.com/apache/shardingsphere">GitHub Repo</link>
          <link href="https://apacheshardingsphere.slack.com/ssb/redirect">Slack Community</link>
          <link href="https://shardingsphere.apache.org">Project Website</link>
          <link href="https://shardingsphere.medium.com">Medium </link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_postgresql_distributed_secure_database_ecosystem_building.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_postgresql_distributed_secure_database_ecosystem_building.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-postgresql_postgresql_distributed_secure_database_ecosystem_building:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-postgresql_postgresql_distributed_secure_database_ecosystem_building:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12521.php">Submit feedback</link>
        </links>
      </event>
      <event id="12825">
        <start>13:30</start>
        <duration>00:30</duration>
        <room>D.postgresql</room>
        <slug>postgresql_automatically_refresh_materialized_views_in_postgresql</slug>
        <title>Automatically refresh materialized views in PostgreSQL</title>
        <subtitle>Tactics to make refreshing a painless process</subtitle>
        <track>PostgreSQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Since PostgreSQL 9.3 introduced materialized views, it’s been an important feature that many users leverage to power dashboards, pre-compute information, or execute common queries in a much faster manner.&lt;/p&gt;

&lt;p&gt;On the flip side, if your database often gets updated, keeping your materialized views up-to-date can be challenging. Especially when working with time-series data where timeliness is often an important requirement. In this talk, I will share some tactics to keep your materialized views up-to-date in PostgreSQL and how to use REFRESH MATERIALIZED VIEW efficiently to fit your use case.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Let’s say you have a real-time dashboard fueled by a PostgreSQL materialized view. How can you make sure that this materialized view is always up-to-date, hence the dashboard is showing up-to-date information as well? How can you avoid read-locks while refreshing the view or minimize refresh periods? These are some of the questions many users ask when starting to work with PostgreSQL materialized views.&lt;/p&gt;

&lt;p&gt;In this talk, I will explore these questions further and show some tactics on how you can optimize the process of refreshing your PostgreSQL materialized views and keeping them maintained. I will dissect the REFRESH MATERIALIZED VIEW command and its usage and show additional tips on how you can make refreshing materialized views as painless as possible.&lt;/p&gt;</description>
        <persons>
          <person id="8747">Attila Tóth</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_automatically_refresh_materialized_views_in_postgresql.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_automatically_refresh_materialized_views_in_postgresql.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-postgresql_automatically_refresh_materialized_views_in_postgresql:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-postgresql_automatically_refresh_materialized_views_in_postgresql:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12825.php">Submit feedback</link>
        </links>
      </event>
      <event id="12667">
        <start>14:00</start>
        <duration>01:00</duration>
        <room>D.postgresql</room>
        <slug>postgresql_working_effectively_with_support_the_community</slug>
        <title>Working effectively with (-support-) the community</title>
        <subtitle>This talk is for those who are new to PostgreSQL or those who just started, or all the others that want to hear a personal story: When I started with PostgreSQL around 10 years ago, I came with an Oracle background. It took me quite some time to understand how the PostgreSQL project is organized, how the community is working and how to deal with issues I've faced when I needed support. This is not a technical talk at all, but it should save you quite some time in your journey with PostgreSQL.</subtitle>
        <track>PostgreSQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk is for those who are new to PostgreSQL or those who just started, or all the others that want to hear a personal story: When I started with PostgreSQL around 10 years ago, I came with an Oracle background. It took me quite some time to understand how the PostgreSQL project is organized, how the community is working and how to deal with issues I've faced when I needed support. This is not a technical talk at all, but it should save you quite some time in your journey with PostgreSQL.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7665">Daniel Westermann</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_working_effectively_with_support_the_community.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_working_effectively_with_support_the_community.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-postgresql_working_effectively_with_support_the_community:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-postgresql_working_effectively_with_support_the_community:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12667.php">Submit feedback</link>
        </links>
      </event>
      <event id="12769">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>D.postgresql</room>
        <slug>postgresql_exploring_linux_memory_usage_and_io_performance_for_cloud_native_databases</slug>
        <title>Exploring Linux Memory Usage and IO Performance for Cloud Native Databases</title>
        <subtitle/>
        <track>PostgreSQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Linux and containers are similar in that they provide operating system resources such as memory and storage. These resources—along with CPU and networking— are key factors to achieve optimal performance.&lt;/p&gt;

&lt;p&gt;In this session, we'll explore how memory allocation at the container or operating system level influences the performance of buffered disk IO, which is typically how IO is handled by PostgreSQL. We'll also examine Linux memory management details and the different ways disk IO could be performed. From there, we'll walk through a number of examples that reveal the typical dynamics of cached and non-cached IOs, as well as the differences between the two.&lt;/p&gt;

&lt;p&gt;Understanding these dynamics is critical to learn how PostgreSQL IO works.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8731">Frits Hoogland</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_exploring_linux_memory_usage_and_io_performance_for_cloud_native_databases.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_exploring_linux_memory_usage_and_io_performance_for_cloud_native_databases.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-postgresql_exploring_linux_memory_usage_and_io_performance_for_cloud_native_databases:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-postgresql_exploring_linux_memory_usage_and_io_performance_for_cloud_native_databases:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12769.php">Submit feedback</link>
        </links>
      </event>
      <event id="12656">
        <start>16:00</start>
        <duration>01:00</duration>
        <room>D.postgresql</room>
        <slug>postgresql_slow_things_down_to_make_them_go_faster</slug>
        <title>Slow things down to make them go faster</title>
        <subtitle/>
        <track>PostgreSQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;It's easy to get misled into overconfidence based on the performance of powerful servers, given today's monster core counts and RAM sizes. However, the reality of high concurrency usage is often disappointing, with less throughput than one would expect. Because of its internals and its multi-process architecture, PostgreSQL is very particular about how it likes to deal with high concurrency and in some cases it can slow down to the point where it looks like it's not performing as it should. In this talk we'll take a look at potential pitfalls when you throw a lot of work at your database. Specifically, very high concurrency and resource contention can cause problems with lock waits in Postgres. Very high transaction rates can also cause problems of a different nature. Finally, we will be looking at ways to mitigate these by examining our queries and connection parameters, leveraging connection pooling and replication, or adapting the workload.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Topics:&lt;br/&gt;
1. Understand what we mean by high concurrency.&lt;br/&gt;
2. Understand ACID &amp;amp; MVCC in Postgres.&lt;br/&gt;
3. Understand how high concurrency affects Postgres performance.&lt;br/&gt;
4. Understand how locks/latches affect Postgres performance.&lt;br/&gt;
5. Understand how high transaction rates can affect Postgres.&lt;br/&gt;
6. Mitigation strategies for high concurrency scenarios.&lt;/p&gt;</description>
        <persons>
          <person id="4095">Jimmy Angelakos</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/postgresql_slow_things_down_to_make_them_go_faster/attachments/slides/5255/export/events/attachments/postgresql_slow_things_down_to_make_them_go_faster/slides/5255/SlowThingsDown_FOSDEM.pdf">Slow things down to make them go faster</attachment>
        </attachments>
        <links>
          <link href="https://www.slideshare.net/vyruss000/slow-things-down-to-make-them-go-faster-fosdem-2022">Presentation slides</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_slow_things_down_to_make_them_go_faster.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_slow_things_down_to_make_them_go_faster.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-postgresql_slow_things_down_to_make_them_go_faster:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-postgresql_slow_things_down_to_make_them_go_faster:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12656.php">Submit feedback</link>
        </links>
      </event>
      <event id="12808">
        <start>17:00</start>
        <duration>01:00</duration>
        <room>D.postgresql</room>
        <slug>postgresql_lesser_known_postgresql_features</slug>
        <title>Lesser Known PostgreSQL Features</title>
        <subtitle>Features you already have but may not know about!</subtitle>
        <track>PostgreSQL</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In the talk I want to present a few lesser know, but useful features you may never heard about! For example, do you know how you can get the number of inserted and update rows in an upsert? how to create reproducible random data for testing and demonstrations? match a text against multiple patterns without complicated condition? How about using \copy with multi-line queries? All that and more... in my talk :)&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk I'll present lesser known features in PostgreSQL such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How you can get the number of inserted and update rows in an upsert&lt;/li&gt;
&lt;li&gt;How to create reproducible random data for testing and demonstration&lt;/li&gt;
&lt;li&gt;How to match a text against multiple patterns without complicated condition&lt;/li&gt;
&lt;li&gt;How to use \copy with multi-line queries&lt;/li&gt;
&lt;li&gt;And many more fun features from the deep end of the documentation!&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="7898">Haki Benita</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://hakibenita.com/postgresql-unknown-features">Lesser Known PostgreSQL Features</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_lesser_known_postgresql_features.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.postgresql/postgresql_lesser_known_postgresql_features.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#postgresql-postgresql_lesser_known_postgresql_features:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#postgresql-postgresql_lesser_known_postgresql_features:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12808.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.public-code">
      <event id="12974">
        <start>10:15</start>
        <duration>00:10</duration>
        <room>D.public-code</room>
        <slug>public_code_welcome</slug>
        <title>Welcome to the Public Code devroom</title>
        <subtitle/>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A brief introduction and overview of what you can expect from the Public Code devroom at FOSDEM.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8436">Jan Ainali</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://blog.publiccode.net/news/2022/01/19/fosdem-2022-is-coming-up.html">Introductory blog post</link>
          <link href="https://video.fosdem.org/2022/D.public-code/public_code_welcome.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/public_code_welcome.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-public_code_welcome:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-public_code_welcome:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12974.php">Submit feedback</link>
        </links>
      </event>
      <event id="12745">
        <start>10:30</start>
        <duration>00:20</duration>
        <room>D.public-code</room>
        <slug>joint_open_source_development</slug>
        <title>Joint open source development in cross-border context</title>
        <subtitle/>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;X-Road® is open-source software and ecosystem solution that provides unified and secure data exchange between organisations. X-Road is a digital public good verified by the Digital Public Goods Alliance, and it’s released under the MIT open source license and is available free of charge. X-Road is used as a national data exchange solution in Estonia, Finland, Iceland and many other countries around the world.&lt;/p&gt;

&lt;p&gt;Nordic Institute for Interoperability Solutions (NIIS) is a non-profit association with the mission to ensure the development and strategic management of X-Road® and other cross-border components for digital government infrastructure. The republics of Estonia, Finland and Iceland are members of NIIS.&lt;/p&gt;

&lt;p&gt;In my talk, I'm going to give an overview of X-Road first. Then, I'm going to discuss the organisational structure of NIIS and the development model of X-Road. The main scope of the presentation is to discuss joint open source development in cross-border context.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8716">Petteri Kivimäki</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/joint_open_source_development/attachments/slides/4841/export/events/attachments/joint_open_source_development/slides/4841/2022_02_06_Joint_Open_Source_Development_in_Cross_Border_Context.pdf">Joint Open-Source Development in Cross-Border Context</attachment>
        </attachments>
        <links>
          <link href="https://niis.org">https://niis.org</link>
          <link href="https://x-road.global">https://x-road.global</link>
          <link href="https://video.fosdem.org/2022/D.public-code/joint_open_source_development.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/joint_open_source_development.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-joint_open_source_development:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-joint_open_source_development:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12745.php">Submit feedback</link>
        </links>
      </event>
      <event id="12877">
        <start>11:00</start>
        <duration>00:25</duration>
        <room>D.public-code</room>
        <slug>developers_italia</slug>
        <title>Developers Italia, four years later</title>
        <subtitle/>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In 2017, Italy launched a key initiative to improve public services by opening up the development of a handful of core technologies and allowing an open governance community to gather around public code. The effort resulted in the launch of two projects: Developers Italia and Designers Italia, which started a virtuous ecosystem involving administrations, businesses, and enthusiasts who want to improve public services and citizens' lives. Today, the two communities attract over 20.000 technical talents capable of contributing to their country's development and have created together hundreds of open source packages. We launched internationally at FOSDEM 2018, with the help of the Free Software community. We're returning four years later to provide updates, share lessons learned, and continue the conversation on how to make Italy the most hacker-friendly country in the world.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3108">Riccardo Iaconelli</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.public-code/developers_italia.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/developers_italia.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-developers_italia:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-developers_italia:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12877.php">Submit feedback</link>
        </links>
      </event>
      <event id="12819">
        <start>11:35</start>
        <duration>00:35</duration>
        <room>D.public-code</room>
        <slug>lessons_from_danish_os2</slug>
        <title>Lessons from the Danish OS2</title>
        <subtitle>Maturing governance</subtitle>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A strong organization is an important part of governing a public code base. The association OS2 scores their IT-solutions after a governance model divided into three levels, which shows the maturing of the code and the organization surrounding it. This talk will cover lessons learned and why scoring is not enough.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The Danish OS2 – Public Digitization Network is an association with 78 public organizations as members. OS2 is not a developing house, not code stewards, rather the association supports development and maintenance of open source IT-solutions through collaboration between public entities and private IT-companies. Solutions are developed as open source and made publicly available. OS2 maintain a governance model which all solutions must comply. In this talk by Rasmus Frey, the head of the main secretariat in OS2, will describe the organization and explain some elements of when it goes well or wrong in governing a public codebase and its life in the public sector.&lt;/p&gt;</description>
        <persons>
          <person id="8751">Rasmus Frey</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/lessons_from_danish_os2/attachments/slides/5205/export/events/attachments/lessons_from_danish_os2/slides/5205/06_02_2022_OS2_FOSDEM_presentation_compressed.pdf">Slidedeck - Lessons from Danish OS2</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.public-code/lessons_from_danish_os2.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/lessons_from_danish_os2.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-lessons_from_danish_os2:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-lessons_from_danish_os2:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12819.php">Submit feedback</link>
        </links>
      </event>
      <event id="12878">
        <start>12:20</start>
        <duration>00:25</duration>
        <room>D.public-code</room>
        <slug>publiccodeyml</slug>
        <title>PublicCode.yml - index all public software!</title>
        <subtitle/>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;PublicCode.yml is a decentralized standard for indexing public software developed by both public and private entities. The specification has always been an open project, but as of December 15th, it has fully transitioned to an open-governance model. Denmark, France, Germany, Israel, and Italy were the official founding countries, and we are looking for more participants to join us. In this presentation, we'll go over the technical ecosystem, current implementations, and how you can get involved - either as a Free Software project or as a government - to promote the use and development of Free Software by public entities, and how to help your Free Software project gain more adoption in public institutions.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3108">Riccardo Iaconelli</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/publiccodeyml">GitHub organization</link>
          <link href="https://video.fosdem.org/2022/D.public-code/publiccodeyml.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/publiccodeyml.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-publiccodeyml:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-publiccodeyml:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12878.php">Submit feedback</link>
        </links>
      </event>
      <event id="12747">
        <start>12:55</start>
        <duration>00:20</duration>
        <room>D.public-code</room>
        <slug>9000_public_code_repositories</slug>
        <title>We listed +9000 public code repositories. Now what?</title>
        <subtitle>How to build valuable services on top of fragile assets</subtitle>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The French administration recently announced https://code.gouv.fr, a website listing more than 9000 repositories from the French public sector. What next?&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this lightening talk, I want to quickly explain how we built this and what we find in these repositories.  The core of my talk will be about what valuable services we aim to provide to public agencies on top of this list, depending on who they are and what they need.  As this topic is partly speculative, we are eager to engage with the audience in a short discussion on what they think would be valuable.&lt;/p&gt;</description>
        <persons>
          <person id="2418">Bastien</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://code.gouv.fr">code.gouv.fr</link>
          <link href="https://sr.ht/~etalab/">Repos from Etalab Free Software task force</link>
          <link href="https://video.fosdem.org/2022/D.public-code/9000_public_code_repositories.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/9000_public_code_repositories.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-9000_public_code_repositories:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-9000_public_code_repositories:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12747.php">Submit feedback</link>
        </links>
      </event>
      <event id="12809">
        <start>13:25</start>
        <duration>00:20</duration>
        <room>D.public-code</room>
        <slug>beware_of_culture</slug>
        <title>Beware of culture</title>
        <subtitle>– what to do as a community manager?</subtitle>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Facilitating a sense of belonging across different cultures in the Danish public sector. A community manager’s point of view.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;We have many active communities in the Danish open source network OS2. As the communication and community manager, it is on me to facilitate a welcoming and introcluding atmosphere between the members and the network. My methods are primarily focused on written text, storytelling, and case stories. But not one strategy will work on everybody. The 'cultures' I will be referring to are the local cultures in the different IT-departments in the public sector. All the open source products OS2 governs should ideally allow for any person to come with ideas - regardless of the local culture of procuring and reusing software.&lt;/p&gt;

&lt;p&gt;This talk will not be technical but rather point to the "soft" element of governing an public open source product.&lt;/p&gt;</description>
        <persons>
          <person id="8636">Charlotte Heikendorf</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.public-code/beware_of_culture.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/beware_of_culture.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-beware_of_culture:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-beware_of_culture:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12809.php">Submit feedback</link>
        </links>
      </event>
      <event id="12633">
        <start>13:55</start>
        <duration>00:45</duration>
        <room>D.public-code</room>
        <slug>decidim</slug>
        <title>Decidim</title>
        <subtitle>Free Open Source Participatory Democracy for Cities and Organizations</subtitle>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Decidim (decidim.org) is a digital platform for participatory democracy, built entirely and collaboratively as free open source software. More specifically, Decidim is a web environment (a framework) produced in Ruby on Rails (a programming language) that allows anyone to create and configure a website platform to be used as a political network for democratic participation. The platform can be deployed by any organization (local/regional/national governments, associations, universities, NGOs, or cooperatives) to host large scale citizen participatory processes for strategic planning, participatory budgeting, public consultations and collaborative policy-making. The project was launched in 2017 in Barcelona and, 4 years later, there are more than 400 active instances of Decidim around the world. In this talk we will present the lessons from this outreach process advocating for a radical model of participatory democracy in contexts as different as the Helsinki City Council, the Mexico City Government, the New York City Commission on Civic Engagement, the French National Assembly, the Italian Government or the European Commission.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8549">Andrés Pereira de Lucena</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/decidim/attachments/slides/5046/export/events/attachments/decidim/slides/5046/Decidim_2022_FOSDEM_en.pdf">Decidim FOSDEM presentation</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.public-code/decidim.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/decidim.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-decidim:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-decidim:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12633.php">Submit feedback</link>
        </links>
      </event>
      <event id="12358">
        <start>14:50</start>
        <duration>00:30</duration>
        <room>D.public-code</room>
        <slug>bluetooth_beyond_digital_contact_tracing</slug>
        <title>Bluetooth beyond Digital Contact Tracing</title>
        <subtitle>Using Bluetooth for wider public healthcare improvements</subtitle>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Herald Project created a reliable API for data exchange used in nations' COVID-19 Digital Contact Tracing applications. The same Bluetooth LE and MESH technology can be used to improve healthcare operations - replacing aging pagers, finding healthcare equipment, navigating through complex environments, and in wearables for personal healthcare monitoring.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;This presentation talks about the use of the Herald API beyond Digital Contact Tracing, using a mix of opensource software, hardware, and data. This can be used to implement public health policy whilst respecting individual freedoms, including freedom of movement internationally.&lt;/p&gt;</description>
        <persons>
          <person id="8486">Adam Fowler</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/bluetooth_beyond_digital_contact_tracing/attachments/slides/4985/export/events/attachments/bluetooth_beyond_digital_contact_tracing/slides/4985/lfph_herald_fosdem_20220124.pdf">Main Presentation Slides</attachment>
        </attachments>
        <links>
          <link href="https://heraldprox.io">Project website</link>
          <link href="https://github.com/theheraldproject">Project GitHub organisation</link>
          <link href="https://video.fosdem.org/2022/D.public-code/bluetooth_beyond_digital_contact_tracing.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/bluetooth_beyond_digital_contact_tracing.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-bluetooth_beyond_digital_contact_tracing:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-bluetooth_beyond_digital_contact_tracing:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12358.php">Submit feedback</link>
        </links>
      </event>
      <event id="12874">
        <start>15:30</start>
        <duration>01:00</duration>
        <room>D.public-code</room>
        <slug>aleksis</slug>
        <title>AlekSIS, the Free School Information System</title>
        <subtitle>Taking on digitisation and digital education at once</subtitle>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Public schools are one natural way to get people in contact with free software, and helping them shape their digital environment with it. The AlekSIS project develops a free, open School Information System that doubles as a platform for students of any age to develop apps to digitise their own schools.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;School Information Systems are programs that help to digitise several processes in public or private schools, reaching from timetables and substitution plans over school meal plans, digital class registers, up to payment systems, and much more.&lt;/p&gt;

&lt;p&gt;Starting out as two independent solutions for School Information Systems, AlekSIS is an actively developed free software project, made by students, teachers, and software engineers together. It is designed to be both a stable and secure software solution, readily available for schools, and a platform that can be used in classes to learn and teach coding. Students can make their own apps, that are seamlessly integrated into the platform, to help digitise real-world scenarios at their schools.&lt;/p&gt;

&lt;p&gt;In this talk, we will show what AlekSIS is, and explain the scheme behind making it a learning platform for young app developers at the same time.&lt;/p&gt;</description>
        <persons>
          <person id="2214">Dominik George</person>
          <person id="8369">Jonathan Weth</person>
          <person id="8963">Jonathan K</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/aleksis/attachments/slides/4964/export/events/attachments/aleksis/slides/4964/AlekSIS_FOSDEM_2022.pdf">Presentation slides</attachment>
        </attachments>
        <links>
          <link href="https://aleksis.org">AlekSIS project website</link>
          <link href="https://schul-frei.dev">schul-frei project</link>
          <link href="https://teckids.org">Teckids e.V.</link>
          <link href="https://edugit.org/AlekSIS">AlekSIS repos on EduGit</link>
          <link href="https://video.fosdem.org/2022/D.public-code/aleksis.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/aleksis.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-aleksis:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-aleksis:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12874.php">Submit feedback</link>
        </links>
      </event>
      <event id="13102">
        <start>16:40</start>
        <duration>00:15</duration>
        <room>D.public-code</room>
        <slug>educamadrid</slug>
        <title>EducaMadrid, the Free and Educational Technology Platform of Madrid</title>
        <subtitle/>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;EducaMadrid is an Educational Technology Platform based on Free Software that offers multiple interconnected and complementary services: school websites, teachers' blogs, virtual classrooms, media library, cloud, mail, videoconferencing, MAdrid_linuX, etc.&lt;/p&gt;

&lt;p&gt;It offers the possibility to develop digital competence, communication between students and teachers and to implement teaching processes both face-to-face and remotely in a secure, free and sustainable environment.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8851">Adolfo Sanz De Diego</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/educamadrid/attachments/slides/4834/export/events/attachments/educamadrid/slides/4834/educamadrid_fosdem_2022_01.pdf"/>
        </attachments>
        <links>
          <link href="https://www.educa2.madrid.org/educamadrid/">https://www.educa2.madrid.org/educamadrid/</link>
          <link href="https://video.fosdem.org/2022/D.public-code/educamadrid.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/educamadrid.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-educamadrid:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-educamadrid:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13102.php">Submit feedback</link>
        </links>
      </event>
      <event id="12973">
        <start>17:05</start>
        <duration>00:15</duration>
        <room>D.public-code</room>
        <slug>open_source_policy</slug>
        <title>Open Source Policy</title>
        <subtitle>Creating value beyond code</subtitle>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this lighting talk we want to talk about the potential of open source not only for code, but also for policy documents.&lt;/p&gt;

&lt;p&gt;One of the pillars to promote open government at any level of government is that there should exist an open data policy. However, in the Mexican context, although one already exists at the federal level, very few states and municipalities have open data policies. This is partly due to the lack of knowledge and culture about open government, especially at the municipal level.&lt;/p&gt;

&lt;p&gt;From Codeando México we work to promote citizen participation and open government, and we have carried out several exercises to co-create open data policies with the three levels of government: federal, state and municipal.&lt;/p&gt;

&lt;p&gt;With this experience, we saw the need for the creation of an open data policy with a free use license. This policy, a work in progress, will be hosted in an open repository, will allow any level of government that wants to have an open data policy to adopt it and adapt it to their needs in a short time.&lt;/p&gt;

&lt;p&gt;This project is nourished not only by the experience of Mexican civil society of the last 10 years but also, being an open source project, it will be in continuous evolution and improvement with the contributions of governments, civil society and any interested citizen.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8943">Ricardo Mirón</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/open_source_policy/attachments/slides/5253/export/events/attachments/open_source_policy/slides/5253/FOSDEM_Open_Source_Policy.pdf">Open Source Policy Slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.public-code/open_source_policy.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/open_source_policy.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-open_source_policy:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-open_source_policy:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12973.php">Submit feedback</link>
        </links>
      </event>
      <event id="13122">
        <start>17:30</start>
        <duration>00:20</duration>
        <room>D.public-code</room>
        <slug>closing_public_code</slug>
        <title>Closing of the Public Code devroom</title>
        <subtitle>Reflections from the day</subtitle>
        <track>Public Code</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Closing of the devroom with some reflections of what we have heard through the day. What might happen next and what would we like to see more of next year?&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7778">Boris van Hoytema</person>
          <person id="8436">Jan Ainali</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.public-code/closing_public_code.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.public-code/closing_public_code.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#public-code-closing_public_code:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#public-code-closing_public_code:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13122.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.python">
      <event id="12392">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.python</room>
        <slug>python_kafka</slug>
        <title>Get to know Apache Kafka with Jupyter Notebooks</title>
        <subtitle/>
        <track>Python</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Apache Kafka is recognised as the best data streaming platform around, but it can be difficult to observe what is happening when you are just getting started with this excellent technology platform. In this session, you will get a tour of key Kafka features using the delightful web UI of Jupyter notebooks.&lt;/p&gt;

&lt;p&gt;Use the notebooks to see Kafka and Python in action, producing and consuming records. We’ll also cover how to get the best from your application by making good use of topic partitioning and consumer groups. From high-level concepts to nitty-gritty details, this session will equip you with the skills you need to build applications with Kafka. Recommended for anyone curious about Apache Kafka or using Jupyter to work with or learn new data platforms.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8515">Francesco Tisiot</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/python_kafka/attachments/slides/5032/export/events/attachments/python_kafka/slides/5032/Apache_Kafka_Jupyter_Notebooks">Apache Kafka Jupyter Notebooks</attachment>
        </attachments>
        <links>
          <link href="https://github.com/aiven/python-notebooks-for-apache-kafka">github repository</link>
          <link href="https://speakerdeck.com/ftisiot/get-to-know-apache-kafka-with-jupyter-notebooks">slides</link>
          <link href="https://video.fosdem.org/2022/D.python/python_kafka.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.python/python_kafka.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#python-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#python-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#python-python_kafka:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#python-python_kafka:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12392.php">Submit feedback</link>
        </links>
      </event>
      <event id="12852">
        <start>10:30</start>
        <duration>00:25</duration>
        <room>D.python</room>
        <slug>python_async_sqlalchemy</slug>
        <title>Introducing Asynchronous SQLAlchemy</title>
        <subtitle/>
        <track>Python</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Driven by the immense popularity of asynchronous frameworks, such as FastAPI, asynchronous database support suddenly became a hot topic in the Python community. As talking to your database often forms a significant portion of the input and output of your application, it's important to do that asynchronously as well. With the release of version 1.4, SQLAlchemy added support for Asynchronous I/O for both its core and ORM features. This means that you can now use the popular SQL toolkit for Python in your asynchronous applications.&lt;/p&gt;

&lt;p&gt;In my talk, I will introduce you to the newly added support for asyncio in SQLAlchemy. I will go over how easy it is to set up the new AsyncEngine, point you to some of the differences with synchronous SQLAlchemy, and show you some of the pitfalls to avoid. In addition, I will also show you how you can run your existing synchronous SQLAlchemy code asynchronously to help you transition to a fully asynchronous application. By the end of my talk, you should know enough to start your own asynchronous SQLAlchemy adventure.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7843">Sebastiaan Zeeff</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://docs.sqlalchemy.org/en/14/orm/extensions/asyncio.html">SQLAlchemy Documentation — Asynchronous I/O (asyncio)</link>
          <link href="https://sebastiaanzeeff.nl/fosdem-2022/">Talk Slides and Additional Information</link>
          <link href="https://www.linkedin.com/in/sebastiaanzeeff/">LinkedIn</link>
          <link href="https://twitter.com/SebastiaanZeeff">Twitter</link>
          <link href="https://github.com/SebastiaanZ/introducing-asynchronous-sqlalchemy/">Code + Slides</link>
          <link href="https://video.fosdem.org/2022/D.python/python_async_sqlalchemy.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.python/python_async_sqlalchemy.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#python-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#python-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#python-python_async_sqlalchemy:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#python-python_async_sqlalchemy:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12852.php">Submit feedback</link>
        </links>
      </event>
      <event id="12807">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>D.python</room>
        <slug>python_concurrency_in_webapps</slug>
        <title>Handling Concurrency in Web Application</title>
        <subtitle>How *not* to build a URL Shortener</subtitle>
        <track>Python</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Concurrency in web applications is so easy to get wrong, and so hard to identify and debug when it comes to bite you. In this talk I'm going to present common concurrency issues with even the simplest application, and suggest ways to identify and prevent them!&lt;/p&gt;</abstract>
        <description>&lt;p&gt;In this talk I'll present common issues, and different approaches for dealing with concurrency:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Why it is better to ask for forgiveness instead of permission when dealing with concurrency&lt;/li&gt;
&lt;li&gt;What is the TOCTOU (time-of-check-time-of-use) problem, how it can happen and how to address it&lt;/li&gt;
&lt;li&gt;How database locking can help with concurrency, and how to avoid it!&lt;/li&gt;
&lt;li&gt;How and when to rely on database features to maintain correctness&lt;/li&gt;
&lt;/ul&gt;
</description>
        <persons>
          <person id="7898">Haki Benita</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://hakibenita.com">Personal welsite</link>
          <link href="https://video.fosdem.org/2022/D.python/python_concurrency_in_webapps.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.python/python_concurrency_in_webapps.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#python-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#python-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#python-python_concurrency_in_webapps:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#python-python_concurrency_in_webapps:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12807.php">Submit feedback</link>
        </links>
      </event>
      <event id="12590">
        <start>11:30</start>
        <duration>00:25</duration>
        <room>D.python</room>
        <slug>python_type_safety</slug>
        <title>Sleep better with type-safe Python</title>
        <subtitle/>
        <track>Python</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Type hints are an essential part of modern Python. By combining type hints with a static type checker and libraries which enable runtime type checking, it is possible to achieve runtime type-safe Python applications.&lt;/p&gt;

&lt;p&gt;This talk discusses the motivation for extensive usage of type hints, how to gradually add types to existing projects, how to deal with untyped dependencies, and finally, how to achieve runtime type-safety without sacrificing performance.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8644">Jerry Pussinen</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/python_type_safety/attachments/slides/5175/export/events/attachments/python_type_safety/slides/5175/Sleep_better_with_type_safe_Python_Jerry_Pussinen.pdf"/>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.python/python_type_safety.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.python/python_type_safety.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#python-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#python-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#python-python_type_safety:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#python-python_type_safety:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12590.php">Submit feedback</link>
        </links>
      </event>
      <event id="12860">
        <start>13:00</start>
        <duration>00:30</duration>
        <room>D.python</room>
        <slug>python_unicode</slug>
        <title>Messing with unicode</title>
        <subtitle>A few possible attacks with unicode</subtitle>
        <track>Python</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Let's look at a few 'tricks' with unicode that can make a program look like it's doing (or not doing, for that matter) something it doesn't. Based on the findings in a recent publication, these are well worth being aware of; both from a security point of view and for simply being on your guard against friends who may be trying to pull a prank on you :-D.&lt;/p&gt;

&lt;p&gt;These tricks are well suited for trojan attacks as it can be difficult to detect even with a manual code review thanks to aspects of unicode like bidirectional (bidi) control characters.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The talk is based on some of the possibilites described in the paper "Trojan Source: Invisible vulnerabilities" by Nicholas Boucher and Ross Anderson of University of Cambridge. The implications of this work with regard to Python has been outlined in PEP 672.&lt;/p&gt;

&lt;p&gt;Examples of using/abusing unicode inlude:
 - Look-alike characters (homoglyphs) being used to make two different functions and make calls of one function look like that of the other (eg: Cyrillic е and Latin e are too similar for us to distinguish easily).
 - Use bidi control characters to make a part of the appear to be present when it's actually part of a comment.
 - Classic trick of naming files so that even an .exe file can look like a .pdf.
 - Use of invisible characters to make strings that look same when they aren't.&lt;/p&gt;</description>
        <persons>
          <person id="8309">Julin Shaji</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/python_unicode/attachments/slides/5023/export/events/attachments/python_unicode/slides/5023/unicode.pdf">messing_with_unicode.pdf</attachment>
        </attachments>
        <links>
          <link href="https://trojansource.codes/trojan-source.pdf">Paper describing the unicode attacks</link>
          <link href="https://www.python.org/dev/peps/pep-0672/">PEP 672</link>
          <link href="https://video.fosdem.org/2022/D.python/python_unicode.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.python/python_unicode.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#python-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#python-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#python-python_unicode:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#python-python_unicode:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12860.php">Submit feedback</link>
        </links>
      </event>
      <event id="12579">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.python</room>
        <slug>python_spyql</slug>
        <title>SPyQL - SQL with Python in the middle</title>
        <subtitle>Making command-line data processing more intuitive, readable and powerful</subtitle>
        <track>Python</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;&lt;a href="https://github.com/dcmoura/spyql"&gt;SPyQL&lt;/a&gt; is SQL with Python in the middle, an open-source project fully written in Python for making command-line data processing more intuitive, readable and powerful. Try mixing in the same pot: a SQL SELECT for providing the structure, Python expressions for defining transformations and conditions, the essence of awk as a data-processing language, and the JSON handling capabilities of jq.&lt;/p&gt;

&lt;p&gt;In this event I will describe the SPyQL language, highlighting its unique features. By the end of this presentation you will know how to write SPyQL queries (probably you already know :-) ), and you will be looking forward to starting using it! I will be solving the task of calculating aggregations in awk (for a CSV), in jq (for a JSON) and in SPyQL (for both). I will then show you a couple more examples where we will be using SPyQL 1) to automate a scaling operation of k8s pods, and 2) to continuously calculate statistics from a Kafka data stream.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;How does a SPyQL query looks like?&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;IMPORT pendulum AS p 
SELECT
    (p.now() - p.from_timestamp(purchase_ts)).in_days() AS days_ago,
    sum_agg(price * quantity) AS total
FROM csv
WHERE department.upper() == 'IT' and purchase_ts is not Null
GROUP BY 1
ORDER BY 1
TO json
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Simple, readable, and, as all SPyQL programs, it's an 1-liner. In a single statement we are 1) reading a CSV (of purchases) with automatic header detection, dialect detection, type inference and casting, 2) filtering out records that do not belong to the IT department or do not have a purchase timestamp 3) summing the total purchases and grouping by how many days ago they happened, 4) sorting from the most to the least recent day and 5) writing the result in JSON format. All this without loading the dataset into memory.&lt;/p&gt;

&lt;p&gt;SPyQL will change data-processing in the terminal, making it accessible to anyone who knows a little-bit of Python and understands the basics of a SQL SELECT.
On the other hand, it will give super-powers to experienced users. The possibilities are endless as you can import any Python library, and pipe data from/to any command-line tool. From querying APIs and Kafka, to write to files or databases, SPyQL will be the tool of choice for processing data in the command-line!&lt;/p&gt;</description>
        <persons>
          <person id="8476">Daniel Moura</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/python_spyql/attachments/slides/5054/export/events/attachments/python_spyql/slides/5054/spyql_fosdem22_slides.pdf">Slides for SPyQL @ FOSDEM22</attachment>
        </attachments>
        <links>
          <link href="https://github.com/dcmoura/spyql">SPyQL repo at GitHub</link>
          <link href="https://vimeo.com/danielcmoura/spyqldemo">SPyQL demo</link>
          <link href="https://video.fosdem.org/2022/D.python/python_spyql.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.python/python_spyql.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#python-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#python-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#python-python_spyql:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#python-python_spyql:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12579.php">Submit feedback</link>
        </links>
      </event>
      <event id="13060">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.python</room>
        <slug>python_mimics</slug>
        <title>Mimics - Records operations to replay them later</title>
        <subtitle/>
        <track>Python</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;https://github.com/maarten-dp/mimics is a tool with the intention to defer actions done on objects or classes. These actions can then be executed at a later date when the subject, to which these actions should be applied to, is available. This is mostly a joke project with no real world applications, but it has some neat implementations showcasing the power of python.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7503">Maarten De Paepe</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/python_mimics/attachments/slides/5221/export/events/attachments/python_mimics/slides/5221/slides">fosdem 2022 slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.python/python_mimics.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.python/python_mimics.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#python-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#python-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#python-python_mimics:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#python-python_mimics:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13060.php">Submit feedback</link>
        </links>
      </event>
      <event id="13082">
        <start>16:30</start>
        <duration>00:30</duration>
        <room>D.python</room>
        <slug>python_feature_flags</slug>
        <title>Implementing and managing feature flags</title>
        <subtitle>How to effectively manage your feature flags in a monolitic Django application</subtitle>
        <track>Python</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;When developing a plateform with a large code base, multiple Django applications in a monolith, feature flags are a must have to keep your release cycle short. Those allow teams to develop a feature throughout multiple releases without users being aware that this feature is under development. Shorter release cycle are still possible without hindering quality teams or users.&lt;/p&gt;

&lt;p&gt;At GitGuardian, we use feature flags for multiple purposes: distinguishing between code deployment and feature rollout, managing differences for premium accounts and A/B testing. We will talk about how we handle feature flags for saas and on premise deployment and how to avoid some common on premise pitfalls with feature flags.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7107">Mehdi Raddadi</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/python_feature_flags/attachments/slides/4857/export/events/attachments/python_feature_flags/slides/4857/FOSDEM_2022_How_to_manage_feature_flags_GitGuardian_MRA">FOSDEM 2022 - How to manage feature flags</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.python/python_feature_flags.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.python/python_feature_flags.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#python-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#python-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#python-python_feature_flags:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#python-python_feature_flags:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13082.php">Submit feedback</link>
        </links>
      </event>
      <event id="12580">
        <start>17:00</start>
        <duration>00:25</duration>
        <room>D.python</room>
        <slug>python_cubicweb</slug>
        <title>CubicWeb: bootstraping a web-application from RDF data</title>
        <subtitle/>
        <track>Python</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We made the Web accessible to human.
We are making the web accessible to computers with Linked Open Data (LOD - https://www.w3.org/standards/semanticweb/data).
More and more RDF data is created by people and institutions to contribute to the LOD.
However, publishing this RDF data with content negotiation is rarely done, because there is no on-shelve solution.
Moreover, there is no easy to use user interface to manage linked data (including CRUD operations, but also user permissions, rendering, etc.).&lt;/p&gt;

&lt;p&gt;CubicWeb is a SCMS (Semantic Content Management System) for Linked Open Data (https://forge.extranet.logilab.fr/cubicweb/cubicweb).
This python-based framework can be used to import OWL schema and RDF data automatically to generate a new CubicWeb instance.
This instance can be used out-of-the-box as a single application to serve RDF data through a conventional web interface for browsing and through
content negotiation for downloading. No need to configure anything, just import and launch the app.
The CubicWeb framework implements an administration interface to manage data easily even
for non-technical people. All the common features of a web application framework are available.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7726">Fabien Amarger</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/python_cubicweb/attachments/slides/5279/export/events/attachments/python_cubicweb/slides/5279/slides">CubicWeb: bootstraping a web-application from RDF data</attachment>
        </attachments>
        <links>
          <link href="https://forge.extranet.logilab.fr/cubicweb/cubicweb">official CubicWeb repository</link>
          <link href="https://forge.extranet.logilab.fr/cubicweb/owl2yams">OWL2yams project: generate CubicWeb instance from RDF data</link>
          <link href="https://video.fosdem.org/2022/D.python/python_cubicweb.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.python/python_cubicweb.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#python-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#python-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#python-python_cubicweb:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#python-python_cubicweb:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12580.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.raku">
    </room>
    <room name="D.retro">
    </room>
    <room name="D.safety">
    </room>
    <room name="D.dependency">
      <event id="12991">
        <start>10:00</start>
        <duration>00:05</duration>
        <room>D.dependency</room>
        <slug>devroom_introduction</slug>
        <title>Devroom introduction</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The devroom intro by devroom organization team!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3237">Kate Stewart</person>
          <person id="4271">Philippe Ombredanne</person>
          <person id="7543">Antoine Mottier</person>
          <person id="7583">Michael C. Jaeger</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.dependency/devroom_introduction.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/devroom_introduction.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom_introduction:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom_introduction:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12991.php">Submit feedback</link>
        </links>
      </event>
      <event id="12986">
        <start>10:05</start>
        <duration>00:15</duration>
        <room>D.dependency</room>
        <slug>package_url_and_version_range_spec</slug>
        <title>Package URL and Version range spec</title>
        <subtitle>Towards mostly universal dependency resolution</subtitle>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Package URLs are a compact way to identify software packages across multiple ecosystems.
Together with the new "vers" Version Range Specifier, these two mini specs will offer a
new way to create new, mostly universal dependency resolvers and installers, working
across ecosystems.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Because &lt;strong&gt;no tech stack is an island&lt;/strong&gt; running on a single programming language and in a single package ecosystem, we need a way to &lt;strong&gt;talk about packages across ecosystems&lt;/strong&gt;: talk about their type, name, location, version and dependent version ranges. &lt;strong&gt;purl&lt;/strong&gt; and &lt;strong&gt;vers&lt;/strong&gt; are an attempt to solve this problem.&lt;/p&gt;

&lt;p&gt;How to talk about packages, dependencies and vulnerabilities using a common language?&lt;/p&gt;

&lt;p&gt;I will present &lt;strong&gt;Package URL&lt;/strong&gt;, a way to references package across ecosystems which is emerging as a de-facto standard. And I will introduce a new work-in-progress, mostly universal notation to express version ranges to be used in resolving package dependencies such as "I require package foo, version 2.0 or later versions" and referencing affected vulnerable packages versions as in  "vulnerability CVE-123 affects package bar, version 3.1 and version 4.2 but not version 5".&lt;/p&gt;

&lt;p&gt;These two will show a way to create new, mostly universal dependency resolvers and installers, working across ecosystems and we will promote the rise of universal package managements where one tool and one unified spec can rule them all.&lt;/p&gt;</description>
        <persons>
          <person id="4271">Philippe Ombredanne</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/package_url_and_version_range_spec/attachments/slides/5078/export/events/attachments/package_url_and_version_range_spec/slides/5078/fosdem_2022_02_07_sca_devroom_purl_vers_ombredanne.pdf">Package URL and Version range spec presentation</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/package_url_and_version_range_spec/attachments/slides/5079/export/events/attachments/package_url_and_version_range_spec/slides/5079/fosdem_2022_02_07_sca_devroom_purl_vers_ombredanne.odp">Package URL and Version range spec presentation (libreoffice)</attachment>
          <attachment type="audio" href="https://fosdem.org/2022/schedule/event/package_url_and_version_range_spec/attachments/audio/5264/export/events/attachments/package_url_and_version_range_spec/audio/5264/fosdem_2022_02_07_sca_devroom_purl_vers_ombredanne_v3.mp4">Video</attachment>
        </attachments>
        <links>
          <link href="https://github.com/package-url/purl-spec">Purl Spec</link>
          <link href="https://github.com/package-url/purl-spec/pull/139">VERS spec</link>
          <link href="https://video.fosdem.org/2022/D.dependency/package_url_and_version_range_spec.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/package_url_and_version_range_spec.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-package_url_and_version_range_spec:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-package_url_and_version_range_spec:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12986.php">Submit feedback</link>
        </links>
      </event>
      <event id="12545">
        <start>10:20</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>dependency_ospo</slug>
        <title>How OSPOs can help secure the software supply chain</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Legal Risk Mitigation is one of the three main functions of an &lt;a href="https://github.com/todogroup/ospodefinition.org"&gt;OSPO&lt;/a&gt; (designated places where open source is supported, nurtured, shared, explained, and grown inside an organization). OSPOs often oversee aspects of a company’s open source license compliance process and supply chain as one of the first activities. The responsibilities include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Maintaining open source license compliance reviews and oversight&lt;/li&gt;
&lt;li&gt;Running a review process for inbound code use&lt;/li&gt;
&lt;li&gt;Ensuring that the company contributes back to open source projects effectively&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;To a certain degree, any organization calling itself an OSPO likely indicates the organization has reached a maturity stage where Executive-level recognition that OSS is an important strategic asset and builds a critical mass of processes, procedures, and tools to streamline and facilitate open source consumption and participation across divisions. Indeed, these activities also include a wide range of software composition analysis solutions such as Software Bill of Materials (SBOM), license management scanning, or continuous monitoring tools.&lt;/p&gt;

&lt;p&gt;While some OSPOs rely on Software composition analysis vendors like Synopsys and Tidelift, others decide to make their own built-in solutions. During this presentation, Ana Jimenez, PM at &lt;a href="https://todogroup.org/members/"&gt;TODO group&lt;/a&gt; (an open community of organizations who run OSPOs worldwide), will introduce the evolution and expansion of OSPOs over the years from a supply chain perspective, some of the common SCA tooling used, as well as how OSPOs can contribute and nurture the &lt;a href="https://landscape.todogroup.org/card-mode?category=sca&amp;amp;grouping=category"&gt;ecosystem of SCA tools&lt;/a&gt; to adapt to the needs of the different industries.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8621">Ana Jimenez Santamaria</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.dependency/dependency_ospo.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/dependency_ospo.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-dependency_ospo:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-dependency_ospo:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12545.php">Submit feedback</link>
        </links>
      </event>
      <event id="12856">
        <start>10:40</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>open_source_license_compliance_project</slug>
        <title>Developing an open source license compliance project : our trials, tribulations and achievements</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk aims at presenting our trials and tribulations as well as our achievements in designing a compliance software project for open source licenses.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;"Are all module licenses in our software project compliant with each other ?"&lt;/em&gt;
Many of our customers have asked us this question even though they already had a plethora of software solutions (not always FOSS software) dealing with this topic.
This surprised us, and led us to seek out the cause of their uncertainty. We then discovered that many solutions only look for potential risks and provide reports both too detailed, from the legal POV, for practical use by an engineer, and too technical for practical use by a lawyer.&lt;/p&gt;

&lt;p&gt;As engineers are bound to do, we thought there might be a technical solution to this and launched a project.
As engineers launching a project are bound to do, we encountered a few hitches and made some discoveries along the way.&lt;/p&gt;

&lt;p&gt;Today, here we are to show off the problems we encountered and how we overpassed them, but also to mention that we are open to your contributions (on technical matter or just for suggestions).&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The features of the project are mainly conditioned by our clients:
 - the ability to process a variety of unstructured inputs (zip archives containing code, github or gitlab, dependency manager package lists, and various hypertext links to libraries) ;
 - the requirement of preserving corporate code confidentiality whether in SaaS or on-premise ;
 - outputting a very structured and human-readable report listing actual non-compliances and potential ways to solve these non-compliances ;
 - designing the strategy for integrating our open source software compliance project with CI/CD processes ;
 - and for the non-client-conditioned feature : our product owner decreed that there could be no false negatives in non-compliance detection.&lt;/p&gt;

&lt;p&gt;After a first PoC based on pre-existing code analysis tools (oss review toolkit, licensee, scancode...), we understood that some roadblocks would remain if no improvements were made.
It is not about reinventing the wheel, but moving from wood to rubber.
So we made a new PoC including Machine Learning and the results are much more promising. We will release it very soon under AGPL v3 license.&lt;/p&gt;</description>
        <persons>
          <person id="8744">Pierre Marty</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://slides.com/pierremarty/lincompliance">Presentation support</link>
          <link href="https://github.com/linagora/lincompliance">GitHub repo</link>
          <link href="https://video.fosdem.org/2022/D.dependency/open_source_license_compliance_project.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/open_source_license_compliance_project.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-open_source_license_compliance_project:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-open_source_license_compliance_project:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12856.php">Submit feedback</link>
        </links>
      </event>
      <event id="12556">
        <start>11:00</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>how_to_manage_oss_license_obligation_and_sbom_using_sw360_new_features</slug>
        <title>How to manage OSS license obligations and SBoM by SW360's new features</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The management of SBoM　(software bill of material) is very important for companies to comply with the OpenChain specification.The latest features of SW360 support the management of license obligations and the management of SBOMs in SPDX format. In this presentation, I will introduce and demonstrate the features of SW360.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;OpenChain ISO/IEC 5230 is the International Standard for open source license compliance. In the OpenChain specification, there are descriptions of SBoM management and OSS license obligations, and SW360 has features to help with both of these.&lt;/p&gt;

&lt;p&gt;SPDX is an open standard for communicating software bill of material information, including components, licenses, copyrights, and security references.　This is also ISO standard (ISO/IEC 5962:2021).  A new feature in SW360 is the ability to register, import, and export software component information according to the SPDX format, making it easier to integrate with other tools and manage information received from other companies.&lt;/p&gt;

&lt;p&gt;For managing OSS licenses in SW360, the information about license obligations can be imported from the OSADL (Open Source Automation Development Lab) web site. This OSADL's web site provides a machine-readble summary of the main points of the OSS license in a form that anyone can get. (Licensed by CC-BY-4.0). New features in SW360 allows you to quickly import this OSADL license obigation information into your company's SW360.&lt;/p&gt;

&lt;p&gt;The features introduced presentation may include some that are still under development.&lt;/p&gt;</description>
        <persons>
          <person id="8628">Kouki Hama</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/how_to_manage_oss_license_obligation_and_sbom_using_sw360_new_features/attachments/slides/5198/export/events/attachments/how_to_manage_oss_license_obligation_and_sbom_using_sw360_new_features/slides/5198/fosdem_2022_hama.pdf">How to manage OSS license obligations and SBoM by SW360's new features</attachment>
        </attachments>
        <links>
          <link href="https://github.com/eclipse/sw360">GitHub SW360</link>
          <link href="https://www.eclipse.org">WebSite SW360</link>
          <link href="https://www.osadl.org/Access-to-raw-data.oss-compliance-raw-data-access.0.html">Open Source License Checklists by OSADL </link>
          <link href="https://video.fosdem.org/2022/D.dependency/how_to_manage_oss_license_obligation_and_sbom_using_sw360_new_features.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/how_to_manage_oss_license_obligation_and_sbom_using_sw360_new_features.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-how_to_manage_oss_license_obligation_and_sbom_using_sw360_new_features:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-how_to_manage_oss_license_obligation_and_sbom_using_sw360_new_features:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12556.php">Submit feedback</link>
        </links>
      </event>
      <event id="12992">
        <start>11:20</start>
        <duration>00:40</duration>
        <room>D.dependency</room>
        <slug>software_composition_dependency_panel_1</slug>
        <title>Panel 1: Processing Dependencies and Compositions and Software </title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Granted that software composition and dependency processing are very relevant for software engineering. The presentations have pointed out how such processing is embedded into activities of an organization. We would like to gather feedback about how the current status of adoption and integration looks like.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5401">Maximilian Huber</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.dependency/software_composition_dependency_panel_1.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/software_composition_dependency_panel_1.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-software_composition_dependency_panel_1:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-software_composition_dependency_panel_1:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12992.php">Submit feedback</link>
        </links>
      </event>
      <event id="13546">
        <start>12:00</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>break</slug>
        <title>Break </title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;break&lt;/p&gt;</abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-break:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-break:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13546.php">Submit feedback</link>
        </links>
      </event>
      <event id="12564">
        <start>12:20</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>scanning_for_known_vulnerabilities_in_an_embedded_distribution</slug>
        <title>Scanning for known vulnerabilities in an embedded distribution</title>
        <subtitle>A return on experience from the Eclipse Oniro project</subtitle>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A Linux distribution is a great playing field for testing tools for
vulnerability scanning. It is even a better playing field if it includes
more operating system kernels, like the Eclipse Oniro project does.
Eclipse Oniro targets the Internet of Things (IOT) domain, where fixing
security issues is critical.&lt;/p&gt;

&lt;p&gt;In this talk, Marta is going to present a return on experience of
scanning for known vulerabilities (CVEs) in the Eclipse Oniro project.
The presentation is going to start with an overview of tools based on
Yocto's cve-check and additions from the Oniro project. Then it will
cover examples of fixes, situations when we found errors in databases
and tools, and how we fixed them. Finally, Marta
is going to describe ideas of improvements in existing tools and propose
new tools that can help the community.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="936">Marta Rybczynska</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/scanning_for_known_vulnerabilities_in_an_embedded_distribution/attachments/slides/4835/export/events/attachments/scanning_for_known_vulnerabilities_in_an_embedded_distribution/slides/4835/Rybczynska_scanning_for_known_vulnerabilities.pdf">Scanning in Oniro-Slides</attachment>
        </attachments>
        <links>
          <link href="https://www.youtube.com/watch?v=u6Xo0QF6AMQ">A previous presentation covering the more general topic of security in the distribution at Embedded Linux Conference 2021</link>
          <link href="https://booting.oniroproject.org/">Oniro project and its security tooling </link>
          <link href="https://video.fosdem.org/2022/D.dependency/scanning_for_known_vulnerabilities_in_an_embedded_distribution.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/scanning_for_known_vulnerabilities_in_an_embedded_distribution.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-scanning_for_known_vulnerabilities_in_an_embedded_distribution:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-scanning_for_known_vulnerabilities_in_an_embedded_distribution:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12564.php">Submit feedback</link>
        </links>
      </event>
      <event id="12479">
        <start>12:40</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>reporting_vulnerabilities_within_complex_software_environment_cve_bin_tool</slug>
        <title>Reporting vulnerabilities within a complex software environment</title>
        <subtitle>Using the CVE-Bin-Tool</subtitle>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Detecting known software vulnerabilities is hard to do perfectly. However, the CVE Binary Tool is a tool which has been designed to analyse and trace dependencies by performing a binary analysis that attempts to detect the versions of the libraries in compiled applications in order to determine the vulnerabilities that may be present. Since the tool was initially released, the number of libraries which can be detected has steadily increased so now over 100 libraries can be detected primarily through the effort of students working under the Google Summer of Code (GSOC) programme. Supported libraries have typically been prioritised based on the number and frequency of vulnerabilities reported in the CVE database. The latest version of tool released at the end of 2021 has added capabilities to perform vulnerability scanning of Linux distros, Python applications and to consume Software Bill of Materials (both the SPDX and CycloneDX formats are supported). Further enhancements are planned in 2022.&lt;/p&gt;

&lt;p&gt;This presentation will describe how the tool works, how to use it in a number of use cases and show how you can contribute to further develop the capabilities of the tool.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8564">Anthony Harrison</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/intel/cve-bin-tool/ ">CVE Bin Tool Repo</link>
          <link href="https://github.com/intel/cve-bin-tool/blob/main/presentation/FOSDEM2022/Finding%20vulnerabilities%20using%20CVE-BIN-TOOL.pdf">Slides</link>
          <link href="https://video.fosdem.org/2022/D.dependency/reporting_vulnerabilities_within_complex_software_environment_cve_bin_tool.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/reporting_vulnerabilities_within_complex_software_environment_cve_bin_tool.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-reporting_vulnerabilities_within_complex_software_environment_cve_bin_tool:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-reporting_vulnerabilities_within_complex_software_environment_cve_bin_tool:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12479.php">Submit feedback</link>
        </links>
      </event>
      <event id="12704">
        <start>13:00</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>commoditising_open_source_risk_management</slug>
        <title>Commoditising Open Source Risk Management</title>
        <subtitle>First Open Source SCA Platform</subtitle>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;SCANOSS disrupts the SCA market by offering the first fully Open Source SCA Platform. From the mining tools to the database engine, scanning engine, CLIs to a fully featured Multiplatform Auditing UI. It is all pure open source and available to use. SCANOSS aims at commoditising Open Source Risk Management and driving SBOM adoption not only for large corporations, but also for independent developers and SMEs who are key parts of the Software Supply Chain.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8693">Julian Coccia</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://scanoss.com">SCANOSS Homepage</link>
          <link href="https://st.foundation">Software Transparency Foundation</link>
          <link href="https://osskb.org">OSSKB Homepage</link>
          <link href="https://video.fosdem.org/2022/D.dependency/commoditising_open_source_risk_management.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/commoditising_open_source_risk_management.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-commoditising_open_source_risk_management:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-commoditising_open_source_risk_management:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12704.php">Submit feedback</link>
        </links>
      </event>
      <event id="12996">
        <start>13:20</start>
        <duration>00:40</duration>
        <room>D.dependency</room>
        <slug>software_composition_dependency_panel_2</slug>
        <title>Panel 2: Dependencies for Vulnerability Discovery and Tracking</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;One important use of dependency information is for the identification and discovery of vulnerabilities. The presentations present diverse interesting projects and approaches.  We want to understand if the current approaches address the needs of cybersecurity efforts, how they compare to threats beyond dependency vulnerabilities, and how they can be combined, extended, and learn from each other.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3691">Diomidis Spinellis</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.dependency/software_composition_dependency_panel_2.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/software_composition_dependency_panel_2.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-software_composition_dependency_panel_2:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-software_composition_dependency_panel_2:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12996.php">Submit feedback</link>
        </links>
      </event>
      <event id="13547">
        <start>14:00</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>lunch_break</slug>
        <title>Lunch Break</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;lunch break&lt;/p&gt;</abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-lunch_break:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-lunch_break:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13547.php">Submit feedback</link>
        </links>
      </event>
      <event id="12551">
        <start>14:20</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>generating_sbom_for_your_code_using_oss_review_toolkit</slug>
        <title>Generating SBOM for your code using OSS Review Toolkit</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In this talk Thomas will present how one can use OSS Review Toolkit (ORT) to build a CI/CD workflow to do license/security compliance and generate SBOMs. The talk will include a demonstration of OSS Review Toolkit and how its various features in combination with GitLab-based process can be used to automated FOSS reviews requirements (incl. SPDX SBOM generation) and use crowdsourcing within an organization and the FOSS community to overcome challenges such as large amounts of scan results or missing/incorrect FOSS package metadata.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="5563">Thomas Steenbergen</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://oss-review-toolkit.org/">Project main code repository</link>
          <link href="https://video.fosdem.org/2022/D.dependency/generating_sbom_for_your_code_using_oss_review_toolkit.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/generating_sbom_for_your_code_using_oss_review_toolkit.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-generating_sbom_for_your_code_using_oss_review_toolkit:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-generating_sbom_for_your_code_using_oss_review_toolkit:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12551.php">Submit feedback</link>
        </links>
      </event>
      <event id="12619">
        <start>14:40</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>sbom_resolver_generating_detailed_sboms_for_alpine</slug>
        <title>SBOM Resolver - Generating detailed SBOMs for Alpine</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In the light of increasing importance of supply chain security, obtaining detailed and accurate Software Bills of Material (SBOMs) for software images is fundamentally important. In this talk, we will present a tool called SBOM Resolver which generates detailed SBOMs for Alpine software images. It specifically leverages meta-data from the Alpine package management system to resolve all dependencies of a list of desired packages and enhances the resulting SBOM with additional information such as patches applied by the Alpine community.&lt;/p&gt;

&lt;p&gt;The current implementation is specific to Alpine, however, this presentation aims to introduce the key concepts and based on those start a discussion of how to apply SBOM Resolver to other distributions.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8573">Georg Kunz</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.dependency/sbom_resolver_generating_detailed_sboms_for_alpine.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/sbom_resolver_generating_detailed_sboms_for_alpine.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-sbom_resolver_generating_detailed_sboms_for_alpine:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-sbom_resolver_generating_detailed_sboms_for_alpine:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12619.php">Submit feedback</link>
        </links>
      </event>
      <event id="12938">
        <start>15:00</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>fasten_fine_grained_analysis_software_ecosystems_networks</slug>
        <title>FASTEN: Fine-Grained Analysis of Software Ecosystems as Networks</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;In modern software development, it is common to use open-source software (OSS) to boost productivity. According to the National Vulnerability Database, OSS often has security vulnerabilities. On the other hand, research has shown that developers do not update their dependencies. Because existing security tools suffer from a high false-positive rate as they analyze software at the package level.&lt;/p&gt;

&lt;p&gt;FASTEN analyzes software packages at the finer-grain level by producing an enormous network of software ecosystems. This allows giving vulnerability information at the method level. With this information, developers are notified when their code uses vulnerable methods, and hence they are more confident to update their dependencies. The said functionality will be provided in the famous package managers such as Maven and PyPI.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8370">Amir Mir</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/fasten-project/fasten">FASTEN's GitHub repository</link>
          <link href="https://video.fosdem.org/2022/D.dependency/fasten_fine_grained_analysis_software_ecosystems_networks.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/fasten_fine_grained_analysis_software_ecosystems_networks.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-fasten_fine_grained_analysis_software_ecosystems_networks:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-fasten_fine_grained_analysis_software_ecosystems_networks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12938.php">Submit feedback</link>
        </links>
      </event>
      <event id="12994">
        <start>15:20</start>
        <duration>00:40</duration>
        <room>D.dependency</room>
        <slug>software_composition_dependency_panel_3</slug>
        <title>Panel 3: Creating SBOMs</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Software Bill-of-Material (SBOM) is the foundation when it comes to the exchange between tools and organizations. SBOMs are not new as the session has outlined, rather, mature approaches exist. We would encourage a discussion about the current experience when exchanging SBOMs between organizations and tools today.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7543">Antoine Mottier</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.dependency/software_composition_dependency_panel_3.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/software_composition_dependency_panel_3.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-software_composition_dependency_panel_3:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-software_composition_dependency_panel_3:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12994.php">Submit feedback</link>
        </links>
      </event>
      <event id="12907">
        <start>16:20</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>on_backporting_practices_in_package_dependency_networks</slug>
        <title>On Backporting Practices in Package Dependency Networks</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The practice of backporting aims to bring the benefits of a bug or vulnerability fix from a higher to a lower release of a software package. When such a package adheres to semantic versioning, backports can be recognised as new releases in a lower major train. This is particularly useful in case a substantial number of software packages continues to depend on that lower major train. In this talk, we discuss the backporting practices in four popular package distributions, namely Cargo, npm, Packagist and RubyGems. We observe that many dependent packages could benefit from backports provided by their dependencies. In particular, we find that a majority of security vulnerabilities affect more than one major train but are only fixed in the highest one, letting thousands of dependent packages exposed to the vulnerability. Despite that, we find that backporting updates is quite infrequent, and mostly practised by long-lived and more active packages for a variety of reasons.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The full paper associated with this talk can be found at https://doi.org/10.1109/TSE.2021.3112204
The research has been carried out in the context of the Belgian SECOASSIST "Excellence of Science" Research Project https://secoassist.github.io&lt;/p&gt;</description>
        <persons>
          <person id="6025">Ahmed Zerouali</person>
          <person id="6889">Tom Mens</person>
        </persons>
        <attachments>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/on_backporting_practices_in_package_dependency_networks/attachments/paper/4800/export/events/attachments/on_backporting_practices_in_package_dependency_networks/paper/4800/Paper_published_in_IEEE_TSE_in_2021">Back to the Past -- Analysing Backporting Practices in Package Dependency Networks</attachment>
        </attachments>
        <links>
          <link href="https://doi.org/10.1109/TSE.2021.3112204">IEEE TSE article "Back to the Past -- Analysing Backporting Practices in Package Dependency Networks"</link>
          <link href="https://video.fosdem.org/2022/D.dependency/on_backporting_practices_in_package_dependency_networks.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/on_backporting_practices_in_package_dependency_networks.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-on_backporting_practices_in_package_dependency_networks:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-on_backporting_practices_in_package_dependency_networks:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12907.php">Submit feedback</link>
        </links>
      </event>
      <event id="12701">
        <start>16:40</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>dependency_owasp</slug>
        <title>Operationalize SBOM with OWASP Dependency-Track</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Dependency-Track is an intelligent Component Analysis platform that allows organizations to operationalize the use of CycloneDX Software Bill of Materials (SBOM). The platform allows organizations to quickly identify and reduce risk in the software supply chain and is ideal for use in modern DevSecOps environments, procurement, and M&amp;amp;A.&lt;/p&gt;

&lt;p&gt;Discover the benefits of leveraging OWASP CycloneDX Software Bill of Materials along with OWASP Dependency-Track.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Dependency-Track maintains accurate and complete inventory of all libraries, frameworks, applications, containers, operating systems, firmware, hardware, and services across an organization. The platform provides full-stack traceability for the cloud, for the enterprise, for smart devices, and for IoT.&lt;/p&gt;

&lt;p&gt;Dependency-Track can quickly identify vulnerable components and supports multiple sources of vulnerability intelligence including the National Vulnerability Database (NVD), Sonatype OSS Index, GitHub Advisories, and VulnDB from Risk Based Security. The platform has a flexible policy engine and identifies security, operational, and license risk across development teams, suppliers, and partners in the supply chain.&lt;/p&gt;</description>
        <persons>
          <person id="8688">Steve Springett</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://dependencytrack.org/">https://dependencytrack.org/</link>
          <link href="https://video.fosdem.org/2022/D.dependency/dependency_owasp.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/dependency_owasp.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-dependency_owasp:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-dependency_owasp:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12701.php">Submit feedback</link>
        </links>
      </event>
      <event id="12836">
        <start>17:00</start>
        <duration>00:20</duration>
        <room>D.dependency</room>
        <slug>tracking_software_dependencies</slug>
        <title>Tracking Software Dependencies</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The accurate identification of software elements and their dependency relationships are critical for understand when specific software is exploitable.  Different types of dependencies necessary for security use cases will be explored.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Recently identified vulnerabilities found in Log4j has made it clear that we need to be able to track how software is included and used in applications and systems.  The first challenge is identifying the software element (be it an application, library, component, file, snippet) accurately when there may be multiple ways to refer to it.  The next challenge is clearly articulating the dependencies between these software elements.   Once a vulnerability is identified and correlated with a well identified software element, the dependency information can be used to find if any key software elements may be impacted.&lt;/p&gt;

&lt;p&gt;This talk will go through the approaches for identifying software via external references, as well as they types of relationships that have proven useful in tools so far to map out dependencies between the elements that tools producing SPDX SBOMs have found useful to date.  We will demonstrate a proof of concept utility where an SPDX document with relationship information can be used to query the OSV online vulnerability database.&lt;/p&gt;</description>
        <persons>
          <person id="3237">Kate Stewart</person>
          <person id="8753">Gary O'Neall</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://spdx.dev/">SPDX community homepage</link>
          <link href="https://video.fosdem.org/2022/D.dependency/tracking_software_dependencies.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/tracking_software_dependencies.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-tracking_software_dependencies:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-tracking_software_dependencies:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12836.php">Submit feedback</link>
        </links>
      </event>
      <event id="12995">
        <start>17:20</start>
        <duration>00:40</duration>
        <room>D.dependency</room>
        <slug>software_composition_dependency_panel_4</slug>
        <title>Panel 4: Software Compositions and Dependency Tools</title>
        <subtitle/>
        <track>Software composition and dependency management</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;As the presentations discuss, identifying dependencies can be a tedious task. It depends on the software project itself, as well as the used technology stack how certain dependencies can be identified. In the panel discussion about the special stories when trying to identify all dependencies.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4271">Philippe Ombredanne</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.dependency/software_composition_dependency_panel_4.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.dependency/software_composition_dependency_panel_4.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#dependency-software_composition_dependency_panel_4:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#dependency-software_composition_dependency_panel_4:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12995.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.sds">
      <event id="13210">
        <start>10:00</start>
        <duration>00:10</duration>
        <room>D.sds</room>
        <slug>sds_ceph_csi_k8s_migration</slug>
        <title>Migrate to Ceph-CSI</title>
        <subtitle>Migrate your persistent volumes from old volume plugins to Ceph-CSI</subtitle>
        <track>Software Defined Storage</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Currently, to access storage, many different type of Volume Plugins are used. But many of them like "FlexVolume" and "In-tree" are either OLD, or deprecated.&lt;/p&gt;

&lt;p&gt;In our talk, we wish to discuss the solution of the same, by sharing information about the different types of volume plugins; and demonstrating the migration procedure from deprecated plugins to the latest "CEPH-CSI"(https://github.com/ceph/ceph-csi); with a pre-recorded demo of the same.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8895">Yug Gupta</person>
          <person id="8896">Subham Rai</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/ceph/persistent-volume-migrator">persistent-volume-migrator</link>
          <link href="https://github.com/ceph/ceph-csi">ceph-csi</link>
          <link href="https://video.fosdem.org/2022/D.sds/sds_ceph_csi_k8s_migration.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.sds/sds_ceph_csi_k8s_migration.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#sds-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#sds-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#sds-sds_ceph_csi_k8s_migration:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#sds-sds_ceph_csi_k8s_migration:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13210.php">Submit feedback</link>
        </links>
      </event>
      <event id="12455">
        <start>10:30</start>
        <duration>00:30</duration>
        <room>D.sds</room>
        <slug>sds_garage_introduction</slug>
        <title>Introducing Garage, a new storage platform for self-hosted geo-distributed clusters</title>
        <subtitle/>
        <track>Software Defined Storage</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Garage is a new storage system for building geo-distributed storage clusters. Garage is developped by Deuxfleurs, an experimental self-hosting collective.&lt;/p&gt;

&lt;p&gt;Garage targets primarily home-grown clusters composed of second-hand commodity hardware, spread over multiple physical locations for redundancy. This deployment scenario implies strong constraints on the software, such as having to deal with slow nodes and high latency between nodes. In a fist part of this talk, we will show how Garage's design enables it to function very well in this scenario, contrarily to other solutions we have tested such as Minio or Glusterfs.&lt;/p&gt;

&lt;p&gt;Garage is focused on implementing the Amazon S3 protocol, a de-facto standard that makes it directly usable as a storage backend for many web applications (such as Nextcloud) or as a backup target. A second part of this talk will be focused on showing how Garage integrates with Deuxfleurs' current self-hosting stack, and how it can be easily configured with a variety of applications.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8541">Alex Auvolat</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://garagehq.deuxfleurs.fr">Website</link>
          <link href="https://git.deuxfleurs.fr/Deuxfleurs/garage">Source code</link>
          <link href="https://garagehq.deuxfleurs.fr/design/benchmarks.html">Benchmarks</link>
          <link href="https://video.fosdem.org/2022/D.sds/sds_garage_introduction.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.sds/sds_garage_introduction.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#sds-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#sds-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#sds-sds_garage_introduction:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#sds-sds_garage_introduction:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12455.php">Submit feedback</link>
        </links>
      </event>
      <event id="13213">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>D.sds</room>
        <slug>sds_replicate_and_migrate_ceph_rgw_to_cloud</slug>
        <title>Data Replication and Migration from Ceph RGW to Cloud</title>
        <subtitle/>
        <track>Software Defined Storage</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;With seemingly insatiable demand for and growth of data within the organizations, secure and quick movement of the data often becomes a challenge in any Hybrid Cloud enviroment. The external tools and multi-cloud gateway providers add overhead to the latency and may not leverage full capabilities of On-Prem infrastructure. To overcome this, Ceph distributed storage, often handling petabytes of data, provides ways to move data directly from its OnPrem S3 RGW servers to multiple cloud providers, thus easing data movement.&lt;/p&gt;

&lt;p&gt;In this session, we will briefly discuss about the CloudSync and CloudTransition features in Ceph RadosGateway (RGW) which can be used to replicate and migrate data to any external cloud providers.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;We will also look into how to configure and enable these features, their current limitation and future work.&lt;/p&gt;

&lt;p&gt;As a pre-requisite, it would help to know what ceph object gateway is and how it works (https://docs.ceph.com/en/latest/radosgw/)&lt;/p&gt;</description>
        <persons>
          <person id="8897">Soumya Koduri</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/sds_replicate_and_migrate_ceph_rgw_to_cloud/attachments/slides/5039/export/events/attachments/sds_replicate_and_migrate_ceph_rgw_to_cloud/slides/5039/Data_Migration_and_Replication_from_Ceph_RGW_to_Cloud.pdf">Data Migration and Replication from Ceph RGW to Cloud</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.sds/sds_replicate_and_migrate_ceph_rgw_to_cloud.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.sds/sds_replicate_and_migrate_ceph_rgw_to_cloud.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#sds-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#sds-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#sds-sds_replicate_and_migrate_ceph_rgw_to_cloud:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#sds-sds_replicate_and_migrate_ceph_rgw_to_cloud:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13213.php">Submit feedback</link>
        </links>
      </event>
      <event id="13208">
        <start>11:30</start>
        <duration>00:40</duration>
        <room>D.sds</room>
        <slug>sds_cosi_update</slug>
        <title>COSI : a brief update </title>
        <subtitle/>
        <track>Software Defined Storage</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;For applications in Kubernetes, CSI provides a way to consume file/block storage for their workloads. The main motivation behind the Container Object Storage Interface is to provide a similar experience for Object Store. Basic idea is to provide a generic, dynamic provisioning API to consume the object store and the app pods can access the bucket in the underlying object-store like a PVC. The major challenge for this implementation there is no standard protocol defined for object and the COSI project need to be vendor agonistic. For example, in the case of RGW, the application can request for S3 bucket and Swift bucket from the same ceph-cosi driver. Ideally, the Kubernetes resource for the bucket can be migrated to the different cloud if the drivers support it and the application can seamlessly continue with the same k8s object. It won't handle the orchestration/management of object store, rather it will be another client and provide bucket access on behalf of applications running in Kubernetes.
A similar session was given in last FOSDEM'21, but the whole project went through design changes and will share that information.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="3109">Jiffin Tony Thottan</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/ceph/ceph-cosi">ceph-cosi-driver </link>
          <link href="https://video.fosdem.org/2022/D.sds/sds_cosi_update.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.sds/sds_cosi_update.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#sds-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#sds-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#sds-sds_cosi_update:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#sds-sds_cosi_update:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13208.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.testing">
    </room>
    <room name="D.valgrind">
      <event id="13019">
        <start>14:20</start>
        <duration>00:55</duration>
        <room>D.valgrind</room>
        <slug>valgrind_freebsd</slug>
        <title>Upstreaming the FreeBSD Port</title>
        <subtitle/>
        <track>Valgrind</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Introduction - about me. Overview of the FreeBSD ports system. History of the FreeBSD port. The mechanics of how Valgrind works - the launcher, stack creation, ELF parsing and much more (but not in too much detail). A description of some of the major issues that were fixed. How clang code generation differs from GCC and the kinds of problems that it causes. Future work - outstanding bugs and other hardware platforms.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8551">Paul Floyd</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/valgrind_freebsd/attachments/slides/4944/export/events/attachments/valgrind_freebsd/slides/4944/upstreaming.key">Upstreaming Keynote Slides</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/valgrind_freebsd/attachments/slides/4945/export/events/attachments/valgrind_freebsd/slides/4945/upstreaming.pdf">Upstreaming PDF</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/valgrind_freebsd/attachments/slides/4947/export/events/attachments/valgrind_freebsd/slides/4947/upstreaming.pptx">Upstreaming PowerPoint</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/valgrind_freebsd/attachments/other/5179/export/events/attachments/valgrind_freebsd/other/5179/upstreaming.txt">Plain text transcript</attachment>
        </attachments>
        <links>
          <link href="https://github.com/paulfloyd/freebsd_valgrind">Github repo used during the upstreaming process</link>
          <link href="https://video.fosdem.org/2022/D.valgrind/valgrind_freebsd.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.valgrind/valgrind_freebsd.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-valgrind_freebsd:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-valgrind_freebsd:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13019.php">Submit feedback</link>
        </links>
      </event>
      <event id="13507">
        <start>15:20</start>
        <duration>00:25</duration>
        <room>D.valgrind</room>
        <slug>valgrind_avx512</slug>
        <title>Enable AVX-512 instructions in Valgrind</title>
        <subtitle/>
        <track>Valgrind</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;AVX-512 is a set of vector assembly instructions available on Intel Xeon Phi processors (for example, Skylake). To allow Valgrind analyze the code compiled with these instructions, they have to be explicitly enabled in Valgrind.
The presentation will briefly describe the specifics of AVX-512 instructions and describe in more detail the way it is has been prototyped in Valgrind.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8908">Tanya Volnina</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/valgrind_avx512/attachments/slides/4987/export/events/attachments/valgrind_avx512/slides/4987/AVX_512_Valgrind.pptx">AVX-512 Valgrind slides</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.valgrind/valgrind_avx512.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.valgrind/valgrind_avx512.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-valgrind_avx512:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-valgrind_avx512:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13507.php">Submit feedback</link>
        </links>
      </event>
      <event id="13224">
        <start>15:50</start>
        <duration>00:35</duration>
        <room>D.valgrind</room>
        <slug>valgrind_debuginfo</slug>
        <title>Valgrind and debuginfo</title>
        <subtitle/>
        <track>Valgrind</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;With debuginfo Valgrind can provide more useful information about issue found. But till recently it was sometimes hard to get at the debuginfo and valgrind startup time would be really slow parsing the debuginfo. With the introduction of debuginfod support getting the debuginfo is much easier, if your distribution supports it. And the parsing of debuginfo has been improved dramatically. This talk will explain how debuginfod integrates with valgrind and how the debuginfo parsing was improved.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="160">Mark Wielaard</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/valgrind_debuginfo/attachments/slides/5238/export/events/attachments/valgrind_debuginfo/slides/5238/valgrind_debuginfo_fosdem_2022.pdf">Valgrind and Debuginfo slides</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/valgrind_debuginfo/attachments/other/5239/export/events/attachments/valgrind_debuginfo/other/5239/valgrind_debuginfo_fosdem_2022.txt">Valgrind and Debuginfo transcript</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.valgrind/valgrind_debuginfo.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.valgrind/valgrind_debuginfo.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-valgrind_debuginfo:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-valgrind_debuginfo:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13224.php">Submit feedback</link>
        </links>
      </event>
      <event id="13089">
        <start>16:30</start>
        <duration>00:25</duration>
        <room>D.valgrind</room>
        <slug>valgrind_riscv</slug>
        <title>Valgrind on RISC-V</title>
        <subtitle/>
        <track>Valgrind</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Valgrind is an instrumentation framework with support for a wide range of general-purpose processor architectures. RISC-V is a modern open-standard architecture which has seen increasing adoption lately. The talk describes an effort to add support for this new architecture in Valgrind.&lt;/p&gt;

&lt;p&gt;The talk provides a brief overview of the dynamic translation in Valgrind and a short introduction to the RISC-V architecture. It then discusses implementation work to add support for RISC-V in Valgrind, and finally presents the current state of this project and outlines future plans.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="1764">Petr Pavlu</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/valgrind_riscv/attachments/slides/4869/export/events/attachments/valgrind_riscv/slides/4869/valgrind_riscv.pdf"/>
        </attachments>
        <links>
          <link href="https://github.com/petrpavlu/valgrind-riscv64/">https://github.com/petrpavlu/valgrind-riscv64/</link>
          <link href="https://video.fosdem.org/2022/D.valgrind/valgrind_riscv.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.valgrind/valgrind_riscv.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-valgrind_riscv:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-valgrind_riscv:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13089.php">Submit feedback</link>
        </links>
      </event>
      <event id="13517">
        <start>17:00</start>
        <duration>00:25</duration>
        <room>D.valgrind</room>
        <slug>valgrind_isa31</slug>
        <title>Adding Power ISA 3.1 instruction support to Valgrind</title>
        <subtitle/>
        <track>Valgrind</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The Power ISA 3.1 is an extension of the Power instruction set.  The presentation is targeted at the Valgrind developer who is interested in implementing new instruction support in Valgrind.  The presentation will discuss implementing new instuctions using Iops, clean helpers and dirty helpers in Valgrind.  A brief discussion of the functionality of the new instructions in the Power ISA 3.1 instruction set will also be discussed.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8917">Carl Love</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/valgrind_isa31/attachments/slides/4901/export/events/attachments/valgrind_isa31/slides/4901/FOSDEM22_Valgrind_ISA3.1">Adding ISA 3.1 support to Valgrind</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.valgrind/valgrind_isa31.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.valgrind/valgrind_isa31.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-valgrind_isa31:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-valgrind_isa31:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13517.php">Submit feedback</link>
        </links>
      </event>
      <event id="13223">
        <start>17:30</start>
        <duration>00:30</duration>
        <room>D.valgrind</room>
        <slug>valgrind_20</slug>
        <title>20 years of Valgrind</title>
        <subtitle>Celebration</subtitle>
        <track>Valgrind</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Valgrind is 20 years old now! On July 27, 2002 Valgrind 1.0 was released. And the initial commit to the code repository was March 22, 2002. But the real birthday of Valgrind might go back as far as the Norse Mythology. Please come and join us for a celebration of (at least) 20 years of Valgrind. A retrospective of the project and (your) ideas for the next 20 years.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="143">Julian Seward</person>
          <person id="160">Mark Wielaard</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#valgrind-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#valgrind-valgrind_20:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#valgrind-valgrind_20:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13223.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="D.virtualization">
    </room>
    <room name="D.web3">
      <event id="12951">
        <start>10:00</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>peergos</slug>
        <title>Peergos - Combining peer-to-peer connectivity, end-to-end encryption and fine grained access control to build a secure and privacy focused self-certifying web protocol</title>
        <subtitle/>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Peergos gives users total control over their data. That means: Where it is, Who can see it, Who can't see it.&lt;/p&gt;

&lt;p&gt;Used as a global file system, Peergos provides a private space where you can store, share and view your media and documents.  Individual content can be shared outside peergos via secret links and whole static sites can be hosted via a gateway.&lt;/p&gt;

&lt;p&gt;Used as an application platform, Peergos provides productivity tools like a calendar, todo/project boards and document viewer/editors.  In the near future users will be able to add their own applications using the same secure application protocol.&lt;/p&gt;

&lt;p&gt;Used as a communication platform, Peergos provides a social media feed, group chat and an email bridge.&lt;/p&gt;

&lt;p&gt;Peergos is open source and self-hostable.&lt;/p&gt;

&lt;p&gt;This talk with introduce Peergos. It will expand on the project's goals, its architecture and some of the technical details. It will provide a walkthrough of the current functionality and a sneak-peak of what the future may hold.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8800">kevin o'dwyer</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/peergos/attachments/slides/4828/export/events/attachments/peergos/slides/4828/Peergos_fosdem.pdf">Peergos Slides</attachment>
        </attachments>
        <links>
          <link href="https://peergos.org/">Peergos website</link>
          <link href="https://github.com/Peergos/Peergos">Main Github repository</link>
          <link href="https://video.fosdem.org/2022/D.web3/peergos.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/peergos.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-peergos:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-peergos:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12951.php">Submit feedback</link>
        </links>
      </event>
      <event id="13018">
        <start>10:30</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>ahau</slug>
        <title>Āhau: Māori Identity &amp; Data Sovereignty</title>
        <subtitle/>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Āhau is a FOSS project from Aotearoa New Zealand, built to meet the data needs of Māori. This talk will share insights from thinking in a less Eurocentric way about data, and how the need for data sovereignty has lead us to p2p data models, which fit really well with human-focused systems. Over the last 3 years, we've built a desktop application on secure scuttlebutt that is currently in use by hapū and iwi (tribal groups) to record family histories and create tribal registries.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Slides: https://mixmix.gitlab.io/fosdem22-ahau/#/&lt;/p&gt;

&lt;p&gt;Repo: https://www.gitlab.com/ahau/ahau&lt;/p&gt;

&lt;p&gt;Homepage: https://ahau.io/&lt;/p&gt;

&lt;p&gt;Technologies:
- secure scuttlebutt - http://dev.scuttlebutt.nz, https://scuttlebutt.nz (p2p messaging)
- tangle-js - https://gitlab.com/tangle-js (used to build ssb-crut) (CRDT-like tech)
- hyperdrive - https://github.com/hypercore-protocol/hyperdrive (hyper/ DAT for large files)
- sodium-native - https://github.com/sodium-friends/sodium-native (encryption)&lt;/p&gt;</description>
        <persons>
          <person id="8822">Mix Irving</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://ahau.io/">Āhau website</link>
          <link href="https://gitlab.com/ahau/ahau">Code repo</link>
          <link href="https://mixmix.gitlab.io/fosdem22-ahau/#/">Slides</link>
          <link href="https://video.fosdem.org/2022/D.web3/ahau.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/ahau.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-ahau:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-ahau:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13018.php">Submit feedback</link>
        </links>
      </event>
      <event id="12379">
        <start>11:00</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>wasm4d</slug>
        <title>WASM for dummies</title>
        <subtitle>A very short primer in a series of acts</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Web Assembly has been touted to be the next best thing after containerization. But what is WASM exactly? Why are people so excited about it and how is it relevant in this day and age? Has Javascript finally found a worthy replacement? "WASM for dummies" is a talk that was born out of the necessity for more content in this space. Also, it definitely contains a lot of stuff the speaker wishes somebody would have spoken about when she began her journey.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="7611">Divya Mohan</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/wasm4d/attachments/slides/5076/export/events/attachments/wasm4d/slides/5076/WASM_for_dummies.pdf">Slides for the presentation</attachment>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.web3/wasm4d.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/wasm4d.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-wasm4d:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-wasm4d:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12379.php">Submit feedback</link>
        </links>
      </event>
      <event id="12985">
        <start>11:30</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>aqua_fluence</slug>
        <title>AquaVM: Empowering distributed systems with Fluence</title>
        <subtitle/>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;At Fluence we are developing an open stack solution that allows developers to choreograph and compose distributed, peer-to-peer hosted services. An integral pillar of this stack is AquaVM, github.com/fluencelabs/aquavm, a composability medium developed in Rust. AquaVM is  the Rust-based AIR interpreter compiles to WebAssembly and allows for the seamless orchestration of peer-to-peer hosted, Wasm-based services. In this talk, we demonstrate and discuss the use of AIR and some it internals. Moreover, we present the project evolution from its beginning in the context of Rust and Wasm.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8010">Mike Voronov</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://github.com/fluencelabs/aquavm">source code of the interpreter</link>
          <link href="https://github.com/fluencelabs/aquavm">source code of the compiler</link>
          <link href="https://video.fosdem.org/2022/D.web3/aqua_fluence.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/aqua_fluence.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-aqua_fluence:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-aqua_fluence:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12985.php">Submit feedback</link>
        </links>
      </event>
      <event id="12755">
        <start>12:00</start>
        <duration>00:25</duration>
        <room>D.web3</room>
        <slug>humanity</slug>
        <title>xHumanity and Web3</title>
        <subtitle>xHumanity - reputation, reduction of fake news, and privacy</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;xHumanity is a project that started from the idea of identifying the future of digital identities. This concern resonated all over the globe. We thus gathered an international team. Our concern is based on the increased impact social media has on our lives, but also the context of the amplification of disinformation actions.
We aim to run a foundation focused on providing our audience with a digital platform based on three pillars, which are reputation, reduction of fake news, and privacy. We aim to empower customers by providing them with a better way of living.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Reputation
Blockchain technology could help all parties involved in any types of transactions. But not alone. To construct a secure and trustable transaction we need to start with valid data. This data in our case will be provided through reputation protocol. Everyone's reputation passport will reduce friction between parties.&lt;/p&gt;

&lt;p&gt;Privacy
xHumanity enables decentralized identities: self-managed identities hold that individuals should have control over their own personal data and determine how it is shared with others. End-to-end encrypted communication: the difference between xHumanity and the current messaging app landscape is that xHumanity does not require users’ phone numbers to provide access to its services and features.&lt;/p&gt;

&lt;p&gt;Reduction of fake news
One of our main goals is to reduce and eliminate fake news from the internet space through a few principles from the gaming theory. Peoples’ involvement in the game is essential, as they are the main actors in creating new social rules.&lt;/p&gt;</description>
        <persons>
          <person id="8724">Cosmin Vranceanu</person>
        </persons>
        <attachments>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/humanity/attachments/paper/4789/export/events/attachments/humanity/paper/4789/xHumanity_presentation.pdf"/>
          <attachment type="paper" href="https://fosdem.org/2022/schedule/event/humanity/attachments/paper/4790/export/events/attachments/humanity/paper/4790/WORKING_PAPER.pdf"/>
        </attachments>
        <links>
          <link href="https://xhumanity.org">https://xhumanity.org</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-humanity:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-humanity:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12755.php">Submit feedback</link>
        </links>
      </event>
      <event id="13062">
        <start>12:30</start>
        <duration>00:35</duration>
        <room>D.web3</room>
        <slug>fluence</slug>
        <title>Commoditizing P2P development </title>
        <subtitle>With Aqua language and Fluence</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;yeah&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Peer-to-peer protocols seem nice and promising, but are actually hard to design and implement properly. Fluence addresses this problem with Aqua, the new-gen distributed language designed for programming p2p networks that can help in a variety of multi-agent scenarios, from notifications pushing to consensus algorithms. We will speak about the infrastructure and tooling we have, and how to make a simple p2p protocol with a few lines of code.&lt;/p&gt;</description>
        <persons>
          <person id="8008">Dmitry Kurinskiy</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.web3/fluence.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/fluence.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-fluence:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-fluence:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13062.php">Submit feedback</link>
        </links>
      </event>
      <event id="13023">
        <start>13:05</start>
        <duration>00:25</duration>
        <room>D.web3</room>
        <slug>earthstar</slug>
        <title>Earthstar</title>
        <subtitle>The merits of being a bicycle when everything else is a hyperloop.</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Earthstar is a specification and Javascript library for building online tools you can truly call your own.&lt;/p&gt;

&lt;p&gt;By being light, simple, and cheap, bicycles confer huge amounts agency to their users. 'Web3' doesn't have a lot of bicycles.&lt;/p&gt;

&lt;p&gt;Instead it's got a lot of hyperloops: slick, complex, expensive, and with very little application.&lt;/p&gt;

&lt;p&gt;What can we learn from bicycles when we design new tools for the web? Earthstar occupies a relatively unexplored band of the contemporary web3 spectrum: ephemerality, lightness, offline-ness, malleability, and serving groups of people who already know each other.&lt;/p&gt;

&lt;p&gt;This project was funded through the NGI Assure Fund, a fund established by NLnet with financial support from the European Commission's Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 957073. Applications are still open, you can apply today.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8826">Sam Gwilym</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://earthstar-project.org">https://earthstar-project.org</link>
          <link href="https://video.fosdem.org/2022/D.web3/earthstar.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/earthstar.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-earthstar:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-earthstar:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13023.php">Submit feedback</link>
        </links>
      </event>
      <event id="13074">
        <start>13:30</start>
        <duration>00:25</duration>
        <room>D.web3</room>
        <slug>ipfs</slug>
        <title>Edges Are Infrastructure: IPFS Everywhere for a More Resilient Future</title>
        <subtitle>Adventures in IPFS support across Bluetooth, mobile devices, XR and more!</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This is an overview of IPFS integrations across various platforms, devices and network transports - including browser integrations, video demos of IPFS apps on a native web3-based OS on Pixel 3, IPFS content loaded into various XR devices like Oculus Quest and HTC Vive Flow, and mobile-to-mobile IPFS apps via Bluetooth LE.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="6619">Dietrich Ayala</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.web3/ipfs.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/ipfs.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-ipfs:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-ipfs:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13074.php">Submit feedback</link>
        </links>
      </event>
      <event id="13036">
        <start>14:00</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>quark</slug>
        <title>The Quark Browser</title>
        <subtitle>Uncovering the paths through the web</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The internet is an entire universe. Countless links emerge and die off every minute. Each of us have our own habits and patterns across it. Our browsing is increasingly complex, so it makes no sense why we're still using technology based on filing cabinets -- tabs, files, folders.  Quark is the DWeb browser x social platform that shows you paths across the internet. Imagine if you could bump into someone else looking at similar content/search results, see where they've been, and tag along to discover content together.&lt;/p&gt;

&lt;p&gt;In this presentation, I'll share use cases for The Quark Browser, as well as how this tool can address the existential crises of the siloed Web 2.0 internet by making the internet more serendipitous, visual, and communal.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The internet is bustling with activity, but today we can only meet and interact with others at specific “parties.”  These online "parties" are free to enter, serve free drinks, and play good music. But in exchange, the hosts of these parties sell your information. The Quark Browser asks the question: What if you can meet and interact with like-minded people &lt;em&gt;anywhere&lt;/em&gt; on the internet?&lt;/p&gt;

&lt;p&gt;The Quark Browser delivers the decentralized p2p vision of DWeb and makes it accessible to the public, no matter their level of technical understanding. Unlike most Web3 companies which innovate with a financial, privacy, or technical focus, Quark does so from a unique interaction design approach. Our vision is product-focused – to build a dynamic, living, and persistent “playground” that nurtures meaningful social connections. With a business model, technology stack, and experience design that learns from the mistakes of Web 2.0, Quark aims to bring variety and serendipity to the content we discover, connect ideas via relational maps, and help us build peer-to-peer communities of likeminded people all in line with the browsing experience.&lt;/p&gt;

&lt;p&gt;We are a two-person team of multi-time founders – Joy, the Founder/CEO, and Sam, the founding Product Designer. This is Joy’s fourth startup, and Sam’s second. Sam’s first startup at age 14 was featured in the Colombian equivalent of “Financial Times” and was invited to Shark Tank. He is a Gen-Z self-learner which makes him familiar with the modern pain points in complex browsing. Joy completed a master's thesis on the very problem that Quark solves. She has worked for companies such as Apple, IDEO, and Fiat Chrysler Automobiles. Her undergraduate degree is in mechanical engineering and human-computer interaction from Georgia Tech, and her master's in interdisciplinary design engineering from the Royal College of Art and Imperial College London. We are looking for a CTO/Tech Lead to help lead the technological development.&lt;/p&gt;</description>
        <persons>
          <person id="8818">Joy Q Zhang</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/quark/attachments/slides/4809/export/events/attachments/quark/slides/4809/Quark_dweb_Dec2021_pitch">Slides</attachment>
        </attachments>
        <links>
          <link href="https://www.youtube.com/watch?v=3MfMfVA-6M8">Use case for The Quark Browser for sustainability research</link>
          <link href="https://video.fosdem.org/2022/D.web3/quark.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/quark.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-quark:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-quark:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13036.php">Submit feedback</link>
        </links>
      </event>
      <event id="13046">
        <start>14:30</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>swarm</slug>
        <title>Swarm, what's in it for me?</title>
        <subtitle>Developers edition</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;The option to choose a decentralized storage network in the stack of your application is far-reaching but perhaps not well understood. In this presentation, I intent to give guidance and understanding by answering the question of when it makes sense to use Swarm in your stack.
I start with a brief introduction to Swarm after which I highlight 3 (not so) typical applications which already run on top of Swarm. I end by introducing the paradigm shift that we see happening when developers start to explore Swarm and truly get to know what it means for them--the avenues that Swarm opens and the new patterns that can be explored.&lt;/p&gt;

&lt;p&gt;I hope to see you at my presentation and be sure to take all your questions to the live Q&amp;amp;A!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8831">R H</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://ethswarm.org">Ethereum Swarm</link>
          <link href="https://video.fosdem.org/2022/D.web3/swarm.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/swarm.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-swarm:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-swarm:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13046.php">Submit feedback</link>
        </links>
      </event>
      <event id="12437">
        <start>15:00</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>libp2p</slug>
        <title>State of libp2p</title>
        <subtitle>Status quo and future roadmap of the peer-to-peer networking library libp2p.</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;&lt;a href="https://libp2p.io"&gt;libp2p&lt;/a&gt; is a universal, cross-platform, multi-language, modular peer-to-peer networking library powering multiple large-scale networks, for example IPFS, Ethereum 2, Filecoin or Polkadot.&lt;/p&gt;

&lt;p&gt;We will discuss the current state of the project, eyeball the various language implementations, take a look at the many live networks running on top of libp2p today and finally cover the project roadmap for the years to come.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="4670">Max Leonard Inden</person>
        </persons>
        <attachments>
          <attachment type="audio" href="https://fosdem.org/2022/schedule/event/libp2p/attachments/audio/4917/export/events/attachments/libp2p/audio/4917/slides.pdf">slides.pdf</attachment>
        </attachments>
        <links>
          <link href="https://libp2p.io/">Project Homepage</link>
          <link href="https://github.com/libp2p/specs/">Specifications</link>
          <link href="https://video.fosdem.org/2022/D.web3/libp2p.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/libp2p.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-libp2p:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-libp2p:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12437.php">Submit feedback</link>
        </links>
      </event>
      <event id="13028">
        <start>15:30</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>hyperhyper</slug>
        <title>Hyper Hyper Space: In-browser p2p applications</title>
        <subtitle>A quick tour on using the browser as a p2p node</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A quick tour on using Hyper Hyper Space datatypes to create fully distributed structures for collaborative applications.&lt;/p&gt;

&lt;p&gt;We'll start with a simple last-writer-wins JSON object, to complex structures like a moderated chat room and a simple ledger.&lt;/p&gt;

&lt;p&gt;Then we'll open them inside a web browser, using plain javascript, and show how the web can be used as a platform for truly peer-to-peer applications.&lt;/p&gt;</abstract>
        <description>&lt;p&gt;The Hyper Hyper Space library offers two things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;A data modeling language, that presents building blocks to create and compose CRDT-like operational datatypes, that are backed by a Merkle-DAG.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A synchronization protocol for Hyper Hyper Space datatypes, with an implementation that works both in-browser (through WebRTC &amp;amp; IndexedDB) and NodeJS.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;In this talk we'll focus on how to use the modeling language, and see in practice how to use the created objects inside a web browser using JavaScript.&lt;/p&gt;</description>
        <persons>
          <person id="8819">Santiago Bazerque</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://www.hyperhyperspace.org">Project Homepage</link>
          <link href="https://hyperhyper.space">Demo</link>
          <link href="https://github.com/hyperhyperspace/hyperhyperspace-core">Core Library</link>
          <link href="https://video.fosdem.org/2022/D.web3/hyperhyper.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/hyperhyper.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-hyperhyper:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-hyperhyper:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13028.php">Submit feedback</link>
        </links>
      </event>
      <event id="13196">
        <start>16:00</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>where</slug>
        <title>Collabortive group self-awareness with Where, a Holochain app</title>
        <subtitle>A demo of how distributed ledger tech can up-regulate group capacity.</subtitle>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;A playground for group self-awareness (awhereness?) on holochain&lt;/p&gt;</abstract>
        <description>&lt;p&gt;Groups, especially remote collaborative groups, often lack contextual information about collaborators that makes working together harder. Co-locating oneself across a number of spaces in the context of a group (or groups) provides an important avenue for improving both sense-making and working together. Where provides a generalized grammar for creating shared maps for groups to see the emergent "whereness" of each other, as well as the grammatics to self-evolve these spaces and how to represent "location" in them.&lt;/p&gt;

&lt;p&gt;Read more in Eric's blog post about Where (https://eric.harris-braun.com/blog/2021/09/16/id-377) and explore the details in Where's github repo (https://github.com/lightningrodlabs/where)&lt;/p&gt;</description>
        <persons>
          <person id="8882">Eric Harris-Braun</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.web3/where.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/where.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-where:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-where:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13196.php">Submit feedback</link>
        </links>
      </event>
      <event id="13054">
        <start>16:30</start>
        <duration>00:25</duration>
        <room>D.web3</room>
        <slug>didkit</slug>
        <title>Verifiable Credentials and Decentralized Identifiers with DIDKit</title>
        <subtitle/>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;We present DIDKit, a toolkit for Verifiable Credentials and Decentralized Identifiers, implemented in Rust. This includes an introduction to Verifiable Credentials ("VCs"), a W3C Recommendation; to Decentralized Identifiers ("DIDs"), a Proposed W3C Recommendation; and to the signing formats used with these: JSON Web Signatures (JWS) and Linked Data Proofs. Charles Lehner will demo using DIDKit to issue, present and verify verifiable credentials using DIDs based on cryptographic keypairs. Charles is joined by Juan Caballero (@bumblefudge) for the Q&amp;amp;A.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8830">Charles Lehner</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/didkit/attachments/slides/4896/export/events/attachments/didkit/slides/4896/2022_fosdem_didkit.pdf">Slides (PDF export)</attachment>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/didkit/attachments/slides/4897/export/events/attachments/didkit/slides/4897/2022_fosdem_didkit.zip">Slides (zip archive)</attachment>
          <attachment type="other" href="https://fosdem.org/2022/schedule/event/didkit/attachments/other/5265/export/events/attachments/didkit/other/5265/2022_fosdem_web3_didkit_vc_vp.json">Verifiable Presentation with embedded Verifiable Credential, generated during the demo</attachment>
        </attachments>
        <links>
          <link href="https://github.com/spruceid/ssi/">ssi: core library used in DIDKit</link>
          <link href="https://github.com/spruceid/didkit/">DIDKit: Toolkit for Decentralized Identifiers and Verifiable Credentials</link>
          <link href="https://spruceid.dev/docs/didkit/">DIDKit - dev portal</link>
          <link href="https://demo.didkit.dev/2022/01/fosdem/">Slides (web page)</link>
          <link href="https://video.fosdem.org/2022/D.web3/didkit.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/didkit.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-didkit:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-didkit:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13054.php">Submit feedback</link>
        </links>
      </event>
      <event id="12737">
        <start>17:00</start>
        <duration>00:25</duration>
        <room>D.web3</room>
        <slug>solid</slug>
        <title>Building Interoperable Applications with Solid in 2022</title>
        <subtitle/>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;Each time a new software project is created, a new data silo is also made. Solid, the decentralized web network pioneered by Tim Berners-Lee, aim to combat the expanding number of data silos by standardizing a global decentralized knowledge graph. Though, this is easier said than done. Ensuring all applications using the knowledge graph are interoperable is a massive undertaking.&lt;/p&gt;

&lt;p&gt;This talk will detail the ongoing efforts to make it easier for application developers to build interoperable applications, the yet to be implemented future visions for interoperability, and how these methods can be used in other decentralized web projects outside of Solid.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8711">Jackson Morgan</person>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://video.fosdem.org/2022/D.web3/solid.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/solid.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-solid:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-solid:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/12737.php">Submit feedback</link>
        </links>
      </event>
      <event id="13051">
        <start>17:30</start>
        <duration>00:30</duration>
        <room>D.web3</room>
        <slug>onecommons</slug>
        <title>How to build a free and open cloud</title>
        <subtitle/>
        <track>Web3 Infrastructure</track>
        <type>devroom</type>
        <language/>
        <abstract>&lt;p&gt;This talk will explore how we can bring open source collaboration to building and running cloud services. We present our vision of "Open Cloud Services" that provide the same openness and freedom to users and developers as open-source software. But running a cloud service requires resources so how can that be funded? An ideal solution would be simple, equitable and fair -- and not compromise the ethos of open source. We'll discuss our attempt at solving this puzzle, a funding mechanism we call cloud funding.
Next, we'll introduce Unfurl, our DevOps tool for building reproducible, cloud-provider independent open cloud services and then look to future Web3 and decentralization technologies that make this possible -- specifically how blockchain-based decentralized data and remote attestation, transparent and reproducible open cloud services, and next-generation secure-computing cloud infrastructure all combine to provide the building blocks of a free and open cloud.&lt;/p&gt;</abstract>
        <description></description>
        <persons>
          <person id="8813">Adam Souzis</person>
        </persons>
        <attachments>
          <attachment type="slides" href="https://fosdem.org/2022/schedule/event/onecommons/attachments/slides/5200/export/events/attachments/onecommons/slides/5200/OneCommons_FOSDEM_22_WEB3_Track.pdf">Slides for Talk</attachment>
        </attachments>
        <links>
          <link href="https://onecommons.org">https://onecommons.org</link>
          <link href="https://video.fosdem.org/2022/D.web3/onecommons.webm">Video recording(WebM/VP9)</link>
          <link href="https://video.fosdem.org/2022/D.web3/onecommons.mp4">Video recording(mp4)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-devroom:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#web3-devroom:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://chat.fosdem.org/#/room/#web3-onecommons:fosdem.org">Hallway chat room (web)</link>
          <link href="https://matrix.to/#/#web3-onecommons:fosdem.org?web-instance[element.io]=chat.fosdem.org">Hallway chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13051.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.box86">
    </room>
    <room name="S.checkmk">
    </room>
    <room name="S.civicrm">
    </room>
    <room name="S.opensuse">
    </room>
    <room name="S.debian">
    </room>
    <room name="S.eclipse">
    </room>
    <room name="S.fedora">
    </room>
    <room name="S.foreman">
    </room>
    <room name="S.fossasia">
    </room>
    <room name="S.fsfe">
    </room>
    <room name="S.freebsd">
    </room>
    <room name="S.gnome">
    </room>
    <room name="S.gsoc">
    </room>
    <room name="S.haiku">
    </room>
    <room name="S.illumos">
    </room>
    <room name="S.kde">
      <event id="13554">
        <start>10:00</start>
        <duration>00:15</duration>
        <room>S.kde</room>
        <slug>kde_news</slug>
        <title>KDE News</title>
        <subtitle>Adam Szopa</subtitle>
        <track>KDE Community stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#kde-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kde-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13554.php">Submit feedback</link>
        </links>
      </event>
      <event id="13555">
        <start>10:30</start>
        <duration>00:30</duration>
        <room>S.kde</room>
        <slug>kde_plasma</slug>
        <title>Plasma 5.24 tour</title>
        <subtitle>Adam Szopa, Aniqa Khokhar and Paul Brown</subtitle>
        <track>KDE Community stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#kde-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kde-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13555.php">Submit feedback</link>
        </links>
      </event>
      <event id="13556">
        <start>12:00</start>
        <duration>01:00</duration>
        <room>S.kde</room>
        <slug>kde_tokodon</slug>
        <title>Live coding session with Tokodon</title>
        <subtitle>Carl Schwan</subtitle>
        <track>KDE Community stand</track>
        <type>standtrack</type>
        <language/>
        <abstract></abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#kde-stand:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#kde-stand:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13556.php">Submit feedback</link>
        </links>
      </event>
    </room>
    <room name="S.kiwi">
    </room>
    <room name="S.libreoffice">
    </room>
    <room name="S.libresoc">
    </room>
    <room name="S.mariadb">
    </room>
    <room name="S.matrix">
    </room>
    <room name="S.mautic">
    </room>
    <room name="S.nextcloud">
    </room>
    <room name="S.ntop">
    </room>
    <room name="S.oniro">
    </room>
    <room name="S.onlyoffice">
    </room>
    <room name="S.openmandriva">
    </room>
    <room name="S.opentap">
    </room>
    <room name="S.openuk">
    </room>
    <room name="S.openwifi">
    </room>
    <room name="S.ow2">
    </room>
    <room name="S.pharo">
    </room>
    <room name="S.postgresql">
    </room>
    <room name="S.pulp">
    </room>
    <room name="S.reactos">
    </room>
    <room name="S.refpersys">
    </room>
    <room name="S.schulfrei">
    </room>
    <room name="S.apache">
    </room>
    <room name="S.ubuntu">
    </room>
    <room name="S.xcpng">
    </room>
    <room name="S.xwiki">
    </room>
    <room name="I.infodesk">
      <event id="13009">
        <start>09:00</start>
        <duration>09:00</duration>
        <room>I.infodesk</room>
        <slug>infodesk_sunday</slug>
        <title>The Virtual FOSDEM Infodesk (Sunday)</title>
        <subtitle/>
        <track>Infodesk</track>
        <type>infodesk</type>
        <language/>
        <abstract>&lt;p&gt;Need any assistance during the event?  Join us in here!&lt;/p&gt;</abstract>
        <description></description>
        <persons>
        </persons>
        <attachments>
        </attachments>
        <links>
          <link href="https://chat.fosdem.org/#/room/#infodesk:fosdem.org">Chat room (web)</link>
          <link href="https://matrix.to/#/#infodesk:fosdem.org?web-instance[element.io]=chat.fosdem.org">Chat room (app)</link>
          <link href="https://submission.fosdem.org/feedback/13009.php">Submit feedback</link>
        </links>
      </event>
    </room>
  </day>
</schedule>

