Skip to content

Consider making Settings Sync available for OSS builds #110668

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

Closed
coxackie opened this issue Nov 15, 2020 · 11 comments
Closed

Consider making Settings Sync available for OSS builds #110668

coxackie opened this issue Nov 15, 2020 · 11 comments
Assignees
Labels
*out-of-scope Posted issue is not in scope of VS Code wont-fix

Comments

@coxackie
Copy link

A lot of Linux distributions use the OSS build of vscode. The Settings Sync functionality is missing there; see #105310

Could you please consider bringing it? I know that there is an extension that does this, but since there is already a built-in feature, it could be preferable.

Many thanks for your amazing work!

@sandy081
Copy link
Member

Sorry that we do not have plans for this. Hence closing this.

@sandy081 sandy081 added the *out-of-scope Posted issue is not in scope of VS Code label Nov 16, 2020
@coxackie
Copy link
Author

Many thanks for your response. Could you please kindly add a couple of words on explaining why the specific functionality is not included in OSS builds, for posterity?

@sandy081
Copy link
Member

CCing @chrisdias @kieferrm to answer above question.

@coxackie
Copy link
Author

Thanks, @sandy081, I am quite looking forward to see what @chrisdias and @kieferrm have to say.

@thebrownfox
Copy link

@coxackie long story short it's just MS being MS. Technically, there is no reason to not include such functionality. We could use MS binary but it doesn't use system electron but its own bundled version.

#56686

@coxackie
Copy link
Author

@thefoxie Well, ok, one may trash all they want, but they do give this wonderful code base that we can use, and it is a terrific editor. I am sure the exclusion of the extension has anything to do with the bundling of system electron, unless you mentioned it to point out that they are not receptive to accommodate open source requests (which, again, may be just because they are also working under certain legal requirements).

Anyway, let see if we do hear from @chrisdias and @kieferrm at some point.

@thebrownfox
Copy link

@coxackie my guess it would be either legal requirement or just management decision. Why would it has to do anything with electron being bundled or not? Haven't studied the code but I doubt that. Do they add that feature in during build on their servers? Same goes for extensions. We can turn them on (I mean the official repos) via product.json. Why we cannot use the official repos is beyond my understanding as it doesn't make any sense. It's not a technical issue but decision making issue. These guys have little to no say in the matter as I believe we wouldn't be having this conversation if they had. In fact they are victims to the corporate BS as well.

@coxackie
Copy link
Author

well, ok. Even though I understand the constraints these guys are working under, it would have been nice if there was a response, so at least there could be a hint of how to circumvent the fact that nothing can be done (from the corporate side) in order to get this feature. But, oh, well. We will continue relying on the Settings Sync extension of Shan Khan (which is anyway awesome).

@darkbasic
Copy link

Still no official answer on this? I guess it's MS being MS after all...

@thebrownfox
Copy link

@darkbasic it's possible to sync, but not officially, thus it might be against the license. I've almost managed to run the remote ssh. The problem is it loads different version on remote (which throws error) and I have no idea why. But sure, MS just being MS 😄

@VijoPlays
Copy link

True chads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*out-of-scope Posted issue is not in scope of VS Code wont-fix
Projects
None yet
Development

No branches or pull requests

5 participants