Consolidate general contributing steps to CONTRIBUTING.md

.github/CONTRIBUTING.md

@@ -6,6 +6,8 @@ However, for those individuals who want a bit more guidance on the best way to c
 
 Before opening a new issue or pull request, we do appreciate if you take some time to search for [possible duplicates](https://github.com/hashicorp/vagrant/issues?q=sort%3Aupdated-desc), or similar discussions on [HashiCorp Discuss](https://discuss.hashicorp.com/c/vagrant/24). On GitHub, you can scope searches by labels to narrow things down.
 
+To ensure that the Vagrant community remains an open and safe space for everyone we also follow the [HashiCorp community guidelines](https://www.hashicorp.com/community-guidelines). When contributing to Vagrant, please respect these guidelines.
+
 ## Issues
 
 ### Reporting an Issue
@@ -30,7 +32,40 @@ No pull request template is provided on GitHub. The expected changes are often a
 
 **Tip:** Make it small! A focused PR gives you the best chance of having it accepted. Then, repeat if you have more to propose!
 
-### How to prepare
+### Setup a development installation of Vagrant
+
+There are a few prerequisites for setting up a development environment with Vagrant. Ensure you have the following installed on your machine:
+
+* git
+* bsdtar
+* curl
+
+#### Install Ruby
+
+It's nice to have a way to control what version of ruby is installed, so you may want to install [rvm](https://rvm.io/rvm/install), [chruby](https://github.com/postmodern/chruby#install) or [rbenv](https://github.com/rbenv/rbenv#installation). For Windows [ruby installer](https://rubyinstaller.org/) is recommended.
+
+#### Setup Vagrant
+Clone Vagrant's repository from GitHub into the directory where you keep code on your machine:
+
+```
+  $ git clone https://github.com/hashicorp/vagrant.git
+```
+
+Next, move into the newly created `./vagrant` directory.
+
+```
+  $ cd ./vagrant
+```
+
+All commands will be run from this path. Now, run the `bundle` command to install the Ruby dependencies:
+
+```
+  $ bundle install
+```
+
+You can now run Vagrant by running `bundle exec vagrant` from inside that directory.    
+
+### How to prepare your pull request
 
 Once you're confident that your upcoming changes will be accepted:
 
@@ -39,11 +74,54 @@ Once you're confident that your upcoming changes will be accepted:
   * Checkout a new branch based on master; `git checkout -b my-contrib master`
     Please avoid working directly on the `master` branch.
 * Make focused commits of logical units and describe them properly.
-* Avoid re-formatting of the existing code
+* Avoid re-formatting of the existing code.
 * Check for unnecessary whitespace with `git diff --check` before committing.
-* If possible, submit tests along with your topic branch. It will help a lot to get your your patch / new feature accepted, and should prevent unwanted breaking changes to silently happen in future developments.
+* Tests are required in each pull request. There are some exceptions like docs changes and dependency constraint updates.
 * Assure nothing is broken by running manual tests, and all the automated tests.
 
+### Running tests
+
+Vagrant uses rspec to run tests. Once your Vagrant bundle is installed from Git repository, you can run the test suite with:
+
+    bundle exec rake
+
+This will run the unit test suite, which should come back all green!
+
+If you are developing Vagrant on a machine that already has a Vagrant package installation present, both will attempt to use the same folder for their configuration (location of this folder depends on system). This can cause errors when Vagrant attempts to load plugins. In this case, override the `VAGRANT_HOME` environment variable for your development version of Vagrant before running any commands to be some new folder within the project or elsewhere on your machine. For example, in Bash:
+
+    export VAGRANT_HOME=~/.vagrant-dev
+
+You can now run Vagrant commands against the development version:
+
+    bundle exec vagrant
+
+### Acceptance Tests
+
+Vagrant also comes with an acceptance test suite that does black-box
+tests of various Vagrant components. Note that these tests are **extremely
+slow** because actual VMs are spun up and down. The full test suite can
+take hours. Instead, try to run focused component tests.
+
+To run the acceptance test suite, first copy `vagrant-spec.config.example.rb`
+to `vagrant-spec.config.rb` and modify it to valid values. The places you
+should fill in are clearly marked.
+
+Next, see the components that can be tested:
+
+```
+$ rake acceptance:components
+cli
+provider/virtualbox/basic
+...
+```
+
+Then, run one of those components:
+
+```
+$ rake acceptance:run COMPONENTS="cli"
+...
+```
+
 ### Submit Changes
 
 * Push your changes to a topic branch in your fork of the repository.

README.md

@@ -50,47 +50,6 @@ and you're welcome to give it a shot. Please review the installation page [here]
 
 ## Contributing to Vagrant
 
-Once your Vagrant bundle is installed from Git repository, you can run the test suite with:
-
-    bundle exec rake
-
-This will run the unit test suite, which should come back all green!
-
-If you are developing Vagrant on a machine that already has a Vagrant package installation present, both will attempt to use the same folder for their configuration (location of this folder depends on system). This can cause errors when Vagrant attempts to load plugins. In this case, override the `VAGRANT_HOME` environment variable for your development version of Vagrant before running any commands, to be some new folder within the project or elsewhere on your machine. For example, in Bash:
-
-    export VAGRANT_HOME=~/.vagrant-dev
-
-You can now run Vagrant commands against the development version:
-
-    bundle exec vagrant
-
 Please take time to read the [HashiCorp Community Guidelines](https://www.hashicorp.com/community-guidelines) and the [Vagrant Contributing Guide](https://github.com/hashicorp/vagrant/blob/master/.github/CONTRIBUTING.md).
 
 Then you're good to go!
-
-### Acceptance Tests
-
-Vagrant also comes with an acceptance test suite that does black-box
-tests of various Vagrant components. Note that these tests are **extremely
-slow** because actual VMs are spun up and down. The full test suite can
-take hours. Instead, try to run focused component tests.
-
-To run the acceptance test suite, first copy `vagrant-spec.config.example.rb`
-to `vagrant-spec.config.rb` and modify it to valid values. The places you
-should fill in are clearly marked.
-
-Next, see the components that can be tested:
-
-```
-$ rake acceptance:components
-cli
-provider/virtualbox/basic
-...
-```
-
-Then, run one of those components:
-
-```
-$ rake acceptance:run COMPONENTS="cli"
-...
-```

website/pages/intro/contributing-guide.mdx

@@ -8,7 +8,7 @@ description: |-
   Style Guide to ensure the Vagrant project stays healthy.
 ---
 
-# Contributing Style Guide
+# Contributing to Vagrant During Hacktoberfest
 
 HashiCorp has some [community guidelines](https://www.hashicorp.com/community-guidelines)
 to ensure our public forums are a safe space for everyone. When contributing 
@@ -38,12 +38,12 @@ in order to setup a development environment.
 
 ## Submitting your first pull request
 
-When submitting your first pull request to Vagrant make sure you have 
+Check out the [Vagrant contribution guide](https://github.com/hashicorp/vagrant/blob/master/.github/CONTRIBUTING.md)
-completed the following steps:
+for instructions on what can be expected for the pull request lifecycle.
+
+When submitting your changes, please ensure you have done the following:
 
 * You have written tests for the changes made
 * You have run the test suite using `bundle exec rake` and all tests pass
 * You have written a descriptive commit message
 * Reference the issue the pull requests resolves if applicable
-
-### Writing your first Vagrant test