You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When contributing to this repository, please first discuss the change you wish to make via issue,
4
-
email, or any other method with the owners of this repository before making a change.
3
+
When contributing to this repository, please first discuss the change you wish
4
+
to make via issue, email, or any other method with the owners of this repository before making a change.
5
5
6
-
Please note we have a code of conduct, please follow it in all your interactions with the project.
6
+
Do note that this project has a code of conduct; please be sure to follow it
7
+
in all of your project interactions.
7
8
8
9
## Pull Request Process
9
10
10
-
1. Ensure any install or build dependencies are removed before the end of the layer when doing a
11
-
build.
12
-
2. Update the README.md with details of changes to the interface, this includes new environment
13
-
variables, exposed ports, useful file locations and container parameters.
14
-
3. Increase the version numbers in any examples files and the README.md to the new version that this
15
-
Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
16
-
4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
17
-
do not have permission to do that, you may request the second reviewer to merge it for you.
11
+
1. Ensure any install or build artifacts are removed before the end of
12
+
the layer when doing a build
13
+
2. Update the README.md or README_VAGRANT.md with details of changes to the
14
+
interface, this includes new environment variables, exposed ports, useful
15
+
file locations and container parameters
16
+
3. Increase the version numbers in any examples files and the README.md
17
+
to the new version that this Pull Request would represent. The versioning scheme we use is (mostly) [SemVer](http://semver.org/)
18
+
4. You may merge the Pull Request in once you have the sign-off of two other
19
+
project contributors, or if you do not have permission to do that, you can
20
+
request the second reviewer to merge it for you
18
21
19
22
## Code of Conduct
20
23
21
24
### Our Pledge
22
25
23
26
In the interest of fostering an open and welcoming environment, we as
24
-
contributors and maintainers pledge to making participation in our project and
25
-
our community a harassment-free experience for everyone, regardless of age, body
26
-
size, disability, ethnicity, gender identity and expression, level of experience,
27
-
nationality, personal appearance, race, religion, or sexual identity and
28
-
orientation.
27
+
contributors and maintainers pledge to making participation in our project
28
+
and our community a harassment-free experience for everyone, regardless of age,
29
+
body size, disability, ethnicity, gender identity and expression, level of
30
+
experience, nationality, personal appearance, race, religion, or sexual
31
+
identity and orientation.
29
32
30
33
### Our Standards
31
34
32
35
Examples of behavior that contributes to creating a positive environment
33
36
include:
34
37
38
+
* Showing empathy towards other community members
35
39
* Using welcoming and inclusive language
36
40
* Being respectful of differing viewpoints and experiences
37
41
* Gracefully accepting constructive criticism
38
42
* Focusing on what is best for the community
39
-
* Showing empathy towards other community members
40
43
41
44
Examples of unacceptable behavior by participants include:
42
45
43
-
*The use of sexualized language or imagery and unwelcome sexual attention or
44
-
advances
45
-
*Trolling, insulting/derogatory comments, and personal or political attacks
46
+
*Use of sexualized language or imagery and unwelcome sexual attention
47
+
or advances
48
+
*Insulting/derogatory comments, and personal or political attacks
46
49
* Public or private harassment
47
50
* Publishing others' private information, such as a physical or electronic
48
51
address, without explicit permission
@@ -66,27 +69,28 @@ threatening, offensive, or harmful.
66
69
This Code of Conduct applies both within project spaces and in public spaces
67
70
when an individual is representing the project or its community. Examples of
68
71
representing a project or community include using an official project e-mail
69
-
address, posting via an official social media account, or acting as an appointed
70
-
representative at an online or offline event. Representation of a project may be
71
-
further defined and clarified by project maintainers.
72
+
address, posting via an official social media account, or acting as an
73
+
appointed representative at an online or offline event. Representation of a
74
+
project may be further defined and clarified by project maintainers.
72
75
73
76
### Enforcement
74
77
75
78
Instances of abusive, harassing, or otherwise unacceptable behavior may be
76
-
reported by contacting the project leadership: brian [at] brianshumate [dot] com. All
77
-
complaints will be reviewed and investigated and will result in a response that
78
-
is deemed necessary and appropriate to the circumstances. The project team is
79
-
obligated to maintain confidentiality with regard to the reporter of an incident.
80
-
Further details of specific enforcement policies may be posted separately.
79
+
reported by contacting the project leadership: brian <at> brianshumate <dot> com.
80
+
81
+
All complaints will be reviewed and investigated and will result in a response
82
+
that is deemed necessary and appropriate to the circumstances. The project
83
+
team is obligated to maintain confidentiality with regard to the reporter of
84
+
an incident. Further details of specific enforcement policies may be posted
85
+
separately.
81
86
82
87
Project maintainers who do not follow or enforce the Code of Conduct in good
83
88
faith may face temporary or permanent repercussions as determined by other
84
89
members of the project's leadership.
85
90
86
91
### Attribution
87
92
88
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
89
-
available at [http://contributor-covenant.org/version/1/4][version]
93
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
0 commit comments