Officially publish the extension on the Open VSX Registry

[kmk3]

Background

Currently, this extension is published both on the Open VSX Registry and on the
Visual Studio Marketplace:

• https://open-vsx.org/extension/EditorConfig/EditorConfig
• https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig

However, only the latter is official.

From https://open-vsx.org/extension/EditorConfig/EditorConfig:

This version of the “EditorConfig for VS Code” extension was published by
open-vsx. That user account is not a verified publisher of the namespace
“EditorConfig” of this extension. See the documentation to learn how we
handle namespaces and what you can do to eliminate this warning.

Why

From https://github.com/eclipse/openvsx:

Open VSX is a vendor-neutral open-source alternative to the Visual Studio Marketplace.
It provides a server application that manages VS Code extensions in a database, a web
application similar to the VS Code Marketplace, and a command-line tool for
publishing extensions similar to vsce.

A public instance of Open VSX is running at open-vsx.org.

See also:
https://blogs.eclipse.org/post/brian-king/open-vsx-registry-under-new-management

This is used by projects like VSCodium, which aims to be a fully FLOSS
(rather than "open core") version of Visual Studio Code:

From VSCodium's README.md:

Why Does This Exist

This repository contains build files to generate free release binaries of
Microsoft's VS Code. When we speak of "free software", we're talking about
freedom, not price.

Microsoft's releases of Visual Studio Code are licensed under this not-FLOSS
license and contain telemetry/tracking.

[...]

This repo exists so that you don't have to download+build from source. The
build scripts in this repo clone Microsoft's vscode repo, run the build
commands, and upload the resulting binaries to GitHub releases.
These binaries are licensed under the MIT license. Telemetry is disabled.

To sum it up, it would be nice to see this FLOSS extension support FLOSS
programs and services.

How

These are the steps for publishing:

• https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

Code-wise, it seems to be basically the same as is already being done
here:

npx vsce publish -p ${{ secrets.VSCE_TOKEN }}

vs

npx ovsx publish -p <token>

Alternatively, that page also mentions the following GitHub action, which
claims to be able to publish to both registries at once:

• https://github.com/HaaLeo/publish-vscode-extension

---

Kind of related to:

• Add VSCodium editorconfig.github.com#141

[fasttime]

The version published on the VS Marketplace is 0.16.4, which is almost one year old. The only maintainer since then has not published any updates.

[kmk3]

@fasttime commented on Nov 6:

The version published on the VS Marketplace is 0.16.4,
which is almost one year old. The only maintainer since then has not
published any updates.

Interesting. open-vsx.org has the latest version (0.16.6); I think it is
auto-updated by a bot.

[andymac4182]

Looks like personal token has expired.

[SunsetTechuila]

@xuhdev could you work on creating an account and adding token to the secrets of repo, please?

[SunsetTechuila]

This version of the “EditorConfig for VS Code” extension was published by
open-vsx. That user account is not a verified publisher of the namespace
“EditorConfig” of this extension

no longer true:

however, the ability to urgently push some changes will not be superfluous

[xuhdev]

@xuhdev could you work on creating an account and adding token to the secrets of repo, please?

We just need to use this for some emergencies, am I understanding this right?

[SunsetTechuila]

Yes, don't see any other meaningful reason

[xuhdev]

I don't seem to have any openvsx account and it is unclear who published the extension to open vsx in the past. However, based on my understanding, open vsx didn't support mirroring a few years ago, when EditorConfig was manually published there (eclipse/openvsx#314) until eclipse/openvsx#586 was merged. I suspect EditorConfig became automatically mirrored after the mirroring feature was merged.

However I may not have understood this right. Please correct me if you find anything not matching up.

[xuhdev]

Perhaps @nrayburn-tech has an idea?