开源并不意味着开放社区。
Open source does not imply open community

原始链接: https://blog.feld.me/posts/2026/04/open-source-does-not-imply-open-community/

这篇短文哀叹了开源开发的演变,认为它已成为维护者不可持续的“第二份工作”。最初,开源很简单:代码通过基本网站、FTP和电子邮件共享,促进协作,而没有现代“社区”管理的压力。 Sourceforge等平台以及最终的GitHub的兴起,引入了正式的流程——问题、拉取请求、路线图——模仿了传统的软件公司。虽然本意是促进协作,但这给维护者带来了对持续可用性、利益相关者管理和冲突解决的期望。 作者提倡回归早期、更简单的模式。他们建议尽量减少外部互动,专注于与值得信赖的合作者进行个人项目,并拒绝大型、常常混乱的“社区”的需求。他们认为,真正的开源并不*需要*开放开发;它只需要可访问的代码。核心信息是,通过优先编码而不是持续的运营和支持,来夺回控制权和乐趣。

黑客新闻 新 | 过去 | 评论 | 提问 | 展示 | 招聘 | 提交 登录 开源并不意味着开放社区 (feld.me) 9点 由 RohanAdwankar 53分钟前 | 隐藏 | 过去 | 收藏 | 讨论 帮助 考虑申请YC 2026年夏季项目!申请截止至5月4日 指南 | 常见问题 | 列表 | API | 安全 | 法律 | 申请YC | 联系 搜索:
相关文章

原文

Open source software has existed long before the invention of the (D)VCS. The author likely hosted a barebones HTML webpage or a txt file describing the project. There definitely was an FTP server somewhere with tarballs. The author may have been reachable by email.

If you were really lucky, there was a mailing list you could sign up for to receive announcements and maybe discuss the software with other interested parties. There might have been an unofficial IRC channel someone created under the name of the software so people could discuss it.

This was and still is open source.

No "community". No politics. No Code of Conduct. No pull requests or issues. No wiki. No core team.

Later, we had sites like Sourceforge. You got your CVS/SVN and mailing lists operated for essentially "free", and it was easier to build in the open.

Then came the DVCS wars which git decidedly won, and the world eventually converged on Github.

"In the late 00's, Github was created. This has made a lot of people very angry and been widely regarded as a bad move." - Douglas Adams if he were alive today.

Github turned all of open source into an unpaid job for maintainers. You go to work and find newly assigned tickets; have meetings with stakeholders; plan a roadmap; deal with office politics and distractions; hit your deadlines, metrics, and KPIs; come into work one day and learn the requirements have changed again and now you have to start over. Standups. One-on-ones. Agile. Waterfall. But you're getting a paycheck and health insurance, so you just deal with the nonsense.

Then you come home from work and it's time to unwind on something you enjoy. Ding, you've got notifications. Issues are piling up. Pull requests are being flung in your direction completely rearchitecting the software to do things that were never really within scope. Complaints. Demands. There's now a chat group. People with no patience are angry and now you have to babysit them, have your own one-on-ones. There's a "community" now that you're responsible for. You never signed up for this, but this baggage is just the way it is, right? Suddenly open source is a second job. You're burned out. You don't even have control or direction over your own project anymore without your name being dragged through the mud.

Some projects are so huge and complicated that it requires a team to manage them. But this the exception, not the rule.

Free yourself. Go back to the old ways. Especially if you're angry about the influx of new people and AI bots stealing your attention.

Turn off the issues tracker and the pull requests or deploy a bare git server for releasing your code. Find a small group of people you really know and trust and work with them on projects, or do it completely alone.

You don't need to allow strangers to invade your space. You don't need a performative Code of Conduct or an LLM policy. Open source doesn't need to be developed openly for it to be "open source".

Write code. Make things you like. Use any tools you want. Do code drops at 2am on Christmas day. Whatever you do, don't get tricked into running an operation that's half tech incubator and half daycare for people whose parents gave them a keyboard and no social skills.

联系我们 contact @ memedata.com