Hi everyone,

It can be difficult to keep track of things if you're not paying attention regularly, and even if you are there's always stuff all over the place. I've been working on ways to collate all of the things happening from across the community into a regular monthly report. Here's Jurassic January.

Changelogs are actually pretty weird in bootc land. We usually extract the package version info from the last rechunking step to generate the changelogs - however that doesn't really cover the entire project, just the things in that repository. There's also a new upstream rechunker coming down the pipeline so that means that we'll need to rework how we generate the changelogs (thanks to @renner0e for investigating this!). The existing changelogs also really only tell you about the things in the image, and not the "whole" of Bluefin. These will always continue to be published on changelogs.projectbluefin.io

These reports aren't a replacement for the changelogs, just as this blog will continue to handle most of the "Why?" we do things -- for us it's a good way to blog about the meta and not the minutiae.

We've divided Bluefin into the categories that match the labels throughout the project, so that we can organize things a little bit better. Each section looks like this:

Ecosystem​

Homebrew packages, AI/ML tools (Bluespeed), and Flatpak applications

Additionally each section is divided into two categories. "Planned Work" are things we're purposely working on. These usually need planning and organization and are tracked in todo.projectbluefin.io.

"Opportunistic Work" are things that people just work on day-to-day and may or may not have a plan attached to them. This is usually the bulk of the work. We also needed a way to track what's going into the production homebrew tap, and in general tell people when something is getting promoted. Here's the first attempt:

Homebrew Package Updates​

75 automated updates this month via GitHub Actions. Homebrew tap version bumps ensure Bluefin users always have access to the latest stable releases.

Quick Summary​

We also took the opportunity to add stats on the builders so you can check out Bluefin's health "at a glance". And lastly we wanted to highlight the contributors. New contributors ("New Lights"), will have a gold foil usercard to celebrate their first Bluefin contribution:

Each month will list every person that contributed to Bluefin for that month, so if you're keen, apply within! This section is incomplete, it does not include discussions and issues, so if you're working in those areas you're not getting a shout out yet, but we'll keep making improvements.

If there's an area of Bluefin that you're finding hard to keep track of leave feedback in this thread!

Discussion​

https://github.com/projectbluefin/finpilot

Originally I mostly just wanted to add copilot instructions to the Universal Blue template. Copilot does an awesome job just automating making a custom image so I kept driving in that direction.

If you are making a custom image I want you to try this!​

The existing templates mostly let you take Bluefin and modify it. But now with this new OCI layout, we can instead have you assemble your own Bluefin like how Aurora, Bluefin LTS, Bluefin, and dakotaraptor do it. This does a few things:

• Let's you be at least as good as any of those right out of the gate, your custom image is built by the production setup that's well known
• You can instead work on making the image
• All desktop agnostic config is centralized in @projectbluefin/common and set up in a way that you can extend it.

Tulip quickly took the Bluefin containers and a bootcrew ubuntu-bootc image to create an Ubuntu Bluefin.

A ublue-os/base-main base image + cosmic would make a COSMIC Bluefin the exact way we would build one. And as a bonus since the config and stuff is centralized any custom image built by consuming the centralized OCI containers has the benefit of shared maintenance.

Anyway if you're already making a custom Bluefin I'd like to encourage you consuming Bluefin this way, adding the few containers is documented in the README so you don't have to move templates or anything like that, you could probably do this in bluebuild too.

Discussions​

Today we're going to go over some of the things we're finishing up for 2025, and talk about where we're going in 2026. Check out the Autumn 2025 Update and the 2024 update if you want more backstory. We appreciate you joining us on your Linux journey, let's get going!

Companion Video if you wanna check it out!

Also check out:

• Aurora - Stargazer 5 - Year in review
• Bazzite “Spring Cleaning in December” Update

How was 2025?​

This year we spent most of our time on cleanup and sustainability. Bluefin is mostly feature complete so we don't really ship major user-visible changes as much as we used to. Much of it is "nerd automation" improvements that most of you will never need to actually care about. This has also been a kickass year for Bazzite, which has been a fantastic real-world test for bootc based sytems like ours! Overall the ecosystem is doing well, this year was great for bootc, here's a photo of the team from KubeCon this past November:

Jorge with members of the bootc team: Mark Russell, Joseph Marrero, Laura Santamaria, and Colin Walters

We continue to sync with the various teams at Red Hat as we journey with bootc through its CNCF Project Lifecycle. This works out well for us because we know what we need to do. Our role is to provide an independent voice, and with new orgs like the bootcrew, bluebuild, and secureblue springing up it brings more voices to the choir. 2026 will be the year where we expect participation in bootc to increase. This is also why you've seen us slowly decouple from Universal Blue more explicitly. This is a forcing function to move us away from monolithic "distributions" to an ecosystem full of different images, each with different communities and needs, while retaining the value of shared components.

As you'll soon see below, we can source software from anywhere and it's just a bunch of containers. This is reflected in our use of @projectbluefin as our new main GitHub org as we strive to move further away from distribution specific tooling to a cloud-native world.

But that sounds like a bunch of marketing crap, let's explain it ... this update will cover mostly "How Bluefin is made" and where we're hoping to head in 2026.

JF's Bluefin desktop

Tracking Progress​

todo.projectbluefin.io will send you to the project board. Every item in this post will be tracked here. Some of the things in this post are complete, and some are close and need help, feel free to dive in!

You may notice some minor changes (like the motd colors changing), but we're hoping to be complete with the major transitions over the next two weeks. File an issue if you notice something! Exercising the fix-loop with this new architecture will immediately show dividends as we can now ship fixes to all Bluefins and Aurora.

We've also updated the Contributing Guide to reflect Bluefin's updated architecture and processes. Note, Linux nerd stuff incoming:

Architecture Overview​

Bluefin is undergoing a refactor with some significant changes under the hood, which we expect to finish soon, but is mostly there. Some of this isn't done yet, so I'm going to talk about the endstate of where we want to be. Bluefin is a combination of a set of configuration OCI containers which are then shipped on different images. Originally the Bluefin repository had everything we needed, and was a result of organic growth. Everything was built here.

The team drastically refactored this repository in 2025 since it predates the usage of bootc and was falling behind. Similarly, Bluefin LTS was built from the ground up on bootc, but we had to manually bring over the Bluefin parts to build it. We want to share as much code with Aurora and Bazzite as we can. The three projects share many things, but we needed a more efficient way to do this. "One big Bluefin" wasn't going to cut it. So we rearchitected Bluefin to the following model:

Bluefin OCI containers​

