Can I use this code

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,20 @@
+## Description
+As a [USER],
+I need [TO DO THIS],
+so that I can [ACCOMPLISH THAT].
+
+## Mocks
+[INSERT RELEVANT PNG FILE]
+
+## Acceptance Criteria
+### Update [Required]
+- [ ] [LIST ITEMS]
+### Enhancement to Update [Optional]
+- [ ] [LIST ITEMS]
+
+## Definition of Done
+- [ ] All of the required items are completed.
+- [ ] Approval by 1 mentor.
+
+## Estimation
+[INSERT NUMBER HERE] hours

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,40 @@
+### Description
+Include a summary of the change and relevant motivation/context. List any dependencies that are required for this change.
+
+Fixes # [ISSUE]
+
+### Type of Change:
+**Delete irrelevant options.**
+
+- Code
+- Quality Assurance
+- User Interface
+- Outreach
+- Documentation
+
+**Code/Quality Assurance Only**
+- Bug fix (non-breaking change which fixes an issue)
+- This change requires a documentation update (software upgrade on readme file)
+- New feature (non-breaking change which adds functionality pre-approved by mentors)
+
+
+
+### How Has This Been Tested?
+Describe the tests you ran to verify your changes. Provide instructions or GIFs so we can reproduce. List any relevant details for your test.
+
+
+### Checklist:
+**Delete irrelevant options.**
+
+- [ ] My PR follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code or materials
+- [ ] I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] Any dependent changes have been merged 
+
+**Code/Quality Assurance Only**
+- [ ] My changes generate no new warnings 
+- [ ] My PR currently breaks something (fix or feature that would cause existing functionality to not work as expected)
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been published in downstream modules

.gitignore

@@ -1,29 +1,48 @@
-# built application files
+# Built application files
 *.apk
 *.ap_
 
-# files for the dex VM
+# Files for the ART/Dalvik VM
 *.dex
 
 # Java class files
 *.class
 
-# generated files
+# Generated files
 bin/
 gen/
+out/
+
+# Gradle files
+.gradle/
+build/
 
 # Local configuration file (sdk path, etc)
 local.properties
 
-# Eclipse project files
-.classpath
-.project
-
 # Proguard folder generated by Eclipse
 proguard/
 
-# Intellij project files
+# Log Files
+*.log
+
+# Android Studio Navigation editor temp files
+.navigation/
+
+# Android Studio captures folder
+captures/
+
+# Intellij
 *.iml
-*.ipr
-*.iws
-.idea/
+.idea/workspace.xml
+.idea/tasks.xml
+.idea/libraries
+**/.idea/**
+**/*.iml
+
+# Keystore files
+*.jks
+
+# External native build folder generated in Android Studio 2.2 and later
+.externalNativeBuild
+

.travis.yml

@@ -0,0 +1,17 @@
+sudo: required
+language: android
+jdk: oraclejdk8
+android:
+ components:
+    - platform-tools
+    - tools
+    - build-tools-26.0.2
+    - android-26
+    - extra-android-m2repository
+before_script:
+ - chmod +x gradlew
+ - chmod +x generate-apk.sh
+script:
+ - ./gradlew assembleDebug --stacktrace # Change 'assembleDebug' to 'build' when lint issues are fixed. Update generate-apk.sh accordingly
+after_success:
+ - ./generate-apk.sh

CONTRIBUTING.md

@@ -0,0 +1,11 @@
+# Contributing Guidelines
+* You can join our [slack channel](http://systers.io/slack-systers-opensource/).  Each active repo has its own channel to direct questions to (for example #powerup or #portal).  
+* Remember that this is an inclusive community, committed to creating a safe, positive environment.  See the full [Code of Conduct](http://www.systers.io/code-of-conduct.html).
+## General Guidelines
+* If you’re just getting started work on an issue labeled “First Timers Only” in any project. Additional resources are available on our [website](http://www.systers.io).
+* In an active repository (not an archived one), choose an open issue from the issue list, claim it in the comments, and a maintainer will assign it to you.  
+* After approval you must make continuous notes on your progress in the issue while working.  If there is not at least one comment every 3 days, the maintainer can reassign the issue.
+* When sending a PR have an appropriate title referencing the issue which it solves. Add “fixes #<issue-number>” in the commit body, so that when the PR gets merged, the issue gets closed automatically. Do not do this if the PR solves only a part of the issue. See more information on commit guidelines [here](https://udacity.github.io/git-styleguide/).
+* If you’d like to create a new issue, please go through our issue list first (open as well as closed) and make sure the issues you are reporting do not replicate the existing issues. 
+* Have a short description on what has gone wrong (like a root cause analysis and description of the fix), if that information is not already present in the issue.
+* If you have issues on multiple pages, report them separately. Do not combine them into a single issue.

README.md

@@ -1,3 +1,5 @@
+[![Build Status](https://travis-ci.org/systers/malaria-app-android.svg?branch=master)](https://travis-ci.org/systers/malaria-app-android)
+
 Malaria App for Android
 ====
 
@@ -31,7 +33,32 @@ Included in this repository are files to help you get started:
 This project uses Jack Wharton's Android-ViewPagerIndicator for the Viewpager Swipe view.
  <a href="https://github.com/chimdi2000/ViewPagerIndicator">Jake Wharton ViewPager Indicator project dependecy</a>
 
-<h4> <a href="https://drive.google.com/file/d/0B0E0_9za8pF1RDg5QkVPNzh6Vjg/view?usp=sharing"> Download Current Malaria APK File here </a> </h4>
+<h4> <a href="https://drive.google.com/open?id=0B6cRm7QFaag1dUMxVU5qQ0dnXzA"> Download Current Malaria APK File here </a> </h4>
+
+## Current Status
+<h4> <a href="https://www.youtube.com/watch?v=078kGriqwvk"> GSOC 2016 Malaria App Demo </a> </h4>
+<h4> <a href="https://www.youtube.com/watch?v=uNik1KMpt-4"> GSOC 2015 Malaria App Demo </a> </h4>
+
+
+## Guidelines for contributors
+To contribute to malaria-app-android pick an open issue from the [issue list](https://github.com/systers/malaria-app-android/issues) tagged as "free", claim it in the comments, fix the issue and send us a pull request. 
+If you find an issue yourself you can report it, a community member will get back to you and approve the issue. Then you can fix it and submit a PR. Please go through our issue list first and make sure the issues you are reporting do not replicate the issues already reported. If you have multiple issues, report them separately. Do not combine them into a single issue.
+
+### Best Practise
+1. Try to do a root cause analysis for the issue, if applicable. 
+2. Reference the issue being fixed in the corresponding PR. 
+3. Use meaningful commit messages in a PR.
+4. Use one commit per task. Do not over commit (add unnecessary commits for a single task) or under commit (merge 2 or more tasks in one commit).
+5. Add screenshot/short video in case the changes made in the PR, are being reflected in the UI of the application.
+6. Close the issue as soon as the corresponding PR is accepted/closed.
+
+### Some Don'ts
+1. Send a PR without an existing issue.
+2. Fix an issue assigned to somebody else and submit a PR before the assignee does. 
+3. Report issues which are previously reported by others. (Please check both the open and closed issues). 
+4. Suggest unnecessary or completely new features in the issue list.
+5. Add unnecessary spacing or indentation to the code.
+
 
 <h3>Contact Information:</h3>