CONTRIBUTING.rst 2.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869
  1. Contributing
  2. ============
  3. Quick Links for Contributing
  4. ----------------------------
  5. - Compiling and building OBS Studio:
  6. https://github.com/jp9000/obs-studio/wiki/Install-Instructions
  7. - Our bug tracker (linked to forum accounts):
  8. https://obsproject.com/mantis/
  9. - Discord Server: https://obsproject.com/discord
  10. - Development chat: #development on the Discord server (see above)
  11. - Development forum:
  12. https://obsproject.com/forum/list/general-development.21/
  13. - Developer/API Documentation:
  14. https://obsproject.com/docs
  15. - To contribute language translations, do not make pull requests.
  16. Instead, use crowdin. Read here for more information:
  17. https://obsproject.com/forum/threads/how-to-contribute-translations-for-obs.16327/
  18. Coding Guidelines
  19. -----------------
  20. - OBS Studio uses kernel normal form (linux variant), for more
  21. information, please read here:
  22. https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst
  23. - Avoid trailing spaces. To view trailing spaces before making a
  24. commit, use "git diff" on your changes. If colors are enabled for
  25. git in the command prompt, it will show you any whitespace issues
  26. marked with red.
  27. - Tabs for indentation, spaces for alignment. Tabs are treated as 8
  28. columns wide.
  29. - 80 columns max
  30. Commit Guidelines
  31. -----------------
  32. - OBS Studio uses the 50/72 standard for commits. 50 characters max
  33. for the title (excluding module prefix), an empty line, and then a
  34. full description of the commit, wrapped to 72 columns max. See this
  35. link for more information: http://chris.beams.io/posts/git-commit/
  36. - Make sure commit titles are always in present tense, and are not
  37. followed by punctuation.
  38. - Prefix each commit's titles with the module name, followed by a colon
  39. and a space (unless modifying a file in the base directory). After
  40. that, the first word should be capitalized.
  41. So for example, if you are modifying the obs-ffmpeg plugin::
  42. obs-ffmpeg: Fix bug with audio output
  43. Or for libobs::
  44. libobs: Fix source not displaying
  45. Note: When modifying cmake modules, just prefix with "cmake".
  46. - If you still need examples, please view the commit history.