This week is busy and continues to keep the pace of previous weeks. A lot has happened this week in the Fedora Project and I’ve taken on a few new tasks too. In addition to existing work on Google Summer of Code, Community Operations, Marketing, and more, I wanted to take some time this week to focus on CommOps Ticket #71. This ticket originally focused on improving accessibility of design resources for Fedora Ambassadors. However, after an interesting conversation with Máirín Duffy on the Design Team workflow, I discovered the availability was not the main issue. Instead, it seemed like communicating was an area needing focus.
I have been trying to implement private projects on Pagure, while doing that I was struggling with certain design of a function and while doing that I constantly have to switch between shell, editor and at times browser.
Think of this scenario: You're sitting at your shiny Fedora install and notice a kernel update is available. You get all excited, update it through dnf or Gnome Software, or whatever you use, reboot and then things stop working. "STUPID KERNEL UPDATE WHY DID YOU BREAK MY MACHINE" you might say. Clearly it's at fault, so you dutifully file a bug against the kernel (you do that instead of just complaining, right?). Then you get told it isn't a kernel problem, and you probably think the developers are crazy. How can a kernel update that doesn't work NOT be a kernel problem?
The typical method of installing Fedora on a desktop distribution is via some physical media (CD/DVD once upon a time, USB sticks these days). Fedora also supports PXE boot installation. I ended up doing a PXE install for some recent hardware that was shipped to me as that was the best supported method. The Fedora instructions are good but I still ran into a few hiccups. These are my notes which might be useful for others (or be wrong, YMMV). This was also a UEFI only setup.
Kamil got to it first, but just a note that UEFI roms for x86 and aarch64 virt are now shipped in the standard Fedora repos, where previously the recommended place to grab them was an external nightly repo. Kamil has updated the UEFI+QEMU wiki page to reflect this change.
Do-it-yourself site MakeUseOf recently highlighted Fedora Design Suite from their article “6 Linux Distros Designed for Artists, Musicians and Editors“. They also called the Fedora Design Suite as the “best of the basics”.
In order to be a great application developer, do you need to understand the stacks and orchestration? David Ward, CTO of Engineering and chief architect at Cisco Systems, Inc., argued that is not the goal. The underlying infrastructure is very complex, and if exposed to too much of it, an application developer may not write applications. Exposing that infrastructure is not the goal at Cisco Systems.