From e7099c90ead4bb3575109f68e1cbd548c138941c Mon Sep 17 00:00:00 2001 From: Dave Page Date: Mon, 18 Feb 2019 10:36:53 +0000 Subject: [PATCH] Move project policies to the website. Changes by myself and Jonathan Katz Review by Jonathan Katz and Daniel Gustafsson --- media/css/main.css | 3 +- pgweb/urls.py | 1 + pgweb/util/contexts.py | 5 +- templates/base/base.html | 2 +- templates/pages/about/policies.html | 53 ++++ templates/pages/about/policies/archives.html | 60 +++++ .../pages/about/policies/news-and-events.html | 244 ++++++++++++++++++ .../about/policies/planet-postgresql.html | 144 +++++++++++ templates/pages/about/policies/privacy.html | 54 ++++ .../pages/about/policies/project-name.html | 30 +++ .../about/policies/services-and-hosting.html | 125 +++++++++ .../pages/about/policies/sponsorship.html | 63 +++++ .../pages/about/policies/trademarks.html | 84 ++++++ templates/pages/about/policies/twitter.html | 88 +++++++ templates/pages/about/privacypolicy.html | 17 -- 15 files changed, 950 insertions(+), 23 deletions(-) create mode 100644 templates/pages/about/policies.html create mode 100644 templates/pages/about/policies/archives.html create mode 100644 templates/pages/about/policies/news-and-events.html create mode 100644 templates/pages/about/policies/planet-postgresql.html create mode 100644 templates/pages/about/policies/privacy.html create mode 100644 templates/pages/about/policies/project-name.html create mode 100644 templates/pages/about/policies/services-and-hosting.html create mode 100644 templates/pages/about/policies/sponsorship.html create mode 100644 templates/pages/about/policies/trademarks.html create mode 100644 templates/pages/about/policies/twitter.html delete mode 100644 templates/pages/about/privacypolicy.html diff --git a/media/css/main.css b/media/css/main.css index 6c93c8b7..e0462ad2 100644 --- a/media/css/main.css +++ b/media/css/main.css @@ -201,7 +201,8 @@ p, ul, ol, dl, table { blockquote { border-left: solid 5px #E7EAE8; - padding: 1em 4em 3em .5em; + padding: 0em 4em 0em .5em; + margin: 1em 0em 1em 0em; font-style: italic; } diff --git a/pgweb/urls.py b/pgweb/urls.py index d40673fc..d8c664f2 100644 --- a/pgweb/urls.py +++ b/pgweb/urls.py @@ -44,6 +44,7 @@ urlpatterns = [ url(r'^about/event/(\d+)(-.*)?/$', pgweb.events.views.item), url(r'^about/featurematrix/$', pgweb.featurematrix.views.root), url(r'^about/featurematrix/detail/(\d+)/$', pgweb.featurematrix.views.detail), + url(r'^about/privacypolicy/$', RedirectView.as_view(url='/about/policies/privacy/', permanent=True)), url(r'^ftp/(.*/)?$', pgweb.downloads.views.ftpbrowser), url(r'^download/mirrors-ftp/+(.*)$', pgweb.downloads.views.mirrorselect), diff --git a/pgweb/util/contexts.py b/pgweb/util/contexts.py index 43f6c3e2..25c4787e 100644 --- a/pgweb/util/contexts.py +++ b/pgweb/util/contexts.py @@ -6,9 +6,7 @@ from django.conf import settings sitenav = { 'about': [ {'title': 'About', 'link': '/about/'}, - {'title': 'Code of Conduct', 'link': '/about/policies/coc/', 'submenu': [ - {'title': 'Committee', 'link': '/about/policies/coc_committee/'} - ]}, + {'title': 'Policies', 'link': '/about/policies/'}, {'title': 'Feature Matrix', 'link': '/about/featurematrix/'}, {'title': 'Donate', 'link': '/about/donate/'}, {'title': 'History', 'link': '/docs/current/history.html'}, @@ -49,7 +47,6 @@ sitenav = { {'title': 'Local User Groups', 'link': '/community/user-groups/'}, {'title': 'Events', 'link': '/about/events/'}, {'title': 'International Sites', 'link': '/community/international/'}, - {'title': 'Recognition Guidelines', 'link': '/community/recognition/'}, ], 'developer': [ {'title': 'Developers', 'link': '/developer/'}, diff --git a/templates/base/base.html b/templates/base/base.html index 00a81300..a508d24b 100644 --- a/templates/base/base.html +++ b/templates/base/base.html @@ -76,7 +76,7 @@
- Privacy Policy | + Policies | Code of Conduct | About PostgreSQL | Contact
diff --git a/templates/pages/about/policies.html b/templates/pages/about/policies.html new file mode 100644 index 00000000..6f44038e --- /dev/null +++ b/templates/pages/about/policies.html @@ -0,0 +1,53 @@ +{%extends "base/page.html"%} +{%block title%}Policies{%endblock%} +{%block contents%} + +

Policies

+ +

Formal policies governing various aspects of the PostgreSQL Project can + be found here:

+ +

General Policies

+ + + +

PostgreSQL Project Policies

+ + + +

Content Policies

+ + + +

Community Recognition Policies

+ + + +{%endblock%} diff --git a/templates/pages/about/policies/archives.html b/templates/pages/about/policies/archives.html new file mode 100644 index 00000000..3a8fbd7a --- /dev/null +++ b/templates/pages/about/policies/archives.html @@ -0,0 +1,60 @@ +{%extends "base/page.html"%} +{%block title%}Archives Policy{%endblock%} +{%block contents%} + +

Archives Policy

+ +

Last updated: February 6, 2019

+ +

The PostgreSQL mailing lists are archived at + www.postgresql.org. This site is intended to provide an accurate + representation of the activity on the lists, and as such will not be + modified.

+ +

Why won't you remove my post?

+ +

There are a number of reasons why we will not remove or modify messages in + the archives:

+ + + +

E-Mail Disclaimers and Licencing

+ +

Some companies or organization add footers to outgoing e-mail messages with + that group's e-mail policies, such as this simple example:

+ +
This e-mail is confidential and only for use by the intended + recipient. +
+ +

These disclaimers are incompatible with sending messages to the PostgreSQL + mailing lists. When the mailing list is the "intended recipient", that + includes all of its current subscribers and the archives. These archives are + public, archived, and searchable; they cannot be made confidential.

+ +

By choosing to send messages to a PostgreSQL mailing list, you are implicitly + granting your permission for that message to be archived in that fashion, + regardless of any e-mail disclaimer it might have. Additionally, source code + submissions to mailing lists such as pgsql-hackers are considered + submissions to the PostgreSQL project, falling under the project's + PostgreSQL licence. Please make sure you have + permission to share information with these lists before sending your + message.

+ +{%endblock%} diff --git a/templates/pages/about/policies/news-and-events.html b/templates/pages/about/policies/news-and-events.html new file mode 100644 index 00000000..cb7b422f --- /dev/null +++ b/templates/pages/about/policies/news-and-events.html @@ -0,0 +1,244 @@ +{%extends "base/page.html"%} +{%block title%}News and Events Approval Policy{%endblock%} +{%block contents%} + +

News and Events Approval Policy

+ +

Last updated: March 29, 2018

+ +

Policies for Approving News & Events & pgsql-announce

+ +

General Rules

+ +

The www.postgresql.org home page contains News and Events listings which are + maintained entirely for the benefit of the PostgreSQL community. As this + space would be quite valuable (up to $400 per listing) if commercially + available, our admins have unlimited authority to be restrictive about what + they allow on the home page.

+ +

All News and Events (including Training Events) to be approved must include + the following information:

+ + + +

Other General Rules include:

+ + + +

In general, the postgresql.org home page is run exclusively for the benefit + of the not-for-profit member-owned PostgreSQL community. It is not an + advertising venue, and site admins are entitled to reject any notice which + they feel is inconsistent with the community's needs for any reason, or for + no reason.

+ +

Approving News and Announcements

+ +

All News policy below is considered to apply equally to the home page and + pgsql-announce, except that pgsql-announce also carries PWN.

+ +

PostgreSQL Core News

+ +

All items will be approved unless inaccurate. The following types of news are + generally appropriate for the home page:

+ + + +

PostgreSQL "Family" News

+ +

This includes news about PostgreSQL add-on projects & drivers, open source + projects which are primarily based on PostgreSQL, and news about PostgreSQL + regional and user groups.

+ +

Any of the following items will be approved, regardless of frequency:

+ + + +

Other types of news, such as changes in leadership, will not be approved.

+ +

Proprietary & External OSS Project News

+

This includes all news from companies whose products contain, support or are + based on PostgreSQL, and OSS projects which support PostgreSQL as one of + several database options.

+ +

The following types of news will be approved:

+ + + +

Other types of announcements, including minor releases, pricing changes, + leadership changes, 3rd-party news coverage, partnerships, and mergers & + acquisitions will be rejected.

+ +

In addition, commercial entities who are not financial, in-kind or code + contributors to the PostgreSQL project will be restricted to one news item + of any kind per six-month period.

+ +

Procedure for Approving pgsql-announce

+ +

Since pgsql-announce goes to over 30,000 addresses, we are cautious in what + we approve to that list. In some cases, this may result in a delay of up to + several days in approving announcements.

+ +
  1. Check if it's spam and reject spam.
    2. +
  2. Check if there is anything else in the 'To' or 'CC' list besides + -announce; if so, reject and ask for re-submission. +
    3. +
  3. Read the announcement
    4. +
  4. Consider if the announcement meets this policy and is appropriate for + announcement +
      +
    • if necessary, check on pgsql-www list
      • +
    +
    5. +
  5. Approve or Reject
    6. +
+

In any case where an approver has doubts about whether to approve an + announcement or not, they should err on the side of caution.

+ +

Please note that PostgreSQL major/minor release posts should be handled by + the release team, not by the pgsql-announce moderators.

+ +

Approving Events and Event-Related News (excluding training)

+ +

Events must have significant PostgreSQL-related content in order to be + listed.

+ +

PostgreSQL Conferences & Events

+

Any semi-annual or less frequent non-training event which is primarily about + PostgreSQL or for PostgreSQL users will be entitled to be listed. + Additionally, conferences which are primarily or entirely about PostgreSQL + will be entitled to post news items at the following milestones, if they are + each a week or more apart:

+ + + +

Routine monthly PostgreSQL User Group meetings will not be listed. First + meetings of a new PUG can be listed, as well as infrequent major special + events likely to be of interest outside of the PUG's normal area.

+ +

Open Source & Database Conferences & Events

+ +

Open source conferences, and database conferences, which are not primarily + about PostgreSQL but have significant PostgreSQL content, such as several + sessions and a booth, may be listed in the Events. Additionally, the Call + For Papers for these events may be accepted as News.

+ +

More routine events, such as monthly local meetings or mini-conferences, will + not be listed. Conferences must have significant PostgreSQL content to be + worth listing, with decisions on relative significance to be made by the WWW + team.

+ +

Training Events

+ +

PostgreSQL Training may be listed from any company, under the following + conditions:

+ + + +

All descriptive text should be purely informative and not include strong + marketing copy or special offers unrelated to the training. The vendors + website should list PostgreSQL training information, including an online + schedule of upcoming trainings.

+ +

In the event that any training company submits more than 4 training events to + be held in any given quarter, site admins may (at their discretion) deny + posting events to that company.

+ +

Rejection Notices

+ +

In cases where the submitter appears to have gone to some effort to submit a + relevant news item or event, but doesn't understand our policies, we should + send them a rejection e-mail linking to this page and explaining what was + wrong with their submission. This certainly goes for any of the major + project sponsors.

+ +

If the submission looks like a 30-second cut-and-paste job, or something else + sloppy and quick, or is a submission by someone who has had multiple + submissions rejected in the past for the same reason, don't bother sending a + response. We get too much spam for that.

+ +

Any company which has had submissions repeatedly rejected for the same + reasons, and does not correct their errors when notified, risks having their + community account suspended and their ability to submit news and events + blocked.

+{%endblock%} diff --git a/templates/pages/about/policies/planet-postgresql.html b/templates/pages/about/policies/planet-postgresql.html new file mode 100644 index 00000000..b9436d4a --- /dev/null +++ b/templates/pages/about/policies/planet-postgresql.html @@ -0,0 +1,144 @@ +{%extends "base/page.html"%} +{%block title%}Planet PostgreSQL{%endblock%} +{%block contents%} + +

Planet PostgreSQL

+ +

Last updated: October 12, 2016

+ +

Planet PostgreSQL is a blog + aggregation service run by the PostgreSQL community. In addition to the main + Planet site, entries are published ("syndicated") to the www.postgresql.org site as + well.

+ +

Planet PostgreSQL Policy

+ +

The following simple rules cover the blogs being listed on Planet + PostgreSQL:

+ + + +

Violating these rules will cause your blog to be removed from Planet + PostgreSQL.

+ +

Approval of Blogs

+ +

Planet PostgreSQL volunteer moderators approve your blog once you submit the + syndication request. Note the following points:

+ + + +

Planet PostgreSQL FAQ

+ +

How can I remove a bad entry from the feed?

+

It's possible to login to the administration interface and hide an individual + entry. If you realize you've made a mistake and done something like + accidentally posting incorrectly tagged content, removing it on your own is + recommended.

+ +

What are the right URLs to use for a labeled feed from blogger.com?

+

Assuming your blog is named "blogname" and you've tagged a subset of your + posts with the "postgresql" label, the correct URLs to input to the Planet + code are:

+ + + +

You can confirm those URLs display a suitable copy of your feed via a web + browser before submitting them.

+ +

Are commercial posts allowed?

+

Informative entries that mention proprietary products are normally + permissible, as long as the main entry is relevant to the PostgreSQL + community. But the policy specifically prohibits publication of advertising + in the portion of a blog that is syndicated to the Planet feed. It's + recommended that blogs that may contain ads tag them appropriately, to + provide a feed to the Planet without those entries included.

+ +

What constitutes an advertisement?

+

The primary test here is whether the information provided would be of some + use even to people who have no interest in the commercial product mentioned. + Consider what your entry would look like if all references to the product + were removed. If there's no useful PostgreSQL content left after doing that, + that post is an ad.

+ +

You can find a blog entry giving a more detailed opinion from one of the + moderators about this subject at Planetary + alignment. That commentary is not part of the official policy.

+ +

Can I offer free or discounted products to people?

+

Not as your only post content. An article that otherwise meets the standards + here, by providing useful information to readers with no interest in the + commercial product mentioned, might also include some commercial offer like + a free product in them. But promotions like product giveaways or providing a + discount to blog readers are not acceptable on their own. You might consider + the offer itself informative, but the moderators of the Planet feed will + usually judge it to be advertisement. Blog entries offering to give away + something for free or at a reduced cost are very likely to be flagged as a + violation of policy.

+ +

What happens to blogs that violate the site policies?

+

A first violation of the advertising policy will result in the blog entry + with the ad being removed, and a warning e-mail sent to the listed owner of + the blog.

+ +

A second violation will resulting in the blog being removed from the Planet + PostgreSQL feed. After a two month suspension period, the blog owner can + submit their blog address--or a new feed URL better tagged to filter out + advertisements--for reconsideration.

+ +

A third violation in any year will result in a full 12 month suspension of + the blog from Planet PostgreSQL.

+ +

Who makes the moderation decisions about the Planet content allowed?

+

Site maintenance and moderation duty is done by a small team of volunteer + moderators, primarily made up of PostgreSQL + contributors from various companies who are familiar with the + policies of the PostgreSQL community.

+ + +{%endblock%} diff --git a/templates/pages/about/policies/privacy.html b/templates/pages/about/policies/privacy.html new file mode 100644 index 00000000..75046b35 --- /dev/null +++ b/templates/pages/about/policies/privacy.html @@ -0,0 +1,54 @@ +{%extends "base/page.html"%} +{%block title%}Privacy Policy{%endblock%} +{%block contents%} +

Privacy Policy

+ +

Last updated: December 10, 2012

+ +

When you visit our website, our servers automatically log your IP address + and/or host name.

+ +

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.

+ +

If you submit content to the website, such as listing your company as a + service provider, the information you submitted will be published.

+ +

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 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.

+ +

We may collect demographic and interest category information from people via + surveys, volunteered information, suggestions from members, and other means. + Our members may voluntarily provide information, including that regarding + personal, interests, geography, and demographics. The purpose of this data + collection is to ensure we continue to understand the needs and wants of the + PostgreSQL community, and therefore can provide the most relevant + information, guides, and content.

+ +

This website uses Google Analytics, a web analytics service provided by + Google, Inc. ("Google"). Google Analytics uses "cookies", which are text + files placed on your computer, to help the website analyze how users use the + site. The information generated by the cookie about your use of the website + (including your IP address) will be transmitted to and stored by Google on + servers in the United States. Google will use this information for the + purpose of evaluating your use of the website, compiling reports on website + activity for website operators and providing other services relating to + website activity and internet usage. Google may also transfer this + information to third parties where required to do so by law, or where such + third parties process the information on Google's behalf. Google will not + associate your IP address with any other data held by Google. You may refuse + the use of cookies by selecting the appropriate settings on your browser, + however please note that if you do this you may not be able to use the full + functionality of this website. By using this website, you consent to the + processing of data about you by Google in the manner and for the purposes + set out above.

+{%endblock%} diff --git a/templates/pages/about/policies/project-name.html b/templates/pages/about/policies/project-name.html new file mode 100644 index 00000000..8e2c0745 --- /dev/null +++ b/templates/pages/about/policies/project-name.html @@ -0,0 +1,30 @@ +{%extends "base/page.html"%} +{%block title%}Project Name{%endblock%} +{%block contents%} + +

Project Name

+ +

Last updated: July 5, 2018

+ +

"PostgreSQL" versus "Postgres"

+ +

The name Postgres is an accepted alias for the PostgreSQL project. However it + is an alias or nickname and is not the official name of the project. Per + Dave Page, PostgreSQL Core Team:

+ +
+

+ Following recent discussions on a name change for the project, it has become + clear that consensus within the community will never be reached. In light of + this, the core team have discussed the matter in depth and decided that the + project shall continue to use the name PostgreSQL, but accept the use of + Postgres as an alias. +

+

Regards, Dave

+
+ +

Ref: Project + name - statement from the core team.

+ +{%endblock%} diff --git a/templates/pages/about/policies/services-and-hosting.html b/templates/pages/about/policies/services-and-hosting.html new file mode 100644 index 00000000..bcb5cf22 --- /dev/null +++ b/templates/pages/about/policies/services-and-hosting.html @@ -0,0 +1,125 @@ +{%extends "base/page.html"%} +{%block title%}Professional Services and Hosting Approval Policy{%endblock%} +{%block contents%} + +

Professional Services and Hosting Approval Policy +

+ +

Last updated: May 19, 2012

+ +

Policies for Approving Professional Services and Hosting Services

+ +

General Rules

+ +

The www.postgresql.org home page contains Professional Services and Hosting + (in general, Services) listings which are maintained entirely for the + benefit of the PostgreSQL community. As this space would be quite valuable + if commercially available, our admins have the authority to be restrictive + about what they allow on the home page.

+ +

All Services to be approved must include the following information:

+ + + +

Further, the web site you link to in the listing must somewhere mention + PostgreSQL as an offered service or platform. If PostgreSQL is not mentioned + anywhere on your website, then your listing will not be approved.

+ +

Also, do not list your company in every single geographic region unless you + are a truly worldwide company (e.g. IBM, Akamai). This may be reason to + reject your listing.

+ +

Other General Rules include:

+ + + +

Professional Services and Listings

+ +

For Professional Services, the "provides support and services" check box must + be checked. Fill out the following form blanks with the listed information. + Incomplete submissions may be rejected.

+ + + +

Hosting Listings

+ +

If you offer web hosting for PostgreSQL applications, please check the + "Provides hosting of PostgreSQL databases"

+ +

Supported Interfaces should detail what programming languages (e.g. Perl, + Java, Ruby, etc.) and/or what database applications (e.g. Drupal, xTuple, + OpenACS, etc.) you specifically have support for. Also include any notes in + this space about limitations or special features of your PostgreSQL + hosting.

+ +

Your web site must specifically list PostgreSQL as a supported hosted + application if you list the other applications which you support on your + hosting platform.

+ +

Removal

+ +

Professional Services and Hosting listings are offered purely and entirely + for the benefit of our not-for-profit member community. Postgresql.org is + not an advertising service or publication. If our admins feel that your + listing is inconsistent with the good of our community, your listing may be + removed for any reason, or no reason.

+ +

Specific reasons which are likely to get your listing removed include:

+ + + +

If your listing is removed, the admins will usually notify you of the reason + for removal, though such notice is not guaranteed.

+ +{%endblock%} diff --git a/templates/pages/about/policies/sponsorship.html b/templates/pages/about/policies/sponsorship.html new file mode 100644 index 00000000..b40bfa5c --- /dev/null +++ b/templates/pages/about/policies/sponsorship.html @@ -0,0 +1,63 @@ +{%extends "base/page.html"%} +{%block title%}Sponsoring{%endblock%} +{%block contents%} + +

PostgreSQL Sponsorship

+ +

Last updated: June 1, 2018

+ +

Sponsorship levels

+ +

There are two levels of PostgreSQL Sponsors:

+ + + +

Contributions to the PostgreSQL Project that may be considered by the + committee include, but are not limited to:

+ + + +

Sponsorship for PostgreSQL events will not be considered in determining + PostgreSQL sponsorship levels.

+ +

All sponsorship recognition is at the discretion of the Sponsor Committee, + who will decide on the status of each sponsor or potential sponsor on an + individual basis. In exceptional circumstances, a contributor may be + recognised at a sponsorship level for outstanding contributions over a + period of time lower than the above stated durations. The decision of the + committee is final.

+ +

Sponsorship Committee

+ +

Using the guidelines above, sponsorship is ultimately determined by the + Sponsorship committee. The current members are:

+ + + +

The current method of choosing who qualifies as a sponsor is via simple + majority vote of those in the committee.

+ +{%endblock%} diff --git a/templates/pages/about/policies/trademarks.html b/templates/pages/about/policies/trademarks.html new file mode 100644 index 00000000..96307b6a --- /dev/null +++ b/templates/pages/about/policies/trademarks.html @@ -0,0 +1,84 @@ +{%extends "base/page.html"%} +{%block title%}Trademark Policy{%endblock%} +{%block contents%} + +

Trademark Policy

+ +

Last updated: August 28, 2018

+ +

Policy

+ +

The PostgreSQL elephant + logo (Slonik) and the names "PostgreSQL" and "Postgres" are registered + trademarks of the PostgreSQL Community + Association of Canada. If you wish to use either name or logo in any + way, you must comply with this policy.

+ + + +

Examples

+ +

The following are examples of acceptable uses of the logo:

+ + + +

Unacceptable use

+ +

The following are example of uses of the logo which are NOT acceptable:

+ + + +

Contact

+ +

The PostgreSQL Community Association of Canada has designated the PostgreSQL + Core Team to be its authoritative agent in most matters regarding trademark + usage. If you have any questions about this policy, or its interpretation, + please email them at + pgsql-core@postgresql.org. +

+ +{%endblock%} diff --git a/templates/pages/about/policies/twitter.html b/templates/pages/about/policies/twitter.html new file mode 100644 index 00000000..b17c2e45 --- /dev/null +++ b/templates/pages/about/policies/twitter.html @@ -0,0 +1,88 @@ +{%extends "base/page.html"%} +{%block title%}@postgresql Twitter Account Policy{%endblock%} +{%block contents%} + +

@postgresql Twitter Account Policy

+ +

Last updated: January 19, 2018

+ +

This policy applies to the manual use of the @postgresql Twitter account.

+ + + +

In addition to approved News & Events, these kinds of Events may also be + tweet'd about, following the same guidelines set forth above:

+ + + +

Replies to mentions are also allowed when and if appropriate, per these + guidelines:

+ + + +

Tweets should follow the same guidelines as one would use when posting to the + project mailing lists.

+ +{%endblock%} diff --git a/templates/pages/about/privacypolicy.html b/templates/pages/about/privacypolicy.html deleted file mode 100644 index 2629e178..00000000 --- a/templates/pages/about/privacypolicy.html +++ /dev/null @@ -1,17 +0,0 @@ -{%extends "base/page.html"%} -{%block title%}Privacy Policy{%endblock%} -{%block contents%} -

Privacy Policy

-

When you visit our website, our servers automatically log your IP address and/or host name.

-

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.

-

If you submit content to the website, such as listing your company as a -service provider, the information you submitted will be published.

-

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 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.

-

We may collect demographic and interest category information from people via surveys, volunteered information, suggestions from members, and other means. Our members may voluntarily provide information, including that regarding personal, interests, geography, and demographics. The purpose of this data collection is to ensure we continue to understand the needs and wants of the PostgreSQL community, and therefore can provide the most relevant information, guides, and content.

-

This website uses Google Analytics, a web analytics service provided by Google, Inc. ("Google"). Google Analytics uses "cookies", which are text files placed on your computer, to help the website analyze how users use the site. The information generated by the cookie about your use of the website (including your IP address) will be transmitted to and stored by Google on servers in the United States. Google will use this information for the purpose of evaluating your use of the website, compiling reports on website activity for website operators and providing other services relating to website activity and internet usage. Google may also transfer this information to third parties where required to do so by law, or where such third parties process the information on Google's behalf. Google will not associate your IP address with any other data held by Google. You may refuse the use of cookies by selecting the appropriate settings on your browser, however please note that if you do this you may not be able to use the full functionality of this website. By using this website, you consent to the processing of data about you by Google in the manner and for the purposes set out above.

-{%endblock%}