Rename "Code - OSS Dev" to "Visual Studio Code OSS" or something similar

[ghost]

Please rename "Code - OSS Dev" to "Visual Studio Code OSS" or something similar.

The current name is bad (IMHO) for two reasons:

1. The hyphen makes it confusing. As you can see with my edits, I initially thought it was meant to be "OSS Dev"
2. It's not similar enough to "Visual Studio Code". Having the same project named "Visual Studio Code" (branded), "vscode" (OSS repo)", "Code - OSS Dev" (built OSS version), and sometimes just "Code" when talking about it is pretty problematic because people might not realize it is essentially the same program.

This is even more problematic if you consider that the OSS version is already so separate with no official prebuilt packages and the official site has only proprietary EULA branded packages, so making the name so vastly different just makes the situation even more confusing for the user.

Compare for example with Oracle (yes I know they also do bad stuff to OSS, but this is one thing they did right):

• JDK vs OpenJDK
• VirtualBox vs VirtualBox OSE
• ...

If the current naming was done because the "Visual Studio" name is protected, then please have your lawyers write a community use policy of the name so it can be used in the open-source builds too (as "Visual Studio Code OSS" or similar). Other companies managed to do the same, it's not that hard.

Edit: revised ticket to be more clear to read

[adamvoss]

@Jonast I'm curious because I don't remember seeing that term. Where does one find "Code - OSS Dev"?

[slodki]

@adamvoss Software build from MIT-licensed sources uses this name. Microsoft closed source builds uses different names.

[vscodebot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that have been on the backlog for a long time but have not gained traction: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!