Close #23

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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 [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.
+
+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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,43 @@
+<!-- From the Deep Review, https://github.com/greenelab/deep-review -->
+
+# Contribution guidelines for Deep Rules
+
+Please see [`USAGE.md`](USAGE.md) for information on how to use the Manubot for
+writing the manuscript. Below you'll find information on the contribution
+workflow for Deep Rules.
+
+## Issues
+
+We use issues for discussion of papers, section outlines, and other structural
+components of the paper.
+
+## Pull requests
+
+Contributions to the article operate on a pull request model. We expect
+participants to actively review pull requests. We'd love to have you ask
+questions, clarify points, and jump in and edit the text.
+
+## Authorship
+
+What qualifies as authorship? We use the [ICMJE
+Guidelines](http://www.icmje.org/recommendations/browse/roles-and-responsibilities/defining-the-role-of-authors-and-contributors.html).
+We expect authors to contribute to the overall design by participating in
+issues, to contribute to the text by contributing sections and/or revisions to
+sections through pull requests. It is important to note that, for authorship,
+these should be substantial intellectual contributions.
+
+## Peer review
+
+All pull requests will undergo peer review. Participants in this project should
+review proposed changes (pull requests), which can be done using [GitHub's
+review interface](https://help.github.com/articles/about-pull-request-reviews/
+"GitHub: about pull request reviews"). They should suggest modifications or,
+potentially, directly edit the pull request to make suggested changes. As a
+reviewer, it's helpful to note the type of review you performed: did you read
+cited literature, look over the text in detail, or are you just supporting the
+concept?
+
+Before a repository maintainer merges a pull request, there must be at least one
+affirmative review. If there is any unaddressed criticism or disapproval, a
+repository maintainer will determine how to proceed and may wait for additional
+feedback.