<?xml version='1.0' encoding='utf-8' ?>
<!-- Made with love by pretalx v2026.3.0.dev0. -->
<schedule>
    <generator name="pretalx" system="program.foss-backstage.de" version="2026.3.0.dev0" />
    <version>1.9</version>
    <conference>
        <title>FOSS Backstage 2024</title>
        <acronym>fossback24</acronym>
        <start>2024-03-04</start>
        <end>2024-03-05</end>
        <days>2</days>
        <timeslot_duration>00:05</timeslot_duration>
        <base_url>https://program.foss-backstage.de</base_url>
        <logo>https://program.foss-backstage.de/media/fossback24/img/23_FOSSBack_Logo_standard_colour_j7L1cem.png</logo>
        <time_zone_name>Europe/Berlin</time_zone_name>
        
        
        <track name="Governance &amp; Community" slug="4025-governance-community"  color="#fcce57" />
        
        <track name="Sustainability &amp; Funding" slug="4026-sustainability-funding"  color="#6bd9cc" />
        
        <track name="Legal &amp; Compliance" slug="4027-legal-compliance"  color="#333333" />
        
        <track name="Diversity &amp; Inclusion" slug="4028-diversity-inclusion"  color="#052da5" />
        
        <track name="Growing Open Source" slug="4029-growing-open-source"  color="#ffd2d7" />
        
        <track name="Security" slug="4030-security"  color="#98d0e7" />
        
    </conference>
    <day index='1' date='2024-03-04' start='2024-03-04T04:00:00+01:00' end='2024-03-05T03:59:00+01:00'>
        <room name='Stage Auditorium' guid='f6a7acb1-4d2c-5dd6-bb0d-f245d3aa58ee'>
            <event guid='0c905658-dbc3-5aa8-a444-30f0a3985f46' id='43273' code='3ERGX7'>
                <room>Stage Auditorium</room>
                <title>When business models are conflicting with security</title>
                <subtitle></subtitle>
                <type>Keynote</type>
                <date>2024-03-04T10:00:00+01:00</date>
                <start>10:00</start>
                <duration>00:45</duration>
                <abstract>When growth is mandatory, open-source goes freemium, and Palantir is a success story, it might be time to start fighting our business models</abstract>
                <slug>fossback24-43273-when-business-models-are-conflicting-with-security</slug>
                <track>Security</track>
                <logo>/media/fossback24/submissions/3ERGX7/Share_v2-2_Security_1_70TEx6K.png</logo>
                <persons>
                    <person id='46469'>Melanie Rieback</person>
                </persons>
                <language>en</language>
                <description>&#8220;In cybersecurity, sharing is caring. Sharing threat intelligence, tools, and knowledge is the best way to collectively improve our security posture. But our business models conflict with this sharing. Through the sands of time, countless non-commercial and open-source initiatives either went &#8220;freemium&#8221; or were absorbed into multinationals and disappeared completely.

It all goes wrong when open-source projects get involved with Venture Capital. It makes some hackers wealthy, but where does this leave the hacker community and the world? Are acquisitions and IPOs collectively achieving our goals of making the world more cybersecure? Or is this all one large distraction? We need to conduct an uncomfortable but necessary discussion within FOSS communities about this.&#8221;</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/3ERGX7/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/3ERGX7/feedback/</feedback_url>
            </event>
            <event guid='dfaa8b6f-03ae-5889-af31-12c4bcefd8ce' id='38283' code='Y9MZD8'>
                <room>Stage Auditorium</room>
                <title>Looking at Open Source Security from the Community Angle</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>00:30</duration>
                <abstract>This talk aims to shed light on different ways OSPOs and security teams can work together, not only from a project risk assessment perspective but also from a more human, relational network of people sustaining those projects.</abstract>
                <slug>fossback24-38283-looking-at-open-source-security-from-the-community-angle</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/Y9MZD8/Share_v2-1_Governance_3_iNorHF5.png</logo>
                <persons>
                    <person id='43177'>Ana Jimenez Santamaria</person>
                </persons>
                <language>en</language>
                <description>The people behind OSPOs can bring strong potential and opportunities to strengthen the security of open source projects. The recent results from the new State of OSPO report find that 96% of organizations with an OSPO or similar open source initiatives use these entities to provide advice on security decisions and risk mitigation strategies. 

People working at OSPOs usually act as the linchpin and point of contact where maintainers of open source projects can reach out and better identify project health issues. Questions arise, such as: How is the working environment of the community that sustains the open source projects critical to my organization? Are maintainers having issues dealing with all the feature requests and problems? Do they need help with infrastructure, funding, etc.? 

This talk aims to shed light on different ways OSPOs and security teams can work together, not only from a project risk assessment perspective but also from a more human, relational network of people sustaining those projects.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/Y9MZD8/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/Y9MZD8/feedback/</feedback_url>
            </event>
            <event guid='bce154e3-2767-50a4-8e91-846f75c827c1' id='39150' code='FFMBDN'>
                <room>Stage Auditorium</room>
                <title>Changing the governance model of an established project</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T11:35:00+01:00</date>
                <start>11:35</start>
                <duration>00:30</duration>
                <abstract>Lessons learned from changing the governance model of an established open source project after ownership of the project was passed from a company to the community.</abstract>
                <slug>fossback24-39150-changing-the-governance-model-of-an-established-project</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/FFMBDN/Share_v2-1_Governance_10_E5AxqGl.png</logo>
                <persons>
                    <person id='43080'>Ruth Cheesley</person>
                </persons>
                <language>en</language>
                <description>Picture the scene, you&apos;re leading a popular open source project used by tens of thousands of businesses, and suddenly your founding company and primary funder steps back from the project.  What will happen to the project? How do we move forward given that all of our governance model and decision making was tied up with the founding company?

This session will explore some of the governance challenges that faced Mautic when this situation arose back in April 2023, and in particular we&apos;ll dive into more detail on how we developed an entirely new governance model and decision making process.

We will touch on issues including how we actually went about creating a new community-driven governance model in a collaborative way, allowing members of the community to have a say, through to the practicalities of how we implemented our new Community Portal (using open source software) for democratic decision making.

This session is for you if you&apos;re curious about all things governance and open source, if you&apos;d like to know more about collaborative decision making and how this can be facilitated with open source software.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/FFMBDN/resources/Ruth_Cheesley_-_FOSS_Backstage_24_-_Changing_Gov_V8LvPez.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/FFMBDN/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/FFMBDN/feedback/</feedback_url>
            </event>
            <event guid='a633f577-282c-5b78-9cc5-01ef8c923ba9' id='38644' code='NEE9SL'>
                <room>Stage Auditorium</room>
                <title>OSPOs in Energy, Transport, Automotive &amp; Public Sector</title>
                <subtitle></subtitle>
                <type>Panel</type>
                <date>2024-03-04T12:10:00+01:00</date>
                <start>12:10</start>
                <duration>00:40</duration>
                <abstract>In today&apos;s world, many organizations are recognizing the importance of Open Source Program Offices (OSPOs) in managing their open source activities. However, companies who are not primarily software companies face unique challenges in adopting OSPOs.</abstract>
                <slug>fossback24-38644-ospos-in-energy-transport-automotive-public-sector</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/NEE9SL/Share_v2-1_Governance_2_TJvD5iD.png</logo>
                <persons>
                    <person id='43177'>Ana Jimenez Santamaria</person><person id='43178'>Cornelius Schumacher</person><person id='43182'>Dr. Wolfgang Gehring</person><person id='42560'>Jonas van den Bogaard</person><person id='43184'>Alexander Butzlaff</person><person id='43213'>karel rietveld</person>
                </persons>
                <language>en</language>
                <description>In today&apos;s world, many organizations are recognizing the importance of Open Source Program Offices (OSPOs) in managing their open source activities by adopting a holistic approach to integrating open source into the organization&apos;s IT strategy. However, some companies who are not primarily software companies face unique challenges in adopting OSPOs. To bridge this gap, this panel will explore best practices that panelists have used in their industries towards building an OSPO. 

During this session, our panelists will focus on the following areas: 
- Why form an OSPO?
- What are the OSPO responsibilities?
- What are the considerations organizations should take care of BEFORE setting up an OSPO? (e.g organizational culture, open source project audit, existing procurements, and regulations, etc)
- How is the OSPO organized and staffed?
- Examples of how OSPOs work with policymakers and security teams in the EU?
- What are the biggest successes and challenges of the OSPO? 

Each of these areas presents its own set of strategic considerations that can serve as transition paths to successful OSPO adoption. 

Join us for a deep dive into the practical steps organizations can take to build an OSPO.

Panel Lead:
- Ana Jimenez - TODO Group, Linux Foundation

Panellists:
- Jonas van den Bogaard - Alliander OSPO
- Karel Rietveld - Dutch Tax and Customs Administration OSPO
- Cornelius Schumacher - Deutsche Bahn OSPO
- Alexander Butzlaff - Bundesdruckerei OSPO
- Wolfgang Gehring - Mercedes Benz Tech Innovation OSPO</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/NEE9SL/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/NEE9SL/feedback/</feedback_url>
            </event>
            <event guid='889a4bc8-6af8-5c02-b648-23174b558e7f' id='39255' code='SL7DWQ'>
                <room>Stage Auditorium</room>
                <title>A Journey to Inner Source</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T14:00:00+01:00</date>
                <start>14:00</start>
                <duration>00:30</duration>
                <abstract>Inner Source is like Open Source, it just stays within the company. Sounds easy enough, right?! However, you may find it&#8217;s just not working as smoothly as you had hoped. Why is that? In this session, we will explore Inner Source and talk about positive factors, obstacles, and what can be done.</abstract>
                <slug>fossback24-39255-a-journey-to-inner-source</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/SL7DWQ/Share_v2-1_Governance_12_m1hkKin.png</logo>
                <persons>
                    <person id='43182'>Dr. Wolfgang Gehring</person>
                </persons>
                <language>en</language>
                <description>So you have decided that Inner Source is the way to go for your enterprise. Good for you! The rest is a piece of cake. You only need to explain to your employees what this is all about. Oh yeah, and talk to the people from corporate tax, should be no problem, you know a guy there. Then get the legal department to answer some simple questions, and off you go! 

Alright, tooling is an issue, too. And governance... Ok ok, so you haven&#8217;t thought about all the minor details, but you just get everybody&#8217;s attention and spread the word. Easy! 

Right?!?

