Open VSX

[noraj]

Hi can you push your extension to https://open-vsx.org/ in addition to VSCode Market Place so people using the FLOSS version could install it too?

I wrote an article on the subject.

[akosyakov]

@sianglim We are running Web version of Code in Gitpod: www.gitpod.io.

This version is not allowed to use MS VS Code extensions Marketplace, since it is not MS product. So we connect to Open VSX instead: https://open-vsx.org/ It is a vendor neutral alternative.

Our users want to install this extension but fail since it is not published to Open VSX: https://community.gitpod.io/t/cannot-activate-the-rails-extension-error/3562

Please publish it as well there 🙏 Docs are here: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions Technically it should be straightforward. You are basically have to get a token and call ovsx publish with it, for instance how RedHat is publishing the java extension: https://github.com/redhat-developer/vscode-java/blob/ff51dbffc30dd23190335c929e9f34ccdf511554/Jenkinsfile#L73-L82

[sianglim]

Hi Anton,

will have a look when I have a moment.

Cheers, Siang

[matschaffer]

Thanks so much @sianglim !

[sianglim]

Hi @akosyakov and @matschaffer, hopefully I've done it right. It's published now on the Open VSX registry at https://open-vsx.org/extension/sianglim-slim/slim

Also, apologies to @noraj for missing your comment.

[noraj]

Also, apologies to @noraj for missing your comment.

No worry.

https://github.com/eclipse/openvsx/wiki/Namespace-Access

[matschaffer]

Thanks @sianglim !

I'm still seeing the error when I launch gitpod from https://github.com/Safecast/safecastapi/pull/810

But maybe @akosyakov should confirm if that's the right way to check. Not sure if the gitpod prebuild might do any sort of caching of the available extensions or what.

[akosyakov]

It is published like sianglim-slim.slim not like sianglim.slim 😬

[noraj]

It is published like sianglim-slim.slim not like sianglim.slim grimacing

The best would be to publish it under the same namespace to avoid those dependency issues.

[sianglim]

Sorry. I think the sianglim namespace was taken. Is there a way to get contributor access to that namespace to publish the extension there?

[akosyakov]

@sianglim I think you should follow https://github.com/eclipse/openvsx/wiki/Namespace-Access#how-to-claim-a-namespace and create an issue here https://github.com/EclipseFdn/open-vsx.org/issues/new?assignees=&labels=namespace&template=claim-namespace-ownership.md&title=Claiming+namespace+%5Bname%5D

[matschaffer]

Looks like it got granted! https://github.com/EclipseFdn/open-vsx.org/issues/516

@sianglim can you republish?

[sianglim]

Hi @matschaffer, I just did so hopefully you're able to use it properly now. 😄

[taylorthurlow]

Can confirm things are working as expected now! I think it's safe for this to be closed.

[matschaffer]

Confirmed here too! This is great @sianglim, thanks so much!