Contributing to Cannonball
We'd love for you to contribute to our source code and to make Cannonball even better than it is today! Here are the guidelines we'd like you to follow:
- Code of Conduct
- Question or Problem?
- Issues and Bugs
- Feature Requests
- Submission Guidelines
- Coding Rules
- Signing the CLA
As contributors and maintainers of the Cannonball project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities.
Communication through any of Cannonball or Firebase's channels (GitHub, StackOverflow, Google+, Twitter, etc.) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
We promise to extend courtesy and respect to everyone involved in this project regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to the project to do the same.
If any member of the community violates this code of conduct, the maintainers of the Cannonball project may take action, removing issues, comments, and PRs or blocking accounts as deemed appropriate.
If you are subject to or witness unacceptable behavior, or have any other concerns, please drop us a line at email@example.com.
If you have technical questions about Friendly Pix, please direct these to StackOverflow and use the
firebase tag. We are also available on GitHub issues.
If you find a bug in the source code or a mistake in the documentation, you can help us by submitting an issue to our GitHub Repository. Even better you can submit a Pull Request with a fix.
See below for some guidelines.
You can request a new feature by submitting an issue to our GitHub Repository.
If you would like to implement a new feature then consider what kind of change it is:
- Major Changes that you wish to contribute to the project should be discussed first on our issue tracker so that we can better coordinate our efforts, prevent duplication of work, and help you to craft the change so that it is successfully accepted into the project.
- Small Changes can be crafted and submitted to the GitHub Repository as a Pull Request directly.
Submitting an Issue
Before you submit your issue, search the archive - maybe your question was already answered.
If your issue appears to be a bug, and hasn't been reported, open a new issue. Help us to maximize the effort we can spend fixing issues and adding new features, by not reporting duplicate issues. Providing the following information will increase the chances of your issue being dealt with quickly:
- Overview of the Issue - if an error is being thrown a non-minified stack trace helps
- Motivation for or Use Case - explain why this is a bug for you
- Friendly Pix Version(s) - is it a regression?
- Browsers and Operating System - is this a problem with all browsers or only some browsers?
- Reproduce the Error - provide an unambiguous set of steps.
- Related Issues - has a similar issue been reported before?
- Suggest a Fix - if you can't fix the bug yourself, perhaps you can point to what might be causing the problem (line of code or commit)
If you get help, help others. Good karma rulez!
Here's a template to get you started:
Browser: Browser version: Operating system: Operating system version: URL, if applicable: What steps will reproduce the problem: 1. 2. 3. What is the expected result? What happens instead of that? Please provide any other information below, and attach a screenshot if possible.
Submitting a Pull Request
Before you submit your pull request consider the following guidelines:
Search GitHub for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.
Please sign our Contributor License Agreement (CLA) before sending pull requests. We cannot accept code without this.
Make your changes in a new git branch:
git checkout -b my-fix-branch master
Create your patch, including appropriate test cases.
Follow our Coding Rules.
Avoid checking in files that shouldn't be tracked (e.g
.idea). We recommend using a global gitignore for this.
Make sure not to include a recompiled version of the files as part of your PR. We will generate these automatically.
Commit your changes using a descriptive commit message.
git commit -a
Note: the optional commit
-acommand line option will automatically "add" and "rm" edited files.
Build your changes locally to ensure all the tests pass:
Push your branch to GitHub:
git push origin my-fix-branch
In GitHub, send a pull request to
If we suggest changes then:
Make the required updates.
Re-run the Friendly Pix test suite to ensure tests are still passing.
Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
git rebase master -i git push origin my-fix-branch -f
That's it! Thank you for your contribution!
After your pull request is merged
After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream) repository:
Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
git push origin --delete my-fix-branch
Check out the master branch
git checkout master -f
Delete the local branch:
git branch -D my-fix-branch
Update your master with the latest upstream version:
git pull --ff upstream master
Make sure to adhere to the coding conventions used throughout the codebase (indentation, accurate comments, etc.) and any other requirements.
Contributions to this project must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project. Head over to https://cla.developers.google.com/ to see your current agreements on file or to sign a new one.
You generally only need to submit a CLA once, so if you've already submitted one (even if it was for a different project), you probably don't need to do it again.