GVfs name is already taken #7
Comments
|
Our product is the "Git Virtual File System". I'm sure we'll take a hard look at the coincidence of the acronyms matching. |
|
Just throwing it out there but perhaps GitVFS is enough to make everyone happy? |
|
Not only polite, but beneficial due to reduced confusion. |
|
It's a very fair point, and something we're considering. |
There repo is named "GVFS", every announcement also callsit "GVFS", the title in the README says "GVFS" and so does everything else in it.
This sentence from the README only says what it GVFS stands for but all the evidence points out to "GVFS" being the product name and not "Git Virtual File System"
Yeah, but what a coinceidence that one of them also ends in "Virtual File System", right? It's not like it only takes 2 seconds to google the name and find out that it's already taken by another project in the same area.
|
|
GitVFS is probably the least confusion option here. After all, gvfs and GnomeVFS are also different.. |
|
The name clash is actually worsened by the fact that they're both |
|
@hobarrera which is even more worsened by the fact that it only takes few seconds to check. It's like Swift and Swift. Swift is 8 years older than Swift. Gvfs git logs go back to 2007. I wouldn't put it past Micro$oft and Apple to deliberately pick these names even though they clash with competing projects. |
|
"Git" is a trademark, so a name like GitVFS seems to be problematic, but so does Git Virtual File System. https://git-scm.com/trademark |
|
msgvfs (TM) |
|
How about calling it 'Remote Git File System' RGFS? This would actually describe what this does a little better and short google and github search didn't reveal collisions to other projects for me. (GRFS does). |
|
Years ago you called it "Smart Files" on SkyDrive on Windows 8.1. Still a good name to consider. |
@TsuTsuKaKushi: there is also OpenStack Swift ;) |
|
Given #4 I don't think this will actually be a problem in the wild. |
|
@TsuTsuKaKushi you give some good arguments but your use of Micro$oft kinda undermines your reasons. Using that term comes over as very childish and immature. We're all adults here, right? Can we have professional discussions without acting like that. |
|
Since it exists mainly for the purpose of making a ~270 GB repository manageable, I put forward |
|
I don't think the GNOME Virtual File System (GVfs) is copyrighted. Alos, this is called GVFS. |
|
That is not correct. GVfs is not designated to the public domain and may only be used in compliance with its copyright license (LPGLv2+). But that does not seem at all relevant to this issue. There is significant potential for confusion due to this naming and it would seem to be beneficial to both parties to avoid that. The vast majority of Linux desktops (anything not KDE-based) have many gvfs processes constantly running in the background; on my machine, I count gvfs-afc-volume-monitor, gvfsd, gvfsd-fus, gvfsd-http, gvfsd-metadata, gvfsd-trash, gvfs-goa-volume-monitor, gvfs-gphoto2-volume-monitor, gvfs-mtp-volume-monitor, gvfs-udisks2-volume-monitor. Having an unrelated project whose name differs only in capitalization is going to be a confusing mess. It will also make searching for GVFS very problematic; a quick web search for GVFS shows about half the results currently refer to Microsoft's GVFS, and half to GNOME's GVfs. It also means users searching for GVFS on e.g. Wikipedia will be directed to information about GNOME and away from information about Microsoft's product. |
|
@mcatanzaro I have already been in touch with Ondrej Holy on the Gnome GVFS project, and thank you for reaching out as well. This was an unfortunate naming coincidence - "VFS" is a very generic term, and we got unlucky that our G collided with yours - and we definitely intend to address it. I don't have an immediate answer but we are working on it. We don't want to make a knee-jerk name change, only to have to change it again later. So what I will say for now is that we are very aware of the need to change, and we will not release on Linux under this name. For now, this is effectively a preview and not a released product, so I ask for some patience as we determine the best name to use. |
|
Sounds good, thanks @sanoursa! |
In many cases they don't differ in that either, for example in package managers the package names aren't usually capitalized. |
Let's welcome
I find this name far far better than "Git Virtual File System", even without name collision, because the purpose of this Git VFS is to allow working on Git repositories connected to a remote one. We can imagine some other Git Virtual File System with other purpose, for example we can imagine a “Dedupe Git File System” that adds underlying support for rolling checksum deduplication to standard git repositories to help big binary files management without git modification. So, today the name is already colliding with GNOME's gvfs project on the VFS part, but tomorrow it can also collide with other Git VFS projects with other purpose, colliding on both Git and VFS. |
|
I'd like to vote for |
|
how about 'telegit', 'gitunnel', 'gitrans' ....'git-remote-magic' ... ☺
|
|
a few gems... |
|
I appreciate all the creative ideas :-). Closing this issue for now until we have something more to announce on the topic. |
|
oh yeah lol forgot alpha characters XD |
This is a renaming example based on suggestion found there: microsoft#7 (comment) This was done doing: ```sh git ls-files | xargs -n1 -P1 dirname | grep GVFS | sort -u | sed -e 's/GVFS/RGFS/g' | xargs -n1 -P1 mkdir -p git ls-files | grep GVFS | sed -e 'p;s/GVFS/RGFS/g' | xargs -n2 -P1 git mv git clean -df git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 sed -e 's/gvfs/rgfs/g;s/gvFS/rgFS/g;s/Gvfs/Rgfs/g;s/GVFS/RGFS/g' -i git add . ``` If you prefer another name, it wouldn't be hard to adapt the renaming script above and replay it on the whole tree.
This is a renaming example based on suggestion found there: microsoft#7 (comment) This was done doing: ```sh git ls-files | xargs -n1 -P1 dirname | grep GVFS | sort -u | sed -e 's/GVFS/RGFS/g' | xargs -n1 -P1 mkdir -p git ls-files | grep GVFS | sed -e 'p;s/GVFS/RGFS/g' | xargs -n2 -P1 git mv git ls-files | grep Gvfs | sed -e 'p;s/Gvfs/Rgfs/g' | xargs -n2 -P1 git mv git clean -df git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 sed -e 's/gvfs/rgfs/g;s/gvFS/rgFS/g;s/Gvfs/Rgfs/g;s/GVFS/RGFS/g' -i git add . ``` If you prefer another name, it wouldn't be hard to adapt the renaming script above and replay it on the whole tree. You can check everything is renamed that way: ```sh git ls-files | grep -i gvfs git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 grep -Hi gvfs ```
This is a renaming example based on suggestion found there: microsoft#7 (comment) Note that RGFS name is not my own idea but that name fits the need. If you prefer another name, it wouldn't be hard to adapt the following renaming script and run it on the whole tree. This was done doing: ```sh git ls-files | xargs -n1 -P1 dirname | grep GVFS | sort -u | sed -e 's/GVFS/RGFS/g' | xargs -n1 -P1 mkdir -p git ls-files | grep GVFS | sed -e 'p;s/GVFS/RGFS/g' | xargs -n2 -P1 git mv git ls-files | grep Gvfs | sed -e 'p;s/Gvfs/Rgfs/g' | xargs -n2 -P1 git mv git clean -df git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 sed -e 's/gvfs/rgfs/g;s/gvFS/rgFS/g;s/Gvfs/Rgfs/g;s/GVFS/RGFS/g' -i git add . ``` You can check everything is renamed that way: ```sh git ls-files | grep -i gvfs git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 grep -Hi gvfs ```
|
There’s currently no confusion between this tool for Git repositories and the GNOME tools, since they don’t even run on the same operating systems. Right now, we are fully invested in our R&D efforts, and we are not actively considering a name change. I understand that many of you are passionate about this issue, but the name will remain GVFS for the immediate future and we will re-evaluate at a later date. |
|
Are you just saying GVFS will never be cross platform? (or assuming GNOME will never run on Windows?) |
|
That thread has the highest amount of weird statements I ever seen in my life:
|
So that article is a lie? |
|
Most certainly not, we are actively looking at other platforms as we speak. However, today they do not run on the same operating systems, so there is no risk of confusion. |
|
@sanoursa I'm not sure running in one or other platform is something important for name collisions, I don't expect someone to think GVFS cannot be confused with GVFS because in the description one says it runs on one platform or the other. Note that we are receiving comments and complains about this, I'm confident GNOME community and by extend the free software community is displeased by this issue and I hope a solution will come sooner rather than later. |
|
Ignoring this issue comes off as extremely arrogant on Microsoft's part. In the past Microsoft dedicated much of its existence to destroying Linux and the free software community. Now if they want to play with the big boys, they need to show some common decency and not act like they are above everyone else. This name is already taken, and the products are extremely similar. |
I've witnessed and experienced confusion because of this on several forums such as Hacker News and Reddit. There is risk of confusion and confusion and every time either technology is discussed there is always confusion. |
|
The longer you guys wait on this, the worse it looks for Microsoft, and the harder and more painful it will be to change the name to something proper. |
|
Hi @sanoursa, not trying to beat this with a dead horse, but there might be a good reason to consider this being a priority. There is a lot tied to the name:
To me, the quesiton is whether to fracture all that now (small difficulty) or later (greater difficulty). And it seems that if a name was chosen the community might make most needed changes for you (see #51). Also, honestly, it can't really take that long to come up with a name. Like what, a few hours tops? My humble opinion 😄 |
This also renames GVFlt to RGFlt to be consistent with GVFS being renamed to RGFS. This is a renaming example based on suggestion found there: microsoft#7 (comment) Note that RGFS name is not my own idea but that name fits the need. If you prefer another name, it wouldn't be hard to adapt the following renaming script and run it on the whole tree. This was done doing: ```sh git ls-files | xargs -n1 -P1 dirname | grep GVFlt | sort -u | sed -e 's/GVFlt/RGFlt/g' | xargs -n1 -P1 mkdir -p git ls-files | xargs -n1 -P1 dirname | grep GvFlt | sort -u | sed -e 's/GvFlt/RgFlt/g' | xargs -n1 -P1 mkdir -p git ls-files | grep GVFlt | sed -e 'p;s/GVFlt/RGFlt/g' | xargs -n2 -P1 git mv git ls-files | grep GvFlt | sed -e 'p;s/GvFlt/RgFlt/g' | xargs -n2 -P1 git mv git ls-files | grep gvflt | sed -e 'p;s/gvflt/rgflt/g' | xargs -n2 -P1 git mv git clean -df git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 sed -e 's/gvflt/rgflt/g;s/Gvflt/Rgflt/g;s/GvFlt/RgFlt/g;s/GVFlt/RGFlt/g;s/GVFLT/RGFLT/g' -i ``` You can check everything is renamed that way: ```sh git ls-files | grep -i gvflt git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 grep -Hi gvflt ```
This also renames GvLib to RgLib to be consistent with GVFS being renamed to RGFS. This is a renaming example based on suggestion found there: microsoft#7 (comment) Note that RGFS name is not my own idea but that name fits the need. If you prefer another name, it wouldn't be hard to adapt the following renaming script and run it on the whole tree. This was done doing: ```sh git ls-files | grep GvLib | sed -e 'p;s/GvLib/RgLib/g' | xargs -n2 -P1 git mv git ls-files | grep gvlib | sed -e 'p;s/gvlib/rglib/g' | xargs -n2 -P1 git mv git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 sed -e 's/gvlib/rglib/g;s/GvLib/RgLib/g;s/GVLIB/RGLIB/g' -i ``` You can check everything is renamed that way: ```sh git ls-files | grep -i gvlib git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 grep -Hi gvlib ```
This also renames GvLib to RgLib to be consistent with GVFS being renamed to RGFS. This is a renaming example based on suggestion found there: microsoft#7 (comment) Note that RGFS name is not my own idea but that name fits the need. If you prefer another name, it wouldn't be hard to adapt the following renaming script and run it on the whole tree. This was done doing: ```sh git ls-files | grep GvLib | sed -e 'p;s/GvLib/RgLib/g' | xargs -n2 -P1 git mv git ls-files | grep gvlib | sed -e 'p;s/gvlib/rglib/g' | xargs -n2 -P1 git mv git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 sed -e 's/gvlib/rglib/g;s/GvLib/RgLib/g;s/GVLIB/RGLIB/g' -i ``` You can check everything is renamed that way: ```sh git ls-files | grep -i gvlib git ls-files | xargs -n1 -P1 file | grep ':.*text' | cut -f1 -d: | xargs -n1 -P1 grep -Hi gvlib ```
Then this issue should remain open, that is unless you don't intend to make good on your promise. |
|
You've hit Slashdot, and Microsoft is squarely in the wrong on this one. You cannot win this battle. Your GVFS info will be buried underneath GNOME's GVFS in search results and you will make nerds personally hate you for your discourteous choice. |
you can't buy love and you're managing that git-related project and git-related issue on GitHub the worst way to get some love. If you want to be loved be kind, see #51 for a one-click way to be kind. |
|
@sanoursa Microsoft's inaction on this issue has brought it to the front page of Slashdot https://tech.slashdot.org/story/18/06/03/0626246/microsoft-sticks-with-controversial-gvfs-name-despite-backlash. Please consider doing something to remedy this issue before it becomes more talked about than the GitHub acquisition. |
|
to be honest, the slashdot news made me wanna try GVfs today |
|
and now the people, who can easily ignore the opinion of the community, own GitHub -- one of the hugest open-source community I hope, there is a decentralized alternative to github 😆 |
|
Many developers jumped ship yesterday to SourceForge, Gitlab, Gogs, etc. on receiving the news that Microsoft owns GitHub now. |
align arg list format in Mac/Linux interop classes
and others
The GNOME Virtual File System (GVfs) is already a well established thing and is in Wikipedia https://en.wikipedia.org/wiki/GVfs. It would be polite to consider a different name for Microsoft GVFS.
The text was updated successfully, but these errors were encountered: