|
| 1 | +# Contributing |
| 2 | + |
| 3 | +Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given. |
| 4 | + |
| 5 | +You can contribute in many ways: |
| 6 | + |
| 7 | +## Types of Contributions |
| 8 | + |
| 9 | +### Report Bugs |
| 10 | + |
| 11 | +Report bugs at https://github.com/FragmentedPacket/net_backup/issues. |
| 12 | + |
| 13 | +If you are reporting a bug, please include: |
| 14 | + |
| 15 | +* Your operating system name and version. |
| 16 | +* Any details about your local setup that might be helpful in troubleshooting. |
| 17 | +* Detailed steps to reproduce the bug. |
| 18 | + |
| 19 | +### Fix Bugs |
| 20 | + |
| 21 | +Look through the GitHub issues for bugs. Anything tagged with "bug" |
| 22 | +is open to whoever wants to implement it. |
| 23 | + |
| 24 | +### Implement Features |
| 25 | + |
| 26 | +Look through the GitHub issues for features. Anything tagged with "feature" |
| 27 | +is open to whoever wants to implement it. |
| 28 | + |
| 29 | +### Write Documentation |
| 30 | + |
| 31 | +net_backup could always use more documentation, whether as part of the |
| 32 | +official net_backup docs, in docstrings, or even on the web in blog posts, |
| 33 | +articles, and such. |
| 34 | + |
| 35 | +### Submit Feedback |
| 36 | + |
| 37 | +The best way to send feedback is to file an issue at https://github.com/FragmentedPacket/net_backup/issues. |
| 38 | + |
| 39 | +If you are proposing a feature: |
| 40 | + |
| 41 | +* Explain in detail how it would work. |
| 42 | +* Keep the scope as narrow as possible, to make it easier to implement. |
| 43 | +* Remember that this is a volunteer-driven project, and that contributions |
| 44 | + are welcome :) |
| 45 | + |
| 46 | +## Get Started! |
| 47 | + |
| 48 | +Ready to contribute? Here's how to set up `net_backup` for local development. |
| 49 | + |
| 50 | +1. Fork the `net_backup` repo on GitHub. |
| 51 | +2. Clone your fork locally:: |
| 52 | +```bash |
| 53 | + $ git clone [email protected]:your_name_here/net_backup.git |
| 54 | +``` |
| 55 | +3. Create a branch for local development:: |
| 56 | +```bash |
| 57 | + $ git checkout -b name-of-your-bugfix-or-feature |
| 58 | +``` |
| 59 | + Now you can make your changes locally. |
| 60 | + |
| 61 | +4. When you're done making changes, check that your changes pass the tests:: |
| 62 | +```bash |
| 63 | + $ make test |
| 64 | +``` |
| 65 | +6. Commit your changes and push your branch to GitHub:: |
| 66 | +```bash |
| 67 | + $ git add . |
| 68 | + $ git commit -m "Your detailed description of your changes." |
| 69 | + $ git push origin name-of-your-bugfix-or-feature |
| 70 | +``` |
| 71 | +7. Submit a pull request through the GitHub website. |
| 72 | + |
| 73 | +Pull Request Guidelines |
| 74 | +----------------------- |
| 75 | + |
| 76 | +Before you submit a pull request, check that it meets these guidelines: |
| 77 | + |
| 78 | +1. The pull request should include tests. |
| 79 | +2. If the pull request adds functionality, the docs should be updated. Put |
| 80 | + your new functionality into a function with a docstring, and add the |
| 81 | + feature to the list in README.md. |
0 commit comments