Love Cobub Razor and want to get involved in the open source mobile analytics?

Thanks! There are plenty of ways you can help!

A bug is a demonstrable problem that is caused by the code in the repository.

Please read the following guidelines before you report an issue:

1. Use the GitHub issue search — check if the issue has already been reported. If it has been, please comment on the existing issue.
2. Check if the issue has been fixed — the latest master or development branch may already contain a fix.

Please try to be as detailed as possible in your report too. What is your environment? What steps will reproduce the issue? What browser(s) and OS experience the problem? What would you expect to be the outcome? All these details will help people to assess and fix any potential bugs.

Short and descriptive title

A summary of the issue and the browser/OS environment in which it occurs. If suitable, include the steps required to reproduce the bug.

1. This is the first step
2. This is the second step
3. Further steps, etc.

Any other information you want to share that is relevant to the issue being reported. This might include the lines of code that you have identified as causing the bug, and potential solutions (and your opinions on their merits).

A good bug report shouldn’t leave people needing to chase you up to get further information that is required to assess or fix the bug.

Good pull requests — patches, improvements, new features — are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.

If your contribution involves a significant amount of work or substantial changes to any part of the project, please open an issue to discuss it first.

Localization