Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36565
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain litespeedtech.com designates 64.18.140.195 as permitted sender)
Message-ID: <47EAAD1C.2050100@litespeedtech.com>
Date: Wed, 26 Mar 2008 16:07:56 -0400
User-Agent: Thunderbird 2.0.0.12 (X11/20080226)
MIME-Version: 1.0
To: internals@lists.php.net
References: <47E80EB9.60900@litespeedtech.com> <47E81136.3040308@zend.com> <47E81315.4060601@lerdorf.com> <47E82351.6040004@litespeedtech.com>
In-Reply-To: <47E82351.6040004@litespeedtech.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Inclusion of PHP LiteSpeed SAPI in the standard PHP
 distribution?
From: gwang@litespeedtech.com (George Wang)

OK, let's back to the topic, is there any conclusion on this topic yet?
I certainly would like not to miss the release of 5.3 and ready to help 
with any issue.

> As to user request, here is one :-)
>
> http://bugs.php.net/bug.php?id=42987
According to this ticket, this has been assigned to johannes, should I 
follow up with this ticket to get it going?
His last update to the ticket is

"I saw that some files use another license than PHP License and other refer

to an outdated version. when bundling they should be licensed under the
current PHP License 3.01."


Our LSAPI library code has been license under BSD license, and there are 
other BSD licensed code get into PHP core, like PCRE, GD, etc. Is that 
really a concern? Do I have to change it to PHP license?

Please let me know if there are other concerns.

Thanks,
George Wang