Windmill.dev 并不是“完全开源的(AGPLv3)”。

3 分•作者: alpine-rockies•大约 1 个月前•原帖
我认为 Windmill.dev (https://github.com/windmill-labs/windmill) 非常酷,并且我完全支持他们希望为自己的工作获得报酬的愿望。 然而,他们的 README 中写道: > “Windmill 是完全开源的(AGPLv3)…” 但他们的 LICENSE 中却写道: > ... backend/ 下的文件是 AGPLv3 许可的,除了任何在“enterprise”编译标志下的代码片段。这些代码片段和文件是基于专有和商业许可的。私有和公共的分支必须不包含上述提到的专有/商业代码。 我深入研究了代码库,发现大约有 300 个文件包含对企业或私有功能的引用,因此并没有一个可以简单删除的明确分隔目录。 我在 GitHub 上看到他们的代码库有 1.1k 个分支,我怀疑所有这些分支都花时间去剔除专有代码以遵守许可证。 所以在这一点上,感觉这对任何点击 GitHub 上的分支按钮或被 AGPL 许可证吸引的人来说,都是一个许可陷阱。 不要误解我的意思,我希望更多的公司能够开源他们的代码,哪怕只是为了透明。但称这个混合源代码库为“完全开源(AGPLv3)”感觉像是虚假宣传,实际上引导用户在不知情的情况下违反条款。 此外,即使那句话从 README 中删除或修正,看到“...私有和公共的分支必须不包含上述提到的专有/商业代码...”与 GitHub 的分支按钮并排放置,还是让人觉得不妥。这就像是一个巨大的违反许可证的按钮与许可证并排放置。
查看原文
I think Windmill.dev (https:&#x2F;&#x2F;github.com&#x2F;windmill-labs&#x2F;windmill) is really cool, and fully support their desire to be paid for their work.<p>However, their README says:<p>&gt; “Windmill is fully open-sourced (AGPLv3)…”<p>But their LICENSE says:<p>&gt; ... The files under backend&#x2F; are AGPLv3 Licensed, except any snippets of code under the compile flag ‘enterprise’. Those snippets and files are under a proprietary and commercial license. Private and public forks MUST not include the proprietary&#x2F;commercial code mentioned above.<p>I dove deeper into the code, there are around 300 files in the codebase that contain references to enterprise or private features, so it&#x27;s not a clearly separated directory that can just be removed.<p>They have 1.1k forks of their repository that I can see on Github, and I doubt all of them took the time to strip the proprietary code to comply with the license.<p>So at this point, it feels like a licensing trap for anyone that clicks the fork button on Github or is attracted by the AGPL license<p>Don&#x27;t get me wrong, I wish more companies made their code open-source if for no other reason other than to be transparent. But calling this mixed source repository &quot;fully open-sourced (AGPLv3)&quot; feels like false advertising that actively leads users to violate the terms unknowingly.<p>Also, even if that line was removed from the readme or fixed, it does not feel right to have: &quot;...Private and public forks MUST not include the proprietary&#x2F;commercial code mentioned above...&quot; and the Github Fork button right next to each other. It&#x27;s like a giant violate-the-license button next to the license.