-
-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Remove Open Source from Strongbox #2654
Conversation
✅ Your preview is ready!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In March 2023 you broke the repo so that only you could compile it. Your attitude confirms this was on purpose. Being a transparent company, where exactly did you announce this critical change?
The discussion at strongbox-password-safe/Strongbox#784 (comment) is informative, and unfortunate. 😢
Signed-off-by: Jonah Aragon <[email protected]> Signed-off-by: Daniel Gray <[email protected]>
This pull request has been mentioned on Privacy Guides. There might be relevant details there: |
This pull request has been mentioned on Privacy Guides. There might be relevant details there: |
This pull request has been mentioned on Privacy Guides. There might be relevant details there: https://discuss.privacyguides.net/t/remove-strongbox/19613/1 |
This pull request has been mentioned on Privacy Guides Community. There might be relevant details there: |
Changes proposed in this PR:
closes #2649
Contribution terms (click to expand)
1) I am the sole author of this work. 2) I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project. 3) I have disclosed any relevant conflicts of interest in my post. 4) I agree to the Community Code of Conduct.