Newsgroups: php.internals,php.pdo
Path: news.php.net
Xref: news.php.net php.internals:35495 php.pdo:137
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain oracle.com from 141.146.126.228 cause and error)
Message-ID: <47B4ADCE.5090907@oracle.com>
Date: Thu, 14 Feb 2008 13:08:30 -0800
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: Lukas Kahwe Smith <mls@pooteeweet.org>
CC: pdo@lists.php.net, PHP Internals <internals@lists.php.net>
References: <37388396.20080201212653@marcus-boerger.de> <47A395BA.9020707@daylessday.org> <Pine.LNX.4.58.0802011702490.15624@miranda.org> <fe05d1540802011420o22144724rdd4c9668e2ebfb94@mail.gmail.com> <47B39DF1.2000607@oracle.com> <fe05d1540802131813t7c58d8a1ke4e681b69a3eca9@mail.gmail.com> <47B3A7B6.9020400@oracle.com> <fe05d1540802131843q2e6f8aadpa0027f790398b6c8@mail.gmail.com> <00a901c86eb6$54321250$c6fc1f3e@foxbox> <79825459-12D4-477D-A252-A23F77128B03@pooteeweet.org>
In-Reply-To: <79825459-12D4-477D-A252-A23F77128B03@pooteeweet.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PDO] Re: [PHP-DEV] Re: [PDO] Re: [PHP-DEV] [RFC] An Idea for
 PDO 2
From: christopher.jones@oracle.com (Christopher Jones)


Lukas Kahwe Smith wrote:
 > OSS is a collaborative process that is not about some manager
 > allocating some ressources here and there. People usually make
 > personal commitments here and maybe this is the bigger culture clash
 > than the CLA.

Oracle contributes to a range of open source projects, big and small,
mature and too new to be known.  The commitments come at the personal
level and from management who expect their staff to work on those
projects.

OSS projects accept contributions on merit, and that doesn't always
mean knowing much about the background of the people contributing.

 > What is being proposed is to turn part of PHP into something that is
 > managed by a manager and the budget he gets allocated by a manager
 > above him.

The proposal is a broader approach to the design and implementation of
a DB access layer.  Instead of a piecemeal, ad hoc set of designs that
ultimately reduces general productivity, I'd like to sit down and
discuss what users want and create a coherent solution.

 > People do not commit access for saying what company they work for.
 > People get commit access once they have send enough patches that are top
 > notch, that php.net decides they can trust them. This is the model of
 > trust we have gone by. So if we are going to change this to start
 > trusting a managerial process, the least we can ask is to have some
 > interaction with the people that will most likely be involved there,
 > even if there is a good chance that things might be shuffled around by
 > the time we get to see code.

The code and strength of contributions and maintenance is the ultimate
evidence of what can be trusted.  Poor quality drivers, if they are
distributed via a PECL-only distribution, will acquire their own bad
reputation and remain little used like other dormant PECL extensions.
Or if the drivers are part of the core PHP distribution, a poor driver
should get pulled if it is not of sufficient quality as determined by
the PHP community.

I believe that all the data access providers potentially involved have
some level of skill with PHP extension writing, and they certainly
have some skill in writing software.

I hope that the data access providers are not the only people
contributing to, or gate-checking, the drivers.

Chris

-- 
Christopher Jones, Oracle
Email: christopher.jones@oracle.com    Tel:  +1 650 506 8630
Blog:  http://blogs.oracle.com/opal/   Free PHP Book: http://tinyurl.com/f8jad