Modernize vim-hack

- update standard files to current FB standards
- remove everything except syntax highlighting in favor of `hh_client
  lsp` (and update readme to cover this)
- set filetype to `hack` rather than `php`

Author: fredemmott

CODE_OF_CONDUCT.md

@@ -0,0 +1,5 @@
+# Code of Conduct
+
+Facebook has adopted a Code of Conduct that we expect project participants to adhere to.
+Please read the [full text](https://code.fb.com/codeofconduct/)
+so that you can understand what actions will and will not be tolerated.

CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# Contributing to vim-hack
+We want to make contributing to this project as easy and transparent as
+possible.
+
+## Our Development Process
+
+We primarily work by sending pull requests to the master branch of GitHub. Releases are also
+tagged from this branch.
+
+## Pull Requests
+We actively welcome your pull requests.
+
+1. Fork the repo and create your branch from `master`.
+2. If you've added code that should be tested, add tests.
+3. If you've changed APIs, update the documentation.
+4. Ensure the test suite passes.
+5. If you haven't already, complete the Contributor License Agreement ("CLA").
+
+## Contributor License Agreement ("CLA")
+In order to accept your pull request, we need you to submit a CLA. You only need
+to do this once to work on any of Facebook's open source projects.
+
+Complete your CLA here: <https://code.facebook.com/cla>
+
+## Issues
+We use GitHub issues to track public bugs. Please ensure your description is
+clear and has sufficient instructions to be able to reproduce the issue.
+
+Facebook has a [bounty program](https://www.facebook.com/whitehat/) for the safe
+disclosure of security bugs. In those cases, please go through the process
+outlined on that page and do not file a public issue.
+
+## License
+By contributing to vim-hack, you agree that your contributions will be licensed
+under the LICENSE file in the root directory of this source tree.

README.md

@@ -1,3 +1,21 @@
+About `vim-hack`
+================
+
+`vim-hack` provides file type detection and syntax highlighting for Hack files.
+
+For advanced features, we recommend using this plugin in combination with a
+Language Server Protocol plugin for Vim, such as
+[LanguageClient-neovim](https://github.com/autozimu/LanguageClient-neovim),
+configured to run `hh_client lsp` - for example:
+
+```
+let g:LanguageClient_serverCommands = {
+  \ 'hack': [ 'hh_client', 'lsp' ],
+  \ }
+```
+
+LanguageClient-neovim supports both vim and nevim.
+
 Installation
 ============
 
@@ -13,3 +31,12 @@ that ships with Vim 7.4, or a compatible file.
 For more information on the Hack language, visit http://hacklang.org.
 
 [pathogen]: https://github.com/tpope/vim-pathogen
+
+Alternatively, if you are using `vim-plug`:
+
+    Plug 'hhvm/vim-hack'
+
+License
+=======
+
+vim-hack is BSD licensed, as found in the LICENSE file. We also provide an additional patent grant.

after/ftplugin/php.vim

@@ -11,9 +11,12 @@
 " grant of patent rights can be found in the PATENTS file in the same
 " directory.
 
-au BufRead,BufNewFile *.hhi setl filetype=php
+au BufRead,BufNewFile *.hhi
+  \ setl filetype=hack |
+  \ runtime! syntax/php.vim
 
-au BufRead,BufNewFile *.hh
+au BufRead,BufNewFile *.hh,*.php
   \ if getline(1) =~ '^<?hh' |
-  \   setl filetype=php |
+  \   setl filetype=hack |
+  \   runtime! syntax/php.vim |
   \ endif