forked from SimGus/Chatette
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
4 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,27 +1,21 @@ | ||
| # Contributing | ||
|
|
||
| This repository follows the motto *code first, discuss later*. If you want to add a feature or make a change to the code, feel free to do so by forking the repo and make a pull request when you deem your change worth being merged into the upstream code. | ||
| This pull request can then be discussed with the maintainer and possibly accepted. | ||
|
|
||
| Please note we have a code of conduct, please follow it in all your interactions with the project. | ||
|
|
||
| ## Pull Request Process | ||
|
|
||
| 1. Ensure any install or build dependencies are removed before the end of the layer when doing a build. | ||
| 2. Update the README.md with details of changes to the interface (this includes new environment variables, exposed ports, useful file locations and container parameters). | ||
| 3. Make a pull request on the GitHub repository. | ||
| 4. The pull request will then be discussed, and accepted or rejected. If changes are required before a merge, please make those changes as soon as possible. | ||
| 1. Update the README.md with details of changes to the interface (this includes new environment variables, exposed ports, useful file locations and container parameters). | ||
| 2. Make a pull request on the GitHub repository. The branch to merge to pull request in should be `dev` (unless otherwise discussed). | ||
| 3. The pull request will then be discussed, and accepted or rejected. If changes are required before a merge, please make those changes as soon as possible. | ||
|
|
||
| Please do not increase the version numbers in any examples files and the README.md. The maintainer is in charge of releasing new versions. | ||
|
|
||
| ## Code of Conduct | ||
|
|
||
| ### TL;DR | ||
|
|
||
| *Just be excellent to each other.* | ||
|
|
||
| ### 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 | ||
|
|
@@ -30,18 +24,15 @@ 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 | ||
| * Focusing on what is best for the community | ||
| * Showing empathy towards other community members | ||
|
|
||
| Examples of unacceptable behavior by participants include: | ||
|
|
||
| * The use of sexualized language or imagery and unwelcome sexual attention or | ||
| advances | ||
| * Trolling, insulting/derogatory comments, and personal or political attacks | ||
|
|
@@ -52,7 +43,6 @@ advances | |
| professional setting | ||
|
|
||
| ### 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. | ||
|
|
@@ -64,7 +54,6 @@ 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 | ||
|
|
@@ -73,9 +62,8 @@ 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 by contacting the project team on this GitHub repository by mentioning the name of the maintainer, or at [email protected]. | ||
| reported by mentioning the name of the maintainer in the relevant thread. | ||
| 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. | ||
|
|
@@ -86,7 +74,6 @@ 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] | ||
|
|
||
|
|
||