added the js files for countrycode dropdown

.gitignore

@@ -0,0 +1,5 @@
+.DS_Store
+cache/*
+vendor/*
+coverage/*
+node_modules/*

.travis.yml

@@ -0,0 +1,37 @@
+# language used in the project
+language: php
+os: linux
+dist: precise
+
+# list any PHP version to test against
+php:
+  - 7.0
+  - 7.1
+
+# restricting the use of root privileges
+sudo: false
+
+# cache directories
+cache:
+  directories:
+    - cache
+    - vendor
+    - $HOME/.composer/cache
+
+# installing dependencies
+install:
+  - npm install
+  - npm install -g gulp-cli karma-cli
+  - gulp
+  - composer install --no-interaction --prefer-source
+
+# checks to run before scripts
+before_script:
+  # php syntax check (lint)
+  - if find . -name "*.php" ! -path "./vendor/*" -exec php -l {} \; | grep "unexpected $end"; then exit 1; fi
+  - ./vendor/bin/phpcs --standard=PSR2 includes/ modules/ request/ index.php
+
+# scripts like phpunit test
+script:
+  - ./vendor/bin/phpunit tests/phpUnitTests/
+  - ./node_modules/karma/bin/karma start jasmine.config.js --single-run

CONTRIBUTING.md

@@ -0,0 +1,12 @@
+# 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.
+## Repo Specific Guidelines

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 

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,42 @@
+### 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

Procfile

@@ -0,0 +1 @@
+web: vendor/bin/heroku-php-apache2 

README.md

@@ -1 +1,35 @@
-# PCSA-web
+# FirstAide-Web [![Build Status](https://travis-ci.org/systers/FirstAide-web.svg?branch=develop)](https://travis-ci.org/systers/FirstAide-web)
+
+### Abstract
+Sexual assault and rape are serious social and public health issues, being one of the major cause of concern.
+FirstAide-Web is a web based application developed to help the PCV(Peace Corps Volunteers), in case of sexual
+harassment. The app ensures safety by sending messages to fellow volunteers, helpline numbers etc. when in trouble. This application makes it a point that the victim can be sure of getting all the help
+he/she needs in case of a critical situation. The sexually assaulted volunteer can get information of Peace Corps policy and safety procedures and also contact Peace Corps for help.
+
+
+### Rules for Contributing
+1. To fix a new issue and submit a PR, the first step is to report the issue and get it approved by repo owners.
+2. Before submitting an issue, make sure it is not already reported by someone else. You can check [here](https://github.com/systers/FirstAide-web/issues) in both open and closed categories
+3. Before picking and working on an issue, make sure it is not already assigned to another developer. The protocol followed is that the issue is assigned to the developer who reports it first.
+4. To suggest features that you think will enhance the app, please email us. 
+5. When you submit a PR please ensure that commit messages are meaningful and reflect what the PR fixes.
+6. When you submit a PR for an issue, ensure that there is description of what the PR fixes, a link to the issue that you are fixing and tag the repo owners for review.
+
+
+### Initial Setup and Installation
+Download XAMPP from here [XAMPP download](https://www.apachefriends.org/download.html). You will also need a text editor.
+
+Go to your terminal and execute this command
+
+`$ git clone https://github.com/systers/FirstAide-web`
+
+Or download the ZIP file from above
+
+### Opening and Running
+1. Launch XAMPP by opening XAMPP control panel
+2. Start 'Apache' and 'MySQL'
+3. Check if XAMPP has started using the url 'http://localhost:8080/' (Here 8080 is the port number, use the one which you have configured)
+4. Now extract the ZIP file of the project FirstAide-web which you have downloaded and paste it in the C:\xampp\htdocs (the path where your xampp is present)
+5. Open the file which you want to work with using a text editor.
+6. Make the required changes and save the file
+7. Now, view your changes using the url http://localhost:8080/directory_name/file_name.extension  Example: 'http://localhost:8080/FirstAide-web/login.html'

cache/README.md

@@ -0,0 +1 @@
+### Note: This is cache directory. Do not commit anything here. 

code_of_conduct.md

@@ -0,0 +1,82 @@
+# Code of Conduct
+
+## 1. Purpose
+
+A primary goal of Systers is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
+
+This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
+
+We invite all those who participate in Systers to help us create safe and positive experiences for everyone.
+
+## 2. Open Source Citizenship
+
+A supplemental goal of this Code of Conduct is to increase open source citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
+
+Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.
+
+If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know.
+
+## 3. Expected Behavior
+
+The following behaviors are expected and requested of all community members:
+
+*   Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
+*   Exercise consideration and respect in your speech and actions.
+*   Attempt collaboration before conflict.
+*   Refrain from demeaning, discriminatory, or harassing behavior and speech.
+*   Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
+*   Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
+
+## 4. Unacceptable Behavior
+
+The following behaviors are considered harassment and are unacceptable within our community:
+
+*   Violence, threats of violence or violent language directed against another person.
+*   Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
+*   Posting or displaying sexually explicit or violent material.
+*   Posting or threatening to post other people’s personally identifying information ("doxing").
+*   Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
+*   Inappropriate photography or recording.
+*   Inappropriate physical contact. You should have someone’s consent before touching them.
+*   Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
+*   Deliberate intimidation, stalking or following (online or in person).
+*   Advocating for, or encouraging, any of the above behavior.
+*   Sustained disruption of community events, including talks and presentations.
+
+## 5. Consequences of Unacceptable Behavior
+
+Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.
+
+Anyone asked to stop unacceptable behavior is expected to comply immediately.
+
+If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).
+
+## 6. Reporting Guidelines
+If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible by emailing [email protected]. Please read [Reporting Guidelines](reporting_guidelines.md) for details.
+
+
+
+Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
+
+## 7. Addressing Grievances
+
+Only permanent resolutions (such as bans) may be appealed. To appeal a decision of the working group, contact the Systers' Open Source Board at [email protected] with your appeal and the board will review the case.
+
+
+## 8. Scope
+
+We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues–online and in-person–as well as in all one-on-one communications pertaining to community business.
+
+This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.
+
+## 9. Contact info
+
+[email protected]
+
+## 10. License and attribution
+
+This Code of Conduct is distributed under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/).
+
+Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy).
+
+Retrieved on November 22, 2016 from [http://citizencodeofconduct.org/](http://citizencodeofconduct.org/)

composer.json

@@ -0,0 +1,18 @@
+{
+    "require" : {
+        "php": "^7.0.0",
+        "twig/twig": "~2.0",
+        "twilio/sdk": "^5.10"
+    },
+    "require-dev" : {
+        "squizlabs/php_codesniffer": "*",
+        "phpunit/phpunit": "^6.1",
+        "mockery/mockery": "dev-master"
+    },
+    "autoload" : {
+        "psr-4" : {
+            "FirstAide\\":"modules/",
+            "Tests\\": "tests/phpUnitTests/"
+        }
+    }
+}