Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish vscode-autopep8 to Open VSX #102

Closed
DabenW opened this issue Jun 2, 2023 · 1 comment
Closed

Publish vscode-autopep8 to Open VSX #102

DabenW opened this issue Jun 2, 2023 · 1 comment

Comments

@DabenW
Copy link

DabenW commented Jun 2, 2023

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.

@brettcannon
Copy link
Member

Unfortunately we don't have the time and staffing to support multiple marketplaces and builds of VS Code appropriately, so we focus on the official builds and Marketplace only.

This repo is licensed under MIT, though, so please feel free to fork this repo and publish your own copy to Open VSX (or publish from the repo if you don't need to edit any files).

@brettcannon brettcannon closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants