Contributing to biicode
Found a bug, have a feature request or want to hack biicode? Great!
Thanks for taking time to contribute. Here's a set of guidelines for contributing and reporting.
Please send your report directly to firstname.lastname@example.org.
We take security issues very seriously. If you're dealing with a security issue, please email us at email@example.com. Thanks!
Questions and Answers
Need any help using biicode?
Have a feature request or found a bug in biicode?
Before opening a fresh issue, do a search on GitHub and make sure it hasn't already been addressed. Here are some notes on how to detail feature requests or bug reports:
- Explain, as detailed as possible, how to reproduce the issue or the specific behaviour for the feautre.
- Include what you expected to happen and what actually happened.
- Please include information on what operating system and biicode version you are working with. Also add any other relevant details.
- Feel free to attach any other information illustrating the issue.
Know how to fix something? Make a pull request! Here's a quick guide:
- (Optional) Open a new issue before you start working on a feature idea or a bug. This way we can help you out and possibly guide you.
- Follow the PEP 8 - Style Guide for Python Code.
- Fork the specific repository on GitHub and add the upstream repository.
- Create a feature branch from
developand start making your changes:
$ git checkout -b my-feature-branch -t origin/develop
- Check out the README for the information specific to that repository.
- Use git rebase (rather than git merge) to sync your work from time to time.
- Push the change.
$ git push origin my-feature-branch
- Open a pull request.
- In time we will revise every single PR received. Be patient.
Individual Contributor License Agreement
Before we can put your code into our codebase, you must sign the Individual Contributor License Agreement (CLA).
We need a CLA because you own the copyright to your changes, even after your contribution becomes part of our codebase, so we need your permission to use and distribute your code. We also need to be sure of various other things—for instance that you'll tell us if you know that your code infringes on other people's patents.