Browse files

Merge branch 'master' of

  • Loading branch information...
jemus42 committed Nov 17, 2018
2 parents e6637e1 + 575778d commit 9cca67118674b049ae1e66f21c75c133008968be
Showing with 63 additions and 0 deletions.
  1. +46 −0
  2. +17 −0
@@ -0,0 +1,46 @@
# Contributor Covenant 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
* 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
* Public or private harassment
* 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

## 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 at The project team will review and investigate all complaints, and will respond in a way that it deems 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 [][version]

@@ -0,0 +1,17 @@
You can suggest any kind of change you want to, but the larger the change, the more careful we need to be.

## Typos, spelling, grammar...

These minor changes can be done quikcly via the GitHub web-editor and submiited as a pull request with minimal comments.
A fix for a typo should be immediately obvious given the diff, so no justification is required. Please keep related changes in one PR.

## Content

Larger changes to content should be discussed in an issue prior to any changes, and optionally in our internal Slack group.
PRs that change larger sections of content without proper comments / explanations might be rejected unless appropriately discussed.

## Nitty gritty

Changes to the build system, i.e. bookdown options or other changes that don't change the content, but the generated output,
are very delicate and should be rigorously tested to ensure we don't accidentally break all the things.
PRs changing these internals are therefore discouraged, unless tested.

0 comments on commit 9cca671

Please sign in to comment.