These are what make up the bulk of Bluefin and are shipped as OCI containers. This moves us away from classic distro packaging and towards a pure cloud native approach. We're migrating away from the packaging repo and instead keep all the config files in an easy-to-read tree in git, that just gets copied over in the build step:

• @projectbluefin/common - Most of Bluefin's opinion on distro experience is here
  • ujust, motd, service units, GNOME and CLI configuration, application choices, etc. Most things that have to do with the workload should live in this repo
  • This is shared with Aurora so that we can maintain consistency across images
• @projectbluefin/branding - Branding assets that we don't want to keep in the common repo
• @ublue-os/artwork - Art assets repository, shared with Aurora and Bazzite
• @ublue-os/brew and associated @ublue-os/homebrew-tap - these provide homebrew itself and our selection of custom brew packages. This also simplifies adding homebrew to custom images. Thanks to those of you who have been helping homebrew be better on Linux, it's amazing!

These containers have the advantage of making consumption by other bootc projects trivial and are (mostly) distribution agnostic. Custom images now have a granular option to pick and choose the components they want to ship instead of dealing with one monolithic experience. We've structured the common repository to be extensible, here is how Aurora does it for reference. This allows the team to keep configuration centralized while allowing endpoints for custom builds.

Final assembly...​

Once we've established a set of re-usable components, we then combine them with a base image that make the final operating system:

• @ublue-os/bluefin - Bluefin: generates a Fedora-based Bluefin OCI container
• @ublue-os/bluefin-lts - Bluefin LTS: generates a CentOS-based Bluefin OCI container
• @projectbluefin/distroless - Dakotaraptor prototype - generates a GNOME OS based Bluefin OCI container (more on this below!)

Since the bulk of what makes Bluefin is now just an OCI container the base OS can more easily be abstracted away. This means that these repositories can now do way less than they were doing before. We will continue to prune these over the course of this year.

A Streamlined, Maintainable set of Images​

Decoupling Bluefin this way has already allowed us to delete a bunch of duplicated code, and makes maintenance easier for the team. This also makes it way easier for people to contribute and resolves a bunch of parity bugs between the images. Maintaining Bluefin happens in the common OCI layers and not as much in the image repositories. Custom images will start moving this way too as it let's custom image builders pick and choose from whichever container they want at a much more granular level.

This also gave us the opportunity to clean up a bunch of old justfiles and scripts that have not been looked at for years. Our new justfiles are much smaller and more maintainable. We also took the time to add confirmation dialogs and other quality of life features in there. We have also been taking a less-is-more approach by shipping less customizations as just recipes.

Thanks for your patience with this transition, it did take longer than expected but we took our time since we're planning on long-term maintenance first. This is the smallest that Bluefin has ever been!

Looking forward to 2026​

I had to explain how Bluefin will be built in order to explain the changes coming. These are the user-visible changes that you can expect in 2026:

Bluefin​

As covered in - Streamlining Bluefin Releases we will be merging the bluefin:gts images into bluefin:stable. Effectively we're merging them both.

We wanted to commit to a date as soon as we could, and will be moving you to a Fedora 43 base that week. And then everyone will be upgraded to a Fedora 44 base about a month later. Note that this won't be a zero-day upgrade and will follow the usual CoreOS cadence. By then the next -> testing -> stable workflow will be live and you'll be able to opt into the newest versions at your leisure. If this is confusing to you don't sweat it, we'll be more communicative when March rolls around to keep the transition as smooth as we can.

This will also be this single most user-affecting change in Bluefin for 2026, and we're really looking forward to having a proper gitops workflow with testing branches!

Bluefin LTS​

Some of you may have noticed parts of GNOME 49 landing in Bluefin LTS. Originally we had planned on backporting GNOME ourselves but this is happening as part of CentOS Stream's lifecycle. This "feels" like a good cadence for an LTS. Here's the lowdown on where LTS is today:

• The tuned policy still needs a fix, this makes you have to run a workaround to get power management working on a laptop. This sucks
• Many of the inconsistencies will be resolved once Bluefin LTS moves to the common OCI layers

The hardware enablement branch brings in the Fedora kernel so you do have a nice option to not fall too far behind. This has effectively replaced Bluefin GTS by bringing a relaxed desktop upgrade cadence and less regressions overall. The lts-hwe branches also now support secure boot. Despite these papercuts this is the image I use on my work machines, and the new architecture will help here.

Bluefin's Distroless Future​

Thanks to Sri Ramkrishna for contributing to this section

It is impossible to ignore the fantastic work happening in the the Linux Userspace API (UAPI) Group. Thanks to the work done by the bootcrew and Jordan Petridis it is now possible to decouple Bluefin from a traditional Linux distribution base image entirely and combine both UAPI and bootc approaches into one OS.

This new Bluefin is nicknamed Dakotaraptor and will be our attempt to ship a production quality bootc image based on GNOME OS. This gives us some benefits that we can't get from other images:

• Faster deployment of the best tech: systemd-boot, systemd-homed, and other UAPI tech will ship much faster here - we can finally say goodbye to grub forever!
• Testing branches with development versions of GNOME so that new contributors can help upstream development
• New GNOME and systemd teammates who are committed to driving and shaping the modern Linux desktop. This has been a boon for us since we're forging new working relationships with these upstream projects, and their help will keep us on the leading edge.
• More "take charge our destiny" by working with our critical upstreams directly instead of waiting for traditional distributions to catch up

Dakotaraptor will not be for everyone and will offer the least amount of compromises. Not only is local layering unsupported, there's no system package manager at all! We'll be using Buildstream since it's the tech behind this, and you'll hear more about it in 2026 as other projects check it out. This effort is still nascent, so no promises, but it's already got people excited, check it out at @projectbluefin/distroless.

JumpyVi's setup

Don't worry, we won't call it "Distroless".

The other Blufin OCI containers will still continue as before. Dakotaraptor will represent a faster development cycle, directly pulling from upstream, while maintaining production quality. Think of "distroless" as a model flip, the source is the main thing we interact with, the Linux desktop, and that's GNOME. And then we can bolt on whatever kernel we want, with modern Linuxes this is straightforward to make. And since the system libraries for GNOME OS are just ... the Freedesktop and GNOME runtimes, we're running on stuff that's already used by a ton of people. This way of assembly is new, but the payload is not.

That's why we're feeling confident about the quality out of the gate on this one. That just leaves a set of automation scripts and some config files, that's Bluefin!

