Publish to OpenVSX

[ItsDrike]

Arch Linux (Linux based operating system distribution) has decided to switch the marketplace for extensions from the MS Visual Studio Marketplace to OpenVSX in this commit.

Here are some more details about OpenVSX, its goal, and why it was created

For that reason, I can't use your extension anymore, could you publish on OpenVSX too?
(It's typically just a matter of running npx ovsx publish you can also check the full guide for publishing)

[Colengms]

Hi @ItsDrike . Thanks for letting us know. We'll look into this.

[sean-mcmanus]

The OpenVSX is for VS Code "compatible" editors, but our extensions has a license that limits it to run only in VS Code and not other "VS Code compatible" editors. So I think this issue is a Won't Fix unless we decide to change our license terms.

[ItsDrike]

The OpenVSX is for VS Code "compatible" editors, but our extensions has a license that limits it to run only in VS Code and not other "VS Code compatible" editors. So I think this issue is a Won't Fix unless we decide to change our license terms.

Oh, that's a shame since for Arch Linux and all other linux distributions based on it, the "original" VS Code editor is the code repository in pacman, and that is now using OpenVSX, rather than the original MS Marketplace. The reasoning behind it was to support open source more since there are some parts about VS Code editor which aren't fully open and I assume using OpenVSX in the original editor will mean more extensions will publish there too. Therefore giving chances to smaller, usually fully open editors, based on the open-sourced parts of VS Code

But I respect your decision and I get that the license you use doesn't allow this. I'm sure there were a lot of people with arch based systems who also lost access to your extension because of this change so it might be worth considering the license change, but I will understand if you won't do that.

[bobbrow]

We need to follow up with the VS Code team about this.

[sean-mcmanus]

@bobbrow FYI, there's another related thread at EclipseFdn/publish-extensions#86 in regards to Platform.IO which has a dependency on our C/C++ extension.

[ivankravets]

Wooow! 👀 It is something new for the PlatformIO which we didn't know... It looks like we are locked and our customers as well.

If Microsoft prefers to lock others just to VSCode, we will stop using this extension. Indeed, we use only 5% of the functionality (just code completion) and the rest of PlatformIO tools and services are fully independent of VSCode and are our native implementation including debugging.

@robotdad, could you provide more details? We have a related issue platformio/platformio-vscode-ide#1802 and we can't resolve it.

P.S: I still believe it was a "typo" on the Microsoft management level and they will fix it.