Let me talk about our journey at Mercedes-Benz. We haven&#8217;t solved everything yet, but we&#8217;re on a good path, and maybe our experience can help you a bit, too. We will look at what factors can make an Inner Source project successful, what some of the stumbling blocks can be and how to overcome at least some of them.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/SL7DWQ/resources/2024_FOSS_Backstage_-_A_Journey_to_Inner_Source__WuvQhS0.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/SL7DWQ/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/SL7DWQ/feedback/</feedback_url>
            </event>
            <event guid='445b5ea1-dfe7-5a82-b1e0-774c54fb4674' id='39081' code='LRRF8A'>
                <room>Stage Auditorium</room>
                <title>Embracing your weird: Community Building through Fun &amp; Play</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T14:35:00+01:00</date>
                <start>14:35</start>
                <duration>00:30</duration>
                <abstract>I believe that the community that plays together, stays together. It sounds cliche (and it is), but the first rule of community building is to remember that communities are made of people, not code. Incorporating &quot;intentional fun&quot; into your community engagements can yield some strong rewards.</abstract>
                <slug>fossback24-39081-embracing-your-weird-community-building-through-fun-play</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/LRRF8A/Share_v2-1_Governance_11_f3tGtC4.png</logo>
                <persons>
                    <person id='43383'>Tom &quot;spot&quot; Callaway</person>
                </persons>
                <language>en</language>
                <description>I believe that the community that plays together, stays together. It sounds cliche (and it is), but the first rule of community building is to remember that communities are made of people, not code. Over the last 15 years, I&apos;ve been experimenting with creating opportunities for the communities that I am a part participated in to play and have fun, at first subconsciously, but later, mindfully and intentionally. In this talk, I will share some of the ideas I have tried, along with some efforts that I have seen done in other communities. I hope to try to convince you to invest in creating opportunities for your communities to connect as people through laughter and play, and critically, and how that can help in growing the size, resiliency, and sustainability of open source communities.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/LRRF8A/resources/FOSS-Backstage-2024-EmbracingYourWeird_minimiert_NPn8f85.odp">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/LRRF8A/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/LRRF8A/feedback/</feedback_url>
            </event>
            <event guid='90b23632-59ad-582e-928f-7173d5674f29' id='38736' code='MPJV9Z'>
                <room>Stage Auditorium</room>
                <title>How you write matters in open source</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T15:30:00+01:00</date>
                <start>15:30</start>
                <duration>00:30</duration>
                <abstract>Form follows function in writing: you probably should write in a distinct way when the topic is open source. In this session, learn about unique writing challenges presented by open source projects and how to overcome them to be inclusive and accurate in your communication.</abstract>
                <slug>fossback24-38736-how-you-write-matters-in-open-source</slug>
                <track>Diversity &amp; Inclusion</track>
                <logo>/media/fossback24/submissions/MPJV9Z/Share_v2-5_Diversity_2_RnYm9Zj.png</logo>
                <persons>
                    <person id='42659'>Kyle J. Davis</person>
                </persons>
                <language>en</language>
                <description>Form follows function in writing: you compose a postcard to your Gran in a particular voice, attorneys draft contracts using specialized terms and grammatical structures, marketing pros formulate content with specific language to sell products, and you probably should write in a distinct way when the topic is open source. In this session, Kyle will go over some unique writing challenges presented by open source projects and how to overcome them to be inclusive and accurate in your communication. This session will dive into how seemingly innocuous terms and grammatical structures embed meaning that may be sending subtle, unintended messages. Additionally, time will be spent discussing how to select and use style guides to concretely establish a consistent voice and approach for both general writing and technical documentation.

In this talk, you&apos;ll learn about:
* Understanding the types of open source writing and audiences
* Linguistic code switching
* How writing about open source software differs from writing about other software &amp; services
* Owning your project&#8217;s &#8220;voice&#8221;
* Practical grammar and writing
    * Problems around anthropomorphizing
    * Ambiguous plural pronouns and unintended dominance
    * Picking the grammatical person for your project
    * Ensuring inclusive terminology
* Voice and style guide shopping (and building)
* Providing good writing feedback in GitHub</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/MPJV9Z/resources/foss-backstage-writing_lzyxHZO.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/MPJV9Z/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/MPJV9Z/feedback/</feedback_url>
            </event>
            <event guid='8d6c3d8a-6b0a-5287-b5bb-bba4d8da9eae' id='39084' code='M397Y7'>
                <room>Stage Auditorium</room>
                <title>Talking with management about open source</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T16:05:00+01:00</date>
                <start>16:05</start>
                <duration>00:30</duration>
                <abstract>You&apos;re passionate about open source, but your management cares about different things. Let&apos;s talk about how to bridge that gap.</abstract>
                <slug>fossback24-39084-talking-with-management-about-open-source</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/M397Y7/Share_v2-1_Governance_13_T7VARoP.png</logo>
                <persons>
                    <person id='43011'>Rich Bowen</person>
                </persons>
                <language>en</language>
                <description>For those of us who already know how important open source is, it can be challenging to persuasively make the case to management, because we assume that everyone already knows the basics. This can work against us, confusing our audience and making us come across as condescending or concerned about irrelevant lofty philosophical points.

In this talk, we take it back to the basics. What does management actually need to know about open source, why it matters, and how to make decisions about consuming open source, contributing to open source, and open sourcing company code?</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/M397Y7/resources/Rich_Bowen_-_Talking_To_Management_About_Open_So_bRZyC5l.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/M397Y7/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/M397Y7/feedback/</feedback_url>
            </event>
            <event guid='ff4f852a-95b0-5be7-a1b6-d27a32404474' id='38045' code='LEQ8GJ'>
                <room>Stage Auditorium</room>
                <title>How contribution programs benefit mentors and participants</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T16:40:00+01:00</date>
                <start>16:40</start>
                <duration>00:30</duration>
                <abstract>We will share our experience mentoring new contributors programs.  We will survey these programs and share both challenges and success stories. Some vivid examples demonstrate the advantages for both participants and the open source projects.</abstract>
                <slug>fossback24-38045-how-contribution-programs-benefit-mentors-and-participants</slug>
                <track>Diversity &amp; Inclusion</track>
                <logo>/media/fossback24/submissions/LEQ8GJ/Share_v2-5_Diversity_ixVWsNk.png</logo>
                <persons>
                    <person id='42043'>Carmen Delgado</person>
                </persons>
                <language>en</language>
                <description>Eclipse Adoptium is a top-level open source project under the Eclipse Foundation where Temurin and AQAvit are developed with assistance by &#8216;new to open source&#8217; contributors under industry mentorship. In this session, we share our experience mentoring new contributors through programs such as Outreachy, Google Summer of Code, and CANOSP.  We will survey these programs and share both challenges and success stories.  There are some vivid examples demonstrating the advantages for both participants and the open source projects. 

All of these open source programs have similarities but also their own unique flavor, with variations in goals and term lengths.  Outreachy provides paid internships to people subject to systemic bias and impacted by underrepresentation in the technical industry where they are living.  Google Summer of Code focuses on bringing new contributors into open source software development. Canada Open-Source Projects (CANOSP) is an academic program that connects top students from Canadian universities to work on open-source projects.  In all cases, the value of collaborating with new contributors who bring a diversity of experience and world view is the essence of open source.  This talk gives practical tips on working with open source programs but also serves to enlighten others on the mutually beneficial reasons they should engage.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/LEQ8GJ/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/LEQ8GJ/feedback/</feedback_url>
            </event>
            <event guid='9cfe613c-8760-5ea7-b67f-75c5312d9c07' id='47617' code='GHXWJS'>
                <room>Stage Auditorium</room>
                <title>Open Source and Inner Source for APIs - Can you treat your APIs like your code?</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2024-03-04T17:15:00+01:00</date>
                <start>17:15</start>
                <duration>00:05</duration>
                <abstract>Lightning talk</abstract>
                <slug>fossback24-47617-open-source-and-inner-source-for-apis-can-you-treat-your-apis-like-your-code</slug>
                <track></track>
                
                <persons>
                    <person id='50135'>Johannes Nicolai</person>
                </persons>
                <language>en</language>
                <description>This session is part of the lightning talks at FOSS Backstage 2024.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/GHXWJS/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/GHXWJS/feedback/</feedback_url>
            </event>
            <event guid='fd1f45c5-79f8-519f-a906-1e6e7c279d67' id='47618' code='JDPF3Q'>
                <room>Stage Auditorium</room>
                <title>TYPO3&apos;s successful approach to supporting government FOSS adoption in the Global South. Example: Rwanda</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2024-03-04T17:20:00+01:00</date>
                <start>17:20</start>
                <duration>00:05</duration>
                <abstract>Lightning talk</abstract>
                <slug>fossback24-47618-typo3-s-successful-approach-to-supporting-government-foss-adoption-in-the-global-south-example-rwanda</slug>
                <track></track>
                
                <persons>
                    <person id='50164'>Mathias Bolt Lesniak</person>
                </persons>
                <language>en</language>
                <description>This session is part of the lightning talks at FOSS Backstage 2024.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/JDPF3Q/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/JDPF3Q/feedback/</feedback_url>
            </event>
            <event guid='09cbaaac-9556-5c8d-8323-b2a862469e53' id='47619' code='PB7PYP'>
                <room>Stage Auditorium</room>
                <title>Bringing Open Source into the Digital Check for New Legislation</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2024-03-04T17:25:00+01:00</date>
                <start>17:25</start>
                <duration>00:05</duration>
                <abstract>Lightning Talk</abstract>
                <slug>fossback24-47619-bringing-open-source-into-the-digital-check-for-new-legislation</slug>
                <track></track>
                
                <persons>
                    <person id='50138'>Miriam Seyffarth</person>
                </persons>
                <language>en</language>
                <description>This talk is part of the lightning talk session at FOSS Backstage 2024</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/PB7PYP/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/PB7PYP/feedback/</feedback_url>
            </event>
            <event guid='8c8484f6-4fce-5f4c-9401-58df9b4f533f' id='47620' code='QBG8DY'>
                <room>Stage Auditorium</room>
                <title>A proposal for a scalable way to fund Open Source with Kudos at Semicolons</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2024-03-04T17:30:00+01:00</date>
                <start>17:30</start>
                <duration>00:05</duration>
                <abstract>Lightning Talk</abstract>
                <slug>fossback24-47620-a-proposal-for-a-scalable-way-to-fund-open-source-with-kudos-at-semicolons</slug>
                <track></track>
                
                <persons>
                    <person id='50136'>Matt Mankins</person>
                </persons>
                <language>en</language>
                <description>This talk is part of the lightning talk session at FOSS Backstage 2024.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/QBG8DY/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/QBG8DY/feedback/</feedback_url>
            </event>
            <event guid='e0cb3f79-7756-5b1b-a187-86b0bcf86424' id='47621' code='MN3MBM'>
                <room>Stage Auditorium</room>
                <title>Working in Open Source and Public Service in Germany (and the Sovereign Tech Fund)</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2024-03-04T17:35:00+01:00</date>
                <start>17:35</start>
                <duration>00:05</duration>
                <abstract>Lightning Talk</abstract>
                <slug>fossback24-47621-working-in-open-source-and-public-service-in-germany-and-the-sovereign-tech-fund</slug>
                <track></track>
                
                <persons>
                    <person id='50137'>Powen Shiah</person>
                </persons>
                <language>en</language>
                <description>This talk is part of the lightning talk session at FOSS Backstage 2024.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/MN3MBM/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/MN3MBM/feedback/</feedback_url>
            </event>
            <event guid='82258836-e40a-5770-9e22-420e3333fc53' id='43354' code='EHMZBC'>
                <room>Stage Auditorium</room>
                <title>Get-Together</title>
                <subtitle></subtitle>
                <type>Off Stage</type>
                <date>2024-03-04T18:00:00+01:00</date>
                <start>18:00</start>
                <duration>02:00</duration>
                <abstract>Join us for a drink and a chat at our Get Together directly after the conference!</abstract>
                <slug>fossback24-43354-get-together</slug>
                <track></track>
                
                <persons>
                    
                </persons>
                <language>en</language>
                <description>What better way to end the first day of FOSS Backstage than with a Get Together?

Take the opportunity to meet old and new friends or maybe the person to collaborate with on your next project in a relaxed atmosphere. 

