COC.rst 6.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153
  1. Code of Conduct
  2. ===============
  3. Preamble
  4. --------
  5. OBS is made up of many people from all over the world, with different
  6. backgrounds and experiences that they bring to the project. In order to
  7. continue letting the community grow, feel safe, and to encourage good
  8. communication, we are adopting the following Code of Conduct. This
  9. document—or any subsequent version—will be enforced from July 31st, 2021
  10. onwards.
  11. Scope
  12. -----
  13. This Code of Conduct applies to anyone who contributes—or wishes to
  14. contribute—to the project directly, is taking part in community
  15. discussion in official channels, or are in a position where they’ll be
  16. seen as a representative of the project, regardless of whether they
  17. intend to speak for the project or not.
  18. A person is considered to be representing the project if they’re
  19. speaking as a code contributor, support volunteer, member involved with
  20. the project, or if they have some kind of visible role in an official
  21. channel for OBS. This does not include roles for Sponsors or Patrons.
  22. Official channels for OBS include the Discord server, the forum, any
  23. GitHub repositories within the OBS Project organization, any social
  24. media accounts for OBS Project, any public events where OBS Project has
  25. a presence, any presentations given on behalf of OBS Project, or any
  26. other situation that can be reasonably interpreted as being hosted,
  27. attended or communicated by the OBS Project.
  28. This Code of Conduct is subject to change, and any changes will have a 2
  29. week notice period before taking immediate effect. Changes will not be
  30. enforced retroactively unless it directly affects the security, safety
  31. or well-being of another individual, or other exceptional circumstances.
  32. Guidelines
  33. ----------
  34. General
  35. ~~~~~~~
  36. - We are committed to providing a friendly, safe and welcoming
  37. environment for all, regardless of level of experience, gender
  38. identity and expression, sexual orientation, disability, personal
  39. appearance, body size, race, ethnicity, age, religion, nationality,
  40. or other similar characteristic.
  41. - Please avoid using overtly sexual aliases or other nicknames that
  42. might detract from a friendly, safe and welcoming environment for
  43. all.
  44. - Please be kind and courteous. There’s no need to be mean or rude.
  45. - Respect that people will have differences of opinion.
  46. - We will exclude you from interaction if you insult, demean or harass
  47. anyone. That is not welcome behavior. The definition of harassment is
  48. provided in the section on Unacceptable Behavior. In particular, we
  49. don’t tolerate behavior that excludes people in socially marginalized
  50. groups. This includes private harassment.
  51. - Likewise any spamming, trolling, flaming, baiting or other
  52. attention-stealing behavior is not welcome.
  53. - Being a recognized Contributor, Support Volunteer, Sponsor or Patron
  54. does not give you special right to avoid following these guidelines
  55. when taking part in community discussions.
  56. Code Contributors
  57. ~~~~~~~~~~~~~~~~~
  58. - Respect that every design or implementation choice carries a
  59. trade-off and numerous costs. There is seldom a right answer.
  60. - Please keep unstructured critique to a minimum. If you have solid
  61. ideas you want to experiment with, make a fork and see how it works.
  62. - Do not post negative or inflammatory comments on code submissions. If
  63. you believe that a code submission has problems, provide constructive
  64. or actionable feedback, or a reason for why a submission is being
  65. rejected. Where it is possible, provide explanations that someone can
  66. use to fix things.
  67. Support Volunteers
  68. ~~~~~~~~~~~~~~~~~~
  69. - There are many users of differing skill levels or abilities. This is
  70. never a reason to refuse support for someone, as long as it’s within
  71. the scope of OBS support, and the user is willing to cooperate.
  72. - Just because something seems obvious to you, doesn’t mean it’s
  73. actually obvious. If someone is having difficulty understanding how
  74. to use OBS, it should never be treated as their fault.
  75. - Bad advice is often worse than no advice. If you don’t know how to
  76. address someone’s issue, then get ahold of someone who’ll be able to
  77. provide them help. We can only expect so much patience from a user
  78. asking for support, and helping without understanding the problem
  79. only results in using up that patience.
  80. Unacceptable Behavior
  81. ---------------------
  82. The following behaviors are considered harassment and are unacceptable
  83. within our community:
  84. - Violence, threats of violence or violent language directed against
  85. another person.
  86. - Sexist, racist, homophobic, transphobic, ableist or otherwise
  87. discriminatory jokes and language.
  88. - Posting or displaying sexually explicit or violent material.
  89. - Posting or threatening to post other people’s personally identifying
  90. information ("doxing").
  91. - Personal insults.
  92. - Unwelcome sexual attention. This includes, sexualized comments or
  93. jokes, and unwelcome sexual advances.
  94. - Deliberate intimidation, stalking or following.
  95. - Advocating for, or encouraging, any of the above behavior.
  96. Enforcement
  97. -----------
  98. Instances of unacceptable behavior may be reported by contacting an
  99. enforcement team member at one of the following addresses:
  100. [email protected]. All complaints will be reviewed and investigated,
  101. and will result in a response that is deemed necessary and appropriate
  102. to the circumstances. The project team is obligated to maintain
  103. confidentiality with regard to the reporter of an incident. Further
  104. details of specific enforcement policies may be posted separately.
  105. In other cases where behavior is against the general guidelines set out
  106. in this Code of Conduct, this may be brought up with a moderator through
  107. either a Discord DM, or through an email to an enforcement member. In
  108. these cases, it is always assumed in the first instance that a person
  109. means well, and action will only be taken in the case of repeated
  110. failure to follow the guidelines.
  111. Feedback
  112. --------
  113. Suggestions for changes can be made by submitting a pull request on the
  114. `obsproject/obs-studio <https://github.com/obsproject/obs-studio>`__
  115. repo, or if you wish to privately discuss your concerns, you can instead
  116. email [email protected].
  117. Attribution
  118. -----------
  119. This Code of Conduct is adapted in part from the Contributor Covenant,
  120. version 1.4, in part from the Citizen Code of Conduct (used under
  121. CC-BY-SA 3.0), and in part from the Rust Code of Conduct.
  122. This Code of Conduct is released and licensed under a Creative Commons
  123. Attribution-ShareAlike 3.0 License.
  124. Version History
  125. ---------------
  126. V1.0 - First Iteration - July 31st, 2021