Bitwarden SDK relicensed from proprietary to GPLv3
1–10 of 381 posts
Re: Bitwarden SDK relicensed from proprietary to GPLv3
#2Re: Bitwarden SDK relicensed from proprietary to GPLv3
#3Well that’s one way to handle that effectively and in what seems to be open source way without fuckery; glad to hear it cause that was going to be a bit annoying migrating away from them.
Re: Bitwarden SDK relicensed from proprietary to GPLv3
#4Props for them to step in the right direction, it wasn’t obvious at all for a few days what they would do.
Re: Bitwarden SDK relicensed from proprietary to GPLv3
#5GPLv3 is interesting because it means to use their code in a commercial setting, then you must also have the guts to open source too.
Re: Bitwarden SDK relicensed from proprietary to GPLv3
#6https://github.com/bitwarden/clients/issues/11611#issuecomme...
> We have made some adjustments to how the SDK code is organized and packaged to allow you to build and run the app with only GPL/OSI licenses included. The sdk-internal package references in the clients now come from a new sdk-internal repository, which follows the licensing model we have historically used for all of our clients (see LICENSE_FAQ.md for more info). The sdk-internal reference only uses GPL licenses at this time. If the reference were to include Bitwarden License code in the future, we will provide a way to produce multiple build variants of the client, similar to what we do with web vault client builds.
Re: Bitwarden SDK relicensed from proprietary to GPLv3
#7GPLv3 is interesting because it means to use their code in a commercial setting, then you must also have the guts to open source too.
I don’t believe that is entirely accurate. I believe it depends on the application and what you’re doing with it whether or not you would be required to open source it. Like, if you’re distributing the application as a product, not necessarily saas application?
Re: Bitwarden SDK relicensed from proprietary to GPLv3
#8Bitwarden is still excellent, but keep an eye on them over the next few years. Remember that Bitwarden was originally a LastPass alternative without the fuckery.
Re: Bitwarden SDK relicensed from proprietary to GPLv3
#9GPLv3 is interesting because it means to use their code in a commercial setting, then you must also have the guts to open source too.
I don’t believe that is entirely accurate. I believe it depends on the application and what you’re doing with it whether or not you would be required to open source it. Like, if you’re distributing the application as a product, not necessarily saas application?
Yes, this is why AGPL is superior.
Re: Bitwarden SDK relicensed from proprietary to GPLv3
#10Luckily if they die another will rise up. At this point I’m thinking I’ll just use the Apple Keychain if Bitwarden gets up to no good again.