DevConf.cz Mini 2022

Fedora Packager Dashboard is a web application aiming to make the life of Fedora packagers easier. It combines data from multiple sources (bugzilla, bodhi, koschei,...) relevant to the maintainers of Fedora packages.

Tracking all these sites can be time consuming, especially if you maintain dozens of different packages, so the Dashboard provides everything you need (or at least what we've thought of) - condensed, cached, searchable and filterable on one page.

We have managed to add some pretty nifty features, and not all of them in the background.

Come to see the new custom (multi-user, multi-group, you name it) dashboard, take a look at our API to find out anything about any Fedora package or packager, and talk to us about what's next!

The Packit team started to develop a common process and tooling for source-git to be shared across the RHEL ecosystem in 2020. In this session we share the progress made in tooling and automation, and invite you to use the source-git workflow to maintain your packages.

A dist-git (a.k.a. “distribution git”) repository is a Git repository used during distribution development in the RHEL ecosystem, tracking the downstream changes of a package as patch files and referencing the corresponding upstream source archive(s) stored in a place called “the lookaside cache”.

Source-git is a thin layer on top of dist-git, aiming to simplify packaging work especially when it comes to collaboration and maintaining long running distribution branches with a large number of patches.

Source-git repositories are forks of the upstream projects, with a few select branches tracking downstream (distribution) patches and packaging paraphernalia as Git commits.

This format allows packagers to tweak code during packaging activities using the same format as upstream projects do and get rid of the friction of handling upstream code and downstream patches as separate entities, as it is done in the canonical dist-git format.

At the beginning of the session we give a walk-through of what source-git is, how it relates to dist-git and how source-git offers a better environment for downstream distribution work, especially when it comes to collaboration.

Next we give a demo to show how to set up a source-git repo for a package, how to perform the main packaging activities in this repository, and how to translate the result to dist-git.

At the end of the session we share the roadmap for the future development of the source-git tooling and automation, and plans to encourage a wider adoption in Fedora Linux and CentOS Stream development.

The Modularity project was always shrouded in mystery and legends. So with this short talk I want to introduce you to the magical land of Modularity. What is a module? How does it look like? Why modules even exists?

NemoMobile is the successor of MeeGo and is a truly opensource Linux-based Mobile Operating System. The user interface is based on Qt and focused on mobile usage from the start. With release of PinePhone we restarted its development with Manjaro Linux.

The talk covers peculiarities related to delivery of microcode for Intel IA-32 (x86 and x86-64) CPUs and the way they are addressed in RHEL. This includes:
- implementation of Intel IA-32 CPU microcode update loading in the Linux kernel;
- packaging of the microcode update files in Fedora and RHEL;
- the reasons for maintaining a separate to linux-firmware package;
- handling of stability issues related to microcode updates;
- current issues with microcode updates packaging in Fedora and RHEL, as well as their possible solutions.

Testing Farm provides a testing environment offered as a service. GitHub Actions is a framework that provides possibilities of CI/CD - allowing you to trigger a specific action (build, test, deployment, etc) directly within a GitHub repository.
The combination of these two tools together enables the user to test the programs, stored on GitHub easily, e.g., within pull requests, periodically, or at any other specified trigger.
Join us in the talk where will be explained how to write a Github Action that triggers tests on the Testing Farm environment, how can be the action integrated into your GitHub project, and how you can benefit from the testing-farm-as-a-github-action that is already available on the GitHub marketplace.