-
Notifications
You must be signed in to change notification settings - Fork 210
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
Licensing concerns #1008
Comments
@isidorn Can you please answer to this? |
Hi @isidorn , did you have chance to look into the above? |
Thanks for the ping, license questions always require me to consult with our legal team which usually means that the response will take at least a couple of weeks, if not months. Thanks for your understanding. |
Of course, I understand these matters can be tricky. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi team,
I noticed that following this PR, this package (
@vscode/vsce
, MIT licensed) now depends on@vscode/vsce-sign
which is under the Microsoft license instead.The current setup makes the licensing for
@vscode/vsce
land in a grey area.Are there any plans to align the two?
Thanks.
The text was updated successfully, but these errors were encountered: