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

Rename GVFS to "M$vfs" #70

Closed
sojirosan opened this issue Jun 4, 2018 · 14 comments
Closed

Rename GVFS to "M$vfs" #70

sojirosan opened this issue Jun 4, 2018 · 14 comments

Comments

@sojirosan
Copy link

Short for Micro$haft virtual file system.

Gnome has used the name GVfs for YEARS. Why do you greedy jerks think you can just steal this name?

I can only imagine what would happen if I tried to name my own file system NTFS...

@sojirosan
Copy link
Author

So this is the "extinguish" part in M$'s strategy, right?

https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

@extremeheat
Copy link

Congratulations on creating your first Github issue.

When you're using Github issues (or perhaps any issue tracker anywhere), it helps to use the thing called the search feature to make sure that nobody has already created the same issue before. As it turns out (I'll save you the time), your issue mirrors #7, #15, #31 and #36. Also, in general it is good etiquette to not be a dick and not ramble about irrelevant stuff or personal vendettas when you're not adding anything relevant to the conversation.

@woohooyeah
Copy link

Yeah, it seems they closed these issues, but the problem has clearly not been solved. The repo still has the stolen 'GVFS' acronym, belonging to the GNOME Virtual File System.

A multi-billion dollar corporation, incapable of inventing their own unique names and acronyms? It looks so incredibly dumb. And it's very provocative. Everyone with a functioning set of brains will hold Microsoft in lower esteem because of this.

Sorry to say it, but in my view they do deserve to be flamed for this. Until they correct their behaviour.

@Licshee
Copy link

Licshee commented Jun 4, 2018

TIL each one need a globally unique name

@sojirosan
Copy link
Author

@extremeheat

Also, in general it is good etiquette to not be a dick and not ramble about irrelevant stuff or personal vendettas when you're not adding anything relevant to the conversation.

And then you do exactly the same thing. Huh... okay. While we're on the subject of hypocrisy, let's not forget about all the projects Microsoft got extremely butthurt over for having the same or similar names as their products:

You know what, I think I'll create my own OS called Windows... Microsoft clearly doesn't care about globally unique names so it should be cool, right? Satya won't mind, will he?

@woohooyeah
Copy link

You know what, I think I'll create my own OS called Windows... Microsoft clearly doesn't care about globally unique names so it should be cool, right? Satya won't mind, will he?

Yeah, but you'll have to pretend that the name collision is coincidental too, as in the initial response in #7 .

@Licshee
Copy link

Licshee commented Jun 4, 2018

You surely can do that and try to make people believe you don't know there is a "Microsoft Windows" which have taken major market share on desktop/laptop for about 30 years and it's a registered trademark.

@mvastola
Copy link

mvastola commented Jun 4, 2018

@extremeheat, I'm normally all for the "you catch more flies with honey" approach, but -- as you pointed out -- that was tried in #7, #15, #31 and #36 to no avail.

Also, while @sojirosan could have commented on the original issue (#7), that would not achieve the same visibility as a new issue which has not yet been closed. This is generally a more direct way of calling Microsoft to task on this issue, especially in light of their acquisition of GitHub -- which, if Microsoft expects to be successful, requires more fully embracing the open source community.

@sojirosan
Copy link
Author

sojirosan commented Jun 4, 2018

Thanks @mvastola , that was the entire point of this issue. The name will cause confusion and is also a giant middle finger to the FOSS community. If Microsoft wants to prove that it has changed its ways, then it needs to respect major conflicts like this. People have argued that it's not a big deal because there are so many examples of similar name conflicts, but none of them are of the same type of project. GVFS and GVfs are both virtual file systems, so there is bound to be significant confusion between the two. In fact, there already has been - people looking for help or info on GVFS may find questions on SO or elsewhere that apply to the other GVFS that will cause confusion. This name is a bad, bad, bad idea, and it will bite M$ in the ass.

@Licshee
Copy link

Licshee commented Jun 4, 2018

I agree microsoft should change the name, but it has nothing to do with openness

it will bite M$ in the ass

this is the reason

@sam0x17
Copy link

sam0x17 commented Jun 4, 2018

I'm sure people will keep opening name change issues over and over again until this is fixed ;)

@bet0x
Copy link

bet0x commented Jun 4, 2018

I propose PoopVFS, i even made a PR: #71

@mvastola
Copy link

mvastola commented Jun 5, 2018

@bet0x, you have to sign the Contributor License Agreement for #71 so Microsoft will own the copyright to your changes and the right to use your PoopVFS name idea. :-)

@sanoursa
Copy link
Contributor

sanoursa commented Jun 5, 2018

I definitely take the name collision seriously. I just opened an issue to brainstorm ideas for a new name for this project

@sanoursa sanoursa closed this as completed Jun 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants