Flock to Fedora 2025
Join us for an optional walking tour of Prague! Sign up is essential as space is limited https://www.lucytours.com/
Estimated start time: To be confirmed with vendor
Meeting point: To be confirmed with vendor
Welcome to Flock to Fedora!
Placeholder for FPL(s) talk as part of extended opening remarks
As during every Flock, we'll hold a session with FESCo members to introduce themselves and say a few words about our plans for the next year. The majority of time will be spent on questions from the audience.
Forgejo is a self-hosted software forge, including Git hosting, basic project management features and CI/CD integrations. Fedora announced to move to Forgejo in 2024 and we are looking forward to collaborate with the Fedora community.
In this talk, we want to take a look at the powerful features of Forgejo, compare it to the tools you might know already (Pagure, GitHub, GitLab) and tell you a few tips and tricks. We are sure you'll have fun developing with Forgejo after watching this talk.
Among other, we are going to introduce you to the concept of collaborating on software using AGit. Contrary to the workflow made popular by GitHub, this saves the need to create forks before collaborating on a change, and we believe that this is a more modern contribution workflow.
Last but not least, we'll try to provide a little peek at things that we have high on our roadmap and you will be able to enjoy soon.
I am a blind software engineer, using various Linux distributions for more than 13 years.
Accessibility of Linux distributions is constantly improving, but overall experience is still not comparable to other major operating systems, especially for newcomers.
In this talk, I would like to give you a brief introduction to problematics of Linux desktop accessibility focused on blind users. Then, I would like to talk more about Vojtux, a future Fedora remix which I am gradually developing as a side project at Red Hat.
So what can you expect to see and hear?
- how does it feel when you introduce a blind Windows user to Fedora?
- What makes a blind computer use really angry?
- Do you need to be an accessibility expert to make accessible applications?
- and more...
Mentorship has always been a big part of what makes Fedora special. This year, we’re adding something new to the Fedora Mentor Summit: a casual lunch matching session where mentors and mentees can meet face-to-face, share stories, swap ideas, and connect over common goals.
Here’s how it works:
We’ve already paired folks based on the Fedora Discussion thread.
If you didn’t sign up ahead of time - no worries! Stop by and we’ll find you a spot based on the groups we’ve already put together.
Need a conversation starter? We’ll have a few prompts ready to help break the ice.
Take a group selfie during lunch and you’ll earn a Fedora Badge as a fun keepsake. 🐧
No formal structure - just good food and good conversation with someone else who cares about growing the Fedora community.
Fedora documentation has felt like a bit of a problem area for years. While we do have a respectable set of docs, its organization is lacking, and there are plenty of gaps, especially in documentation aimed at end-users. The project also struggles to find recurring contributors. The overall project situation has improved significantly in recent years, compared to a low point around 2020-2021, but there is still much to do.
This talk will discuss the current state of the Fedora Docs Project and its development over the past several years, identify common hurdles and issues that keep potential contributors away, present a user survey of Fedora Docs (scheduled for April), and outline next steps that we plan to take to both get more people involved and make contributing easier, as well as to improve and expand the existing documentation set: automation, streamlining the git workflow, and so on.
The yearly State of EPEL talk. Troy Dawson (EPEL Steering Committee chair) and Carl George (Red Hat EPEL team lead) will present what EPEL and its community have done in the past year, and what we are planning for the future.
We are the developers of Log Detective, a project that can explain failed build logs using Large Language Models. In this presentation, we will not only cover technical details of how it works, but also showcase its architecture, perform a demonstration, and answer your questions.
Log Detective service lives in Fedora infrastructure - we are very grateful for this funding and wouldn’t be able to get this far in the project. Let us share our achievements and struggles. We are open to collaborate with others and plug Log Detective into other Fedora infrastructure services.
After attending Flock 2024 in Rochester, I was inspired to contribute more to the Linux kernel. As an aspiring kernel developer, I decided to start by exploring the Fedora Kernel bug tracker. I quickly realized it contained many valuable reports—some highlighting Fedora-specific issues, but others uncovering real upstream bugs that had gone unnoticed.
In this talk, I’ll share real-world examples where the Fedora Kernel played a crucial role in identifying and fixing upstream Linux kernel issues that weren’t being addressed. I’ll also discuss how others can get involved, particularly in tackling hardware and driver-related problems.
Give and updated overview of what we are tracking for the Software Ecosystem readiness across the various Linux Distributions. This will include and update on which HW boards we have been working on and what the current status of enablement is.
to be added
Fedora packagers have to upload upstream sources prior to build. They are supposed to validate the content they build in Fedora prior to submitting it. However, many projects have dependencies on others, to the point that sometimes hundreds of small packages are bundled together. This makes it challenging for packagers to handle updates when projects written in JavaScript, Rust, Go, Java or similar languages where the ecosystem is built around small and interdependent components. An attack on a chained dependency might go far unnoticed.
The Fedora Project had for a long time struggled with packaging of these components. While it is hard to solve the packaging problem without increasing effort, there are still ways to help Fedora packagers in their job. This talk will look into an experiment FreeIPA team ran together with Red Hat Engineering's Core Platform Management group on helping to prevent malware from getting to Fedora.
This session will be on AMD's ROCm(tm) platform for GPU-accelerated computing. It will cover brief introduction to the ROCm platform, the state of Fedora's ROCm packages, answers to some common questions like "will my GPU work with ROCm?" and a bit of insight into AMD efforts to improve the "out of box" experience for ROCm users in Linux distros like Fedora.
Fedora CoreOS has consistently grown over the past five years, eventually becoming a top level edition and now competing with the Server and Cloud editions for most active node count on any given week. This, however, is just the beginning. Operating system and container technology continue to evolve at a breakneck pace and Fedora CoreOS sits nicely at the intersection of this evolution; providing a nice stable ride along the way.
In this session we'll discuss what is next for Fedora CoreOS; our goals for the project and the community, and how we can achieve those goals through coordinated technical and non-technical efforts. Topics will include fedora-bootc, configuration management, systemd sysexts, Kubernetes, and RISC-V.
Given how expansive the Fedora Project community is—with its subprojects and SIGs—many newcomers struggle to find an area to contribute.
The Join SIG was set up several years ago to help newcomers gain a foothold and become part of Fedora. Over the years, we've tried many methods to increase our retention rates. Most recently, we've used a people-centric "Welcome to Fedora" process.
Our main goal has been to try to help newcomers get to know the people of Fedora by easing them into a friendly space before having them jump into tickets or tasks.
We think that we can retain more people with Fedora-wide co-operation. We hope that you will agree that everyone in the Fedora community has a role to play with the Welcome Wagon.
In this talk, we will start a conversation about how we can better retain the many new friends who come to Fedora through Join SIG.
To prepare for the talk, you may wish to peruse https://pagure.io/fedora-join/WelcomeToFedora
Fedora has been using DIscourse for some while, but it has many clever little features that people are often unaware of. In this session, we'll go over some many of these, and go over any challenges people may be having with Discourse as well.
As a nearly 10-year user of Discourse (I started using it in 2016, and became an admin for the first time in 2017) I've learned a lot about what is possible with the platform, as well as having some insights as to what it does well for the moderators and admins as well as the day-to-day users. Ask me anything on Discourse, and we'll dig into it!
The Fedora Atomic Desktops have been available in Fedora for while now, but they are not the default option displayed on the website nor recommended to new users.
At the same time, Universal Blue is gathering a lot of interest, notably via the Bazzite variant that targets mobile gaming devices and other form factors. What are the main difference that make Bazzite ready for new users today while the Atomic Desktops are not considered to be?
In this session we will take a look at what is currently missing for the Atomic Desktops to become a first class option in Fedora and how we could make that happen. We will also talk about the present and the future of the Atomic Desktops: Bootable Containers (bootc), systemd system extensions (sysexts), Fedora and Flathub Flatpaks, license encumbered codecs, external kernel modules, etc.
Breaking into tech can feel overwhelming, but mentorship and community can make all the difference. In this talk, I’ll share my journey from transitioning into tech to becoming an Outreachy intern with the Fedora Project and how that experience shaped my career. Beyond being mentored, I’ve now taken up the role of a mentor—building a community to support aspiring and transitioning Product Managers. Through my story, I’ll highlight the impact of structured mentorship, the importance of fostering welcoming spaces in open-source communities, and how we can empower new voices in tech. This talk is for anyone looking to navigate their own transition, give back through mentorship, or build a thriving community that drives growth for both individuals and the broader ecosystem.
Fedora Ready is a promotional program that supports and promotes hardware vendors who ship devices with Fedora Linux preloaded. But how can we scale Fedora Ready beyond the work we’ve done so far and invite community members to get involved in driving our mission forward?
For many users, figuring out which hardware brands or models work well with Fedora OS can be a challenge, and that’s frustrating. Choosing an incompatible device can lead to unnecessary complexity when running Fedora. But what if we had contributors like you helping inform users about tested, compatible devices? You can become a Fedora Ready reviewer or hardware tester. As a Fedora Ambassador, you could help communicate Fedora Ready’s benefits at events and within your local communities.
Join me in this workshop to learn how to get involved with the Fedora Ready Team and help make Fedora Ready more accessible to the community.
The effort to make Fedora package builds fully reproducible is progressing. For Fedora 42 we introduced a tool to resolve common sources of build irreproducibility into the set of postprocessing tools that are executed at the end of every package build. We also reported bugs or opened pull requests to fix individual issues in many packages. Together, this has increased the fraction of reproducible builds to about 90%.
For Fedora 43 we want to start treating irreproducible builds as packaging bugs. We introduced a portal for packagers to view rebuild reports for their packages. Bugzilla tickets are being opened when a build irreproducibility is found. Our rough goal is to have 99% of package builds reproducible.
In this session, we want to describe what is happening and why, what resources are available to packagers, where we the next steps, and answer any questions packagers or users might have.
It is just like it sounds. At in-person Flock events, Fedora contributors gather to share small pieces of where we come from in our various journeys around the world to get to Flock. At one evening of the conference, we gather people together, spread out several tables, and everyone "contributes" their confectionery item to the table. Typically, we have representation across several countries and multiple continents! Join us at Geekarna https://geekarna.cz/ for some light snacks, candy and games from 8pm - 11pm!
Join us for a fun way to meet fellow attendees. Pick up a Fedora mascot sticker (we’ll have plenty of designs), then look around for others wearing the same one. That’s your cue to say hello - it’s that simple.
This isn’t just for mentors or mentees - it’s for anyone who wants to connect with new or familiar faces and feel more at home in the Fedora community. And yes, there might be some goodies in the mix too. 🐧
During the last couple of months, the Packit team has been working hard on providing a better CI experience for dist-git pull requests. Let’s take a look at how it works, and how you can tweak it to your needs. You’ll also learn how it fits the whole ecosystem and how the default setup is defined so you can suggest improvements.
No worries, we are not reimplementing a wheel. – We are building on the experience and solutions developed for upstream testing; most importantly, we use Testing Farm and tmt as a base for this so your test setup can be preserved. During the talk, you’ll also learn some news from the Testing Farm team about the test execution itself.
We have learned a lot from automating the package releases and one thing in particular – to be successful we need to listen to you and be responsive to the feedback. And we want to do the same for this new effort as well. So, come and bring your questions so we can make the whole system better together. We have plenty of ideas on how to improve it but maybe we are wrong about the importance - come, and tell us what is the most crucial to you. Help us not to forget about use cases like yours we might have forgotten about.
The aim of this session is to inform you about the changes in the Fedora dist-git pull request CI and to gather feedback and input for our future work.
specfile library
Have you ever wanted to make changes in an RPM spec file programmatically?
specfile library has been created for that very purpose. It is a pure Python library that allows you to conveniently edit different parts of a spec file while trying its best to keep the resulting changeset minimal.
In this talk we will take a look at the basic concepts of the library, we will go through
usage examples, from simple (version/release bumping, adding changelog entries, manipulating section content) to more advanced (forced parsing, making modifications less obstructive), and we will discuss macro expansion and condition evaluation, for which the library relies on RPM.
norpm
RPM specfile parser is a very powerful tool, we all know. Did you know though that you should not just blindly trust all the specfiles out there, and be very careful when executing basic tools like fedpkg verrel or fedpkg srpm? These could potentially break your system!
In this part of the talk we’d like to describe elementary requirements of RPM build system related to RPM spec file parsing, the hidden risks, things that complicate our life - and how to (maybe?) make the topic a lot simpler (and safer) in the future.
Anaconda introduced a new web-based user interface, currently available in the Fedora Workstation Live ISO. This modern interface goes beyond just new technologies, we are actively enhancing user experience to make system installation more intuitive and accessible. At the same time we are looking for ways to free up possibilities for advanced users and system administrators.
I will share our rollout plan for Fedora, however, we need your feedback to target the correct deliverables and to know the obstacles we may be facing.
Introduction
SyncStar lets users create bootable USB storage devices with the operating system of their choice. This application is intended to be deployed on kiosk devices and electronic signage where conference guests and booth visitors can avail themselves of its services. This self-service system allows booth visitors in free and open-source software conferences to consider using a GNU/Linux Distribution by creating a bootable USB storage device there in the booth, thus helping increase the adoption of GNU/Linux distributions as SyncStar supports multiple free and open-source software GNU/Linux distributions.
Inspiration
SyncStar was inspired by the original Fedorator project, a kiosk device for writing Fedora Linux Live Images onto USB drives, designed for conference booths. While it sparked interest among attendees, its adoption stalled with the pause in in-person events due to COVID-19. The semiconductor shortage also increased the cost of Raspberry Pi and peripherals, limiting project usability as these were used in building the service hardware. Additionally, the limited 3D printer access raised entry barriers for booth organizers, making it challenging for local conferences to promote Fedora Linux easily.
I present and demo various cli tools related to Fedora development.
I plan to cover fbrnch (packager power tool) workflows in some detail,
also some of the unique features of koji-tool, dnf-repo & dl-fedora,
and time allowing a few others like lsfrom and ostree-pin.
These tools are all packaged and still being maintained & developed.
People attending will learn about these useful tools, that they didn't know they needed.
I expect some useful ideas and directions to emerge from discussion and feedback.
The available information about the use of Fedora Editions is sparse. It is essentially limited to the download numbers accumulated via “countme”. But even these are only partially meaningful.
The Fedora Server Edition Working Group has therefore conducted a user survey to learn more about the current user profile, as well as the wishes and expectations for future development. A total of 4,241 users participated, although only 574 answered all questions in a completely systematic manner. The evaluation is still ongoing. The results shed a new light on some of our plans for further development.
From our experience, we can also make suggestions for a systematization and regularity of such a survey, which can help not only the Server Edition, but also other editions and spins, in addition to “countme”, to reduce the knowledge gap about our users and their needs.
Ever wondered why your newly installed Fedora won't let you play videos recorded with an iPhone? Annoyed with high CPU usage when playing certain videos? Join me on a journey through the history of multimedia software in Fedora and hear why some code is not (yet) allowed to be included in the official repositories. As the founder of the Multimedia SIG, I will talk about what we are doing to bring the most complete multimedia experience possible to Fedora users out of the box, the challenges we have been facing along the way and how you can help us.
About a year ago, Microsoft started the Community Linux Engineering team. One of our focuses is the Fedora Project. What have we been doing for the last year, what are our plans for the next year, and why are we here?
First, we will look back at the past year and celebrate some work we have done. Highlights include expanding the supported content types in the image uploading service we initially built to automatically upload the Fedora Cloud images to Azure, onboarding several folks from Microsoft to maintain their software in Fedora, working to improve Fedora’s signing infrastructure, and adding an official Fedora WSL build.
Next, we’ll talk a bit about the work we hope to highlight at Flock 2026, like a more reliable and capable signing service, more automated testing for Cloud images, and more.
Finally, we’ll wrap up by talking about why we’re committing resources to the Fedora Project and what we hope to accomplish.
Let's go through the most recent features and improvements that enable you to automate boring and menial tasks you have to do regularly. We will show you how you can automate releases even for upstreams that are not based on git. You will get to see a demo of support for Koji sidetags in Packit for downstream releases. And also we will go through some of the recent internal changes that you can benefit from, e.g., customization for specific ecosystems (like Go), or distro aliases that you can use even in your own projects. And many other subtle changes that improve both user experience and the release workflow.
Testing Farm is working on splitting the test environment setup for Fedora CI, CentOS Stream CI and Packit.
This will make the test environment setup visible to the end users and easily usable for local execution when reproducing CI failures. Moreover, the test environment setup will become easily contributable by the community, so the users will be able to influence the test environment setup by submitting a merge request.
Upstream project: https://gitlab.com/testing-farm/profiles
To bolster Fedora's membership and cultivate increased community engagement and participation, a strategic approach emphasizing regional visibility is required. This involves establishing a presence at relevant open-source events, particularly within the Latin American region, and re-establishing connections with local colleges and universities. Achieving this necessitates the development and delivery of compelling events and workshops led by internationally recognized experts or facilitators.
In today's rapidly evolving technological landscape, accessibility remains a crucial consideration in software development. This presentation delves into the complex world of screen readers, exploring how these essential tools empower visually impaired individuals to effectively interact with computers. We will underscore the continued importance of the keyboard as the most effective input device for visually impaired users, even in the modern digital environment.
As we transition from legacy systems to modern platforms like Wayland and GTK 4, significant challenges arise in handling input devices. Our discussion will cover the current state of screen reader integration with these platforms, the obstacles presented by deprecated APIs, particularly in GTK 4, and the interactions involved in the shift to Wayland.
This talk will also introduce a new approach that, when embraced by all stakeholders, promises to resolve these challenges effectively. Join us as we explore the path toward a more inclusive digital world, where technology truly empowers all users, regardless of their abilities.
With more than five years of experience making community in Mexico, in this talk we will share how we do it. From the organization of the local chapter, mediating to achieve group harmony, to walk together on the path of mutual support and support the project in achieving the group goal.
To bring the use of Fedora Linux in a world where there are so many and so good Linux distributions is a great challenge. In Fedora Mexico we take the challenge to bring it to a technical level of excellence.
From the organization of technical talks demonstrating the technology driven and supported by the project, to the personal experience that all this journey has brought with it.
We will share with you the strategies we use to be present in the most important and relevant events of the Mexican technology community, ranging from the most basic beginners to the most expert users.
Not only on the technical side, but also emphasizing the human side of the project, in our four foundations, which are in charge of reaching all levels, to motivate learning, use and participation in the development of Fedora Linux.
At Flock To Fedora 2025, join us for an insightful exploration of Fedora Project’s participation in Google Summer of Code 2025 with an emphasis on the essential roles of mentors and organization administrators. This talk will delve into the unique challenges and rewarding experiences associated with guiding emerging talent through two innovative projects: the "AI-Powered Log Triage and Security Alert Aggregator", and a novel service designed to streamline the introduction of new projects to Fedora Project. Hear interns progress stories and view snippets from the impactful work undertaken by Google Summer of Code 2025 interns. First half the presentation underscores how dedicated organization administrators and mentors help build a robust mentoring experience.
Alongside showcasing the GSoC and Outreachy contributions to Fedora Project, we will share the deeper reflection on mentorship from a challenging experience by Aurelien Bompard and Akashdeep Dhar's participation as mentors in Outreachy. In the previous year, they proposed a Fedora Infrastructure project and began mentoring the applicants with Tomas Hrcka's and Michal Konecny's support. Unfortunately, the contribution phase did not go as planned and we ended up discontinuing the internship early than intended. Here we will share our experiences from mentoring in the Fedora Infrastructure team - highlighting both the positive moments, arising issues and lessons learnt. Whether you are a current or aspiring mentor or mentee in the free and open-source software community, you can be sure to obtain valuable insights to help strengthen mentorship practices.
Learn about Bootable Containers: why this technology is transformative and how to implement bootc for work, homelab, or just for fun! Learn about what Day 0, 1, & 2 operations all could look like. This presentation is for those who understand what containers are and want to learn how to apply the same principles to your servers, desktops, or even embedded devices!
Desktop apps nowadays have modern system requirements and require an evolution of the roles and responsibilities of upstream developers and the desktop distro. I am going to discuss my perspective as an app developer dealing with the Linux Fragmentation Problem and the solutions being built to address it. My perspective developing GNOME Boxes, participating in the GNOME and Flatpak communities, while being a Fedora and RHEL contributor in my day job at Red Hat.
Mentoring in open source is a powerful catalyst for change—it not only fosters individual growth but also strengthens communities and builds tomorrow’s leaders. This talk will explore the crucial role of mentorship in the open source world, going beyond simply sharing technical skills. It's about guiding contributors, cultivating collaborative spaces, and creating ripple effects that resonate far beyond a single project.
Through personal stories, real-world examples, and practical advice, you'll learn how mentorship can bridge gaps, inspire new talent, and drive innovation. We will delve into what mentoring is—and isn’t—shedding light on the misunderstandings and highlighting the true essence of a successful mentor-mentee relationship.
Outreachy is conducted by Software Freedom Conservancy and it provides internships in open source and open science. Over the years, there has been an explosive reach in the public about this program. As a Outreachy intern in the summer of 2022 for the Fedora Badges Design Project and eventually becoming the general Fedora mentor for the 2024 summer cohort, I want to highlight how it works for both the mentors and the mentees. Taking inspiration from experience, I want to discuss best mentor practices and what all changes can we bring to make the Fedora Outreachy experience better.
Attendees will discover the dual impact of mentorship: it benefits not just the mentees but also enriches the mentors by helping them learn, lead, and leave a legacy. We'll cover how to find the right mentor, how to be one, and why it matters in the open source ecosystem. You'll gain insights into fostering an inclusive, supportive culture that encourages growth, promotes diversity, and empowers contributors to excel and, eventually, become mentors themselves.
Whether you’re a newcomer eager to learn or a seasoned contributor looking to give back, this talk will equip you with the tools and mindset needed to make a lasting impact. By mentoring, you’re not just teaching; you’re shaping the future of open source—and the universe.
Join us for a session that will inspire you to engage, mentor, and make a difference in ways that extend beyond code and into the heart of the open source community.
What is Bazzite?
Bazzite is an open source custom operating system image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. It is built with Cloud Native Technology through the use of OCI containers and GitHub Runners.
It is built for Linux newcomers and enthusiasts to provide the best user friendly experience for playing your favorite video games.
Topics
- What is Bazzite?
- Bazzite Features
- Why Bazzite uses Fedora Atomic OCI Images
- Impacts of Bazzite on the gaming space
- Discuss paths for upstream contribution from Bazzite to Fedora
- Discuss reviving the Fedora Gaming SIG to have a better base for projects like Bazzite
- Assert why Gamers are a good audience to capture for Fedora
- Future Plans for the Project
- SystemD Systems Extensions
- Bazzite-DX
- ZSTD:Chunked Images
Themes
Welcoming New Voices: Pathways for Fedora Contributors
- Bazzite creates a path for new Fedora contributors by accessing a younger audience interested in gaming and technology
- Many of Bazzite’s contributors have never contributed to Linux before
Driving Innovation: Fedora and Emerging Technologies
- Bazzite is built on Fedora bootable containers and has been driving innovation in this space for several years.
- Bazzite has the desire to drive these innovations that it has created directly into Fedora
In the high-stakes world of autonomous vehicle development, system stability isn't just a convenience—it's a necessity. During my time leading Linux deployments for Ford's Autonomous Vehicle and Smart Infrastructure program, we faced countless challenges with traditional mutable distributions: broken NVIDIA drivers, undocumented configuration changes, and hours spent debugging in freezing Michigan winters and sweltering Miami summers.
This presentation explores how Fedora Atomic's immutability and predictable rollbacks would have transformed our embedded systems landscape. Drawing from real-world examples across testing facilities, roadside units, and development environments, I'll demonstrate how immutable distributions solve the most painful aspects of embedded Linux deployments.
You'll learn:
Why developer-modified systems became our biggest reliability challenge
How immutable filesystems prevent configuration drift across deployed devices
When and how rollbacks can save critical field deployments
Practical workflows for managing updates in embedded environments
Fedora Atomic's reliability isn't just for large corporations. I'll show how the same principles make it ideal for small organizations, community groups, and non-profits currently stuck on outdated distributions. Through a live demonstration, you'll see how simple rollbacks can transform maintenance for teams without dedicated IT staff.
As we push toward more connected and intelligent infrastructure, Fedora has an opportunity to become the go-to platform for embedded systems that simply work—saving both Fortune 500 companies and local organizations from the pain of mutable Linux distributions.
As community leaders (or even as group leaders within a larger community), we try to make decisions that will lead to the type of community we're trying to foster. We tend to think about this is the same way that we would construct a building (often we call ourselves architects!), but humans are not bricks, and don't always react in rational ways.
In this talk, we'll look at some of the problems we have to confront when designing communities, including:
- How can we get people to contribute to specific tasks/efforts
- How do we motivate & recognise contribution
- How do we encourage the right behaviour and norms, and deal with those who break the rules
- How do we integrate newcomers with our existing members
Drawing on evidence from the literature of psychology, sociology, and economics, we can learn more about how to design around these questions. Many of the results are known from experience to community managers and architects, but other results are not so obvious, and some are completely counter-intuitive. We'll go into detail on a handful, and provide some further reading material for those who want to explore more.
This talk is aimed at new and existing community leaders, and hopes to leave them better informed about some of the choices and pitfalls in front of them when working in their own groups.
This talk will show you how to cleanly install the latest vanilla Linux kernels on Fedora, as sometimes you'll need one to get upstream to act on something – like resolving a bug Fedora's kernel package maintainers lack resources to tackle. Going upstream in situations like that is in your own and everybody else's interest, as fixes and improvements usually will reach Fedora Linux and its users quickly through regular updates.
Thorsten will describe various ways to install upstream kernels and explain which of them is the best depending on what you want to achieve – like helping testing upstream kernel's ahead of time or reporting and possibly bisecting a regression. Of course you'll also learn how to cleanly remove any kernels later to keep your system clean and healthy, as if you never had installed a upstream kernel manually or via RPM/DNF.
While describing these things Thorsten will also provide a few tips on how to best engage and interact with upstream, for example when reporting a Linux kernel bug.
Join members of the Fedora Council for an Ask Me Anything session at Flock.
Closing remarks by FPL. FCA & FOA
This year, we return to a large body of water to celebrate the official Flock party :tada: Join us aboard the Anna Carolina boat at Dvořák Embankment right at Čech Bridge on Friday, June 6 from 7pm - 10pm for drinks and finger food and celebration!
Join your fellow EPEL maintainers for this hackfest all about EPEL. Here are some of the topic areas we intend to explore.
- adding new packages to EPEL
- patching CVEs
- policy revisions
- mass branching improvements
- documentation
We'll also set aside a section of time for a general EPEL Q&A, geared specifically at helping Fedora contributors get onboarded to EPEL.
Tired of manual packaging tasks? Packit can ease that by automating package maintenance for upstream releases to Fedora and providing upstream CI to build and test packages against Fedora, CentOS Stream, and EPEL. Whether you're new to Packit or looking to optimize your workflow, this session is for you!
In this workshop, we’ll guide you through setting up Packit for your package. We’ll cover everything from getting your changes into dist-git, handling Koji builds (including side-tags), and wrapping up with Bodhi updates. If you’ve been hesitant to use Packit before, now will be the perfect time to give it another look - we’ve introduced support for side-tags, handling non-divergent dist-git branches, removing the need for an upstream Git repo, streamlining the configuration, and more to unblock packages that weren’t previously supported. And if there’s interest, we’ll also dive into Packit’s upstream CI capabilities.
Join us to see Packit in action, discuss your feature requests or design ideas, and let us help you simplify package maintenance!
The Initial Setup tool provides an interactive way of setting up Fedora machines on their first boot after the installation, using a graphical or text based UI. It is currently built as a launcher for relevant screens of the Anaconda installer and uses the Anaconda backend code to configure the system.
Initial Setup was introduced around the time of Fedora 19 to replace the standalone Firstboot tool, with the aim of reducing code duplication and providing consistent configuration. The design has worked reasonably well so far, but there are new challenges as both the Anaconda installer & the distribution landscape changes over time.
We will discuss the impact of X/Wayland and WebUI on the initial setup, main use cases, current challenges and ways forward.
Initial Setup is a release blocking deliverable on Fedora ARM images and is used also in other places, including Fedora derivatives, so want to provide this opportunity for all interested stakeholders to bein informed & to provide feedback and get involved in our future plans.
A containers BoF, hosted by Dan Walsh
Got a multimedia package that's missing in Fedora? Found an annoying issue with a multimedia package in Fedora? Having trouble with getting your videos to play correctly? You've come to the right place! With Multimedia SIG members present, we'll do our best to help you solve your issues live and discuss the future of multimedia in Fedora.
This session will be held as part workshop, part presentation of modern (or just new) packaging practices and tools for the Python, Go, and Rust ecosystems.
- Python: 2021-era Python packaging ("pyproject" macros) and declarative buildsystem support in RPM 4.20
- Go: go-vendor-tools and upcoming packaging changes (potentially changing the default to using vendored dependencies)
- Rust: improvements for rust2rpm, new busywork-reducing features, improved support for building with vendored dependencies
The workshop will begin with a short introduction and presentation of these features and upcoming changes from SIG members. At this point, common problem areas of RPM packaging that affect multiple language stacks could be discussed if there is audience interest. After a short break, attendees can ask questions and / or split into groups to get hands-on experience or demonstrations.
The Rust SIG will also be collecting ideas for a new "cookbook" style documentation for rust2rpm that will serve as a more "if-this-then-that" style documentation for common situations people encounter when doing Rust packaging in Fedora.
Let’s discuss and collaborate on defining the new implementation for our distgit service.
In the past, the ARC team https://fedora-arc.readthedocs.io/en/latest/dist-git-move/index.html migrating from pagure-distgit to a different forge and identified the services and processes that would require changes and updates.
Now, together with Forgejo developers, we’ll explore the available options to achieve the necessary distgit functionality.
Design plays a crucial role in the Fedora community, shaping its visual identity and user experience. This hands-on workshop will provide beginners or those interested with the knowledge and tools needed to effectively engage with the Fedora Design Team.
Participants will learn:
- How to get started as a Fedora Design contributor.
- How to navigate and manage design requests.
- What software and tools are used for different design tasks.
By the end of this workshop, attendees will have a clear understanding of how to contribute to Fedora’s design efforts and collaborate with the team.
When RPM builds fail, uncovering the root causes can be a complex and time-consuming process. The intricacies of these failures often lie in the nuances of the build logs, which require extensive examination. This workshop aims to bring together the Fedora maintainers community to address this challenge. By collaboratively annotating snippets of failed RPM build logs, we aspire to create an open, collective knowledge base that anyone in the open source community can benefit from and we can create a system that will assist in troubleshooting RPM build failures.
This workshop teaches you how to use of the popular project kiwi to build images in the same way that we are building them for the Fedora Cloud Edition, but then takes it a step further than just building the base images and guides you through the process we use to build and test those cloud image, including all of the necessary components to run a KDE desktop from a Public cloud provider. We’ll use the Fedora Cloud Edition image build process, add the VDI software provided by Amazon and install it as a part of our image build process.
In this workshop, we'll pick our pet peeves with the Fedora Infrastructure applications and look at how we could make our daily lives easier. Help will be provided to get started with hacking on the apps, which app do what, how they are interconnected with each other, etc.
Knowledge of the programming language used in the app is very useful, but not mandatory: writing a detailed feature request with clear requirements is also very useful!
A few years ago we got rid of ldconfig scriptlets. With sysusers support in rpm, in Fedora 42 & 43 we got rid of scriptlets calling getent/useradd/groupadd. Can we get rid of most other scriplets? One of the most pervasive are the scriptlets for systemd unit enablement. Let's discuss options how to make those unnecessary and simplify packaging. What about the rest? It'd be great to remove the calls to update-alternatives and make scriptlets the rare exception, not the norm.
Another source of complexity in packaging is arch-specific dependencies (%ifarch foo, BuildRequires:bar-devel, %endif). We could replace those by rich dependencies, making srpms arch-independent. This would make querying package dependencies much easier, but also help with reproducible builds. What is the best design for this? Some syntactic sugar in rpm would make this easier to implement.