Change GVFS name

We’ve heard the feedback, so lets use this issue to come up with a new name for this project. As we all know, folks from Microsoft don’t have a rich tradition of picking super awesome names for things. I'm no exception to that pattern, so I was thinking we could all put some sensible suggestions into this issue. I’ll then compile a short list and then we’ll all get to vote on the new name.

Some guidelines:

1. No Git - As discussed, we don’t want it to be GitName or things like that – we don’t want to mess with Git’s name and the fact that it is vendor agnostic.
2. Short and welcoming - It has to be a nice welcoming word in most languages (sorry – while PoopVFS might elicit a giggle, it won't make the cut when I go to meetings with the Windows team with that in my slide deck. Also it needs to not contain special characters so M$FT is a no go as well)
3. Descriptive - Something that sort of sounds descriptive for how GVFS works would be awesome. If you leave the naming up to me I’ve already proven it will turn into an acronym and the point of this is to have a name we love. Ideally a word that you can type into a search bar and get to our project would be good, so it probably shouldn't be a real word - but sounds like one.

I'll put my thinking cap on and start putting some stuff in here, but please add your ideas. Making the name change won't be as simple as doing s/gvfs/newname/g so I'll need to do some stuff once we pick a name, but I'm excited to try to come up with something cool.

Read the naming guidelines in this issue and the linked discussion in issue #7, then review the comment thread for the current decision status. No files, tests, or implementation entry points are identified; done would require an agreed new name followed by a separately scoped migration plan.