Update community conference guidelines, per agreement with -core.

diff --git a/templates/pages/community/recognition.html b/templates/pages/community/recognition.html
index 6447656317519c69509e8dd18450ad3267873224..207cac63c8c8fb1383ab54dcce491c1fcd93637b 100644 (file)
--- a/templates/pages/community/recognition.html
+++ b/templates/pages/community/recognition.html
@@ -61,8 +61,12 @@
 
 <a name="conferences" />
 <h2>Community Conference Recognition</h2>
+<p><em>Last updated: July 15, 2019</em></p>
+
 <p>The Community Conference Recognition programme is a voluntary scheme under which submitters of events to the <a href="/about/events/">PostgreSQL Website listings</a> may self-assess their entry against the criteria below, and if they comply may market their event as a PostgreSQL Community event.</p>
+
 <p>Events that do not meet the criteria will still be welcomed (where appropriate under the <a href="https://wiki.postgresql.org/wiki/NewsEventsApproval#Approving_Events_and_Event-Related_News_.28excluding_training.29" target="_blank">general listing policies</a>) - for example, events organised by a single company which may still be valuable for people to attend, but are not necessarily what we would consider fully "open."</p>
+
 <p>Use of the terms "MUST", "MUST NOT", "SHOULD" and "SHOULD NOT" in the criteria below should be interpreted per <a href="https://www.ietf.org/rfc/rfc2119.txt" target="_blank">RFC2119</a>.</p>
 
 <h3>General</h3>
@@ -70,18 +74,33 @@
   <li>The event MUST be primarily focused on PostgreSQL and targeted at existing and/or potential developers and users of PostgreSQL.</li>
   <li>The event MUST adopt and follow an appropriate Code of Conduct to ensure a safe and enjoyable environment for anyone who wishes to attend.</li>
   <li>The <a href="/developer/core/">PostgreSQL Core Team</a> reserves the right to recognise, not recognise, or rescind a previous recognition for any event without justification.</li>
+  <li>Information that is required to be publicly disclosed MUST be available on the website of the event, or, if it is not possible to publish to the event’s website, MUST be made available in the <a href="/about/events/">PostgreSQL Website events list</a>.</li>
   <li>Events are self-certified as complying with these criteria when <a href="/about/events/">listed on the PostgreSQL Website</a>. If an event is self-certified by the organisers and later found not to comply with the criteria, the <a href="/developer/core/">PostgreSQL Core Team</a> reserves the right to rescind the recognition of the event as a community event and, where appropriate, take further action up to a permanent ban on future event listings from the organisers.</li>
   <li>These criteria may be reviewed and potentially updated at any time.</li>
 </ul>
 
-<h3>Talk selection</h3>
+<h3>Organisers</h3>
+<ul>
+  <li>The organizing committee (also referred to as a steering committee) MUST be fully disclosed on the event website OR the PostgreSQL Website event listing.</li>
+  <li>The organizing committee SHOULD NOT consist of 50% or more members from a single company or group of companies under the same ultimate ownership or management.</li>
+  <li>Any benefits granted to the companies that employ the organisers MUST be considered sponsorship benefits.</li>
+  <li>
+    The organizing committee MUST either:
+    <ul>
+      <li>Establish a code of conduct committee. The code of conduct committee MUST include at least one person who is not on the organizing committee. The membership of the code of conduct committee MUST be published. OR</li>
+      <li>Adopt the <a href="/about/policies/coc/">PostgreSQL Code of Conduct</a> and refer code of conduct complaints to the <a href="/about/policies/coc_committee/">PostgreSQL Code of Conduct Committee</a>.</li>
+    </ul>
+  </li>
+</ul>
+
+<h3>Talk Selection</h3>
 <ul>
   <li>The talk selection committee MUST be fully disclosed on the event website.</li>
   <li>The talk selection committee MUST NOT consist of 50% or more members from a single company or group of companies under the same ultimate ownership or management.</li>
-  <li>All members of the talk committee MUST have an equal vote (except in case of a tie-breaker).</li>
+  <li>All members of the talk committee MUST have an equal vote.</li>
   <li>The Call For Papers MUST be open for anyone to submit.</li>
-  <li>Solicited or sponsor keynote presentations may bypass the normal talk selection process, but their topics MUST be approved by a majority of the talk committee.</li>
-  <li>The full talk selection process and voting system MUST be fully disclosed to all members of the talk committee.</li>
+  <li>Solicited or sponsor presentations may bypass the normal talk selection process, but MUST be approved by a majority of the talk selection committee.</li>
+  <li>The full talk selection process and voting system MUST be fully disclosed to all members of the talk selection committee.</li>
   <li>Details of the talk selection process and how results were obtained MUST be provided to the <a href="/developer/core/">PostgreSQL Core Team</a> on request.</li>
 </ul>