Skip to content

Commit c839ab8

Browse files
MonolithProjectsMonolithProjects
committed
Community standards improvement
1 parent 3e0892b commit c839ab8

File tree

9 files changed

+322
-9
lines changed

9 files changed

+322
-9
lines changed

‎.github/CODE_OF_CONDUCT.md

Lines changed: 133 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,133 @@
1+
2+
# Contributor Covenant Code of Conduct
3+
4+
## Our Pledge
5+
6+
We as members, contributors, and leaders pledge to make participation in our
7+
community a harassment-free experience for everyone, regardless of age, body
8+
size, visible or invisible disability, ethnicity, sex characteristics, gender
9+
identity and expression, level of experience, education, socio-economic status,
10+
nationality, personal appearance, race, caste, color, religion, or sexual
11+
identity and orientation.
12+
13+
We pledge to act and interact in ways that contribute to an open, welcoming,
14+
diverse, inclusive, and healthy community.
15+
16+
## Our Standards
17+
18+
Examples of behavior that contributes to a positive environment for our
19+
community include:
20+
21+
* Demonstrating empathy and kindness toward other people
22+
* Being respectful of differing opinions, viewpoints, and experiences
23+
* Giving and gracefully accepting constructive feedback
24+
* Accepting responsibility and apologizing to those affected by our mistakes,
25+
and learning from the experience
26+
* Focusing on what is best not just for us as individuals, but for the overall
27+
community
28+
29+
Examples of unacceptable behavior include:
30+
31+
* The use of sexualized language or imagery, and sexual attention or advances of
32+
any kind
33+
* Trolling, insulting or derogatory comments, and personal or political attacks
34+
* Public or private harassment
35+
* Publishing others' private information, such as a physical or email address,
36+
without their explicit permission
37+
* Other conduct which could reasonably be considered inappropriate in a
38+
professional setting
39+
40+
## Enforcement Responsibilities
41+
42+
Community leaders are responsible for clarifying and enforcing our standards of
43+
acceptable behavior and will take appropriate and fair corrective action in
44+
response to any behavior that they deem inappropriate, threatening, offensive,
45+
or harmful.
46+
47+
Community leaders have the right and responsibility to remove, edit, or reject
48+
comments, commits, code, wiki edits, issues, and other contributions that are
49+
not aligned to this Code of Conduct, and will communicate reasons for moderation
50+
decisions when appropriate.
51+
52+
## Scope
53+
54+
This Code of Conduct applies within all community spaces, and also applies when
55+
an individual is officially representing the community in public spaces.
56+
Examples of representing our community include using an official e-mail address,
57+
posting via an official social media account, or acting as an appointed
58+
representative at an online or offline event.
59+
60+
## Enforcement
61+
62+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
63+
reported to the community leaders responsible for enforcement at
64+
[email protected].
65+
All complaints will be reviewed and investigated promptly and fairly.
66+
67+
All community leaders are obligated to respect the privacy and security of the
68+
reporter of any incident.
69+
70+
## Enforcement Guidelines
71+
72+
Community leaders will follow these Community Impact Guidelines in determining
73+
the consequences for any action they deem in violation of this Code of Conduct:
74+
75+
### 1. Correction
76+
77+
**Community Impact**: Use of inappropriate language or other behavior deemed
78+
unprofessional or unwelcome in the community.
79+
80+
**Consequence**: A private, written warning from community leaders, providing
81+
clarity around the nature of the violation and an explanation of why the
82+
behavior was inappropriate. A public apology may be requested.
83+
84+
### 2. Warning
85+
86+
**Community Impact**: A violation through a single incident or series of
87+
actions.
88+
89+
**Consequence**: A warning with consequences for continued behavior. No
90+
interaction with the people involved, including unsolicited interaction with
91+
those enforcing the Code of Conduct, for a specified period of time. This
92+
includes avoiding interactions in community spaces as well as external channels
93+
like social media. Violating these terms may lead to a temporary or permanent
94+
ban.
95+
96+
### 3. Temporary Ban
97+
98+
**Community Impact**: A serious violation of community standards, including
99+
sustained inappropriate behavior.
100+
101+
**Consequence**: A temporary ban from any sort of interaction or public
102+
communication with the community for a specified period of time. No public or
103+
private interaction with the people involved, including unsolicited interaction
104+
with those enforcing the Code of Conduct, is allowed during this period.
105+
Violating these terms may lead to a permanent ban.
106+
107+
### 4. Permanent Ban
108+
109+
**Community Impact**: Demonstrating a pattern of violation of community
110+
standards, including sustained inappropriate behavior, harassment of an
111+
individual, or aggression toward or disparagement of classes of individuals.
112+
113+
**Consequence**: A permanent ban from any sort of public interaction within the
114+
community.
115+
116+
## Attribution
117+
118+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119+
version 2.1, available at
120+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
121+
122+
Community Impact Guidelines were inspired by
123+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
124+
125+
For answers to common questions about this code of conduct, see the FAQ at
126+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
127+
[https://www.contributor-covenant.org/translations][translations].
128+
129+
[homepage]: https://www.contributor-covenant.org
130+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131+
[Mozilla CoC]: https://github.com/mozilla/diversity
132+
[FAQ]: https://www.contributor-covenant.org/faq
133+
[translations]: https://www.contributor-covenant.org/translations

‎.github/CONTRIBUTING.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
Feel free to:
44

55
- [Create an issue](https://help.github.com/articles/creating-an-issue/)
6-
- [Make a pull request](https://services.github.com/on-demand/github-cli/open-pull-request-github) into the `develop` branch
6+
- [Make a pull request](https://services.github.com/on-demand/github-cli/open-pull-request-github) into the `master` branch
77

88
Here is how you can help, a lot of steps are related to GitHub, not specifically my roles.
99

@@ -38,6 +38,6 @@ molecule test
3838
3939
## 6. Create a pull request
4040

41-
Please create a pull request into the `develop` branch. Here is [how to do it](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork).
41+
Please create a pull request into the `master` branch. Here is [how to do it](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork).
4242

4343
Please consider to [sponsor](https://github.com/sponsors/monolithprojects) me :-)

‎.github/ISSUE_TEMPLATE/bug_report.yml

Lines changed: 110 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,110 @@
1+
---
2+
name: Bug report
3+
description: File a bug report
4+
title: "bug: "
5+
labels: bug
6+
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: >
11+
**Thank you for wanting to report a bug!**
12+
13+
Verify first that your issue is not [already reported on
14+
GitHub][issue search].
15+
16+
Also test if the latest release is affected too.
17+
18+
- type: textarea
19+
attributes:
20+
label: Summary
21+
description: Explain the problem briefly below.
22+
placeholder: >-
23+
When I try to do X with teraform module from the main branch on GitHub, Y
24+
breaks in a way Z under the env E. Here are all the details I know
25+
about this problem...
26+
validations:
27+
required: true
28+
29+
- type: dropdown
30+
attributes:
31+
label: Issue Type
32+
description: >
33+
Please select the single available option in the drop-down.
34+
35+
<details>
36+
<summary>
37+
<em>Why?</em>
38+
</summary>
39+
40+
We would do it by ourselves but unfortunatelly, the curent
41+
edition of GitHub Issue Forms Alpha does not support this yet 🤷
42+
43+
44+
_We will make it easier in the future, once GitHub
45+
supports dropdown defaults. Promise!_
46+
47+
</details>
48+
options:
49+
- Bug Report
50+
validations:
51+
required: true
52+
53+
- type: textarea
54+
attributes:
55+
label: Ansible Version
56+
description: >-
57+
Paste verbatim output from `ansible --version` below, under
58+
the prompt line. Please don't wrap it with tripple backticks — your
59+
whole input will be turned into a code snippet automatically.
60+
render: console
61+
placeholder: |
62+
ansible [core 2.12.5]
63+
config file = None
64+
configured module search path = ['/home/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
65+
ansible python module location = /home/user/.local/lib/python3.10/site-packages/ansible
66+
ansible collection location = /home/user/.ansible/collections:/usr/share/ansible/collections
67+
executable location = /home/user/.local/bin/ansible
68+
python version = 3.10.4 (main, Mar 25 2022, 00:00:00) [GCC 12.0.1 20220308 (Red Hat 12.0.1-0)]
69+
jinja version = 3.0.3
70+
libyaml = True
71+
validations:
72+
required: true
73+
74+
- type: textarea
75+
attributes:
76+
label: Steps to Reproduce
77+
description: |
78+
Describe exactly how to reproduce the problem, using a minimal test-case.
79+
80+
**HINT:** You can paste https://gist.github.com links for larger files.
81+
value: |
82+
<!--- Paste example playbook between quotes below -->
83+
```yaml (paste below)
84+
85+
```
86+
validations:
87+
required: true
88+
89+
- type: textarea
90+
attributes:
91+
label: Expected Results
92+
description: >-
93+
Describe what you expected to happen when running the steps above.
94+
placeholder: >-
95+
I expected X to happen because I assumed Y.
96+
validations:
97+
required: true
98+
99+
- type: textarea
100+
attributes:
101+
label: Actual Results
102+
description: |
103+
Describe what actually happened.
104+
105+
Paste command output and don't wrap it with tripple backticks — your
106+
whole input will be turned into a code snippet automatically.
107+
render: console
108+
placeholder: Ansible command output...
109+
validations:
110+
required: true

‎.github/ISSUE_TEMPLATE/config.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
blank_issues_enabled: true

‎.github/ISSUE_TEMPLATE/feature_request.yml

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
---
2+
name: Feature request
3+
description: Suggest an idea for this project
4+
title: "feature: "
5+
labels: enhancement
6+
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: >
11+
**Thank you for wanting to suggest a feature!**
12+
13+
Please verify first that your idea is not [already requested on [GitHub][issue search].
14+
15+
- type: textarea
16+
attributes:
17+
label: Summary
18+
description: >
19+
Describe the new feature/improvement you would like briefly below.
20+
21+
What's the problem this feature will solve?
22+
What are you trying to do, that you are unable to achieve?
23+
24+
placeholder: >-
25+
The new feature will improve...
26+
validations:
27+
required: true
28+
29+
- type: dropdown
30+
attributes:
31+
label: Issue Type
32+
description: >
33+
Please select the single available option in the drop-down.
34+
35+
<details>
36+
<summary>
37+
<em>Why?</em>
38+
</summary>
39+
40+
We would do it by ourselves but unfortunatelly, the curent
41+
edition of GitHub Issue Forms Alpha does not support this yet 🤷
42+
43+
44+
_We will make it easier in the future, once GitHub
45+
supports dropdown defaults. Promise!_
46+
47+
</details>
48+
options:
49+
- Feature Idea
50+
validations:
51+
required: true

‎.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,20 @@
11
# Description
22

3+
<!---
34
Please include a summary of the change and which issue is fixed.
5+
--->
46

57
## Type of change
68

79
- [ ] Bug fix (non-breaking change which fixes an issue)
810
- [ ] New feature (non-breaking change which adds functionality)
911
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
1012
- [ ] This change requires a documentation update
11-
- [ ] Minor change (pipeline, tests, spelling ...)
13+
- [ ] Small minor change not affecting the Ansible Role code (Github Actions Workflow, Documentation etc.)
1214

1315
## How Has This Been Tested?
1416

17+
<!---
1518
Please describe the tests that you ran to verify your changes.
16-
17-
## Destination branch
18-
19-
Create a PR into `develop` branch
19+
Create a PR into `master` branch.
20+
--->

‎.github/workflows/galaxy.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,9 @@ on:
88

99
jobs:
1010
release:
11-
runs-on: ubuntu-18.04
11+
runs-on: ubuntu-20.04
1212
steps:
1313
- name: galaxy
1414
uses: robertdebock/[email protected]
1515
with:
1616
galaxy_api_key: ${{ secrets.galaxy_api_key }}
17-

‎.github/workflows/main.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ name: molecule test
33
on:
44
pull_request:
55
branches:
6+
- main
67
- master
78
types: [opened, synchronize, reopened]
89
schedule:

‎.github/workflows/pre-commit.yml

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
name: pre-commit
2+
3+
on:
4+
pull_request:
5+
branches:
6+
- main
7+
- master
8+
9+
jobs:
10+
pre-commit:
11+
runs-on: ubuntu-20.04
12+
steps:
13+
- uses: actions/checkout@v2
14+
- uses: actions/setup-python@v2
15+
16+
- name: Run pre-commit
17+
uses: pre-commit/[email protected]

0 commit comments

Comments
 (0)