Newsgroups: php.internals,php.pdo
Path: news.php.net
Xref: news.php.net php.internals:35109 php.pdo:99
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 64.97.136.175 cause and error)
Message-ID: <019c01c865d5$2ebbacf0$c6fc1f3e@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Marcus Boerger" <helly@php.net>
Cc: <pdo@lists.php.net>,
	"internals" <internals@lists.php.net>
References: <00ce01c865c2$22f23aa0$c6fc1f3e@foxbox> <510220265.20080202204406@marcus-boerger.de>
Date: Sat, 2 Feb 2008 19:52:44 -0000
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PDO] Re: [PHP-DEV] Fw: [PDO] [RFC] An Idea for PDO 2
From: steph@zend.com ("Steph Fox")

>  all we need is to extend the PECL database with a license type field and 
> a
> CLA flag. Nothing else is required at that end. But we should still move 
> as
> much from php-src/ext to pecl as we can.

Hm but then when you checked out you'd have CLA'd stuff as well as normal 
PECL stuff, as now. Don't you find you automatically tend to fix things if 
they're broken? I know I do... even if I rarely get around to posting those 
fixes (because once everything works here I go on to the stuff I wanted to 
do and forget there was even a problem, until the next time.)

I was just trying to find a way that would be acceptable to php.net and also 
would mean PDO2 driver development doesn't have to wait on PECL process 
decisions, but actually my off-list feedback says even a PECLA module 
wouldn't be an acceptable option for some.

- Steph

> marcus