Repository navigation
Publish extension to Open VSX Repo? #17173
Description
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?
Activity
brettcannon commentedon Sep 1, 2021
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 commentedon Sep 6, 2021
Cool, already 17 of necessary 5 upvotes provided.
brettcannon commentedon Sep 8, 2021
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 commentedon Sep 8, 2021
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 commentedon Sep 8, 2021
Simon Sobisch (@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
releasebranches for all major versions.GitMensch commentedon Sep 8, 2021
So, is this a "no, please use some CI to publish to open-vsx" (after asking for enough upvotes to do this)?
brettcannon commentedon Sep 9, 2021
Simon Sobisch (@GitMensch) I don't know as I have not discussed this with anyone (I transferred 59 discussions to issues, so I did not filter what got moved over; every created issue got the same comment with no judgement on the merit of the feature request). But do note the message says, "If there's enough upvotes then we will consider this feature request in our future planning", not that we would definitively take it if there was enough votes.
But you specifically said you didn't want to "build the complete repo regularly to just check 'maybe there is a new version to publish'", and so I gave you multiple ways of how to check if there's an update w/o creating a VSIX. I was just trying to be helpful, not send some coded message.
GitMensch commentedon Sep 9, 2021
Thanks for the follow-up. In general I'd also like to see an "official" publishing, but I have no problem to wait for the final decision on that - it is good that you've created an issue to track this.
brettcannon commentedon Nov 1, 2021
Thanks for everyone who voted, but after thinking this over we have decided to not proceed with supporting Open VSIX. Having to support another Marketplace would also mean needing to directly support that Marketplace's users and we are not prepared to take on that increase support requirements of supporting e.g. Theia.
That being said, the extension is and will continue to be open source, and so anyone wanting to upload their own VSIX is welcome to do so as long as the MIT license is met.