Thanks to our partner [Mercedes-Benz Tech Innovation](https://opensource.mercedes-benz.com), food and drinks will be provided: We will offer a range of vegetarian and vegan snacks as well as alcoholic and non-alcoholic drinks.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/EHMZBC/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/EHMZBC/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Stage Wintergarten' guid='31282bc0-32b3-5ca2-ae3d-a9f2bbf987cf'>
            <event guid='be215d3c-6954-5749-aad2-4af75960f2b5' id='39128' code='3DHGWR'>
                <room>Stage Wintergarten</room>
                <title>A Strategic Approach to Assessing Viability of OSS Projects</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>00:30</duration>
                <abstract>Not all open source projects are created equal, and some will be more viable than others. This talk will help you strategically assess and measure open source software viability to make better business decisions when including open source projects into your products, services, and infrastructure.</abstract>
                <slug>fossback24-39128-a-strategic-approach-to-assessing-viability-of-oss-projects</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/3DHGWR/Share_v2-1_Governance_6_8kIGQWn.png</logo>
                <persons>
                    <person id='43056'>Dawn Foster</person>
                </persons>
                <language>en</language>
                <description>The ease in adopting open source software means that organizations sometimes use open source software without giving much thought to whether the projects that produce that software are likely to be viable over the long-term. What happens when a project changes their license, stops making security updates, or has other issues that impact its usage? When an open source project that later becomes unviable has already been incorporated into your products or services, this can have implications for your users, customers, and reputation. 

It&#8217;s worth spending time to critically assess whether a project is likely to be successful and continue to meet your needs over the long-term. Open source project decisions have strategic implications that should be proactively evaluated to identify risks that can be mitigated. Ultimately, whether to use an open source project boils down to balancing the risk vs. the reward for your use case.

This talk will compare the risks and rewards associated with projects under neutral foundations vs. those controlled by companies and look at how the people leading and contributing to the project can influence risk. The presentation will contain details about how to assess project policies, governance, security practices, adoption, and community dynamics that can impact the stability and overall success of a project. Throughout the presentation, there will be discussions about techniques for measurement and which collections of metrics might be appropriate for your evaluations.

The audience will walk away with practical advice about how to strategically evaluate the viability of open source projects and assess the risks and rewards for their situation. The presentation also provides insight into how other people might evaluate the sustainability of your organization&#8217;s projects.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/3DHGWR/resources/Strategic_Approach_Viability_FOSSBack_compressed_TVnObCJ.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/3DHGWR/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/3DHGWR/feedback/</feedback_url>
            </event>
            <event guid='74eed419-9c6b-5690-8053-399d9a3d7dee' id='39378' code='SVRP9E'>
                <room>Stage Wintergarten</room>
                <title>EU cybersecurity regulation and Open Source governance</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T11:35:00+01:00</date>
                <start>11:35</start>
                <duration>00:30</duration>
                <abstract>The EU Cyber Resilience Act sets standards for how software should be designed, developed and distributed with security in mind. Any regulation of how software is developed also affects FOSS.  How do individual developers and communities adapt to the new regulatory environment?</abstract>
                <slug>fossback24-39378-eu-cybersecurity-regulation-and-open-source-governance</slug>
                <track>Security</track>
                <logo>/media/fossback24/submissions/SVRP9E/Share_v2-2_Security_eTCNgIo.png</logo>
                <persons>
                    <person id='43307'>Mirko Boehm</person>
                </persons>
                <language>en</language>
                <description>Non-commercial FOSS development is excluded from the scope of the EU Cyber Resilience Act, and so are individual volunteer developers. Businesses are not. But where is the line between an incorporated FOSS community and an open source business? Depending on the answer, making FOSS releases comes with significant obligations like implementing maintenance and vulnerability reporting processes, self or third party certifications or providing patches for the 5 years or more lifecycle of the product. This will impact the viability of some FOSS development models like that of part-time maintainers supported by donations, or business-sponsored communities. The governance setup of FOSS projects may have to be sharpened to match the roles required in the law. The presentation will break down the obligations, when and how they apply and what actions communities can take to handle them.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/SVRP9E/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/SVRP9E/feedback/</feedback_url>
            </event>
            <event guid='0ff021f8-be4e-5a0d-8a3f-d1d93c5ac329' id='38441' code='EL7CEP'>
                <room>Stage Wintergarten</room>
                <title>FOSS and Security Risk Management</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T12:10:00+01:00</date>
                <start>12:10</start>
                <duration>00:30</duration>
                <abstract>Due to the complex nature of software products, it&apos;s not always possible to patch all known vulnerabilities and insecurities in time. But how to take the choice what to take care about? And are there legal requirements?</abstract>
                <slug>fossback24-38441-foss-and-security-risk-management</slug>
                <track>Security</track>
                <logo>/media/fossback24/submissions/EL7CEP/Share_v2-6_Legal_2_fMEsh1U.png</logo>
                <persons>
                    <person id='42431'>fukami</person>
                </persons>
                <language>en</language>
                <description>Recent and ongoing EU legislation concerning data protection, product and service security fundamentally change how insecurity is supposed to be dealt with. For FOSS, managing security risks is crucial, and this talk is examining its intersection with these recent legal changes. The talk will focus on practical approaches, strategies and frameworks for assessing, prioritizing, and mitigating security risks. Whether you&apos;re a FOSS enthusiast, developer, or security professional, this talk provides valuable insights into safeguarding FOSS use within a shifting regulatory landscape.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/EL7CEP/resources/Backstage24-fukami_2Ijt5Gc.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/EL7CEP/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/EL7CEP/feedback/</feedback_url>
            </event>
            <event guid='d3674b17-8edf-5821-bd72-a1aa229ccf06' id='39199' code='MLAFCH'>
                <room>Stage Wintergarten</room>
                <title>Open Source Contributions in Today&#8217;s World</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T14:00:00+01:00</date>
                <start>14:00</start>
                <duration>00:30</duration>
                <abstract>Are you contributing to an OSS project? And do you know how to distribute software in today&#8217;s diverse ecosystem? What publishing software legally implies when it comes to containers and AI code? If you want to learn about insights from a technical AND a legal point of view, this talk is for you!</abstract>
                <slug>fossback24-39199-open-source-contributions-in-today-s-world</slug>
                <track>Legal &amp; Compliance</track>
                <logo>/media/fossback24/submissions/MLAFCH/Share_v2-6_Legal_3_gI53ArL.png</logo>
                <persons>
                    <person id='43384'>Dr. Lina B&#246;cker</person><person id='43949'>Angelika Wittek</person>
                </persons>
                <language>en</language>
                <description>We will start by outlining the drawing up the legal and technical framework between copyright and, patent law, new EU regulations (Cyber Resilience Act and Product Liability Directive) and different FOSS licenses.We will explain, explaining some crucial terms and the change of their meaning in the past few years (such as distribution).

Against this background, we will share, from a technical position, suggestions on FOSS compliance in real-world scenarios examples, such as publishing artifacts on package managers, repositories, docker and in the cloud.

From a technical point of view we show real-world scenarios,
e.g. publishing code and the according legal documentation under different OSS licenses and making build artifacts publicly available on package managers, Docker and the cloud in a FOSS-compliant manner.

Using these examples, we will show from a lawyer&#8217;s angle how the legal requirements need to be  reflected in the composition of software applications and what the practical consequences are for contributors in the modern FOSS world. We will, in particular, give some hints on how to deal with (a lack of) license compatibility in the cloud, specific license obligations and other requirements that might result from working with Open Source Software. 

To round things up, Lina will share an update on new obligations for FOSS distributors resulting from the Cyber Resilience Act, the Product Liability Directive and AI.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/MLAFCH/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/MLAFCH/feedback/</feedback_url>
            </event>
            <event guid='e77b5bc4-24a0-5364-b277-89470064ad9b' id='38392' code='9JVKJG'>
                <room>Stage Wintergarten</room>
                <title>Automating Open-Source License Compliance</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T14:35:00+01:00</date>
                <start>14:35</start>
                <duration>00:30</duration>
                <abstract>Open-source license compliance can require a lot of effort and manual work. Fortunately, most of the tasks can be automated. Would you like to know how to automate the open-source license compliance process using open-source tools?</abstract>
                <slug>fossback24-38392-automating-open-source-license-compliance</slug>
                <track>Legal &amp; Compliance</track>
                <logo>/media/fossback24/submissions/9JVKJG/Share_v2-6_Legal_5_XzWjM4B.png</logo>
                <persons>
                    <person id='42374'>Petteri Kivim&#228;ki</person>
                </persons>
                <language>en</language>
                <description>X-Road&#174; 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&#8217;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.

X-Road utilises many third party open source libraries and components that are licensed under various open source licenses. The dependencies are managed using different package management systems depending on their implementation technologies, e.g., Gradle / Java, NPM / Javascript. Overall, the number of direct dependencies is counted in tens and the number of transitive dependencies is counted in hundreds.

The main challenges regarding the open source license compliance are how to meet the requirements of the licenses of different 3rd party components and how to know that they&apos;re not conflicting with the main license? Until 2021 the legal qualities of the X-Road&#8217;s software packages were validated approximately once year using a project based approach that required a lot of manual work. In summer 2021, the open source compliance was automated to the largest effective extent by taking into use Open Source Review Toolkit (ORT) and integrating it into the development process and CI/CD pipelines.

In my talk, I&apos;m going to give an overview of X-Road first. Then, I&apos;m going to discuss the open source compliance automation project, its different phases and deliverables. The main scope of the presentation is to discuss the benefits of open source compliance automation and what should be taken consideration in the process.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/9JVKJG/resources/2024-03-04-Petteri_Kivim%C3%A4ki-Automating_Open-Sour_Cmlqqx0.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/9JVKJG/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/9JVKJG/feedback/</feedback_url>
            </event>
            <event guid='b45ccfb1-21aa-53c7-92ba-e239646109e0' id='38465' code='BZ8RG7'>
                <room>Stage Wintergarten</room>
                <title>Distributed teams that actually work!</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T15:30:00+01:00</date>
                <start>15:30</start>
                <duration>00:30</duration>
                <abstract>Based on two decades of experience in Open Source communities and corporate distributed teams, this talk revisits the core principles of remote collaboration. Concrete recommendations will help you improve the efficiency and happiness of your distributed teams.</abstract>
                <slug>fossback24-38465-distributed-teams-that-actually-work</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/BZ8RG7/Share_v2-1_Governance_JVbXqtN.png</logo>
                <persons>
                    <person id='42450'>Bertrand Delacretaz</person>
                </persons>
                <language>en</language>
                <description>Do distributed teams really need to spend most of their time in video meetings to make things happen? Drawing from over two decades of experience in Open Source projects and corporate distributed teams, this talk goes back to the fundamental principles of remote collaboration to explain why the answer is no.

Discover the power of asynchronous decision-making tools and techniques, communication patterns that prioritize clarity and brevity, how being nice and constructive matters, and the art of choosing the right communication tools and using them efficiently.

Many learnings from successful Open Source projects apply to all organizations, but there&apos;s no one-size-fits-all solution. Understanding the core principles will help you tune our recommendations to your team&apos;s shape and experience.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/BZ8RG7/resources/distributed-teams-foss-backstage-2024-bertrand_c_3h3obFz.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/BZ8RG7/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/BZ8RG7/feedback/</feedback_url>
            </event>
            <event guid='ced291ad-6524-5a1d-ad02-a8b73ceda9b5' id='38073' code='LQUUXM'>
                <room>Stage Wintergarten</room>
                <title>Why is there no new Release? Nobody pays for the basics :-(</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-04T16:05:00+01:00</date>
                <start>16:05</start>
                <duration>00:30</duration>
                <abstract>The Relax-and-Recover (ReaR) Open Source project exists since 2006 and is now the de-facto standard for automated Linux Disaster Recovery.

A behind-the-scenes look at how a project works for such a long time, what goes well and what could be better, with specific examples and advice for others.</abstract>
                <slug>fossback24-38073-why-is-there-no-new-release-nobody-pays-for-the-basics</slug>
                <track>Sustainability &amp; Funding</track>
                <logo>/media/fossback24/submissions/LQUUXM/Share_v2-4_Sustainabilty_3_KDdgp5j.png</logo>
                <persons>
                    <person id='42067'>Schlomo Schapiro</person><person id='42068'>Gratien Dhaese</person>
                </persons>
                <language>en</language>
                <description>ReaR was born out of a single customers&apos; need and a consulting project, to offer a cheaper and better alternative to a commercial disaster recovery product. Since then it has grown by many contributions to cover nearly any disaster recovery situation for Linux servers and desktops - and it is used in many data centres around the world. Red Hat and SUSE even provide commercial support, with their package maintainers also acting as ReaR maintainers.

With all this success, we still struggle to provide regular releases, test automation or even good architecture documentation.

This talk explores the reasons for that and shows some of the approaches that work, and some that didn&apos;t work. I&apos;ll be happy for a conversation with other maintainers/projects about how they solve this problem.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/LQUUXM/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/LQUUXM/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Monday: Workshop Room /  Tuesday: Remote Stage' guid='8c8a6b23-136b-5808-b2c2-7892f91b8a9d'>
            <event guid='947715b3-b8e0-5ebb-9f77-9902016474e5' id='39257' code='X7PCWD'>
                <room>Monday: Workshop Room /  Tuesday: Remote Stage</room>
                <title>How to explain your project better &#128712;</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2024-03-04T11:35:00+01:00</date>
                <start>11:35</start>
                <duration>01:00</duration>
                <abstract>You&apos;ve spent hours and sleepless nights coding a project that promises to solve someone&apos;s problems bigger, better, and faster. But no one understands it or how to use it. This workshop aims to help you communicate your project&apos;s intentions more clearly.</abstract>
                <slug>fossback24-39257-how-to-explain-your-project-better</slug>
                <track>Growing Open Source</track>
                <logo>/media/fossback24/submissions/X7PCWD/Share_v2-3_Growing_2_ymPpIrr.png</logo>
                <persons>
                    <person id='43187'>Chris Chinchilla</person>
                </persons>
                <language>en</language>
                <description>Many open-source projects are technically brilliant, with great intentions and approaches, but poorly communicated. Potential users aren&apos;t clear on what a project is, what it does, why it might help them, and why they should try it. Even if they get past that initial point of confusion, they will likely find documentation and other resources that are unclear, incomplete or don&apos;t work.

All these people a project loses or confuses are potential users, contributors, and community members.

In this workshop, I cover a series of easy-to-follow nuggets of tips and advice to communicate your project better, including:

- Explaining what you do as an elevator pitch
- How to decide on consistent terminology
- How to communicate clearly
- How to make your communication more confident without losing important details 
- What resources to create and maintain to help with communication
- And more!

&#128712; This workshop won&apos;t be recorded and participation is only possible onsite.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/X7PCWD/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/X7PCWD/feedback/</feedback_url>
            </event>
            <event guid='53b5b5c1-6538-5eb1-9f18-996f2dfef32f' id='39239' code='LLAFBT'>
                <room>Monday: Workshop Room /  Tuesday: Remote Stage</room>
                <title>Single Developer Community? About community architecture. &#128712;</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2024-03-04T14:00:00+01:00</date>
                <start>14:00</start>
                <duration>01:00</duration>
                <abstract>Most FOSS projects are a one-man show, so a key question remains: How do we build a functional, diverse and vivid community? After some insights from research on Linux distribution communities, we want to share pitfalls and potentials of participatory design in the FOSS community.</abstract>
                <slug>fossback24-39239-single-developer-community-about-community-architecture</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/LLAFBT/Share_v2-1_Governance_4_56WK4W4.png</logo>
                <persons>
                    <person id='43162'>Daniel Guagnin</person><person id='43164'>Antonios Hazim</person><person id='48398'>Anett H&#252;bner</person>
                </persons>
                <language>en</language>
                <description>Most FOSS projects are a one-man show, so a key question remains: How do we build a functional, diverse and vivid community?
What decisions do we want to make, who should be allowed to contribute and in what area? How to get the community involved?
It seems simple: whoever writes the code is right, and their decisions are simply implemented. But there is no one right answer, and fundamental questions can lead to forking and weakening of the community.

After a brief introduction to the development of community structures and their impact on the software produced, based on research in various Linux distribution communities and the Android FOSS community, we will discuss the pitfalls and key elements of community design and Human Centered Design as a practical approach to community-driven research in a world caf&#233;.

&#128712; This workshop won&apos;t be recorded and participation is only possible onsite.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/LLAFBT/resources/FOSS_Backstage_Voll_TbZY7o3.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/LLAFBT/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/LLAFBT/feedback/</feedback_url>
            </event>
            <event guid='bc18efe4-0d2e-516d-98a0-a01fec0d4147' id='39270' code='RPNDEV'>
                <room>Monday: Workshop Room /  Tuesday: Remote Stage</room>
                <title>Bridging Both Sides: A FOSS Funding LARP &#128712;</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2024-03-04T15:30:00+01:00</date>
                <start>15:30</start>
                <duration>01:00</duration>
                <abstract>Step into the shoes of both FOSS funders and creators and engage in a dynamic world of fictitious organizations and collectives in a live-action role play (LARP) of&#8230; THE FOSS FUNDING PROCESS</abstract>
                <slug>fossback24-39270-bridging-both-sides-a-foss-funding-larp</slug>
                <track>Sustainability &amp; Funding</track>
                
                <persons>
                    <person id='48400'>Carolyn Beer</person><person id='43201'>Eric Bear</person><person id='43202'>ng&#7885;c tri&#7879;u</person>
                </persons>
                <language>en</language>
                <description>Over the span of a captivating and fast-paced hour, participants will, with a touch of space-time manipulation, navigate the intricate landscape of a many-month-long funding process. 

Participants playing as FOSS funders will be designing, and carrying out the funding processes for fictitious funding bodies, while those playing as FOSS creators will be applying to them with fictitious projects. 

Throughout the experience, participants will: 
- Gain empathy and understanding for people&#8217;s experiences on both sides of the process
- Discover friction/leverage points in the overall funding system
- Identify and codesign structures, patterns, and approaches to better provide and pursue funding
- Have fun!

&#128712; This workshop won&apos;t be recorded and participation is only possible onsite.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/RPNDEV/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/RPNDEV/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Lobby' guid='c3579769-2cd5-5a07-9eeb-abeaabe157b5'>
            <event guid='0572773d-e9a1-5810-9c59-26ee7d621581' id='44662' code='M8NDTK'>
                <room>Lobby</room>
                <title>Accessibility Clinic &#128712;</title>
                <subtitle></subtitle>
                <type>Off Stage</type>
                <date>2024-03-04T10:45:00+01:00</date>
                <start>10:45</start>
                <duration>04:45</duration>
                <abstract>Web accessibility clinic for open-source privacy and security tools: Enhancing user experiences for people with disabilities</abstract>
                <slug>fossback24-44662-accessibility-clinic</slug>
                <track>Diversity &amp; Inclusion</track>
                
                <persons>
                    <person id='48269'>Nancy Reyes</person><person id='47623'>Raashi Saxena</person>
                </persons>
                <language>en</language>
                <description>Does your open-source project need a second opinion to improve accessibility features? Are you building/designing software and want to learn more about how to make your product accessible? Come visit the Accesibility Lab&apos;s help desk clinic hours to chat with the experts that can consult with you directly to cater to your needs. 

One in 6 people across the world suffer from a disability. Many designers meanwhile know of design accessibility and may even recognize the growing need to ensure a design that is accessible to people with disabilities. Yet how to address web accessibility is commonly not well understood, and there are often sensitivities and myths.

Our idea is to explore the intersection of accessibility for people with disabilities with other disciplines, including language support, artificial intelligence, privacy and data protection, security, and safety. For example, how do AI bias, dark patterns, and lack of language support lead to discrimination, and how can we work together to ensure the inclusion of everyone? This clinic brings together expertise from various disciplines and geographies to share insights on interdisciplinary approaches for an inclusive design that enhances the navigation capacity of people with disabilities. 

This accessibility clinic is a bold endeavour to encourage FOSS tool teams or individuals (designers, developers, decision makers, project managers, etc.) to talk about accessibility challenges and coach them in any way they need.

We perform live audits, training &amp; testing with their tool, website or app using assistive technology to simulate disabilities.

&#128712; This session won&apos;t be recorded and participation is only possible onsite.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/M8NDTK/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/M8NDTK/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    <day index='2' date='2024-03-05' start='2024-03-05T04:00:00+01:00' end='2024-03-06T03:59:00+01:00'>
        <room name='Stage Auditorium' guid='f6a7acb1-4d2c-5dd6-bb0d-f245d3aa58ee'>
            <event guid='e589fae6-d6b6-5d81-ba2f-7729c18c6fc5' id='43280' code='BFTPXD'>
                <room>Stage Auditorium</room>
                <title>CERN&#8217;s Open Source Program Office</title>
                <subtitle></subtitle>
                <type>Keynote</type>
                <date>2024-03-05T10:00:00+01:00</date>
                <start>10:00</start>
                <duration>00:40</duration>
                <abstract>CERN, the physics lab near Geneva, operating the Large Hadron Collider, has a rich history of Open Source contributions and in Open Science. Last year CERN established an innovative Open Source Program Office (OSPO), covering both software and hardware. The OSPO aims to ensure CERN&apos;s Open Source projects adhere to best practices, fostering consistency and longevity of Open Source at CERN.</abstract>
                <slug>fossback24-43280-cern-s-open-source-program-office</slug>
                <track>Growing Open Source</track>
                <logo>/media/fossback24/submissions/BFTPXD/Share_v2-3_Growing_8_byNtTao.png</logo>
                <persons>
                    <person id='48818'>Giacomo Tenaglia</person>
                </persons>
                <language>en</language>
                <description>The European Organization for Nuclear Research (CERN) is considered the world&#8217;s largest physics lab and sits on the border of France and Switzerland, close to Geneva. It is known for operating the Large Hadron Collider, and also runs many other research projects as well as all the supporting infrastructure. CERN&#8217;s community is a strong user, supporter and contributor to Open Source and is proud to have been the founder of many Open Source innovations, among them being the World Wide Web. Open Source is one of the key elements of CERN&#8217;s Open Science activities. 
Last year, November 2023, CERN launched an Open Source Program Office to better support Open Source practices at CERN. In comparison to other OSPOs around, CERN&#8217;s OSPO takes a novel approach by including Open Source Hardware in it. The internal and external mandate of the OSPO underlines its a service &#8220;from the community to the community&#8221; to make sure CERN&#8217;s Open Source projects, contributions and usage is consistent, long-lived and following best practices.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/BFTPXD/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/BFTPXD/feedback/</feedback_url>
            </event>
            <event guid='d91583e3-93e0-5210-8a89-1a6a8cb1befd' id='39188' code='A8WREG'>
                <room>Stage Auditorium</room>
                <title>Has Open Source outgrown the OSPO?</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>00:30</duration>
                <abstract>Our definition of OSPOs have largely stayed the same since Sun microsystems establised their OSPO in the 90s - but open source is no longer a fringe activity understood by the few, but a critical part of a companys overall IT strategy - so isn&apos;t it time that we change how OSPOs work?</abstract>
                <slug>fossback24-39188-has-open-source-outgrown-the-ospo</slug>
                <track>Growing Open Source</track>
                <logo>/media/fossback24/submissions/A8WREG/Share_v2-3_Growing_6_ZpJiun8.png</logo>
                <persons>
                    <person id='43116'>Per Ploug Krogslund</person>
                </persons>
                <language>en</language>
                <description>The fundamental concept and purpose of having an open source programme office
has largely stayed the same, since Sun Microsystems launched their OSPO in 1999. The TODOGroup
definition of OSPOs still focuses on centering open source compliance, policies and communities
around an OSPO. 

But the world and the criticality of Open Source has dramatically changed the last 25 years, and we 
See both a greater maturity inside companies making the OSPO largely unnecessary, as well as bigger 
challenges which an OSPO Is not enabled to solve, but should rather be an integral part of the companys 
IT strategy as a whole. 

Open source is no longer a fringe activity, but something which 97% of companies use, and for the large part is a very critical part of their IT strategy and investment. At the same time the vendor landscape as well as 
internal Security, Legal and compliance teams have matured their understanding of open source and no 
longer need an OSPO to support them. 

So what does the OSPO of the future look like? Is there even a need and a space for such a function? 

In this session I will bring in my learnings from 10 years in an open source start up and from establishing OSPOs  in 2 of the largest european tech companies and give my view on how OSPOs should position themselves to  still be relevant and support open source going forward.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/A8WREG/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/A8WREG/feedback/</feedback_url>
            </event>
            <event guid='3e090db7-4610-5312-92b2-a758c6c64ca0' id='39156' code='WANZN8'>
                <room>Stage Auditorium</room>
                <title>Open Source Excellence: Munich&apos;s Journey towards Public Code</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T11:35:00+01:00</date>
                <start>11:35</start>
                <duration>00:30</duration>
                <abstract>Following an important decision by the Munich City Council, the publication of all internal software developments has been the standard since 2021. In our presentation, you will find out which success factors, advantages and legal conditions are decisive for this change.</abstract>
                <slug>fossback24-39156-open-source-excellence-munich-s-journey-towards-public-code</slug>
                <track>Growing Open Source</track>
                <logo>/media/fossback24/submissions/WANZN8/Share_v2-3_Growing_3_54IM2U2.png</logo>
                <persons>
                    <person id='43089'>Dr. Dirk Gernhardt</person><person id='47513'>Klaus Mueller</person>
                </persons>
                <language>en</language>
                <description>The City of Munich has a long open source history. We have been using open source products and frameworks in both infrastructure and software development since the turn of the millennium.
We reached a new level of our open source development in 2021 when our city council decided that all open source in-house developments would be made publicly available - according to the principle of public money - public code.
With our presentation, we would like to show what the success factors for open source development are, what advantages it has and what legal and organizational requirements we had to create for this.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/WANZN8/resources/2024-03-FOSS-Backstage-Gernhardt-Mueller-Munich__N99gX5j.odp">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/WANZN8/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/WANZN8/feedback/</feedback_url>
            </event>
            <event guid='4e170521-99b7-54b9-a798-60f01926c549' id='39189' code='M9JRSR'>
                <room>Stage Auditorium</room>
                <title>Freedom vs Sustainable Business: A Candid Necessary Debate</title>
                <subtitle></subtitle>
                <type>Panel</type>
                <date>2024-03-05T12:10:00+01:00</date>
                <start>12:10</start>
                <duration>00:40</duration>
                <abstract>The interplay between freedom, business sustainability, and open source models confronts a pivotal moment. In this debate panel we will explore licenses types, business models and open source sustainability in a candid needed manner as a way to improve ethics, sustainability and community</abstract>
                <slug>fossback24-39189-freedom-vs-sustainable-business-a-candid-necessary-debate</slug>
                <track>Legal &amp; Compliance</track>
                <logo>/media/fossback24/submissions/M9JRSR/Share_v2-6_Legal_4_Apg61WT.png</logo>
                <persons>
                    <person id='43140'>Thomas Steenbergen</person><person id='43384'>Dr. Lina B&#246;cker</person><person id='43117'>Paloma Oliveira</person><person id='48404'>Fiona Krakenb&#252;rger</person>
                </persons>
                <language>en</language>
                <description>Open source software, the bedrock of innovation and collaboration in the modern software industry, faces a critical juncture as the interplay between freedom, sustainable business models and sustainable open source models becomes increasingly complex. The choice of open source license, once considered a technical decision, now carries profound ethical and legal implications, impacting its community, its development, distribution, and usage.

This discussion panel will explore the current landscape of open source licenses - from permissive, ethical, dual and business-source, examining the impact of recent developments and changes on individual developers, communities, and its effects on society. Through a debate-style format, panelists will engage in a discussion on the following topics:

1) The ethical implications of different open source license types: the ethical considerations surrounding copyleft, permissive, and hybrid licenses, examining the impact of license choices on the freedom to modify, distribute, and build upon open source software.

2) The impact of license changes on existing software projects and communities: the challenges and opportunities presented by license changes, discussing the ethical implications of altering the terms of existing open source projects and the potential impact on communities of developers and users.

