('website_url', models.TextField(null=True, blank=True)),
('mailing_list_url', models.TextField(null=True, blank=True)),
('country', models.ForeignKey(to='core.Country')),
- ('org', models.ForeignKey(blank=True, to='core.Organisation', help_text=b'Organization that manages the PUG and its contents', null=True)),
+ ('org', models.ForeignKey(blank=True, to='core.Organisation', help_text=b'Organisation that manages the PUG and its contents', null=True)),
],
),
]
contains information about a local PostgreSQL user group
"""
country = models.ForeignKey('core.Country')
- org = models.ForeignKey('core.Organisation', null=True, blank=True, help_text='Organization that manages the PUG and its contents')
+ org = models.ForeignKey('core.Organisation', null=True, blank=True, help_text='Organisation that manages the PUG and its contents')
approved = models.BooleanField(null=False, blank=False, default=False)
locale = models.CharField(max_length=255, help_text="Locale where the PUG meets, e.g. 'New York City'")
title = models.CharField(max_length=255, help_text="Title/Name of the PUG, e.g. 'NYC PostgreSQL User Group'")
if not obj.org.email:
# Should not happen because we remove the form field. Thus
# a hard exception is ok.
- raise Exception("Organization does not have an email, canot send notification!")
+ raise Exception("Organisation does not have an email, canot send notification!")
n = ModerationNotification()
n.objecttype = obj.__class__.__name__
n.objectid = obj.id
</ul>
<p>
{%if original.org.email%}
-New notification: <input type="text" name="new_notification" style="width:400px;" /> (<b>Note!</b> This comment is emailed to the organization!)<br/>
+New notification: <input type="text" name="new_notification" style="width:400px;" /> (<b>Note!</b> This comment is emailed to the organisation!)<br/>
To send a notification on rejection, first add the notification above and hit
"Save and continue editing". Then as a separate step, delete the record.
{%else%}
refer to the party you are donating to and your tax professional.</p>
<h2>PostgreSQL Nonprofit Organisation (NPO) Recognition</h2>
-<p>For information about how <a href="/community/recognition/#npos">Recognised PostgreSQL Nonprofit Organi
zations (NPOs)</a> become recognised, please review the guidelines <a href="/community/recognition/#npos">here</a>.
+<p>For information about how <a href="/community/recognition/#npos">Recognised PostgreSQL Nonprofit Organi
sations (NPOs)</a> become recognised, please review the guidelines <a href="/community/recognition/#npos">here</a>.
<h2>Questions</h2>
<p>If you have any questions about donations please contact either the
<a href="mailto:funds-group@postgresql.org">PostgreSQL Funds Group</a> or the
-respective organization you are donating to.
+respective organisation you are donating to.
</p>
{%endblock%}
{%block contents%}
<h1>Privacy Policy</h1>
<p>When you visit our website, our servers automatically log your IP address and/or host name.</p>
-<p>We store information such as your email address, name and locality only if you decide to send us such information by completing a survey, or registering as a user on one of our sites. We collect this information to help us improve the content of our sites, customize the layout of our web pages and to contact people for technical and support purposes. We will not share your email address with other organizations unless required by law.</p>
+<p>We store information such as your email address, name and locality only if you decide to send us such information by completing a survey, or registering as a user on one of our sites. We collect this information to help us improve the content of our sites, customize the layout of our web pages and to contact people for technical and support purposes. We will not share your email address with other organisations unless required by law.</p>
<p>If you submit content to the website, such as listing your company as a
service provider, the information you submitted will be published.</p>
<p>If you post a message to one of our public mailinglists, your sending
email address and any content of the email will be published, and archived,
-both by us and by other organizations. These archives are permanent, and
+both by us and by other organisations. These archives are permanent, and
posted emails are not removed. By sending a message to one of these lists
you implicitly grant permission for this archival, overriding any
disclaimers in the message itself.</p>
<p>
<ul>
<li>
- <a href="#npos">Recognised PostgreSQL Nonprofit Organizations (NPOs)</a>
+ <a href="#npos">Recognised PostgreSQL Nonprofit Organisations (NPOs)</a>
</li>
<li>
<a href="#conferences">Community Conference Recognition</a>
</p>
<a name="npos" />
-<h1>Recognised PostgreSQL Nonprofit Organizations (NPOs)</h1>
-<p>Recognised PostgreSQL Nonprofit Organi
zations (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.
+<h1>Recognised PostgreSQL Nonprofit Organisations (NPOs)</h1>
+<p>Recognised PostgreSQL Nonprofit Organi
sations (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>.
<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 Organization</a></li>
+ <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>
<h2>How is the PostgreSQL project organized?</h2>
<p>PostgreSQL Global Development Group (PGDG) is a volunteer-run, global
-organization. We have a six-person core team, a number of Major Contributors and
+organisation. We have a six-person core team, a number of Major Contributors and
several mailing lists that make up the centralized portion of our community.
<a href="/community/contributors/">See here for details
about contributors</a>.</p>
projects / pgweb.git / commitdiff