TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

The Bus Factor: Life for Open-Source Projects After a Developer's Death

30 pointsby klintover 7 years ago

2 comments

chisover 7 years ago
Why not just fork the repo? I’d be annoyed if software I depended on was taken over by new management and messed with with.
评论 #15639350 未加载
zbentleyover 7 years ago
This was thought provoking. Questions that arise after reading:<p>- How do you verify proof-of-death of developers who may be working from an environment where they can&#x27;t easily separately verify their identities (e.g. house arrest, or people who are working in secret due to legal or cultural barriers to their being OSS engineers)?<p>- What happens to people whose death is faked, e.g. by a government wishing to take control of a project in order to introduce vulnerabilities or be an obstacle to further development?<p>- What happens when someone dies and people impersonate their family&#x2F;inheritors in order to take control of their projects for unethical reasons? Given that a lot of the value here is political (&quot;lead maintainer&quot;-type titles) as opposed to physical (data on servers somewhere), are there any laws that affect this behavior? This is a regrettably common phenomenon with non-software inheritances; can developer communities do better?<p>- What happens when someone dies who didn&#x27;t leave instructions for the event of their death, and the legally- or traditionally-entitled inheritors harm their project or otherwise act unethically with it? Is the answer just &quot;fork it&quot; with all of the FUD that entails? Or can something else be done?
评论 #15637451 未加载
评论 #15640210 未加载