|
| 1 | +# Contributing to UNCode |
| 2 | +We love your input! We want to make contributing to this project as easy and |
| 3 | +transparent as possible, whether it's: |
| 4 | + |
| 5 | +- Reporting a bug. |
| 6 | +- Discussing the current state of the code. |
| 7 | +- Submitting a fix. |
| 8 | +- Proposing new features |
| 9 | + |
| 10 | +## Our Development Process |
| 11 | + |
| 12 | +We use github to host code, to track issues and feature requests, as well |
| 13 | +as accept pull requests. |
| 14 | + |
| 15 | +## Your First Contribution |
| 16 | + |
| 17 | +Unsure where to begin contributing to UNCode? You can start by looking through these beginner issues: |
| 18 | +**Good first issue** - issues which should only require a few lines of code and a not big understanding of UNCode. |
| 19 | + |
| 20 | +Working on your first Pull Request? You can learn how from this *free* series, |
| 21 | +[How to Contribute to an Open Source Project on GitHub][contribute_github_url]. |
| 22 | + |
| 23 | +## Pull Requests |
| 24 | + |
| 25 | +Pull requests are the best way to propose changes to the codebase |
| 26 | +(we use [Github Flow][github_flow_url]. |
| 27 | + |
| 28 | +We actively welcome your pull requests. |
| 29 | + |
| 30 | +1. Fork the repo (in case not an admin) and create your branch from `master`. |
| 31 | +2. If you've added code that should be tested, add tests. |
| 32 | +3. If you've changed APIs, update the documentation. |
| 33 | +4. Ensure the test suite passes. |
| 34 | +5. Be sure you have followed the code style for the project. |
| 35 | +6. If you haven't already, complete the Contributor License Agreement ("CLA"). Note the code of conduct. |
| 36 | +7. Create the pull request to `master` branch. |
| 37 | + |
| 38 | +### Code review |
| 39 | + |
| 40 | +UNCode team will check your pull request and one of us will be assigned to review it and |
| 41 | +leave feedback. Make to reply the given feedback ASAP. |
| 42 | + |
| 43 | +## Contributor License Agreement ("CLA") |
| 44 | +In order to accept your pull request, you will need to sign the Contributor License Agreement. |
| 45 | +Once the PR is created, you will be told whether or not you need to sign it and how to do it. |
| 46 | + |
| 47 | +## Issues |
| 48 | +We use GitHub issues to track public bugs or Feature Requests. Please ensure your description is |
| 49 | +clear and has sufficient instructions to be able to reproduce the issue. |
| 50 | + |
| 51 | +## License |
| 52 | +In short, when you submit code changes, your submissions are understood to be under the |
| 53 | +same [GNU][license_url] that covers the project. |
| 54 | +Feel free to contact the maintainers if that's a concern. |
| 55 | + |
| 56 | +## Community |
| 57 | + |
| 58 | +Chat with us on [Gitter][gitter_url]. |
| 59 | +We will reply for sure on weekdays at GMT-5 time. |
| 60 | + |
| 61 | +[contribute_github_url]: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github |
| 62 | +[github_flow_url]: https://guides.github.com/introduction/flow/index.html |
| 63 | +[license_url]: https://github.com/JuezUN/opt-cpp-backend/blob/master/LICENSE |
| 64 | +[gitter_url]: https://gitter.im/uncode-unal/community |
0 commit comments