Paste #ps1albdw1

  1. --- gentoo-coc.txt  2013-05-23 13:57:46.000000000 +0200
  2. +++ gentoo-coc.fixed.txt    2013-05-23 14:19:35.496004262 +0200
  3. @@ -1,167 +1,5 @@
  4.  ï»¿Gentoo Code of Conduct 0.2
  6. -Preamble
  7. ---------
  8. -
  9. -Gentoo is distribution developed world-wide. We all collaborate to improve
  10. -Gentoo and its usage.
  11. -
  12. -We strive for happy and friendly community that can embrace new ideas, improve
  13. -and foster collaboration among groups with different goals, interests and
  14. -needs.
  15. -
  16. -The Code of Conduct governs how we behave in public or in private whenever the
  17. -project will be judged by our actions. We expect it to be honored by everyone
  18. -who represent the project officially or informally, claim affiliation with
  19. -the project, or participate directly.
  20. -
  21. -Questions about this document and its contents can be directed to the Gentoo
  22. -council at council@gentoo.org.
  23. -
  24. -Overview
  25. ---------
  26. -
  27. -Basic social consents that our project works with are:
  28. -
  29. - - Be considerate
  30. - - Be responsible
  31. - - Be respectful
  32. - - Be collaborative
  33. - - Support others in the community and get support from them
  34. -
  35. -Be considerate
  36. ---------------
  37. -
  38. -As a contributor, ensure that you give full credit for the work of others and
  39. -bear in mind how your changes affect others. It is also expected that you try
  40. -to follow the development schedule and guidelines.
  41. -
  42. -As a user, remember that contributors work hard on their part of the
  43. -distribution and take great pride in it. If you are frustrated, your problems
  44. -are more likely to be resolved if you can give accurate and well-mannered
  45. -information to all concerned.
  46. -
  47. -Any decission we make will affect users and colleagues, and we should consider
  48. -them when making those decissions.
  49. -
  50. -Be responsible
  51. ---------------
  52. -
  53. -We can all make mistakes; when we do, we take responsibility for them. If
  54. -someone has been harmed or offended, we listen carefully and respectfully, and
  55. -work to right the wrong.
  56. -
  57. -Keep in mind that undoing one wrongdoing usually takes at least three
  58. -positive ones in the eyes of the harmed/offended person.
  59. -
  60. -Be respectful
  61. --------------
  62. -
  63. -In order for the Gentoo community to stay healthy, its members must feel
  64. -comfortable and accepted. Treating one another with respect is absolutely
  65. -necessary for this. In a disagreement, in the first instance assume that people
  66. -mean well.
  67. -
  68. -We do not tolerate personal attacks, racism, sexism or any other form of
  69. -discrimination. Disagreement is inevitable, from time to time, but respect for
  70. -the views of others will go a long way to winning respect for your own view.
  71. -
  72. -Respecting other people, their work, their contributions and assuming
  73. -well-meaning motivation will make community members feel comfortable and safe
  74. -and will result in motivation and productivity.
  75. -
  76. -We expect members of our community to be respectful when dealing with other
  77. -contributors, users and communities. Remember that Gentoo is an international
  78. -project and that you may be unaware of important aspects of other cultures.
  79. -
  80. -Be collaborative
  81. -----------------
  82. -
  83. -What we produce is a complex whole made of many parts, it is the sum of many
  84. -dreams. Collaboration between teams that each have their own goal and vision is
  85. -essential; for the whole to be more than the sum of its parts, each part must
  86. -make an effort to understand the whole.
  87. -
  88. -Collaboration reduces redundancy and improves the quality of our work.
  89. -Internally and externally, we celebrate good collaboration. Wherever possible,
  90. -we work closely with upstream projects and others in the free software
  91. -community to coordinate our efforts. We prefer to work transparently and
  92. -involve interested parties as early as possible.
  93. -
  94. -It may not always be possible to reach consensus on the implementation of an
  95. -idea, so don't feel obliged to achieve this before you begin. However, always
  96. -ensure that you keep others informed of your work, and publish it in
  97. -a way that allows outsiders to test, discuss and contribute to your efforts.
  98. -
  99. -Contributors on every project come and go. When you leave or disengage from the
  100. -project, in whole or in part, you should do so with pride about what you have
  101. -achieved and by acting responsibly towards others who come after you to
  102. -continue the project.
  103. -
  104. -As a user, your feedback is important, as is its form. Poorly thought out
  105. -comments can cause pain and the demotivation of other community members, but
  106. -considerate discussion of problems can bring positive results. An encouraging
  107. -word works wonders.
  108. -
  109. -Support others in the community and get support from them
  110. ----------------------------------------------------------
  111. -
  112. -If you witness others being attacked, think first about how you can offer them
  113. -personal support. If you feel that the situation is beyond your ability to help
  114. -individually, go privately to the victim and ask if some form of official
  115. -intervention is needed. Similarly you should support anyone who appears to be
  116. -in danger of burning out, either through work-related stress or personal
  117. -problems.
  118. -
  119. -When problems do arise, consider respectfully reminding those involved of our
  120. -shared Code of Conduct as a first action.
  121. -
  122. -Disagreements, both political and technical, happen all the time. Our community
  123. -is no exception to the rule. The goal is not to avoid disagreements or
  124. -differing views but to resolve them constructively.
  125. -
  126. -Think deeply before turning a disagreement into a public dispute. If you do
  127. -feel
  128. -that you or your work is being attacked, take your time to breathe through
  129. -before writing heated replies.
  130. -
  131. -
  132. -Examples of inappropriate behavior
  133. ------------------------------------
  134. -
  135. - - offensive verbal comments related to gender, sexual orientation, race,
  136. -   cultural background or other personal characteristics
  137. - - inappropriate jokes and insults
  138. - - sexual or racial images in public accessible areas (git, mailing-list, irc
  139. -   channels, ...)
  140. - - intentional off-topic communication (flame-wars) starting
  141. -
  142. -Consequences of such behaviour
  143. -------------------------------
  144. -
  145. -Disciplinary action will be up to the descretion of the proctors. What is a
  146. -proctor? A proctor is an official charged with the duty of maintaining good
  147. -order. Currently this responsibility falls to two existing Gentoo projects:
  148. -DevRel and UserRel.
  149. -
  150. -If you perceive a breach of the Code of Conduct guidelines, let the appropriate
  151. -proctors know. Though they will also be watching many of the public mediums for
  152. -any problems, they can not be expected to catch everything. If the offender is a
  153. -Gentoo developer, contact devrel@g.o, otherwise contact userrel@g.o.
  154. -
  155. -The proctors will attempt to resolve the problem by talking to involved parties,
  156. -potentially issuing warnings if appropriate. If the problem repeats itself,
  157. -there are various options open to the proctors, including temporary or permanent
  158. -suspension of a person's ability to post to mailing lists, removal of Bugzilla
  159. -access, or in more severe cases suspension of developer privileges.
  160. -
  161. -If discplinary measures are taken and the affected person wishes to appeal,
  162. -appeals should be addressed to the Gentoo Council via email at council@g.o. To
  163. -prevent conflicts of interest, Council members may not perform the duties of a
  164. -proctor.
  165. -
  166. -
  167. ---
  168. -Based on KDE, openSUSE, Ubuntu and former Gentoo CoC.
  169. +Don't be a dick and grow some balls.
  171.  Released under CC-SA 3.0