Merge branch 'master' into version-3.1.3-dev

Change-Id: I4ed551f5ad70e0c0b76c2297b9bf6c74191772bc

Author: samtstern

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @samtstern @SUPERCILEX

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md renamed to .github/CONTRIBUTING.md

@@ -2,5 +2,5 @@ Hey there! So you want to contribute to FirebaseUI? Before you file this pull re
 
   * Read [the contribution guidelines](CONTRIBUTING.md).
   * Run `./gradlew check` to ensure the Travis build passes.
-  * If this has been discussed in an issue, make sure to mention the issue number here.  If not, go file an issue about this to make sure this is a desirable change.
+  * If this has been discussed in an issue, make sure to mention the issue number here. If not, go file an issue about this to make sure this is a desirable change.
   * If this is a new feature please co-ordinate with someone on [FirebaseUI-iOS](https://github.com/firebase/firebaseui-ios) to make sure that we can implement this on both platforms and maintain feature parity.

ISSUE_TEMPLATE.md renamed to .github/ISSUE_TEMPLATE.md

@@ -7,24 +7,31 @@ quickly connect common UI elements to [Firebase](https://firebase.google.com) AP
 
 A compatible FirebaseUI client is also available for [iOS](https://github.com/firebase/firebaseui-ios).
 
-## Table of Contents
-
-  1. [Usage](#usage)
-  1. [Installation](#installation)
-  1. [Upgrading](#upgrading)
-  1. [Dependencies](#dependencies)
-  1. [Sample App](#sample-app)
-  1. [Contributing](#contributing)
+## Table of contents
+
+1. [Usage](#usage)
+1. [Installation](#installation)
+   1. [Upgrading](#upgrading)
+1. [Dependencies](#dependencies)
+   1. [Compatability](#compatibility-with-firebase--google-play-services-libraries)
+   1. [Upgrading dependencies](#upgrading-dependencies)
+1. [Sample App](#sample-app)
+1. [Contributing](#contributing)
+   1. [Installing](#installing-locally)
+   1. [Deploying](#deployment)
+   1. [Tagging](#tag-a-release-on-github)
+   1. [License agreements](#contributor-license-agreements)
+   1. [Process](#contribution-process)
 
 ## Usage
 
 FirebaseUI has separate modules for using Firebase Realtime Database, Cloud Firestore,
 Firebase Auth, and Cloud Storage. To get started, see the individual instructions for each module:
 
-  * [firebase-ui-database](database/README.md)
-  * [firebase-ui-firestore](firestore/README.md)
-  * [firebase-ui-auth](auth/README.md)
-  * [firebase-ui-storage](storage/README.md)
+* [FirebaseUI Auth](auth/README.md)
+* [FirebaseUI Firestore](firestore/README.md)
+* [FirebaseUI Database](database/README.md)
+* [FirebaseUI Storage](storage/README.md)
 
 ## Installation
 
@@ -53,22 +60,21 @@ implementation 'com.firebaseui:firebase-ui-storage:3.1.2'
 ```
 
 If you're including the `firebase-ui-auth` dependency, there's a little
-[more setup](https://github.com/firebase/FirebaseUI-Android/tree/master/auth#configuration)
-required.
+[more setup](auth/README.md#configuration) required.
 
 After the project is synchronized, we're ready to start using Firebase functionality in our app.
 
-## Upgrading
+### Upgrading
 
 If you are using an old version of FirebaseUI and upgrading, please see the appropriate
 migration guide:
 
-  * [Upgrade from 2.3.0 to 3.x.x](./docs/upgrade-to-3.0.md)
-  * [Upgrade from 1.2.0 to 2.x.x](./docs/upgrade-to-2.0.md)
+* [Upgrade from 2.3.0 to 3.x.x](./docs/upgrade-to-3.0.md)
+* [Upgrade from 1.2.0 to 2.x.x](./docs/upgrade-to-2.0.md)
 
 ## Dependencies
 
-### Compatibility with Firebase / Google Play Services Libraries
+### Compatibility with Firebase / Google Play Services libraries
 
 FirebaseUI libraries have the following transitive dependencies on the Firebase SDK:
 ```
@@ -87,7 +93,7 @@ firebase-ui-storage
 ```
 
 Each version of FirebaseUI has dependency on a fixed version of these libraries, defined as the variable `firebase_version`
-in `common/constants.gradle`.  If you are using any dependencies in your app of the form
+in `common/constants.gradle`. If you are using any dependencies in your app of the form
 `implementation 'com.google.firebase:firebase-*:x.y.z'` or
 `implementation 'com.google.android.gms:play-services-*:x.y.z'`
 you need to make sure that you use the same version that your chosen version of FirebaseUI requires.
@@ -110,15 +116,15 @@ For convenience, here are some recent examples:
 | 1.0.0              | 9.8.0                          |
 
 
-## Upgrading dependencies
+### Upgrading dependencies
 
 If you would like to use a newer version of one of FirebaseUI's transitive dependencies, such
 as Firebase, Play services, or the Android support libraries, you need to add explicit
 `implementation` declarations in your `build.gradle` for all of FirebaseUI's dependencies at the version
 you want to use. For example if you want to use Play services/Firebase version `FOO` and support
 libraries version `BAR` add the following extra lines for each FirebaseUI module you're using:
 
-Auth:
+#### Auth
 
 ```groovy
 implementation "com.google.firebase:firebase-auth:$FOO"
@@ -129,25 +135,25 @@ implementation "com.android.support:customtabs:$BAR"
 implementation "com.android.support:cardview-v7:$BAR"
 ```
 
-Realtime Database:
+#### Firestore
 
 ```groovy
-implementation "com.google.firebase:firebase-database:$FOO"
+implementation "com.google.firebase:firebase-firestore:$FOO"
 
 implementation "com.android.support:recyclerview-v7:$BAR"
 implementation "com.android.support:support-v4:$BAR"
 ```
 
-Firestore:
+#### Realtime Database
 
 ```groovy
-implementation "com.google.firebase:firebase-firestore:$FOO"
+implementation "com.google.firebase:firebase-database:$FOO"
 
 implementation "com.android.support:recyclerview-v7:$BAR"
 implementation "com.android.support:support-v4:$BAR"
 ```
 
-Storage:
+#### Storage
 
 ```groovy
 implementation "com.google.firebase:firebase-storage:$FOO"
@@ -156,7 +162,8 @@ implementation "com.android.support:appcompat-v7:$BAR"
 implementation "com.android.support:palette-v7:$BAR"
 ```
 
-NOTE :
+#### Note
+
 Starting version 25.4.0, support libraries are now available through
 [Google's Maven repository](https://developer.android.com/studio/build/dependencies.html#google-maven),
 so ensure that you have that added to your project's repositories.
@@ -172,9 +179,9 @@ allprojects {
 }
 ```
 
-## Sample App
+## Sample app
 
-There is a sample app in the `app/` directory that demonstrates most
+There is a sample app in the [`app/`](app) directory that demonstrates most
 of the features of FirebaseUI. Load the project in Android Studio and
 run it on your Android device to see a demonstration.
 
@@ -197,17 +204,19 @@ Gradle to their latest versions.
 You can download FirebaseUI and install it locally by cloning this
 repository and running:
 
-    ./gradlew :library:prepareArtifacts :library:publishAllToMavenLocal
+```sh
+./gradlew :library:prepareArtifacts :library:publishAllToMavenLocal
+```
 
 ###  Deployment
 
 To deploy FirebaseUI to Bintray
 
-  1. Set `BINTRAY_USER` and `BINTRAY_KEY` in your environment. You must
-     be a member of the firebaseui Bintray organization.
-  1. Run `./gradlew clean :library:prepareArtifacts :library:bintrayUploadAll`
-  1. Go to the Bintray dashboard and click 'Publish'.
-    1. In Bintray click the 'Maven Central' tab and publish the release.
+1. Set `BINTRAY_USER` and `BINTRAY_KEY` in your environment. You must
+   be a member of the firebaseui Bintray organization.
+1. Run `./gradlew clean :library:prepareArtifacts :library:bintrayUploadAll`
+1. Go to the Bintray dashboard and click 'Publish'.
+   1. In Bintray click the 'Maven Central' tab and publish the release.
 
 ### Tag a release on GitHub
 
@@ -222,25 +231,25 @@ have to jump a couple of legal hurdles.
 Please fill out either the individual or corporate Contributor License Agreement
 (CLA).
 
-  * If you are an individual writing original source code and you're sure you
-    own the intellectual property, then you'll need to sign an
-    [individual CLA](https://developers.google.com/open-source/cla/individual).
-  * If you work for a company that wants to allow you to contribute your work,
-    then you'll need to sign a
-    [corporate CLA](https://developers.google.com/open-source/cla/corporate).
+* If you are an individual writing original source code and you're sure you
+  own the intellectual property, then you'll need to sign an
+  [individual CLA](https://developers.google.com/open-source/cla/individual).
+* If you work for a company that wants to allow you to contribute your work,
+  then you'll need to sign a
+  [corporate CLA](https://developers.google.com/open-source/cla/corporate).
 
 Follow either of the two links above to access the appropriate CLA and
 instructions for how to sign and return it. Once we receive it, we'll be able to
 accept your pull requests.
 
-### Contribution Process
+### Contribution process
 
 1. Submit an issue describing your proposed change to the repo in question.
 1. The repo owner will respond to your issue promptly.
 1. If your proposed change is accepted, and you haven't already done so, sign a
    Contributor License Agreement (see details above).
-1. Fork the desired repo, develop and test your code changes.
+1. Fork the desired repo, develop, and then test your code changes **on the latest dev branch**.
 1. Ensure that your code adheres to the existing style of the library to which
    you are contributing.
 1. Ensure that your code has an appropriate set of unit tests which all pass.
-1. Submit a pull request and cc @puf or @samtstern
+1. Submit a pull request targeting the latest dev branch.