开源治理
Search documents
“别犯蠢了,”Linus怒怼“AI垃圾代码”争论:靠写文档,根本救不了Linux内核
3 6 Ke· 2026-01-09 11:29
最近几个月,Linux 内核社区一直在激烈讨论一件事:要不要为"工具生成代码"制定一套专门的提交规 范文档? 这里说的"工具",本质上就是指如今越来越常见的 AI 编程助手、LLM 自动生成补丁等现象。随着 Copilot、ChatGPT 等工具深入开发流程,一些维护者开始担心:大量未经理解、质量堪忧的"AI 生成补 丁"正在涌入内核仓库,俗称 AI Slop(AI 垃圾代码)。 围绕是否要在内核文档中专门强调"AI 生成内容的标注与规范",社区争论不休,Linux 之父 Linus Torvalds 也终于忍不住发声了。 在 Linux 内核邮件列表中,Linus 明确表达了他的立场:文档应该聚焦"工具"本身,而不是把矛头直接 对准 AI——原因很简单:不管你写不写文档,AI 辅助提交都会持续存在。 Linus 对"AI 辅助补丁"的态度 在 Linux 社区中,有开发者吐槽,把 LLM 当成'只是另一种工具',本质上就是在宣称 Linux 内核可以 免疫 AI 带来的问题:"在我看来,这是个非常愚蠢的立场。" 对于这个说法,Linus 直接回怼:"不,你的立场才是愚蠢的。"然后,他还补充道:"讨论 AI ...
开源项目遭“夺权”,原核心维护者全被踢出局后怒批:这是一次恶意接管
3 6 Ke· 2025-09-25 07:36
Core Points - The recent controversy in the Ruby community revolves around the management of the RubyGems and Bundler projects, with accusations of a "hostile takeover" by Ruby Central, the non-profit organization overseeing these tools [1][11][12] - Long-time maintainers, including Ellen Dash, have expressed their outrage over being removed from their roles without prior notice or explanation, leading to significant community backlash [5][10][14] - Ruby Central's justification for these actions is centered on enhancing security and governance, citing the need to protect the Ruby ecosystem from supply chain attacks [11][12] Summary by Sections Project Management and Governance - RubyGems and Bundler, essential tools for the Ruby programming language, have been maintained by a dedicated team for years without formal compensation [2] - The abrupt removal of maintainers, including Ellen Dash, was executed by Marty Haught, Ruby Central's open-source director, raising questions about governance practices [5][6][11] Community Response - The Ruby community has reacted strongly against Ruby Central's actions, with many developers expressing disappointment and anger on social media [14][16] - Critics argue that Ruby Central's actions reflect a shift towards corporate influence over community-driven projects, undermining the principles of open-source collaboration [14][16] Future Implications - The incident highlights the ongoing struggle between professional management and community autonomy in open-source governance, emphasizing the need for transparency and communication [20] - As core maintainers resign, the new management team faces scrutiny to prove their capability and maintain community trust [20]