3) The role of open source licenses in addressing issues of intellectual property, copyright, and fair use: explore the legal and ethical complexities surrounding open source licenses, examining how different license types address issues of intellectual property, copyright, and fair use in the context of open source software development and utilization.

4) The ethical considerations of using open source software in commercial products: discuss the ethical implications of incorporating open source software into commercial products, examining the balance between leveraging open source contributions and ensuring fair compensation for developers and contributors.

5) Real cases to have a candid conversation from both sides: Recent news and changes on companies like HashiCorp and Red Hat can be analyzed and the implications can be explored in a non defensive or offensive way, favoring dialogue and deepening the discussion

6) Balancing open source principles with sustainable business models: the challenges faced by companies in balancing the principles of open source with the financial realities of running a business, examining the need for sustainable business models that support the development and maintenance of open-source projects.

This panel will provide a platform for open and honest dialogue on the ethical complexities of open source licenses, fostering a deeper understanding of the ethical implications of our technological choices. By engaging in this discussion, we can collectively work towards developing a more ethical and responsible approach to open source software development and use, ensuring that open source remains a force for innovation, collaboration, and societal benefit.

*I&apos;ll be mediating the debate. I will invite 3 panelists who will be prepared for the debate. The choice of panelists will depend on people who confirm their presence at the event, either because they have tickets or are confirmed speakers. In this way, we can avoid extra costs for production and/or panelists

