28年老开发者弃MIT转欧盟开源许可
推荐指数 47.0 NO. 015 · 2026.09.07
发布2026/09/06Score140Comments150
为什么值得看
资深开发者将其项目从MIT许可证切换至欧盟公共许可证EUPL 1.2，理由是后者在专利保护、法律可执行性和与欧盟法规兼容性上更优。对依赖开源组件的AI创业团队有选型参考价值。
编辑判断
EUPL 1.2 在国内几乎无人讨论，但它是少数被欧盟法院判例直接认可的开源许可证，专利报复条款比Apache 2.0更严格。用MIT的AI项目最头疼的是被大厂拿去做云服务闭源变现，EUPL的强copyleft特性对这类场景有天然防御性。
如果你在做AI基础设施或模型权重分发，EUPL比GPL更适合——它明确兼容网络和SaaS场景，而GPL的"传播"定义在云服务时代已经模糊。不过NPM生态的惯性极大，这个切换短期内不会引发跟风。
社区反馈
意见分歧 116 条评论
核心争论：开源许可证能否真正约束商业滥用，还是只会被大公司规避或AI时代失去意义
CC BY-NC-ND is what I'm also increasingly using (for non-code), though not always, and disheartenedly. (And as commented, the non-code context is different.)
ND is usually a bit sad, as it makes the thing a dead-end. The magic of the web has always been that things would continuously morph through being reinterpreted and all, and that just doesn't happen with ND. I can of course see the valid reasons why one would pick that license, but it's still.. kind
True enough; philosophically, I am still in the BY camp (a.k.a. BSD/MIT/etc.), and I do not particularly care about the NC part, but ND is increasingly important for non-code. But if they could do even the BY properly, it would be a step to the right direction (and, to some extent, I think