Initial commit.

.github/ISSUE_TEMPLATE/1.Bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a bug report for one of the extensions.
+---
+
+# Bug report
+
+- Extension name: [e.g. `firestore-stripe-subscriptions`]
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+## To Reproduce
+
+Steps to reproduce the behavior, please provide code snippets or a repository:
+
+1. Go to '…'
+2. Click on '…'
+3. Scroll down to '…'
+4. See error
+
+## Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+## Screenshots
+
+If applicable, add screenshots to help explain your problem.
+
+## System information
+
+- OS: [e.g. macOS, Windows]
+- Browser (if applies) [e.g. Chrome, Safari]
+
+## Additional context
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/2.Feature_request.md

@@ -0,0 +1,24 @@
+---
+name: Feature request
+about: Request a new feature or extension.
+---
+
+# Feature request
+
+- Extension name: [e.g. `firestore-stripe-subscriptions`, or leave empty if suggesting a new extension]
+
+## Is your feature request related to a problem? Please describe.
+
+A clear and concise description of what you want and what your use case is.
+
+## Describe the solution you'd like
+
+A clear and concise description of what you want to happen.
+
+## Describe alternatives you've considered
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+## Additional context
+
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Need help with your integration?
+    url: https://support.stripe.com
+    about: Ask questions via our email support or the technical chat on IRC.

.gitignore

@@ -0,0 +1,14 @@
+.vscode
+node_modules/
+*.env
+firebase-debug.log
+.DS_Store
+mods-test-data/key.json
+.gradle
+.idea
+build
+*.iml
+local.properties
+coverage
+package-lock.json
+yarn.lock

.prettierignore

@@ -0,0 +1,17 @@
+package.json
+extension.yaml
+package-lock.json
+
+**/node_modules/**
+
+# generated files
+README.md
+**/functions/lib/**
+**/lib/**
+**/dist/**
+coverage
+
+# extension install md files
+#   - excluded as prettier escapes variables e.g. `${PROJECT_ID}` becomes `\${PROJECT_ID}`
+POSTINSTALL.md
+PREINSTALL.md

.prettierrc.yaml

@@ -0,0 +1,20 @@
+# Copyright 2020 Stripe, Inc.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#    https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+trailingComma: es5
+arrowParens: always
+overrides:
+  - files: "*.{yml,yaml}"
+    options:
+      proseWrap: always

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,39 @@
+# Contributing
+
+We highly appreciate feedback and contributions from the community! If you'd like to contribute to this project, please make sure to review and follow the guidelines below.
+
+## Code of conduct
+
+In the interest of fostering an open and welcoming environment, please review and follow our [code of conduct](./CODE_OF_CONDUCT.md).
+
+## Code and copy reviews
+
+All submissions, including submissions by project members, require review. We
+use GitHub pull requests for this purpose. Consult
+[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
+information on using pull requests.
+
+## Report an issue
+
+Report all issues through GitHub Issues using the [Report a Bug](https://github.com/stripe/stripe-firebase-extensions/issues/new?template=1.Bug_report.md) template.
+
+To help resolve your issue as quickly as possible, read the template and provide all the requested information.
+
+## File a feature request
+
+We welcome all feature requests, whether it's to add new functionality to an existing extension or to offer an idea for a brand new extension.
+
+File your feature request through GitHub Issues using the [Feature Request template](https://github.com/stripe/stripe-firebase-extensions/issues/new?template=2.Feature_request.md).
+
+## Create a pull request
+
+When making pull requests to the repository, make sure to follow these guidelines for both bug fixes and new features:
+
+- Before creating a pull request, file a GitHub Issue so that maintainers and the community can discuss the problem and potential solutions before you spend time on an implementation.
+- In your PR's description, link to any related issues or pull requests to give reviewers the full context of your change.
+- For commit messages, follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format.
+  - For example, if you update documentation for a specific extension, your commit message might be: `docs(extension-name) updated installation documentation`.
+
+### Features
+
+Before creating pull requests for new features, first file a GitHub Issue describing the reasoning and motivation for the feature. This gives maintainers and the community the opportunity to provide feedback on your idea before implementing it.