“源代码可用”不等于开源(这没问题)
'Source available' is not open source (and that's okay)

原始链接: https://dri.es/source-available-is-not-open-source-and-that-is-okay

最近,Ruby on Rails 的创建者 David Heinemeier Hansson (DHH) 与 WordPress 创始人 Matt Mullenweg 之间的一次争论,凸显了开源社区内部持续存在的紧张关系。DHH 发布了 Fizzy,一款看板工具,使用了新的“O’Saasy”许可协议,该协议禁止竞争的 SaaS 产品——这违反了开源倡议组织 (OSI) 的定义。DHH 不予理会批评,认为“开源”仅仅意味着源代码可用。 Mullenweg 反驳说,遵守既定的 OSI 定义至关重要。虽然对定义的争论很重要,但核心问题是*可持续性*。许多公司从开源工作中获利,却没有充分地贡献于其维护和开发。 DHH 的许可协议旨在解决这个问题,允许他的公司建立可持续的业务。然而,它更准确地描述为“源代码可用”,而不是“开源”。这场争论强调了寻找解决方案的必要性——不仅仅是重新命名问题——以激励贡献并解决开源生态系统中的“搭便车”现象。辩论应该集中在*如何*鼓励可持续参与,而不是*如何*称呼它。

## “源代码可用” vs. 开源:一场辩论 一场 Hacker News 的讨论集中在称呼带有使用限制的许可协议为“开源”的有效性上——特别是那些阻止 SaaS 竞争的协议,例如 David Heinemeier Hansson (DHH) 的新许可协议。 许多人认为这具有误导性,因为真正的开源允许不受限制的使用,包括商业竞争。 这场辩论的核心在于,限制使用场景是否会使许可协议失去被视为“开源”的资格,即使源代码是*可用*的。 一些人认为 DHH 试图两者兼得。 另一些人指出另一种形式的“源代码可用”,即代码以 OSI 批准的许可协议(如 BSD 或 GPL)发布,但缺乏强大的社区参与——认为这也是对开源精神的一种偏离,尽管在技术上仍然符合资格。 然而,贡献者承认,即使没有保证接受贡献,分叉和修改代码的权利仍然是开源的本质。 最终,这场讨论强调了维护“开源”定义的完整性以及真正不受限制的代码访问的重要性。 虽然“源代码可用”许可协议可能是有益的,但它们不应稀释开源的含义。
相关文章

原文

I have spent twenty years working on open source sustainability, so watching a fight ignite between Ruby on Rails creator David Heinemeier Hansson and WordPress founding developer Matt Mullenweg this week felt uncomfortably familiar in a way I wish it didn't.

David Heinemeier Hansson (also known as DHH) released a new kanban tool, Fizzy, this week and called it open source.

People quickly pointed out that the O'Saasy license that Fizzy is released under blocks others from offering a competing SaaS version, which violates the Open Source Initiative's definition. When challenged, he brushed it off on X and said, "You know this is just some shit people made up, right?". He followed with "Open source is when the source is open. Simple as that".

This morning, Matt Mullenweg rightly pushed back. He argued that you can't ignore the Open Source Initiative definition. He compared it to North Korea calling itself a democracy. A clumsy analogy, but the point stands.

Look, the term "open source" has a specific, shared meaning. It is not a loose idea and not something you can repurpose for marketing. Thousands of people shaped that definition over decades. Ignoring that work means benefiting from the community while setting aside its rules.

This whole debate becomes spicier knowing that DHH was on Lex Fridman's podcast only a few months ago, appealing to the spirit and ethics of open source to criticize Matt's handling of the WP Engine dispute. If the definition is just "shit people made up", what spirit was Matt violating?

The definition debate matters, but the bigger issue here is sustainability. DHH's choice of license reacts to a real pressure in open source: many companies make real money from open source software while leaving the hard work of building and maintaining it to others.

This tension also played a role in Matt's fight with WP Engine, so he and DHH share some common ground, even if they handle it differently. We see the same thing in Drupal, where the biggest companies do not always contribute at the same level.

DHH can experiment because Fizzy is new. He can choose a different license and see how it works. Matt can't as WordPress has been under the GPL for more than twenty years. Changing that now is virtually impossible.

Both conversations are important, but watching two of the most influential people in open source argue about definitions while we all wrestle with free riders feels a bit like firefighters arguing about hose lengths during a fire.

The definition debate matters because open source only works when we agree on what the term means. But sustainability decides whether projects like Drupal, WordPress, and Ruby on Rails keep thriving for decades to come. That is the conversation we need to have.

In Drupal, we are experimenting with contribution credits and with guiding work toward companies that support the project. These ideas have helped, but also have not solved the imbalance.

Six years ago I wrote in my Makers and Takers blog post that I would love to see new licenses that "encourage software free riding", but "discourage customer free riding". O'Saasy is exactly that kind of experiment.

A more accurate framing would be that Fizzy is source available. You can read it, run it, and modify it. But DHH's company is keeping the SaaS rights because they want to be able to build a sustainable business. That is defensible and generous, but it is not open source.

I still do not have the full answer to the open source sustainability problem. I have been wrestling with it for more than twenty years. But I do know the solution is not renaming the problem.

Some questions are worth asking, and answering:

  • How do we distinguish between companies that can't contribute and those that won't?
  • What actually changes corporate behavior: shame, self-interest, punitive action, exclusive benefits, or regulation?

If this latest fight nudges us away from word games and toward these questions, some good may come from it.

联系我们 contact @ memedata.com