@@ -20,80 +20,5 @@ Please note we have a code of conduct, please follow it in all your interactions
2020 variables, exposed ports, useful file locations and container parameters.
21216 . Increase the version numbers in any examples files and the README.md to the new version that this
2222 Pull Request would represent. The versioning scheme we use is [ SemVer] ( http://semver.org/ ) .
23- 7 . You may merge the Pull Request in once you have the sign-off of two other developers, or if you
24- do not have permission to do that, you may request the second reviewer to merge it for you.
25-
26- ## Code of Conduct
27-
28- ### Our Pledge
29-
30- In the interest of fostering an open and welcoming environment, we as
31- contributors and maintainers pledge to making participation in our project and
32- our community a harassment-free experience for everyone, regardless of age, body
33- size, disability, ethnicity, gender identity and expression, level of experience,
34- nationality, personal appearance, race, religion, or sexual identity and
35- orientation.
36-
37- ### Our Standards
38-
39- Examples of behavior that contributes to creating a positive environment
40- include:
41-
42- * Using welcoming and inclusive language
43- * Being respectful of differing viewpoints and experiences
44- * Gracefully accepting constructive criticism
45- * Focusing on what is best for the community
46- * Showing empathy towards other community members
47-
48- Examples of unacceptable behavior by participants include:
49-
50- * The use of sexualized language or imagery and unwelcome sexual attention or
51- advances
52- * Trolling, insulting/derogatory comments, and personal or political attacks
53- * Public or private harassment
54- * Publishing others' private information, such as a physical or electronic
55- address, without explicit permission
56- * Other conduct which could reasonably be considered inappropriate in a
57- professional setting
58-
59- ### Our Responsibilities
60-
61- Project maintainers are responsible for clarifying the standards of acceptable
62- behavior and are expected to take appropriate and fair corrective action in
63- response to any instances of unacceptable behavior.
64-
65- Project maintainers have the right and responsibility to remove, edit, or
66- reject comments, commits, code, wiki edits, issues, and other contributions
67- that are not aligned to this Code of Conduct, or to ban temporarily or
68- permanently any contributor for other behaviors that they deem inappropriate,
69- threatening, offensive, or harmful.
70-
71- ### Scope
72-
73- This Code of Conduct applies both within project spaces and in public spaces
74- when an individual is representing the project or its community. Examples of
75- representing a project or community include using an official project e-mail
76- address, posting via an official social media account, or acting as an appointed
77- representative at an online or offline event. Representation of a project may be
78- further defined and clarified by project maintainers.
79-
80- ### Enforcement
81-
82- Instances of abusive, harassing, or otherwise unacceptable behavior may be
83- reported by contacting the project team at [ INSERT EMAIL ADDRESS] . All
84- complaints will be reviewed and investigated and will result in a response that
85- is deemed necessary and appropriate to the circumstances. The project team is
86- obligated to maintain confidentiality with regard to the reporter of an incident.
87- Further details of specific enforcement policies may be posted separately.
88-
89- Project maintainers who do not follow or enforce the Code of Conduct in good
90- faith may face temporary or permanent repercussions as determined by other
91- members of the project's leadership.
92-
93- ### Attribution
94-
95- This Code of Conduct is adapted from the [ Contributor Covenant] [ homepage ] , version 1.4,
96- available at [ http://contributor-covenant.org/version/1/4 ] [ version ]
97-
98- [ homepage ] : http://contributor-covenant.org
99- [ version ] : http://contributor-covenant.org/version/1/4/
23+ 7 . You may merge the Pull Request in once you have the sign-off of one other developer. If you
24+ do not have permission to do that, you may request reviewer to merge it for you.
0 commit comments