Skip to content
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

Open
hador opened this issue Jun 21, 2024 · 4 comments
Open

Licensing concerns #1008

hador opened this issue Jun 21, 2024 · 4 comments
Assignees

Comments

@hador
Copy link

hador commented Jun 21, 2024

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.

@sandy081
Copy link
Member

@isidorn Can you please answer to this?

@hador
Copy link
Author

hador commented Jun 26, 2024

Hi @isidorn , did you have chance to look into the above?
Thanks!

@isidorn
Copy link
Contributor

isidorn commented Jun 26, 2024

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.

@hador
Copy link
Author

hador commented Jun 27, 2024

Of course, I understand these matters can be tricky.
Thanks for getting back to me!

@joaomoreno joaomoreno self-assigned this Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants