Message-ID: <4F259C4D.5050806@agliodbs.com>
Date: Sun, 29 Jan 2012 11:21:49 -0800
From: Josh Berkus <josh@agliodbs.com>
Organization: PostgreSQL Experts Inc.
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
	rv:1.9.2.24) Gecko/20111103 Lightning/1.0b2 Thunderbird/3.1.16
MIME-Version: 1.0
To: pgsql-www@postgresql.org
Subject: Re: Planet posting policy
References: 
 <CA+OCxow3T9g-Cpt+B437vgCoYL+y83+LCYVw8Z42SnW3ciUB1g@mail.gmail.com>
	<96e5156e36277877d18484a5148ad516@biglumber.com>
	<CA+OCxoxOTJjzLUpeCPdaA0so9yMUA20ABX+u8N=xKjmF4s3ocw@mail.gmail.com>
In-Reply-To: 
 <CA+OCxoxOTJjzLUpeCPdaA0so9yMUA20ABX+u8N=xKjmF4s3ocw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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.

==============================


-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com