You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In regards to avoiding trademark issues, shouldn't the use of "VS" and "Visual Studio" be removed since that's the name of the Microsoft suite of products? Perhaps this should be named "Codium"? Thoughts?
Any references to "Visual Studio" should be removed (are there any?), but I like keeping the VS part of VSCodium, because it matches with the idea of Chrome/Chromium. "vscode" is MIT licensed, whereas "Visual Studio Code" is not. So iterating on the MIT licensed "vscode" into "VSCodium" seems kosher to me.
Will leave open for a couple of days to allow further discussion
For me it is OK. Originally it comes from Visual Studio but since the name of the project is vscodium and it does not come explicitly from Visual Studio Codium, I don't really think there should be any problem. We can even make up our own meaning of VS...
It is completely legal to use the Visual Studio subbrand?
It's seems like deleting Adobe from Adobe Photoshop Elements and use only Photoshop Elements. I'm not lawyer, but stealing the part of original brand is dirty.
We aren't using "Visual Studio" anywhere. We are using the letters "vs". There exists a open source project called "vscode" and there exists a product called "Visual Studio Code".
@paulcarroty in my opinion your example does not line up with what is happening here. Perhaps a more fitting example: Adobe has an open source project called "brackets". If we were to find something awry with the way it is built and Adobe declined to accept PRs to remedy the situation, we might create "bracketium" which builds "brackets" a specific way but has a name that users can use to distinguish between the two.
When I type code and get into editor - cool.
When I type vscodium - I am unhappy.
Making option in installer to name exe as code would make me very happy.
Reacted by Jannik Siebert and Otavio Augusto Gomes
I agree with @dzmitry-lahoda, well, mostly. It may be just a matter of getting used to it, but ...
What would be the deal if we followed the same idea as the non-free distribution?
codium instead of code (for the binary's name only) - that's much easier to get used to. Type cod<tab>, and you're done.
(As a side-comment, code as a name has always kept me a bit uncomfortable. I think this was intentional name squatting by the developers, using a generic name for a specific product.)
Activity
stripedpajamas commentedon Oct 3, 2018
Any references to "Visual Studio" should be removed (are there any?), but I like keeping the VS part of VSCodium, because it matches with the idea of Chrome/Chromium. "vscode" is MIT licensed, whereas "Visual Studio Code" is not. So iterating on the MIT licensed "vscode" into "VSCodium" seems kosher to me.
Will leave open for a couple of days to allow further discussion
jaredreich commentedon Oct 3, 2018
Ok sounds like you've already done your research on this. Just wanted to ask!
Jorgeelalto commentedon Oct 3, 2018
For me it is OK. Originally it comes from Visual Studio but since the name of the project is vscodium and it does not come explicitly from Visual Studio Codium, I don't really think there should be any problem. We can even make up our own meaning of VS...
paulcarroty commentedon Oct 4, 2018
It is completely legal to use the
Visual Studiosubbrand?It's seems like deleting
AdobefromAdobe Photoshop Elementsand use onlyPhotoshop Elements. I'm not lawyer, but stealing the part of original brand is dirty.stripedpajamas commentedon Oct 4, 2018
We aren't using "Visual Studio" anywhere. We are using the letters "vs". There exists a open source project called "vscode" and there exists a product called "Visual Studio Code".
@paulcarroty in my opinion your example does not line up with what is happening here. Perhaps a more fitting example: Adobe has an open source project called "brackets". If we were to find something awry with the way it is built and Adobe declined to accept PRs to remedy the situation, we might create "bracketium" which builds "brackets" a specific way but has a name that users can use to distinguish between the two.
dzmitry-lahoda commentedon Apr 29, 2019
Renaming to codium would make me happy.
When I type
codeand get into editor - cool.When I type
vscodium- I am unhappy.Making option in installer to name
exeascodewould make me very happy.bittner commentedon May 28, 2019
I agree with @dzmitry-lahoda, well, mostly. It may be just a matter of getting used to it, but ...
What would be the deal if we followed the same idea as the non-free distribution?
codiuminstead ofcode(for the binary's name only) - that's much easier to get used to. Typecod<tab>, and you're done.(As a side-comment,
codeas a name has always kept me a bit uncomfortable. I think this was intentional name squatting by the developers, using a generic name for a specific product.)Any thoughts?
See #36 for a follow-up on this issue.