Can I put the extensionsGallery on my vscode fork?

[evandrocoan]

By default the https://github.com/Microsoft/vscode does not come with key:

"extensionsGallery": {
    "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
    "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
    "itemUrl": "https://marketplace.visualstudio.com/items"
}

on its https://github.com/Microsoft/vscode/blob/master/product.json file. That entry is required to install extensions from the marketplace as showed on:

1. https://stackoverflow.com/questions/37143536/no-extensions-found-when-running-visual-studio-code-from-source

Also there is this commits, where their developer putted the key:

1. b00945f
2. f1d0c1d

But sequentially removed it justifying:

Revert inadvertant change to product.json

Why they are removing it? Seems they are using it while developing, as we may see he let slip the line to the upper stream. Can I put it on my fork? Or I can only use it locally as they seem to be doing?

---

Related issues:

1. Menu license links to non Open Source license #60 Command "Extensions: Install Extension" missing when running vscode from source
2. Command "Extensions: Install Extension" missing when running vscode from source #2647 Command "Extensions: Install Extension" missing when running vscode from source
3. Can't see extensions or load via command line #28253 Can't see extensions or load via command line
4. How do I enable extensions in the extensions dir in OSS Dev mode #23831 How do I enable extensions in the extensions dir in OSS Dev mode
5. Add marketplace extension installation details vscode-wiki#30 Add marketplace extension installation details

[joaomoreno]

cc @chrisdias @chrmarti

[MattSturgeon]

Since b00945f was committed under the MIT license, I would argue that you can redistribute any changes from it under a MIT compatible license.

While you cannot copy from the product.json included in the proprietary VS Code product, I would maintain that the following text has been released under MIT and therefore can be redistributed within your fork.

"extensionsGallery": {
    "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
    "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
    "itemUrl": "https://marketplace.visualstudio.com/items"
}

---

Being new to the project and conscious of Free Software licenses, I have never downloaded the propitiatory product, agreed to the license nor read any of the propitiatory code. My only knowledge of the above code comes through b00945f and this issue.

I am not a lawyer and this is not legal advice.

[kenijo]

A question on the cacheURL: https://vscode.blob.core.windows.net/gallery/index

It looks like it hasn't been updated since March 2017. The most recent "lastUpdated" date is 2017-03.
It there anyway to get this fixed or to get working URL?

[dtinth]

Based on this comment, the answer is yes?

[ghost]

Even if it wasn't licensed, the code in question is so tiny and generic (it's literally a few labels and web addresses) that I would question whether it's even copyrightable in the first place.

[jens1o]

@chrisdias any legal update?

[ivanfilhoz]

Acknowledging some public URLs and copying them into the settings file of your own product isn't a copyright infringement at all.

[nhooyr]

@ivanslf its not just about copying the lines, the terms of use for the vs code marketplace state that it can only be used with visual studio products. It's not clear whether that includes forks.

[rrmckinley]

This exists now
https://projects.eclipse.org/proposals/eclipse-open-vsx-registry
https://devclass.com/2020/03/31/eclipses-theia-sees-1-0-declared-not-your-parents-ide/

http://open-vsx.org/ Extensions for VS Code Compatible Editors

Sven Efftinge, co-founder of both Gitpod and TypeFox... continued, “Microsoft prohibits non-Visual Studio products from installing any binaries downloaded from their marketplace.”

So, “We encourage VS Code extension developers to push their extensions to Open VSX in addition to Microsoft’s marketplace.” Open VSX is “an open-source implementation of a VS Code extension registry that we have developed under the umbrella of the Eclipse Foundation”.

[ivanfilhoz]

@nhooyr @rrmckinley I wasn't aware of that, thanks.

For ethical reasons, I'm uninstalling VSCode immediately in favor of Theia.

Vendor Neutral
The Theia project is hosted at the Eclipse Foundation, a not-for-profit corporation, and is developed by a diverse community.
Unlike other "open-source" projects, projects hosted at an Open-Source Foundation are protected against single-vendor decisions against the interest of the diverse community. Learn more here.

[rrmckinley]

@ivanfilhoz It was announced today so very few people were aware.

eclipse-theia/theia#7072
eclipse-theia/theia@73bd544

If you get the chance, I'd love to hear your first impressions of Theia 1.0, thanks

I've created a feature request for the VSCodium project which would allow this on plain Code and not just Theia VSCodium/vscodium#372

[spoenemann]

For ethical reasons, I'm uninstalling VSCode immediately in favor of Theia.

@ivanfilhoz Theia is not an editor/IDE, but a framework for building IDEs. There's no generic Theia-based application that you could download at the moment. But of course anyone is free to start a new project using Theia to build an Electron app that mimics VS Code.

[theAkito]

@toddewilliams

Thanks for the effort. This clarified everything and I think we all can understand now, without a doubt. 😃

[toddewilliams]

Hey @chrisdias, I believe you can close this now, unless you want to officially contradict the analysis in my prior comment.

[StarNumber12046]

as far as I know, if you HAVE vscode, you can use the marketplace BUT not distribute it

[GitMensch]

Hm, this is still open, not resolved...
Actually @chrisdias wrote in #1557 (comment)

yes, you can configure product.json to point to the official marketplace. look in the product.json that is installed with the visual studio code distro for the url.

So that does contradict to @toddewilliams analysis.
As others pointed out: it is totally fine to have extensions published in the MS marketplace that are explicit licensed only for use with Microsoft Visual Code - but what would be the point of the marketplace to forbid its use with OSS vscode, especially as it is also allowed to be accessed via any browser?

As vscode is the only OSS the list could easily be adjusted to read;

-Visual Studio Code, GitHub Codespaces, Azure DevOps, Azure DevOps Server, and successor products and services
+Visual Studio Code and derivatives thereof, GitHub Codespaces, Azure DevOps, Azure DevOps Server, and successor products and services

... it may be good to update the marketplace TOU as the use is said to be only valid

for use only with In-Scope Products and Services

where does accessing it with the browser instead of the APIs fit there?

[toddewilliams]

@chrisdias is not in a position to speak for Microsoft and was likely told he overstepped his role in his prior comment. That is why he has not commented further.

And while it is true that you can configure project.json to point to the official marketplace that doesn't mean you may (ie. you legally are permitted to do it). Licenses tell you what you are legally permitted to do and they are very clear on this point; I stand by my prior analysis, above.

Microsoft benefits from not answering this question directly as the only answer is to admit that you are not permitted to use the their official marketplace in anything that isn't a Microsoft product. They don't want to do that for obvious reasons.

I continue to invite an actual representative of Microsoft to contradict my prior analysis and close this issue if I've made any errors in the interpretation of their licenses.