-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[DO NOT MERGE] Add Required OSC Information (#110)
* OSC updates * Add license info to source files * Fix trailing newlines * Update CONTRIBUTING.md Co-authored-by: Severin Neumann <[email protected]> * Update CONTRIBUTING.md Co-authored-by: Severin Neumann <[email protected]> * Update CONTRIBUTING.md Co-authored-by: Severin Neumann <[email protected]> * Update CONTRIBUTING.md Co-authored-by: Severin Neumann <[email protected]> * Update SECURITY.md Co-authored-by: Severin Neumann <[email protected]> * Update SECURITY.md Co-authored-by: Severin Neumann <[email protected]> --------- Co-authored-by: Severin Neumann <[email protected]>
- Loading branch information
Showing
141 changed files
with
3,105 additions
and
77 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 |
---|---|---|
@@ -0,0 +1,132 @@ | ||
# Contributor Covenant Code of Conduct | ||
|
||
## Our Pledge | ||
|
||
We as members, contributors, and leaders pledge to make participation in our | ||
community a harassment-free experience for everyone, regardless of age, body | ||
size, visible or invisible disability, ethnicity, sex characteristics, gender | ||
identity and expression, level of experience, education, socio-economic status, | ||
nationality, personal appearance, race, caste, color, religion, or sexual identity | ||
and orientation. | ||
|
||
We pledge to act and interact in ways that contribute to an open, welcoming, | ||
diverse, inclusive, and healthy community. | ||
|
||
## Our Standards | ||
|
||
Examples of behavior that contributes to a positive environment for our | ||
community include: | ||
|
||
* Demonstrating empathy and kindness toward other people | ||
* Being respectful of differing opinions, viewpoints, and experiences | ||
* Giving and gracefully accepting constructive feedback | ||
* Accepting responsibility and apologizing to those affected by our mistakes, | ||
and learning from the experience | ||
* Focusing on what is best not just for us as individuals, but for the | ||
overall community | ||
|
||
Examples of unacceptable behavior include: | ||
|
||
* The use of sexualized language or imagery, and sexual attention or | ||
advances of any kind | ||
* Trolling, insulting or derogatory comments, and personal or political attacks | ||
* Public or private harassment | ||
* Publishing others' private information, such as a physical or email | ||
address, without their explicit permission | ||
* Other conduct which could reasonably be considered inappropriate in a | ||
professional setting | ||
|
||
## Enforcement Responsibilities | ||
|
||
Community leaders are responsible for clarifying and enforcing our standards of | ||
acceptable behavior and will take appropriate and fair corrective action in | ||
response to any behavior that they deem inappropriate, threatening, offensive, | ||
or harmful. | ||
|
||
Community leaders have the right and responsibility to remove, edit, or reject | ||
comments, commits, code, wiki edits, issues, and other contributions that are | ||
not aligned to this Code of Conduct, and will communicate reasons for moderation | ||
decisions when appropriate. | ||
|
||
## Scope | ||
|
||
This Code of Conduct applies within all community spaces, and also applies when | ||
an individual is officially representing the community in public spaces. | ||
Examples of representing our community include using an official email address, | ||
posting via an official social media account, or acting as an appointed | ||
representative at an online or offline event. | ||
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported to the community leaders responsible for enforcement at | ||
*<[email protected]>*. | ||
All complaints will be reviewed and investigated promptly and fairly. | ||
|
||
All community leaders are obligated to respect the privacy and security of the | ||
reporter of any incident. | ||
|
||
## Enforcement Guidelines | ||
|
||
Community leaders will follow these Community Impact Guidelines in determining | ||
the consequences for any action they deem in violation of this Code of Conduct: | ||
|
||
### 1. Correction | ||
|
||
**Community Impact**: Use of inappropriate language or other behavior deemed | ||
unprofessional or unwelcome in the community. | ||
|
||
**Consequence**: A private, written warning from community leaders, providing | ||
clarity around the nature of the violation and an explanation of why the | ||
behavior was inappropriate. A public apology may be requested. | ||
|
||
### 2. Warning | ||
|
||
**Community Impact**: A violation through a single incident or series | ||
of actions. | ||
|
||
**Consequence**: A warning with consequences for continued behavior. No | ||
interaction with the people involved, including unsolicited interaction with | ||
those enforcing the Code of Conduct, for a specified period of time. This | ||
includes avoiding interactions in community spaces as well as external channels | ||
like social media. Violating these terms may lead to a temporary or | ||
permanent ban. | ||
|
||
### 3. Temporary Ban | ||
|
||
**Community Impact**: A serious violation of community standards, including | ||
sustained inappropriate behavior. | ||
|
||
**Consequence**: A temporary ban from any sort of interaction or public | ||
communication with the community for a specified period of time. No public or | ||
private interaction with the people involved, including unsolicited interaction | ||
with those enforcing the Code of Conduct, is allowed during this period. | ||
Violating these terms may lead to a permanent ban. | ||
|
||
### 4. Permanent Ban | ||
|
||
**Community Impact**: Demonstrating a pattern of violation of community | ||
standards, including sustained inappropriate behavior, harassment of an | ||
individual, or aggression toward or disparagement of classes of individuals. | ||
|
||
**Consequence**: A permanent ban from any sort of public interaction within | ||
the community. | ||
|
||
## Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], | ||
version 2.1, available at | ||
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. | ||
|
||
Community Impact Guidelines were inspired by | ||
[Mozilla's code of conduct enforcement ladder][Mozilla CoC]. | ||
|
||
For answers to common questions about this code of conduct, see the FAQ at | ||
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available | ||
at [https://www.contributor-covenant.org/translations][translations]. | ||
|
||
[homepage]: https://www.contributor-covenant.org | ||
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html | ||
[Mozilla CoC]: https://github.com/mozilla/diversity | ||
[FAQ]: https://www.contributor-covenant.org/faq | ||
[translations]: https://www.contributor-covenant.org/translations |
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 |
---|---|---|
@@ -0,0 +1,47 @@ | ||
# How to Contribute | ||
|
||
Thanks for your interest in contributing to `ansible-dc-vxlan`! Here are a few general guidelines on contributing and | ||
reporting bugs that we ask you to review. Following these guidelines helps to communicate that you respect the time of | ||
the contributors managing and developing this open source project. In return, they should reciprocate that respect in | ||
addressing your issue, assessing changes, and helping you finalize your pull requests. In that spirit of mutual respect, | ||
we endeavor to review incoming issues and pull requests within 10 days, and will close any lingering issues or pull | ||
requests after 60 days of inactivity. | ||
|
||
Please note that all of your interactions in the project are subject to our [Code of Conduct](/CODE_OF_CONDUCT.md). This | ||
includes creation of issues or pull requests, commenting on issues or pull requests, and extends to all interactions in | ||
any real-time space e.g., Slack, Discord, etc. | ||
|
||
## Reporting Issues | ||
|
||
Before reporting a new issue, please ensure that the issue was not already reported or fixed by searching through our | ||
[issues list](https://github.com/netascode/ansible-dc-vxlan/issues). | ||
|
||
When creating a new issue, please be sure to include a **title and clear description**, as much relevant information as | ||
possible, and, if possible, a test case. | ||
|
||
**If you discover a security bug, please do not report it through GitHub. Instead, please see security procedures in | ||
[SECURITY.md](/SECURITY.md).** | ||
|
||
## Sending Pull Requests | ||
|
||
Before sending a new pull request, take a look at existing pull requests and issues to see if the proposed change or fix | ||
has been discussed in the past, or if the change was already implemented but not yet released. | ||
|
||
We expect new pull requests to include tests for any affected behavior, and, as we follow semantic versioning, we may | ||
reserve breaking changes until the next major version release. | ||
|
||
## Other Ways to Contribute | ||
|
||
We welcome anyone that wants to contribute to `ansible-dc-vxlan` to triage and reply to open issues to help troubleshoot | ||
and fix existing bugs. Here is what you can do: | ||
|
||
- Help ensure that existing issues follows the recommendations from the _[Reporting Issues](#reporting-issues)_ section, | ||
providing feedback to the issue's author on what might be missing. | ||
<!-- - Review and update the existing content of our [Wiki](https://github.com/org_name/repo_name/wiki) with up-to-date | ||
instructions and code samples. --> | ||
- Review existing pull requests, and testing patches against real existing applications that use `ansible-dc-vxlan`. | ||
- Write a test, or add a missing test case to an existing test. | ||
|
||
Thanks again for your interest on contributing to `ansible-dc-vxlan`! | ||
|
||
:heart: |
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 |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# Security Policies and Procedures | ||
|
||
This document outlines security procedures and general policies for the | ||
`ansible-dc-vxlan` project. | ||
|
||
- [Reporting a Bug](#reporting-a-bug) | ||
- [Disclosure Policy](#disclosure-policy) | ||
- [Comments on this Policy](#comments-on-this-policy) | ||
|
||
## Reporting a Bug | ||
|
||
The `ansible-dc-vxlan` team and community take all security bugs in | ||
`ansible-dc-vxlan` seriously. Thank you for improving the security of | ||
`ansible-dc-vxlan`. We appreciate your efforts and responsible disclosure and | ||
will make every effort to acknowledge your contributions. | ||
|
||
Report security bugs by emailing `[email protected]`. | ||
|
||
The lead maintainer will acknowledge your email within 48 hours, and will send a | ||
more detailed response within 48 hours indicating the next steps in handling | ||
your report. After the initial reply to your report, the security team will | ||
endeavor to keep you informed of the progress towards a fix and full | ||
announcement, and may ask for additional information or guidance. | ||
|
||
## Disclosure Policy | ||
|
||
When the security team receives a security bug report, they will assign it to a | ||
primary handler. This person will coordinate the fix and release process, | ||
involving the following steps: | ||
|
||
- Confirm the problem and determine the affected versions. | ||
- Audit code to find any potential similar problems. | ||
- Prepare fixes for all releases still under maintenance. These fixes will be | ||
released as quickly as possible. | ||
|
||
## Comments on this Policy | ||
|
||
If you have suggestions on how this process could be improved please submit a | ||
pull request. |
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
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
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
21 changes: 21 additions & 0 deletions
21
plugins/action/common/prepare_plugins/001_prep_list_defaults.py
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
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
21 changes: 21 additions & 0 deletions
21
plugins/action/common/prepare_plugins/103_prep_topology_switches.py
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
21 changes: 21 additions & 0 deletions
21
plugins/action/common/prepare_plugins/104_prep_fabric_overlay_services.py
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
Oops, something went wrong.