@@ -14,7 +14,7 @@ The following is a set of guidelines for contributing to the NGINX AWS Auto-Scal
1414 * [ Git Style Guide] ( #git-style-guide )
1515 * [ Go Style Guide] ( #go-style-guide )
1616
17- [ Code of Conduct] ( #code-of-conduct )
17+ [ Code of Conduct] ( https://github.com/nginxinc/nginx-asg-sync/blob/master/CODE_OF_CONDUCT.md )
1818
1919## Ask a Question
2020
@@ -67,79 +67,3 @@ Note: if you’d like to implement a new feature, please consider creating a fea
6767* Run ` gofmt ` over your code to automatically resolve a lot of style issues. Most editors support this running automatically when saving a code file.
6868* Run ` go lint ` and ` go vet ` on your code too to catch any other issues.
6969* Follow this guide on some good practice and idioms for Go - https://github.com/golang/go/wiki/CodeReviewComments
70-
71- ## Code of Conduct
72-
73- This project and everyone participating in it is governed by this code.
74-
75- ### Our Pledge
76-
77- In the interest of fostering an open and welcoming environment, we as
78- contributors and maintainers pledge to making participation in our project and
79- our community a harassment-free experience for everyone, regardless of age, body
80- size, disability, ethnicity, sex characteristics, gender identity and expression,
81- level of experience, education, socio-economic status, nationality, personal
82- appearance, race, religion, or sexual identity and orientation.
83-
84- ### Our Standards
85-
86- Examples of behavior that contributes to creating a positive environment
87- include:
88-
89- * Using welcoming and inclusive language
90- * Being respectful of differing viewpoints and experiences
91- * Gracefully accepting constructive criticism
92- * Focusing on what is best for the community
93- * Showing empathy towards other community members
94-
95- Examples of unacceptable behavior by participants include:
96-
97- * The use of sexualized language or imagery and unwelcome sexual attention or
98- advances
99- * Trolling, insulting/derogatory comments, and personal or political attacks
100- * Public or private harassment
101- * Publishing others' private information, such as a physical or electronic
102- address, without explicit permission
103- * Other conduct which could reasonably be considered inappropriate in a
104- professional setting
105-
106- ### Our Responsibilities
107-
108- Project maintainers are responsible for clarifying the standards of acceptable
109- behavior and are expected to take appropriate and fair corrective action in
110- response to any instances of unacceptable behavior.
111-
112- Project maintainers have the right and responsibility to remove, edit, or
113- reject comments, commits, code, wiki edits, issues, and other contributions
114- that are not aligned to this Code of Conduct, or to ban temporarily or
115- permanently any contributor for other behaviors that they deem inappropriate,
116- threatening, offensive, or harmful.
117-
118- ### Scope
119-
120- This Code of Conduct applies both within project spaces and in public spaces
121- when an individual is representing the project or its community. Examples of
122- representing a project or community include using an official project e-mail
123- address, posting via an official social media account, or acting as an appointed
124- representative at an online or offline event. Representation of a project may be
125- further defined and clarified by project maintainers.
126-
127- ### Enforcement
128-
129- Instances of abusive, harassing, or otherwise unacceptable behavior may be
130- reported by contacting the project team at [ mailto:nginx@nginx.org ] . All
131- complaints will be reviewed and investigated and will result in a response that
132- is deemed necessary and appropriate to the circumstances. The project team is
133- obligated to maintain confidentiality with regard to the reporter of an incident.
134- Further details of specific enforcement policies may be posted separately.
135-
136- Project maintainers who do not follow or enforce the Code of Conduct in good
137- faith may face temporary or permanent repercussions as determined by other
138- members of the project's leadership.
139-
140- ### Attribution
141-
142- This Code of Conduct is adapted from the [ Contributor Covenant] [ homepage ] , version 1.4,
143- available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
144-
145- [ homepage ] : https://www.contributor-covenant.org
0 commit comments