<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;">
<h1 style="font-size: 1.4em;">FOSDEM 2023 In Person – Sovereign Cloud DevRoom Call for Participation!</h1>
<p dir="auto">The twenty-third edition of FOSDEM takes place Saturday 4th and Sunday 5th<br>
February 2023 in Brussels, Belgium.<br>
For the first time there will be a DevRoom that focuses on the subject of Sovereign Cloud<br>
and its practical aspect for digital sovereignty.</p>
<h2 style="font-size: 1.2em;">Key dates tl;dr:</h2>
<ul>
<li>Conference dates 4-5 February, 2023 In person</li>
<li>Sovereign Cloud DevRoom date: Saturday 4th February</li>
<li>Submission deadline: Friday December 9th, 2022 - 23:59 UTC.</li>
<li>Announcement of selected talks: Thursday 15th December</li>
<li>You must be available in person to present your talk</li>
</ul>
<h2 style="font-size: 1.2em;">About the Sovereign Cloud DevRoom</h2>
<h3 style="font-size: 1.1em;">Overview</h3>
<p dir="auto">The Sovereign Cloud DevRoom is for discussing topics and issues of user privacy and<br>
sovereignty and the intersection with the needs of infrastructure providers in the cloud<br>
computing era.</p>
<p dir="auto">A few topic examples to illustrate (a longer list is below):</p>
<ul>
<li>Can all operations be open, or may there be a need for a two+ tier openess (country specific laws or company secrets)?</li>
<li>How can privacy relevant data be anonymized instead of being deleted, without losing the useful information?</li>
<li>Open Operations is more than just sharing runbooks, how is knowledge shared and fostered best across organizations?</li>
<li>Navigating our personal data lakes -- we're going to need better tools that are easier to use by more people for managing and curating encrypted data lakes</li>
<li>The role of machine learning in conducting data science on anonymized information</li>
<li>Countering the risks of integrated platforms</li>
</ul>
<p dir="auto">These are just a few example suggestions, we welcome proposals on any aspects around these topic.</p>
<p dir="auto">More topic ideas and details on how to submit proposals is below.</p>
<h3 style="font-size: 1.1em;">Discussing the Sovereign Cloud</h3>
<p dir="auto">The recent EU focus on digital sovereignity has brought fresh attention and innovation to a problem<br>
area many of us have been interested in and working on for a long time. This DevRoom focuses on<br>
a practical aspect of digital sovereignty: how it affects user-oriented and<br>
potentially privacy-containing infrastructure in the cloud computing era.</p>
<p dir="auto">This aspect is the <em>sovereign cloud</em>, the intersection of digital sovereignty and a modern cloud-centric<br>
way to create and sustain infrastructure, operations, and development to address the needs of<br>
users (which may be other cloud services or actual, real people.)</p>
<p dir="auto">With the rise of the Confidential Computing Consortium (<a href="https://confidentialcomputing.io/" style="color: #3983C4;">https://confidentialcomputing.io/</a>), some<br>
people feel we are beginning to achieve "sovereign enough" where it comes to the balance of the<br>
needs of the individual and the needs of tech companies et al. But there are just as many other voices<br>
calling attention to potential problems and unfulfillable needs of staying on that path.</p>
<p dir="auto">Looking at the entire landscape of the problem, it's clear that Confidential Computing also aligns with<br>
usage on a sovereign cloud. It is a tool to ensure the least amount of provider trust, and it is still a good<br>
idea until we've moved new processor architectures into the mainstream that are less impacted by<br>
predictive execution vulnerabilities. So while it is not perfect, making it harder for an attacker is always<br>
a good idea where feasible.</p>
<p dir="auto">In looking for other paths to fill more needs, we naturally come to the intersection of Free/Open where<br>
interests from different backgrounds pursuing different goals suddenly find themselves working together<br>
in a common direction. Two of those groups are part of the organizing committee for this devroom:</p>
<p dir="auto">As a way of addressing the holistic needs and supporting a truly balanced digital sovereignty, organizations<br>
such as the overeign Cloud Stack (<a href="https://scs.community/" style="color: #3983C4;">https://scs.community/</a>) have come together to provide a complete<br>
technology solution, standards as well as reference implementations, that can be proven and recognized<br>
by everyone as a truly sovereign cloud.</p>
<p dir="auto">In this area where the requirements of a sovereign cloud are being met is another intersection from the<br>
ecosytem of Free and Open Source software development. The idea of Open Operations is essential to<br>
projects such as Operate First that provide a developer-friendly post-CI/CD platform for running, testing,<br>
and proving Open Source services.</p>
<p dir="auto">Longer list of topic ideas - this is not an exclusive list, feel free to submit further ideas:</p>
<ul>
<li>Can all operations be open, or may there be a need for a two+ tier openess (country specific laws or company secrets)?</li>
<li>How can privacy relevant data be anonymized instead of being deleted, without losing the useful information?</li>
<li>Discussion: How open can software be called, if it relies on closed operations and closed infrastructure?</li>
<li>Do we need to refine the definition of upstream in the idea of Open Operations?</li>
<li>Is hybrid accelerating Open Operations or can it be a slow-downer/ separator? Or the solution to possible privacy issues?</li>
<li>Interoperability, transparency, and independence are the go to goals, what can be accepted on our way until we are there?</li>
<li>Open Operations is more than just sharing runbooks, how is knowledge shared and fostered best across organizations?</li>
<li>Share experiences and stories on creating environments of psychological safety so that failures indeed make us experts</li>
<li>Building communities of practice across organizations</li>
<li>Navigating our personal data lakes -- we're going to need better tools that are easier to use by more people for managing and curating encrypted data lakes</li>
<li>The role of machine learning in conducting data science on anonymized information</li>
<li>Countering the risks of integrated platforms</li>
</ul>
<p dir="auto">Again, these are just suggestions. We welcome proposals on any aspects around these topic.</p>
<p dir="auto">Format and lengths of submissions:</p>
<pre style="margin-left: 15px; margin-right: 15px; padding: 5px; background-color: #F7F7F7; border-radius: 5px 5px 5px 5px; overflow-x: auto; max-width: 90vw;"><code style="margin: 0 0; border-radius: 3px; background-color: #F7F7F7; padding: 0px;">- Long (40 minutes, including Q&A)
- Short (20 minutes, including Q&A)
- Lightning (5 minutes, no Q&A)
</code></pre>
<p dir="auto">Aside from Presentation also Meetings/Discussions are welcome for topics where a BoF-style (Birds of Feather) session<br>
is appropriate.</p>
<p dir="auto">HOW TO SUBMIT A TALK</p>
<ul>
<li>Head to the FOSDEM 2023 Pentabarf</li>
</ul>
<p dir="auto"><a href="https://penta.fosdem.org/submission/FOSDEM23" style="color: #3983C4;">https://penta.fosdem.org/submission/FOSDEM23</a> website.</p>
<ul>
<li>If you already have a Pentabarf account, please don’t create a new one.</li>
<li>If you forgot your password, reset it.</li>
<li>Otherwise, follow the instructions to create an account.</li>
<li>Once logged in, select “New Event” and click on “Show All” in the top right corner to display the full form.</li>
</ul>
<p dir="auto">Your submission must include the following information:</p>
<ul>
<li>
<p dir="auto">First and last name / Nickname (optional)/ Image</p>
</li>
<li>
<p dir="auto">Email address</p>
</li>
<li>
<p dir="auto">Mobile phone number (this is a very hard requirement as there will be no other reliable form of emergency communication on the day)</p>
</li>
<li>
<p dir="auto">Title and subtitle of your talk (please be descriptive, as titles will be listed with ~500 from other projects)</p>
</li>
<li>
<p dir="auto">Track: Select “Sovereign Cloud DevRoom” as the track</p>
</li>
<li>
<p dir="auto">Event type:</p>
<ul>
<li>Lightning Talk OR</li>
<li>Meeting or Discussion OR</li>
<li>Presentation</li>
</ul>
</li>
<li>
<p dir="auto">Persons: Add yourself as the speaker with your bio</p>
</li>
<li>
<p dir="auto">Description: Abstract (required)/ Full Description (optional)</p>
</li>
<li>
<p dir="auto">Links to related websites / blogs etc.</p>
</li>
<li>
<p dir="auto">Beyond giving us the above, let us know if there’s anything else you’d like to share as part of your submission – Twitter handle, GitHub activity</p>
</li>
</ul>
<p dir="auto">history – whatever works for you. We especially welcome videos of you speaking elsewhere, or even just a list of talks you have done previously.<br>
First time speakers are, of course, welcome!</p>
<ul>
<li>For issues with Pentabarf, please contact</li>
</ul>
<p dir="auto"><a href="mailto:cloud-devroom-manager@fosdem.org" style="color: #3983C4;">cloud-devroom-manager@fosdem.org</a>. Feel free to send a notification of<br>
your submission to that email.</p>
<p dir="auto">If you need to get in touch with the organisers or program committee of the<br>
Sovereign Cloud DevRoom, email us at <a href="mailto:cloud-devroom-manager@fosdem.org" style="color: #3983C4;">cloud-devroom-manager@fosdem.org</a></p>
<p dir="auto">FOSDEM website <a href="https://fosdem.org/2023/" style="color: #3983C4;">https://fosdem.org/2023/</a> / FOSDEM code of conduct<br>
<a href="https://fosdem.org/2023/practical/conduct/" style="color: #3983C4;">https://fosdem.org/2023/practical/conduct/</a></p>
</div>
</div>
</body>
</html>