Provide stardog vsc extensions via Eclipse Open VSX

[acka47]

I want to use the some stardog extensions in codium, a telemetry free build of vscode. At the moment it is not possible the documented way, e.g. doing ext install stardog-union.vscode-stardog-languages like it says at https://marketplace.visualstudio.com/items?itemName=stardog-union.vscode-stardog-languages.

The best way to allow usage in codium and many other vscode-based editors would be to publish extensions via Open VSX in addition to the VS Code Marketplace. The publishing process is documented in the here.

It would be really nice if you could enable the use of your helpful extensions for users of vscode-compatible editors.

[vemonet]

Indeed that would be really nice to be able to install this extension easily from the extensions catalog of browser-based VisualStudio Code (e.g. code-server https://github.com/cdr/code-server)

@acka47 you can still install this extension by downloading the .vsix file and installing it from this file

I published a mirror on OpenVSX to be able to automate the download of the .vsix file and install it to code-server:

wget https://open-vsx.org/api/vemonet/stardog-rdf-grammars/0.1.2/file/vemonet.stardog-rdf-grammars-0.1.2.vsix
code-server --install-extension vemonet.stardog-rdf-grammars-0.1.2.vsix

It was quick and easy by the way! Let me know if you need help with doing it

[acka47]

you can still install this extension by downloading the .vsix file and installing it from this file

Thanks @vemonet , that's what I've also been doing so far.

[akosyakov]

Hi, Gitpod committer is here 👋

@jmrog Unfortunately MS prohibits usages of MS marketplace by any other products or redistribution vsix files from it. Because of it we kindly ask you to take the ownership of your namespace in OpenVSX and publish there as well.

OpenVSX is a vendor neutral alternative to MS marketplace used by all other derivatives of VS Code like Gitpod, OpenVSCode, VSCodium, Theia based IDEs, and so on.

The docs for publishing the extension are here: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions. Technically this should be straightforward. You get a token and call ovsx publish with it. For example, this is how RedHat publishes their java extension: redhat-developer/vscode-java@ff51dbf/Jenkinsfile#L73-L82

Let me know if you are opened to a PR contributing a release GH action both to MS marketplace and OpenVSX, similar to PDConSec/vsc-print#121.

BTW at Gitpod we support open source developers by providing unlimited access to platform. Feel free to reach out via https://www.gitpod.io/docs/professional-open-source

[akosyakov]

@vemonet I am not sure which marketplace code-server is using. At Gitpod we rely on OpenVSCode server which is basically a server from MS but connected to OpenVSX.

You can learn more about it here:

• VS Code in the browser for everyone
• From Theia to OpenVSCode Server - A history of Cloud IDEs
• Thanks Microsoft for open-sourcing VS Code Server 👐

[vemonet]

@akosyakov not sure too, I think I saw somewhere code-server were now using OpenVSX exclusively for extensions, but it seems like it's not exactly straightforward

I have seen the open sourcing of VSCode! Nice move, and it looks really good, I already have a setup which install and config code-server in a JupyterLab image (our users are researchers so they love having also JupyterLab or RStudio alongside code-server), but I am planning to give it a try when I have enough time and incentive

I just checked with the GitPod VSCode image and the extension is properly there! (you have more than 1k extensions, nice)

So the issue is on the side of code-server who are not properly indexing OpenVSX extension!