├── CODE_OF_CONDUCT.md ├── LICENSE ├── README.md ├── SECURITY.md └── SUPPORT.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 | # Microsoft Build 2022 - AI examples 2 | This repository contains AI examples that aim to grow the understanding of using Microsoft AI toolsets in applications by providing samples of implementation and references to support the Microsoft Build conference in 2022. 3 | 4 | | Project | Description | 5 | | :-- | :-- | 6 | | [Codex for Minecraft Non-Player Characters](https://github.com/microsoft/MinecraftCodex) | Use Codex to generate code to power a non-player character (NPC) in Minecraft and accomplish a variety of in-game tasks. | 7 | | [Codex Command Line Interface](https://github.com/microsoft/Codex-CLI) | Use Codex to convert natural language into commands in Bash, Z shell (zsh) and PowerShell. | 8 | | [Codex Babylon](https://github.com/microsoft/Codex-Babylon) | Use natural language to create and manipulate 3D objects in Babylon.js, from simple primitives to complex scenes. | 9 | | [Azure Search - Query Classification](https://github.com/microsoft/azure-search-query-classification/) | Leveraging large language models (LLMs) to enable semantic understanding with Azure Cognitive Search that improves the search experience. | 10 | | [ML.NET on Excel](https://github.com/microsoft/MLNETExcel) | Bring your own ML.NET model to Excel. | 11 | | [Turtlebot3 Simulator with Bonsai](https://github.com/microsoft/ROS-bonsai-connector/blob/main/samples/turtlebot3_bonsai/README.md) | Train reinforcement learning policies for Turtlebot3 using Microsoft Bonsai. | 12 | | [ONNX Runtime with Unreal Engine 5](https://github.com/microsoft/OnnxRuntime-UnrealEngine5-StyleTransfer-NNI-Plugin) | Apply style transfer models in Unreal Engine 5 via the ONNX Neural Network Inference (NNI) plugin powered by ONNX Runtime. | 13 | | [Papiro Document Intelligence](https://github.com/azure-samples/papiro) | A conference intelligence application that uses intelligence APIs to showcase what might be done to support conferences with AI. | 14 | | [locutus GPT-2 Text Generation](https://github.com/Azure-Samples/locutus) | Demonstrate an end-to-end process within Azure Machine Learning to deploy the GPT-2 model from Hugging Face and fine-tuned it on the writings of Homer. | 15 | 16 | ## Statement of Purpose 17 | This project is not intended to be the forum on discussing Microsoft products nor requesting new features. 18 | 19 | ## Reference 20 | * [How to build Codex solutions (Microsoft Build 2022 on-demand session)](https://mybuild.microsoft.com/en-US/sessions/cfa6ef6a-1f0d-45cf-bb8c-1209bdcc232e?source=/favorites) 21 | * [How to get Codex to produce the code you want](https://aka.ms/oai/prompt-engineering) 22 | 23 | ## Contributing 24 | 25 | This project welcomes contributions and suggestions. Most contributions require you to agree to a 26 | Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us 27 | the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com. 28 | 29 | When you submit a pull request, a CLA bot will automatically determine whether you need to provide 30 | a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions 31 | provided by the bot. You will only need to do this once across all repos using our CLA. 32 | 33 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 34 | For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or 35 | contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 36 | 37 | ## Trademarks 38 | 39 | This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft 40 | trademarks or logos is subject to and must follow 41 | [Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/legal/intellectualproperty/trademarks/usage/general). 42 | Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. 43 | Any use of third-party trademarks or logos are subject to those third-party's policies. 44 | -------------------------------------------------------------------------------- /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://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)), 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://msrc.microsoft.com/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://www.microsoft.com/en-us/msrc/pgp-key-msrc). 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://www.microsoft.com/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://microsoft.com/msrc/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://www.microsoft.com/en-us/msrc/cvd). 40 | 41 | -------------------------------------------------------------------------------- /SUPPORT.md: -------------------------------------------------------------------------------- 1 | # TODO: The maintainer of this repo has not yet edited this file 2 | 3 | **REPO OWNER**: Do you want Customer Service & Support (CSS) support for this product/project? 4 | 5 | - **No CSS support:** Fill out this template with information about how to file issues and get help. 6 | - **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. 7 | - **Not sure?** Fill out an intake as though the answer were "Yes". CSS will help you decide. 8 | 9 | *Then remove this first heading from this SUPPORT.MD file before publishing your repo.* 10 | 11 | # Support 12 | 13 | ## How to file issues and get help 14 | 15 | This project uses GitHub Issues to track bugs and feature requests. Please search the existing 16 | issues before filing new issues to avoid duplicates. For new issues, file your bug or 17 | feature request as a new Issue. 18 | 19 | For help and questions about using this project, please **REPO MAINTAINER: INSERT INSTRUCTIONS HERE 20 | FOR HOW TO ENGAGE REPO OWNERS OR COMMUNITY FOR HELP. COULD BE A STACK OVERFLOW TAG OR OTHER 21 | CHANNEL. WHERE WILL YOU HELP PEOPLE?**. 22 | 23 | ## Microsoft Support Policy 24 | 25 | Support for this **PROJECT or PRODUCT** is limited to the resources listed above. 26 | --------------------------------------------------------------------------------