We haven't yet finalized how next -> testing -> stable will look like, but having the next branch following the nightly GNOME development cadence is a goal. This channel will be our fastest raptor with aggressive component upgrades and no holds barred. The stable branch will be based on the stable GNOME builds and we're hoping to help GNOME maintain these branches. If you want to be part of this effort, now is the time to step up!

Oh, and in order to help us out with this you don't even need to talk to us, just go talk to GNOME directly. "Distroless" means spending more time with the things you love, and not so much time with the delivery service. We're mostly just waiting for GNOME 50 to come out. Expect this one to be VM-only for a while.

Refining the Bluefin Developer Experience​

About 60% of you turn on Bluefin's Developer Mode. We purposely focus on these 15.6 millions developers and strive to deliver the world's best cloud native development experience.

Now thanks to the efforts from the team homebrew is now in a much better state on Linux, allowing us to reshuffle some things around. In 2026 we will strive to remove the need for a dedicated bluefin-dx image and give you more flexibility moving forward:

• IDEs won't be baked into the images so you can use what you want.
• Homebrew will continue to be our path forward for IDEs - we hope to drum up interest so that the upstream projects can just "turn on" Linux builds in Homebrew. In the meantime we'll ship the major IDEs we need.
• We've added containerd to the base images and will bring Docker in as well so that everything works out of the box, there will not be a need to do the adduser mumbo jumbo, we'll take care of that for you. Research in this area is still ongoing!
• How we'll accomplish this transition is still a bunch of guesstimates, so consider this one a slow burn.

Curated Developer Experiences​

Thanks to to Vito Castellano from Bold Brew for continuing to improve the experience! Check out the Bold Brew v2.2.0 post to get more info! We've got all the issues fixed so this menu should work great moving forward. The intent is less stuff baked in, and more options, that you can freely install and remove. Note that these will also all work on any Linux with Homebrew:

The first is our ide selection, which offers a selection of VSCode, Codium, and Jetbrains toolbox for graphical IDEs, as well as nvim, helix, and micro for you CLI nerds.

The experimental-ide selection includes the individual Jetbrains products if you prefer to install those one-by-one, as well as Antigravity and Cursor. These will be promoted to the production tap as we get more feedback. We've also started to add Swift tools into the list so that we can tap into this exciting open source community!

Thanks to the new flatpak support in brewfiles we can ship all sorts of combinations now!

And finally, thanks to our custom tap we are investigating on how to bring bluefin-cli to MacOS, so that you can have these same convenience tools on multiple operating systems. James has a prototype that you can check out.

AI/Machine Learning Tools​

aka "Bluespeed"

Our AI toolset continues to expand. I'd like to highlight goose as a tool that I have been really digging into lately. Its donation to the Agentic AI Foundation makes this a great choice for your local LLM/CLI needs.

We've also added Codex, Copilot CLI, Gemini, LM Studio, Mistral Vibe, and Qwen Code to the list. Please continue to send us feedback on the tools you use.

Other Goodies​

And here's the stuff that doesn't fit anywhere else in this report!

• Consolidated ISOs - we'll be centralizing ISO building into one repository and plan on having regularly refreshed ISOs every month
• Powerwash is here! - ujust powerwash is now in alpha and ready for testing - use this command if you want to blow away the data on your PC for donation. This wraps the bootc install reset --experimental command for convenience behind some confirmation dialogs. Be careful with this one! Check the bootc documentation for more info
• Actually Going to Market (GTM)
  • We're almost to the point where we can start to market Bluefin instead of purposely going under the radar
  • Investigating refreshed video content for the website - this will be expensive so we probably won't look into this until after the user-visible features have landed
• Updated Contributor Guide

Metrics​

On to the numbers! First off let's look at our critical upstreams. This level of growth confirms our decision to trust in systems that prioritize application developers.

• Flathub 2025 year in review - 20.3% Year over Year Growth, and Bazaar continues to get better all the time.

As you can see, we not only bet on Flathub, we worked with the folks at Bazaar to ship a pure Flathub experience on our images. If you're looking for one thing to donate to in 2026, please consider donating to Kolunmi - app development on Linux will never improve unless we invest in the application ecosystem directly.

