{"action":"created","issue":{"url":"https://api.github.com/repos/Microsoft/VFSForGit/issues/72","repository_url":"https://api.github.com/repos/Microsoft/VFSForGit","labels_url":"https://api.github.com/repos/Microsoft/VFSForGit/issues/72/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/VFSForGit/issues/72/comments","events_url":"https://api.github.com/repos/Microsoft/VFSForGit/issues/72/events","html_url":"https://github.com/Microsoft/VFSForGit/issues/72","id":329623724,"node_id":"MDU6SXNzdWUzMjk2MjM3MjQ=","number":72,"title":"Change GVFS name","user":{"login":"sanoursa","id":8729434,"node_id":"MDQ6VXNlcjg3Mjk0MzQ=","avatar_url":"https://avatars3.githubusercontent.com/u/8729434?v=4","gravatar_id":"","url":"https://api.github.com/users/sanoursa","html_url":"https://github.com/sanoursa","followers_url":"https://api.github.com/users/sanoursa/followers","following_url":"https://api.github.com/users/sanoursa/following{/other_user}","gists_url":"https://api.github.com/users/sanoursa/gists{/gist_id}","starred_url":"https://api.github.com/users/sanoursa/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sanoursa/subscriptions","organizations_url":"https://api.github.com/users/sanoursa/orgs","repos_url":"https://api.github.com/users/sanoursa/repos","events_url":"https://api.github.com/users/sanoursa/events{/privacy}","received_events_url":"https://api.github.com/users/sanoursa/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":350,"created_at":"2018-06-05T21:02:38Z","updated_at":"2018-08-09T16:53:15Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"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.\r\n\r\nSome guidelines:\r\n\r\n1. **No Git** - As [discussed](https://github.com/Microsoft/GVFS/issues/7), 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.\r\n2. **Short and welcoming** - It has to be a nice welcoming word in most languages (sorry – while [PoopVFS](https://github.com/Microsoft/GVFS/pull/71) 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](https://github.com/Microsoft/GVFS/issues/70) is a no go as well)\r\n3. **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.\r\n\r\nI'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."},"comment":{"url":"https://api.github.com/repos/Microsoft/VFSForGit/issues/comments/411824966","html_url":"https://github.com/Microsoft/VFSForGit/issues/72#issuecomment-411824966","issue_url":"https://api.github.com/repos/Microsoft/VFSForGit/issues/72","id":411824966,"node_id":"MDEyOklzc3VlQ29tbWVudDQxMTgyNDk2Ng==","user":{"login":"sanoursa","id":8729434,"node_id":"MDQ6VXNlcjg3Mjk0MzQ=","avatar_url":"https://avatars3.githubusercontent.com/u/8729434?v=4","gravatar_id":"","url":"https://api.github.com/users/sanoursa","html_url":"https://github.com/sanoursa","followers_url":"https://api.github.com/users/sanoursa/followers","following_url":"https://api.github.com/users/sanoursa/following{/other_user}","gists_url":"https://api.github.com/users/sanoursa/gists{/gist_id}","starred_url":"https://api.github.com/users/sanoursa/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sanoursa/subscriptions","organizations_url":"https://api.github.com/users/sanoursa/orgs","repos_url":"https://api.github.com/users/sanoursa/repos","events_url":"https://api.github.com/users/sanoursa/events{/privacy}","received_events_url":"https://api.github.com/users/sanoursa/received_events","type":"User","site_admin":false},"created_at":"2018-08-09T16:53:15Z","updated_at":"2018-08-09T16:53:15Z","author_association":"CONTRIBUTOR","body":"@chilinux thanks for pointing out the copyright notice, that definitely should not be there. I think it was mistakenly added by someone's default editor settings, and I have filed #149 to remove it. In general, feel free to file issues for problems that you find in the code.\r\n\r\n@nlieb  I agree that the FUSE discussion is off topic here. #126 would be a better place for this discussion. That said, thanks to everyone for all the ideas around how to implement this on Linux. I will restate that I know very little about our available options there, so very open to ideas and suggestions. @nlieb is spot on though, we have a primary constraint that we require near native file system speeds for reads (after initial hydration), or build performance will be unacceptable. There's also a secondary constraint, super nice to have though not required if there are strong reasons to abandon it, to preserve the same driver model on all operating systems so that our user mode code can be the same everywhere. Beyond those two, I think the playing field is currently wide open for our Linux designs."}}
{"actor":{"display_login":"sanoursa"}}