Avatar of Jussi Pakkanen

Jussi Pakkanen

@jpakkane

Welcome to Soviet Union 2.0, comrade

I have a former coworker who was born in the Soviet Union at a very specific time in history. He was just old enough to see the system from the inside and grasp how it works (or, more specifically, did not work) but young enough that it did not consume him. He got out fairly quickly after the collapse and is nowadays doing computer related work in "the west", as it were. Having seen both sides of the world order he had quite an interesting view on why the Soviet Union eventually crashed and how it ties to modern companies.

Let's assume that you are working in the Soviet Union in a car factory. Your job is to be responsible for all things needed to attach the wheels to the body of the car. In practice this means taking parts from subcontractors (typically other divisions of the same factory) such as break pads and lines, the actual wheels, and all other things and put them together so that the car can roll forward. Seems reasonable enough, right?

In practice it turns out that all parts you get are actually garbage. The wheels are not properly balanced. The inner tube might have a hole in it or be completely missing. The metal in brake pads has been silently changed to a cheaper one removing 50-70% of braking power. The brake lines are too short for installation. To make them work you'd need to cut holes in the car's superstructure. Your screws are too soft to properly function, but fortunately so are your wrenches. The downside is that after tightening one wheel all your tools are shaped like a banana. And so on and so on.

Should you find yourself in such a situation, what should you do about it? In theory the parts you are given are not up to spec. So you could file a complaint about it. But you really can't, because then the problem would be you. You would need to do the extra work of getting the people providing you parts to fix their process (which you can't do). You would need to file the paper work. Your name would be on every one of them. When higher ups get reprimanded for cars not getting finished fast enough to reach the requirements of the current five year plan, they are going to come looking for a scapegoat. You made a ruckus. You stopped the pipeline. You are the problem. You get punished.

But it gets worse. Not only are the people below you not caring and producing garbage work, so are the people above you. At every part of the chain nobody gives a shit, they just take things from below, fiddle with them a bit and then shove them upwards and hope that when things eventually fail, you can deflect the blame on to someone else. If you wish to survive, that is what you must do also. This, according to my coworker, was what eventually brought down the Soviet Union. When all organizational layers of an entire nation gets filled with garbage in – garbage out shovelers, the system loses its capability to function, becomes a zombie, wanders on aimlessly and eventually dies.

He claims to have witnessed aspects of this appearing in the organizational chains of several software companies and that he has tried to warn them about the bad direction things are heading. Usually to deaf ears.

But what about today?

All of that happened years ago. The question is whether any of it still matters in this, our Shining New Era of AI. It most definitely does, more than ever.

Any organization can tolerate a small fraction of employees that don't particularly care about "the job" and are just hanging around putting in the minimal amount of effort they need to to still remain employed. That is just how large organizations work. The problem is ratio, and this is where AI comes in.

One of the main non-technical changes AI has brought about seems to be the wholesale conversion of formerly competent and caring people into garbage in – garbage out shovelers. We see them all around us every day. Like the people who handle all emails sent to them by copypasting the entire email thread to a chatbot, asking "what should I reply to this" and then copypasting the entire thing (including the prompt) back as their reply. Or software developers who used to be smart, knowledgeable and competent but suddenly resemble Alzheimer's patients who reply to merge review questions such as "why did you do this thing here" with "I don't know, Claude told me to" and then merge their code without fixing any of the issues raised.

All of this is exacerbated by all the recent layoffs in the tech sector. No doubt this has been used to rid the company of those pesky troublemakers who dare point out flaws in The Perfect New System. Those who know their history might remember that this was the preferred tactic of Stalin (though, granted, his methods were more extreme). As firing people saves money immediately and only causes problems with a delay, this is seen as a good thing and managers doing it get rewarded.

And this is where we are today. Many formerly good organizations have become or are on their way to becoming lumbering hulks that can no longer properly function and will eventually collapse under the weight of their own incompetence. You can already feel this with the recent outages of Microsoft cloud and other services. Things that should have worked just breaking down randomly without anyone really knowing why was an every day occurrence in the Soviet Union. People just shrugged it off as an unavoidable fact of life. That is the direction we are heading.

The last laugh of Lenin

The latter half of the 20th century was a battle between communism and capitalism. The latter won and having its world view validated went on to an even more extreme end of ultra-capitalism. The ultimate irony is that eventually it reached the exact same end state as communism: an absolute unwavering ideological religion. Which is made all the more amusing by the fact that both of these movements were meant to be fully atheistic.

In communism the country was filled with party leaders who were vocal that communism would lead to "the workers' paradise" which was "within our grasp just over the horizon", we just have to give it some time. The average person, on the other hand, did not believe a word of this nonsense, just pretended to care to get along with their life.

I communism 2.0 we instead have CEOs claiming that AI leads to "freeing humanity from the shackles of work" and that "the cure for cancer is just over the horizon", we just have to give them infinite amounts of money first. The average person does not believe a word of this nonsense, just pretend to care to get along with their life.

At least the Soviet Union had the banging Red Army Choir. All noises the techbro CEOs seem to be capable of producing seem to consist of whingy stuttering and vocal fry.

Mundi

Apart from Teclas, few months ago I started another small application called Mundi, Mundi is a geography learning application for GNOME. It all started from an assignment from the teacher of my kid where they had to use the following web page: https://mapasenriquealonso.com/

The web page is actually quite nice but it pissed me off that it had publicity. So I said to myself, what if I make a clone but better for GNOME? Since then I started adding maps and different exercises and I think the application reached to a pretty good state.

When you start the application you get to select the country or a region of the world you want to learn.

The country may have different exercises.

Once you select the exercise you want you can either select the different regions to learn what they are or you can click on “Start Quiz”.

The quiz will start asking you the different regions and you have to click on the right one. It will account for the timing.


Once you are done it will give you the result and you can save your name.

I’ve been playing it with my family and colleagues and it is really funny. It is also interesting to discover how bad you are at geography when you start playing with it!

Go fetch it in Flathub or Snapcraft and enjoy!

Avatar of Miguel de Icaza

Miguel de Icaza

@miguel

What Maintaining SwiftTerm Taught Me About AI Contributions

If you maintain an open-source project right now, your pull request queue probably looks very different than it did two years ago.

I maintain SwiftTerm, an open-source terminal emulator library that is now seven years old. Today, I estimate that about 80% of the pull requests I receive involve AI in some capacity. Looking back, though, this didn't happen all at once—it came in distinct waves.

Disclosure: as a Mexican national that routinely writes tedious and typo-ridden English blog posts, I had Antigravity fix my writing and repeated tedious and repetitive points (as my wife often points out).

Wave One: Vibe-Coded Band-Aids and Fork Experiments

Before people even started opening AI-assisted pull requests on my repository, I would browse the GitHub network graph just to see what forks were popping up and what problems users were struggling with. Early on, what I found was a lot of "vibe coding"—folks patching around issues in ways that were fundamentally wrong, slapping surface-level band-aids over deeper terminal state bugs. I would fix or implement the feature, despite the fact that the user had not submitted the fix - for the sake of helping all my users.

In one fork I stumbled across, someone had clearly unleashed an autonomous agent to try to fix all of my open issues in rapid fire. Luckily, they never actually submitted those PRs—they were likely just experimenting—and it was only my nosy self browsing the network graph that spotted it. Still, looking through those commits confirmed the early reality: the fixes weren't worth merging. They solved surface symptoms without understanding the system.

The Rise of the Promptsplainer

Alongside those early waves came a new open-source archetype—one that many communities had to deal with: the Promptsplainer.

Some folks are really eager to particiapte in improving a project and LLMs have opened new doors, but they lack some basic etiquette.

A Promptsplainer is someone who asks an LLM a question, gets back a confident-sounding explanation or a sprawling patch, and suddenly believes they can override decades of hard-won domain expertise. They don't actually understand the underlying quirks, race conditions, or protocol edge cases of the codebase they are touching. When a veteran maintainer points out a flaw, the Promptsplainer doesn't go investigate the code; they just copy-paste the maintainer's review comments straight back into their chat session and paste whatever the bot spits out next.

You don't need a massive daily flood of Promptsplainers to feel the damage. Even the occasional encounter can fill a maintainer with rage - and with good reason.

Wave Two: "Send a Patch" Finally Became Real

Here is what has changed dramatically over the last year. We went from AI fixes being flat-out wrong or lazy band-aids to pretty much landing in the right ballpark.

To appreciate why this matters so much to me, you have to remember what maintaining an open-source library looked like just a few years ago. Back then, I would get a steady stream of bug reports—and if I had the spare time, the patience, the kids went to sleep early, and my Netflix queue was empty, I might actually sit down and fix the bug.

For decades, open-source communities had a semi-joking, semi-exasperated stock response whenever a user asked, "Why doesn't it...?". We told them, "Patches welcome," or "Send a PR." Most of the time, we knew they wouldn't, because diving into a complex codebase from scratch was too steep a climb. The perfect storm between unpaid volunteer work, uneducated takes and exasperation.

Like many others, I have witnessed the change from getting bug reports to getting detailed pull requests. And I am personally grateful for this.

My philosophy on incoming contributions comes down to a simple reality: every PR represents a real pain point caught in the wild. It means a real user ran into a problem in their day-to-day work, reported or tracked down the issue, found a working solution, and felt the pain acutely enough that they took the time to package it up and upstream it.

As a maintainer, that is an infinitely better signal than my own laundry list of wish-list items sitting in the issue tracker. Even if the implementation needs additional work, someone just handed me proof of a real-world problem along with a concrete starting point to fix it.

Multi-Agent Code Review on My Side of the Table

The catch is that many coding models and agents still have a bad habit of just doing the fix—taking the shortest path to make a test pass without stepping back to look at the whole library. And not every contributor has learned how to tune their agents for deep engineering review, or has access to the best models for it.

The first pass of AI-generated code often needs work, and that is okay. Just as we spent years developing the discipline to master our programming languages, debuggers, and in some cases, write m4 macros, we now need to develop the muscle for using AI tools effectively—learning how to steer them, verify their assumptions, and audit their output.

For me, building that muscle meant putting AI on my side of the table to bridge the gap. Before I even bother reading a contributor's patch line-by-line, I religiously run /code-review in Claude and /review in ChatGPT [1].

These review passes routinely catch far more than narrow syntax nits—they surface genuine architectural flaws, subtle API breakage, rare side effects, and terminal conformance problems that would take me hours to trace manually [2].

Armed with that feedback, I can point contributors toward concrete architectural fixes—or, if someone disappears after opening a PR for a critical bug, I can clean up their branch and land it myself.

Some maintainers lament that reviewing these PRs feels like talking to someone who just copies and pastes feedback into a remote LLM. But we are still communicating with a human being on the other end. That gives us a real opportunity not just to coach contributors on how to use these tools responsibly, but to model and adopt better engineering practices across our industry. Given that the economics of top-tier reasoning models aren't ideal for everyone doing casual open-source work, I’m happy to foot that bill on my end for the sake of keeping my library healthy.

The Friction of One-Size-Fits-All Rules

This brings me to why I’ve been watching the broader debate around AI policies in large projects like Gnome and Godot with a lot of sympathy—and a bit of concern.

At Godot's massive scale, protecting volunteer reviewers from unvetted submissions and the occasional Promptsplainer is a completely understandable instinct. Nobody wants their Netflix time eaten up by drive-by code the author didn't bother to understand.

The challenge is that drawing hard lines around how code was written inevitably creates friction for experienced contributors who are already doing the architectural heavy lifting. Recently, I tried to upstream a small, production-tested bug fix to Godot as a trial balloon—one of roughly 60 to 80 improvements my team has built and tested in our own tree. Because I disclosed my AI workflow honestly, it ran afoul of their strict guidelines and was rejected.

When a policy polices provenance rather than quality, two unintended things happen:

  1. It penalizes transparency: Honest contributors who disclose their tools get blocked, while others are quietly nudged to keep quiet and pretend they typed every character by hand.
  2. Good fixes stay locked in private forks: Rather than wrestling with policy friction, teams like mine simply keep useful patches in our own internal trees. Because AI has made maintaining forks trivial, it doesn't slow us down—it just means the broader community misses out on fixes that could have helped everyone.

Accountability Over Provenance

The Promptsplainer is a real headache, and open-source projects are right to push back against uncomprehending, drive-by contributions.

But the antidote isn't banning the tools—it's requiring human accountability paired with better review tooling on the maintainer's side. At the end of the day, as the maintainer of a library, it is my role to make the editorial decisions about what goes in—and the people who depend on my library trust me to make those calls. Whether a patch started in an LLM prompt or was typed out by hand doesn't change that responsibility. If a contributor understands the problem, has tested the fix, and can engage thoughtfully in review as a human being, the models they used in their editor shouldn't disqualify their work.

