Any time someone uses the word "sustainable" in regards to a FOSS project, I know they're buttering up the community as they plan to make the project not FOSS anymore. In this particular case, it's not as bad as that, as Open WebUI is merely introducing a more onerous version of the BSD advertising clause. BSD 4-clause was considered a FOSS license but, in practice, demanding specific forms of attribution was incredi…
Open WebUI changed license from BSD-3 to Open WebUI license with CLA
51–60 of 60 posts
Re: Open WebUI changed license from BSD-3 to Open WebUI license with CLA
#52Any time someone uses the word "sustainable" in regards to a FOSS project, I know they're buttering up the community as they plan to make the project not FOSS anymore. In this particular case, it's not as bad as that, as Open WebUI is merely introducing a more onerous version of the BSD advertising clause. BSD 4-clause was considered a FOSS license but, in practice, demanding specific forms of attribution was incredi…
I think CLA signing is fine if the projects is owned by a reputable organization (Apache, FSF, whatever). If the project is controlled by a commercial entity, you just have to understand it will likely change in a way you disagree with.
Re: Open WebUI changed license from BSD-3 to Open WebUI license with CLA
#53What really is the moat of openwebui? I have seen at least 4 - 5 react UIs with similar functionality (chat, RAG, document library).
Not sure about the moat, it's mostly a SvelteKit web app with extra utils after all. But it has a rather unique combination of advanced features (RAG integrations, workspaces[1], pipelines[2], code execution[3], MCP integration[4], etc.) and a user-friendly "production grade" interface. I've built a dependency for OWUI using many of these advanced features, and now I'm trying to figure out where to migrate with no ob…
Re: Open WebUI changed license from BSD-3 to Open WebUI license with CLA
#54Earlier quoted context omitted.
Its deliberate, use a permissive/pushover license to get adoption, then rugpull once you have the userbase who are relying on you, then bathe your VCs in cash.
You can't make such a claim without any backing. While undoubtedly it's the case for some, I strongly doubt everyone does it on purpose. It's just that orgs mature with time and realise their original naiveté. Do you have any proof of that? Hell, are OpenWebUI even receiving VC funding?
Re: Open WebUI changed license from BSD-3 to Open WebUI license with CLA
#55Earlier quoted context omitted.
I think CLA signing is fine if the projects is owned by a reputable organization (Apache, FSF, whatever). If the project is controlled by a commercial entity, you just have to understand it will likely change in a way you disagree with.
A CLA is all about changing the terms of the deal after the deal. It's hard to imagine a scenario in which that can be legitimate.
E.g. the original GPL or Apache licenses did not consider patents, DRM or Tivoization, but the modern versions do.
I think it's legitimate for a project to say "we think we should address these issues but we didn't think of them" and update their license.
I'm not saying this is always the case, but it's the reason I think it's ok to sign a CLA for an organization you trust: it's _likely_ you'd also trust their choice to change a license.
Re: Open WebUI changed license from BSD-3 to Open WebUI license with CLA
#56Why does this keep happening? Do people not understand the implications choosing an open source license.in the first place? There are a million licenses, in fact you can just make your own one up! But when you choose a class of license the specifically allows commercial exploitation... you don't get to act wronged when it happens.
Two key reasons, they don't understand the implications, and many developers are cheapskates nowadays, they wouldn't have survived in old days until 2000's, where we paid for everything, or pirated it. Somehow it feels great to be paid, to pay others for the tools, like in every other profession, not so much.
Re: Open WebUI changed license from BSD-3 to Open WebUI license with CLA
#57Earlier quoted context omitted.
Two key reasons, they don't understand the implications, and many developers are cheapskates nowadays, they wouldn't have survived in old days until 2000's, where we paid for everything, or pirated it. Somehow it feels great to be paid, to pay others for the tools, like in every other profession, not so much.
There was a lot of tools available for free in the the 90's. Both the BSDs and Linux existed.
Re: Open WebUI changed license from BSD-3 to Open WebUI license with CLA
#58Earlier quoted context omitted.
Not sure about the moat, it's mostly a SvelteKit web app with extra utils after all. But it has a rather unique combination of advanced features (RAG integrations, workspaces[1], pipelines[2], code execution[3], MCP integration[4], etc.) and a user-friendly "production grade" interface. I've built a dependency for OWUI using many of these advanced features, and now I'm trying to figure out where to migrate with no ob…
It's RAG never worked for me tbh. I thought it was simply because I didn't have Gpu.
Re: Open WebUI changed license from BSD-3 to Open WebUI license with CLA
#59Earlier quoted context omitted.
I note that the GPL does not require publishing the source code, only distributing it to users of the binary code.
You're right, but it's equivalent to publishing because all users can have the source code AND can then distribute it freely once at least one user has it.
Your users don't know what source code is.
Your users don't bother to look at what they downloaded to find the code therein.
Your users aren't developers and they don't know any devs, so having the source isn't useful to them, so even if they see the code they won't redistribute.
Your users find the code a competitive advantage and don't want to spread that around. Its also too expensive for most organisations to obtain the code too.
You deliver binary and source, but then disincentivise redistribution by cutting off access to something else, like updates. This is what grsecurity and RedHat do. There was one leak of grsec, but that quickly became obsolete.