Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 33FEBE60237 for ; Sun, 29 Jan 2012 15:56:03 -0400 (AST) Received: from mail-tul01m020-f174.google.com ([209.85.214.174]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Rrar4-0004l9-On for pgsql-www@postgresql.org; Sun, 29 Jan 2012 19:56:03 +0000 Received: by obcva7 with SMTP id va7so3254321obc.19 for ; Sun, 29 Jan 2012 11:55:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.72.74 with SMTP id b10mr23256005obv.69.1327866950427; Sun, 29 Jan 2012 11:55:50 -0800 (PST) Received: by 10.60.6.227 with HTTP; Sun, 29 Jan 2012 11:55:50 -0800 (PST) In-Reply-To: <4F259C4D.5050806@agliodbs.com> References: <96e5156e36277877d18484a5148ad516@biglumber.com> <4F259C4D.5050806@agliodbs.com> Date: Sun, 29 Jan 2012 19:55:50 +0000 Message-ID: Subject: Re: Planet posting policy From: Dave Page To: Josh Berkus Cc: pgsql-www@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201201/65 X-Sequence-Number: 20463 On Sun, Jan 29, 2012 at 7:21 PM, Josh Berkus wrote: > Dave, > > I think a list of what's prohibited would be simpler: > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > The purpose of Planet PostgreSQL is to provide useful news, ideas, > technical information, and community discussion for members of the > PostgreSQL community. =A0It 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. --=20 Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company