-
Notifications
You must be signed in to change notification settings - Fork 385
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Showing
1 changed file
with
9 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,31 +9,31 @@ | |
| </ul> | ||
| - question: Why this Code of Conduct? | ||
| answer: The Microsoft Open Source Code of Conduct is an instantiation of the <a href="https://www.contributor-covenant.org/version/2/0/code_of_conduct/">Contributor's Covenant 2.0</a>, that captures the Microsoft culture of equality, respect and inclusion. By leveraging this template, which is used by many <a href="https://www.contributor-covenant.org/adopters/">open source projects</a>, we acknowledge both the opportunity gained by leveraging a community-based effort for inclusion, and responsibility to contribute to its evolution. | ||
| answer: The Microsoft Open Source Code of Conduct is an instantiation of the <a class="link-standard" href="https://www.contributor-covenant.org/version/2/0/code_of_conduct/">Contributor's Covenant 2.0</a>, that captures the Microsoft culture of equality, respect and inclusion. By leveraging this template, which is used by many <a class="link-standard" href="https://www.contributor-covenant.org/adopters/">open source projects</a>, we acknowledge both the opportunity gained by leveraging a community-based effort for inclusion, and responsibility to contribute to its evolution. | ||
|
|
||
|
|
||
| - question: Why do this across all repos? | ||
| answer: Having one code and process is both efficient and consistent — community members can participate in any Microsoft-driven project and be confident that they know the norms and that they are supported by a robust process. | ||
|
|
||
| - question: How does a project adopt the code and process? | ||
| answer: | | ||
| <p>All Microsoft projects are automatically covered by the Code of Conduct and the Issue Resolution Process. However, it is critical that everyone in the communities be aware of the code and process. For that reason, all projects must link to the Code of Conduct. Please refer to this <a href="https://github.com/microsoft/repo-templates/blob/main/shared/CODE_OF_CONDUCT.md">repository standard</a> for the current CODE_OF_CONDUCT.md version.</p> | ||
| <p>All Microsoft projects are automatically covered by the Code of Conduct and the Issue Resolution Process. However, it is critical that everyone in the communities be aware of the code and process. For that reason, all projects must link to the Code of Conduct. Please refer to this <a class="link-standard" href="https://github.com/microsoft/repo-templates/blob/main/shared/CODE_OF_CONDUCT.md">repository standard</a> for the current CODE_OF_CONDUCT.md version.</p> | ||
| - question: What if my Microsoft project already has a Code of Conduct? | ||
| answer: | | ||
| <p>Thanks for being proactive in this important area. You are welcome to continue using your existing Code of Conduct, or you may change to the <a href="https://opensource.microsoft.com/codeofconduct/">Microsoft Open Source Code of Conduct</a>. Either way, all Microsoft projects must use the same issue resolution process. Please ensure that your documentation and guidance is updated to point people at the process outlined in this FAQ (see below).</p> | ||
| <p>Projects in the .NET Foundation are already covered by the <a href="https://www.dotnetfoundation.org/code-of-conduct">.NET Foundation Contributors Code of Conduct</a>. As such, there is no need for .NET Foundation projects to make any changes.</p> | ||
| <p>Thanks for being proactive in this important area. You are welcome to continue using your existing Code of Conduct, or you may change to the <a class="link-standard" href="https://opensource.microsoft.com/codeofconduct/">Microsoft Open Source Code of Conduct</a>. Either way, all Microsoft projects must use the same issue resolution process. Please ensure that your documentation and guidance is updated to point people at the process outlined in this FAQ (see below).</p> | ||
| <p>Projects in the .NET Foundation are already covered by the <a class="link-standard" href="https://www.dotnetfoundation.org/code-of-conduct">.NET Foundation Contributors Code of Conduct</a>. As such, there is no need for .NET Foundation projects to make any changes.</p> | ||
| - question: How do I raise a concern? | ||
| answer: | | ||
| <p>If you have witnessed or been subjected to a violation of the Code of Conduct, please send an email to <a href="mailto:[email protected]">[email protected]</a>. Your message will be handled in a secure and confidential manner. This email address is monitored by the Open Source Program's Office, who are not directly active in open source projects or communities — so you can be sure that you are not communicating with a person involved in the issue you are reporting.</p> | ||
| <p>If you have witnessed or been subjected to a violation of the Code of Conduct, please send an email to <a class="link-standard" href="mailto:[email protected]">[email protected]</a>. Your message will be handled in a secure and confidential manner. This email address is monitored by the Open Source Program's Office, who are not directly active in open source projects or communities — so you can be sure that you are not communicating with a person involved in the issue you are reporting.</p> | ||
| <p> You will receive a response within one business day acknowledging receipt of your email and describing the process for its resolution. (See below for more details.)</p> | ||
| <p>NOTE: this process is not appropriate for reporting spamming. Please reach out to <a href="https://support.github.com/contact">GitHub Support</a> for these issues.</p> | ||
| <p>NOTE: this process is not appropriate for reporting spamming. Please reach out to <a class="link-standard" href="https://support.github.com/contact">GitHub Support</a> for these issues.</p> | ||
| - question: What is the process for addressing issues that arise? | ||
| answer: | | ||
| <p>Emails sent to <a href="mailto:[email protected]">[email protected]</a> or reported directly to a member of the OSPO team, kick off the following process:</p> | ||
| <p>Emails sent to <a class="link-standard" href="mailto:[email protected]">[email protected]</a> or reported directly to a member of the OSPO team, kick off the following process:</p> | ||
| <ol> | ||
| <li><span>Your message will be acknowledged within one business day.</span></li> | ||
| <li><span>Within the following business day a small, (2-3) person team will be assembled from a pool of Microsoft employee volunteers to review your concern. This team will be as diverse as possible given its size and will pull in additional people as needed to gain further insight and provide guidance. The team will not include anyone directly involved in the issue that has been raised.</span></li> | ||
|
|
@@ -43,8 +43,8 @@ | |
| <div class="pre"> | ||
| <div> | ||
| <p>Step 1: Issue Reported</p> | ||
| <p><span class="org">Reporter</span> reports directly to a member of the OSPO team or via email to <a href="mailto:[email protected]">[email protected]</a></p> | ||
| <small>Email address is published with Code of Conduct, linked from every Microsoft Open Source project’s repo.</small> | ||
| <p><span class="org">Reporter</span> reports directly to a member of the OSPO team or via email to <a class="link-standard" href="mailto:[email protected]">[email protected]</a></p> | ||
| <small>Email address is published with Code of Conduct, linked from every Microsoft Open Source project's repo.</small> | ||
| <hr> | ||
| </div> | ||
| <div> | ||
|
|
||