Re: Re: [HACKERS] My new job

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Adam Lang" <aalang(at)rutgersinsurance(dot)com>
Cc: "PostgreSQL-general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Re: [HACKERS] My new job
Date: 2000-10-11 02:44:31
Message-ID: 3.0.5.32.20001011124431.029674f0@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

At 17:25 10/10/00 -0400, Tom Lane wrote:
>
>So the question is, what do we do now?
>

There seem to be several concerns (in no particular order):

1. Conscious design/development choices based partly/solely on the needs of
one or more companies as opposed to the interest of the open source project.

eg. if changes to the core of pgsql to support erServer are actually
detrimental to the maintainability and reliability of the open source project.

This can not be completely avoided, but the existing core team review
system will presumably help. Expanding the core to include non-company
people is a good idea.

2. Subconscious design/development choices based on the interests of one or
more companies.

Can't really avoid this, but one hopes such subconscious decisions will be
far less significant than the conscious ones. Again, expanding the core to
include non-company people is a good idea.

3. Loss of core members to wholly private development.

Can't avoid this. Always was and will be a risk.

In answer to "What do we do now", it seems a first step would be to ensure
transparency in decision making (something that I think Peter E mentioned).
The fact we have two companies, who in theory will compete, is a good thing
(let's hope there are no strategic alliances announced in the near future).

What about setting up some kind of committee consisting of an expanded core
as well as some rotated members (possibly) selected randomly from the
non-core developers or users?

In reality, any suggestions of 'what to do' has to come from the core. It
has to be something you are happy to follow and which is not painful, but
which also satisfies the concerns already raised.

The first attempt at self-regulation failed, probably because the sights
were set unreasonably high. What is needed now is an agreed and reasonable
set of guidelines or principles.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2000-10-11 03:08:01 Re: Re: [HACKERS] My new job
Previous Message Adam Haberlach 2000-10-11 02:06:47 Re: Re: [HACKERS] My new job

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-10-11 03:08:01 Re: Re: [HACKERS] My new job
Previous Message Alfred Perlstein 2000-10-11 02:23:17 calling PQendcopy() without blocking.