templates/pages/about/policies/coc.html

   1 {%extends "base/cocpage.html"%}
   2 {%load pgfilters%}
   3 {%block title%}Code of Conduct{%endblock%}
   4 {%block cocmain%}
   5     <h1>Code of Conduct <i class="fas fa-gavel"></i></h1>
   6
   7     <p><em>Last updated: October 4, 2024. {%git_changes_link%}</em></p>
   8
   9
  10     <h2>Introduction</h2>
  11
  12     <p>The PostgreSQL Project prides itself on the quality of our code and our work,
  13         and the technical and professional accomplishments of our community. We
  14         expect everyone who participates to conduct themselves in a professional
  15         manner, acting with common courtesy and in the common interest, with respect
  16         for all users and developers.</p>
  17
  18     <p>To that end, we have established this Code of Conduct for community
  19         interaction and participation in the project’s work and the community at
  20         large. This Code is meant to cover all interaction between community
  21         members, whether or not it takes place within postgresql.org infrastructure,
  22         so long as there is not another Code of Conduct that takes precedence (such
  23         as a conference's Code of Conduct).</p>
  24
  25     <h2>Inclusivity and Appropriate Conduct</h2>
  26
  27     <p>The PostgreSQL Project is open to participation by anyone with an interest in
  28         working with PostgreSQL, regardless of their level of experience with the
  29         software, or with technology in general. We encourage development and
  30         contributions from all users, whatever their background may be.</p>
  31
  32     <p>We encourage thoughtful, constructive discussion of the software and this
  33         community, their current state, and possible directions for development. The
  34         focus of our discussions should be the code and related technology,
  35         community projects, and infrastructure.</p>
  36
  37     <p>Personal attacks and negative comments on personal characteristics are
  38         unacceptable, and will not be permitted. Examples of personal
  39         characteristics include, but are not limited to age, race, national origin
  40         or ancestry, religion, gender, or sexual orientation.</p>
  41
  42     <p>Additional behaviors which are also violations of this code of conduct
  43         include, but are not limited to, threats of violence against an individual
  44         or group, threats of professional, community, and/or project sabotage,
  45         unwelcome sexual attentions in any form, engaging in behavior that may
  46         bring the PostgreSQL project into disrepute, and refusing to cease
  47         inappropriate conduct when requested to do so.</p>
  48
  49     <h2>Retaliation</h2>
  50
  51     <p>It is also expressly forbidden for anyone to retaliate against a person who
  52         brings a complaint under this Code of Conduct, or who assists in
  53         investigating such a complaint. Retaliation may take the form of, among
  54         other actions:</p>
  55
  56     <ul>
  57         <li>further personal attacks (public or private);</li>
  58         <li>actions which undermine an individual's professional status and/or
  59             status with their employer, coworkers, clients, or community;</li>
  60         <li>actions which threaten the individual's privacy, physical person,
  61             well-being, home, and/or family.</li>
  62     </ul>
  63
  64     <p>Acts of retaliation will be treated in the same manner as any other violation
  65         of this Code of Conduct.</p>
  66
  67     <h2>Code of Conduct Committee</h2>
  68
  69     <p>The Core Team will appoint a Code of Conduct Committee to receive and
  70         investigate all complaints, and a Chair for that Committee. Any member of
  71         the community may volunteer to be on the Committee, with the exception of
  72         Core Team members. As the Core Team oversees the Committee, Core Team
  73         members will not serve on the Committee to prevent conflicts of interest.
  74         The membership list of the Committee will be publicly available at all times
  75         and can be viewed <a href="/about/policies/coc_committee/">here</a>.</p>
  76
  77     <p>The Committee membership will be refreshed on an annual basis. The Core Team
  78         or the Committee Chair will announce the opening and closing dates of the
  79         annual membership selection process through the usual community channels of
  80         communication.</p>
  81
  82     <p>Any community member who would like to serve on the Committee will complete
  83         an initial questionnaire for review by the Core Team and the current
  84         Committee. The current Committee members will review the candidates, and
  85         conduct interviews if needed. The current Committee will make
  86         recommendations, and the Core Team will choose the new members for the
  87         Committee.</p>
  88
  89     <p>The Committee may have a transition period of up to one month to allow
  90         transfer of knowledge and responsibilities between the retiring members
  91         and the new members.</p>
  92
  93     <p>While there is no specified number of Committee members who may serve at any
  94         one time, the Committee will consist of at least four individuals at all
  95         times. A term for a Committee member is one (1) year. A Committee member
  96         may serve no more than three (3) terms consecutively.</p>
  97
  98     <p>Committee members serve at the pleasure of the Core Team, and the Core Team
  99         may relieve a Committee member of their duties if the Core Team believes
 100         that member is not meeting the responsibilities of their position.</p>
 101
 102     <p>The Committee may also approach the Core Team to coordinate removal of a
 103         member on their own initiative if such person is unable or unwilling to
 104         fulfill the responsibilities of their position.</p>
 105
 106     <h2>Reporting</h2>
 107
 108     <p>If you are the recipient of inappropriate behavior, or witness such behavior,
 109         please report it promptly to the Code of Conduct Committee at
 110         <a href="mailto:coc@postgresql.org">coc@postgresql.org</a>. In the
 111         unfortunate event that you wish to make a complaint against some member of
 112         the Committee, you may instead contact any of the other Committee member(s)
 113         individually.</p>
 114
 115     <p>In your report, please include as much detail as possible:</p>
 116
 117     <ul>
 118         <li>a description of the incident;</li>
 119         <li>the timing of events;</li>
 120         <li>screen shots of any electronic discussions;</li>
 121         <li>names, and if possible, contact information for any witnesses; and,</li>
 122         <li>any other information which you think would be helpful in the investigation.</li>
 123     </ul>
 124
 125     <h2>Handling of Complaints</h2>
 126
 127     <p>The Committee will promptly acknowledge and investigate each reported
 128         incident. With the cooperation of all parties, the Committee will aim to
 129         complete the investigation in a period of two weeks from the receipt of the
 130         complaint.</p>
 131
 132     <p>Incident reports and investigation activities will be kept confidential to
 133         the extent possible, consistent with the need to conduct an adequate
 134         investigation.</p>
 135
 136     <p>The Committee will inform the complainant and the alleged violator of their
 137         decision at that time. If the investigation is still ongoing, the Committee
 138         will give the parties a status report and an estimated completion date.</p>
 139
 140     <p>A lack of cooperation could prolong the investigation. The Committee will
 141         make every effort to complete the investigation and deliver the results to
 142         the complainant and the alleged violator as soon as practicable, notifying
 143         them of its decision when the investigation is completed.</p>
 144
 145     <p>In the event of a complaint by or against a CoC Committee member or Core Team
 146         member, the complaint handling will proceed as usual, with the exception
 147         that the person who is involved in the complaint will be excluded from the
 148         proceedings in their role on the Committee or Core Team.</p>
 149
 150     <p>Possible results include, but are not limited to:</p>
 151
 152     <ul>
 153         <li>A determination of no violation of the Code of Conduct;</li>
 154         <li>A private reprimand with specific guidance on acceptable behavior to the
 155             individual(s) involved;</li>
 156         <li>A public reprimand with specific guidance on acceptable behavior to the
 157             individual(s);</li>
 158         <li>A temporary or permanent ban from some or all community-managed spaces,
 159             including, but not limited to, community mailing lists, forums, IRC, and
 160             loss of commit privileges;</li>
 161         <li>A determination for a public and/or private apology.</li>
 162     </ul>
 163
 164     <p>Because of the seriousness of a determination involving a temporary or
 165         permanent ban, and the associated technical and infrastructure actions
 166         required by such a result, such a finding would be subject to review by the
 167         Core Team before the involved parties are informed of the decision. If the
 168         Core Team disagrees with the Committee's finding, the Core Team would
 169         present its reasoning to the Committee. The Committee would consider the
 170         Core Team's recommendations, and engage in further discussion if needed.
 171         If the Core Team and Committee cannot agree on a determination, the Core
 172         Team's decision would prevail.</p>
 173
 174     <p>The Committee may determine that a violation of this policy was inadvertent,
 175         perhaps arising from cultural differences (for example, use of a slang term
 176         which is harmless in one language and offensive in another) or a misguided
 177         attempt at humor. Such cases will be treated as opportunities for education
 178         rather than reprimand. If the Committee determines that a reported incident
 179         falls into the category of inadvertent violation, the Committee will decide
 180         whether the incident is likely to be repeated by others, and, if so, share
 181         the information in a general way with the community to prevent further
 182         incidents.</p>
 183
 184     <p>If either party feels the determination is incorrect, an appeal may be filed
 185         with the Committee within one week of its decision. The appeal should
 186         include new information, sources, witnesses, etc. to provide the Committee
 187         with additional information to re-consider the incident.</p>
 188
 189     <p>Records of incident reports, investigations, Committee decisions, and all
 190         related matters will be retained for a period of three calendar years from
 191         the date of the last item in the incident file. The Committee will take
 192         suitable measures to ensure the confidentiality of all reports and
 193         discussions.</p>
 194
 195     <p>The Committee will produce an annual report summarizing the types of
 196         complaints received and the actions taken to address the complaints by the
 197         end of the first quarter of each year for the prior year, and share that
 198         report with the community. The complaints and actions will be anonymized to
 199         protect the identities of all involved parties.</p>
 200
 201     <h2>Acting in Good Faith</h2>
 202
 203     <p>Anyone filing a complaint concerning an incident is expected to be acting in
 204         good faith and have reasonable grounds for believing the information
 205         disclosed indicates a violation of this policy. Any allegations that prove
 206         not to be substantiated, and which prove to have been made maliciously or
 207         knowingly to be false, will be viewed as a serious community offense and a
 208         violation of this Code of Conduct.</p>
 209
 210     <h2>Updates to the Code of Conduct</h2>
 211
 212     <p>The Committee and/or the Core Team will consider updates to this Code of
 213         Conduct as needed, and at least once per year, based on incidents reported,
 214         recommendations from legal professionals, suggestions from community
 215         members, community cultural developments, or other events which create a
 216         need for revision.</p>
 217
 218     <p>Community members who have a suggestion for a revision to the Code of Conduct
 219         may submit their ideas to the Committee via email to
 220         <a href="mailto:coc@postgresql.org">coc@postgresql.org</a>.</p>
 221
 222     <h2>Conferences and Events</h2>
 223
 224     <p>The project encourages each event organizer to create and maintain a Code of
 225         Conduct for their event. Those Codes of Conduct may or may not be identical
 226         to this Code of Conduct. Each event organizer is responsible for handling
 227         inappropriate conduct at their event in a prompt and objective manner.</p>
 228
 229     <h2>Conclusion</h2>
 230
 231     <p>We encourage appropriate and collegial relationships among community members;
 232         however, members must be sensitive to conduct that may be considered
 233         offensive by fellow members and must refrain from engaging in such
 234         conduct.</p>
 235
 236     <p>In all interactions with the community, use your professional judgment, and
 237         keep the discussion focused on moving our project and our community forward
 238         in a positive direction for all.</p>
 239
 240     <h2>Licence</h2>
 241
 242     <p>
 243         The PostgreSQL Code of Conduct is released under the
 244         <a href="/about/licence/">PostgreSQL Licence</a>.
 245     </p>
 246 {%endblock%}