Last updated: March 29, 2018
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.
All News policy below is considered to apply equally to the home page and pgsql-announce, except that pgsql-announce also carries PWN.
All items will be approved unless inaccurate. The following types of news are generally appropriate for the home page:
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.
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.
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.
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.
Events must have significant PostgreSQL-related content in order to be listed.
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 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.
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.
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.