#BusFactor

gnu0os0ta ✅🐧gnu0os0ta@fedi.at
2026-02-01

Wie der Linux‑Kernel seine Zukunft absichert!

Die Linux‑Kernel‑Community hat nach über 30 Jahren Projektgeschichte erstmals einen formalen Project Continuity Plan verabschiedet. Ziel dieses Dokuments ist es, verbindlich zu regeln, wie die technische Gesamtverantwortung für den Linux‑Kernel neu organisiert wird, falls der derzeitige Haupt‑Maintainer Linus Torvalds unerwartet ausfällt oder sich planmäßig aus seiner Rolle zurückzieht. Damit reagiert das Projekt auf ein bislang bestehendes strukturelles Risiko, da nahezu alle finalen Merge‑Entscheidungen zentral bei einer einzelnen Person liegen.

Der Continuity Plan verzichtet bewusst auf die Benennung eines festen Nachfolgers. Stattdessen definiert er einen prozessorientierten Ansatz zur Bestimmung der künftigen Projektleitung. Im Ereignisfall ist ein Organizer üblicherweise der Organisator des zuletzt abgehaltenen Linux Maintainer Summit, ersatzweise der Vorsitzende des Technical Advisory Board (TAB) der Linux Foundation verpflichtet, innerhalb von 72 Stunden ein Entscheidungsgremium einzuberufen. Dieses Gremium setzt sich aus den eingeladenen Teilnehmern des letzten Maintainer Summit sowie Mitgliedern des Technical Advisory Board zusammen.

Das einberufene Gremium hat einen Zeitraum von bis zu zwei Wochen, um über die zukünftige Struktur der Kernel‑Leitung zu beraten und eine Entscheidung herbeizuführen. Der Plan lässt dabei mehrere Organisationsmodelle ausdrücklich zu. Neben der Ernennung eines einzelnen neuen Haupt‑Maintainers sind auch kollektive Führungsmodelle oder alternative Governance Strukturen möglich. Die getroffene Entscheidung ist der Kernel‑Community anschließend transparent und öffentlich zu kommunizieren.

Mit diesem Verfahren soll insbesondere das sogenannte Bus‑Factor‑1‑Risiko reduziert werden, das sich aus der bisherigen Konzentration der finalen Verantwortung auf Linus Torvalds ergibt. Der Artikel weist darauf hin, dass in der aktuellen Maintainer‑Struktur Greg Kroah‑Hartman, langjähriger Maintainer der stabilen Kernel‑Releases, faktisch als naheliegender Kandidat gelten könnte. Der Continuity Plan vermeidet jedoch bewusst eine solche Festlegung, um im Bedarfsfall flexibel auf personelle, organisatorische und technische Rahmenbedingungen reagieren zu können.

Der Plan ist nicht als Hinweis auf einen unmittelbar bevorstehenden Führungswechsel zu verstehen. Linus Torvalds ist derzeit 56 Jahre alt, weiterhin aktiv als Haupt Maintainer tätig und hat nach Angaben des Artikels keine Absicht, sich in absehbarer Zeit aus dem Projekt zurückzuziehen. Vielmehr stellt der Project Continuity Plan eine präventive Maßnahme dar, die der langfristigen Stabilität eines zentralen Open‑Source‑Infrastrukturprojekts dient. Vor dem Hintergrund einer alternden Maintainer Basis und zunehmender Schwierigkeiten bei der Gewinnung neuer Kernel Maintainer schafft der Plan einen klar definierten Rahmen für den Umgang mit einem möglichen Führungsvakuum.

Quelle: zdnet.com/article/linux-commun

#LinuxKernel #ProjectContinuityPlan
#OpenSource #KernelDevelopment
#LinuxCommunity #Maintainer
#Linux #TechnicalLeadership
#BusFactor #RiskManagement
#LinuxFoundation #MaintainerSummit
#TechnicalAdvisoryBoard
#TAB #LinusTorvalds
#GregKroahHartman
#KernelMaintainer

Dmytro (Dima) Oliinykdima@dol.social
2026-01-13

While planning my NAS build, I had a sobering realization. My "Bus Factor" at home is exactly 1.

I'm going to spend so much time securing my data against drive failures and hackers but what about my family? If something happens to me, my homelab becomes a digital tomb that no one has the keys to.

I dug up this repo I bookmarked a while ago: eol-dr (End of Life / Disaster Recovery). It’s basically a framework for documenting your digital life for your loved ones.

GitHub: github.com/potatoqualitee/eol-

Configuring a RAID array is easy. Writing a "How to access our photos when I'm gone" guide is the hard part. Probably, the hardest. But it's arguably the most important backup you'll ever make.
Hope it'll be useful for somebody. Just make a star and take a look later when you feel it's a time.

#SelfHosted #Homelab #DigitalLegacy #OpSec #SysAdmin #Privacy #LifeTips #BusFactor #Backup #Nas #Death #Thoughts #Blog

2026-01-06

@benjamineskola

Gilbert Healton was not the only customer who went elsewhere, if the note about only 'select clients' having hosting service nowadays is anything to go by.

exit109.com./news/

@ianbetteridge

#Exit109 #NewJersey #LinkRot #BusFactor

cathillcathill
2025-12-15

Pixelfed has a far smaller bus factor than Mastodon. What is Pixelfed's maintainer doing to reduce key person risk?

cathillcathill
2025-12-12

What is the bus factor of PIxelfed and its developer's instance pixelfed.social?

