Request: Publish extension on https://open-vsx.org/

[leopoldfajtak]

For users of the FLOSS vscodium, VSLilyPond is not yet available, because vscodium does not (by default) use Microsoft's repository. This can be changed by the user, but it would be easier in the long term if VSLilyPond were hosted on https://open-vsx.org/

The publishing process is documented in the Open VSX Wiki.

[KaiVinter]

This can also be useful in order to use VSLilyPond with VH Editor in Android ✨

[lbssousa]

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.