contributing.rst 2.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758
  1. Contributing to Docker
  2. ======================
  3. Want to hack on Docker? Awesome! There are instructions to get you
  4. started on the website: http://docker.io/gettingstarted.html
  5. They are probably not perfect, please let us know if anything feels
  6. wrong or incomplete.
  7. Contribution guidelines
  8. -----------------------
  9. Pull requests are always welcome
  10. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  11. We are always thrilled to receive pull requests, and do our best to
  12. process them as fast as possible. Not sure if that typo is worth a pull
  13. request? Do it! We will appreciate it.
  14. If your pull request is not accepted on the first try, don't be
  15. discouraged! If there's a problem with the implementation, hopefully you
  16. received feedback on what to improve.
  17. We're trying very hard to keep Docker lean and focused. We don't want it
  18. to do everything for everybody. This means that we might decide against
  19. incorporating a new feature. However, there might be a way to implement
  20. that feature *on top of* docker.
  21. Discuss your design on the mailing list
  22. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  23. We recommend discussing your plans `on the mailing
  24. list <https://groups.google.com/forum/?fromgroups#!forum/docker-club>`__
  25. before starting to code - especially for more ambitious contributions.
  26. This gives other contributors a chance to point you in the right
  27. direction, give feedback on your design, and maybe point out if someone
  28. else is working on the same thing.
  29. Create issues...
  30. ~~~~~~~~~~~~~~~~
  31. Any significant improvement should be documented as `a github
  32. issue <https://github.com/dotcloud/docker/issues>`__ before anybody
  33. starts working on it.
  34. ...but check for existing issues first!
  35. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  36. Please take a moment to check that an issue doesn't already exist
  37. documenting your bug report or improvement proposal. If it does, it
  38. never hurts to add a quick "+1" or "I have this problem too". This will
  39. help prioritize the most common problems and requests.
  40. Write tests
  41. ~~~~~~~~~~~
  42. Golang has a great testing suite built in: use it! Take a look at
  43. existing tests for inspiration.