Publishing to OpenVSX

[nichtverstehen]

VSCode installations that are not managed by Microsoft (e.g. very popular Gitpod.io) do not have access to the Microsoft Extension Marketplace. They typically use OpenVSX registry (http://open-vsx.org).

I find vscode-pbkit extension excellent and would love it to be included in the OpenVSX registry.

There are two ways to achieve that:

1. The maintainers (i.e. you folks) include publishing to OpenVSX in their workflow (manual or automatic).
2. Rely on automatic scripts maintained by OpenVSX to push thrid-party extensions on best-effort basis.

The first way (maintainer-owned) is of naturally preferred. Would you be open to including OpenVSX in your workflows?

[nichtverstehen]

Oh, and here is a text from OpenVSX to advocate for this:

Dear extension author, Please publish this extension to the Open VSX marketplace.

Context

Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX.

What is Open VSX? Why does it exist?

Open VSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia-based IDEs, and so on.

You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.

How can you publish to Open VSX?

The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the ovsx publish command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.