Merge pull request #1 from riibeirogabriel/migrating-python-client

Migrating python client

Author: riibeirogabriel

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,31 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!-- Give a title explaining the bug/issue -->
+#### Bug description
+<!-- Describe the issue that you are having -->
+
+#### Expected result
+<!-- What should be the expected result? -->
+
+#### Actual result
+<!-- What is the result now? -->
+
+#### Steps to reproduce
+<!-- If applicable -->
+
+1.
+2.
+3.
+#### Context
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+#### Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+#### Is your feature request related to a problem? Please describe.
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+#### Describe the solution you'd like
+A clear and concise description of what you want to happen.
+
+#### Describe alternatives you've considered
+A clear and concise description of any alternative solutions or features you've considered.
+
+#### Additional context
+Add any other context or screenshots about the feature request here.

.github/pull_request_template.md

@@ -0,0 +1,22 @@
+#### Changes
+<!-- Please include a summary of the change and which issue is fixed. --> 
+<!-- Please also include relevant motivation and context. -->
+<!-- List any dependencies that are required for this change. -->
+
+Fixes # (issue)
+
+#### Type of change
+<!-- Please delete options that are not relevant. -->
+
+- [ ] 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
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings

CONTRIBUTING.md

@@ -0,0 +1,40 @@
+# Contributing to LearningOrchestra
+We want to make contributing to LearningOrchestra as easy and as simple as humanly possible.\
+Whether you want to:
+* Report an issue
+* Contribute with a feature
+* Contribute with a fix
+
+Before you open an issue or a pull request, check whether that issue has been discussed already or a PR exists that addresses it. Don't open pull requests for issues that are already under review.
+
+After looking through the issues and seeing that an issue is available for you to tackle, you may begin the pull request process.
+
+### Reporting a bug/issue
+When creating an issue for a bug or other undefined/unwanted behaviour remember to include in your issue or pull request steps necessary to reproduce that behaviour.
+
+## Pull Request process
+
+1. [Fork](https://github.com/riibeirogabriel/learningOrchestra/fork) the repository
+2. [Clone](https://git-scm.com/docs/git-clone) your fork to your local environment
+3. Navigate into the project root directory
+4. Create a new [branch](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging), the branch should be named according to what feature/fix you're implementing
+5. Make your changes, stage them and [commit](https://git-scm.com/docs/git-commit) them to the branch
+    - Make sure to use proper language idioms, formatting and linting before commiting your work, like proper variable naming, indentation, etc.
+    - Make sure your code passes any tests the repository offers
+    - Make sure to adopt the coding style of the repository and not to force your own coding habits into the codebase
+6. [Push](https://git-scm.com/docs/git-push) the changes to your fork
+7. Create a Pull Request
+
+Remember to describe what feature or fix you're implementing in the Pull Request window.
+In the Pull Request window remember to include a quick summary of what the committed code does and how it is an improvement. 
+
+After the Pull Request the repository owner will review your request.\
+Be patient, if they require you to make changes to your request, do so.
+
+## Standards
+Please be polite to other members and contributors and follow GitHub etiquette.\
+Don't be rude, use crude language or harass other users.
+
+## License
+The repository is currently licenses under GNU General Public License v3.0.
+By contributing to the project you agree that your contributions will be licensed under the same license and provisions.