Merge branch 'master' into travis_improvement

Author: hypery2k

.gitattributes

@@ -0,0 +1,2 @@
+# Use LF for shell scripts
+*.sh eol=lf

.github/ISSUE_TEMPLATE.md

@@ -1,7 +1,7 @@
 PSST! Want to get faster responses to bug reports and important issues? Help us keep the issue tracker organized by:
 
-- Reporting bugs. Please include all details about the problem and provide a sample app.
+- Reporting bugs. Please include all details about the problem and provide a sample app (consider using the [playground](https://play.nativescript.org) for this.
 - Proposing features and enhancements.
 - Discussing implementation details.
 
-Please move all other content to [Stack Overflow](http://stackoverflow.com/questions/tagged/nativescript).
+Please move all other content to the [forums](http://forum.nativescript.org).

CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# NativeScript Community Code of Conduct
+
+Our community members come from all walks of life and are all at different stages of their personal and professional journeys. To support everyone, we've prepared a short code of conduct. Our mission is best served in an environment that is friendly, safe, and accepting; free from intimidation or harassment.
+
+Towards this end, certain behaviors and practices will not be tolerated.
+
+## tl;dr
+
+- Be respectful. 
+- We're here to help.
+- Abusive behavior is never tolerated. 
+- Violations of this code may result in swift and permanent expulsion from the NativeScript community channels. 
+
+## Administrators
+
+- Dan Wilson (@DanWilson on Slack)
+- Jen Looper (@jen.looper on Slack)
+- TJ VanToll (@tjvantoll on Slack)
+
+## Scope
+
+We expect all members of the NativeScript community, including administrators, users, facilitators, and vendors to abide by this Code of Conduct at all times in our community venues, online and in person, and in one-on-one communications pertaining to NativeScript affairs.
+
+This policy covers the usage of the NativeScript Slack community, as well as the NativeScript support forums, NativeScript GitHub repositories, the NativeScript website, and any NativeScript-related events. This Code of Conduct is in addition to, and does not in any way nullify or invalidate, any other terms or conditions related to use of NativeScript.
+
+The definitions of various subjective terms such as "discriminatory", "hateful", or "confusing" will be decided at the sole discretion of the NativeScript administrators.
+
+## Friendly, Harassment-Free Space
+
+We are committed to providing a friendly, safe, and welcoming environment for all, regardless of gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics.
+
+We ask that you please respect that people have differences of opinion regarding technical choices, and acknowledge that every design or implementation choice carries a trade-off and numerous costs. There is seldom a single right answer. A difference of technology preferences is never a license to be rude.
+
+Any spamming, trolling, flaming, baiting, or other attention-stealing behaviour is not welcome, and will not be tolerated.
+
+Harassing other users of NativeScript is never tolerated, whether via public or private media.
+
+Avoid using offensive or harassing package names, nicknames, or other identifiers that might detract from a friendly, safe, and welcoming environment for all.
+
+Harassment includes, but is not limited to: harmful or prejudicial verbal or written comments related to gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics; inappropriate use of nudity, sexual images, and/or sexually explicit language in public spaces; threats of physical or non-physical harm; deliberate intimidation, stalking or following; harassing photography or recording; sustained disruption of talks or other events; inappropriate physical contact; and unwelcome sexual attention.
+
+## Acceptable Content
+
+The NativeScript administrators reserve the right to make judgement calls about what is and isn't appropriate in published content. These are guidelines to help you be successful in our community.
+
+Content must contain something applicable to the previously stated goals of the NativeScript community. "Spamming", that is, publishing any form of content that is not applicable, is not allowed.
+
+Content must not contain illegal or infringing content. You should only publish content to NativeScript properties if you have the right to do so. This includes complying with all software license agreements or other intellectual property restrictions. For example, redistributing an MIT-licensed module with the copyright notice removed, would not be allowed. You will be responsible for any violation of laws or others’ intellectual property rights.
+
+Content must not be malware. For example, content (code, video, pictures, words, etc.) which is designed to maliciously exploit or damage computer systems, is not allowed.
+
+Content name, description, and other visible metadata must not include abusive, inappropriate, or harassing content.
+
+## Reporting Violations of this Code of Conduct
+
+If you believe someone is harassing you or has otherwise violated this Code of Conduct, please contact the administrators and send us an abuse report. If this is the initial report of a problem, please include as much detail as possible. It is easiest for us to address issues when we have more context.
+
+## Consequences
+
+All content published to the NativeScript community channels is hosted at the sole discretion of the NativeScript administrators.
+
+Unacceptable behavior from any community member, including sponsors, employees, customers, or others 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 NativeScript administrators 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 or service).
+
+## Addressing Grievances
+
+If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the administrators. We will do our best to ensure that your grievance is handled appropriately.
+
+In general, we will choose the course of action that we judge as being most in the interest of fostering a safe and friendly community.
+
+## Contact Info
+Please contact Dan Wilson @DanWilson if you need to report a problem or address a grievance related to an abuse report.
+
+You are also encouraged to contact us if you are curious about something that might be "on the line" between appropriate and inappropriate content. We are happy to provide guidance to help you be a successful part of our community.
+
+## Credit and License
+
+This Code of Conduct borrows heavily from the WADE Code of Conduct, which is derived from the NodeBots Code of Conduct, which in turn borrows from the npm Code of Conduct, which was derived from the Stumptown Syndicate Citizen's Code of Conduct, and the Rust Project Code of Conduct.
+
+This document may be reused under a Creative Commons Attribution-ShareAlike License.

CONTRIBUTING.md

@@ -0,0 +1,78 @@
+# Contributing to NativeScript Angular
+
+:+1: First of all, thank you for taking the time to contribute! :+1:
+
+Here are some guides on how to do that:
+
+<!-- TOC depthFrom:2 -->
+
+- [Code of Conduct](#code-of-conduct)
+- [Reporting Bugs](#reporting-bugs)
+- [Requesting Features](#requesting-features)
+- [Submitting a PR](#submitting-a-pr)
+- [Where to Start](#where-to-start)
+
+<!-- /TOC -->
+
+##  Code of Conduct
+Help us keep a healthy and open community. We expect all participants in this project to adhere to the [NativeScript Code Of Conduct](https://github.com/NativeScript/codeofconduct).
+
+
+## Reporting Bugs
+
+1. Always update to the most recent master release; the bug may already be resolved.
+2. Search for similar issues in the issues list for this repo; it may already be an identified problem.
+3. If this is a bug or problem that is clear, simple, and is unlikely to require any discussion -- it is OK to open an issue on GitHub with a reproduction of the bug including workflows and screenshots. If possible, submit a Pull Request with a failing test, entire application or module. If you'd rather take matters into your own hands, fix the bug yourself (jump down to the [Submitting a PR](#pr) section).
+
+## Requesting Features
+
+1. Use Github Issues to submit feature requests.
+2. First, search for a similar request and extend it if applicable. This way it would be easier for the community to track the features.
+3. When requesting a new feature, please provide as much detail as possible about why you need the feature in your apps. We prefer that you explain a need rather than explain a technical solution for it. That might trigger a nice conversation on finding the best and broadest technical solution to a specific need.
+
+## Submitting a PR
+
+Before you begin:
+* Read and sign the [NativeScript Contribution License Agreement](http://www.nativescript.org/cla).
+* Make sure there is an issue for the bug or feature you will be working on.
+
+Following these steps is the best way to get you code included in the project:
+
+1. Fork and clone the nativescript-angular repo:
+```bash
+git clone https://github.com/<your-git-username>/nativescript-angular.git
+# Navigate to the newly cloned directory
+cd nativescript-angular
+# Add an "upstream" remote pointing to the original repo.
+git remote add upstream https://github.com/NativeScript/nativescript-angular.git
+```
+
+2. Read our [development workflow guide](DevelopmentWorkflow.md) for local setup:
+
+3. Create a branch for your PR
+```bash
+git checkout -b <my-fix-branch> master
+```
+
+4. The fun part! Make your code changes. Make sure you:
+    - Follow the [code conventions guide](https://github.com/NativeScript/NativeScript/blob/master/CodingConvention.md).
+    - Write unit tests for your fix or feature.
+
+5. Before you submit your PR:
+    - Rebase your changes to the latest master: `git pull --rebase upstream master`.
+    - Ensure all unit test are green. Check [running unit tests](DevelopmentWorkflow.md#running-the-tests).
+    - Ensure your changes pass tslint validation. (run `npm run tslint` in the root of the repo).
+
+6. Push your fork. If you have rebased you might have to use force-push your branch:
+```
+git push origin <my-fix-branch> --force
+```
+
+7. [Submit your pull request](https://github.com/NativeScript/nativescript-angular/compare). Please, fill in the Pull Request template - it will help us better understand the PR and increase the chances of it getting merged quickly.
+
+It's our turn from there on! We will review the PR and discuss changes you might have to make before merging it! Thanks! 
+
+
+## Where to Start
+
+If you want to contribute, but you are not sure where to start - look for [issues labeled `help wanted`](https://github.com/NativeScript/nativescript-angular/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22).

DevelopmentWorkflow.md

@@ -0,0 +1,96 @@
+# Development Workflow
+
+<!-- TOC depthFrom:2 -->
+
+- [Running locally](#running-locally)
+    - [Prerequisites](#prerequisites)
+    - [Install dependencies](#install-dependencies)
+    - [Run the sample application (ng-sample)](#run-the-sample-application-ng-sample)
+- [Running the tests](#running-the-tests)
+- [Testing locally by running e2e tests](#testing-locally-by-running-e2e-tests)
+- [Developer workflow](#developer-workflow)
+
+<!-- /TOC -->
+
+## Running locally
+
+### Prerequisites
+
+Install your native toolchain and NativeScript as described in the docs:
+
+https://docs.nativescript.org/setup/quick-setup
+
+
+### Install dependencies
+
+```
+$ cd nativescript-angular
+$ npm install
+```
+
+### Run the sample application (ng-sample)
+
+Install NPM packages (use the local copy of `nativescript-angular`):
+```
+$ cd ng-sample
+$ npm install
+```
+
+Start the app:
+
+```
+$ tns run android
+$ tns run ios
+```
+
+## Running the tests
+
+Install NPM packages (use the local copy of `nativescript-angular`):
+```
+$ cd tests
+$ npm install
+```
+
+Start test run:
+
+```
+$ tns test ios
+$ tns test android
+```
+
+## Testing locally by running e2e tests
+
+NOTE: The steps below describe how to run `renderer` tests, but the same approach can be used to run `router` or any other `e2e` tests.
+
+1. Navigate to `e2e/renderer`
+    ``` bash
+    cd e2e/renderer
+    ```
+
+2. Install dependencies. This also installs your local copy of the nativescript-angular plugin.
+    ``` bash
+    npm install
+    ```
+3. Make sure to have an emulator set up or connect a physical Android/iOS device.
+
+4. Build the app for Android or iOS
+    ```bash
+    tns run android/ios
+    ```
+
+5. Install [appium](http://appium.io/) globally.
+    ``` bash
+    npm install -g appium
+    ```
+
+6. Follow the instructions in the [nativescript-dev-appium](https://github.com/nativescript/nativescript-dev-appium#custom-appium-capabilities) plugin to add an appium capability for your device inside `./e2e/renderer/e2e/config/appium.capabilities.json`.
+
+7. Run the automated tests. The value of the `runType` argument should match the name of the capability that you just added.
+    ``` bash
+    npm run e2e -- --runType capabilityName
+    ```
+
+## Developer workflow
+
+1. Make changes to the `test`, `ng-sample` projects or in `nativescript-angular` folder.
+2. Run the `tests` or `ng-sample` as shown above.