That’s a poor understanding of the situation. Nothing in the licensing changed. The SDK has always been the proprietary business to business secrets management product. The client integrates with and can use that SDK to provide the paid service to businesses. The client and the server side management of password has always been and still is FOSS.
This was apparently an accidental change in the build code (not the client code, just the building scripts) that required the inclusion of the SDK to build the client when actually it has never and doesn’t really need any of that code. It prevented building the client without accepting the SDK license. Which it shouldn’t.
This was fixed and some things will be put in place so it doesn’t happen again. Nothing in the licensing scheme changed, at all. This is not a catastrophic enshittification event. A Dev was just being lazy and forgot to check the dependencies on the build chain before their commit.
Thank you for bringing some sanity. I get that people experience capitalist enshittification on a regular basis, but sometimes people make honest mistakes.
That’s a poor understanding of the situation. Nothing in the licensing changed. The SDK has always been the proprietary business to business secrets management product. The client integrates with and can use that SDK to provide the paid service to businesses. The client and the server side management of password has always been and still is FOSS.
This was apparently an accidental change in the build code (not the client code, just the building scripts) that required the inclusion of the SDK to build the client when actually it has never and doesn’t really need any of that code. It prevented building the client without accepting the SDK license. Which it shouldn’t.
This was fixed and some things will be put in place so it doesn’t happen again. Nothing in the licensing scheme changed, at all. This is not a catastrophic enshittification event. A Dev was just being lazy and forgot to check the dependencies on the build chain before their commit.
Thanks for the summary, it adds great clarity to seeing how it could happen
This statement is incorrect. The SDK had specific source files placed exclusively under the SDK license, and the remainder of the repository dual licensed between GPL 3 and the SDK license. So the licensing scheme did change.
See also: https://github.com/bitwarden/sdk-internal/blob/main/LICENSE
Thank you for bringing some sanity. I get that people experience capitalist enshittification on a regular basis, but sometimes people make honest mistakes.
Bullshit. Developers never make mistakes. N.E.V.R.
Okay, I actually laughed at that one! I guess us QA folks can just pack up and go home 😆
If it looks like a developer made a mistake, it was actually the product owner. Or the user. Or cosmic rays. But never the developer.
And, amazingly, someone still downvoted you.
Idiots downvoting amazes you? Then there’s a whole world of amazement awaiting you!