Add Contributing.md and ISSUE_TEMPLATE.md and PULL_REQUEST_TEMPLATE

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,28 @@
+**Checklist**
+
+- [ ] Bug Report - The issue you are reporting might be there already. Please search on the [issues tracker](https://github.com/openfoodfacts/openfoodfacts-server/issues) before creating or reporting a issue.
+
+- [ ] Before reporting, please ensure (if you can) that you have tested it with the latest (dev) version of the software.
+
+- [ ] Don't forget to tag your issue, it makes it easier to discover.
+
+**Summary:** 
+
+Summarize your issue in one sentence (what goes wrong, what did you expect to happen)
+
+**Steps to reproduce:** 
+
+How can we reproduce the issue?
+
+**Add system logs:**
+
+Add logcat files here (if you are able to add).
+
+**Expected behavior:** 
+
+What did you expect the app to do?
+
+**Observed behavior:** 
+
+What did you see instead?  Describe your issue in detail here.
+

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+## Description
+
+Describe the changes made and why they were made instead of how they were made.
+
+## Related issues and discussion
+#{Issue Number}
+
+
+## Checklist
+
+Make sure you've done all the following (You can delete the checklist before submitting)
+
+ - [ ] Code is well documented
+ - [ ] Include unit tests for new functionality
+ - [ ] Code passes Travis builds in your branch
+ - [ ] If you have multiple commits please combine them into one commit by squashing them.
+ - [ ] Read and understood the [contribution guidelines](https://github.com/openfoodfacts/openfoodfacts-server/blob/master/CONTRIBUTING.md)
+

CONTRIBUTING.md

@@ -0,0 +1,31 @@
+# Join the development
+* Before you join development, please set up the project on your local machine, run it and go through the application completely. Press on any button you can find and see where it leads to. Explore.You'll be more familiar with what is where and might even get some cool ideas on how to improve various aspects of the app.
+* If you would like to work on an issue, drop in a comment at the issue. If it is already assigned to someone, but there is no sign of any work being done, please free to drop in a comment so that the issue can be assigned to you if the previous assignee has dropped it entirely.
+
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via issue, or the official [slack channel](https://slack-ssl-openfoodfacts.herokuapp.com/).
+
+## Pull Request Process
+
+1. Ensure any install or build dependencies are removed before the end of the layer when doing a 
+   build.
+2. Check that there are no conflicts and your request passes [Travis](https://travis-ci.org) build. Check the log of the pass test if it fails the build.
+3. Give the description of the issue that you want to resolve in the pull request message. The format of the commit message to be fixed    - **Fixes #[issue number] [Description of the issue]** Example: **Fixes #529: Add toast warning in `MainActivity.java`** 
+4. Wait for the maintainers to review your pull request and do the changes if requested.
+
+## Contributions Best Practices
+
+### Commits
+
+* Write clear meaningful git commit messages (Do read [here](http://chris.beams.io/posts/git-commit/))
+* Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (For more info click [here]( https://github.com/blog/1506-closing-issues-via-pull-requests))
+* When you make very very minor changes to a PR of yours (like for example fixing a failing Travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at [here](https://davidwalsh.name/squash-commits-git )
+* When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.
+
+### Feature Requests and Bug Reports
+* When you file a feature request or when you are submitting a bug report to the [issue tracker](https://github.com/openfoodfacts/openfoodfacts-server/issues), make sure you add steps to reproduce it. Especially if that bug is some weird/rare one.
+
+## Code of Conduct
+
+For our Code of Conduct, you should head over [here](https://en.wiki.openfoodfacts.org/Code_of_conduct)

README.md

@@ -66,6 +66,8 @@ along with this program.  If not, see <http://www.gnu.org/licenses/>.
 
 ### Contribution guidelines ###
 
+If you're new to Open-Source,We recommend you to Checkout our [_Contributing Guidelines_](https://github.com/openfoodfacts/openfoodfacts-server/blob/master/CONTRIBUTING.md).Feel free to fork the project and send us a pull request.
+
 * Writing tests
 * Code review
 * Other guidelines