**Debate rules will also be put in place to encourage honest and non-inflammatory discussions, since the proposal is to deepen discussions in a safe space.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/M9JRSR/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/M9JRSR/feedback/</feedback_url>
            </event>
            <event guid='0ed3c19c-779b-5856-8666-f675e5e6eae9' id='38480' code='KRPEVQ'>
                <room>Stage Auditorium</room>
                <title>What the AI revolution means for Open Source and our society</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T14:00:00+01:00</date>
                <start>14:00</start>
                <duration>00:30</duration>
                <abstract>This talk will discuss the current challenges around AI. In the second half it covers the new innovative local and open source AI features that the Nextcloud community is building. At the end the talk looks into the new Ethical AI framework and what it means for existing SaaS AI solutions</abstract>
                <slug>fossback24-38480-what-the-ai-revolution-means-for-open-source-and-our-society</slug>
                <track>Growing Open Source</track>
                <logo>/media/fossback24/submissions/KRPEVQ/Share_v2-3_Growing_5_kRCMZFg.png</logo>
                <persons>
                    <person id='42461'>Frank Karlitschek</person>
                </persons>
                <language>en</language>
                <description>In the last year we saw the rise of AI systems like ChatGPT, Stable Diffusion, Dall-E and others. Large Language Models like GPT are enabling a lot of new innovative features and products which will revolutionise the world.
But this large autoregressive language models come with a lot of challenges that can have negative effects on the Open Source and Open Tech community. For example it&#8217;s unclear if in the future everyone will have access to the same ML models and training data. Can students, startups and open source people build innovative new products using AI in the same way the open source communities build Open Code and Open Tech. How can we make sure that the AI system are not discriminating underrepresented minorities? What is the energy consumption and CO2 emissions of this new big AI systems? 
This talk will discuss the current challenges around AI. In the second half it covers the new innovative local and open source AI features that the Nextcloud community is building. At the end the talk looks into the new Ethical AI framework and what it means for existing SaaS AI solutions and the open source local alternatives. It  also covers the ongoing discussion to define an Open Source AI definition in the OSI community.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/KRPEVQ/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/KRPEVQ/feedback/</feedback_url>
            </event>
            <event guid='18dd6184-15f0-5c0f-b02b-5d3d621a1010' id='39478' code='YRNQMR'>
                <room>Stage Auditorium</room>
                <title>The Cuckoo in Bidding: When the Manufacturer Loses to Itself</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T14:35:00+01:00</date>
                <start>14:35</start>
                <duration>00:30</duration>
                <abstract>OSS manufacturers must be financially compensated for their work to enable further development. When freeloaders enter bidding processes with cutthroat prices without manufacturer involvement, they strip the OSS ecosystem of its foundation. Various initiatives aim to ensure fair and sustainable use.</abstract>
                <slug>fossback24-39478-the-cuckoo-in-bidding-when-the-manufacturer-loses-to-itself</slug>
                <track>Sustainability &amp; Funding</track>
                <logo>/media/fossback24/submissions/YRNQMR/Share_v2-4_Sustainabilty_3Mf6f1P.png</logo>
                <persons>
                    <person id='43423'>Peer Heinlein</person><person id='43705'>Daniel Zielke</person>
                </persons>
                <language>en</language>
                <description>Open Source often means more than just &quot;free and accessible source code&quot;; it also encompasses license models for free, unrestricted use. Yet, there are companies that successfully develop high-quality, commercially viable software with significant financial investment and a dedicated team of developers. Revenue is generated through &quot;service and support&quot; contracts, quality-tested releases, troubleshooting with short SLAs, or assistance with rollout and operation. This is based on the general understanding and acceptance that manufacturers need to be financially compensated for the use of their software, even if it is available as FOSS.

As Open Source becomes more popular in public administration, procurement projects are increasingly being tendered solely on price. This attracts bidders who neither internalize nor share the principles of free software: Parasitic freeloaders offering third-party software on pure operational terms without any manufacturer compensation, consistently outbidding the manufacturer or its partners. Like a cuckoo, they shirk the work of raising their young onto others, even killing their offspring and peers in the process.

The consequences are devastating. If this happens systematically and regularly, it rapidly deprives any further development of Open Source software of its financial foundation. The Open Source ecosystem is ruthlessly destroyed by freeloaders who play against the rules.

How can Open Source projects protect themselves against this abuse?

Various associations and providers are currently launching initiatives to ensure fair and sustainable procurement of Open Source software. A &quot;Code of Conduct&quot; could foster a common understanding. Ultimately, the tendering entities and public procurement officers need to be convinced that pure tenders seeking only the cheapest bidder destroy their future choices. And there are legal tasks to be accomplished: What might legally robust &quot;Fair Use&quot; clauses look like that could become mandatory criteria for tenders?</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/YRNQMR/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/YRNQMR/feedback/</feedback_url>
            </event>
            <event guid='0b54e4eb-5d40-5b2e-8528-351b6c7287b6' id='39162' code='CPMH8W'>
                <room>Stage Auditorium</room>
                <title>A modern OS information system for the french fire fighters</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T15:30:00+01:00</date>
                <start>15:30</start>
                <duration>00:30</duration>
                <abstract>Camptocamp has been working since 2019 on the NexSIS 18-112 project, the future information and command system of the French fire and rescue services. We will present the journey and the challenges we had to overcome when building a mission critical information system based on OS technologies.</abstract>
                <slug>fossback24-39162-a-modern-os-information-system-for-the-french-fire-fighters</slug>
                <track>Growing Open Source</track>
                <logo>/media/fossback24/submissions/CPMH8W/Share_v2-3_Growing_1V8fcDf.png</logo>
                <persons>
                    <person id='43106'>Olivia Guyot</person>
                </persons>
                <language>en</language>
                <description>Camptocamp has been working with its partners for over four years on the technical implementation of the NexSIS 18-112 project, the future information and command system for the French fire and rescue services. The project is being carried out on behalf of the Agence du Num&#233;rique de la S&#233;curit&#233; Civile (ANSC), which reports to the Ministry of the Interior. The Camptocamp teams, responsible for implementing the NexSIS geographical information system, faced several challenges in order to develop a modern, resilient and ergonomic solution.
