Clean up readme

1. Remove contribution section as it has been moved to contribution.md
2. Cleanup other redundant sections.

README.md

@@ -8,8 +8,6 @@
 - [Quick Start Guide](#quick-start-guide)
 - [Run SDK Samples](#run-sdk-samples)
 - [API Documentation](#api-documentation)
-- [Submitting samples](#submitting-samples)
-- [Resource Maintenance](#resource-maintenance)
 - [Repository Administrator Resources](#repository-administrator-resources)
 - [VMware Resources](#vmware-resources)
 
@@ -207,65 +205,6 @@ $ python samples/vsphere/vcenter/vm/list_vms.py -v
 
 The API documentation can be found [here](doc/client.zip)
 
-## Submitting samples
-
-### Developer Certificate of Origin
-
-Before you start working with this project, please read our [Developer Certificate of Origin](https://cla.vmware.com/dco). All contributions to this repository must be signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on as an open-source patch.
-
-### Sample Template
-
-[Sample template](sample_template) contains boilerplate code that can be used to build a new sample.
-Please copy the file and use it as a starting point to write a new sample.
-
-### Required Information
-
-The following information must be included in the README.md or in the sample docstring in case README already exists in same folder.
-* Author Name
-  * This can include full name, email address or other identifiable piece of information that would allow interested parties to contact author with questions.
-* Minimal/High Level Description
-  * What does the sample do ?
-* Any KNOWN limitations or dependencies
-
-### Suggested Information
-
-The following information should be included when possible. Inclusion of information provides valuable information to consumers of the resource.
-* vSphere version against which the sample was developed/tested
-* SDK version against which the sample was developed/tested
-* Python version against which the sample was developed/tested
-
-### Contribution Process
-
-* Follow the [GitHub process](https://help.github.com/articles/fork-a-repo)
-  * Please use one branch per sample or change-set
-  * Please use one commit and pull request per sample
-  * Please post the sample output along with the pull request
-  * If you include a license with your sample, use the project license
-
-### Code Style
-
-Please conform to pep8 standards. Check your code by running the pep8 tool.
-    https://pypi.python.org/pypi/pep8
-
-## Resource Maintenance
-### Maintenance Ownership
-
-Ownership of any and all submitted samples are maintained by the submitter.
-
-### Filing Issues
-
-Any bugs or other issues should be filed within GitHub by way of the repository’s Issue Tracker.
-
-### Resolving Issues
-
-Any community member can resolve issues within the repository, however only the board member can approve the update. Once approved, assuming the resolution involves a pull request, only a board member will be able to merge and close the request.
-
-### VMware Sample Exchange
-
-It is highly recommended to add any and all submitted samples to the VMware Sample Exchange:  <https://code.vmware.com/samples>
-
-Sample Exchange can be allowed to access your GitHub resources, by way of a linking process, where they can be indexed and searched by the community. There are VMware social media accounts which will advertise resources posted to the site and there's no additional accounts needed, as the VMware Sample Exchange uses MyVMware credentials.     
-
 ## Repository Administrator Resources
 
 ### Board Members
@@ -276,13 +215,10 @@ Members:
 * Tianhao He (VMware)
 * Steve Trefethen (VMware)
 
-### Approval of Additions
-
-Items added to the repository, including items from the Board members, require 2 votes from the board members before being added to the repository. The approving members will have ideally downloaded and tested the item. When two “Approved for Merge” comments are added from board members, the pull can then be committed to the repository.
-
 ## VMware Resources
 
 * [vSphere Automation SDK Overview](http://pubs.vmware.com/vsphere-65/index.jsp#com.vmware.vapi.progguide.doc/GUID-AF73991C-FC1C-47DF-8362-184B6544CFDE.html)
+* [VMware Sample Exchange](https://code.vmware.com/samples) It is highly recommended to add any and all submitted samples to the VMware Sample Exchange
 * [VMware Code](https://code.vmware.com/home)
 * [VMware Developer Community](https://communities.vmware.com/community/vmtn/developer)
 * VMware vSphere [REST API Reference documentation](https://code.vmware.com/web/dp/doc/preview?id=4644).