public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dave Page <[email protected]>
To: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Planet posting policy
Date: Sun, 29 Jan 2012 19:55:50 +0000
Message-ID: <CA+OCxox7_0r8oeamJBWY6c-7df4Muy600H0nw5xT1L_4Eg7WAA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CA+OCxow3T9g-Cpt+B437vgCoYL+y83+LCYVw8Z42SnW3ciUB1g@mail.gmail.com>
	<[email protected]>
	<CA+OCxoxOTJjzLUpeCPdaA0so9yMUA20ABX+u8N=xKjmF4s3ocw@mail.gmail.com>
	<[email protected]>

On Sun, Jan 29, 2012 at 7:21 PM, Josh Berkus <[email protected]> wrote:
> Dave,
>
> I think a list of what's prohibited would be simpler:
>
> ==================
>
> The purpose of Planet PostgreSQL is to provide useful news, ideas,
> technical information, and community discussion for members of the
> PostgreSQL community.  It is not a medium for advertising commercial
> products and services; the community has other channels for that.
> Therefore, the following kinds of content are prohibited from Planet
> PostgreSQL, and may cause your blog to be removed from syndication if
> you post them:
>
> * Posts whose primary purpose is to advertise a commercial product,
> service, website, or event and lack substantial technical information or
> news of community interest;
>
> * Multiple and frequent posts which center around the same commercial
> product, service, event, or website with significant advertising content.
>
> Since the above evaluations are qualitative, here's some examples:
>
> BAD: Post announcing the launch of your new PostGIS-based website,
> without any real mention of PostGIS.
>
> GOOD: Post announcing the launch of your new PostGIS-based website, with
> a couple sentences about how it's based on PostGIS.
>
> BAD: 5 posts in a row about the new PostGIS website, all of which lack
> siginificant technical content.
>
> GOOD: Post about your commercial Postgres fork, how it differs from
> mainstream PostgreSQL, and why you'd want to use it.
>
> GOOD: Post about the technical challenges you overcame when developing
> your commercial Postgres fork.
>
> BAD: Post announcing the availability of version 3.5.641 of your
> commercial Postgres fork, with details copied directly from the press
> release.

I like that.


-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

view thread (52+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Planet posting policy
  In-Reply-To: <CA+OCxox7_0r8oeamJBWY6c-7df4Muy600H0nw5xT1L_4Eg7WAA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox