Publish extension to Open VSX Repo?

[brettcannon]

Discussed in #16730

^{Originally posted by clin1234 July 20, 2021}
For the sake of VSCodium users, please be generous in the spirit of open-source and also publish it in Open VSX?

[brettcannon]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 5 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[GitMensch]

Cool, already 17 of necessary 5 upvotes provided.

[brettcannon]

Do note this repository is open source and under an MIT license, so anyone can fork this repo and publish on Open VSX w/o us (people already do this for Vim).

[GitMensch]

Totally, but it is obviously "better" to not create unnecessary forks or build the complete repo regularly to just check "maybe there is a new version to publish".

[brettcannon]

@GitMensch we publish on the same day as VS Code does for major releases (which is roughly once a month; there isn't a release of VS Code in the month of January). We also create an issue under the https://github.com/microsoft/vscode-python/labels/release%20plan label for all major releases (and we pin them to the top of our issue tracker here).

We also publish all releases to https://github.com/microsoft/vscode-python/releases, so you can subscribe to this repo and choose to only be notified when we make a new release, big or small.

We also create release branches for all major versions.

[GitMensch]

So, is this a "no, please use some CI to publish to open-vsx" (after asking for enough upvotes to do this)?