🔨 LobeChat 1.0 - Update LICENSE to Apache 2.0 #1812
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
👍 @arvinxx Thank you for raising your pull request and contributing to our Community |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1812 +/- ##
=======================================
Coverage 92.69% 92.69%
=======================================
Files 256 256
Lines 14558 14558
Branches 1681 1681
=======================================
Hits 13495 13495
Misses 1063 1063 ☔ View full report in Codecov by Sentry. |
|
if users modified the code a little bit with lobechat 0.x would that is still allowed? |
Yes. |
|
https://opensource.guide/zh-hans/legal/ 我发现国内的这些厂商都喜欢自己发明一些新的 license, 说除了 1234 之外, 我们的软件就是 apache license 的.
|
https://opensource.guide/zh-hans/legal/ I found that these domestic manufacturers like to invent some new licenses themselves, saying that except for 1234, our software is under the apache license.
|
我们不是大厂，也不是小厂，就两三个人搭伙兼职搞的这个产品，你的地图炮命中失败了 🤡
就算侵权了我们大概率也计较不了，说实话开源协议也只是君子协议。而且改 Apache 的目的我之前在公告里也提过了。
为何你会如此非黑即白地觉得我们接下去就是做的纯商业软件？我们提供的免费使用场景已经够宽泛了吧？ 
按你这么苛刻的要求， Supabase 这样的开源项目也需要商业化，也是用的 Apache 2.0，为啥你不推荐他们用你所谓的 BUSL？ 开源社区如果都按你说的这么搞，世界能变好吗？ |
We are neither a big factory nor a small factory. We are just two or three people working part-time to produce this product. Your map cannon failed to hit the target 🤡
Even if there is infringement, we most likely won't care. To be honest, the open source agreement is just a gentleman's agreement. Moreover, I have mentioned the purpose of changing Apache in the announcement before.
Why do you think so black and white that the next thing we do is purely commercial software? Are the free usage scenarios we provide broad enough?
According to your demanding requirements, open source projects like Supabase also need to be commercialized, and they also use Apache 2.0. Why don't you recommend them to use what you call BUSL? If the open source community does what you say, will the world be a better place? |
|
对不起可能我语气不好了，我想表达的建议是：
对于我使用者或者开发者（可能我自大了）其实一个稳定的协议会给人带来很多安全感，在使用时不用担心协议突然有一天换成了 BUSL ，今天加了一个附加条款，我其实不敢确定哪天这个附加条款会不会增加。 有些厂商在这两个线之间跳，一方面声称自己开源，可以自由 fork ，一方面又禁止商业使用，我很感激 lobe chat 给大家带来的这些便利，但是不希望 lobe 也变成这样的两头吃的项目。 |
Sorry, maybe my tone is not good, but the suggestion I want to express is:
For me as a user or developer (maybe I am arrogant), a stable protocol will bring a lot of security to people. When using it, I don’t have to worry about the protocol suddenly being changed to BUSL one day. Today I added an additional clause. In fact, I am not sure whether this additional clause will be increased one day. Some manufacturers jump between these two lines. On the one hand, they claim that they are open source and can be freely forked, but on the other hand, they prohibit commercial use. I am very grateful for the convenience that lobe chat brings to everyone, but I don’t want lobe to become like this. Items that both ends can eat. |
|
@LeoQuote 我知道你应该也是爱之深责之切，可以理解。 我详细解释下这次协议变更背后的原因吧。 首先我们的初心没有变，始终希望是将LobeChat做成开源的，所以后续我们会在Cloud版上线的核心功能也仍然会保持开源(比如服务端数据库、文件上传等）。 做这次协议变更的原因主要有两点，第一个是的确之前有企业找我们咨询时问过协议的问题，他们希望有明确的专利授权，而这个是改成 apache2.0 的主要原因。 第二个附加条款的原因是就在过去几个月里我们确实看到了一些挂着我们logo招摇撞骗的项目。比如 https://lobehub.top 。无论从用户角度来说，还是后续做商业化来说这都是对我们品牌的损害，这个是我们绝对不能容忍的，这是最后那条商业化限制条款的由来。如果不是这个例子，我们大概率也就不限制了。但现实世界远没有开源社区这么单纯。所以至少我们要在协议层面有所限制，未来真要维权也有由头。 如果直接采用原版 apache 协议，像现在号商的做法就是侵权的(因为没有品牌授权)，但在我们看来这是 LobeChat 合理的用法。我们当时还聊过号商会不会抢我们自己cloud版的生意，但是最后评估下来其实现在的市场完全够大，远远没到存量竞争的阶段，我们期望与社区卖 api 的服务商一同推进 ai 的普及，仅仅凭借我们以一己之力肯定是做不到的。所以我们还补充了一条，允许号商这种用 lobechat 做前端的商业化方式。 当然我们的商业化尝试也才刚刚开始，如果未来发展尽如人意，可能我们也会再放宽一些条款吧。总之未来只可能会松，不太可能会再变严了。 |
@LeoQuote I know that you should also feel deep love and responsibility, which is understandable. Let me explain in detail the reasons behind this protocol change. First of all, our original intention has not changed. We always hope to make LobeChat open source, so the core functions we will launch in the Cloud version will still remain open source (such as server-side database, file upload, etc.). There are two main reasons for this protocol change. The first is that some companies have asked us about the protocol before. They hope to have clear patent authorization, and this is the main reason for changing to apache2.0. The reason for the second proviso is that just in the past few months we have definitely seen some projects showing off with our logo on them. For example https://lobehub.top. No matter from the user's point of view, or from the perspective of subsequent commercialization, this is damage to our brand. This is something we absolutely cannot tolerate. This is the origin of the last commercialization restriction clause. If it weren't for this example, we would probably not have restrictions. But the real world is far from as simple as the open source community. So at least we must have some restrictions at the agreement level, and there will be reasons to protect rights in the future. If you directly use the original apache protocol, like the current account provider's approach, it will be infringement (because there is no brand authorization), but in our opinion this is a reasonable usage of LobeChat. We also talked about whether account providers would steal our own cloud version business, but in the final assessment, the current market is actually big enough, and it is far from the stage of stock competition. We hope to promote AI together with service providers who sell APIs in the community. The popularization of education cannot be achieved by ourselves alone. Therefore, we also added that the commercialization method of using lobechat as the front-end for account providers is also allowed. Of course, our commercialization attempts have just begun. If the future development goes as expected, we may also relax some terms. In short, it will only be loosened in the future, and it is unlikely that it will become stricter again. |
💻 变更类型 | Change Type
🔀 变更说明 | Description of Change
https://lobehub.com/blog/lobe-chat-v1-license-update
📝 补充信息 | Additional Information