CONTRIBUTING.rst 2.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107
  1. ============
  2. Contributing
  3. ============
  4. Contributions are welcome, and they are greatly appreciated! Every
  5. little bit helps, and credit will always be given.
  6. You can contribute in many ways:
  7. Types of Contributions
  8. ----------------------
  9. Report Bugs
  10. ~~~~~~~~~~~
  11. If you are reporting a bug, please include:
  12. * Your operating system name and version.
  13. * Any details about your local setup that might be helpful in troubleshooting.
  14. * Detailed steps to reproduce the bug.
  15. Fix Bugs
  16. ~~~~~~~~
  17. Look through the GitHub issues for bugs. Anything tagged with "bug"
  18. is open to whoever wants to implement it.
  19. Implement Features
  20. ~~~~~~~~~~~~~~~~~~
  21. Look through the GitHub issues for features. Anything tagged with "feature"
  22. is open to whoever wants to implement it.
  23. Write Documentation
  24. ~~~~~~~~~~~~~~~~~~~
  25. Infclass Muter could always use more documentation, whether as part of the
  26. official Infclass Muter docs, in docstrings, or even on the web in blog posts,
  27. articles, and such.
  28. Submit Feedback
  29. ~~~~~~~~~~~~~~~
  30. The best way to send feedback is to file an issue.
  31. If you are proposing a feature:
  32. * Explain in detail how it would work.
  33. * Keep the scope as narrow as possible, to make it easier to implement.
  34. * Remember that this is a volunteer-driven project, and that contributions
  35. are welcome :)
  36. Get Started!
  37. ------------
  38. Ready to contribute? Here's how to set up `infclass_muter` for local development.
  39. 1. Fork the `infclass_muter` repo
  40. 2. Clone your fork locally::
  41. $ git clone <...>
  42. 3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development::
  43. $ mkvirtualenv infclass_muter
  44. $ cd infclass_muter/
  45. $ python setup.py develop
  46. 4. Create a branch for local development::
  47. $ git checkout -b name-of-your-bugfix-or-feature
  48. Now you can make your changes locally.
  49. 5. When you're done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox::
  50. $ flake8 infclass_muter tests
  51. $ python setup.py test
  52. $ tox
  53. To get flake8 and tox, just pip install them into your virtualenv.
  54. 6. Commit your changes and push your branch to GitHub::
  55. $ git add .
  56. $ git commit -m "Your detailed description of your changes."
  57. $ git push origin name-of-your-bugfix-or-feature
  58. 7. Submit a pull request or send the patch
  59. Pull Request Guidelines
  60. -----------------------
  61. Before you submit a pull request, check that it meets these guidelines:
  62. 1. The pull request should include tests.
  63. 2. If the pull request adds functionality, the docs should be updated. Put
  64. your new functionality into a function with a docstring, and add the
  65. feature to the list in README.rst.
  66. Tips
  67. ----
  68. To run a subset of tests (that do not exist yet)::
  69. $ python -m unittest tests.test_infclass_muter