Skip to content

Commit 108a277

Browse files
lupraxuslupraxus
committed
The initial commit
0 parents  commit 108a277

19 files changed

+677
-0
lines changed

‎.github/CODEOWNERS

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
#
2+
# These owners will be the default owners for everything in the repo.
3+
#
4+
* @TGWolf
5+

‎.github/CODE_OF_CONDUCT.md

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at . All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

‎.github/CONTRIBUTING.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Contributing
2+
3+
Please refer to the [contributing](https://github.com/WolfSoftware/contributing) documentation.
4+
5+
## Important
6+
7+
ALL commits must be signed to ensure the identity of the developer, any pull requests that are made with unsigned commits will be rejected as a matter of course.
8+
9+
> This project has a [code of conduct](CODE_OF_CONDUCT.md). By interacting with this repository, organization, or community you agree to abide by its terms.

‎.github/FUNDING.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
# Funding
2+
# https://help.github.com/en/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository
3+
4+
ko_fi: wolfsoftware

‎.github/ISSUE_TEMPLATE/ask_question.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: Ask a question
3+
about: Feel free to ask us a question
4+
title: ''
5+
labels: 'question'
6+
assignees: 'TGWolf'
7+
8+
---
9+
10+
**What would you like to know?**

‎.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: 'bug'
6+
assignees: 'TGWolf'
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1.
16+
2.
17+
3.
18+
4.
19+
20+
**Expected behavior**
21+
A clear and concise description of what you expected to happen.
22+
23+
**Screenshots**
24+
If applicable, add screenshots to help explain your problem.
25+
26+
**Environment**
27+
Any relevant information about your environment, OS version, virtualised or not.
28+
29+
**Additional context**
30+
Add any other context about the problem here.

‎.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: false

‎.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: 'enhancement'
6+
assignees: 'TGWolf'
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

‎.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
2+
3+
**Summary**
4+
5+
<!-- Summary of the PR -->
6+
7+
This PR fixes/implements the following **bugs/features**
8+
9+
* [ ] Bug 1
10+
* [ ] Feature 1
11+
* [ ] Breaking changes
12+
13+
<!-- You can skip this if you're fixing a typo or adding an app to the Showcase. -->
14+
15+
Explain the **motivation** for making this change. What existing problem does the pull request solve?
16+
17+
<!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. -->
18+
19+
**Test plan (required)**
20+
21+
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots help greatly.
22+
23+
<!-- Make sure tests pass on both Travis. -->
24+
25+
**Closing issues**
26+
27+
<!-- Put `fixes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). -->
28+
Fixes #

‎.github/SECURITY.md

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# Security Policies and Procedures
2+
3+
This document outlines security procedures and general policies for this project.
4+
5+
* [Reporting a Bug](#reporting-a-bug)
6+
* [Disclosure Policy](#disclosure-policy)
7+
* [Comments on this Policy](#comments-on-this-policy)
8+
9+
## Reporting a Bug
10+
11+
We take **ALL** security related bugs and issues very seriously.
12+
13+
If you think you have identified a security related issue, please [report it immediately](mailto:[email protected])
14+
and include the word "SECURITY" in the subject line. If you are not sure, don’t worry.
15+
Better safe than sorry – just send an email.
16+
17+
* Please provide as much information as you can.
18+
* Please do not open issues related to any security concerns publicly.
19+
* Please do not include anyone else on the disclosure email.
20+
21+
Report security bugs in third-party modules to the person or team maintaining
22+
the module.
23+
24+
## Disclosure Policy
25+
26+
When a security report is received, we will carry out the following steps:
27+
28+
* Confirm the problem and determine the affected versions.
29+
* Audit code to find any potential similar problems.
30+
* Prepare fixes for all releases still under maintenance. These fixes will be
31+
released as fast as possible.
32+
33+
We will endeavor to keep you informed of the progress towards a fix
34+
and full announcement, and may ask for additional information or guidance.
35+
36+
## Comments on this Policy
37+
38+
If you have suggestions on how this process could be improved please submit a
39+
pull request.

0 commit comments

Comments
 (0)