CONTRIBUTING.rst 2.5 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. Contributing
  2. ============
  3. Quick Links for Contributing
  4. ----------------------------
  5. - Compiling and building OBS Studio:
  6. https://github.com/obsproject/obs-studio/wiki/Install-Instructions
  7. - Our bug tracker:
  8. https://github.com/obsproject/obs-studio/issues
  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. - To add a new service to OBS Studio please see the service submission guidelines:
  19. https://github.com/obsproject/obs-studio/wiki/Service-Submission-Guidelines
  20. Coding Guidelines
  21. -----------------
  22. - OBS Studio uses kernel normal form (linux variant), for more
  23. information, please read here:
  24. https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst
  25. - Avoid trailing spaces. To view trailing spaces before making a
  26. commit, use "git diff" on your changes. If colors are enabled for
  27. git in the command prompt, it will show you any whitespace issues
  28. marked with red.
  29. - Tabs for indentation, spaces for alignment. Tabs are treated as 8
  30. columns wide.
  31. - 80 columns max
  32. Commit Guidelines
  33. -----------------
  34. - OBS Studio uses the 50/72 standard for commits. 50 characters max
  35. for the title (excluding module prefix), an empty line, and then a
  36. full description of the commit, wrapped to 72 columns max. See this
  37. link for more information: http://chris.beams.io/posts/git-commit/
  38. - Make sure commit titles are always in present tense, and are not
  39. followed by punctuation.
  40. - Prefix each commit's titles with the module name, followed by a colon
  41. and a space (unless modifying a file in the base directory). After
  42. that, the first word should be capitalized.
  43. So for example, if you are modifying the obs-ffmpeg plugin::
  44. obs-ffmpeg: Fix bug with audio output
  45. Or for libobs::
  46. libobs: Fix source not displaying
  47. Note: When modifying cmake modules, just prefix with "cmake".
  48. - If you still need examples, please view the commit history.
  49. Conduct Guidelines
  50. ------------------
  51. - Contributors to the OBS Project are expected to abide by the OBS Project Code of Conduct: https://github.com/obsproject/obs-studio/blob/master/COC.rst