New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[License] 涉及 LagrangeGo 的项目许可证问题 #773

Closed

2 tasks done

JustAnotherID opened this issue May 6, 2024 · 4 comments

Closed

2 tasks done

[License] 涉及 LagrangeGo 的项目许可证问题 #773

JustAnotherID opened this issue May 6, 2024 · 4 comments

Labels

Contributor

JustAnotherID commented May 6, 2024 •

edited

Loading

在提问之前...

我填写了简短且清晰明确的标题，以便开发者在翻阅 issue 列表时能快速确定大致问题。而不是“一个建议”、“卡住了”等
我基本确定这是一个新功能/建议，而不是遇到了 bug（不确定的话请附上日志）

说说你遇到的问题？

新引入的 LagrangeGo 使用 AGPLv3 协议开源，具有传染性。作为开源社区的一部分，我们应当尊重相关协议的限制。

有什么好的想法？

两个可能选择：

不更改当前协议，移除或隔离主线代码中的 LagrangeGo 的引用。
直接切换到 AGPLv3。

个人倾向于选择 2，更换协议对我们来说并没有什么实质影响。

@fy0 @Szzrain @Xiangze-Li @oissevalt @FlameTEXT @Fripine @PaienNate @yichere

其他内容

No response

JustAnotherID added the enhancement label

JustAnotherID mentioned this issue

chore(license): 切换为 agplv3 #774

Closed

Contributor Author

JustAnotherID commented May 6, 2024

根据 #774 中的意见，方案为先移除对 LagrangeGo 的直接引用（悲

Member

Xiangze-Li commented May 6, 2024

尊重 BDFL 的意见，同时希望 BDFL 意识到自己做出的决定对整个开发组的影响。

Contributor Author

JustAnotherID commented May 6, 2024 •

edited

Loading

不舍得 Szzrain 佬当前的贡献变成无用功，进行了分叉保留：
https://github.com/sealdice/libre-sealdice-core
https://github.com/sealdice/libre-sealdice-ui

JustAnotherID pinned this issue

Szzrain mentioned this issue

Revert: remove lagrange go #779

Merged

Contributor

Szzrain commented May 7, 2024

Szzrain closed this as completed

JustAnotherID unpinned this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment