Publish on Open VSX

[piechologist]

Would you mind publishing this extension on Open VSX? I noticed you have already a few others over there.

Anyway, thank you for making this at all! It's one of few extensions I use.

[rioj7]

@piechologist I haven't published them. They are ported and published automatically by a script.

I have added a PR to add a few more: open-vsx/publish-extensions#683

Some of them might be useful to you too. Some have a scary configuration but can do a lot ;-) of repetitive work.

[piechologist]

Thank you very much! I'll check them out when they become available (Open VSX refreshes at 3:03 UTC).

BTW: I like scary configs 😃.

[GanerCodes]

Any update on this? I'm switching over and can't seem to find my favorite plugin

[rioj7]

@GanerCodes the previous time I added a PR to the same repo they responded within a few days. And merged the PR. Now I do it for a couple of extensions. The last commit was 2023-05-08.

[filiptronicek]

Hey there @rioj7 👋,
since the PR at hand, open-vsx/publish-extensions#683 is adding quite a few extensions, would it be possible for you to setup publishing on your end? If we succeeded with that, there would be way less overhead for us (Open VSX) and if something goes wrong (like wrong versions being published and publishing delays after releases), you'll know right away, which might take some time before users reach out about missing releases.

Setting this up with GitHub Actions is pretty easy¹ and could be even realized from one repository instead of having a release Action for every extension of yours.

The main motivation for us to have it this way is to keep the number of extensions in the repository as small as possible so that it can only focus on extensions for which the community takes care in terms of publishing.

Footnotes

1. The doc for help with this is in our repository: link ↩

[rioj7]

@filiptronicek

If openVSX can do the publishing automatically via extensions.json (it does it already for a few hundred extensions) I see no reason to change my workflow. Is the script not capable of handling a few more? All those developers also don't publish it themselves. That is the reason the auto publish script was made.

I will not put any publish tokens in Github.

I don't mind the delay. I don't use OpenVSX and the related VSC.

[filiptronicek]

@rioj7 it is true that the script could "handle publishing a few more", but the scope of my work for the last year and a half has been in big part to reduce how many extensions are in that extensions.json file. Having less of them reduces the nightly CI time and it frees my time for maintaining extensions from people who e.g. cannot legally publish the extensions¹ or extensions whose authors we fail to contact about publishing.

Nevertheless, I'll merge the PR and get back to you with how things went with publishing. We'll be happy to have your extensions.

Footnotes

1. because publishing requires signing the Eclipse Open VSX agreement, some large companies take years to process ↩

[rioj7]

@filiptronicek Thanks.

If OpenVSX had a similar program like vsce I would use it to publish on OpenVSX.

If an extension fails to publish automatic remove it from the list, if the developer does not respond to contact/issues remove the extension (you are not able to update the extension repo, forking would make you the maintainer of all those extensions), maybe don't try to update all extensions every night, update n%7==day_of_week.

[filiptronicek]

If OpenVSX had a similar program like vsce I would use it to publish on OpenVSX.

@rioj7 we do! It's called ovsx and it's built on vsce.

[GanerCodes]

@rioj7 pls