Initial commit

CONTRIBUTING.md

@@ -0,0 +1,78 @@
+Please provide as much information as possible when reporting a bug or filing an issue on the Visual C++ for Linux Development.
+A well written bug will follow the template:
+
+###1) Issue Title
+
+A title succinctly describing the issue. 
+
+####Example:
+
+`Build not working with GCC 5.4.`
+
+###2) Brief description
+
+A brief description of what you are attemping to do.
+
+####Example:
+
+`I'm trying to use GCC 5.4 with the extension and it isn't working, description of my configuration below.`
+
+###3) VC++ version / Linux system / enviornment details
+
+Your Visual Studio and VC++ version numer.  This can be seen in the VS Help, About menu. Look for Visual C++ for Linux Development.
+
+Additional information like GCC, GDB versions is also helpful, as are details of your hardware if running on an embedded system.
+
+Here is an example on getting basic Linux system information.
+```
+uname -a
+Linux jinx 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux
+``` 
+
+####Example:
+`Microsoft Visual Studio Community 2015`
+`Version 14.0.25421.03 Update 3`
+`Visual C++ for Linux Development 1.0.4`
+`Linux jinx 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux`
+
+###4) Steps required to reproduce
+
+Explanation of how to reproduce the probelm, e.g. libraries needed, propery page options set, sequence of build, debug steps, packages installed on Linux system, etc.
+
+####Example:
+
+`On Linux box:`
+`sudo add-apt-repository ppa:ubuntu-toolchain-r/test`
+`sudo apt-get update`
+`sudo apt-get install gcc-5 g++-5`
+`In Visual Studio`
+`Create console project`
+`Set a breakpoint on entry to main and hit F5`
+
+###5) Copy of the build output window
+
+####Example:
+
+```
+1>------ Build started: Project: ConsoleApplication9, Configuration: Debug ARM ------
+1>Build started 7/14/2016 2:19:58 PM.
+1>     1>
+1>Building with tools version "14.0".
+1>     1>
+```
+
+###6) Expected Behavior
+
+What was the expected result of what you expected? HEre for example, "It should have built and hit the break point" would be sufficient, other cases may require more explanation to help us understand.
+
+###8) Additional information
+
+Some bugs require additional information such as scripts to reproduce.  Please add to this section.
+
+If there are files required, email the files to [email protected] with:
+Subject:  RE: github issue <issue #>
+Body:  "Here are some supporting files for the issue I filed." and include your attachment.
+
+###9) Detailed Logs
+Some bugs will require more detailed logs to help determine the cause. 
+

ISSUE_TEMPLATE.md

@@ -0,0 +1,16 @@
+Please use the following bug reporting template to help produce actionable and reproduceable issues:
+
+* A brief description
+
+* Expected results
+
+* Actual results (with build output window contents if applicable)
+
+* VC++ version, Linux system name and version, GCC/GDB version, CPU arch, etc.
+
+* Steps required to reproduce the error
+
+* Required packages and commands to install
+
+See [our contributing instructions](/CONTRIBUTING.md) for assistance.
+

README.md

@@ -1,2 +1,37 @@
 # VSLinux
-VS extension for C++ Linux development
+Visual C++ for Linux Development
+
+This repo is for the reporting of issues found within and when using Visual C++ for Linux Development.
+
+###Labels
+This is your best ways to interact directly with the Visual C++ for Linux Development team. We will be monitoring and responding to issues as best we can. Please attempt to avoid filing duplicates of open or closed items when possible. In the spirit of openness we will be tagging issues with the following:
+
+- **bug** – We consider this issue to be a bug internally. This tag is generally for bugs in implemented features, or something we consider to be a “bug level” change. Things marked with Bug have a corresponding bug in on Microsoft’s internal bug tracking system.
+  - Example: Adding a library in linker command line get's added in middle of linker command instead of end
+
+- **feature** – Denotes something that is not yet implemented.  
+  - Example:  clang compiler support
+
+- **discussion** – Denotes a discussion on the board that does not relate to a specific feature.
+  - Example: Visual C++ for Linux Development is not open source 
+
+- **fixed** – When possible, we will mark bugs that have been fixed internally.  Unfortunately we cannot say specifically when the bug will hit the insider flights.
+
+- **wontfix** – Denotes an issue we won't be making a fix for.  We will give some reasoning why in resolving, e.g. it could be working by design as see it.  After one week we will either close the issue or mark as Discussion depending on what comes up.
+
+Additional tags may be used to denote specific types of issues. 
+
+###Closing
+Issues may be closed by the original poster at any time.  We will close issues if:
+- One week passes after the change goes out in a new release
+- An issue is clearly a dupe of another.  The duplicate will be linked
+- Any discussion that has clearly run its course
+
+###Important Links
+- Documentation:  https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual-c-for-linux-development/
+- Reases and Release Notes: https://visualstudiogallery.msdn.microsoft.com/725025cf-7067-45c2-8d01-1e0fd359ae6e
+- VC++ Blog: https://blogs.msdn.microsoft.com/wsl
+- Our support email list: [email protected]
+
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 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.
+