DevConf.cz Mini 2022

To celebrate the 30 years of Linux we’ve invited a few panelists to discuss some of the major milestones and changes throughout its history. Come to hear about the past and the thoughts of the future!

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!

Let's talk about what it takes for Software as a Service to be truly Open Source. So many of us work on services, and want to understand what it means to bring our Open Source practices and standards with us.

When a service meets basic requirements, it is then possible for contributors to further progress the service toward more Open Source practices. Thus there should be minimum requirements that we expect from any service claiming to be Open Source.
We'll propose two simple requirements, as outlined by the Operate First methodology, and discuss various aspects of the Service that they impact.
https://www.operate-first.cloud/community/open-source-services.html

Being a blind user poses many challenges on its own. However, being a blind Linux user adds some more. Let's have a look at how the user can use a Linux computer, what challenges he faces and how the broader developer community can help these folks.

Birds Of Feather (stick together) session about Kubernetes.
Have you installed k8s on a dead badger? Or manage billions of clusters for Fortune 500 company? Do you maintain your own k8s distro? Would you like to learn about hot new stuff in cloud land? Confused about hundreds of alternatives? A group of field experts would gather here to discuss all that and more.

Come over and lets have a chat, do some demos and discuss implementation details

Red Hat OpenShift container orchestration platform is the most deployed enterprise distribution of Kubernetes in modern hybrid cloud environments. Why is that so? What is so cool about OpenShift? How can one start and benefit from its usage?
 
In this workshop session we will introduce important basic concepts and principles of this container orchestration platform based on popular open-source Kubernetes project. During the given set of hands-on examples we will emulate an arbitrary use-case and implement working application using both Kubernetes and OpenShift resources.
 
Workshop agenda:

• Platform architecture and fundamentals
• Cluster interface options
• 12 Factor application deployment
• Basic software development cycle
• Application management 101

 
Requirement – in order to participate on this workshop, please be sure to bring your own laptop (BYOL) with working web browser (Chrome[ium], Firefox, Safari). All other tools or assets will be provided during the session itself.

Working instructions for the workshop: https://pad.riseup.net/p/ocp-devconf2022 

BugHunting is a challenge for the conference attendees, who want to try their development and debugging skills. Participants will be provided with several tasks in various programming languages, while each task consists of a broken code and a bug report. 

The purpose of every task is to find the bug, and fix it in the code. Your solution is evaluated in real-time after you submit it, and you score points if your solution is correct. Some of the issues are artificial and were created only for the Challenge, while some are real-life issues.

More info about the challenge at https://howto.bughunting.cz and it's suggested to set up an environment for the challenge itself according to the steps at https://howto.bughunting.cz/env_setup.html prior the event, so you have more time for solving the tasks.

You can also continue solving the tasks after the event ends (we'll keep the server running). Please pick up the credentials at our booth!

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.

Open discussion after Open Source requirements for Services talk.

Have you ever wondered about differences in the installation of Fedora Server and Fedora Workstation? Would you like to customize the Anaconda installer for your operating system? Anaconda is used by several distributions and spins and each of them targets a little different user group. It is natural that they need to tweak some parts of the installer to provide the best user experience. I will talk about common customizations, how to configure them and how customizations affected the recent development of the Anaconda installer.

Understanding what a feature or functionality does is important for everyone involved in their development. Not only something specific for Dev or QE. User Story Mapping is a powerful tool that can help teams have a shared understanding of what a feature or functionality of a system does, from a user perspective. This shared understanding will definitely improve the quality of the development. Come and join us to discover a little more about User Story Mapping through some good hands-on experience.

Let’s start from the beginning. Quarkus. What’s Quarkus? That’s a pretty good question and probably a good start. If you go to the Quarkus website, you’ll read that Quarkus is "A Kubernetes Native Java stack tailored for OpenJDK HotSpot & GraalVM, crafted from the best of breed Java libraries and standards." This description is somewhat unclear but does an outstanding job at using bankable keywords. It’s also written: "Supersonic Subatomic Java." Still very foggy. In practice, Quarkus is a stack to develop distributed systems and modern applications in Java, Kotlin, or Scala. Quarkus applications are tailored for the Cloud, containers, and Kubernetes. That does not mean you can’t use Quarkus in other environments, there are no limits, but the principles infused in Quarkus have made containerization of applications more efficient. In this workshop, we will explain what Quarkus is and because the best way to understand Quarkus is to use it, build a set of microservices with it. Again, Quarkus is not limited to microservices, but it’s a generally well-understood type of architecture.

This workshop offers attendees an intro-level, hands-on session with Quarkus, from the first line of code to making services, to consuming them, and finally to assembling everything in a consistent system. But, what are we going to build? Well, it’s going to be a set of microservices:

- Using Quarkus

- Using HTTP and events (with Apache Kafka)

- With some parts of the dark side of microservices (resilience, health, monitoring with Prometheus)

- Answer the ultimate question: are super-heroes stronger than super-villains?

This workshop is a BYOL (Bring Your Own Laptop) session, so bring your Windows, OSX, or Linux laptop. You need JDK 11 on your machine, Apache Maven (3.8.x), and Docker. On Mac and Windows, Docker for x is recommended instead of the Docker toolbox setup.

What you are going to learn:

- What is Quarkus, and how you can use it

- How to build an HTTP endpoint (REST API) with Quarkus

- How to access a relational database

- How you can use Swagger and OpenAPI

- How you test your microservice

- How to build a reactive microservice, including reactive data access

- How you improve the resilience of your service

- How to build event-driven microservices with Kafka

- How to build native executable

- How to extend Quarkus with extensions

And much more!

Ready? Here we go!

Link to the workshop - https://quarkus.io/quarkus-workshops/super-heroes

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?

Let’s talk about blockchain and web3! I know, I know, it’s all ponzi and hype, but there is also plenty of cool development happening. And most of it is open source.

We’ll take a look at popular open source tools, interesting projects and some basic concepts like governance and DAOs.

What are latest changes in Fedora 36 Workstation? What improvements and changes did GNOME 42 bring to Fedora? And what are the plans for the near future?

After the talk, three panelists will discuss Fedora-related topics with the release party attendees, answering their questions and listening to feedback and ideas.

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.

What has changed in the open-source communities after 2 years of lockdown? What are the threats and opportunities for open-source communities right now? We'll discuss this and much more with the local open-source contributors and leaders.

How are Fedora Releases getting tested? What are our processes around ensuring quality of each Fedora release? How can community help us here?

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.

Many forward-looking organizations have been undertaking a digital transformation. They have been providing their services via APIs to not only enlarge their business but create new types of services.

Of course, financial institutions in the world have also tried to take the same way. However, by their providing APIs' own nature, high level security is required to utilizing them.

Keycloak, an Identity and Access Management OSS, can protect such APIs requiring financial-grade security level by Financial-grade API (FAPI) security profile, which leads to promoting financial institutions' digital transformation.

In this talk, the speaker provides a summary of FAPI and tells how to realize FAPI support to keycloak through OSS community activities called FAPI-SIG. The speaker also tells the actual use case leveraging keycloak's FAPI support, namely Open Banking Brazil.

Birds Of Feather (stick together) session about observability. Lets meet and discuss hot new things related to monitoring, tracing and logging. A group of experts and newcomers alike will help you navigate in ever-changing landscape of hot new and good old trusted tools and solutions

Upstream projects don’t usually care about Linux distributions and how exactly the projects are integrated with other distro components. Getting new upstream releases built and updated is even more tiresome. The process tends to be very manual, requires in-house knowledge and is usually done by downstream maintainers.
What if I told you that you not only can build and test contributions in your upstream project, but also can seamlessly bring your new upstream releases into Fedora Linux very easily. Packit can do all of this and much more! We have recently added new functionality into Packit to completely automate the downstream release process - it is much simpler now! But wait, there is more - over the past year we have implemented many new features and UX improvements for our existing user base. Join us on this workshop session to learn more.

In this workshop, you will:

• Learn about the Packit project and how to set up an automated downstream release process for Fedora.
• Also, we will help you to use Packit for validation of your pull-requests via RPM building and testing.
• You can try it on your own package.
• Discuss any issue or idea you have. (Our current users are more than welcome!)

To actively participate, you need:

• GitHub account for trying upstream builds and tests done by Packit.
• Fedora account for trying downstream automation.
• Ideally, you are a maintainer of a package in Fedora, but you don’t need to be – in that case we will prepare an example package for you.
• RPM packaging knowledge is welcome.

We are also doing another session about a next-generation downstream maintenance process called source-git [https://sched.co/11l5p]. If you are an upstream or a downstream maintainer, you shouldn’t miss these sessions.

Anaconda is getting a brand new UI based on web technologies, what were the challenges, what remains to be done and when we can expect this in Fedora?

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.

Project Thoth provides an open database that is used to resolve high-quality Python application dependencies and suggests using runtime environments when running Python applications. The database is used by the Python cloud resolver but it can be used by the community to help resolve issues in open-source Python libraries. This talk will show this database in action, how it is used and how anyone can benefit from using it. We also welcome contributions to the database by the community. Let's build better Python environments together!