This is a sobering post that revisits the notion that given a project, how many developers have to be hit by a bus before it stalls.

According to the methodology explained in the article, in 2015 it took 57 developers for the Linux kernel to fail, now it appears that it takes 8.

That’s not good.

  • eldavi@lemmy.ml
    link
    fedilink
    arrow-up
    20
    ·
    edit-2
    9 days ago

    the years as a system admin taught me that you can identify the influential contributors because they were the only people whose accounts were not immediately shut off when the management identified a bus factor.

    and now i have a name for the phenomena; thank you.

  • ikidd@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    ·
    9 days ago

    I always thought the more developers you added the higher the likelihood of stalling.

    • davad@lemmy.world
      link
      fedilink
      arrow-up
      28
      ·
      9 days ago

      Two different concepts.

      You’re talking about work slowing because of increased overhead from more people needing to communicate and make decisions.

      The OP is talking about the"bus factor". How many people can leave the project unexpectedly and still have the project survive. E.g. if only one person has access to merge changes, the bus factor is 1 regardless of how many people actively contribute.

  • Bob Smith@sopuli.xyz
    link
    fedilink
    arrow-up
    10
    arrow-down
    2
    ·
    edit-2
    9 days ago

    If the lessons that I’ve learned about lightbulb replacement are applicable, then the nationality of the developers on the bus will impact the answer to your question.