Skip site navigation (1) Skip section navigation (2)

Re: Increased company involvement

From: "Andy Astor" <andya(at)enterprisedb(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>,"Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>,"PostgreSQL advocacy" <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Increased company involvement
Date: 2005-04-28 19:01:11
Message-ID: B319CFEC3B80D3408CA36F99ADE8409406D43B@edb-dc1.Edb-net.EnterpriseDB.com (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-hackers
> > However, there was a lot of coordination that happened with Fujitsu
that
> > I don't see happening with the current companies involved.
Companies
> > are already duplicating work that is also done by community members
or
> > by other companies.
> 
> That is bound to happen no matter what. Look at plJava and plJ. Some
> people just feel that their way is better. Some people just don't get
> along etc...
> 
> That is why we have 80 Linux distributions and a dozen FreeBSD
> distributions (can I include MacOSX?).

True enough. And coordination, just like other outward-facing
activities, is often inconvenient and easy to forget. But it's
important. I've just left the Board of Directors of the Web Services
Interoperability organization (WS-I). Coordinating the standards
activities of IBM, MS, Sun, Oracle, BEA, Fujitsu, SAP, and 130 others
takes enormous time and care, but it's the only way coop-etors can
function.

And having said that, aggressive businesspeople will move too quickly at
times, or will hide their activities for business reasons. It's a mostly
forgivable sin, IMO.

> > Second, some developers are being hired from the community to work
on
> > closed-source additions to PostgreSQL.  That is fine and great, but
one
> > way to kill PostgreSQL is to hire away its developers.  If a
commercial
> > company wanted to hurt us, that is certainly one way they might do
it.
> > Anyway, it is a concern I have.  I am hoping community members hired
to
> > do closed-source additions can at least spend some of their time on
> > community work.
> 
> I would think that most of the developers would stipulate that in
order
> to take the position??? I know Command Prompt would always make sure
> that the developer could work on the community stuff.

The same is true for EnterpriseDB.

> > And finally, we have a few companies working on features that they
> > eventually want merged back into the PostgreSQL codebase.  That is a
> > very tricky process and usually goes badly unless the company seeks
> > community involvement from the start, including user interface,
> > implementation, and coding standards.
> 
> I concur with this. We ran into this with plPerl.

The only way to successfully extend PostgreSQL commercially is to
coordinate with the community.

	-- Andy




pgsql-hackers by date

Next:From: Thomas HallgrenDate: 2005-04-28 19:47:45
Subject: Re: Returning a RECORD, not SETOF RECORD
Previous:From: Michael FuhrDate: 2005-04-28 18:48:09
Subject: Re: Returning a RECORD, not SETOF RECORD

pgsql-advocacy by date

Next:From: Larry RosenmanDate: 2005-04-29 00:16:24
Subject: Hey, Pervasive folks
Previous:From: Josh BerkusDate: 2005-04-28 17:13:17
Subject: Re: [pgsql-advocacy] Need help on drivers, add-ons

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group