{%extends "base/page.html"%}
{%block title%}Community{%endblock%}
{%block contents%}
-<div id="pgCommunityWrap">
-<div id="pgCommunity">
-<h1>Community</h1>
-
-<p>PostgreSQL is well supported by its active community. There are more than a dozen <a href="/community/lists/">mailing lists</a> available, categorized into topics like administration, announcements, jobs, performance, and SQL. We also have several PostgreSQL User Groups in the world, and there is also an active <a href="/community/irc/">IRC</a> community.</p>
-
-<p>In addition to the resources available on this site, there are also links to <a href="/community/international/">international sites</a> that contain PostgreSQL information in various languages. PostgreSQL community <a href="/community/resources/">resources</a> are also highlighted in this section of the website.</p>
-</div>
-</div>
-
-{%if survey%}
-<div id="pgSurveyWrap">
-<div id="pgSurvey">
- <dl>
- <dt>User Survey</dt>
- <dd>{{survey.question}}</dd>
- <dd>
- <form method="post" action="/community/survey/vote/{{survey.id}}/"><!-- CSRF exempt -->
+ <div class="row">
+ <div class="col-md-8">
+ <h1>Community <i class="fa fa-users"></i></h1>
<p>
- {%for q in survey.questions%}
- <input type="radio" name="answer" value="{{q.value}}" id="surv_opt_{{q.value}}" /><label for="surv_opt_{{q.value}}">{{q.text}}</label><br />
- {%endfor%}
+ PostgreSQL is well-supported by its active community. There are more than a dozen <a href="https://lists.postgresql.org/">mailing lists</a> available, categorized into topics like:
+ <ul>
+ <li><a href="/list/pgsql-announce/">Announcements</a></li>
+ <li><a href="/list/pgsql-hackers/">PostgreSQL development</a></li>
+ <li><a href="/list/pgsql-general/">General PostgreSQL Support</a></li>
+ <li><a href="/list/pgsql-jobs/">Jobs</a></li>
+ </ul>
+ and more. We also have many local <a href="/community/user-groups/">PostgreSQL User Groups</a> all over the world, and there is also an active <a href="/community/irc/">IRC</a> & <a href="https://postgres-slack.herokuapp.com/" target="_blank">Slack</a> community.
</p>
- <p><input id="surveySubmit" type="submit" name="submit" value="Vote" /></p>
- </form>
- </dd>
- <dd><a href="/community/survey/{{survey.id}}-{{survey|slugify}}/">Results</a></dd>
- </dl>
-</div>
-</div>
-{%endif%}
-
-<div id="pgPlanetWrap">
-<div id="pgPlanet">
- <dl>
- <dt>Planet PostgreSQL</dt>
- <dd><ul>
- {%for post in planet%}
- <li><a href="{{post.url}}">{{post.title}}</a></li>
- {%endfor%}
- </ul></dd>
- <dd><a href="https://planet.postgresql.org">More</a></dd>
- </dl>
-</div>
-</div>
-
+ <p>
+ There are also links to <a href="/community/international/">international sites</a> that contain PostgreSQL information in various languages.
+ </p>
+ <p>People in the PostgreSQL community also contribute to:</p>
+ <ul>
+ <li><a href="https://planet.postgresql.org/" target="_blank">Planet PostgreSQL</a>, an aggregator of blogs covering many topics around PostgreSQL</li>
+ <li><a href="https://wiki.postgresql.org" target="_blank">PostgreSQL Wiki</a>, our wiki, hosting user generated content as well as information for how to contribute code to PostgreSQL</li>
+ </ul>
+ </div>
+ <div class="col-md-4">
+ <h2>Planet PostgreSQL</h2>
+ <dl>
+ <dd><ul class="feature">
+ {% for post in planet %}
+ <li class="{% cycle '' 'pg-bg-gray' %}"><a href="{{ post.url }}">{{ post.title }}</a></li>
+ {%endfor%}
+ </ul></dd>
+ </dl>
+ <a href="https://planet.postgresql.org"><button type="button" class="btn btn-primary">More</button></a>
+ </div>
+ </div>
+ <div class="row">
+ <div class="col-md-8">
+ <h2>External Resources</h2>
+ <ul>
+ <li><a href="http://www.pg-forum.de/" target="_blank">pg-forum.de</a>, a German PostgreSQL forum.</li>
+ </ul>
+ <p>
+ Please send appropriate links to <a href="mailto:webmaster@postgresql.org">webmaster@postgresql.org</a> for possible inclusion on this page.
+ </p>
+ </div>
+ <div class="col-md-4">
+ <h2>Survey</h2>
+ {% if survey %}
+ <h3>{{survey.question}}</h3>
+ <form method="post" action="/community/survey/vote/{{survey.id}}/"><!-- CSRF exempt -->
+ <fieldset class="form-group">
+ {%for q in survey.questions%}
+ <div class="form-check">
+ <input id="surv_opt_{{q.value}}" class="form-check-input" type="radio" name="answer" value="{{ q.value }}" />
+ <label class="form-check-label" for="surv_opt_{{q.value}}">{{q.text}}</label>
+ </div>
+ {%endfor%}
+ </fieldset>
+ <div class="form-row">
+ <input class="btn btn-primary" type="submit" name="submit" value="Vote!" />
+ </div>
+ <div class="form-row">
+ <a href="/community/survey/{{survey.id}}-{{survey|slugify}}/"><button type="button" class="btn btn-primary">View Results</button></a>
+ </div>
+ </form>
+ {% endif %}
+ </div>
+ </div>
{%endblock%}
<h1>International Sites</h1>
-<p>Following are links to international PostgreSQL community websites.</p>
+<p>The following are links to international PostgreSQL community websites.</p>
-<div class="tblBasic">
-<table border="0" cellpadding="0" cellspacing="0" class="tblBasicGrey">
-<tr>
- <th class="colFirst">Community</th>
- <th class="colLast">Description</th>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://www.postgresql.org.br/">Brazilian</a></td>
- <td class="colLast">O centro de informações para os usuários brasileiros</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://www.postgres.cn/">Chinese (Simplified)</a></td>
- <td class="colLast">Simplified Chinese PostgreSQL Community</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://postgresql.tw/">Chinese (Traditional)</a></td>
- <td class="colLast">Traditional Chinese PostgreSQL Community</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://www.postgres.cz/">Czech</a></td>
- <td class="colLast">Informace o PostgreSQL v češtině</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://www.postgres.de/">Deutsch</a></td>
- <td class="colLast">Die Deutsche PostgreSQL Seite</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="https://www.postgresql.fr/">Français</a></td>
- <td class="colLast">La communaute Française de PostgreSQL</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://www.postgresql.org.il/">Israel</a></td>
- <td class="colLast">The Israeli PostgreSQL Community</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://www.psql.it/">Italiano</a></td>
- <td class="colLast">Comunità italiana di PostgreSQL </td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://www.itpug.org/">Italiano</a></td>
- <td class="colLast">Associazione ITPUG</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://www.postgresql.jp/">Japanese</a></td>
- <td class="colLast">The Japanese PostgreSQL Community</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://www.postgresql.kr/">Korean</a></td>
- <td class="colLast">The Korean PostgreSQL Community</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://www.postgresql.org.pl/">Polska</a></td>
- <td class="colLast">Informacje o PostgreSQL po polsku</td>
-</tr>
-<tr>
- <td class="colFirst"><a href="http://postgresql.ru.net/">Russian</a></td>
- <td class="colLast">A Russian community site</td>
-</tr>
-
-<tr class="lastrow">
- <td class="colFirst"><a href="http://www.postgresql.org.tr/">Türkce</a></td>
- <td class="colLast">Türkiye PostgreSQL Kullanıcıları Grubu</td>
-</tr>
+<table class="table table-striped">
+ <thead class="thead-light">
+ <tr>
+ <th scope="col">Community</th>
+ <th scope="col">Description</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><a href="http://www.postgresql.org.br/">Brazilian</a></td>
+ <td>O centro de informações para os usuários brasileiros</td>
+ </tr>
+ <tr>
+ <td><a href="http://www.postgres.cn/">Chinese (Simplified)</a></td>
+ <td>Simplified Chinese PostgreSQL Community</td>
+ </tr>
+ <tr>
+ <td><a href="http://postgresql.tw/">Chinese (Traditional)</a></td>
+ <td>Traditional Chinese PostgreSQL Community</td>
+ </tr>
+ <tr>
+ <td><a href="http://www.postgres.cz/">Czech</a></td>
+ <td>Informace o PostgreSQL v češtině</td>
+ </tr>
+ <tr>
+ <td><a href="http://www.postgres.de/">Deutsch</a></td>
+ <td>Die Deutsche PostgreSQL Seite</td>
+ </tr>
+ <tr>
+ <td><a href="https://www.postgresql.fr/">Français</a></td>
+ <td>La communaute Française de PostgreSQL</td>
+ </tr>
+ <tr>
+ <td><a href="http://www.postgresql.org.il/">Israel</a></td>
+ <td>The Israeli PostgreSQL Community</td>
+ </tr>
+ <tr>
+ <td><a href="http://www.psql.it/">Italiano</a></td>
+ <td>Comunità italiana di PostgreSQL </td>
+ </tr>
+ <tr>
+ <td><a href="http://www.itpug.org/">Italiano</a></td>
+ <td>Associazione ITPUG</td>
+ </tr>
+ <tr>
+ <td><a href="http://www.postgresql.jp/">Japanese</a></td>
+ <td>The Japanese PostgreSQL Community</td>
+ </tr>
+ <tr>
+ <td><a href="http://www.postgresql.kr/">Korean</a></td>
+ <td>The Korean PostgreSQL Community</td>
+ </tr>
+ <tr>
+ <td><a href="http://www.postgresql.org.pl/">Polska</a></td>
+ <td>Informacje o PostgreSQL po polsku</td>
+ </tr>
+ <tr>
+ <td><a href="http://postgresql.ru.net/">Russian</a></td>
+ <td>A Russian community site</td>
+ </tr>
+ <tr>
+ <td><a href="http://www.postgresql.org.tr/">Türkce</a></td>
+ <td>Türkiye PostgreSQL Kullanıcıları Grubu</td>
+ </tr>
+ </tbody>
</table>
-</div>
<p>If you know of an international PostgreSQL community site that isn't listed on this page, please contact <a href="mailto:webmaster@postgresql.org">webmaster@postgresql.org</a>.</p>
{%endblock%}
{%block title%}IRC{%endblock%}
{%block contents%}
-<h1>IRC</h1>
+<h1>IRC <i class="fas fa-comments"></i></h1>
<p>If you have a problem that you cannot resolve, you might want to try asking a question in our IRC channel
<a href="irc://irc.freenode.net/postgresql">#postgresql on irc.freenode.net</a>. The channel has many active users,
+++ /dev/null
-{%extends "base/page.html"%}
-{%block title%}Propaganda{%endblock%}
-{%block contents%}
-
-<h1>Propaganda</h1>
-
-<p><a href="http://www.templatemonster.com">Template Monster</a>, a graphics and website design company, has provided us with a number of updated PostgreSQL related graphics that you can use on your website. Right click on these images and select "Save As" to save the logo, then link them to the PostgreSQL home page at www.postgresql.org. You can also find more logos for different styles and colors, and the source files for these graphics, on our logo project page at <a href="http://pgfoundry.org/projects/graphics/">http://pgfoundry.org/projects/graphics/</a> in case you want to play around with them and maybe submit your own.
-</p>
-
-<table>
-<tr>
- <td>
- <img src="/files/community/propaganda/32x32_1.gif" alt="PostgreSQL logo" />
- <img src="/files/community/propaganda/32x32_2.gif" alt="PostgreSQL logo" />
- <img src="/files/community/propaganda/32x32_3.gif" alt="PostgreSQL logo" />
- </td>
- <td><ul><li>32 x 32 pixels</li><li>Web Icons</li><li>Elephant Style</li><li>GIF Format</li></ul></td>
-</tr>
-<tr><td colspan="2"><hr /></td></tr>
-<tr>
- <td>
- <img src="/files/community/propaganda/80x16_1.gif" alt="PostgreSQL logo" />
- <br />
- <img src="/files/community/propaganda/80x16_2.gif" alt="PostgreSQL logo" />
- <br />
- <img src="/files/community/propaganda/80x16_3.gif" alt="PostgreSQL logo" />
- </td>
- <td><ul><li>80 x 15 pixels</li><li>"PostgreSQL Powered" logo</li><li>Suitable for any background, usually used on blogs</li><li>GIF Format</li></ul></td>
-</tr>
-<tr><td colspan="2"><hr /></td></tr>
-<tr>
- <td><img src="/files/community/propaganda/88x31_2.gif" alt="PostgreSQL logo" /></td>
- <td><ul><li>88 x 31 pixels</li><li>"PostgreSQL Powered" logo</li><li>Text Style</li><li>GIF Format</li></ul></td>
-</tr>
-<tr><td colspan="2"><hr /></td></tr>
-<tr>
- <td><img src="/files/community/propaganda/95x51_4.gif" alt="PostgreSQL logo" /></td>
- <td><ul><li>95 x 51 pixels</li><li>"PostgreSQL Powered" logo</li><li>Elephant Style</li><li>GIF Format</li></ul></td>
-</tr>
-<tr><td colspan="2"><hr /></td></tr>
-<tr>
- <td><img src="/files/community/propaganda/95x51_6.gif" alt="PostgreSQL logo" /></td>
- <td><ul><li>95 x 51 pixels</li><li>"PostgreSQL Powered" logo</li><li>Turtle Style</li><li>GIF Format</li></ul></td>
-</tr>
-<tr><td colspan="2"><hr /></td></tr>
-<tr>
- <td><img src="/files/community/propaganda/100x58_1.gif" alt="PostgreSQL logo" /></td>
- <td><ul><li>100 x 58 pixels</li><li>"PostgreSQL Powered" logo</li><li>Elephant Style</li><li>GIF Format</li></ul></td>
-</tr>
-</table>
-
-<br />
-
-<!-- Creative Commons License -->
-These works are licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5 License</a>.
-<!-- /Creative Commons License -->
-
-<!--
-
-<rdf:RDF xmlns="http://web.resource.org/cc/"
- xmlns:dc="http://purl.org/dc/elements/1.1/"
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
-<Work rdf:about="">
- <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
- <license rdf:resource="http://creativecommons.org/licenses/by-sa/2.5/" />
-</Work>
-
-<License rdf:about="http://creativecommons.org/licenses/by-sa/2.5/">
- <permits rdf:resource="http://web.resource.org/cc/Reproduction" />
- <permits rdf:resource="http://web.resource.org/cc/Distribution" />
- <requires rdf:resource="http://web.resource.org/cc/Notice" />
- <requires rdf:resource="http://web.resource.org/cc/Attribution" />
- <permits rdf:resource="http://web.resource.org/cc/DerivativeWorks" />
- <requires rdf:resource="http://web.resource.org/cc/ShareAlike" />
-</License>
-
-</rdf:RDF>
-
--->
-
-{%endblock%}
{%block title%}Community Guidelines{%endblock%}
{%block contents%}
-<h1>Community Recognition Guidelines</h1>
+<h1>Community Recognition Guidelines <i class="fa fa-users"></i></h1>
<p>The PostgreSQL community is comprised of an international group of individuals and 3rd-party organisations who contribute to the PostgreSQL Development Group through various efforts. In order to help recognise the efforts of everyone contributing to the PostgreSQL project, the <a href="/developer/core/">PostgreSQL Core Committee</a> has put together a set of guidelines to fairly recognise these contributions to the community.</p>
<p>The following sections provide the guidelines for how various affiliates of the PostgreSQL community can qualify for official recognition by the PostgreSQL Development Group.</p>
-<p>
- <ul>
- <li>
- <a href="#npos">Recognised PostgreSQL Nonprofit Organisations (NPOs)</a>
- </li>
- <li>
- <a href="#conferences">Community Conference Recognition</a>
- </li>
- </ul>
-</p>
+<ul>
+ <li>
+ <a href="#npos">Recognised PostgreSQL Nonprofit Organisations (NPOs)</a>
+ </li>
+ <li>
+ <a href="#conferences">Community Conference Recognition</a>
+ </li>
+</ul>
<a name="npos" />
-<h1>Recognised PostgreSQL Nonprofit Organisations (NPOs)</h1>
-<p>Recognised PostgreSQL Nonprofit Organisations (NPOs) will be listed on the <a href="/">PostgreSQL Website</a> as such. To become recognised as an NPO, the organisation must self-certify that they meet the criteria below, aimed at ensuring they meet the standards of openness expected in the PostgreSQL Community.
-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>.
+<h2>Recognised PostgreSQL Nonprofit Organisations (NPOs)</h2>
+<p>Recognised PostgreSQL Nonprofit Organisations (NPOs) will be listed on the <a href="/">PostgreSQL Website</a> as such. To become recognised as an NPO, the organisation must self-certify that they meet the criteria below, aimed at ensuring they meet the standards of openness expected in the PostgreSQL Community.
+</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>
-<h2>Assessment Criteria</h2>
<h3>General</h3>
-<p>
- <ul>
- <li>A Code of Conduct should be adopted and apply to all members and directors.</li>
- <li>The organisation must be registered as a Non Profit Organisation in the territory in which it operates.</li>
- <li>No payments may be made to directors or members for their service with the exception of reimbursement of expenses incurred on the organisation's business, and sponsorship of conference attendance where deemed appropriate to help ensure the success of an event.</li>
- <li>The organisation must work towards the betterment of the PostgreSQL Project and/or community. It may not participate in any activities which may bring the project into disrepute or otherwise work against the interests of the project or the community.</li>
- <li>The <a href="/developer/core/">PostgreSQL Core Team</a> may recognise, not recognise, or rescind a previous recognition of any organisation without justification, regardless of whether or not the criteria above are met.</li>
- <li>These criteria may be reviewed and potentially updated at any time.</li>
- </ul>
-</p>
+<ul>
+ <li>A Code of Conduct should be adopted and apply to all members and directors.</li>
+ <li>The organisation must be registered as a Non Profit Organisation in the territory in which it operates.</li>
+ <li>No payments may be made to directors or members for their service with the exception of reimbursement of expenses incurred on the organisation's business, and sponsorship of conference attendance where deemed appropriate to help ensure the success of an event.</li>
+ <li>The organisation must work towards the betterment of the PostgreSQL Project and/or community. It may not participate in any activities which may bring the project into disrepute or otherwise work against the interests of the project or the community.</li>
+ <li>The <a href="/developer/core/">PostgreSQL Core Team</a> may recognise, not recognise, or rescind a previous recognition of any organisation without justification, regardless of whether or not the criteria above are met.</li>
+ <li>These criteria may be reviewed and potentially updated at any time.</li>
+</ul>
<h3>Membership</h3>
-<p>
- <ul>
- <li>Membership must be open to anyone, limited only to the geographic area in which the NPO operates or a specific spoken language, if desired.</li>
- <li>Membership must be at zero cost or a nominal cost (up to US $50 per year) to allow participation from any interested community members.</li>
- <li>Corporate memberships may be allowed, at higher cost than individual membership if desired, provided the same membership terms are available to any company.</li>
- <li>Membership must be renewed at least once every three years. "Lifetime" memberships must not be allowed.</li>
- </ul>
-</p>
+<ul>
+ <li>Membership must be open to anyone, limited only to the geographic area in which the NPO operates or a specific spoken language, if desired.</li>
+ <li>Membership must be at zero cost or a nominal cost (up to US $50 per year) to allow participation from any interested community members.</li>
+ <li>Corporate memberships may be allowed, at higher cost than individual membership if desired, provided the same membership terms are available to any company.</li>
+ <li>Membership must be renewed at least once every three years. "Lifetime" memberships must not be allowed.</li>
+</ul>
<h3>Directors</h3>
-<p>
- <ul>
- <li>The board of directors must be elected by the membership, and all members including any corporate members must have an equal vote.</li>
- <li>The board of directors should not consist of 50% or more directors working for the same company or group of companies under the same ultimate ownership or management, a situation which must be actively avoided as much as is possible. Should such a situation arise, for example, following the resignation of a director, an election should be held as soon as possible to restore the balance of the board.</li>
- <li>Director terms must last no longer than three years without re-election. A limit on the number of terms served may be set. "Lifetime" directorships must not be allowed.</li>
- </ul>
-</p>
+<ul>
+ <li>The board of directors must be elected by the membership, and all members including any corporate members must have an equal vote.</li>
+ <li>The board of directors should not consist of 50% or more directors working for the same company or group of companies under the same ultimate ownership or management, a situation which must be actively avoided as much as is possible. Should such a situation arise, for example, following the resignation of a director, an election should be held as soon as possible to restore the balance of the board.</li>
+ <li>Director terms must last no longer than three years without re-election. A limit on the number of terms served may be set. "Lifetime" directorships must not be allowed.</li>
+</ul>
<h3>Vetting</h3>
-<p>
- <ul>
- <li>Voting for the board of directors must be done in a way that may be externally vetted.</li>
- <li>Financial reports must be published at least annually for review by the membership.</li>
- <li>The organisation must make its financial reports and voting processes and records available to the <a href="/developer/core/">PostgreSQL Core Team</a> or their nominated representative for review if requested.</li>
- </ul>
-</p>
+<ul>
+ <li>Voting for the board of directors must be done in a way that may be externally vetted.</li>
+ <li>Financial reports must be published at least annually for review by the membership.</li>
+ <li>The organisation must make its financial reports and voting processes and records available to the <a href="/developer/core/">PostgreSQL Core Team</a> or their nominated representative for review if requested.</li>
+</ul>
<a name="conferences" />
-<h1>Community Conference Recognition</h1>
+<h2>Community Conference Recognition</h2>
<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>
-<h2>Assessment Criteria</h2>
<h3>General</h3>
-<p>
- <ul>
- <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>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>
-</p>
+<ul>
+ <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>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>
-<p>
- <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>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>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>
-</p>
+<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>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>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>
<h3>Sponsorship</h3>
-<p>
- <ul>
- <li>The sponsorship terms and/or prospectus must be published on the event website for public review.</li>
- <li>All sponsors of the same level or type must be treated equally; they must be offered the same benefits at the same cost as all others.</li>
- <li>Changes to the benefits offered should not be made following publication, and must not be made following the first executed sponsor agreement.</li>
- <li>There should not be an exclusive top sponsorship level.</li>
- <li>Sponsor benefits for all levels or types should include a listing on the event website. Ordering of the sponsor listing must be in randomised or predictable order with text stating how they are ordered, grouped by level or type of sponsorship.</li>
- <li>Sponsorship opportunities should be open to all, offered on a first-come, first-served basis. Limits on the number of any given level or type of sponsorship may be set.</li>
- <li>Only recognised sponsors may exhibit at the event, or be listed on the event website or other materials.</li>
- </ul>
-</p>
+<ul>
+ <li>The sponsorship terms and/or prospectus must be published on the event website for public review.</li>
+ <li>All sponsors of the same level or type must be treated equally; they must be offered the same benefits at the same cost as all others.</li>
+ <li>Changes to the benefits offered should not be made following publication, and must not be made following the first executed sponsor agreement.</li>
+ <li>There should not be an exclusive top sponsorship level.</li>
+ <li>Sponsor benefits for all levels or types should include a listing on the event website. Ordering of the sponsor listing must be in randomised or predictable order with text stating how they are ordered, grouped by level or type of sponsorship.</li>
+ <li>Sponsorship opportunities should be open to all, offered on a first-come, first-served basis. Limits on the number of any given level or type of sponsorship may be set.</li>
+ <li>Only recognised sponsors may exhibit at the event, or be listed on the event website or other materials.</li>
+</ul>
<h3>Financial</h3>
-<p>
- <ul>
- <li>The event organisers must provide copies of financial records to the <a href="/developer/core/">PostgreSQL Core Team</a> or their nominated representative for review if requested.</li>
- <li>
- A statement on the event website must indicate where any profits from the event will go, which specifically must support PostgreSQL community activities, either through:
- <ol>
- <li>a <a href="#npos">recognized PostgreSQL Nonprofit Organisation</a></li>
- <li>a detailed list of how the profits will support
- ongoing PostgreSQL Global Development Group development</li>
- <li>to the future growth and expansion of the event, OR</li>
- <li>a
- PostgreSQL-related activity that supports the community at-large
- that can be validated by the PostgreSQL Core Team</li>
- </ol>
- </li>
- </ul>
-</p>
+<ul>
+ <li>The event organisers must provide copies of financial records to the <a href="/developer/core/">PostgreSQL Core Team</a> or their nominated representative for review if requested.</li>
+ <li>
+ A statement on the event website must indicate where any profits from the event will go, which specifically must support PostgreSQL community activities, either through:
+ <ol>
+ <li>a <a href="#npos">recognized PostgreSQL Nonprofit Organisation</a></li>
+ <li>a detailed list of how the profits will support
+ ongoing PostgreSQL Global Development Group development</li>
+ <li>to the future growth and expansion of the event, OR</li>
+ <li>a
+ PostgreSQL-related activity that supports the community at-large
+ that can be validated by the PostgreSQL Core Team</li>
+ </ol>
+ </li>
+</ul>
{%endblock%}
+++ /dev/null
-{%extends "base/page.html"%}
-{%block title%}Resources{%endblock%}
-{%block contents%}
-<h1>Resources</h1>
-<p>Following are resources that may be of interest to the PostgreSQL community.</p>
-<h3>Community Resources</h3>
-<ul>
-<li><a href="https://planet.postgresql.org/">Planet PostgreSQL</a>, a site dedicated to aggregating PostgreSQL related blogs.</li>
-<li><a href="https://wiki.postgresql.org">PostgreSQL Wiki</a>, our wiki, hosting user created content and development related information</li>
-</ul>
-<h3>External Resources</h3>
-<ul>
-<li><a href="http://www.pg-forum.de/">pg-forum.de</a>, a German PostgreSQL forum.</li>
-<li><a href="http://www.pgsql.ru/">PGSearch</a>, a fast search engine (powered by PostgreSQL & TSearch2) indexing a number of PostgreSQL and PostgreSQL related websites.</li>
-</ul>
-<p>Please send appropriate links to <a href="mailto:webmaster@postgresql.org">webmaster@postgresql.org</a> for possible inclusion on this page.</p>
-{%endblock%}
{%extends "base/page.html"%}
{%block title%}Local PostgreSQL User Groups{%endblock%}
{%block contents%}
+<h1>Local User Groups <i class="fa fa-users"></i></h1>
-<h1>Local User Groups</h1>
<p>The PostgreSQL community is proud to have many local chapters that advocate and educate users about PostgreSQL. Below is a list of PostgreSQL User Groups (PUGs) sorted by country and local area. If you would like to start a PostgreSQL User Group, please send an email to <a href="mailto:usergroups@postgresql.org">usergroups@postgresql.org</a> and describe the PUG that you want to create.</p>
<p>If a PUG already exists in your area, follow the URLs below to find out how to attend and participate.</p>
{% for pug_group in pug_list %}
<h2>{{ pug_group.country }}</h2>
- <p>
- <ul>
- {% for pug in pug_group.pugs %}
- <li>
- <strong>{{ pug.locale }}</strong>:
- {{ pug.title }}
- {% if pug.website_url %}
- (<a href="{{ pug.website_url }}">website</a>)
- {% endif %}
- {% if pug.mailing_list_url %}
- (<a href="{{ pug.mailing_list_url }}">mailing list</a>)
- {% endif %}
- </li>
- {% endfor %}
- </ul>
- </p>
+ <ul>
+ {% for pug in pug_group.pugs %}
+ <li>
+ <strong>{{ pug.locale }}</strong>:
+ {% if pug.website_url %}
+ <a href="{{ pug.website_url }}" target="_blank">
+ {% endif %}
+ {{ pug.title }}
+ {% if pug.website_url %}
+ </a>
+ {% endif %}
+ {% if pug.website_url %}
+ (<a href="{{ pug.website_url }}" target="_blank">website</a>)
+ {% endif %}
+ {% if pug.mailing_list_url %}
+ (<a href="{{ pug.mailing_list_url }}" target="_blank">mailing list</a>)
+ {% endif %}
+ </li>
+ {% endfor %}
+ </ul>
{% endfor %}
-
-<h1>PostgreSQL Nonprofit Organisation (NPO) Recognition</h1>
-<p>For information about how <a href="/community/recognition/#npos">Recognised PostgreSQL Nonprofit Organizations (NPOs)</a> become recognised, please review the guidelines <a href="/community/recognition/#npos">here</a>.
{%endblock%}
projects / pgweb.git / commitdiff