From 98082e31700462d9e565161c4fc7a1f64fa484dd Mon Sep 17 00:00:00 2001 From: Eilon Lipton Date: Tue, 13 May 2014 00:39:08 -0700 Subject: [PATCH] Create CONTRIBUTING.md --- CONTRIBUTING.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000000..d889e97feb --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,23 @@ +## Filing issues + +The GitHub issue list is for bugs, not discussions. If you have a question you want to ask you have many alternatives: +- [Stackoverflow](http://stackoverflow.com/questions/tagged/asp.net-vnext) +- [The JabbR chat room](https://jabbr.net/#/rooms/aspnetvnext) + +When filing issues, please use our [bug filing templates](https://github.com/aspnet/Home/wiki/Functional-bug-template). +The best way to get your bug fixed is to be as detailed as you can be about the problem. +Providing a minimal project with steps to reproduce the problem is ideal. +Here are questions you can answer before you file a bug to make sure you're not missing any important information. + +1. Did you read the [documentation](https://github.com/aspnet/home/wiki)? +2. Did you include the snippet of broken code in the issue? +3. What are the *EXACT* steps to reproduce this problem? +4. What package versions are you using (you can see these in the `project.json` file)? +5. What operating system are you using? +6. What version of IIS are you using? + +GitHub supports [markdown](http://github.github.com/github-flavored-markdown/), so when filing bugs make sure you check the formatting before clicking submit. + +## Contributing code + +We are actively working to allow community code contributions. We can't accept code contributions yet, but check back soon for updates.