Open-source projects, especially foundational ones, face significant risks when a single maintainer steps down, unlike corporate software with structured replacement plans. Christian Hergert, a key Red Hat developer, recently departed, leaving numerous critical GNOME-related projects unmaintained due to being their sole active developer. His departure was due to Red Hat denying his request for an international transfer, leading him to leave and be unable to work on these projects. Many of the affected projects, such as GTK Source View, GNOME Text Editor, Ptyxis, and Libspelling, are foundational libraries or core applications for the GNOME platform and widely used in Linux distributions. Analysis of these projects' repositories reveals a severe lack of recent code commits, with most activity limited to translation updates, indicating a stalled state. This highlights a recurring problem in the FOSS space where "boring" but essential foundational projects struggle to attract and retain multiple active contributors, leaving them vulnerable. The video calls for community members and organizations to step up and contribute engineering time or funding to ensure the long-term sustainability of these vital components.
Christian Hergert's Mastodon post announcing his departure from Red Hat and the unmaintained status of his projects
[
00:01:20
]
The Challenge of Single Maintainers in Open Source [0:00]
Unlike corporate software where replacement is typically feasible due to company resources, open-source projects, even popular ones, often rely on a single maintainer.
This creates a significant vulnerability when that individual decides to step down, potentially leaving critical projects unmaintained.
The common suggestion to "fork the project" is often not practical, as many who suggest it do not actively contribute to such efforts themselves.
Christian Hergert's Departure and its Implications [1:13]
Christian Hergert, formerly employed by Red Hat, announced his departure, stating that all projects he maintained as part of his employment should no longer be considered maintained by him.
Christian Hergert's Mastodon post announcing his departure from Red Hat and the unmaintained status of his projects
[
00:01:20
]
He emphasized that these projects, solely maintained by him, would become unmaintained unless new community members stepped in, as he would not be available for maintenance or support in the foreseeable future.
While Red Hat typically hires replacements for employees working on open-source projects, the situation is more complex when an individual maintains multiple, often tangential, open-source projects beyond their direct paid role.
These supplementary projects, even if foundational, often lack dedicated funding or a clear succession plan within the corporate structure.
Hergert's decision to leave Red Hat stemmed from the company repeatedly denying his requests for an internal transfer to their France office, where he wished to relocate.
His new long-stay visitor visa in France prohibits him from working, necessitating a complete professional shift away from his previous open-source maintenance roles.
Hergert dedicated over two decades to maintaining and developing key components across the GNOME platform and its surrounding ecosystem, often working beyond 40 hours a week without pay for some projects.
He stressed that the long-term stewardship of these widely used projects, critical for major Linux distributions and enterprise environments, requires funded, dedicated work rather than sporadic spare-time contributions.
This situation is not unique, with other GNOME ecosystem projects like Dash to Panel and LibXML2 previously facing similar maintainer crises.
GitHub issue for Dash to Panel, indicating a need for maintainer help
[
00:04:58
]
GNOME Discourse post announcing a maintainer stepping down from LibXML2
[
00:05:19
]
Key Projects Affected by Lack of Maintainership [5:42]
Status: Similar to GTK Source View, recent activity is limited to translation work. No issues have been closed in the past two months, demonstrating a lack of active development.
GNOME Text Editor GitLab commit history, revealing only translation work since the maintainer's departure announcement
[
00:06:48
]
GNOME Text Editor GitLab issues, showing few closed issues in the past two months
[
00:07:00
]
Description: A popular terminal emulator for GNOME, widely adopted as the default terminal in distributions like Fedora, Debian, and Ubuntu, considered superior to the standard GNOME Terminal.
Status: Despite its popularity and foundational role, it also had a single maintainer, with recent commits primarily being translation updates. This highlights that popularity doesn't guarantee a large development team.
Ptyxis GitLab commit history, showing minimal core development and mostly translation activity
[
00:07:48
]
Description: A crucial bridge between GTK and Enchant 2 for spell-checking functionality.
Status: Primarily sees translation work. While a slower-moving project, its last closed issue was six months prior, suggesting slow or minimal maintenance.
Libspelling GitLab commit history, indicating slow development with infrequent commits beyond translations
[
00:08:08
]
Description: GNOME's flagship IDE (Integrated Development Environment).
Status: Shows some closed issues and a recent Flatpak-related change a month ago, with Jordan Petridis seemingly taking on a minor maintainership role.
Builder GitLab commit history, showing some activity in issue closing and a recent Flatpak update
[
00:08:58
]
Builder GitLab issues, showing some discussion on a closed issue
[
00:09:21
]
Description: Provides templating and a small language runtime for a scriptable GObject introspection syntax.
Status: A less frequently updated project, with its last merge request a year ago. It's considered likely to remain stable for a while without active maintenance.
Template GLib GitLab commit history, indicating very infrequent changes with the last merge request over a year ago
[
00:09:57
]
Template GLib merge requests, showing only nine merged requests over its entire lifespan
[
00:10:06
]
Description: Offers Futures, Fibers, and io_uring integration.
Status: A patch was applied six days prior, and Christian Hergert is still partially maintaining this project, indicating some continued, albeit limited, involvement.
Libdex GitLab commit history, showing a recent patch merged by Christian Hergert
[
00:11:17
]
Description: Handles data object binding between GObject and SQLite.
Status: These foundational projects, though important, are often "boring" and struggle to attract new maintainers. The last merge was five months prior.
GOM GitLab commit history, showing infrequent updates, with the last merge five months prior
[
00:12:07
]
Description: QEMU mouse, keyboard, and screen implementation with DMA-buff integration for GTK.
Status: The last commit to main was two years prior, indicating it is effectively unmaintained.
Libmks GitLab commit history, showing the last commit to the main branch was two years ago
[
00:13:36
]
The Underlying Problem: Lack of Interest in Foundational Projects [15:21]
The consistent issue in the FOSS (Free and Open Source Software) space is the reluctance of developers to work on "boring" but essential foundational projects, libraries, and background glue code that holds the ecosystem together.
While major libraries like GTK and Qt attract contributors, the less visible, deeply technical components often go unnoticed and unmaintained.
Contributions to highly visible environments like GNOME or XFCE are recognized, but changes to obscure integration libraries or low-level components often go unappreciated by even most developers.
This phenomenon extends to critical but less glamorous areas like printing, which fewer people use outside of specific environments, further limiting the pool of potential contributors.
The open-source model's ability to function despite this inherent challenge, with individuals willing to work on these obscure foundational libraries, is remarkable.
The video encourages potential contributors to consider getting involved with these overlooked projects that genuinely need active maintainers, rather than adding to already popular projects.
It emphasizes the ongoing need for committed developers to address issues and ensure the long-term sustainability of these vital components.
