#busfactor — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #busfactor, aggregated by home.social.
-
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: https://www.zdnet.com/article/linux-community-project-continuity-plan-for-replacing-linus-torvalds/
#LinuxKernel #ProjectContinuityPlan
#OpenSource #KernelDevelopment
#LinuxCommunity #Maintainer
#Linux #TechnicalLeadership
#BusFactor #RiskManagement
#LinuxFoundation #MaintainerSummit
#TechnicalAdvisoryBoard
#TAB #LinusTorvalds
#GregKroahHartman
#KernelMaintainer -
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: https://github.com/potatoqualitee/eol-dr
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
-
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: https://github.com/potatoqualitee/eol-dr
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
-
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: https://github.com/potatoqualitee/eol-dr
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
-
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: https://github.com/potatoqualitee/eol-dr
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
-
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: https://github.com/potatoqualitee/eol-dr
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
-
Pixelfed has a far smaller bus factor than Mastodon. What is Pixelfed's maintainer doing to reduce key person risk?
#pixelfed #dansup #busfactor #keypersonrisk #softwaredevelopment #fediverse #photosharing #opensource -
☝️ 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? 🤷♂️
https://www.mindflash.org/coding/ai/ai-and-the-bus-factor-of-0-1608 #AmazonEngineer #AIHubris #BusFactor #TechIrony #BackupPlan #HackerNews #ngated -
☝️ 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? 🤷♂️
https://www.mindflash.org/coding/ai/ai-and-the-bus-factor-of-0-1608 #AmazonEngineer #AIHubris #BusFactor #TechIrony #BackupPlan #HackerNews #ngated -
☝️ 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? 🤷♂️
https://www.mindflash.org/coding/ai/ai-and-the-bus-factor-of-0-1608 #AmazonEngineer #AIHubris #BusFactor #TechIrony #BackupPlan #HackerNews #ngated -
☝️ 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? 🤷♂️
https://www.mindflash.org/coding/ai/ai-and-the-bus-factor-of-0-1608 #AmazonEngineer #AIHubris #BusFactor #TechIrony #BackupPlan #HackerNews #ngated -
💯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.
-
@vaurora: In this case it was rather "not enough people involved" istead of "too many involved": See #busfactor and https://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.
-
@johnm I have similar concerns about #CondaForge #BusFactor again from the perspective of a minor contributor to/of a few recipes.
-
@jerry I'd tried setting up a resource for Google+ refugees, which ... turned out to be hard.
Lessons learned, however, at https://social.antefriguserat.de/index.php/Main_Page.
Related subreddit: https://old.reddit.com/r/plexodus/
I've been meaning to compile a set of lessons learned, of possible interest to you and perhaps @evacide (I'd initiated contacts w/ EFF a ways back but dropped that ball).
Community is a lot harder to preserve than content. Existing social media platforms aren't just the publisher but the directory.
Move to an established platform. Even if it's not ideal, something that's up right now beats the heck out of still-in-development (or not even that) options.
Mailing lists are highly underappreciated. They offer an out-of-band universal contact mechanism: email addresses.
Though managed migration of community is hard ... informal migration can still be surprisingly effective if people know where to find you. Post VERY PROMINENT NOTICES of where you'll be moving to.
#SIGNALFLARE was a mechanism created and employed heavily at G+. The hashtag, plus a set of contacts and alternate platforms at which you could be found was encouraged. I'd compiled many of those in a Notable Names Database: https://social.antefriguserat.de/index.php/G%2B_Notable_Names_Database
Once a platform has either announced it will be shutting down, or appears quite likely to do so for other reasons, the best thing to do is to establish alternative presences sooner rather than later.
In fact, better than that is to have a multi-platform strategy from the start. Do NOT put all your eggs in one basket. (Jerry with mailing list, blog, podcast, Twitter, and Mastodon presences is an exemplar here.)
There's a notion of three types of people in an emergency: 1) deer in the headlights, 2) show us what to do, and 3) this ship's unsinkable. Numbers 1 & 3 can't be helped, group 2 are your squad. (There are also a few other categories, including griefers and profiteers/opportunists.) For a platform migration, the good news is that few people are likely to die, so groups 1 & 3 will eventually rediscover the main body, but during the transition they're of less than no use.
People do in fact die. The refugee Diaspora* instance for G+ refugees, Pluspora.com, failed after its admin died, without any continuity / transfer-of-leadership plan. Joindiaspora, the original Diaspora* instance, after both technical debt and an AWOL admin meant that it was no longer viable. #BusFactor is a real problem, continuity needs addressing.
There's more I could write, this is probably a good start.
#TwitterExodus #Plexodus #CommunityMigration #CommunityContinuity #SwitchingPlatforms
-
@jerry I'd tried setting up a resource for Google+ refugees, which ... turned out to be hard.
Lessons learned, however, at https://social.antefriguserat.de/index.php/Main_Page.
Related subreddit: https://old.reddit.com/r/plexodus/
I've been meaning to compile a set of lessons learned, of possible interest to you and perhaps @evacide (I'd initiated contacts w/ EFF a ways back but dropped that ball).
Community is a lot harder to preserve than content. Existing social media platforms aren't just the publisher but the directory.
Move to an established platform. Even if it's not ideal, something that's up right now beats the heck out of still-in-development (or not even that) options.
Mailing lists are highly underappreciated. They offer an out-of-band universal contact mechanism: email addresses.
Though managed migration of community is hard ... informal migration can still be surprisingly effective if people know where to find you. Post VERY PROMINENT NOTICES of where you'll be moving to.
#SIGNALFLARE was a mechanism created and employed heavily at G+. The hashtag, plus a set of contacts and alternate platforms at which you could be found was encouraged. I'd compiled many of those in a Notable Names Database: https://social.antefriguserat.de/index.php/G%2B_Notable_Names_Database
Once a platform has either announced it will be shutting down, or appears quite likely to do so for other reasons, the best thing to do is to establish alternative presences sooner rather than later.
In fact, better than that is to have a multi-platform strategy from the start. Do NOT put all your eggs in one basket. (Jerry with mailing list, blog, podcast, Twitter, and Mastodon presences is an exemplar here.)
There's a notion of three types of people in an emergency: 1) deer in the headlights, 2) show us what to do, and 3) this ship's unsinkable. Numbers 1 & 3 can't be helped, group 2 are your squad. (There are also a few other categories, including griefers and profiteers/opportunists.) For a platform migration, the good news is that few people are likely to die, so groups 1 & 3 will eventually rediscover the main body, but during the transition they're of less than no use.
People do in fact die. The refugee Diaspora* instance for G+ refugees, Pluspora.com, failed after its admin died, without any continuity / transfer-of-leadership plan. Joindiaspora, the original Diaspora* instance, after both technical debt and an AWOL admin meant that it was no longer viable. #BusFactor is a real problem, continuity needs addressing.
There's more I could write, this is probably a good start.
#TwitterExodus #Plexodus #CommunityMigration #CommunityContinuity #SwitchingPlatforms
-
@jerry I'd tried setting up a resource for Google+ refugees, which ... turned out to be hard.
Lessons learned, however, at https://social.antefriguserat.de/index.php/Main_Page.
Related subreddit: https://old.reddit.com/r/plexodus/
I've been meaning to compile a set of lessons learned, of possible interest to you and perhaps @evacide (I'd initiated contacts w/ EFF a ways back but dropped that ball).
Community is a lot harder to preserve than content. Existing social media platforms aren't just the publisher but the directory.
Move to an established platform. Even if it's not ideal, something that's up right now beats the heck out of still-in-development (or not even that) options.
Mailing lists are highly underappreciated. They offer an out-of-band universal contact mechanism: email addresses.
Though managed migration of community is hard ... informal migration can still be surprisingly effective if people know where to find you. Post VERY PROMINENT NOTICES of where you'll be moving to.
#SIGNALFLARE was a mechanism created and employed heavily at G+. The hashtag, plus a set of contacts and alternate platforms at which you could be found was encouraged. I'd compiled many of those in a Notable Names Database: https://social.antefriguserat.de/index.php/G%2B_Notable_Names_Database
Once a platform has either announced it will be shutting down, or appears quite likely to do so for other reasons, the best thing to do is to establish alternative presences sooner rather than later.
In fact, better than that is to have a multi-platform strategy from the start. Do NOT put all your eggs in one basket. (Jerry with mailing list, blog, podcast, Twitter, and Mastodon presences is an exemplar here.)
There's a notion of three types of people in an emergency: 1) deer in the headlights, 2) show us what to do, and 3) this ship's unsinkable. Numbers 1 & 3 can't be helped, group 2 are your squad. (There are also a few other categories, including griefers and profiteers/opportunists.) For a platform migration, the good news is that few people are likely to die, so groups 1 & 3 will eventually rediscover the main body, but during the transition they're of less than no use.
People do in fact die. The refugee Diaspora* instance for G+ refugees, Pluspora.com, failed after its admin died, without any continuity / transfer-of-leadership plan. Joindiaspora, the original Diaspora* instance, after both technical debt and an AWOL admin meant that it was no longer viable. #BusFactor is a real problem, continuity needs addressing.
There's more I could write, this is probably a good start.
#TwitterExodus #Plexodus #CommunityMigration #CommunityContinuity #SwitchingPlatforms
-
@jerry I'd tried setting up a resource for Google+ refugees, which ... turned out to be hard.
Lessons learned, however, at https://social.antefriguserat.de/index.php/Main_Page.
Related subreddit: https://old.reddit.com/r/plexodus/
I've been meaning to compile a set of lessons learned, of possible interest to you and perhaps @evacide (I'd initiated contacts w/ EFF a ways back but dropped that ball).
Community is a lot harder to preserve than content. Existing social media platforms aren't just the publisher but the directory.
Move to an established platform. Even if it's not ideal, something that's up right now beats the heck out of still-in-development (or not even that) options.
Mailing lists are highly underappreciated. They offer an out-of-band universal contact mechanism: email addresses.
Though managed migration of community is hard ... informal migration can still be surprisingly effective if people know where to find you. Post VERY PROMINENT NOTICES of where you'll be moving to.
#SIGNALFLARE was a mechanism created and employed heavily at G+. The hashtag, plus a set of contacts and alternate platforms at which you could be found was encouraged. I'd compiled many of those in a Notable Names Database: https://social.antefriguserat.de/index.php/G%2B_Notable_Names_Database
Once a platform has either announced it will be shutting down, or appears quite likely to do so for other reasons, the best thing to do is to establish alternative presences sooner rather than later.
In fact, better than that is to have a multi-platform strategy from the start. Do NOT put all your eggs in one basket. (Jerry with mailing list, blog, podcast, Twitter, and Mastodon presences is an exemplar here.)
There's a notion of three types of people in an emergency: 1) deer in the headlights, 2) show us what to do, and 3) this ship's unsinkable. Numbers 1 & 3 can't be helped, group 2 are your squad. (There are also a few other categories, including griefers and profiteers/opportunists.) For a platform migration, the good news is that few people are likely to die, so groups 1 & 3 will eventually rediscover the main body, but during the transition they're of less than no use.
People do in fact die. The refugee Diaspora* instance for G+ refugees, Pluspora.com, failed after its admin died, without any continuity / transfer-of-leadership plan. Joindiaspora, the original Diaspora* instance, after both technical debt and an AWOL admin meant that it was no longer viable. #BusFactor is a real problem, continuity needs addressing.
There's more I could write, this is probably a good start.
#TwitterExodus #Plexodus #CommunityMigration #CommunityContinuity #SwitchingPlatforms
-
@jerry I'd tried setting up a resource for Google+ refugees, which ... turned out to be hard.
Lessons learned, however, at https://social.antefriguserat.de/index.php/Main_Page.
Related subreddit: https://old.reddit.com/r/plexodus/
I've been meaning to compile a set of lessons learned, of possible interest to you and perhaps @evacide (I'd initiated contacts w/ EFF a ways back but dropped that ball).
Community is a lot harder to preserve than content. Existing social media platforms aren't just the publisher but the directory.
Move to an established platform. Even if it's not ideal, something that's up right now beats the heck out of still-in-development (or not even that) options.
Mailing lists are highly underappreciated. They offer an out-of-band universal contact mechanism: email addresses.
Though managed migration of community is hard ... informal migration can still be surprisingly effective if people know where to find you. Post VERY PROMINENT NOTICES of where you'll be moving to.
#SIGNALFLARE was a mechanism created and employed heavily at G+. The hashtag, plus a set of contacts and alternate platforms at which you could be found was encouraged. I'd compiled many of those in a Notable Names Database: https://social.antefriguserat.de/index.php/G%2B_Notable_Names_Database
Once a platform has either announced it will be shutting down, or appears quite likely to do so for other reasons, the best thing to do is to establish alternative presences sooner rather than later.
In fact, better than that is to have a multi-platform strategy from the start. Do NOT put all your eggs in one basket. (Jerry with mailing list, blog, podcast, Twitter, and Mastodon presences is an exemplar here.)
There's a notion of three types of people in an emergency: 1) deer in the headlights, 2) show us what to do, and 3) this ship's unsinkable. Numbers 1 & 3 can't be helped, group 2 are your squad. (There are also a few other categories, including griefers and profiteers/opportunists.) For a platform migration, the good news is that few people are likely to die, so groups 1 & 3 will eventually rediscover the main body, but during the transition they're of less than no use.
People do in fact die. The refugee Diaspora* instance for G+ refugees, Pluspora.com, failed after its admin died, without any continuity / transfer-of-leadership plan. Joindiaspora, the original Diaspora* instance, after both technical debt and an AWOL admin meant that it was no longer viable. #BusFactor is a real problem, continuity needs addressing.
There's more I could write, this is probably a good start.
#TwitterExodus #Plexodus #CommunityMigration #CommunityContinuity #SwitchingPlatforms