DevConf.cz 2018

"Containers are all the rage, alongside cloud and DevOps. Sometimes they also induce rage. In this talk, we will take a look at using Fedora Atomic on your desktop, when it makes sense, and what the potential benefits vs drawbacks of having a container-based OS on your desktop are for you as a developer.

You will learn:

* what Atomic Host is
* how it compares to CoreOS
* that you can use container-based OS on your desktop machine as well
* if and why that makes sense from a developer's perspective
* how to do it effectively

No maximum for attendees, no specific requirements, the talk is beginner-friendly, but some existing knowledge of containers is advised."

"Pagure (https://pagure.io) has been changing quite a bit over the last months, this presentation aims at providing an overview of the changes that were implemented, bugs fixes and features added.
Being a simple pagure user or just curious about this, you might have missed a few of the features that were added. We will try to go through the main ones, present the ones we are planning on and leave time for questions or live feature requests!"

"OSTree on Fedora can now handle multi platform, and a number of other issues with using Fedora IoT have improved which means we can start to accelerate the IoT SIG and engage in the wider community with usable demos. Where are we and where do we envision being in time for Fedora 28 and what's the short to medium roadmap"

"We been pushing Fedora Workstation for 3 years now and have successfully grown the userbase significantly. At the same time changes within Red Hat and in the marketplace has affected some of the plans made so this talk will both cover some of major milestones we achieved, but also talk about the items we need to focus on going forward to keep growing."

The Fedora Modular Server is dead for F27 but we still need the benefits of a modular distro in F28 and beyond. For F28, the Modularity WG has proposed a new architecture (as a Fedora Change) that we are calling "Addon Modularity." The new architecture allows modules to deploy on top of the traditionally built distro. However, there are some changes for module authors which is what we will focus on in this presentation.

During this presentation, we will walk you through how we are making Django v2 and Django v1.6 both available for Fedora 28. Next, we will walk through how to make an application that depends on Django (Review Board) available. We will lead you through exactly what we did, including collaboration with the existing maintainers, while developing and deploying this content. Lastly, by the grace of the demo gods, we will demonstrate the application(s) working from a rawhide image.

"We want the composition of packages in our operating system to be in an “always ready” state: functioning, integrated, and coherent with one another. Continuous integration (CI) is absolutely essential for this. We show a few key pieces from the developer perspective: Tests in dist-git, CI pipeline, discoverable tests and results with a pull request workflow in Pagure and a Fedora OS that only accepts properly tested changes. Most of the tests currently in Fedora dist-git originate from Red Hat internal QE. We show what happens before a pull request lands in a Fedora package repository to the benefit of both upstream and downstream."

"Fedora Atomic Workstation provides a new desktop experience powered by rpm-ostree, flatpak, and docker. There are many benefits to this combination that should make Fedora Atomic Workstation an attractive choice, some of which include:
- transactional updates: never fear updating again, even across major releases
- clear separation of host and apps: flatpaks and docker containers are updated on their own cadence and have little impact on host requirements (and vice-versa)
- other rpm-ostree features such as immutability, update rollbacks, and effortless package tracking

In this session, you will learn:
- why Fedora Atomic Workstation is awesome,
- what you can accomplish on Fedora Atomic Workstation, and
- how you can get started.

This session has no requirements."

"1000 Python 2 packages were renamed for the new naming rules
("python2-" prefixes) in F28.

Spec files can be arbitrarily complex. Changes were automatized using
pattern matching and heuristics.

Proven Packager permissions and Mass Package Change procedure were
used to interact with the huge number of packages and packagers.

Issues occured: bugs in the design _and_implementation, external
problems such as infrastrucure hiccups and many packages FTBFS, some
maintainers not being thrilled.

This talk is about:

- new python package guidelines and why packages are being renamed,

- an introduction to the Mass Package Change procedure,

- pitfalls and things to watch out for in package renames and when
touching packages of other maintainers,

- why such changes are worth doing."

"Over the last year, Fedora has automated the package signing. In this talk, I hope to explain how this is working, how things are secured and the future plans.
For this, I will be starting with a short summary on Sigul (https://pagure.io/sigul/) and Koji, and then discuss how Robosignatory (https://pagure.io/robosignatory) ties it all together, and how it plays with Bodhi."