Of course, scaling that kind of review culture when a handful of core maintainers are already stretched thin is a structural challenge all its own.

[1] With Claude I use Opus 5.5 alongside /review in GPT 6.2 with Sol-xhigh. In Claude, /code-review actually launches multiple distinct agents in parallel, each focused on different goals and common engineering mistakes. Looking forward to Antigravity to get this.

[2] In fact these reviews are so thorough, that I use /code-review on my own changes before shipping. In a seven-year-old codebase, it is impossible to keep every historical invariant in your head at once, and those agents regularly catch edge-case scenarios I had completely forgotten about.

Avatar of Matthias Klumpp

Matthias Klumpp

@ximion

Changes on freedesktop.org!

Today we launched a change that has been a long time in the making: The updated website for freedesktop.org, as well as the refreshed wiki.freedesktop.org are live now!

You can read the announcement here, this blog post elaborates a bit on it and on the background of the changes, as well as future plans.

Why change anything?

The freedesktop.org website has been a wiki for a long time, which definitely was the right call in its inception. A wiki is very much in spirit of Freedesktop’s mission statement to foster collaboration between desktop environments and to be a place to create de-facto standards.

However, over the years, working with the wiki became a bit of an issue: Not only did we face multiple spam-apocalypses (which in part motivated the switch to IkiWiki in 2013 and resulted in us heavily restricting write access to the wiki), but it also meant that official project information, finished specifications, half-finished proposals and pages nobody had touched in fifteen years were all sitting next to each other.

Since 2000 when Freedesktop.org was started, the project has grown so much and has had so many associated projects and specifications over the decades that it is now very difficult for new people to get an overview what is current and what state the software projects and specifications hosted by Freedesktop.org are in.

Having only a wiki as a large and somewhat disorganized pile of information did not help with that issue, so I worked to split things up: We now have a website as well as a wiki, using different designs to distinguish the two, and serving different purposes.

Website & website plans

The website at www.freedesktop.org will be the place for “official”, or rather, more curated information. Now that the new website is live, its content is still largely that of the old wiki. Over the next weeks, I will be working on cleaning up its contents and listings. For example, I will clearly split active projects from archived ones, add missing ones, and also work towards synchronizing the specifications hosted on the former wiki / website with the ones listed on specifications.fd.o.

So, basically I will do an inventory check of Freedesktop. That work has already started, but until now, I could not make any public changes to not disrupt workflows or make my own future work harder by having diverging information in two places (website & wiki).

I also wanted to make it easier for people to find information on how to get involved with Freedesktop and associated projects, so the new website now has a more discoverable section for that.

The new website is a static site hosted via GitLab Pages and using Pelican. You can view its sources if you like.

Wiki changes

Of course, we also still want to keep the Wiki and all of its rich history around! It remains the easy-to-edit place for collaboration on upcoming projects and specifications.

Wiki edits must now happen through GitLab instead of the old IkiWiki web interface. While this sounds like an additional barrier to edit the wiki, it is significantly easier than requesting an account on annarchy to edit the old Wiki through the web interface. It also still allows us to keep the existing history as well as spam protection measures. In order to use the wiki with GitLab Pages and to keep the history easily accessible and readable, I rewrote the Git history of the wiki to make it pretend that all changes always happened in a content subdirectory. So, if commit signatures are missing and hashes are different: That is the only reason why. There have been no content changes or other metadata changes (and we still have a copy of the pristine wiki Git repository).

For the fd.o wiki, we are now also using Hari’s IkiWiki template that is already in use on the X.org website and which is much easier on the eyes.

Next steps

At the moment, I am mostly concerned with ensuring that the change has not broken any existing links and all systems keep working. After that, the wiki 🡘 website deduplication work will start and we can modernize both the content of the website and wiki.

If you find a broken link, an outdated page or anything else that looks wrong, please file an issue or, even better, open a merge request.
For the wiki, you are very welcome to just fix or otherwise update the page directly.

I did reach out to all wiki editors and projects impacted by this change in advance, but since there are so many people and projects involved, it is always possible to miss someone or something. If you found a bug, need edit permissions, or need help with anything, don’t hesitate to ping me: You can find me as ximion in OFTC’s #freedesktop IRC channel, in the very recently created #xdg-specs channel on the Freedesktop Matrix space, or you can email me.

Thank you!

I do want to echo the announcement news post here: None of Freedesktop.org would exist without the people who filled it with life over the years and who worked on cross-desktop collaborative projects. I have read through a lot of wiki history and old project pages over the recent months, and it feels amazing to know how much work and passion people have poured into the projects and collaborative efforts over the years – no matter if they were successes in the end, or remained experiments. I am very thankful for all current, past and future editors of the website and wiki, as well as all project maintainers and contributors.

I also want to thank the Sovereign Tech Agency once more for supporting me in their fellowship program as a maintainer, which enabled me to work on this task among other things.

Thanks to all contributors, in whichever way you contribute to our free desktop ecosystem!

Avatar of This Week in GNOME

This Week in GNOME

@thisweek

#275 Grand Theft Auto-Paste

Update on what happened across the GNOME project in the week from November 13 to November 20.

Third Party Projects

Tanay reports

Whisp v1.7.0 Auto Paste Module , Improved Lists and Mobile Devices

New Features

  • Smart Paste Module: Activate with :paste to auto-collect clipboard text into formatted Markdown lists.
  • Refocus Sync & OCR: Syncs external copies on window refocus and deduplicates screenshots via cryptographic hashing.
  • Paste & Link Shortcuts: Paste plain text with Ctrl+Shift+V and format links with Ctrl+Shift+L.
  • Dynamic List Renumbering: Automatically preserves numbering sequences when inserting, editing, or deleting ordered list items.
  • Enhanced Mobile UI: Full adaptive layout support for Linux Mobile devices (e.g. Phosh, PinePhone).

Bug Fixes & Refinements

  • Fixed shortcuts panel crash by presenting Adw.ShortcutsDialog directly and added <Ctrl>question keybinding support.

  • Live synchronization of custom keybindings across preferences and the shortcuts display panel.

  • Fixed OCR text extraction artifacts on small image inputs.

Download | Github | Website | Donate

Anton Isaiev reports

RustConn 0.25 is out - a connection manager for SSH, RDP, VNC, SPICE, Telnet, Serial, Kubernetes, WinRM, Web and Zero Trust, built with GTK4 and Libadwaita.