True to its DNA, Camptocamp is building this solution exclusively using open source building blocks. This desire to promote and contribute to open source tools wherever possible is shared with our customer.

Geographical information has a central place within NexSIS. Most of the functions of NexSIS are supplied or enriched with geographical data via mainly cartographic user interfaces: rapid localization of an emergency situation following a call to 18 (or 112); transmission of intervention information to all the forces responsible for this emergency situation (fire department, police, gendarmerie, municipal authorities, prefectures, road or energy network operators, etc.); mobilization of the most appropriate personnel and equipment to be sent on rescue missions.

All these functions require heterogeneous geographical data from very different sources: Data producers (Base Adresse Nationale, Institut G&#233;ographique National, HERE), organizations and companies (SNCF, RTE, Veolia, Voies Navigables de France, etc.), field reports (fire and rescue services), open data (OpenStreetMap), etc. This heterogenity leads to a certain technical complexity, but above all to an extensive set of functions in NexSIS, ultimately providing a better service for the end users, the firefighters.

The aim of the presentation is therefore to use the example of NexSIS to show how open source tools and data can make the work of the emergency services easier, so that they can respond more quickly and efficiently to emergency situations and ultimately offer citizens a better service.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/CPMH8W/resources/A_modern_OS_information_system_for_the_french_fi_lnry6hg.odp">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/CPMH8W/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/CPMH8W/feedback/</feedback_url>
            </event>
            <event guid='16166696-cd7d-58c7-84b0-88bebf968b4d' id='39391' code='PWXM7V'>
                <room>Stage Auditorium</room>
                <title>Success through a thousand emails: Fundraising and outreach</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T16:05:00+01:00</date>
                <start>16:05</start>
                <duration>00:30</duration>
                <abstract>How to fund for medium to large goals before you have community buy-in? Tens of thousands of dollars do not drop from the sky and sometimes when you need it most, the &quot;no&quot;s hit harder. We&apos;ll cover wins, losses and amazing teams who have won fundraising goals through thousands of small moves.</abstract>
                <slug>fossback24-39391-success-through-a-thousand-emails-fundraising-and-outreach</slug>
                <track>Sustainability &amp; Funding</track>
                <logo>/media/fossback24/submissions/PWXM7V/Share_v2-4_Sustainabilty_1_8HXuGFQ.png</logo>
                <persons>
                    <person id='43320'>Dawn Wages</person>
                </persons>
                <language>en</language>
                <description>All of the most successful fundraising campaigns come from three categories: services rendered, shared identity, or urgency; and are driven by thousands of small actions and follow up to create opportunities clarity and collaboration. Getting the right people to care is a beheamoth task. Large corporations that are expected to write a check and fill the gap of a worthwhile initiative don&apos;t show up like we expect; why does money never seem to flow to the right place at the right time?

Through this presentation I&apos;ll discuss ways grassroots campaigns strike a cord  with their audience to get over the fundraising finish line with some common gotchas: 
- The audience you thought would care, doesn&apos;t. 
- Who has the bank account?
- How much is a handshake worth?
- Getting Western donations to African initiatives.
- Reduce the &quot;I&apos;m going to get yelled at&quot; factor when asking corporations for contributions. 
- Creating the next wave of financially and fiscally aware in Open Source.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/PWXM7V/resources/FOSS_Backstage_SUCCESS_THROUGH_A_THOUSAND_EMAILS_HISGHQi.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/PWXM7V/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/PWXM7V/feedback/</feedback_url>
            </event>
            <event guid='80947edb-b868-5e31-9330-762d071e119e' id='39211' code='UCPFAJ'>
                <room>Stage Auditorium</room>
                <title>Aligning wishes of multiple orgs into an open source project</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T16:40:00+01:00</date>
                <start>16:40</start>
                <duration>00:30</duration>
                <abstract>Having a roadmap as an open source project can encourage adaption and align contributors. However roadmaps require commitment from its participants - how do you do this as open source project with contributions coming from multiple organizations? Join this session to learn how one could solve this.</abstract>
                <slug>fossback24-39211-aligning-wishes-of-multiple-orgs-into-an-open-source-project</slug>
                <track>Sustainability &amp; Funding</track>
                <logo>/media/fossback24/submissions/UCPFAJ/Share_v2-4_Sustainabilty_4_PL6pIxR.png</logo>
                <persons>
                    <person id='43140'>Thomas Steenbergen</person><person id='43138'>Nick Vidal</person>
                </persons>
                <language>en</language>
                <description>Having a public and up-to-date roadmap for an open source project can encourage new contributors to join a project, guide the efforts of existing contributors, and give confidence to adopters about the direction and sustainability of the project. 

However for a roadmap to work you need commitment from its participants. In a company, management can commit to a product roadmaps top-down but you can&apos;t do that in an open source project with various organizations contributing. Nick and Thomas are working on a solution in two of their open source projects (ClearlyDefined &amp; OSS Review Toolkit) to try to solve this commitment challenge.

Multiple organizations and individuals are working together in the ClearlyDefined and ORT, the call for a public roadmap became stronger. For example, people want to know when improvement requests relevant to their organization will be implemented. Whether something gets implemented and when, depends on the priorities of the people making and reviewing the contributions. In most open source projects small requests can often be quickly addressed but bigger changes usually require a commitment from people&#8217;s employers. This was where ClearlyDefined and ORT - like other open source projects - ran into a demand and supply mismatch: each organization has their own wishes, priorities and resources towards the projects, but every big change requires the involvement of the project maintainers who are either volunteering their time or need to get time from their organization to be involved.

In this session Nick and Thomas will present an innovative governance and funding model created by the ORT community to align demand and supply between organizations so they can agree to implement items together resulting in a roadmap with committed delivery items.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/UCPFAJ/resources/Aligning_wishes_of_multiple_orgs_into_an_open_so_gIRhL6R.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/UCPFAJ/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/UCPFAJ/feedback/</feedback_url>
            </event>
            <event guid='c5f662e8-19f0-5597-ba98-e770e1a68787' id='43353' code='8CR8UG'>
                <room>Stage Auditorium</room>
                <title>Closing Session</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2024-03-05T17:10:00+01:00</date>
                <start>17:10</start>
                <duration>00:15</duration>
                <abstract></abstract>
                <slug>fossback24-43353-closing-session</slug>
                <track></track>
                
                <persons>
                    
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/8CR8UG/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/8CR8UG/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Stage Wintergarten' guid='31282bc0-32b3-5ca2-ae3d-a9f2bbf987cf'>
            <event guid='c48f8f30-5375-562b-a7db-6e3246d9c78c' id='39088' code='AMDURF'>
                <room>Stage Wintergarten</room>
                <title>Adventures with Open Source Business Models</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>00:30</duration>
                <abstract>I spent 20 years on an adventure running an open source business. This session will cover open source business models and especially the ones that work. If you have ever thought about doing FOSS as a full time business, come hear what I&apos;ve learned.</abstract>
                <slug>fossback24-39088-adventures-with-open-source-business-models</slug>
                <track>Sustainability &amp; Funding</track>
                <logo>/media/fossback24/submissions/AMDURF/Share_v2-4_Sustainabilty_6_J9VAGZq.png</logo>
                <persons>
                    <person id='43013'>Tarus Balog</person>
                </persons>
                <language>en</language>
                <description>I became involved in open source full time in 2001 when I joined the company behind OpenNMS, an open source network monitoring platform. In 2002 I became the primary maintainer when that company decided to stop supporting the project. Becoming the maintainer was easier than explaining to my wife that I was quitting my job to sell free software.

I was able to grow the company up until 2019 when we sold it, and I stayed with the acquiring company until 2021. Our customers were some of the biggest companies in the world, and we explored every possible way to make money while keeping the product 100% free and open source software.

In this session I will talk about how we got started, what worked and what didn&apos;t, and what I would do differently if I had to do it all again.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/AMDURF/resources/2024_FOSS_Backstage_Open_Source_Business_Models_EcIIH8D.pdf">FOSS Backstage Presentation</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/AMDURF/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/AMDURF/feedback/</feedback_url>
            </event>
            <event guid='36b73888-0d2d-5fe6-917a-4790e573726e' id='39154' code='WTPUCL'>
                <room>Stage Wintergarten</room>
                <title>More than developers: growing your maintainer community</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T11:35:00+01:00</date>
                <start>11:35</start>
                <duration>00:30</duration>
                <abstract>As projects grow, they need roles like QA, docs, and more&#8230; but most full time contributors are devs. What should we do?! This talk is about strategy: how to incentivize non-developers to contribute, how for-profit companies can support open source, and what projects need upstream communities.</abstract>
                <slug>fossback24-39154-more-than-developers-growing-your-maintainer-community</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/WTPUCL/Share_v2-1_Governance_14_232455b.png</logo>
                <persons>
                    <person id='43086'>Celeste Horgan</person>
                </persons>
                <language>en</language>
                <description>A consistent question across all open source projects is how to grow their maintainer communities. More specifically, as projects grow they move from needing generalists to looking for  specialized roles, like documentation, community management, and security. It can be challenging to shift from bootstrapping a project to growing a community because these roles require different skillsets and outlooks, and it can be hard to shift your mindset and figure out how to accommodate diverse kinds of contributors. 

In this talk we&#8217;ll learn the importance of growing your community in a balanced way that includes roles beyond developers, and how to attract and retain those contributors. 

In this talk we&#8217;ll go over:
From 5 to 500: the challenges a project faces as it goes from a small team of developers to a diverse set of contributors
The different ways to open source something (through a foundation, sponsored by a company, all on your own) and what that means for your growing contributor base
How to keep new contributors and grow them into project leadership
The importance of defining and documenting specific roles in your open source project
Smoothing the path for non-code contributors to open source

This talk will benefit maintainers and community owners who manage open source projects in large companies in specific, as it focuses on business-led opportunities for maintainer growth. At the end of this talk you&#8217;ll have the hints on how to manage the growing pains for your open source project community, recruit new contributors and keep them. We&#8217;ll give you examples from successful open source projects that you can emulate and use in your own growth.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/WTPUCL/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/WTPUCL/feedback/</feedback_url>
            </event>
            <event guid='407e6972-4ba2-595e-a813-c3eb68d2a20f' id='38287' code='G9CAHP'>
                <room>Stage Wintergarten</room>
                <title>Measuring the Impact of Community Events</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T12:10:00+01:00</date>
                <start>12:10</start>
                <duration>00:30</duration>
                <abstract>For commercial organizations and community projects, what&apos;s the return on investment in running a booth or giving talks at such events? In this presentation, Brian Proffitt outlines the challenges of figuring out the ROI of community event participation.</abstract>
                <slug>fossback24-38287-measuring-the-impact-of-community-events</slug>
                <track>Growing Open Source</track>
                <logo>/media/fossback24/submissions/G9CAHP/Share_v2-3_Growing_1_AIPFaas.png</logo>
                <persons>
                    <person id='42261'>Brian Proffitt</person>
                </persons>
                <language>en</language>
                <description>One of the mainstays of the open source ecosystem are community events. Open Source Summit, Community Over Code, SCaLE... all examples of community events with vitality and influence within open source. But unlike more commercially focused events, community events are not as simple to measure in terms of benefits to organizations that participate. Without sales leads or conversions, how does a commercial organization measure the gains of participation? And for community projects, what&apos;s the return on investment in running a booth or giving talks at such events? In this presentation, Brian Proffitt outlines the challenges of figuring out the ROI of community event participation, and then will offer multiple potential solutions Red Hat has been experimenting with to measure impact and gains. These solutions will include:

* Collateral delivery
* Messaging impact
* Calls to action

Brian will also discuss measuring the health, ROI, and strategic fit for events, in order for organizations to determine which event will have the best impact for an organization&apos;s primary mission.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/G9CAHP/resources/Proffitt_Measuring_the_Impact_of_Community_Event_nEaxO8O.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/G9CAHP/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/G9CAHP/feedback/</feedback_url>
            </event>
            <event guid='a23d7906-55a0-5a5a-8523-e36a6ad41a87' id='39193' code='WNHFDT'>
                <room>Stage Wintergarten</room>
                <title>Who Funds FOSS Foundations?</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T14:00:00+01:00</date>
                <start>14:00</start>
                <duration>00:30</duration>
                <abstract>FOSS foundations provide a wide variety of critical project support services.  But how do these foundations get funded themselves?</abstract>
                <slug>fossback24-39193-who-funds-foss-foundations</slug>
                <track>Sustainability &amp; Funding</track>
                <logo>/media/fossback24/submissions/WNHFDT/Share_v2-4_Sustainabilty_5_70AQplL.png</logo>
                <persons>
                    <person id='43119'>Shane Curcuru</person>
                </persons>
                <language>en</language>
                <description>Have you ever wondered how open source organizations get funded? Not just the developers, but the whole ecosystem around major open source projects, either at a FOSS Foundation, independent projects, or an open core project at a company? 

Most major software projects we all rely on are hosted at Foundations like Apache, Eclipse, Linux, or Software Freedom Conservancy. Those foundations provide a wide variety of support to project communities, including legal and licensing assistance, trademark management, event support, and more. As non-profits, these foundations rely on donors and sponsors for all of their work. So who funds all of this critical support for open source foundations? 

Come find out what companies are behind the popular open source foundations and major independent projects, and who&apos;s actually paying for all of the other support work that&apos;s done to keep the servers running, press releases coming, and license compliance work. Surprises are guaranteed; I know I was surprised when I realized how many different FOSS projects that Microsoft is an annual sponsor for, what projects a few other companies supported with their cash, and how big one foundation has gotten.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/WNHFDT/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/WNHFDT/feedback/</feedback_url>
            </event>
            <event guid='f807d290-3728-5bab-940e-0fcd673d397e' id='39251' code='LYCLBX'>
                <room>Stage Wintergarten</room>
                <title>Size matters: Why some projects can&apos;t do UX well</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T14:35:00+01:00</date>
                <start>14:35</start>
                <duration>00:30</duration>
                <abstract>There are lots of people that critique the UX of open source. Some of it is warranted but what can we DO about it? This talk will discuss which repos do UX well and what we can all learn from them.</abstract>
                <slug>fossback24-39251-size-matters-why-some-projects-can-t-do-ux-well</slug>
                <track>Growing Open Source</track>
                <logo>/media/fossback24/submissions/LYCLBX/Share_v2-3_Growing_7_ZENodpA.png</logo>
                <persons>
                    <person id='43180'>Scott Jenson</person>
                </persons>
                <language>en</language>
                <description>There are strong opinions about UX and how it should fit in open source but what&apos;s clear is that one size does not fit all. How you can do proper UX (if at all) depends on the size and shape of your group. After interviewing many different repo maintainers, there is a clear pattern about which projects are better at doing UX. This talk will explain what I&apos;ve found and how projects of any size can still incorporate UX into their process flow.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links>
                    <link href="https://docs.google.com/presentation/d/15mB9Va5NSzeUcOXxNGydpsV_Q9ZUE6IdvZHIUJcWKYg/edit?usp=sharing">Slides</link>
                </links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/LYCLBX/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/LYCLBX/feedback/</feedback_url>
            </event>
            <event guid='efb7ba12-6582-5f82-9aa2-b82c43609686' id='38415' code='YCKULE'>
                <room>Stage Wintergarten</room>
                <title>Why UX and FOSS clash and what we can do about it</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T15:30:00+01:00</date>
                <start>15:30</start>
                <duration>00:30</duration>
                <abstract>Open source programs have often been seen as hard to use. UX Designers are professionals who try to make things easier to use &#8211; that seems to be a great match! However, practices and values of both cultures often clash, and I describe why.</abstract>
                <slug>fossback24-38415-why-ux-and-foss-clash-and-what-we-can-do-about-it</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/YCKULE/Share_v2-1_Governance_8_wxzkMym.png</logo>
                <persons>
                    <person id='42395'>Jan Dittrich</person>
                </persons>
                <language>en</language>
                <description>This talk focusses on a central difference between UX designers and Open Source developers: The ideas of what a &quot;good&quot; user is and one should relate to them. Given their different cultures and histories, both have come to different conclusions: The ideal user for open source projects is a programmer themselves and thus similar to the people already working on the software &#8211; whereas for UX designers, the users are seen as unlike designers nor programmers and understanding them and transporting that understanding in the project is seen as a major and difficult task.
Based on these differences, the suggestion is not to educate one profession to act like the other. Instead, I look at existing modes of cross-professional collaboration assuming that the strenght of working together are also the very different skills and assumptions that designers and developers bring to the project.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/YCKULE/resources/Dittrich_UX-FOSS-Conflicts_KQ6Vjzt.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/YCKULE/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/YCKULE/feedback/</feedback_url>
            </event>
            <event guid='545a26e3-4c28-51e5-a6ae-3d11ebe86714' id='39346' code='HGJAQP'>
                <room>Stage Wintergarten</room>
                <title>A UX Toolbox for Usability, Accessibility, and Security</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T16:05:00+01:00</date>
                <start>16:05</start>
                <duration>00:30</duration>
                <abstract>How do we move usability beyond a set of heuristics, towards a holistic approach that mitigates risk within human-centered tool design? This talk will explore our User Experience Toolbox, a set of resources that aims to bridge accessibility, usability, and security as core principles.</abstract>
                <slug>fossback24-39346-a-ux-toolbox-for-usability-accessibility-and-security</slug>
                <track>Security</track>
                <logo>/media/fossback24/submissions/HGJAQP/Share_v2-2_Security_nc18Oy8.png</logo>
                <persons>
                    <person id='43271'>Katie Wilson</person>
                </persons>
                <language>en</language>
                <description>In today&#8217;s landscape of increasingly riskier digital experiences, successful software development requires more than just functionality and aesthetics. The challenges faced by software teams require prioritizing user experiences while carefully addressing potential harms and respecting human rights. While traditional technical security audits serve a valuable purpose, they do not typically focus on the socio-technical aspects of a tool that make systems insecure, like its usability. Similarly, accessibility practices and audits often happen in addition to, not in concert with, usable security reviews, and sometimes they don&#8217;t happen at all. As UX practitioners, we&#8217;ve learned that there is interplay, overlap, and synergistic benefits between each of these aspects, and developed our open UX Toolbox for Risk Mitigation and Accessibility to provide tool teams, designers, and product managers with an adaptable set of resources that help them work holistically toward secure, usable, and accessible user experiences. This talk will explore the research and landscape analysis that led to the development of the toolbox, discuss use cases for some of the open resources included, and seek community feedback to help improve it collaboratively.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/HGJAQP/resources/A_UX_Toolbox_for_Usability_Accessibility_and_Sec_ZFTtvEy.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/HGJAQP/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/HGJAQP/feedback/</feedback_url>
            </event>
            <event guid='821223af-3ca3-58d5-8191-9ce27028bc35' id='38413' code='LQSRZN'>
                <room>Stage Wintergarten</room>
                <title>The secret lives of designers in OSS</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T16:40:00+01:00</date>
                <start>16:40</start>
                <duration>00:30</duration>
                <abstract>Superbloom has published a findings document/report from our 16 week diary study about how designers contribute to OSS. You&apos;ll learn what designers contributing to OSS&apos;s lives are like day to day as they contribute all types of design - from visual UI, graphics and user research and accessibility.</abstract>
                <slug>fossback24-38413-the-secret-lives-of-designers-in-oss</slug>
                <track>Diversity &amp; Inclusion</track>
                <logo>/media/fossback24/submissions/LQSRZN/Share_v2-5_Diversity_1_kvzoH94.png</logo>
                <persons>
                    <person id='42393'>Eriol Fox</person><person id='43294'>Nimisha Vijay</person>
                </persons>
                <language>en</language>
                <description>We will cover the main topics that we found were important for designers in OSS and OSS from the diary studies. These include:
- How designers decide to contribute to OSS
- Communication and collaboration with developers
- How designers measure design success in OSS
- Processes and tools used by designers in OSS
- What states designers would like to leave OSS in after they finish contributing

Along with this data we&apos;ll present Superbloom&apos;s recommendations on how to address the challenges raised by our diary study in OSS

We&apos;ll also outline and offer up how we structured this study and our future hopes for research into design in OSS.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/LQSRZN/resources/Designers_in_OSS_diary_studies_-_20_min_-_FOSS_B_I5SgXE5.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/LQSRZN/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/LQSRZN/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Monday: Workshop Room /  Tuesday: Remote Stage' guid='8c8a6b23-136b-5808-b2c2-7892f91b8a9d'>
            <event guid='9969b2de-3d61-59ec-8d4e-9aa0950277d1' id='39222' code='X8KZGM'>
                <room>Monday: Workshop Room /  Tuesday: Remote Stage</room>
                <title>Open Source Inclusivity: Empowering Newcomers</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>00:30</duration>
                <abstract>Explore effective methods to lower the entry barriers for newcomers in open source. This talk addresses the challenges new contributors face, offering practical solutions to foster inclusivity and encourage diverse participation in open source projects.</abstract>
                <slug>fossback24-39222-open-source-inclusivity-empowering-newcomers</slug>
                <track>Diversity &amp; Inclusion</track>
                <logo>/media/fossback24/submissions/X8KZGM/Share_v2-5_Diversity_3_3r7JASV.png</logo>
                <persons>
                    <person id='43147'>Mayank Jindal</person>
                </persons>
                <language>en</language>
                <description>In the realm of open source development, the influx of new contributors is vital for innovation and progress. However, first-time contributors often find themselves at a crossroads, daunted by vast codebases and extensive issue lists. This talk aims to dissect and address these barriers.

We will delve into the psychological and technical hurdles that new contributors face, such as selecting the right issue to tackle and overcoming the intimidation of large-scale projects. By examining case studies and current practices, the talk will reveal how these barriers not only deter individual learning and growth but also deprive organizations of potential talent.

Furthermore, the session will introduce actionable strategies that projects can implement to make their environments more welcoming and accessible. These include structured mentorship programs, clear documentation, beginner-friendly issue tagging, and inclusive community practices. The talk will also highlight the importance of fostering a culture that values diversity and inclusivity, ensuring that open source is a field where all voices, regardless of experience level, are heard and valued.

Attendees will leave with a comprehensive understanding of the challenges faced by new open source contributors and a toolkit of strategies to implement in their projects or communities. This talk is particularly relevant for project maintainers, community managers, and anyone interested in enhancing the diversity and inclusivity of open source projects.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/X8KZGM/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/X8KZGM/feedback/</feedback_url>
            </event>
            <event guid='3cf03370-6af4-545f-940e-3978d6849a1a' id='38271' code='9CZALK'>
                <room>Monday: Workshop Room /  Tuesday: Remote Stage</room>
                <title>Navigating the gold rush: Of influencer economies and FOSS</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T11:35:00+01:00</date>
                <start>11:35</start>
                <duration>00:30</duration>
                <abstract>With FOSS outreach increasingly being dependent on tech influencers, mass adoption and contribution is no longer a pipe dream! But are these fantastic numbers actually a cry for help? Buckle up as we look at some cold hard facts about the FOSS ecosystem in times of the influencer economy.</abstract>
                <slug>fossback24-38271-navigating-the-gold-rush-of-influencer-economies-and-foss</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/9CZALK/Share_v2-1_Governance_7_xOrGC7p.png</logo>
                <persons>
                    <person id='42248'>Divya Mohan</person>
                </persons>
                <language>en</language>
                <description>Raise your hands if you, as a maintainer, have been traumatised by the influx of spam PRs during Hacktoberfest every year. With trends like &quot;Learning in public&quot;, &quot;What prevents you from contributing like this?&quot;, and &quot;Every typo edit matters&quot;, the last few years have witnessed open source contributions soar in popularity like never before. While this messaging was initially helpful to attract more contributors by promising them better visibility &amp; career opportunities, its eventual virality across platforms on account of promotions by tech influencers and contributors alike has resulted in a slow spiral toward unsustainability.  Not only has the ecosystem become a hot bed for such clickbait messaging, various organizations and projects continue to enable this shifting of balance with their outreach &amp; messaging strategies.

This isn&#8217;t meant to be a critique of the influencer economy or its adoption by the open source ecosystem. However, with issues like maintainer burnout, lesser promotions across the contributor ladder, deteriorating project health, and terrible work-life balance staring back at us, it is essential that we talk about the elephant in the room - how do we navigate past this wreck to sustainably scaling open source communities? How do we fix forward so as to handover a healthy contributor ecosystem to the next generation of maintainers? Can the ecosystem and the influencer economy co-exist sustainably?

This talk aims to cover the above topics broadly with suggestions and anecdotes drawn from the speaker&apos;s experience as a documentation maintainer, open source DevRel, and contributor to several open source projects.

While it is impossible to solve this problem with one talk alone, the speaker hopes to set the ball rolling on this discussion with this session.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/9CZALK/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/9CZALK/feedback/</feedback_url>
            </event>
            <event guid='d1772935-267f-5fa1-a6b8-509049807b08' id='38323' code='7S9WGD'>
                <room>Monday: Workshop Room /  Tuesday: Remote Stage</room>
                <title>Docs For All: Improving Open Source Accessibility</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T12:10:00+01:00</date>
                <start>12:10</start>
                <duration>00:30</duration>
                <abstract>Users first is something the open source world and technical documentation have in common. In this talk, we&#8217;ll explore the intersection of inclusivity in technical documentation and how these factors enhance accessibility in open source, which in turn creates sustainable and inclusive communities.</abstract>
                <slug>fossback24-38323-docs-for-all-improving-open-source-accessibility</slug>
                <track>Diversity &amp; Inclusion</track>
                <logo>/media/fossback24/submissions/7S9WGD/Share_v2-5_Diversity_4_70mKlmu.png</logo>
                <persons>
                    <person id='42312'>Zainab Daodu</person><person id='42579'>Omotola Eunice OMOTAYO</person>
                </persons>
                <language>en</language>
                <description>In a world that&#8217;s increasingly diverse and championed by technology and development, ensuring that the tools users need serve their diversity is paramount. This is why factors like accessibility, diversity, and inclusion within technical documentation need more amplification. 
 
This session unfolds the pivotal role of crafting technical documentation that speaks to a broad audience, ensuring that open-source projects are not just universally accessible but also resonate with a diverse global user base. 
Examine the art of creating comprehensive documentation that caters to various demographics while being accessible by incorporating assistive technologies like screen readers, subtitles, etc. 
We navigate through the intricate web of creating documentation that is not just a guide but a gateway to making technology inclusive, ensuring no one is left behind in the use of important technological advancements. Join us as we embark on a journey from understanding to implementing strategies that boost accessibility through technical documentation in the open-source space, fostering a community that is sustainable, inclusive, and universal.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/7S9WGD/resources/Docs_For_All_Improving_Open_Source_Accessibility_xM1KTJn.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/7S9WGD/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/7S9WGD/feedback/</feedback_url>
            </event>
            <event guid='7792cb41-4896-57d0-b5cf-25ac30c81096' id='38788' code='XPQNQN'>
                <room>Monday: Workshop Room /  Tuesday: Remote Stage</room>
                <title>What being a Biker Gang Investigator taught me about FOSS</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2024-03-05T14:00:00+01:00</date>
                <start>14:00</start>
                <duration>00:30</duration>
                <abstract>Ah, the Open Road. Almost as good as Open Code! Before getting to know Open Source, I worked as a Biker Gang investigator in Canada, and while it may not seem like it at first blush, everything you need to know about working with and in open source communities can be learned from outlaw bikers!</abstract>
                <slug>fossback24-38788-what-being-a-biker-gang-investigator-taught-me-about-foss</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/XPQNQN/Share_v2-1_Governance_5_NMMzTKW.png</logo>
                <persons>
                    <person id='42712'>Ashley Sametz</person>
                </persons>
                <language>en</language>
                <description>My talk will go into the nuances of participating in open source, and how there are unwritten rules within the community which n00bs (or &quot;hangarounds&quot; as we might want to call them...) may not know right away.  As with any community, the reasons for joining can vary from person to person, but with both OMG&apos;s and OG coders, there are a lot of shared ideologies. The notions of  shared brother/sister/personhood are of course, one of the biggest reasons. We all like being a part of something that is bigger than ourselves, and a sense of contributing to the greater good and looking out for &quot;the little guy&quot; (aka: not MS) is a common thread in both groups.  In partnership with this is the need or desire for Freedom - where can we go that others haven&apos;t gone? How can we be more nimble? How can we make this bike (or process) go faster? And possibly greatest of all - the thrill! Whether it be customizing a sweet ride, or a piece of code, there isn&apos;t a lot more exhilarating than seeing all the pieces come together!
Of course, there are other things - like codes of conduct, patches (on your leather OR in your latest release...) and meet-ups - but ultimately, this is a talk about how folks who are not always understood by others have built an astounding community of people that is far more than meets the eye!</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/XPQNQN/resources/Biker_gangs_and_Open_Source_V2.0_YEn3KK8.pptx">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/XPQNQN/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/XPQNQN/feedback/</feedback_url>
            </event>
            <event guid='7bad5cdf-cf41-514d-b2e0-aa85c041d632' id='39215' code='N3VMFY'>
                <room>Monday: Workshop Room /  Tuesday: Remote Stage</room>
                <title>Exploring the Intersection Between OSS and Exit to Community</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2024-03-05T15:30:00+01:00</date>
                <start>15:30</start>
                <duration>01:00</duration>
                <abstract>A speculative organizational-design workshop where participants will discover how the framework of Exit to Community can enable open-source projects to adopt more appropriate governance processes across a variety of software projects.</abstract>
                <slug>fossback24-39215-exploring-the-intersection-between-oss-and-exit-to-community</slug>
                <track>Governance &amp; Community</track>
                <logo>/media/fossback24/submissions/N3VMFY/Share_v2-1_Governance_1_MIMAPpg.png</logo>
                <persons>
                    <person id='43141'>Adina Glickstein</person><person id='46719'>Eli Zeger</person><person id='46720'>Hazel Devjani</person>
                </persons>
                <language>en</language>
                <description>This workshop intends to help FOSS contributors and enthusiasts learn about Exit to Community (E2C), an economic justice strategy that empowers players in the digital economy to move towards ownership and governance by the users, workers, and other stakeholders who give platforms their value, ensuring long-term sustainability and benefits for all. 
In this workshop, we&#8217;ll briefly introduce the notion of &#8220;Exit to Community&#8221; and explore how it resonates with the values of the free software movement. We will overview 3 case study &#8220;snapshots&#8221; that embody the values and practices of Exit to Community in the software world: Debian, Python, and BuyTwitter.org. (While the former two exemplify E2C&#8217;s resonance with open-source values, the latter imagines turning a proprietary platform into a public utility, demonstrating the imaginative potential unlocked by thinking between E2C and FOSS.) In approximately 5 minutes, each overview will map out 1) motivation to pursue community ownership/governance and 2) the practical path to achieving it. We will then guide participants through the design of a speculative Community Exit Strategy for a tech platform or utility that matters to them. This could be a FOSS project they are involved with as a contributor or user, or a proprietary platform that they fantasize about bringing into alignment with open-source values by taking it under collective ownership. 
Whether participants choose to plot a new governance strategy for an existing FOSS project based on our case studies or speculatively re-envision a proprietary platform as an open-source project, we hope this workshop will catalyze conversations about the many forms community ownership of software can take, clarifying the idea of Exit to Community and building awareness of what it entails. By refining our collective understanding of how community ownership functions in practice, we&#8217;ll aim to define some lessons that can be applied to the organizational design of successful open-source software projects.

&#128712; This workshop won&apos;t be recorded, participation is possible both online and onsite.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://program.foss-backstage.de/media/fossback24/submissions/N3VMFY/resources/Adina_Glickstein_Exploring_the_intersection_E2C__9HNmxCC.pdf">Slides</attachment>
                </attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/N3VMFY/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/N3VMFY/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Lobby' guid='c3579769-2cd5-5a07-9eeb-abeaabe157b5'>
            <event guid='3294613b-f4e3-5d45-a321-846a4b7126c8' id='38813' code='HWYSUB'>
                <room>Lobby</room>
                <title>Usability Clinic &#128712;</title>
                <subtitle></subtitle>
                <type>Off Stage</type>
                <date>2024-03-05T14:35:00+01:00</date>
                <start>14:35</start>
                <duration>02:00</duration>
                <abstract>Are you an open source maintainer? We provide free (as in free beer) design support for your project, including UI, UX and User Research. Talk to us in person and receive pro-bono design support at the event and after!</abstract>
                <slug>fossback24-38813-usability-clinic</slug>
                <track>Growing Open Source</track>
                <logo>/media/fossback24/submissions/HWYSUB/Share_v2-3_Growing_4_Cr6QBsF.png</logo>
                <persons>
                    <person id='42728'>Elio Qoshi</person><person id='42799'>Marit Brademann</person>
                </persons>
                <language>en</language>
                <description>Are you an open source maintainer? We provide free (as in free beer) design support for your project, including UI, UX and User Research. Talk to us in person and receive pro-bono design support at the event and after!

What we can help with:

Discovering:
At the start of the project we can help explore with you the problem space and find potential pathways to help you ask the right questions. This can include understanding your audience, designing for the right audience or figuring out potential user journeys for new features.

Refactoring:
You have a technically working solution but need some support with tidying up, regardless if it&#8217;s information architecture or layout. We can support you with some design housekeeping without relying on major design changes.

Auditing:
You have a working solution and need to test and audit it for potential shortcomings. We do conduct UX heuristics evaluations as well as accessibility audits (web, mobile or desktop).

Refreshing:
Communicating technical feasibility as part of a visual identity can prove to be difficult. We work with you to ensure your project can communicate its values efficiently.

Implementing:
We specialize in supporting to shape your product with frontend implementation, accessibility considerations, as well quality assurance.


More information: https://ura.design/probono

&#128712; This session won&apos;t be recorded and participation is only possible onsite.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://program.foss-backstage.de/fossback24/talk/HWYSUB/</url>
                <feedback_url>https://program.foss-backstage.de/fossback24/talk/HWYSUB/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    
</schedule>
