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

Source code #179

Closed
wwahammy opened this issue May 6, 2019 · 7 comments
Closed

Source code #179

wwahammy opened this issue May 6, 2019 · 7 comments
Labels
*question Issue represents a question, should be posted to StackOverflow (VS Code)

Comments

@wwahammy
Copy link

wwahammy commented May 6, 2019

Where is the source code? I read the FAQ but VSCode is supposed to be an open source tool. So again, where is the source code?

@kieferrm kieferrm added the *question Issue represents a question, should be posted to StackOverflow (VS Code) label May 6, 2019
@kieferrm kieferrm closed this as completed May 6, 2019
@wwahammy
Copy link
Author

wwahammy commented May 6, 2019

As mentioned in my first message, I read the FAQ. You're using GOBS of open source and promote VSCode as an open source tool. This is really uncool and anti-community.

@bhack
Copy link

bhack commented May 6, 2019

@kieferrm I hope that "are not currently open-source" it is not, between the line, "never".

This is because the VS Code Remote extensions are also used in fully managed remote development services

I think nobody care about open-sourcing the full managed part of the code, so I hope that at some point you can separate the code useful to be released from the managed one.

@wwahammy
Copy link
Author

wwahammy commented May 6, 2019

@kieferrm Why would the container extension even use Microsoft services? I shouldn't have to use your services to work with containers on my own machine.

And while I would love if the managed part of the code was available, I don't see that as the major issue. Developing in a container is a MAJOR feature for developing code and it feels pretty anti-user for me to have to either use your services or have to use a proprietary license in your "open source" editor to do it.

@wwahammy
Copy link
Author

wwahammy commented May 6, 2019

Oh, I get what's going on: you're using this in your proprietary Visual Studio Online and you don't want anyone else to be able to do the same.

Glad my needs as a developer are so high on your list.

@bhack
Copy link

bhack commented May 6, 2019

@EricSchultz I understand you point but I don't think that a flame mode it is useful here.
I think managed code could be proprietary and related to free or payed managed Microsoft services but could be separated for the others remote plugins features that not strictly involved in the managed services.
I hope the the team could do a claim about this topic as an outlook over the plugins cause if all the stuffs will stay embedded with managed services it will be hard to release any part of this plugins of general use.

@wwahammy
Copy link
Author

wwahammy commented May 6, 2019

@bhack to be clear, I'm not flaming. I expected that core features of VSCode would be open source and I've been telling people how great of an open source editor it was. As a community member, I feel pretty misled.

@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*question Issue represents a question, should be posted to StackOverflow (VS Code)
Projects
None yet
Development

No branches or pull requests

3 participants