public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jonathan S. Katz <[email protected]>
To: Joshua D. Drake <[email protected]>
To: Simon Riggs <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: w^3 <[email protected]>
Subject: Re: Planet posting policy
Date: Mon, 30 Jan 2012 14:56:36 -0500
Message-ID: <[email protected]> (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]>
<CABUevEzG2Qb5kuw5=YnAx9-aAhh0r5YJ9kdZNzA5CwQKbmvsmw@mail.gmail.com>
<[email protected]>
<[email protected]>
On Jan 30, 2012, at 7:29 AM, Simon Riggs wrote:
> Yeh. It all seems quite simple to me. We're here to contribute to a
> specific open source project, so write a blog about what you have done
> lately that furthers those goals.
On Jan 30, 2012, at 2:37 PM, Joshua D. Drake wrote:
> I have to say I am with JoshB on this one. I want to know *all* about PostgreSQL. I want Greenplum, VMWare, EDB Advanced Server and .Org represented because they all directly apply to what I do for a living. I want to know about all the tools and all the options available to me.
Though these may seem like opposing arguments, I agree with both Simon and JD. Planet blog entries should be pertaining specifically what's going on in the noncommercial part of the community, but at the same time, it's good for the world to be aware of what is being developed commercial and how PostgreSQL and it's derivatives are being employed. After all, a lot of the commercial development does help provide the necessary financing to put new features into core.
That being said, based on the proposals for the Planet acceptance policy, there is too much of a "gray line" on what is acceptable (even by just debate on the list over one entry). Having two separate feeds is a possibility, and has a few pros:
* Highlight both feeds on the postgresql.org home page (both in separate sections, and I would put community higher up) - show what is happening in the community, and what is happening the commercial world, hopefully driving more interest in both
* Eliminate "confusion" over what is acceptable content in the community blogs
Having a commercial.planet.postresql.org could help community members working on commercial products highlight some of the cool stuff they are doing, while not taking away from community-led efforts. Thus the policy could be:
* If the work is strictly community related (i.e. the work is going directly into core, some extension, or some open-source Postgres derivative or project), then it's on planet
* If the work is for a commercial product, it goes on the other feed
Jonathan
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], [email protected], [email protected], [email protected]
Subject: Re: Planet posting policy
In-Reply-To: <[email protected]>
* 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