Update documentation for extensions and contribution model.

CONTRIBUTING.md

@@ -4,21 +4,21 @@ Welcome and thank you for your interest in contributing to **Virtual Client** pr
 review this document for policies and procedures which will ease the contribution and review process for everyone. 
 If you have questions, please contact **[email protected]**.
 
-### Before Starting
+## Before Starting
 Ensure that you have attended to the preliminaries for the repo and have an understanding of how to build and test your
 changes to the source code.
 
 * [Repo Fundamentals](README.md)
 
-### Style Guidelines
+## Style Guidelines
 Most of the coding style is enforced using static code/style analysis toolsets that are integrated into the project when built.
 This makes it easier for developers to follow the patterns. The important thing to remember here is that new projects must import
 the build environment settings. You can see examples of the import at the bottom of any project (e.g. csproj) file in the
 repo.
 
 As a general rule, if it builds, the majority of your style requirements are already completed! :)
 
-### Test Guidelines
+## Test Guidelines
 Any changes or additions to source code in this repo carry the requirement at a minimum that unit tests be written to verify
 important behaviors. The team does not typically accept changes to source code in this repo without having proper unit tests.
 Take the time to look at existing unit tests within the project. A lot of effort was made to create unit tests that are clear,
@@ -27,30 +27,23 @@ robust unit tests for code in this repo.
 
 Review our documentation on testing if you would like to learn more on our practices and philosophies around testing.
 
-### Pull Request(PR) Process
+## Pull Request(PR) Process
 The following steps will help you get your changes in for review by the team. Review the repo README if you need a reminder
 or examples on how to build and test code within the repo.
 
-##### Creating/Submitting Changes
-* Create a topic branch for your changes (e.g. users/alias/ChangeDescription). We do not allow users to push changes directly to the master branch.
-* Ensure all solutions/projects within the repo build successfully before submitting your PR.
+### Creating/Submitting Changes
+* Create a fork/branch for your changes (e.g. users/alias/ChangeDescription). We do not allow users to push changes directly to the master branch.
+* Ensure all solutions/projects within the repo build successfully before submitting your PR (see README noted above).
 * Ensure all tests within the repo pass before submitting your PR. Passing unit and functional tests is a gate to complete the PR.
 * Update any documentation, user and contributor, that is impacted by your changes.
   * Check for markdown (e.g. README.md) files within the solution or project directory.
   * Team members will typically help you with pointers to documentation needing update as part of the pull request process.
-* Increase the version numbers for any assemblies (.exe or .dll) for which you have changed.
-  * We use [semantic versioning](http://semver.org/).
-* Include your change description in `CHANGELOG.md` file as part of pull request.
 * Push your changes to the remote.
-* Browse to the Azure DevOps location for the repo and create a pull request for your branch/changes. You do not need to
-  add reviewers to the pull request. The team will be automatically added.  Feel free to add any other reviewers that you'd like
-  to the pull request though.
-* Add a referenced work item to the pull request you created.
+* Start a pull request for the team to review.
 
-##### Getting Approvals
+### Getting Approvals
 After you've created the pull request, the following requirements must be met before you will be able to complete the pull request:
 * An automated PR build must complete successfully.
 * Team reviewers must review the code and provide at least 1 approval.
   * Any feedback/comments provided by reviewers must be resolved and changes committed + pushed to the remote.
-* Ownership enforcement must be satisfied. In general this is satisfied by the step above since most (if not all) of the team reviewers
-  are part of the owners group for the repo (see: owners.txt).
+* Once approved, your changes will be merged with the "main" branch.

README.md

@@ -14,18 +14,19 @@ The following links provide additional information on the Virtual Client project
 
 ## [Getting Started](https://microsoft.github.io/VirtualClient/docs/guides/getting-started/)
 
-You will follow the [**Tutorial**](https://microsoft.github.io/VirtualClient/docs/guides/getting-started/) to benchmark your system with a quick workload: OpenSSL Speed - SHA256.
+You can follow along with the ["getting started" tutorial](https://microsoft.github.io/VirtualClient/docs/guides/getting-started/) running a quick workload (OpenSSL Speed - SHA256) on your
+local system.
 
 ## Contributing
 
-We welcome your contribution, and there are many ways to contribute to VirtualClient:
+We welcome your contribution, and there are a number of ways to contribute to the Virtual Client project:
 
-* [Just say Hi](https://github.com/microsoft/VirtualClient/discussions/categories/show-and-tell). It inspires us to know that there are fellow performance enthusiatics out there and VirtualClient made your work a little easier.
-* [Feature Requests](https://github.com/microsoft/VirtualClient/issues/new/choose). It helps us to know what benchmarks people are using.
-* [Submit bugs](https://github.com/microsoft/VirtualClient/issues/new/choose). We apologize for the bug and we will investigate it ASAP.
-* Review [source code changes](https://github.com/microsoft/VirtualClient/pulls). You likely know more about one workload than us. Tell us your insights.
-* Review the [documentation](https://github.com/microsoft/VirtualClient/tree/main/website/docs) and make pull requests for anything from typos to new content.
-* We welcome you to directly work in the codebase. Please take a look at our [CONTRIBUTING.md](./CONTRIBUTING.md). [Start here](https://microsoft.github.io/VirtualClient/docs/category/developing/) and contact us if you have any questions.
+* [Make a Feature Request](https://github.com/microsoft/VirtualClient/issues/new/choose).
+* [Submit bugs](https://github.com/microsoft/VirtualClient/issues/new/choose). We apologize for anything missed and will investigate it ASAP.
+* [Review source code changes](https://github.com/microsoft/VirtualClient/pulls).
+* [Review the documentation](https://github.com/microsoft/VirtualClient/tree/main/website/docs).
+* [Fork and Contribute Directly](./CONTRIBUTING.md). We welcome you to directly work in the codebase. We offer a [developer guide](https://microsoft.github.io/VirtualClient/docs/category/developing/). Please contact us if you have any questions.
+* [Provide Feedback to the Team](https://github.com/microsoft/VirtualClient/discussions/categories/show-and-tell).
 
 Thank you and we look forward to your contribution.