Skip to content

Commit 92fc7ea

Browse files
committed
Merge branch 'master' of https://github.com/jocic/PHP.Encoders
2 parents ece32cb + bc60cbe commit 92fc7ea

File tree

8 files changed

+1153
-3
lines changed

8 files changed

+1153
-3
lines changed
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: Bug Report Template
3+
about: Use the following markdown template when creating a bug report.
4+
title: "(BUG) "
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
## Bug Description
11+
12+
BUG DESCRIPTION SHOULD GO HERE
13+
14+
## Bug Reproduction
15+
16+
STEP BY STEP INSTRUCTIONS SHOULD GO HERE
17+
18+
## Expected Behavior
19+
20+
INFORMATION ABOUT EXPECTED BEHAVIOR SHOULD GO HERE
21+
22+
## Screenshots
23+
24+
ATTACH ANY SCREENSHOTS THAT MAY HELP WITH BUG RESOLUTION HERE
25+
26+
## System Information
27+
28+
YOUR SYSTEM INFORMATION SHOULD GO HERE - OS, ARCHITECTURE, ETC.
29+
30+
## Additional Context
31+
32+
ANY ADDITIONAL CONTEXT THAT MAY HELP WITH BUG RESOLUTION SHOULD GO HERE
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Custom Issue Template
3+
about: Use the following markdown template when creating a custom issue template.
4+
title: "(CUSTOM) "
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
## Issue Description
11+
12+
ISSUE DESCRIPTION SHOULD GO HERE
13+
14+
## Additional Context
15+
16+
ANY ADDITIONAL CONTEXT THAT MAY HELP WITH BUG RESOLUTION SHOULD GO HERE
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: Feature Request Template
3+
about: Use the following markdown template when creating a feature request.
4+
title: "(FEATURE) "
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
## Problem Description
11+
12+
IF YOUR FEATURE REQUEST IS RELATED TO A PROBLEM - PROBLEM DESCRIPTION SHOULD GO HERE
13+
14+
## Feature Description
15+
16+
YOUR DESCRIPTION SHOULD GO HERE
17+
18+
## Describe Potential Alternatives
19+
20+
YOUR DESCRIPTION ABOUT ALTERNATIVE SOLUTIONS SHOULD GO HERE - IF ANY
21+
22+
## Additional Context
23+
24+
ANY ADDITIONAL CONTEXT THAT MAY HELP WITH BUG RESOLUTION SHOULD GO HERE

code-of-conduct.md

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

contributing.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# Contributing Guidelines
2+
3+
* Don't break the existing features
4+
* Try to mimic the existing coding style
5+
* Add an appropriate unit test for your feature

0 commit comments

Comments
 (0)