Merge pull request #80 from koolamusic/GithubTemplates

Github Project Templates for PULL REQUESTS, CONTRIBUTING AND CREATING ISSUES

Author: erikguntner

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,80 @@
+# REACT PROTO CODE OF CONDUCT 1.0
+
+### Introduction
+
+>Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open 
+source project. In return, we ensure to reciprocate that respect in addressing your issue, assessing changes, and helping you 
+finalize your pull requests. If you are new here also checkout our [Contribution Guidelines](CONTRIBUTING.md)
+
+### 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 [INSERT EMAIL ADDRESS]. 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/

.github/CONTRIBUTING.md

@@ -0,0 +1,76 @@
+# React-Proto Contributing Guide 1.0
+
+> First off, thank you for considering making a contribution to [React Proto](https://github.com/React-Proto/react-proto). 
+It's people like you that inspire our commitment to open-source.
+
+The goal of this document is to create a contribution process that:
+
+* Encourages new contributions.
+* Encourages contributors to remain involved.
+* Creates a transparent decision making process that makes it clear how contributors can be involved in decision making.
+
+## Vocabulary
+
+* A **Contributor** is any individual creating or commenting on an issue or pull request.
+* A **Committer** is a subset of contributors who have been given write access to the repository.
+
+# Logging Issues
+
+Log an issue for any question or problem you might have. When in doubt, log an issue, and
+any additional policies about what to include will be provided in the responses. The only
+exception is security dislosures which should be sent privately.
+
+Committers may direct you to another repository, ask for additional clarifications, and
+add appropriate metadata before the issue is addressed.
+
+Please be courteous and respectful. Every participant is expected to follow the
+project's Code of Conduct.
+
+Keep an open mind! Improving documentation, bug triaging, or writing tutorials are all examples of helpful contributions that 
+mean less work for you.
+
+# Contributions
+
+### Ground Rules
+
+> Responsibilities
+> * Ensure cross-platform compatibility for every change that's accepted. Windows, Mac, Debian & Ubuntu Linux.
+> * Ensure that code that goes into core meets all requirements and pass tests. 
+> * Create issues for any major changes and enhancements that you wish to make. Discuss things transparently and get community 
+feedback.
+> * Keep feature versions as small as possible, preferably one new feature per version.
+> * Be welcoming to newcomers and encourage diverse new contributors from all backgrounds. Check our [CODE OF
+CONDUCT](CODE_OF_CONDUCT.md)
+
+
+
+
+
+Any change to resources in this repository must be through pull requests. This applies to all changes
+to documentation, code, binary files, etc. Even long term committers and Project Maintainers must use
+pull requests.
+
+No pull request can be merged without being reviewed.
+
+For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
+contributors in other timezones have time to review. Consideration should also be given to
+weekends and other holiday periods to ensure active committers all have reasonable time to
+become involved in the discussion and review process if they wish.
+
+The default for each contribution is that it is accepted once no committer has an objection.
+During review committers may also request that a specific contributor who is most versed in a
+particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
+process for contributions to land. Once all issues brought by committers are addressed it can
+be landed by any committer.
+
+In the case of an objection being raised in a pull request by another committer, all involved
+committers should seek to arrive at a consensus by way of addressing concerns being expressed
+by discussion, compromise on the proposed change, or withdrawal of the proposed change.
+
+If a contribution is controversial and committers cannot agree about how to get it to land
+or if it should land then it should be escalated to any of the Project Maintainers, 
+[@refinedblessing](https://github.com/refinedblessing) , [@erikguntner](https://github.com/erikguntner) , 
+[brianwtaylor](https://github.com/brianwtaylor). 
+Project Maintainers should regularly discuss pending contributions in order to find a resolution. It is expected that only a
+small minority of issues be brought to the Project Maintainers for resolution and that discussion and compromise among 
+committers be the default resolution mechanism.

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,52 @@
+---
+name: "\U0001F41BBug report"
+about: Something isn't working right
+---
+
+### React-Prot Version: x.x.x
+
+<!--- Provide the exact version of React-Proto in which you see the bug. -->
+
+### Details
+
+<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug. How has this bug affected 
+you? What were you trying to accomplish? -->
+
+### Expected Behavior
+
+<!--- Tell us what should happen -->
+
+### Actual Behavior
+
+<!--- Tell us what happens instead -->
+
+### Possible Fix
+
+<!--- Not obligatory, but suggest a fix or reason for the bug -->
+
+<details><summary>Additional Info</summary>
+
+### Your Environment
+
+<!-- Include as many relevant details about the environment you experienced the bug in -->
+
+- Environment name and version (e.g. Windows 10, node.js 5.4):
+- Operating System and version (Mac or Linux):
+- Useful link to screenshot or any other information:
+
+### Steps to Reproduce
+
+<!-- or an unambiguous set of steps to reproduce this bug -->
+
+<!-- include code to reproduce, if relevant -->
+
+1. first...
+2.
+3.
+4.
+
+### Stack Trace
+
+<!-- If an error is thrown, provide the stack trace here -->
+
+</details>

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,25 @@
+---
+name: "\U0001F680Feature request"
+about: Suggest an idea for React-Proto
+---
+
+### Description
+
+<!--- Provide a detailed description of the change or addition you are proposing -->
+
+### Why
+
+<!--- Why is this change important to you? How would you use it? -->
+
+<!--- How can it benefit other users? -->
+
+### Possible Implementation & Open Questions
+
+<!--- Not obligatory, but suggest an idea for implementing addition or change -->
+
+<!--- What still needs to be discussed -->
+
+### Is this something you're interested in working on?
+
+<!--- Yes or no -->
+

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,34 @@
+<!--- Provide a general summary of your changes in the Title above -->
+
+## Description
+
+<!--- Describe your changes in detail -->
+
+<!--- Why is this change required? What problem does it solve? -->
+
+<!--- If it fixes an open issue, please link to the issue here. -->
+
+## How Has This Been Tested?
+
+<!--- Please describe in detail how you tested your changes. -->
+
+<!--- Include details of your testing environment, tests ran to see how -->
+
+## Types of changes
+
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This change requires a documentation update
+
+## Checklist:
+
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+
+- [ ] I have read the **CONTRIBUTING** document and have signed (or will sign) the CLA.
+- [ ] I have updated/added documentation affected by my changes.
+- [ ] I have added tests to cover my changes.