mirror of
https://github.com/kellyjonbrazil/jc.git
synced 2025-06-25 00:37:31 +02:00
47 lines
2.3 KiB
Markdown
47 lines
2.3 KiB
Markdown
|
# Contributing to jc
|
||
|
|
We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
|
||
|
|
|
||
|
|
- Reporting a bug
|
||
|
|
- Discussing the current state of the code
|
||
|
|
- Submitting a fix
|
||
|
|
- Proposing new features
|
||
|
|
- Proposing a new parser
|
||
|
|
|
||
|
|
## We Develop with Github
|
||
|
|
We use github to host code, to track issues and feature requests, as well as accept pull requests.
|
||
|
|
|
||
|
|
## We Use Github Flow, So All Code Changes Happen Through Pull Requests
|
||
|
|
Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
|
||
|
|
|
||
|
|
1. Open an issue to discuss the new feature, bug fix, or parser before opening a pull request. For new parsers, it is important to agree upon a schema before developing the parser.
|
||
|
|
2. Fork the repo and create your branch from `dev`, if available, otherwise `master`.
|
||
|
|
3. If you've added code that should be tested, add tests. All new parsers should have several sample outputs and tests.
|
||
|
|
4. Documentation is auto-generated from docstrings, so ensure they are clear and accurate.
|
||
|
|
5. Ensure the test suite passes.
|
||
|
|
6. Make sure your code lints.
|
||
|
|
7. Issue that pull request!
|
||
|
|
|
||
|
|
## Any contributions you make will be under the MIT Software License
|
||
|
|
In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
|
||
|
|
|
||
|
|
## Report bugs using Github's [issues](https://github.com/kellyjonbrazil/jc/issues)
|
||
|
|
We use GitHub issues to track public bugs. Report a bug by [opening a new issue](); it's that easy!
|
||
|
|
|
||
|
|
## Write bug reports with detail, background, and sample code
|
||
|
|
**Great Bug Reports** tend to have:
|
||
|
|
|
||
|
|
- A quick summary and/or background
|
||
|
|
- Steps to reproduce
|
||
|
|
- Be specific!
|
||
|
|
- Give sample code if you can.
|
||
|
|
- What you expected would happen
|
||
|
|
- What actually happens
|
||
|
|
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
|
||
|
|
|
||
|
|
## Use a Consistent Coding Style
|
||
|
|
* 4 spaces for indentation rather than tabs
|
||
|
|
* Use a Python linter that will enforce PEP 8 and other best practices
|
||
|
|
|
||
|
|
## License
|
||
|
|
By contributing, you agree that your contributions will be licensed under its MIT License.
|