• Homebrew Yearly Statistics - Bluefin (#11), Bazzite (#12), and Aurora (#15) have a strong showing in homebrew usage

This year we moved to LFX Insights as our platform. Here are our complete contributor metrics and a few charts. You can also always check out all our charts on our Analytics page, where we've finally crossed the 3k weekly users milestone!

I've selected some graphs, feel free to dive in and don't forget to check out Aurora and Bazzite too!

Development Roadmap(ish)​

Here's some important dates

• January 2026 - Bluefin LTS and Bluefin's transition to the common OCI containers is complete
• March 1, 2026 - Bluefin GTS moves to a F43 base and is merged into Bluefin
• April 2026 - Bluefin upgraded to F44 base (this includes all the former GTS users)
• Spring 2026 - Dakotaraptor alpha released

See you in 2026!​

This year the team plans to attend SCaLE again as well as the following conferences:

• KubeCon + CloudNativeCon Europe - see you in Amsterdam!
• KubeCon + CloudNativeCon North America - see you in Salt Lake City! The game is afoot, the key is: lumina.

This ended up longer than anticipated, thank you for joining us in 2025, and we look forward to working with you in 2026! And lastly if you've made it this far and still want more backstory, make sure you check out this interview with Michael Tunnell:

Discussions​

Leave a comment or question!

Homebrew​

Homebrew's path will now be placed after the system path. This will cause brew doctor to complain, but we feel that this will lead to a cleaner experience overall. This has been working well in testing, and the change is already on the daily builds if you're using one of them.

Bluefin CLI​

Atuin has been causing some issues, so we've disabled it by default to ensure a stable experience with bluefin-cli. We plan to investigate a better integration for Atuin in the future.

More updates coming​

We will be publishing a large year-in-review update next week that will cover these topics in much more detail, but we wanted to give you a heads-up on these behavioral changes before they land. In the meantime, we've set up todo.projectbluefin.io for you to follow along with the major changes coming in Bluefin. Thanks!

Discussion​

COPY --from=ghcr.io/ublue-os/brew:latest /system_files /

On first boot, the brew-setup.service automatically extracts Homebrew to /var/home/linuxbrew/.linuxbrew, sets up proper permissions, and makes it ready to use. The image also includes timers for automatic updates and upgrades, keeping your Homebrew installation current.

This removes a bunch of the manual stuff you had to do in your template to get the full thing, now it's much easier and reliable for everyone. Once we're done the container will rebuild after a Homebrew release, keeping us up to date and safe!

Check out the repository at github.com/ublue-os/brew for more information and examples.

Thanks!​

This work and testing brought to you by:

Discussions​

We're excited to announce two beautiful new wallpapers: Andy Frazer's latest creation Huntress, and a festive holiday wallpaper from Aurora.

Huntress by Andy Frazer (Dragons of Wales)​

Original Bluefin artist Andy Frazer returns with Huntress, a stunning new addition to our wallpaper collection. Following his previous work on Dusk, Andy continues to bring his distinctive paleoart style to Bluefin. We were going for a more weathered Bluefin this time around. No longer the ideal one perched on a rock ... this one has been through some things.

Andy's books make excellent gifts for dinosaur enthusiasts of all ages. Check out his Etsy shop for his full collection of paleoart books and prints.

Holiday Blues by Chandeleer​

This next one is by Chandeleer and captures all of the mascots from Aurora, Bazzite, and Bluefin playing in the snow.

If you enjoy Chandeleer's work, please consider supporting them through their Ko-fi page.

How to Install​

These wallpapers are available through the @ublue-os/homebrew tap. We've finally solved the teething problems with the tap and we now consider it production ready. You can install them using ujust bbrew and selecting the artwork option: (this is broken right now sorry). We do not yet ship these by default so right now they are opt in:

Installing Bluefin Wallpapers Extra​

To get the Huntress wallpaper and other extra Bluefin wallpapers:

brew install ublue-os/tap/bluefin-wallpapers-extra

And for the Aurora artwork:

brew install ublue-os/tap/aurora-wallpapers

Download Directly​

You can also grab these wallpapers directly from the artwork repository:

• Huntress
• Holiday Blues

Happy holidays from the Bluefin team!

Discussion​

Driver Versions Page​

Regressions suck. And it also sucks finding out where they happened, especially with the power of bootc switch available! What good is a switch if you don't know where to switch to! I hate looking this up by hand, so we whipped this up:

The Driver Versions page tracks kernel, NVIDIA driver, and Mesa versions across all Bluefin release channels. This consolidated view makes it straightforward to:

• Troubleshoot driver-specific issues - If a recent update broke something, you can identify exactly which driver version changed
• Switch to specific versions - Each release links directly to the GitHub release notes and includes bootc switch commands
• Compare channels - See how stable, GTS, and LTS differ in driver versions at a glance

The page includes direct links to upstream release notes for NVIDIA drivers and Mesa, so you can dig into the details when needed.

Improved Extensions Section​

The Tips and Tricks page has a new refreshed look with extension thumbnails. We haven't touched these in a while, but the reason I was there was to add Copyous to our list of recommended extensions. This thing is so good! It puts a strip of clipboard items on the top that you can summon:

Kick the tyres and let us know what you think!

Discussions​

Check out TuxDigital and This Week in Linux.

Discussions​

What's New​

Homebrew Bundle now supports Flatpak packages on Linux. This means you can declare your Flatpak applications in your Brewfile and have them installed automatically with brew bundle.

Note from Jorge: I haven't played with this feature yet but announcing it so we can get feedback right away.

Basic Usage​

Add Flatpak packages to your Brewfile using the flatpak directive:

# Brewfile
brew "neovim"
flatpak "com.spotify.Client"
flatpak "com.visualstudio.code"

Then run:

brew bundle

Remote Support​

Homebrew Bundle supports three ways to interact with Flatpak remotes:

Default Remote (Flathub)​

For packages from Flathub (the default), just specify the app ID. Most of us will use it this way:

flatpak "com.spotify.Client"

URL Remote​

For packages from other repositories, specify the remote URL:

flatpak "org.godotengine.Godot", remote: "https://dl.flathub.org/beta-repo/"

Named Remote with URL​

For shared remotes that you want to reuse across multiple packages:

flatpak "org.godotengine.Godot", remote: "flathub-beta", url: "https://dl.flathub.org/beta-repo/"
flatpak "io.github.dvlv.boxbuddyrs", remote: "flathub-beta"

Commands​

All the standard brew bundle commands work with Flatpak:

• brew bundle - Install Flatpak packages from your Brewfile
• brew bundle dump - Export your installed Flatpak packages to a Brewfile
• brew bundle cleanup - Remove Flatpak packages not in your Brewfile
• brew bundle check - Verify all Flatpak packages are installed
• brew bundle list --flatpak - List Flatpak packages in your Brewfile

Check out the brew bundle documentation for more information.

Dump Options​

# Include Flatpak packages when dumping (default on Linux)
brew bundle dump

# Exclude Flatpak packages
brew bundle dump --no-flatpak

# List only Flatpak packages
brew bundle list --flatpak

Why This Matters for Bluefin​

This feature allows Bluefin users to maintain a single Brewfile that manages:

• Command-line and GUI applications in one file
• Lightweight gitops between all of your machines
• Paves the wave for better Homebrew/Flatpak integration

The huge community benefit is the shareability of a list-o-files. You can give your friend the hookup, and in fact many of Bluefin's "features" are just us shipping our own Brewfiles. For you experts out there this likely just simplifies something you probably already have. And for those of you just starting your command line spec tree it's a nice milestone to hit: "I can get a new install up and running in 10 minutes". There's lots of ways to do this, but this is an easy one. 😄

Woo! We feel that this is a nice complement to devcontainers, providing even more flexibility to your workflows!

How does it work in practice?​

You're going to have to tell me, I am on holiday in the German countryside, but this feature is super exciting and I'm looking forward to hearing your feedback!

Refer to the Homebrew Bundle documentation for more!

References​

• Pull Request: Add Flatpak support to brew bundle
• Issue: Feature Request - Add Flatpak support to Brewfile

Also Check Out​

Speaking about "Easiest way to get a clean install in 10 minutes", SaveDesktop is the nice GUI way to do this. You'll always find it in Bluefin's Curated section in the Bazaar app store. (Tell your friends!)

Discussion​

Natalia Jagielska​

Our newest collaboration is with Dr. Natalia Jagielska, a world renowned expert paleontologist and paleoartist! I've always been a huge fan of her art style and she has graciously given us three wonderful pieces of art. The first you probably already recognize since it's been the wallpaper of the month for November, entitled Collapse:

The second is an homage to Ubuntu's famous Hardy Heron wallpaper, originally designed by Ken Wimer. This one is a mashup of one Natalia's pterosaurs in place of the heron. This one is called Tenacious Pterosaur.

And lastly we have Prey, starring a hungry Venetoraptor gassenae, which is a pterosaur ancestor from the Triassic. This one surprised me, I thought it was a mammal at first!

Natalia's artwork was vectorized and remastered by Delphic Melody, please consider donating so that the collaboration can continue!

Andy Frazer (Dragons of Wales)​

Original Bluefin artist Andy Frazer returns with Dusk. I love this one.

Also Andy is working on another Bluefin for us, which I haven't seen yet. I can't wait to find out! Andy also has a 25% off special on all his books. I have a few of these and they are not only awesome to own but make great gifts as well.

How to get them​

This is not yet included by default so you can hop in early with a ujust bbrew and select artwork. In the future this will be automated for you:

bluefin-wallpapers-extra will bring this collection in. Also you will notice that the Aurora and Bazzite artwork collections are available. This tap is distro agnostic so go nuts putting dinosaurs, cone people, and mechs everywhere!

You can also just grab them from the repository if you prefer to do it that way. Stay tuned for a special holiday wallpaper, coming soon!

Discussion​

A few minor updates today, you'll receive these updates either today or tomorrow depending on the build you're on. Our first is some updates to our usage of just. Just is a task runner that we use to ship community aliases. Our justfiles are ancient, some going back to the beginning of the project. We are consolidating most parts of what you call "Bluefin" into a common repository. These are all mostly scripts, there's nothing distribution specific about them.

We wanted to centralize this because keeping Bluefin and Bluefin LTS configs in sync is too problematic. In this manner we can make the Bluefin parts easily plop onto any image no matter what the image is.

It also means we cleaned out some broken stuff, and are down to just 34 just recipes, which makes all of this sustainable, especially since we're sharing the maintenance with Aurora. All the recipes now include confirmation dialogs and have been refined. I am glad we got this done because this part of Bluefin was really starting to show its age! Thanks to @tullilirockz for working on this! Thanks to @hanthor for implementing it in Bluefin LTS! Run ujust or ujust --choose to get started!

Bold Brew and Brewfiles​

We now have a nice way for the community to contribute to Bluefin's Brewfiles.

We workshopped some ideas on how to make this nicer for users. We approached bold-brew with the idea of presenting Brewfiles to users in a dedicated view. Vito was very accomodating and implemented the idea, kudos to him! Now let me show you how it works:

ujust bbrew is the entry point, we will generate a little menu for you for every Brewfile in Bluefin. So if we add more they just show up here. Then after you choose one bbrew will open up showing you that Brewfile. You can then select and choose what you want to install, or hit Ctrl-A to grab everything.

Bold Brew is to Homebrew what Bazaar is to Flathub​

This is awesome because we can now curate app bundles of CLI tools to users. We're starting off with AI tools, k8s tools, and monospace fonts. Feel free to send PRs to these Brewfiles, since users can pick and choose we can ship the tools you depend on the most. You'll also notice some color improvements in bbrew, make sure you check out the repo and give them a star!

More Cloud Mumbo Jumbo​

And lastly, we now have ujust cncf, which will show you all of the projects that are part of the CNCF. Many of you work with these tools every day, the hope is to show you all of the cool things you can play with in cloud native!

More Consistent Bluefin​

Ultimately this consolidation of all of our config will lead to better Bluefins and has been a primary source of parity issues between Bluefin and Bluefin LTS. Bluefin continutes to actively shrink over time!

We still have work to do, like the motd, bling, and all that other stuff but we'll keep you up to date!

Discussion​

We're doing this for a few reasons:

• The value GTS provided is "older software works better". What it really means is "no one messed with this", changes still made in Bluefin affect this branch immediately.
• bluefin:latest - this one is an antipattern, you want to be able to pin something, and people make assumptions of what it means. We'll transparently move you to bluefin:stable-daily.

If you're new here there's no need to panic, bluefin:gts and bluefin:stable always share the same version twice a year for a few weeks. We're in that period now, they're both at Fedora 42.

In the meantime let's pretend it's out so that we can continue to Bluefin's new model. The workflow looks like this currently:

Current Bluefin (November 2025)​

This has resulted in confusion, especially as Bluefin LTS has come up to speed. So starting in the Spring of 2026 we're moving to this layout:

Future Bluefin (Spring 2026)​

Changes and Rationale​

At first this looks like a rename, so let's go over the changes:

• bluefin:next - all changes will land here first. We make no stability guarantees. It will build daily. This will not replace bluefin:latest because we will for sure break things in here. This will build at least daily and every time a change lands
• bluefin:testing - When changes in :next have been tested by at least one person they queue up to land in testing. We anticipate things to sit in here for a week or two at a minimum unless we need to fix a regression. This builds daily.
• bluefin:stable - This is effectively the current version of Fedora, except all changes going into this will have at least be vetted by the previous branches.

We do NOT have this promotion process today. This is the goal. If you are on bluefin:latest we will point you to bluefin:stable-daily so that you are still getting daily builds. We purposely are not moving you to next because that will be volatile. Both the next and testing branches will be opt in.

Benefits​

For You​

• Less confusion, you either download Bluefin or Bluefin LTS.
• Better testing in general as we add tests to each step before promotion
• TLDR: Everyone moves to bluefin:stable in the Spring, and those of you who want newer stuff can opt into testing and next

For Us​

• Testing workflow allows for super fast iteration and two stages of testing before hitting end users. This is the #1 reason to do all of this
• We no longer have to keep GTS bits around the rest of the org to support it, freeing up builder space and resources
• Better alignmed with Fedora CoreOS development

This does mean that we will no longer be shipping the stock Fedora kernel in any branch. We're fine with this since we prefer to keep all our users on a gated kernel.

Discussions and Questions​

This Q3 2025 "State of Cloud Native Development" study shows this group now makes up nearly a third (32%) of all developers worldwide. This explosive growth is driven by the mainstream adoption of projects like Kubernetes, OpenTelemetry, and others. The project we depend on the most, bootc, is a CNCF Sandbox project.

This represents remarkable growth from the Q1 2025 survey, which reported 9.2 million cloud-native developers—a 70% increase in just seven months.

Discussion​

• Murder Chickens: Weekly count of Bluefin users.
• Bazaar Installs: Weekly count of package installations from Bazaar.

Expect it to land in next week's build, enjoy!

Discussion​

Guardians, today Bluefin GTS switched its base from Fedora 41 to Fedora 42. The gathering of raptors has begun. In a two weeks Bluefin (aka bluefin:stable) releases on Fedora 43 and we will start the cycle all over again!

Looking for Fedora 43? That's here too in bluefin:latest, and will roll out to bluefin:stable users in 2 weeks. It's tough to write two of these, so we'll likely just move to spring/autumn announcements and whenever major things land. When bluefin:stable upgrades I will post it as an addenum in the discussion thread for this post.

Introduction​

As it ends up F43 will be coming to bluefin:stable while we're in Atlanta, GA, for KubeCon + CloudNativeCon, come say hello! As a bootc reference architecture we tend to align with the release cadence of other projects. This usually means that I'm on the road when there's a Bluefin release happening, so we do status reports like this depending on where we are in the world at the time, and to ensure transparency. It's also our chance to gather with attendees and get feedback on how we can make Bluefin better and gather feedback.

You'll receive this update during your next update window, or you can run an update manually by clicking on this icon:

If you've never experienced a Bluefin upgrade before, McPhail has a full writeup. Here's the major release information:

• GNOME 48 release notes
• Fedora 42 release notes
• Bluefin changelog - detailed changes

What is Bluefin?​​

Bluefin is an operating system for your computer. It is designed to be installed on a device upgrade for the life of the hardware – we accomplish this by sharing the maintenance and care of our systems together as a community. It is designed to be as “zero touch” as possible by providing a curated GNOME experience.

Bluefin GTS (aka bluefin:gts) is our standard release, designed to be one cycle behind the most current Fedora release. This one's been in the oven for about six months and is ready to go. In a few weeks the bluefin:stable branch will move on to Fedora 43. If you're brand new you can use the website to pick the right image or select from the grid below:

Welcome to Bluefin​

This unidentified Dromeasaur is by Dr. Natalia Jagielska, a world renowned expert paleontologist and paleoartist! We reached out to work with her on bringing her artwork and style to Bluefin, and she said yes! This rendition will be revealed in November, or you can just manually pick it in the wallpaper chooser.

I am so stoked about this, an actual scientist! We're retconning that this is just Bluefin enjoying a nice day at the lake. We have two more wallpapers from her coming soon. I have come to really appreciate the world of flying reptiles. They are terrifying.

Natalia's artwork was vectorized and remastered by Delphic Melody, please consider donating so that the collaboration can continue!

Major Changes​​

There are a few major changes from a Bluefin perspective that we've been looking forward to:

Installation Experience​​

• The Anaconda web-ui installer is now the default installer, dramatically improving the experience. We say goodbye to the old GTK Anaconda installer.
• We'll be automatically refreshing all the Bluefin ISOs once a month to ensure the installation media is fresh.

Introducing Bazaar​

Bazaar makes its debut in Bluefin GTS! All Bluefins are now just using the Bazaar flatpak. You're in for a treat:

It's been super awesome seeing Bazaar move from a random project we found on r/gnome to what is effectively now the premier app store experience for FlatHub and Linux. You can help out tremendously by sponsoring the author.

This is also a major milestone for Bluefin since we've effectively done our part for the GNOME and FlatHub ecosystems and can now consider application installation a solved problem, we can introduce new things into Bluefin as a flatpak to begin with and move us away from distribution specific formats.

I am finding more applications now than I ever have. It's also a milestone for all Linuxes since flatpak's upcoming release gives us the flexibility to do this in a proper way with full lifecycle management. We can now be more flexible with the applications we can ship mid-cycle by plopping a file in /etc/preinstall.d. Those of you making custom images will really take advantage of this!

Shoutout to Sebastian Wick for this work in Flatpak and working on the next release of this cool tech!

Homebrew​

Speaking of packages, we've been doing more work engaging with Homebrew developers, check out this interview I did with Workbrew talking about our hopes and dreams:

Let us know if you're interested in working on Homebrew for Linux, we have opened a homebrew tap so that we can interate on bringing cool new things to you. A huge shoutout goes to Yulian Kuncheff and Ahmed Adan for spearheading this effort, please consider donating!

Fonts​

The fonts have been a disaster for a long time, we're finally ripping the bandaid off and removing a bunch of fonts from the image. For you command line nerds you can install any of the fonts listed in Homebrew or use a tool like Embellish to install more fonts.

If you're in developer mode you can bring the monospace fonts back with ujust bluefin-fonts.

Tailscale​

We've dropped the GNOME Quick Settings extension for tailscale in favor of the upstream system tray implementation. For more information, check the docs, this requires manual set up.

• Linux systray application - these docs will get your tailscale icon going in your tray.

The tailscale experience is still not where it needs to be, but now that Tailscale has started work on an official system tray implementation we expect this to solidify over the next few upstream releases.

ujust commands returning​

After a hiatus we've finally refactored the Homebrew management in Bluefin. We're adding back some convenience commands:

• AI & Machine Learning Tools: run ujust bluefin-ai to install them.
  • Learn more in the AI and Machine Learning documentation.
• Kubernetes Tools: Run ujust bluefin-k8s to install them.
  • For a full list of the tools, check out the Kubernetes documentation.
• Developer Fonts: Run ujust bluefin-fonts to install them.
  • See the full list of fonts in the Fonts documentation.

Removal Notices​​

Extinction is a natural part of life. After a deprecation cycle the following images are now removed:

• Nvidia Closed Images: Due to Nvidia's software support changes we can no longer support the older closed modules for Nvidia cards. Not many people are using these, either migrate to the nvidia-open images or move to a stock image to use the built in kernel drivers.
• Bluefin HWE Images: Not many people were using these, they have also been removed.

Repository Changes​

As usual most of the changes we do in GitHub to deliver Bluefin and not so much in the image itself. Major parts of the Bluefin repository have been cleaned up to align with the improvements and lessons learned from building Bluefin LTS earlier in the year. This has been the bulk of the work in the past few weeks.

Bluefin has significantly been simplified, now would be a great time to contribute as we've brought the repository up to the state of more modern bootc projects like Bluefin LTS.

• bluefin:gts and bluefin:stable will be publishing on Tuesdays from now on instead of Saturdays. Publishing on Saturday nights is an artifact of pre-automation "reserved time" for testing before a weekly release. This matches the same release schedule as Bluefin LTS.

More Information​​

Bluefin is a deinonychus, and may snap at you occasionally. Four year olds can get feisty of so there might be issues that you discover that we haven't seen before. Filing issues is always appreciated.

• Bluefin Documentation
• Universal Blue

We also accept donations to sponsor the infrastructure and artwork.

Helping FlatHub​

Sometimes starting in open source can be a real barrier if you don't know where to start. Don't have the skills to do cloud native things yet? Here's a good way to help out FlatHub. Flatpaks rely on what we call "runtimes" to ensure that the application has the dependencies it needs to run. Do a flatpak list to check them out:

Flatpak Tracker is a site we made that will check all of the applications we ship in Bluefin and see which runtimes need to be updated. We label them by image, here's the the list of applications that need to be updated.

This is important work because we want applications to be updated to the latest runtimes for security reasons. As it turns out, many of these applications have OPEN PULL REQUESTS already with people updating the runtime, you just need to find the app, run the updated version by following the instructions, and then report back to the Flatpak maintainer that the new app is working great (or broken!). Since GNOME 49 just released, there's plenty to do, so feel free to dive in and get started! Also remember, this work helps all of FlatHub, we're explictly sending new volunteers to help upstream.

Find your favorite app and see if there's a test build available for a new runtime. And if you have the skills to port applications to new runtimes, now is the time to flex. 😄

store.projectbluefin.io​

Check out store.projectbluefin.io and pick up some dino merch. Thanks to John Johnson for ensuring our coffee mug game is up to snuff:

Is that it?​​

Nothing makes ops people happier than uneventful things.

Today is really like any other, we just updated a few tags, you always have the option to go to any version we support at any time. Wether you like the chill vibe of bluefin:gts or the refined aggresiveness of bluefin:stable , the raptor abides.

Here's the current lay of the land:

NOTE: The stable and stable-daily branches will move to F43 in two weeks.

Desktop DevOps folks wanted!​​

Bluefin is an active predator and is constantly hungry. You can help keep Bluefin healthy by becoming a contributor! We are an open source project and accept contributions:

• Help Wanted issues
• Contributing Guide

As a cloud native project we are always looking for contributors with skills in Podman, Docker, CI/CD, GitHub Actions, and good ole bash.

Bring on the Charts!​

Let's take a look at our contributor health, and celebrate the amazing folks who have come together to bring you Bluefin! We use LFX Insights to measure our project health. First note that my results here are skewed, since I am either usually just merging or telling a bot it's ok to do something. This also does not include the rest of Universal Blue. Yes, Aurora people basically maintain both, haha.

This next one surprised me, I was expecting 20 or 30ish at best. Nice work ya'll!

Haha yep, I can't hide from the data though, free me from this!

Feel free to browse around and learn cool things about Bluefin's creators.

What's Next?​​

After KubeCon we head into the holidays, where things will slow down significantly. We've been in the lab with mad doctor Timothée Ravier and have been cooking up something. We expect that this will change the course of Bluefin for the better, forever. We can't wait to show you, until then, enjoy!

Discussion Thread​

I was thrilled at the opportunity to team up with Pragyan Poudal from Red Hat to showcase Bootc along with Bluefin's vision for desktop Linux to a packed house at IndiaFOSS 2025 in Bangalore this past weekend. I managed to make only a handful of Linux users mad. It was a great chance to spread the word about image-based bliss.

After nine months of development Bluefin LTS and Bluefin GDX are now Generally Available(GA). The reign of Achillobator has begun. Find the download links on the website, or snag them below.

Bluefin LTS is a workstation designed for people who prefer Long Term Support but desire a modern desktop. This species of raptor is for users who prefer a slower release cadence, about a three-to-five year lifespan on a single release. Like other Bluefins it features first-class support for Flathub via Bazaar, Homebrew, ZFS, and all the other goodies.

Bluefin LTS is composed of:

• Mostly the same packages of Bluefin and Bluefin GTS, but built with CentOS Stream 10 and EPEL for extra packages.
  • The same features since they share the same source RPMs, just built on CentOS
• A backported GNOME 48 desktop
• ARM (aarch64) based images

Bluefin LTS also offers a hardware enablement branch (bluefin:lts-hwe) with:

• Updated Linux kernel, currently 6.15.9.
• Toggle between branches with ujust rebase-helper.
• Dedicated HWE ISOs for newer kit

Rationale​

Bluefin LTS ships with Linux 6.12.0, which is the kernel for the lifetime of release. An optional hwe branch with new kernels is available, offering the same modern kernel you'll find in Bluefin and Bluefin GTS. Both vanilla and HWE ISOs are available, and you can always choose to switch back and forth after installation.

I have been dogfooding Bluefin LTS for most of this year. This is the most "work focused" image and is suitable for "set it and forget it" style desktops. We are proud of this one!

Here's how I pitched the idea earlier this year:

A modern GNOME Desktop​

Bluefin LTS provides a backported GNOME desktop so that you are not left behind. This is an important thing for us. James has been diligenlty working on GNOME backports with the upstream CentOS community, and we feel bringing modern GNOME desktops to an LTS makes sense. I may be old but I'm not dead!

A very special thanks to Jordan Petridis from GNOME for technical advice and review.

New Installation Experience​

Installation is via a live session with the new Anaconda webui. This installer is miles better than the ones we used to ship, thanks to the Anaconda team.

Secure boot and all those goodies are available:

Update Cadence​

Updates will come as often as we need them for now and will settle into weekly releases on Tuesdays. Follow updates on changelogs.projectbluefin.io.

Errata​

There are a few lingering issues that will take more time:

• hwe doesn't have secure boot - we hope to revisit later this fall
• Bazaar curated config is missing - the curated section isn't available yet
• gnome-user-share is missing - we recommend using rclone mount instead

What is Bluefin GDX?

Bluefin GDX is designed to be an AI Workstation by providng Nvidia drivers and CUDA in one image. It combines Bluefin LTS with the Bluefin Developer Experience. There's no cool expansion of GDX: GPU Developer Experience I guess. Maybe someday we'll call it Bluefin CUDA Edition. (Jensen call me!)

The reason we brand it differently is that it is designed for AI and Machine Learning professionals. Instead of a multitude of Nvidia images like Bluefin we will concentrate on this one image to focus on one thing: this is our platform for open source AI. Improvements made in GDX will make it's way into Bluefin's developer mode. GDX gives us a place to rev fast with some new friends:

This will be the lab that will keep Bluefin on the leading edge of open source AI. Here's Mo Duffy on Destination Linux to give you an idea of what we're thinking about.

Features​

• Nvidia CUDA and VSCode integrations and full secureboot support out of the box. There are many parts of the CUDA ecosystem that need to be included, but the raw core is there and ready to be expanded upon.
• Ramalama for local management and serving of AI models
• uv for Python package management
• ... and more! Check the AI and Machine Learning section for more!
• We are looking for AI/ML enthusiasts with strong opinions who want to be involved! Inquire within!

You can find Bluefin GDX on the conference circuit!

What this all means

Bluefin LTS will end up being way more sustainable than Bluefin and Bluefin GTS from a developer perspective. It's more of an initial setup and then we don't touch it as often. We have had periods in beta development where we didn't need to touch it for weeks. If you look changelogs.projectbluefin.io you'll soon notice the pattern, mostly minor version bumps. Nice.

It's also much more advantageous for us to derive off of a base image that ends up being a commercial product -- there is no doubt that CentOS and Red Hat have their weight behind these base images, whereas we are unable to get that level of commitment from Fedora. And as Steven Rosenberg pointed out, Fedora isn't really improving in this area, and with bootc's composefs work coming along nicely we now have multiple base images to choose from. It will be an interesting year!

What does this mean for Bluefin GTS?​

As it turns out, Bluefin LTS HWE is in the exact same ecological niche as GTS. They will end up being competitors. There's no death knell or anything like that, once development moves on it doesn't cost us much to keep it running. And we do love our pets. Check out the awesome brand new image by Delphic Melody and ahmedadan:

As you can see, it's getting a bit crowded. We'll see how people react to LTS, and I expect we'd hide the GTS option from the website but continue to offer it.

With bootc we can deliver a desktop experience with the latest GNOME, and a new kernel -- but on a solid base with less regressions. The previous generation of thinking kept CentOS in a very locked set of use cases. The old boring ones. Now with bootc + containers + flathub + homebrew, we feel that this less churny base makes for a compelling desktop. We'll see how they compete!

Less bitey Bluefin and Bluefin GTS​

Since Bluefin LTS is "bootc natural" and not a transplant, it comes with less compromises out of the box. Bluefin LTS doesn't support local layering at all and AppImages don't work either. (Told ya'll those things were not gonna make it lol.) Bluefin LTS also does not support older machines with v2 CPU instructions.

This also lets us be less strict in Bluefin. We've decided to leave local layering enabled by default in Bluefin and Bluefin GTS. There are users who use that ecosystem, so no worries there. Savages. The Fedora based images will continue to serve these use cases. James also has his own tunaOS, which offers a wide variety of Bluefin-derived variants, including an AlmaLinux based sister to Bluefin LTS. That covers just about everybody - The bootc community around CentOS is quite diverse, and offers a variety of options.

The downloads page is looking pretty good these days but I am very interested to see what you decide since we do measure everything, so feel free to peruse that list. 😄

Merch

Now let's get on to the good stuff. store.projectbluefin.io will take you to the new Bluefin store, which has a ton of awesome items!

We celebrate this release with this T-shirt, the "Reign of Achillobator", signifying Bluefin LTS's role in this ecosystem as a top predator, along with some other goodies:

And of course we've got stuff for the kids, and some other weird things! Currently this store is US only for now.

Proceeds from the store items will go towards paying for more paleoartwork. I think this is a fair deal, Bluefin would have never gotten this far without the work of these fine artists. Having a way for the community to sponsor the artwork in return for the awesome comfort of an Achillobator giganticus hoodie? Peak Linux.

Special Thanks

Bluefin is brought to you by Tulip Blossom and James Reilly. The team grew this cycle with some fantastic new folks helping out to finish Bluefin LTS:

Yulian Kuncheff (Daegalus) hopped in to help with the GitHub actions and the lts-hwe branch. Ahmed Adan and M. Gopal (Delphic Melody) round out the new team with fantastic work on the artwork, website, documentation, and testing. And don't forget to check out the new coloring book!

Special thanks to Carl George, Laura Santamaria, Shaun McCance, and the entire bootc team for their (continuing) support of this project! The game has started. The clue is: Gardener

The Road Ahead

And lastly, there is some missing functionality compared to the Fedora build as there are some creature comforts that are missing. We call these parity bugs, so if find them, file them. There are some things that won't be coming with; CentOS Stream's focus is on long term support, so we may choose to drop a feature if it's not straightforward to bring to Bluefin LTS.

Imagine choosing between LTS, GTS, and stable with just a slider on an update page in a control panel. They should feel and act the same as each other. I'm pretty much there with my personal machines, sometimes I have to check which machine is which because it doesn't really matter. I feel the pain on the infrastructure side instead. 😄

Shred to Achillobator​

Two new soundtracks accompany this release, enjoy!

• Bluefin and Achillobator
• Bluefin and The Children of Jensen

Downloads

Download Bluefin LTS​

The long term support experience.

📖 Read the documentation to learn about features and differences.

Download Bluefin GDX​

The AI workstation with Nvidia and CUDA.

📖 Read the documentation to learn about features and differences.

Discussion​

Download it here

Discussion​

This has led to us publishing our SBOMs and in general giving everything a once over. p5 also dove in to ensure we're rocking and rolling to secure our supply chain. Though we still depend on many third party sources for our software, we've severely cut that down, bringing things inhouse when necessary or removing a dependency alltogether. Thanks to p5's automation work the project is constantly rebuilding when there's a new base image, ensuring that you're getting those timely security updates!

This was also a good time for us to work with Alan Pope and the rest of the crew at Anchore. The team deployed Syft across our important repos and got to work.

This work is of course, always ongoing. I am still green in this field myself, if you're looking to learn more start here with the OpenSSF

• GitHub Secure Open Source Fund

Discussion​

This is a Linux Foundation effort to measure something near and dear to our hearts: contributor metrics. I work with many tools at the CNCF. You will find tools we depend on, like bootc and Podman. This lets us measure contributor health not just for ourselves, but to see how we're doing when compared to other projects. No more guessing, now we can look.

Let's see how we're doing ...

Fancy Charts​

Whew! Ok, that's always good. Let's drill right to the red parts because that's the interesting part.

Here's where we need to use our brains. Charts by themselves can be misleading. Our names are missing (caching issue, probably), but it's clear that I am doing a ton of work! Too much!

What this doesn't show you is that 95% of the work I do on Bluefin is telling a bot it's ok to do something. My takeaway here is "we need to automate more things" because in an ideal world, it's the bots and automation humming away quietly. But ... the chart is also not lying, we are top-heavy for sure, no doubt. We also ensure we measure things outside of code:

If all you do is file an issue or start a discussion, then I do owe you a thanks; we couldn't do it without you.

Here come the new raptors ...​

We've been getting new pull requests in for folks - our way to improve is to continue to work on getting people contributing. LFX Insights is open source and contains some of the largest projects in the world. The fact that we can be involved with this is awesome, and you can submit OSS projects! Stick everything in there, and let's see who is working on improving. 😄

This is just coming live for us, if you're a chart nerd, then feel free to dive into LFX and get started, the team is responsive and moving fast. And if you're like me, you'll find yourself fixing up your dashboard. Make yourself look spectacular! You'll be seeing these charts featured more on the website, etc. Enjoy!

Discussion​