microsoft / vscode-data-wrangler

Other
419 stars 16 forks source link

Publish data-wrangler to Open VSX #165

Closed roxane-data closed 5 months ago

roxane-data commented 5 months ago

Dear extension author, Please publish this extension to the Open VSX marketplace.

Context

Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX.

What is Open VSX? Why does it exist?

Open VSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia-based IDEs, and so on.

You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.

How can you publish to Open VSX?

The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the ovsx publish command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.

pwang347 commented 5 months ago

Hi @roxane-data, thank you for opening this issue. I discussed this with the team and unfortunately this is not something we plan to support at the moment, since this means we would need to be prepared to support users from all derivative IDEs. Note that we are currently moving fast and making various integrations; as a result we cannot make such guarantees. For a similar answer please see https://github.com/microsoft/vscode-python/issues/17173#issuecomment-956875871.

If anything changes, I will reopen this issue and let you know. Thank you!

ChristofKaufmann commented 2 months ago

@pwang347 I do understand this, but vscode-python has got an MIT license, while vscode-data-wrangler has got a VS Marketplace license (?). So, to my understanding, it is not possible that the community can handle the user support for derived IDEs. Or is it? For such an important extension, especially now that the Jupyter DataViewer got deprecated, there should something available for derived IDEs. As an example: We use code-server on a JupyterHub on our University cluster and there will be an exam in September. With no alternative to view DataFrames in memory, I won't update code-server to 1.92.