Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 9E3F9197AB88 for ; Mon, 30 Jan 2012 15:56:55 -0400 (AST) Received: from mail-qw0-f46.google.com ([209.85.216.46]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RrxLS-0006TG-Tz for pgsql-www@postgresql.org; Mon, 30 Jan 2012 19:56:55 +0000 Received: by qadc10 with SMTP id c10so2333649qad.19 for ; Mon, 30 Jan 2012 11:56:41 -0800 (PST) Received: by 10.224.203.67 with SMTP id fh3mr24351466qab.13.1327953401799; Mon, 30 Jan 2012 11:56:41 -0800 (PST) Received: from [192.168.1.145] (rrcs-184-75-23-182.nyc.biz.rr.com. [184.75.23.182]) by mx.google.com with ESMTPS id s18sm36681038qaz.15.2012.01.30.11.56.38 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 Jan 2012 11:56:39 -0800 (PST) Subject: Re: Planet posting policy Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Jonathan S. Katz" In-Reply-To: <4F26F174.70308@commandprompt.com> Date: Mon, 30 Jan 2012 14:56:36 -0500 Cc: Josh Berkus , Magnus Hagander , w^3 Content-Transfer-Encoding: quoted-printable Message-Id: References: <96e5156e36277877d18484a5148ad516@biglumber.com> <4F26DA5D.7040808@agliodbs.com> <4F26DBDD.60104@agliodbs.com> <4F26F174.70308@commandprompt.com> To: "Joshua D. Drake" , Simon Riggs X-Mailer: Apple Mail (2.1084) X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201201/84 X-Sequence-Number: 20482 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=