Replies: 51 comments 25 replies
-
I, Mathijs van Veluw hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by BlackDex are copyright of Mathijs van Veluw. |
Beta Was this translation helpful? Give feedback.
-
I, Joel Beckmeyer hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by TinfoilSubmarine are copyright of Joel Beckmeyer. |
Beta Was this translation helpful? Give feedback.
-
I, Ave Özkal hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by aveao are copyright of Ave Özkal. |
Beta Was this translation helpful? Give feedback.
-
I, Ian hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by ViViDboarder are copyright of Ian. |
Beta Was this translation helpful? Give feedback.
-
I, Martijn Hanegraaf hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by TheMardy are copyright of Martijn Hanegraaf. |
Beta Was this translation helpful? Give feedback.
-
I, Michael Powers hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by swedishborgie are copyright of Michael Powers. |
Beta Was this translation helpful? Give feedback.
-
I, Armaan Tobaccowalla hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by ArmaanT are copyright of Armaan Tobaccowalla. |
Beta Was this translation helpful? Give feedback.
-
I, Miro Prasil hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by mprasil are copyright of Miro Prasil. |
Beta Was this translation helpful? Give feedback.
-
I, Shane Faulkner hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by shauder are copyright of Shane Faulkner. |
Beta Was this translation helpful? Give feedback.
-
I, Rob Watson, hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @rfwatson are copyright of Rob Watson. |
Beta Was this translation helpful? Give feedback.
-
I, Daniel García hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @dani-garcia are copyright of Daniel García. |
Beta Was this translation helpful? Give feedback.
-
I, Janos Tassy hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @janost are copyright of Janos Tassy. |
Beta Was this translation helpful? Give feedback.
-
While I don't object to changing the license, I think a few things mentioned in the intro are not quite true and should be clarified.
If you make your Vaultwarden instance publicly accessible, then there is a reasonable expectation that anyone could interact with it (if only to load the login page), so if you've modified any of the Vaultwarden backend (e.g., custom templates or graphics that get built into the binary), I believe you would technically be obligated to "prominently offer" the source. In practice, that would probably mean modifying the web vault login page with a link to your source.
As mentioned above, this also affects non-commercial users who have modified the Vaultwarden code.
While this may prevent deep integration of Vaultwarden with a company's other products, they are still perfectly able to provide standalone instances, even with some customizations (as long as they make the modified source available), so I don't think this change would have much effect on most MSPs who offer managed Vaultwarden services. Overall, AGPL has a limited ability to prevent third-party competition with the original product, as can be seen with Bitwarden's shift towards a non-open-source ("source-available") license for key portions of their software. |
Beta Was this translation helpful? Give feedback.
-
I, Jeremy Lin, hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @jjlin are copyright of Jeremy Lin. |
Beta Was this translation helpful? Give feedback.
-
I, Adam Jones hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by domdomegg are copyright of Adam Jones. And I hereby grant the Vaultwarden project team to re-license Vaultwarden, including all past, present and future contributions of the author listed above. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
I, Samuel Tardieu hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @samueltardieu are copyright of Samuel Tardieu. |
Beta Was this translation helpful? Give feedback.
-
I, Helmut K. C. Tessarek hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @tessus are copyright of Helmut K. C. Tessarek. |
Beta Was this translation helpful? Give feedback.
-
I, Pat Sier hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @pjsier are copyright of Pat Sier. |
Beta Was this translation helpful? Give feedback.
-
I, Maximilian Fijak hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @MFijak are copyright of Maximilian Fijak. |
Beta Was this translation helpful? Give feedback.
-
I, @tomuta hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @tomuta are copyright of @tomuta. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
I, Daniele Andrei hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by Kurnihil are copyright of Daniele Andrei. |
Beta Was this translation helpful? Give feedback.
-
I, Matthias G. hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @sirux88 are copyright of Matthias G. |
Beta Was this translation helpful? Give feedback.
-
I, Jan Jansen hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @farodin91 are copyright of Jan Jansen. |
Beta Was this translation helpful? Give feedback.
-
I, Paul Römer hereby grant permission to re-license Vaultwarden under the GNU Affero General Public License. A portion of the commits made by @soruh are copyright of Paul Römer. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
I want to thank everybody who signed the consent to make it possible to convert Vaultwarden from GPLv3 to AGPLv3 🥳 Thanks! |
Beta Was this translation helpful? Give feedback.
-
To save the current state I have created a PDF of this topic and attached it to this post. Re-License of Vaultwarden to AGPLv3 - Discussion #2450 - dani-garcia_vaultwarden - 2023-02-13.pdf |
Beta Was this translation helpful? Give feedback.
-
Hello contributors to Vaultwarden,
I'm starting this discussion because we want to change the open source license of Vaultwarden.
Currently it is licensed under GPLv3 which is nice, but this has a gap which could allow commercial usage of Vaultwarden without providing back to the community.
For this reason Bitwarden has it's server licensed under the AGPLv3. That same license we want to use for Vaultwarden to keep Vaultwarden fully open source.
To be clear, this will not effect any (end)user or any self-hosted environment which you share with your family and friends.
This will only have an effect on companies or self-hosted environments that build proprietary tools using Vaultwarden code or modify the Vaultwarden code.
This is also more fair towards Bitwarden, since currently the GPLv3 license of Vaultwarden could allow other companies to compete with Bitwarden by modifying the Vaultwarden code and not providing these changes back to the community, which is not something we want.
What we need to do
We need a consent from all major contributors who made Vaultwarden towards what it is now. This only includes actual changes to the Rust code and does not include spelling changes, formatting, clippy fixes etc...
For this we have compiled a list of all these users from whom we would like to have a consent to continue to fully change the Vaultwarden code to AGPLv3.
The only thing you need to do is comment below using the following template, and change the parts in between
{{ }}
:If for some reason you do not want your real name to be visible, please use the same as is visible on Github, or just your Github username instead.
What is GPL?
GPL (Gnu Public License) was originally written by Richard Stallman, the founder of the Free Software Foundation for the GNU project. All licenses in the GPL series are copyleft licenses which means that the derivative works should be released under the same license or an equivalent license.
The difference between GPL and AGPL
GPL says that if the software is redistributed, you have to release the source code of the modification. But the GPL license doesn't mention anything about modifying the software and providing it as a service. This is due to the fact that letting users interact with software over a network cannot be considered as redistribution. Redistribution is thus the triggering event of GPL. This is often referred to as the SaaS loophole of GPL.
AGPL added one more requirement to GPL, which is:
This just means that the software cannot be sold as a proprietary product with modification without providing the source of the modifications to the users of the product.
AGPL Is also recommended by the Free Software Foundation (FSF) if the software is commonly run over a network, which is what Vaultwarden is.
Tagging contributors
This list is just in alphabetic order. I hope i haven't missed anyone, if I did, please let us know, but it would be even better if you would sign it right away 😄 .
✔️ @aksdb
✔️ @ArmaanT
✔️ @aveao
✔️ @Baelyk
✔️ @BlackDex
✔️ @dani-garcia
✔️ @domdomegg
✔️ @dongcarl
✔️ @endyman
✔️ @farodin91
✔️ @janost
✔️ @jjlin
✔️ @Kurnihil
✔️ @MFijak
✔️ @mprasil
✔️ @njfox
✔️ @olivierIllogika
✔️ @paolobarbolini
✔️ @pjsier
✔️ @RealOrangeOne
✔️ @rfwatson
✔️ @samueltardieu
✔️ @shauder
✔️ @sirux88
✔️ @soruh
✔️ @Skeen
✔️ @stefan0xC
✔️ @Step7750
✔️ @swedishborgie
✔️ @tessus
✔️ @thelittlefireman
✔️ @TheMardy
✔️ @TinfoilSubmarine
✔️ @tomuta
✔️ @tycho
✔️ @ViViDboarder
✔️ @vplme
Thanks
And, thanks for all your support to the Vaultwarden Project!
Beta Was this translation helpful? Give feedback.
All reactions