:awesome:🐦‍🔥nemo™🐦‍⬛ 🇺🇦🍉nemo@mas.to
2025-11-24

@b9AcE @fedora @kde

Also apparmor is used instead of selinux. And it was maintained afaik from only one person #busfactor But besides these interesting :)

petites singularitésps@s10y.eu
2025-10-20

Hi @signalapp, can we talk about the #BusFactor following today's outage of AWS? How comes Signal communications go down when Armagezzon goes down?

N-gated Hacker Newsngate
2025-08-20

☝️ Surprise! Yet another Amazon engineer believes they're uniquely qualified to solve AI's problems while simultaneously ignoring the all-important Bus Factor 🚍💥. Because who needs a backup plan when you've got infinite hubris? 🤷‍♂️
mindflash.org/coding/ai/ai-and

2025-07-02

💯th citation for our work on "Assessing the bus factor of git repositories"

A good related research question today would be whether #bots / #agents reduce the bus factor risk compared to when humans were the only contributors to a project.

#SANER15 #busfactor #git #research #opensource #oss #msr

scholar.google.es/citations?vi

Karsten Schmidttoxi@mastodon.thi.ng
2025-04-26

Reading about Google keeping their long tradition of discontinuing products/services, often after just a few years[1]. On the other hand, the minimal "bus factor"[2] of my open source offerings is one of the stated reasons for people to not use them, even though the vast majority of the 200+ thi.ng/ libraries & tools has been actively maintained for much longer than many Google projects (99% by this single person)... Even many of my older projects which are defunkt by now have had an active period which outlasted many Google services, and — crucially — they're are stable, still available and can still be used now (e.g. my Java library collection developed between 2005-2013 still has regular users)...

Maybe internal politics, re-orgs and layoffs in BigTech are an equal/bigger risk factor for users (aside from other differences in design philosophy and resulting coupling and tech debt, e.g. massive all-in frameworks vs. lightweight composable pick-n-mix toolkits)? 🤔

[1] killedbygoogle.com/
[2] en.wikipedia.org/wiki/Bus_fact

#OpenSource #BusFactor #Maintenance

Henrik Schönemannlavaeolus@fedihum.org
2025-01-23

Please share with your colleagues:
Asking all US-based scientists:
Are there repositories of #OpenAccess papers etc. pp. that need mirrored?
(I'm proud #GuerillaOpenAccess, but not currently trying to do an Aaron Swartz #RIP 😢)

You've got research to safeguard?
Consider uploading to zenodo.org (run by CERN, well established, trustworthy, you can private your uploads)

To organize: matrix.to/#/#safeguarding-rese
(Everyone welcome! #BusFactor)

@academicchatter @academicsunite

Carmen Bianca BAKKERcarmenbianca@todon.eu
2024-10-22

stop using niche #linux distributions already p l e a s e.

just use #debian, #ubuntu, #fedora, or even #opensuse. these titanic collective efforts are so much better at creating a good, reliable, secure, and accessible computing environment than today's Distro Of The Week with a #BusFactor of one (1).

thank you.

2024-10-10

@tlaurion @jrf_nl @opencollective Listening to the keynote, I wrote for communal clarity in case of #maintainer #death and how to continue maintenance of my #FOSS #projects.

github.com/niccokunzmann/case-

Really, I wonder how to reach out to increase the #busFactor of my projects. But in case this has not happened tomorrow, there is my #software #will :)

My intention is also to flag up the issues we face as a community.

Dmitri Goosens :elephpant:dgoosens@phpc.social
2024-04-11
Axel ⌨🐧🐪🚴😷☕️ | #WeAreNatenomxtaran@chaos.social
2024-03-30

@vaurora: In this case it was rather "not enough people involved" istead of "too many involved": See #busfactor and xkcd.com/2347 #xkcd2347

This was only possible because the original maintainer did that work alone and seems to have been close to a #burnout and urgently needed someone to step in. So it was easy to get the co-maintainer position without long-time #trust being involved.

#JiaT75 #xzorcist #xz #FLOSS

Dmitri Goosens :elephpant:dgoosens@phpc.social
2024-02-23

Funny... But lets not forget the real unprofessional problem is for a company to rely on a #BusFactor of 1.

(see en.wikipedia.org/wiki/Bus_fact)

Konstantin Weddigeweddige@gruene.social
2024-01-20

@dansup as far as I know, you do almost all of the development on pixelfed yourself. Would this be an opportunity to move to a maintainer team?

#busfactor

2024-01-14

People who use GitHub: have you designated an account successor in case something happens to you?

A successor cannot log into your account, but can manage your public repositories after presenting proof of your death.

Probably something we should all do sooner rather than later, especially if we're responsible for projects that other people rely on …

docs.github.com/en/account-and
#GitHub #BusFactor

2024-01-10

@johnm I have similar concerns about #CondaForge #BusFactor again from the perspective of a minor contributor to/of a few recipes.

Arnaud Langlandearnolanglade
2023-11-16

🚌 Facteur de bus : évitez de mettre tous vos œufs dans le même panier

J'ai discuté avec quelqu'un dont le CTO était la seule personne à intervenir sur les parties critiques de leur application. Cela m’a rappelé le concept du "Bus Factor."

J'explique 🧵👇[1/4]

Photo by Rock Staar on Unsplash:

https://unsplash.com/photos/white-and-blue-bus-near-palm-tree-under-blue-sky-during-daytime-wGyHvtLcW_U

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst