From c9dca6e72f70c8ed3c85b5d72f935b1c5d2f9e26 Mon Sep 17 00:00:00 2001 From: "Jens H. Nielsen" Date: Mon, 16 Sep 2024 15:05:17 +0200 Subject: [PATCH] add standard MS open source docs --- CODE_OF_CONDUCT.md | 10 ++++++++++ CONTRIBUTING.rst | 13 +++++++++++++ README.rst | 6 ++++++ SECURITY.md | 41 +++++++++++++++++++++++++++++++++++++++++ 4 files changed, 70 insertions(+) create mode 100644 CODE_OF_CONDUCT.md create mode 100644 SECURITY.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000000..686e5e7a090 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,10 @@ +# Microsoft Open Source Code of Conduct + +This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). + +Resources: + +- [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) +- [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) +- Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns +- Employees can reach out at [aka.ms/opensource/moderation-support](https://aka.ms/opensource/moderation-support) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 60af16ec142..72e55526e8c 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -4,6 +4,19 @@ Contributing Hi, thanks for your interest in the project! We, the development team, welcome all pull requests from developers of any skill level. +This project welcomes contributions and suggestions. Most contributions require you to +agree to a Contributor License Agreement (CLA) declaring that you have the right to, +and actually do, grant us the rights to use your contribution. For details, visit +https://cla.microsoft.com. + +When you submit a pull request, a CLA-bot will automatically determine whether you need +to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the +instructions provided by the bot. You will only need to do this once across all repositories using our CLA. + +This project has adopted the `Microsoft Open Source Code of Conduct `__. +For more information see the `Code of Conduct FAQ `__ +or contact `opencode@microsoft.com `__ with any additional questions or comments. + Who are we? Jens H. Nielsen, William H.P Nielsen, Mikhail Astafev and Trevor Morgan are the current maintainers, or core developers, of QCoDeS. diff --git a/README.rst b/README.rst index e44c927799f..0f24d788a1c 100644 --- a/README.rst +++ b/README.rst @@ -91,7 +91,13 @@ https://github.com/QCoDeS/Qcodes_contrib_drivers See `Contributing `__ for general information about bug/issue reports, contributing code, style, and testing. +Trademarks +========== +This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or +logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks +or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. +Any use of third-party trademarks or logos are subject to those third-party’s policies. License ======= diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 00000000000..82db58aa7c8 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,41 @@ + + +## Security + +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) and [Xamarin](https://github.com/xamarin). + +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/security.md/definition), please report it to us as described below. + +## Reporting Security Issues + +**Please do not report security vulnerabilities through public GitHub issues.** + +Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/security.md/msrc/create-report). + +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/security.md/msrc/pgp). + +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). + +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: + + * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) + * Full paths of source file(s) related to the manifestation of the issue + * The location of the affected source code (tag/branch/commit or direct URL) + * Any special configuration required to reproduce the issue + * Step-by-step instructions to reproduce the issue + * Proof-of-concept or exploit code (if possible) + * Impact of the issue, including how an attacker might exploit the issue + +This information will help us triage your report more quickly. + +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/security.md/msrc/bounty) page for more details about our active programs. + +## Preferred Languages + +We prefer all communications to be in English. + +## Policy + +Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/security.md/cvd). + +