Repo checklist items (#70)

Adding:
- contributing guide
- readme updates
- support information
- issue templates
- component governance pipeline definition

Author: idavis

.ado/build.yml

@@ -0,0 +1,23 @@
+name: qsharp
+
+trigger:
+- main
+
+pr:
+- main
+
+schedules:
+- cron: "0 9 * * Sat"
+  displayName: 'Build for Component Governance'
+  branches:
+    include:
+    - main
+  always: true
+
+jobs:
+- job: "qsharp"
+  pool: 
+    vmImage: 'ubuntu-latest'
+  steps:
+  - task: ms.vss-governance-buildtask.governance-build-task-component-detection.ComponentGovernanceComponentDetection@0
+    displayName: 'Component detection'

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,39 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug, needs triage
+assignees: ''
+---
+
+**Describe the bug**
+
+Describe what the unexpected behavior or issue is. 
+Please file a single issue per bug instead of enumerating multiple items.
+
+**To Reproduce**
+
+Steps to reproduce the behavior:
+1. Open or go to '...'
+2. Type or click on '....'
+3. See error
+
+The more information you can provide, the more likely someone will be successful at reproducing the issue and finding a fix.
+
+**Expected behavior**
+
+Describe what you expect to happen, versus what actually happened.
+
+**Screenshots**
+
+If applicable, add screenshots to help explain your problem.
+
+**System information**
+
+- Version of the package or extension for which the problem occurs
+- Your operating system
+- For issues with extensions, the version of the IDE for which the problem occurs
+
+**Additional context**
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement, needs triage
+assignees: ''
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

CONTRIBUTING.md

@@ -0,0 +1,59 @@
+# Contributing to Q#
+
+Welcome, and thank you for your interest in contributing to Q# and the Quantum Development Kit!
+
+## Asking and Answering Questions
+
+Have a question? The `q#` tags on [Stack Overflow](https://stackoverflow.com/questions/tagged/q%23) and [Quantum Computing StackExchange](https://quantumcomputing.stackexchange.com/questions/tagged/q%23) are great places to ask questions about Q#, Quantum Development Kit and quantum computing in general.
+You can learn more about our work on the [Q# Development Blog](https://devblogs.microsoft.com/qsharp/) and ask questions in the comments as well.
+Your question will server as resource to others searching for help.
+
+## Reporting Issues
+
+Have you identified a reproducible problem in the Quantum Development Kit?
+Have a feature request?
+We want to hear about it!
+
+You can follow the [template](https://github.com/microsoft/qsharp/issues/new?assignees=&labels=bug&template=bug_report.md&title=) for reporting issues on this repository.
+
+## Contributing Code
+
+If you are interested in helping fix issues you or someone else encountered,
+please make sure that the corresponding issue has been filed on the repository.
+Check that nobody is currently working on it and that it has indeed been marked as bug.
+If that's the case, indicate on the issue that you are working on it,
+and link to the corresponding GitHub page where the fix is being developed.
+If someone is already working on a fix, ask if you can help or see what other things can be done.
+If an issue is labeled as feature, please follow the guidelines related to contributing features.
+Sometimes it may take a couple of days for us to label issues appropriately.
+If an issue has not been labeled yet, please indicate that you would like to work on it and be patient -
+we are a small team and are doing our best to be quick with responding to your inquiry!
+
+**Note:**
+Issues related to the design and evolution of the Q# language are marked with
+[Area-Language](https://github.com/microsoft/qsharp/issues?q=is%3Aissue+is%3Aopen+label%3AArea-Language).
+
+If you are interested in contributing a new feature,
+please first check if a similar functionality has already been requested.
+If so, consider contributing to the discussion around it rather than filing a separate issue.
+If no open or closed issue with such a request already exists,
+please file one following the [feature request template](https://github.com/microsoft/qsharp/issues/new?assignees=&labels=feature&template=feature_request.md&title=).
+We will respond to feature requests and follow up with a discussion around its feasibility,
+how one might go about implementing it, and whether that is something we would consider adding to our repo.
+There are several reasons why we might not be able to eventually merge even a great feature for one reason or another.
+Take a look at our general contribution guide for [reasons why this might be the case](https://docs.microsoft.com/azure/quantum/contributing-code#when-a-pull-request-is-rejected).
+Even if we are not able to incorporate something into the packages and extensions we distribute,
+we encourage you to pursue your passion project in your own fork,
+and share and discuss your thoughts and progress on the corresponding issue.
+
+If you are looking for a place to get started with contributing code,
+search for example for the [good-first-issue](https://github.com/microsoft/qsharp/labels/good%20first%20issue) or [help-wanted](https://github.com/microsoft/qsharp/labels/help%20wanted) labels.
+Also, look for issues that have already been discussed in more detail,
+and check if you can help someone who has already started working on it.
+
+And last but not least:
+
+# Thank You!
+
+Your contributions to open source, large or small, make great projects like this possible.
+Thank you for taking the time to contribute.

LICENSE LICENSE.txt

@@ -1,14 +1,21 @@
-# Project
+# Q# language and tooling:
 
-> This repo has been populated by an initial template to help get you started. Please
-> make sure to update the content to build a great experience for community-building.
+> Under development
 
-As the maintainer of this project, please make a few updates:
+This repository contains Q# tooling, specifically:
 
-- Improving this README.MD file to provide a great experience
-- Updating SUPPORT.MD with content about this project's support experience
-- Understanding the security reporting process in SECURITY.MD
-- Remove this section from the README
+- **[compiler](./compiler/qsc/)**: command line compiler
+- **[library](./library/)**: standard library
+- **[npm](./npm/)**: Q# npm module
+- **[playground](./playground/)**: simple website for interacting with Q#
+
+## Feedback
+
+If you have feedback about the content in this repository, please let us know by filing a [new issue](https://github.com/microsoft/qsharp/issues/new/choose)!
+
+## Reporting Security Issues
+
+Security issues and bugs should be reported privately following our [security issue documentation](./SECURITY.md#reporting-security-issues).
 
 ## Contributing
 
@@ -24,7 +31,11 @@ This project has adopted the [Microsoft Open Source Code of Conduct](https://ope
 For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
 contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
 
-## Trademarks
+For more details, please see [CONTRIBUTING.md](./CONTRIBUTING.md).
+
+## Legal and Licensing
+
+### Trademarks
 
 This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft 
 trademarks or logos is subject to and must follow 

README.md

@@ -1,13 +1,3 @@
-# TODO: The maintainer of this repo has not yet edited this file
-
-**REPO OWNER**: Do you want Customer Service & Support (CSS) support for this product/project?
-
-- **No CSS support:** Fill out this template with information about how to file issues and get help.
-- **Yes CSS support:** Fill out an intake form at [aka.ms/onboardsupport](https://aka.ms/onboardsupport). CSS will work with/help you to determine next steps.
-- **Not sure?** Fill out an intake as though the answer were "Yes". CSS will help you decide.
-
-*Then remove this first heading from this SUPPORT.MD file before publishing your repo.*
-
 # Support
 
 ## How to file issues and get help  
@@ -16,10 +6,6 @@ This project uses GitHub Issues to track bugs and feature requests. Please searc
 issues before filing new issues to avoid duplicates.  For new issues, file your bug or 
 feature request as a new Issue.
 
-For help and questions about using this project, please **REPO MAINTAINER: INSERT INSTRUCTIONS HERE 
-FOR HOW TO ENGAGE REPO OWNERS OR COMMUNITY FOR HELP. COULD BE A STACK OVERFLOW TAG OR OTHER
-CHANNEL. WHERE WILL YOU HELP PEOPLE?**.
-
 ## Microsoft Support Policy  
 
 Support for this **PROJECT or PRODUCT** is limited to the resources listed above.