Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 3C700BED7F2 for ; Mon, 30 Jan 2012 03:50:33 -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 1Rrm0W-000859-Tp for pgsql-www@postgresql.org; Mon, 30 Jan 2012 07:50:33 +0000 Received: by obcva7 with SMTP id va7so3598904obc.19 for ; Sun, 29 Jan 2012 23:50:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.49.106 with SMTP id t10mr26765584obn.49.1327909820410; Sun, 29 Jan 2012 23:50:20 -0800 (PST) Received: by 10.60.6.227 with HTTP; Sun, 29 Jan 2012 23:50:20 -0800 (PST) In-Reply-To: References: Date: Mon, 30 Jan 2012 07:50:20 +0000 Message-ID: Subject: Re: Planet posting policy From: Dave Page To: Peter Geoghegan Cc: Magnus Hagander , PostgreSQL WWW Content-Type: text/plain; charset=ISO-8859-1 X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201201/69 X-Sequence-Number: 20467 On Mon, Jan 30, 2012 at 5:21 AM, Peter Geoghegan wrote: > On 29 January 2012 18:42, Dave Page wrote: >> I was trying to find a way to allow posts that aren't purely technical >> in nature. For example, if a company started a new website that >> happened to have 10TB of geo data stored in Postgres, I'd want to hear >> about it as a good example of Postgres being used in "state of the >> art" ways, even if it wasn't necessarily a post about how they did it >> in technical detail. > > Are you sure that that wouldn't be allowed under our current policy? > I'd have thought that was fine, provided that it was actually useful. It might have been under the policy itself, however we've been interpreting that based on the guidance notes which are pretty strict, and essentially only allow posts of a purely technical nature. > It might be helpful if you could cite a specific incident of the > current rules tripping someone up in a way that was clearly against > the community's interest. I can't do that I'm afraid, as it may cause embarrassment for the people/companies involved. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company