Since 0.24:

  • WinRM connections, fallback jump hosts, numbered-range duplication and running a local bash script on many SSH hosts (contributed by Konstantinos Patronas)
  • Trash that keeps deleted connections and groups until you empty it, with Restore / Delete Permanently / Empty Trash in the sidebar
  • Folder actions: New Subgroup, Duplicate, Move to Group, and a search field in every group picker
  • “Split with Other Tabs…” builds a balanced split grid in one step (Ctrl+Shift+K), plus saved sidebar searches
  • Much faster Bitwarden through an optional persistent CLI, and a KeePass database per connection or group
  • RDP: IronRDP graphics pipeline and AVC444, microphone, smart cards, auto-reconnect after a network drop, monitor selection for an external window
  • Terminal: OSC 133 prompt navigation and failed-command marker, remote working directory in the tab tooltip, snippets in the Command Palette
  • SSH keys added to the agent expire after 12 hours and are removed on screen lock or suspend; encrypted keys are unlocked once per session
  • Connections added with rustconn-cli now show up in a running window, and a save no longer overwrites changes made by another process
  • Security fixes: shell metacharacters in jump host and key paths, Passbolt passphrase no longer visible in the process list, checksum checks for six CLI downloads
  • New languages: Azerbaijani (Naim Shafiev) and Vietnamese (dinhkarate) Thanks to Konstantinos Patronas, Naim Shafiev, dinhkarate and all the contributors and translators who drove this cycle. And thanks to everyone who files bugs and supports the project - this cycle was driven largely by the issues you reported. If you’d like to support development, the repo has a Sponsor link.

https://github.com/totoshko88/RustConn https://flathub.org/apps/io.github.totoshko88.RustConn https://snapcraft.io/rustconn/

hernantz says

Timezones is a GTK/Libadwaita app that lets you compare a single time in different timezones. Shows one timezone row per city on a shared timeline, so a glance tells you who is asleep, who is at work, and when to meet. It is available in:

Phosh ↗

A pure wayland shell for mobile devices.

Guido announces

Phosh 0.59 is out:

We’ve added new screenshot and SSH quick-settings, and a camera indicator to the status bar. Phosh can now fetch the PIN length from systemd-homed so you no longer need to hit “submit” on the lock screen. The thumbnail-overlay rendering moved to the compositor, the on-screen keyboard stevia now supports speech input via Vosk (demo video) and we added initial support for UnifiedPush.

There’s more — see the full details here. {{< video src=“XfuEXEcoyYXUddpyxIQUhpvo_phosh-overview.webm” >}}

GNOME Core Apps and Libraries

Maps ↗

Maps gives you quick access to maps all across the world.

mlundblad says

Maps now shows OpenLocationCodes (plus codes) when opening a place, thanks to work by Ihor Nakonechnyi, a new contributor

GLib ↗

The low-level core library that forms the basis for projects such as GTK and GNOME.

Philip Withnall says

This week GLib has seen a lot of performance improvements to various leaf functions land, courtesy of Christian Hergert; various D-Bus fixes from Nieves Montero and Dimitriy Ryazantcev; and various appinfo fixes from Ana Bobillo

GNOME Circle Apps and Libraries

Valos (Ee) says

Komikku has surpassed a quarter of a million downloads on Flathub! To celebrate, a long-requested double-page view has been added.

The OCR translator, added a few weeks ago, is now considered stable. The OCR currently supports English, French, Spanish, and Japanese (feel free to request other languages). As for translations, they can be done using Google Translate or DeepL services.

Download from Flathub: https://flathub.org/apps/info.febvre.Komikku

Shell Extensions

Mehmet Nural announces

Dynamic Brightness is a lightweight gnome shell extension which adjusts you screen brightness according to the current content in your screen. Inspired by Wluma and Lumen. It’s available in https://extensions.gnome.org/extension/10557/dynamic-brightness/

Christian Lauinger announces

