Open VSX Registry: Awareness and Important Steps

[brianking]

@gattytto has published this extension in the Open VSX Registry.

The service was recently transferred to the Eclipse Foundation and we want to ensure a seamless transition for our users. To ensure uninterrupted service and more exposure for your extension, I recommend the following.

To the maintainers: If you would like to take over publishing to open-vsx.org, here’s how: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

To the current publisher: Please sign the Eclipse Publisher Agreement. The signing process is explained in the Wiki (steps 1 and 2).

Claiming ownership of the namespace for your extension(s). To find out how to do this, see: https://github.com/eclipse/openvsx/wiki/Namespace-Access As owner you can add more namespace members (including service accounts) yourself in https://open-vsx.org/user-settings/namespaces. Note that publishing can be done by any contributor to the extension, namely those you add as namespace members once they have signed the Publisher Agreement as well.

Please also note that a license is now mandatory for publishing your extension to Open VSX. If your project doesn't have any license, please add one, preferably an open source license such as MIT. The publishing tool ovsx offers to automatically add the MIT license when you try to publish without a license.

Useful links: Eclipse Publisher Agreement Eclipse Foundation Open VSX Registry Frequently Asked Questions (FAQ)

More details are in these recent blog posts: https://blogs.eclipse.org/post/brian-king/open-vsx-registry-under-new-management https://blogs.eclipse.org/post/brian-king/new-era-open-vsx-registry

Today, there’s growing momentum around open source tools and technologies that support Visual Studio (VS) Code extensions. Leading global organizations are adopting these tools and technologies. This momentum has spurred demand for a marketplace without restrictions and limitations. We hope you join us on this journey as we continue to build the Open VSX community. We look forward to continued innovation from you in 2021!

[brianking]

@phoityne @gattytto Just a reminder for you in case you missed this. Our deadline was extended but the new one is today, Friday January 29.

[phoityne]

Hi.

Sorry for late reply. I didn't take that I would need to do something to VSX. What is the deadline for ? (for user registration on VSX Registry ?)

Regards.

[brianking]

@phoityne The date has passed and the extension is no longer active.

If you would like to have your extension(s) listed on open-vsx.org, I recommend publishing them fresh via the following steps.

1. Claim the extension namespace https://github.com/eclipse/openvsx/wiki/Namespace-Access
2. Publish the latest version https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

[gattytto]

Hi.

Sorry for late reply. I didn't take that I would need to do something to VSX. What is the deadline for ? (for user registration on VSX Registry ?)

Regards.

hello, Phoityne. The open-vsx registry allows us to add your extension to a web ide called Eclipse Che which allows the use of different editors, one of them called theia (which is the one compatible with .visx extensions).

Since we can't get the .vsix from MS marketplace I once published a fork of your debug extenison to open-vsx but it got removed.

I will try to re-publish it the same way I did last time

[phoityne]

@gattytto Thanks for your information and contribution.

If there is something I should do, please let me know.

Regards.