mirror of https://github.com/CHEF-KOCH/Warez
97 lines
4.7 KiB
Markdown
97 lines
4.7 KiB
Markdown
# Contributing
|
|
|
|
When contributing to CHEF-KOCH/Warez, please first discuss the change you wish to make via issue
|
|
ticket, eMai or Discord with the owners of this repository before making any change.
|
|
|
|
Please note that we have a code of conduct, please follow it in all your interactions with this project.
|
|
|
|
## Pull Request Process
|
|
|
|
1. Ensure you fetch the latest versions first before you do a PR.
|
|
2. Update the README.md (or the file you like to change) with the changes which needs to be mention.
|
|
3. Do not link to offline websites, check it against [Down For Everyone Or Just Me](https://downforeveryoneorjustme.com/)
|
|
or [Down.com](https://down.com/).
|
|
4. Open Source programs should be preferred, whenever you mention a new program. Keep that in mind!
|
|
|
|
## Code of Conduct
|
|
|
|
### Our Pledge
|
|
|
|
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, gender identity and expression, level of experience,
|
|
nationality, personal appearance, race, religion, or sexual identity and
|
|
orientation.
|
|
|
|
### Our Standards
|
|
|
|
Examples of behavior that contributes to creating a positive environment
|
|
include:
|
|
|
|
* Using welcoming and inclusive language
|
|
* Being respectful of differing viewpoints and experiences
|
|
* Gracefully accepting [constructive criticism](https://www.definitions.net/definition/CONSTRUCTIVE+CRITICISM)
|
|
* Focusing on what is best for the community - quality over quantity!
|
|
* Showing empathy towards other community members
|
|
* Do not post/submit any links with `http://`, `ftp://` or any unencrypted protocol.
|
|
* Do not add mirrors or "new" website if the owner was not verified. You still can submit it but the review process will take longer to avoid linking to _fake_ or imposter websites.
|
|
|
|
|
|
Examples of unacceptable behavior by participants include:
|
|
|
|
* The use of sexualized language or imagery and unwelcome sexual attention or
|
|
advances
|
|
* [Trolling](https://en.wikipedia.org/wiki/Internet_troll), insulting/derogatory comments, and personal or political attacks
|
|
* Public or private harassment, there is a zero tollerance for this.
|
|
* Abusing GitHub's issue/pull request feature to troll/spam.
|
|
* Publishing others' private information, such as a physical or electronic
|
|
address, without explicit permission.
|
|
* Other conduct which could reasonably be considered inappropriate in a
|
|
professional setting
|
|
* Submitting something without doing research, testing or something which was
|
|
copied from the internet without any substantial evidence.
|
|
* Do not link to explicit content (see GitHUb FAQ what "explicit" means).
|
|
|
|
### Our Responsibilities
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
### Scope
|
|
|
|
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.
|
|
|
|
### Enforcement
|
|
|
|
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
reported by contacting the project team via eMail. 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.
|
|
|
|
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.
|
|
|
|
### Attribution
|
|
|
|
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
|
available at [http://contributor-covenant.org/version/1/4][version]
|
|
|
|
[homepage]: http://contributor-covenant.org
|
|
[version]: http://contributor-covenant.org/version/1/4/.
|