-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Redistribution Permissions for Windows Terminal Binaries #15740
Comments
Hey, thanks for asking! As a passing curiosity (and you're free not to answer!): what's your goal? For example...
|
I find Windows Terminal to be an excellent piece of software that provides all required functionality straight out of the box. As for motivation we try to maintain a streamlined conda development environment for ease of use and consistency across machines and different types of infrastructure. Since our work often involves extensive terminal operations, having Windows Terminal integrated would be highly convenient and beneficial for us. |
Is there a reason why Windows Terminal couldn't be installed from the app store on the target machine when conda is installed / first used? Otherwise, this might result in user confusion when they use Windows Terminal bundled with conda and it has settings that don't exist in another (regular) Windows Terminal installation on the machine. |
To add, redistributing Windows Terminal is completely fine from a license standpoint. |
in some Windows Server instances (and also other contexts) there is no Microsoft App Store to download the terminal from. |
Yea, this basically just seems like the same thing as shipping it on |
@lhecker, to clarify, redistributing the binary is allowed? |
Yep 👍 |
Hello,
I'm considering redistributing Windows Terminal binaries as part of conda-forge. Can you clarify if this is permissible under your license and if any conditions apply?
Thanks
The text was updated successfully, but these errors were encountered: