public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Page <[email protected]>
To: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Planet posting policy
Date: Wed, 1 Feb 2012 09:40:56 +0000
Message-ID: <CA+OCxoxC8nAKRYhx2ALS93c6CrHUm5RsAEzu0g6bqQAiwC_usg@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>
<CABUevEzWPnYr7PW6+GLh8Q6S+PvPi-7GKipE8ZuLPLRQKBLf_g@mail.gmail.com>
<[email protected]>
On Mon, Jan 30, 2012 at 5:58 PM, Josh Berkus <[email protected]> wrote:
>
>> I think that blog post itself is a very good example of content we
>> *don't* necessarily want on planet.
>
> See, while for me it's exactly the kind of post I think *should* be
> included. Because I'm a working consultant, I'm interested in what the
> various commercial forks can do for my customers, and as a PostgreSQL
> hacker I'm interested in what the various commercial tools tell us about
> our users. As long as it's not press releases.
Right - and we shouldn't lose sight of the fact that Planet isn't
their primarily for us; it's there for the users. Some of them
probably only want to know about PostgreSQL itself, whilst others will
certainly be interested in the entire eco-system around PostgreSQL.
In just about every other aspect of what we do, we encourage input and
content from commercial and OSS product vendors alike, both about
their products and because they're vendors we're happy to be
associated with; news, events, announcements, press quotes, the
product catalogue etc. etc. Planet is the only exception to this I can
think of.
--
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+OCxoxC8nAKRYhx2ALS93c6CrHUm5RsAEzu0g6bqQAiwC_usg@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