From: "Magnus Hagander" <magnus@hagander.net>
To: "Josh Berkus" <josh@agliodbs.com>
CC: pgsql-www@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Message-ID: <200710160743200000@1265611355>
Subject: Re: Approval process for news/events/training is broken
Date: Tue, 16 Oct 2007 07:43:20 +0200
Content-Transfer-Encoding: 8bit


> >>> The real question is, "is it proprietary". If it is even partially
> >>> closed source then it really doesn't belong in the "postgresql family
> >>> product" unless we also include MPP and Replicator.
> >> You know what I mean :-). And all of EDB-Postgres is open source,
> >> including the funky little MySQL migrator tool in the latest builds.
> > 
> > Uh, doesn't the installer use a commercial product that isn't open
> > source?  Does requiring non-open source tools to build something make it
> > non-open source?  Postgres requires a C compiler that can be open or
> > closed source so I don't know if that helps clarify things.
> 
> I don't think any of this is relevant for the News page.  The question 
> is, will the person sending me the press release be a paid PR person, or 
> an OSS developer?  We treat the two differently because they're going to 
> send us different sorts of news at different intervals.
> 
> For example, I would treat EDB-Postgres as "commercial" because they 
> send us formal press releases every 3 weeks, which often need 
> significant re-writing to target our developers.  On the other hand, if 
> we get anything from OpenRPT it's just a release announcement, maybe 
> once a year, so we can treat them like an "PostgreSQL Family" OSS project.
> 
> So it's not commercial vs. open source *product*, it's commercial vs. 
> open source *news*.

That makes sense. But that needs to be clear in the policy, since it seems we all got it wrong :-)

(maybe now they'll have Dave write the news submissions instead. He'l hate you forever :-P)

/Magnus