public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Dave Page <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Approval process for news/events/training is broken
Date: Mon, 15 Oct 2007 18:20:36 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Dave Page wrote:
> >>> Also, looking back at the news just added today, is "EnterpriseDB
> >>> Postgres"
> >>> considered a "postgresql family product" or a commercial one? Maybe a
> >>> guidance bullet on "downstream distributions"?
> >>
> >> It's certainly not commercial, but yes that does seem worth clarifying.
> > 
> > It depends on what you are meaning by "commercial". This is a common
> > problem amongst FOSS people. FOSS can be commercial. I would actually
> > argue that EnterpriseDB Postgres *is* commercial as it is backed and
> > supported by a *commercial* Enterprise.
> > 
> > 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.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

view thread (31+ 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: Approval process for news/events/training is broken
  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