├── CODE_OF_CONDUCT.md ├── LICENSE ├── README.md └── SECURITY.md /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Microsoft Open Source Code of Conduct 2 | 3 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 4 | 5 | Resources: 6 | 7 | - [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) 8 | - [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) 9 | - Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns 10 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) Microsoft Corporation. 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## Visual Studio Code Community Discussions 2 | 3 | Community discussions is the place to discuss VS Code's extension platform, ask questions, help other members of the community, and get answers. 4 | 5 | [👉 Jump into VS Code extension development discussions](https://github.com/microsoft/vscode-discussions/discussions). 6 | 7 | We are scoping discussions to just extension development to learn, experiment, and grow sustainably. 8 | 9 | Other places to participate with VS Code: 10 | 11 | - 🔎 `"Help: Report Issue"` is VS Code's built-in command to 🐛 report bugs, 🐌 performance issues, and 💡 feature requests. 12 | - 🏠 [VS Code repo](https://github.com/microsoft/vscode) for triaging issues and upvoting [feature requests](https://go.microsoft.com/fwlink/?LinkID=533482), and [contributing](https://github.com/microsoft/vscode/wiki/How-to-Contribute). 13 | - 📚 [StackOverflow](https://stackoverflow.com/questions/tagged/vscode) for general VS Code questions. 14 | - 💬 [Extension Dev Slack](https://aka.ms/vscode-dev-community) for chatting with other extension authors. 15 | - 🩻 [Extension API Documentation](https://code.visualstudio.com/api) and [code samples](https://github.com/microsoft/vscode-extension-samples) for learning and contributing documentation improvements. 16 | 17 | 18 | ### We need your participation 19 | 20 | … to create a welcoming and inspiring community. [Microsoft's Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) applies here, in short **please be kind and remember that there are real people on the other side of the keyboard.** 21 | 22 | Also: 23 | 24 | - As we begin to build this community, we ask that you limit conversations to the categories available (more categories will be released as the community grows!) 25 | 26 | - Before opening a new discussion, please search existing posts to see if the topic thread already exists. 27 | 28 | - Please do not use this as a place to `@` your favorite VS Code contributor to get an extra bump on a feature request. Spoiler: it won't work. 29 | 30 | Happy discussing! :) 31 | 32 | ### FAQ 33 | 34 | **How can I help?** 35 | Answer questions with empathy and kindness. Keep the community welcoming by giving contructive feedback and reporting unacceptable behavior. Reach out if you like to help with moderation. 36 | 37 | **Why are there just categories for extension development?** 38 | We want to start small, and the extension author community is just the right size. Meanwhile [StackOverflow](https://stackoverflow.com/questions/tagged/visual-studio-code?tab=Newest) continues to serve most other questions. 39 | 40 | **When will more categories be added?** 41 | As we learn what works well, tweak our moderation process, and see the community grow before expanding topics. If we see moderation becoming a burden on the team we will also consider take action. 42 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Security 4 | 5 | Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). 6 | 7 | If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below. 8 | 9 | ## Reporting Security Issues 10 | 11 | **Please do not report security vulnerabilities through public GitHub issues.** 12 | 13 | Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report). 14 | 15 | If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey). 16 | 17 | You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 18 | 19 | Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: 20 | 21 | * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) 22 | * Full paths of source file(s) related to the manifestation of the issue 23 | * The location of the affected source code (tag/branch/commit or direct URL) 24 | * Any special configuration required to reproduce the issue 25 | * Step-by-step instructions to reproduce the issue 26 | * Proof-of-concept or exploit code (if possible) 27 | * Impact of the issue, including how an attacker might exploit the issue 28 | 29 | This information will help us triage your report more quickly. 30 | 31 | If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs. 32 | 33 | ## Preferred Languages 34 | 35 | We prefer all communications to be in English. 36 | 37 | ## Policy 38 | 39 | Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd). 40 | 41 | 42 | --------------------------------------------------------------------------------