Merge pull request #43 from super-harsh/improve/samples

Update ASOv2 samples and repo docs

Author: theunrepentantgeek

CONTRIBUTING.md

@@ -1,8 +1,8 @@
 # Contributing Guidelines
 
-The Azure Service Operator project accepts contributions via GitHub pull requests. This document outlines the process to help get your contribution accepted.
+The Azure Service Operator Samples project accepts contributions via GitHub pull requests. This document outlines the process to help get your contribution accepted.
 
-Please see also the [Azure Service Operator Developer Guide](docs/community/developer-guide.md).
+Please see also the [Azure Service Operator Contribution Guide](https://azure.github.io/azure-service-operator/contributing) for Azure Service Operator contributions.
 
 ## Contributor License Agreements
 
@@ -14,48 +14,17 @@ The [Microsoft CLA](https://cla.microsoft.com/) must be signed by all contributo
 ***NOTE***: Only original source code from you and other people that have
 signed the CLA can be accepted into the repository.
 
-## Support Channels
-
-This is an open source project and as such no formal support is available. However, like all good open source projects we do offer "best effort" support through github issues.
-
-GitHub issues can be filed here - https://github.com/Azure/azure-service-operator/issues
-
-Before opening a new issue or submitting a new pull request, it's helpful to search the project - it's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware of.
-
-## Issues
-
-Issues are used as the primary method for tracking anything to do with the Azure Service Operator project.
-
-### Issue Lifecycle
-
-The issue lifecycle is mainly driven by the core maintainers, but is good information for those contributing to the project. All issue types follow the same general lifecycle. Differences are noted below.
-1. Issue creation
-2. Triage
-    - The maintainer in charge of triaging will apply the proper labels for the issue. This includes labels for priority, type, and metadata. If additional
-    labels are needed in the future, we will add them.
-    - (If needed) Clean up the title to succinctly and clearly state the issue. Also ensure that proposals are prefaced with "Proposal".
-3. Discussion
-    - "Feature" and "Bug" issues should be connected to the PR that resolves it.
-    - Whoever is working on a "Feature" or "Bug" issue (whether a maintainer or someone from the community), should either assign the issue to themself or make a comment in the issue saying that they are taking it.
-    - "Proposal" and "Question" issues should stay open until resolved or if they have not been active for more than 30 days. This will help keep the issue queue to a manageable size and reduce noise. Should the issue need to stay open, the `keep open` label can be added.
-4. Issue closure
 
 ## How to Contribute a Patch
 
 1. If you haven't already done so, sign a Contributor License Agreement (see details above).
 2. Fork the desired repo, develop and test your code changes.
 3. Submit a pull request.
 
-## Reporting Security Issues
-
-Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, including this one.
-
-If you believe you have found a security vulnerability in this repository that meets Microsoft's [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below.
-
-**Please do not report security vulnerabilities through public GitHub issues.**
+## Support Channels
 
-Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).
+This is an open source project and as such no formal support is available. However, like all good open source projects we do offer "best effort" support through github issues.
 
-We prefer all communications to be in English.
+GitHub issues can be filed here - https://github.com/Azure/azure-service-operator/issues
 
-Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).
+Before opening a new issue or submitting a new pull request, it's helpful to search the project - it's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware of.

README.md

@@ -1,14 +1,10 @@
 # Azure Service Operator Samples
 
-This project contains example uses of the Azure Service Operator. These examples show how to deploy Azure services alongside your Kubernetes deployments.
+This project contains example uses of the Azure Service Operator. These examples show how to deploy Azure services alongside your Kubernetes deployments. 
+For more information on ASO, refer to our [official documentation website](https://azure.github.io/azure-service-operator/).
 
 ## Examples
 
-The example deployments currently contained in this repository:
-
-* [azure-votes-sql](./azure-votes-sql) - example Go web app using Azure SQL Server
-* [wordpress-demo](./wordpress-demo) - example deploying Wordpress with Azure Databases for MySQL
-
 ### ASO v2
 Examples using the v2 operator with code-generated resources for full coverage.
 * [azure-votes-postgresql](./azure-votes-postgresql) - Go voting web app using PostgreSQL server
@@ -33,7 +29,7 @@ Go to the directory containing the example you would like to try. Follow the rea
 
 ## Contributing
 
-The [contribution guide][contribution-guide] covers everything you need to know about how you can contribute to Azure Service Operators. The [developer guide][developer-guide] will help you onboard as a developer.
+The [contribution guide][contribution-guide] covers everything you need to know about how you can contribute to Azure Service Operator Samples.
 
 ## Support