Encrypt all the Fedora Project


It seems that thanks to the hard work of the Fedora Infrastructure team we can soon enforce HTTPS for all of the Fedora Project – at least of all hosts within *.fedoraproject.org. To make sure that this does not awfully break everything it would be awesome if you could test whether we need to fix something for you for this. If you use chromium or chrome, you can easily enforce HTTPS for fedoraproject.org and its subdomains:

  1. Go to the net internals settings at chrome:://net-internals#hsts
  2. Put fedoraproject.org in the input field for domain
  3. Check the Include subdomains for STS checkbox
  4. Click on the Add button

chromium-hsts-fedoraAfterwards you should notice that all requests to any fedoraproject.org URL should got to HTTPS by default. If you notice any problems with yes, please not this in the Fedora Infrastructure ticket #2888. Let me know if you figure out how to do this in Firefox and I will add the instructions here as well.

Translation Sprint 2017


The last couple of days there was a Fedora Translation Sprint that I took as an opportunity to find out how translations in Fedora work nowadays. The actual translation happens at Fedora’s Zanata instance, a web based application for translation collaborations. Even though it accepts Fedora’s FAS single sign-on system, it is not possible to directly propose translations. Unfortunately, several manual steps are required. Luckily I noticed this early enough in the sprint and Roman, the German translation team coordinator, pressed the necessary buttons in time for me to join during the sprint.

After I learned Latin, English, French, Spanish and some Dutch at school nowadays I find some joy in analyzing language. This is quite useful for translating documentation since the vocabulary used for software like RPM and DNF is quite challenging. Continue reading “Translation Sprint 2017”

(Spring-)Cleaning the Fedora Package Collection

cat-1435458Spring arrived and doing spring-cleaning I thought about all the cleanup tasks in Fedora. If you are interested in doing some Fedora spring-cleaning, I will show you some opportunities to get your hand’s dirty and Fedora cleaner.

The required cleanup tasks depend on the state a package is in. In my opinion there are about five different states:

  1. Not packaged, yet
  2. Under review
  3. With a maintainer
  4. Orphaned
  5. Retired (Removed from Fedora)

Continue reading “(Spring-)Cleaning the Fedora Package Collection”

32nd Chaos Communication Congress (32C3)

Table with Fedora cloth, swag and sweets.
Fedora Assembly at 32C3

At the end of last year Zacharias and Jacob joined me in representing Fedora at the 32nd Chaos Communication Congress in Hamburg, Germany. It was the first Fedora Event that I organized as Fedora Ambassador, therefore I was quite nervous. Until I arrived at the hotel it was unclear whether I will have any swag to decorate the assembly (there are no classic booths at the Congress), but I also packed some blue sweets, chocolate and Aachener Printen to lure visitors to our assembly. Luckily as you can see on the picture, additional swag also arrived in time.

In contrast to the booths at other events, we had kind of a round square table we we could meet with interested visitors and talk about Fedora and related topics – I wished that we could also show some more items, like a 3D printer, but I was not fortunate enough to win one at last years Flock. I tried to get a LED stripe running to show some Fedora controlled blinkenlights, but I did not get it ready in time. Despite the usual SWAG like stickers, DVDs and buttons, I printed some brochures designed for SXSW 2011 that I found in the wiki. They attracted several visitors, who took a copy. Thanks to the digitalcourage assembly I was able to print more copies for a small donation. Additionally I prepared some sheets that showed the GPG fingerprints of the current Fedora keys that were also popular at this event. It was a very interesting experience to organize an event an I am looking forward to this years Congress to implement some of the ideas I have to improve our assembly. I also liked the change of perspective, since the previous years I was mostly a visitor going to other assemblies to talk to people, this time the people found me. I am looking forward to representing Fedora at the 33rd Chaos Communication Congress this year.

Support Status of Installed Fedora/EPEL Packages

Did you ever wonder whether the packages you have installed are still maintained or will be available when you update to the next release? I might have a solution to answer this question for you. Recently I wrote a little script that reports packages that are orphaned, retired or missing from your current Fedora/EPEL release or any newer release. It is still only in a proof-of-concept status, but I hope to get it into Fedora eventually together with a useful cron job (or systemd timer) to get regular status reports.

If you would like to know why there might be a difference between missing and retired packages, I have the answer for you. This is quite common for EPEL packages. Even if a package is available in for example EPEL 6, it still needs active action by a maintainer to branch it for EPEL 7. Therefore packages in EPEL 7 might currently be missing and still become available. I, for example, hope that ipython will get into EPEL 7, but I read on IRC that some RHEL 7 package is not recent enought for a recent ipython release. Therefore it might take a while. Also for Fedora packages it might happen that a package is retired before the next release is branched (which is currently Fedora 21), therefore a package might be reported missing for Fedora 21 and retired for Rawhide/Fedora 22.

Keep in mind hat in about seven weeks a lot of currently orphaned packages will be removed from the EPEL repositories, if nobody shows up to maintain them. My script will help you identify packages, you might be missing, therefore it is now a good idea to join the Fedora package maintainers and adopt orphaned packages that are important to you.