Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36622
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: <47EBF155.901@litespeedtech.com>
Date: Thu, 27 Mar 2008 15:11:17 -0400
User-Agent: Thunderbird 2.0.0.12 (X11/20080226)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@php.net>
CC: internals@lists.php.net
References: <47E80EB9.60900@litespeedtech.com> <47E81136.3040308@zend.com>	 <47E81315.4060601@lerdorf.com> <47E82351.6040004@litespeedtech.com>	 <47EAAD1C.2050100@litespeedtech.com> <1206574218.11056.24.camel@goldfinger>
In-Reply-To: <1206574218.11056.24.camel@goldfinger>
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)

Hi Johannes,

Thank you for the quick reply.

> Well, the idea is that all PHP-specific code is licensed under the same
> license terms. PCRE and GD are external libraries which live outside
> PHP's context and which are simply bundled. That's why the clear
> preference there is PHP License.
>   
OK, let me make some clarifications on this.
the main SAPI code, lsapi_main.c,  which is specific for PHP, has been 
licensed under PHP license.
Other c source code are our generic LSAPI library, which will be used 
for all third parties integrations, those files are licensed under BSD 
license.

I don't mind dual license those code under both BSD and PHP license if 
required as long as it won't prevent us from using the same code 
somewhere else under BSD license.

> Additionally it would nice to follow the PHP coding standards. Like
> always having  { } after an if statement. This helps PHP developers who
> might (possibly) help fixing reported (simple) bugs or apply API
> changes.
>   
No problem, will do. :-)
If there is other requirements, please just let me know.

> Other than that we, again, have our problem about what's the best way to
> "bundle" something from pecl. I guess the symlink on the CVS server is
> the best option we currently have...
>   
I have no problem with moving or recreating that directory at the right 
place either.


Thanks,
George