search

chapel-lang / chapel-vscode

Apache License 2.0
3 stars 2 forks source link

also publish to the eclipse foundation's OpenVSX marketplace #16

Open MariusAlbrecht opened 1 week ago

MariusAlbrecht commented 1 week ago

microsoft's package registry (as well as their vscode build) come with a number of concerns. An alternative is the OpenVSX marketplace by the eclipse foundation (https://open-vsx.org/about). ovsx is the default marketplace used by vscodium (https://github.com/VSCodium/vscodium/blob/master/docs/index.md#extensions-marketplace).

I think it'd be nice to publish this extension there, as well as in the ms registry. I assume this project's values align with the ones of the eclipse foundation quite well (and certainly more than with microsoft). ovsx also takes the same .vsix file as the ms marketplace so this would mostly be a one-time effort of setting up an account. I would also offer to handle the publishing myself, though I'm not sure if its possible for me to operate a "chapel hpe" eclipse account when I'm just a random person.

see this https://github.com/eclipse/openvsx/wiki/Publishing-Extensions for the publishing process.

jabraham17 commented 1 week ago

Hi @MariusAlbrecht, thanks for the suggestion! This is something we can look into adding.

Something I am not totally clear on is how this interacts with the existing published extension on the Microsoft extension marketplace. Can both exist simultaneously? This is a legal question we need to answer before we do this. But other than that, I see no reason not to do this.

MariusAlbrecht commented 1 week ago

I think both can exist simultaneously. But both the fact that (at least) vscodium exposes custom marketplaces (https://github.com/VSCodium/vscodium/blob/master/docs/index.md#howto-openvsx-marketplace) and that vscode is almost entirely foss and ms just repackages it and adds telemetry make it seem like it should definitely be fine.

I only have the user perspective tho