HeadsetControl - Gnome Shell Extension to visualize headset status from HeadsetControl (https://github.com/Sapd/HeadsetControl) command line tool. Supported capabilities can also be controlled like ChatMix, Sidetone, Equalizer etc. Available here: https://extensions.gnome.org/extension/5823/headsetcontrol/

Christian Lauinger says

Harddisk LED NG is a gnome shell extension to show harddisk activity with IO speed and an LED. Click to cycle through display modes. Preferences are also added. It is available here: https://extensions.gnome.org/extension/11798/harddisk-led-ng/

Miscellaneous

Damned Lies ↗

The internal application to manage localization of GNOME & friends modules

Guillaume Bernard reports

Damned Lies received new features this week! We received contributions from new contributors and new features were implemented thanks to their work!

In short, we upgraded the base operating system of Damned Lies to Fedora 45, which means we now use the new gettext version: 1.0. So yes, gettext 1.0 was released at the beginning of this year, after so many years of development! Considering the release notes, there are no substantial changes for you as module developers. We also switched to Python 3.15, released a month ago.

In addition to these infrastructure changes, I reworked the processing of statistics on the release pages: it is now faster, consumes fewer resources, and the code is way easier to understand. In short, we removed the lot of dicts, built on the fly, with clear and explicit @dataclass: now, you know what’s inside. Other refactoring work was done to extract services and decouple the big ball of mud we had in some parts of the code.

Ramal Rəhimov worked on performance issues with queries and started to implement new endpoints to communicate with Damned Lies through the REST API. This is a major change that will allow us to do more with clients, while still having Damned Lies as a proxy between the translation teams and the GNOME repositories. I recently spoke with some contributors from other communities that contribute to translations downstream: I see an opportunity for us, as upstream managers, to receive some translations automatically from downstream communities, with Damned Lies. The review workflow that is in place ensures the quality of translations is kept - it then flows down again to the downstream distributions.

Paul Pidou fixed a few bugs in the last weeks and worked on a long-awaited feature for module maintainers: you can now check your DOAP file in advance to debug it. This feature was inspired by the CI Lint feature of GitLab: https://l10n.gnome.org/module/doap/check/. In addition to this feature, if your .doap file has some issues, there is a warning banner on top of the module itself.

That is all for this new week for Damned Lies!

That’s all for this week!

See you next week, and be sure to stop by #thisweek:gnome.org with updates on your own projects!

Mecalin is now Teclas

Almost a year ago I released Mecalin to the world. https://blogs.gnome.org/nacho/2026/01/15/mecalin/

The idea that I had for that application was to have something that would allow you to learn touch typing, play some games and have some speed test as part of a single application. In the meantime Philipp Sauberzweig started to review the GNOME Circle application request I made. Philipp came in with lots of design ideas to improve the application. The first one was to make Mecalin to do one thing and to make it well. For this I got rid of the games and of the copy of KeyPunch.

As part of the review he also proposed to change the name to something that does not sound as old as Mecalin and that follows the naming conventions of GNOME. Mecalin is now Teclas. https://flathub.org/en/apps/io.github.nacho.teclas

Since last year almost 500 commits have happened. This application is looking very nice and I wished I had access to such an application many years ago to learn touch typing, I hope many kids out there will use it and enjoy it as much as I enjoyed putting it together.

At this point I will show a bit where we stand with this application:

A new welcome page is what you will see the first time you run the application.

One you are done with the welcome pages you will start already with the course. It comes with a new improved UI. Both the entry where you introduce the text, the hands, the keyboard is improved. Colors are On by default and in general the application looks quite nice in my opinion.

If you close the application or you go back you will have a selector to continue with the course where you left it, or it will allow you to jump to the different lessons in case you want to repeat one or you feel brave enough to jump one of the lessons.

If you manage to complete all the lessons, you will be presented with this great cup 😛 The important thing of this UI is that it makes it easy for you to have a one way click to install Keypunch and to continue learning touch typing by using that great application.

You will not see this application as part of GNOME Circle due to the extensive usage I did of LLMs to create it and I think it makes sense given what the program is meant to be.

Finally I want to thank again Philipp for all the great work he put on the reviews of this application and to all the people who reported bugs or feature requests.

Go ahead and fetch it from Flathub!

Avatar of GNOME Foundation News

GNOME Foundation News

@foundationblog

Let’s Build the Future of GNOME Together

Today we are launching the GNOME Foundation’s 2026 end-of-year fundraiser, and we need your donations to help build a stronger, healthier GNOME ecosystem.

GNOME is an independent computing platform enjoyed by millions of people worldwide. What if a small fraction of them helped financially sustain it? Together, we could give GNOME the resources to accomplish so much more.


GNOME 2026 end-of-year fundraiser progress

GNOME and the GNOME Foundation

GNOME is a Linux desktop environment and collection of apps intentionally designed to be elegant, intuitive, and privacy-respecting. It’s the default experience on many popular Linux distributions like Fedora, Ubuntu, Debian, and Zorin OS.

The GNOME Foundation is the organization working to sustain GNOME, but its resources are stretched thin. We are currently limited to a handful of paid team members, most of whom are part-time.

GNOME exists today thanks to a global community of volunteers sharing their time, talent, and passion to build software that benefits millions. They frequently juggle jobs, family, hobbies, and other commitments to accomplish this work. We see an opportunity to give some of these talented people the time, resources, and financial incentive to contribute more to GNOME.

The Fellowship is Making a Difference

And thanks to your generosity in 2025, we were able to launch the GNOME Fellowship program in April 2026. The Fellowship allows us to directly support two talented members of this community, who in turn spend dedicated time enhancing the long-term sustainability and health of the GNOME project.

These Fellows are already making noticeable quality-of-life enhancements to your everyday desktop experience, and the underlying technologies that power GNOME.

In their first three months, Fellows Peter and Sophie have modernized the file previewer, made substantial improvements to image handling, and fixed many problematic bugs — some of which have existed for years. And that’s only a small sampling of what they’ve accomplished.

With your help, we can raise an additional $60,000 to sustain the fellowship program throughout 2027. Donate today, and let’s continue supporting the vital work our Fellows are doing!

Your Donation Matters

GNOME isn’t just a desktop environment. It’s an alternative to a world where corporations decide how you should use your hardware, treat your personal data as a commodity, and disregard your privacy.

GNOME is a reflection of what we believe technology should be: open, empowering, and built to put the control back in your hands.

If you’re reading this, GNOME matters to you. And your donation matters to GNOME! Please give what you can today. Every single gift helps make a stronger, healthier GNOME possible.

Avatar of Hylke Bons

Hylke Bons

@hbons

Icon for Liferea

Icon for Liferea

Week 34

This week's icon is for Lars Windolf's project:
Liferea: "Keep up with your feeds"

Check out all weekly app icons created so far in the gallery and follow my icon creation adventures as they happen (including sketches) on the Fediverse.

Need icons?

I love designing icons and am happy to contribute them free of charge when your project is Free and Open Source. Join as a community sponsor to maintain a steady supply of app icons to the Linux ecosystem (every little helps!).

16th November 2026

I was watching a meme-heavy video there entitled “Bad Gear – BIG BRANDS have a PROBLEM!!!” which ended on the following insight:

We were promised flying cars but all we got was a dystopia with cheap synths - and I'm only partly complaining

I’ve been following the world of synthesizers and drum machines for the last decade, since the first Akai MPC with a touchscreen appeared and I thought I’d have more fun making music on that than a laptop. (Which I was wrong about, in hindsight. But it opened the door to a lot of fun exploration in the space where music intersects with technology and human interface design.)

Music technology always involved proprietary platforms and locked-down devices. Macbooks everywhere. Copy protection schemes with hardware dongles (see: iLok). Copyright sting operations against small studios (see: Waves Audio. Read Markus Schmidt of Calf Audio’s story for how wild they go). People regularly call me crazy for making music using a Linux desktop. Even in the world of “creative coding”, where making custom instruments and tools in software is part of the musicians practice, the most popular environment is Max/MSP, a proprietary product that costs 400€ and runs on Windows and Mac only.

That’s before we get to hardware devices. There has been a huge boom in the last decade, it’s been a fun time, and is much better use for semiconductors compared to making drones. There are dedicated DSP chips available. Some devices manage to build an impressive amount of functionality in the DSP chip itself… checkout how many guitar pedals use the Spin FV-1 for example. Others have an ARM chip as the brain, usually running Linux, and usually completely closed to any kind of customisation. These machines are expensive. I still think of 600€ as a cheap price point for a synth. The most expensive MPC costs over 2 grand. You’re paying a premium for custom hardware being produced at relatively small scale, and the expectation that it will be rock solid — built to the quality of any other musical instrument. A guitar doesn’t randomly reboot to install a firmware update and neither do these devices. (The level of programming skill at music tech companies is waaaay above what I’ve seen anywhere else in the tech industry… but that’s a whole other blog post).

Akai MPC XL, a big slab with many knobs and pads

Open, hackable devices exist but have always been pretty niche. Have you been to a gig where someone played the Monome Norns? Or maybe an Organelle concert?

The year of our Lord 2026 is the year that changed. This month I’m being bombarded with videos about the MVAVE FM-1, a synth that costs 70€, and comes with an online IDE, and an open SDK. It’s arrived at a moment when LLM coding tools are heavily subsidized by the AI bubble, and at time of writing there are two hundred and nineteen alternative firmwaves available for this thing. There’s a website hosting them all. In fact there are multiple. People are making this box into all sorts of different instruments that suit different purposes, experimenting, learning, playing and abandoning them.

To put that in comparison, I have a Korg Minilogue synth, which has had an open plugin development platform since 2019. Korgs are one of the longest established and best selling synth makers in the world. In 7 years, the official list of plugins grown to about… 200 plugins, many of which are from pro plugin makers. By comparsion, the FM-1 was released in June of this year, that is, not even 7 months have passed yet.

While a lot of the music tech video sphere is hyping the FM-1, there are some more measured takes. Jeremy Blake a.k.a Red Means Recording made a video entitled “Vibecoding in Plato’s Cave (AI, Music Tech, and Star Trek)”, which in turn links to an editorial from audionewsroom.net under “Why the open source hardware revolution is a lie”. These both make some good points, which I won’t repeat as I think everyone who reads my blog already knows that Anthropic and OpenAI are malevolent forces and today’s vibe coding apps are optimized for addiction by the same people who designed slot machines and infinite scroll. I called this back in January 2026 in a post titled “AI predictions for 2026”.

Maybe I’m in an optimistic mood, especially as we might be seeing the first signs of the AI bubble bursting, thanks to Jensen Huang accidentally having sex with a Chinese spy, but I see this sudden boom in hackable music tech as a really cool thing. Musicians who wouldn’t feel comfortable writing “Hello World” in C are suddenly designing and deploying custom device firmwares with wacky interface ideas that they dreamed up themselves. Sure, most of them probably don’t work very well and are quickly abandoned, but people are learning. You learn by doing! I didn’t get into programming because I wanted to study programming — I wanted to do cool stuff with a computer, and learning to code was a byproduct of that. My first attempts at coding were terrible and it was a long, long road to becoming good. I didn’t exactly enjoy it, more than anything it was frustrating because I could never have the time or skill to build the things I wanted. Now I find coding fun, because I did it long enough to get good, but I really see it as a lucky coincidence that I had the time and circumstances to be able to practice and fail on hundreds of projects over many years to get to where I am today.

People who have spent a long time learning to code are worrying about the effect AI coding tools will have on our world. Which is reasonable; leaders in the software industry have mostly lost their minds, almost nobody is hiring and training junior engineers, everyone is getting hacked all the time, and so on. I’m sure you know all of this.

I think the booming FM-1 firmware scene shows that we are missing a bigger point. What effect do AI coding tools have for people who use computers but never felt empowered to hack them before ?

The FM-1 is a perfect playground for learning to hack. There are very few security concerns — it doesn’t even have a network interface, and there’s no private data to steal (unless maybe you’ve saved a really really good song). If you brick the device — and people are doing that — you get to learn how to fix it, and you probably only make that mistake once. In the absolute worst case, you lost 70€ and you have to go back to making music on the bagpipes instead, or whatever you did before.

We need to see this as an entirely new way to interface with a computer.

The oldest computers dealt with binary numbers, one bit at a time. Modern computers do exactly the same thing! They look unrecognizably different, because we have innovated so much in how we interface with them. First we mapped the numbers to a character set, and suddenly we could communicate with them in strings of text. Programming languages emerged only once that was possible. Then we learned to map numbers to pixels on a display. From there, we could build pointing devices and touch screens and eventually get to the modern desktop interface and smartphone.

LLMs map the numbers to tokens in a heavily compressed database of basically all the text that humans ever wrote down, which gives us another new way to communicate with computers. English words map to chunks of code, which get clumsily mangled into something that the computer can and will execute. Yes, that’s a terrible way to make systems software, but that’s not the only thing you can do with this new interface. The sudden fad for making FM-1 firmwares wouldn’t have happened if the device came out 5 years ago. We are looking at the most powerful interface for hacking computers and devices that has ever existed.

I got into the open source desktop world because I wanted to see computer use democratized. Apple and Microsoft promised to lock down and control what we could do with PCs, and Google is doing the same with smartphones now. The open source movement fought against this and we are winning! The Linux desktop is more popular than ever, and operating systems are increasingly a commodity.

But when we win this round, are we clear where to go next? It feels like our only proposition is to do the same thing as before, but also be really angry about AI. I don’t think that is going to work! I’m as angry as you about OpenAI stealing all our work. I’m angry about the climate crisis and the wealth inequality crisis, too, and those both seem a lot more pressing.

It is possible to define your community around rejecting new things but it leads to stagnation. And things don’t go away just because you want them to! As Armin Ronacher put it in his post Communities of Not: “Cars shape cities even for people who cycle”. (I hate cars, too, by the way, and avoided having one for years, but they have stubbornly refused to go away).

Like many of my posts, this is partly wondering out loud about where the GNOME project could go. Fifteen years ago, we did some radical design work, and made a bet that everyone would have GPU in their computer in future. At the time I thought that was a bad call, and actually I couldn’t use GNOME Shell for 5 or so years after the GNOME 3 release because of driver issues. It works great nowadays and it’s obvious now that GNOME Shell included a lot of good decisions that have kept GNOME at the forefront of desktop Linux ever since.

Front page from FM-1

I’m not very excited if our bet for the future is “do the same as before but also argue a lot about AI use.” Now is the time to make some bets about the future of hackable, ethical, open computing that includes the 99% of the population who haven’t spent decades learning to write code with the same level of proficiency and control that Khn de Poitrine has at playing guitar.

Avatar of GIMP

GIMP

@GIMP

Improved Graphical User Interface testing

GIMP has a lot of intertwined menus, dialogs and tools. When we change a part of the interface, another may stop working and sometimes, the problem can be missed until a user reports it.

To find these problems early, a new GUI testing platform was implemented. A typical GUI test starts GIMP, clicks menus and buttons, and then checks the result. These tests run automatically each time we merge contributor changes.

Why we need them⁠

GIMP already has unit tests. A unit test checks one small part of the code, for example how GIMP reads an XCF file. But our unit tests were not opening a real window. So it coult not tell us if a dialog opens, or if a menu item did its job.

Note that GIMP already had tests of GUI code, usually interacting directly with the core code, and sometimes even simulating input devices’ events (pointer movements, clicks, drags…). But nothing can beat interacting with the real interface. Furthermore such legacy tests directly hijacking core code come with their own problems, such as breaking all too often (and not because they detected a bug), all while not being able to detect whole categories of bugs.

UI tests check the program as a whole, in the same way as you use it.

What the tests do⁠

Each test starts a real GIMP and does one small task. Then it reads the result from GIMP. If the result is not correct, the test fails and tells us what went wrong.

We have 13 tests at this time. They check that:

  • GIMP starts and shows its main window.
  • The Welcome dialog opens on the correct tab. It also stays hidden when you turn off “Show on Start”.
  • File > New makes an image with the size you set.
  • File > Export As writes a correct PNG file.
  • Tools > Swap Colors swaps the foreground and background colors.
  • You can type a new foreground color in the Colors dialog.
  • You can add a layer and delete a layer.
  • Undo and Redo work.
  • Zoom In changes the zoom level.
  • A click on a tool button in the toolbox selects that tool. The test then uses the Bucket Fill tool on the canvas.
  • A change in Preferences is saved when you click OK.
  • A menu action, Image > Flatten Image, does its job.

How they work⁠

The tests do not need a screen. Each test starts a small, hidden desktop, runs GIMP in it, and removes it at the end. Because of this, the tests can run on our CI servers, where no screen is available.

To find a button or a menu, the tests do not look at the pixels on the screen. They use the accessibility information that GIMP gives to tools such as screen readers. This has one more good result: when we make GIMP easier to test, we also make it easier to use with a screen reader, hence improve the software accessibility.

The tests use dogtail, a Python tool for UI tests. To run GIMP on a server with no screen, dogtail needed a new feature. We contributed this feature upstream, to dogtail itself, so other projects can use it too.

At this time, the tests run only on Linux (both X11 and Wayland) since dogtail does not support Windows or macOs.

Adding even these few simple tests considerably increases confidence that the GIMP build has worked, and also shows the test infrastructure is working and useful.

Credits⁠

  • Harsh Verma wrote the UI tests and the new dogtail feature.
  • Jehan reviewed the UI tests.
  • Michal Odehnal reviewed the new dogtail feature.

You can read the full change in merge request !2909.

How you can help⁠

13 tests is a good start, but GIMP has many more dialogs and tools. If you want to help, you can write a test for the part of GIMP that you use the most.

We wrote a guide that shows how to write a new test and how to find the cause when a test fails: UI tests on developer.gimp.org.

We hope this work will help us find bugs earlier and keep GIMP working well for everyone.

Avatar of This Week in GNOME

This Week in GNOME

@thisweek

#274 Fancy Statistics

Update on what happened across the GNOME project in the week from November 6 to November 13.

GNOME Fellowship

Peter Eisenmann says

I wrote about the 🧟spooky👻 stuff I got up to as a GNOME fellow in October, read about it here 🎃 https://blogs.gnome.org/p3732/fellowship-report-october-2026-lothlorien/

GNOME Core Apps and Libraries

GTK ↗

Cross-platform widget toolkit for creating graphical user interfaces.

Felix says

I’ve been working on some more GTK macOS fixes, which were merged this week!

  • When a window is maximized (“zoomed”), its content now resizes smoothly along with the animation. Before, the content only updated once the animation had finished. (!10667)
  • When an app starts, it no longer briefly shows an empty window frame before the actual content appears. GTK now waits until the first frame has been drawn before putting the window on screen. (!10640)
  • Mouse back/forward buttons now work as expected. For example, pressing the back button in an app that uses AdwNavigationView now goes back, just like it does on Linux. (!10625)
  • GTK can now tell trackpad scrolling apart from a regular mouse wheel. Widgets that rely on touchpad swipes, for example the swipe-back gesture of AdwNavigationView now also works on macOS. (!10617)
  • Apps can now open links with their own custom URL schemes, for example a link that opens a specific app. Before, these links were silently ignored. (!10615)
  • Finally, I fixed a bug that caused some tooltips to be clipped. (!10614)

GNOME Circle Apps and Libraries

Alexander Vanhee reports

Bazaar 0.10.0 was released this Tuesday with many improvements: you can now install from user remotes in the Flatpak version, remove remotes from within the app, and the daily downloads graph got a redesign.

For the next release, I’ve also added a fancy new distro statistics graph, which should hopefully give app developers more insight into where their users come from.

Third Party Projects

Charalampos Kardaris reports

Klisi is a callgrind profile viewer designed to fit nicely into the GNOME desktop.

It is an alternative to KCachegrind.

A callgrind profile contains information about the cost of the functions in an executable. It can be used to find bottlenecks in your code and speed up your program’s execution.

Klisi prioritises a simple interface, supports full keyboard navigation and touchpad gestures, and aims to cover as much ground as possible with regard to accessibility.

What’s more, it is not a typical GTK4/Adwaita application. It is written in Clojure using the excellent java-gi bindings.

You can read more about the why and how in a blog post of mine from three months ago, written after the first release.

I hope you find this useful and I am looking forward to your feedback.

seja-arctic-fox reports

Last week, I released a new version of VidCom, a video archival utility. The new version is nothing big, but brings some nice improvements to the user experience.

Changes:

  • Better window sizing and side-panel collapsing
  • Various UI changes
  • Queue is visible and can be interacted with during encoding. This allows the user to add, remove or shuffle videos in the queue while the encoding is in progress. This becomes useful especially when encoding takes a long time to finish.
  • Bug fixes adressing app stability, threading, encoding and GUI
  • Fixes for AVC codec options, radio buttons and opening of output folders
  • Added confirmation dialog for overwriting existing files (both GUI and CLI) and an option to always overwrite files on conflict
  • VidCom now works on Windows as well

VidCom can be installed via Flathub or AUR

moosee reports

I have two updates to share for Moose, a GTK and libadwaita app for chatting with local AI models through Ollama or connecting to cloud services!

Version 0.8.0 brings web search and a calculator to chats with compatible Ollama and Ollama Cloud models. Search uses DuckDuckGo by default, without needing a search account, and asks for permission first. Sources stay with the conversation, so you can come back and check them later. Choosing a model has also become easier: the redesigned Models view lets you browse by task and see estimated memory and storage needs before downloading. Longer Ollama replies can now be continued if they reach their length limit, and OpenRouter joins the supported providers, thanks to olumolu!

Version 0.8.5 adds a way to take your work out of the chat. With Create Document, you can describe what you need or turn an existing answer into a file: a report, a budget spreadsheet or a presentation, for example. Supported formats include PDF, Word, Excel, PowerPoint and OpenDocument. The files stay with the answer and appear alongside your uploads in Moose’s Files view, where you can search their contents, preview them or jump back to the conversation they came from.

You can try Moose on Flathub and find the code on GitHub. Feedback, bug reports and contributions are welcome!

Vlad Krupinski announces

Errands has been rewritten from Python to C. It was a 2-year effort and it’s finally here. Many new features have been added, and many existing issues have been fixed.

Here is the short list of changes:

  • Much lower resources usage and memory consumption even with thousands of tasks
  • Instant startup
  • Reworked UI
  • Recurrent tasks
  • Task search and sorting
  • Cancelled tasks
  • Custom colors
  • All Tasks view
  • Reworked sync using Evolution Data Server

Get the latest update on Flathub!

Era ↗

Manage your time

Titouan Real announces

Era 0.3.0 is out. Download Era from Flathub now and report any bugs you can find.

Era is a calendar app for mobile and desktop, designed to stay simple for everyday use while offering powerful tools when you need them. It syncs with most online calendar providers and works offline, too.

This release brings updated month and agenda views, with clearer time labels in the agenda and larger date headers in month view, making it easier to spot the start of each month as you scroll. You can now move events to another calendar, and Era remembers your last-used view when you reopen the app. The update also includes further performance improvements in month view.

Era is also available on GNOME Nightly for the latest features, bug fixes, and performance improvements.

That’s all for this week!

See you next week, and be sure to stop by #thisweek:gnome.org with updates on your own projects!

Copr, explained: the sandbox where Fedora packaging starts

Copr, explained: the sandbox where Fedora packaging starts

In 2017, I wanted a small tool to change my laptop’s screen brightness. I found one that worked, but Fedora did not have an RPM package for it. So I set out to package it myself. Fedora Copr made that first attempt far less stressful. I wrote up that first package at the time: How I created my first RPM package in Fedora. Copr remains one of the most useful tools in the Fedora contribution ecosystem.

This post is the introduction I wish I had read before I started. It explains what Copr is, why packagers and users rely on it, and why its sandbox-like design matters now.

What Copr is 🔗

Copr, short for Community Projects, is a build service. You give it a source RPM (SRPM), and it builds the package and hosts the results in a DNF or YUM repository. Copr runs on Fedora infrastructure. You can use the public instance at copr.fedorainfracloud.org.

If you use Arch Linux, Copr is the closest parallel to the Arch User Repository (AUR). Both are community spaces where people share packages for others to use. The AUR shares build scripts, and you build the package on your own machine. Copr goes a step further. It builds the RPM for you and hosts the repository, so you enable it and install with DNF.

You need a Fedora Account System (FAS) login to create a project. You do not need special approval. You can build for several Fedora releases, EPEL releases, and other targets in one step. One SRPM can produce packages for many releases and architectures.

Why packagers use Copr 🔗

When I started, my biggest question was whether my package would build on the releases I cared about. Koji is Fedora’s official build system, and I used scratch builds there to test. Copr solved a different problem. It let me host the package, install it on my own machine, and share a repository with others before I submitted anything for review.

Koji scratch builds caught a Fedora 27 failure that I fixed before I submitted my package for review. Copr is not a replacement for that process. It is a place to test first.

Copr as an instant enablement path 🔗

Recently, I used Copr to package something new I was working on. I packaged a set of Markdown files, each one an Agent Skill, from the Fedora Agent Skills Library into a single RPM. I published it in the AI/ML SIG Copr project and started sharing it for testing and use.

My plan is to package agent-skills officially in Fedora. Copr made that first step possible because it gave me the fastest path to get an RPM into users' hands. Users got a semi-official channel to install the package now, and I got real feedback while the official process moves along.

Copr as a sandbox 🔗

Copr works well as a sandbox. Several design choices make that true.

  • Projects are separate. Packages in your Copr project do not enter Fedora’s official repositories. Your experiments stay in your own repository.

  • Packaging rules are relaxed. Copr packages do not have to follow the Fedora Packaging Guidelines. The guidelines are still recommended, but you can test ideas before you meet every rule.

  • Projects can expire. You can set a project to delete itself after a number of days. This suits short tests and one-off experiments.

  • Old builds are removed. By default, Copr keeps one build per package and deletes the others after 14 days. Projects on the newer Pulp backend keep the five most recent successful builds per package instead, so test projects do not grow forever.

A sandbox does not mean anything goes. Copr is Free Software, and its repositories are signed. However, the Copr maintainers do not review every package. Before you install a package from a Copr project, check who maintains it. If you can, look at the SRPM and spec file. Projects distributed in Copr must also follow Fedora’s license rules.

Where Copr fits in the innovation discussion 🔗

Fedora is discussing a Council proposal for an Innovation Lifecycle. The proposal includes a "sandbox stage" for experimental work that is too large for a single change proposal. One of its stated goals is to isolate risk. Experiments should be able to break without affecting the main distribution or the people who depend on it.

The proposal also notes that it does not yet define standard sandbox infrastructure. Copr is not part of that proposal. It already shows what a low-risk space for experiments can look like. Work stays separate from official releases, feedback comes quickly, and strong packages can follow a path into Fedora. I hope we keep that spirit as the larger discussion moves forward.

Packaging as a fallback 🔗

Distribution methods will change over time. Right now, RPM packaging works well. It is tested, proven, and well understood by Fedora contributors and users. When we do not know how to share something new, RPM packaging is a path we can always fall back on. It provides versioning and a distribution mechanism for large varieties of software. Copr makes that RPM packaging fallback fast.

Getting started 🔗

You need a FAS account, a project, and an SRPM or RPM spec. These commands create a project for Fedora Rawhide and submit a build:

copr-cli create --chroot fedora-rawhide-x86_64 my-first-project
copr-cli build my-first-project ./my-package.spec

For more detail, read the Copr user documentation.

Final thoughts 🔗

Copr gave me a low-risk way to learn packaging, and it can do the same for you. If you have a package that is too early for Fedora, build it in Copr, share it, and learn from the results. Thank you to everyone who maintains Copr and helps packagers use it.


Featured image generated by LLM-gen-AI using the OpenAI image API.