Repository navigation
Publish to OpenVSX #6388
Description
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)
Activity
Colengms commentedon Oct 27, 2020
Hi ItsDrike (@ItsDrike) . Thanks for letting us know. We'll look into this.
sean-mcmanus commentedon Oct 29, 2020
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 commentedon Oct 30, 2020
Oh, that's a shame since for Arch Linux and all other linux distributions based on it, the "original" VS Code editor is the
coderepository 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 CodeBut 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 commentedon Oct 30, 2020
We need to follow up with the VS Code team about this.
sean-mcmanus commentedon Oct 30, 2020
Bob Brown (@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 commentedon Nov 1, 2020
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.
Marc Goodner (@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.
CrossR commentedon Nov 1, 2020
It may be possible to do something like the MS C# plugin.
tl;dr someone forked the repo and released an extension without the proprietary parts https://github.com/muhammadsammy/free-omnisharp-vscode, such that it could be published on OpenVSX.
Of course, for that to happen the license here would need to be clarified as to what is MIT licensed and what is not, to ensure any forked ext fits with the license.
I believe generally as more "VSCode compatible" editors come out, there will need to be a clearer response from MS about limits and usage, as there is open issues about this for VSCodium and more, as well as LSP consumers who want to use the C++/C#/Python extensions etc in non code editors like Vim, Emacs, Sublime etc.
(I say this from a very biased position of someone who works on a VSCode compatible editor and gets regular questions about those plugins and the Docker/WSL/SSH ones, as it is unclear inside the editor where the OSS stuff ends and closed source proprietary stuff begins).
robotdad commentedon Nov 2, 2020
I'm unfamiliar with the issues here around the license. I'll do some research and report back.
11 remaining items
github-actions commentedon Feb 24, 2021
This feature request has received enough votes to be added to our backlog.
caio-vinicius commentedon Oct 18, 2021
Up for this.
mfouesneau commentedon Nov 23, 2021
May I ping on what's the status of this issue?
sean-mcmanus commentedon Nov 23, 2021
Bob Brown (@bobbrow) ?
bobbrow commentedon Nov 23, 2021
I didn't realize this issue was still open. Nothing has changed from a licensing perspective.