issue tracking workflow, contributing

Home.md

@@ -7,7 +7,7 @@ If you simply want more information on using Code, please visit our [homepage](h
 ## Project Overview
 * [[Roadmap]]
 * [[Design Goals]]
-* [[Workflow]]
+* [[Issue Tracking Workflow]]
 
 ## Contributing to VS Code
 * [[How to Contribute]]

How-to-Contribute.md

@@ -0,0 +1,18 @@
+There are three great ways to contribute to the VS Code project: logging bugs, submitting pull requests, and creating suggestions.
+
+## Logging Bugs
+To log a bug, just use the GitHub issue tracker. Confirmed bugs will be labelled with the `Bug` label. Please include code to reproduce the issue and a description of what you expected to happen.
+
+Don't feel bad if we can't reproduce the issue and ask for more information!
+
+## Pull Requests
+
+Before we can accept a pull request from you, you'll need to sign the Contributor License Agreement (CLA). See the "Legal" section of the [CONTRIBUTING.md guide in the repository](https://github.com/Microsoft/vscode/blob/master/CONTRIBUTING.md). That document also outlines the technical nuts and bolts of submitting a pull request. Be sure to follow our [[Coding Guidelines|Coding-Guidelines]].
+
+## Suggestions
+
+We're also interested in your feedback in future of Code. You can submit a suggestion or feature request through the issue tracker. To make this process more effective, we're asking that these include more information to help define them more clearly. Start by reading the [[Design Goals]].
+
+## Discussion Etiquette
+
+In order to keep the conversation clear and transparent, please limit discussion to English and keep things on topic with the issue. Be considerate to others and try to be courteous and professional at all times.

Issue-Tracking-Workflow.md

@@ -0,0 +1,53 @@
+## Issue Tracking 101
+
+When you submit an issue, here's what will happen.
+
+We'll be using Labels to track the status of suggestions or feature requests. You can expect to see the following:
+
+`[empty]`
+
+Issues that are unlabelled have not been looked at by a VS Code coordinator. You can expect to see them labelled within a few days of being logged.
+
+`Bug`
+
+Issues with the `Bug` label are considered to be defects. Once they have the `Bug` label, they'll either be assigned to a developer and assigned a milestone, or put in the Community milestone, indicating that we're accepting pull requests for this bug. Community bugs are a great place to start if you're interested in making a code contribution to TypeScript.
+
+`Suggestion`
+
+We consider this issue to not be a bug per se, but rather a design change or feature of some sort. Any issue with this label should have at least one more label from the list below
+
+`Needs Proposal`
+
+A full write-up is needed to explain how the feature should work
+
+`Needs More Info`
+
+A proposal exists, but there are follow-up questions that need to be addressed
+
+`In Discussion`
+
+This is being discussed by the TypeScript design team. You can expect this phase to take at least a few weeks, depending on our schedule
+
+`Ready to Implement`
+
+The proposal is accepted and has been designed enough that it can be implemented now
+
+`Accepting PRs`
+
+We are accepting pull requests that fully implement this feature
+
+`Committed`
+
+We have allocated time on the team schedule to implement this feature
+
+`Declined`
+
+Declined suggestions will have this label along with one of the following:
+ * `Out of Scope`: Is outside the scope of the project and would be better implemented as a separate tool or extension
+ * `Too Complex`: The amount of complexity that this (and its future implications) would introduce is not justified by the amount of value it adds
+ * `Breaking Change`: Would meaningfully break compatibility with a previous version of VS Code, or would prevent us from implementing known future proposals
+ * `By Design`: This aspect of the Tool is an intentional design decision
+
+Issues that are not bugs or suggestions will be labelled appropriately (`Question`, `By Design`, `External`) and closed.
+
+Please use [Stack Overflow](http://go.microsoft.com/fwlink/?LinkID=536384) for VS Code questions.

Roadmap.md

@@ -1,7 +1,7 @@
 
 ## 0.10.0
 ### Schedule
-| Task | Dates |
+| Task                      | Dates         |
 | ------------------------- | ------------- |
 | Development               | Oct 5 - Nov 6 |
 | Insiders drop             | Nov 9         |