Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36733 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31056 invoked from network); 31 Mar 2008 21:50:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Mar 2008 21:50:32 -0000 Authentication-Results: pb1.pair.com header.from=gwang@litespeedtech.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=gwang@litespeedtech.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain litespeedtech.com designates 64.18.140.195 as permitted sender) X-PHP-List-Original-Sender: gwang@litespeedtech.com X-Host-Fingerprint: 64.18.140.195 mail.litespeedtech.com Received: from [64.18.140.195] ([64.18.140.195:53658] helo=mail.litespeedtech.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D1/C2-17962-6AC51F74 for ; Mon, 31 Mar 2008 16:50:32 -0500 Received: from ip-216-39-248-126.hqglobal.net ([216.39.248.126] helo=[192.168.0.66]) by mail.litespeedtech.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1JgRtT-0004ij-Tc; Mon, 31 Mar 2008 17:50:25 -0400 Message-ID: <47F15C9B.5090901@litespeedtech.com> Date: Mon, 31 Mar 2008 17:50:19 -0400 User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Pierre Joye CC: =?ISO-8859-1?Q?Johannes_Schl=FCter?= , 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> <47EBF155.901@litespeedtech.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -3.2 (---) X-Spam-Report: Spam detection software, running on the system "mail.litespeedtech.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see admin@litespeedtech.com for details. Content preview: Hi Pierre, I also prefer BSD license as well, Johannes will make the final call, if he think that it is a show stopper, I will dual-license it. I have updated lsapi_main.c to address the "{ } after an if statement" issue on the other day. If there is anything need to be taken care, please just let me know. [...] Content analysis details: (-3.2 points, 5.3 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP 1.1 SPF_FAIL SPF: sender does not match SPF record (fail) [SPF failed: Please see http://spf.pobox.com/why.html?sender=gwang%40litespeedtech.com&ip=216.39.248.126&receiver=mail.litespeedtech.com] -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.1 AWL AWL: From: address is in the auto white-list Subject: Re: [PHP-DEV] Inclusion of PHP LiteSpeed SAPI in the standard PHP distribution? From: gwang@litespeedtech.com (George Wang) Hi Pierre, I also prefer BSD license as well, Johannes will make the final call, if he think that it is a show stopper, I will dual-license it. I have updated lsapi_main.c to address the "{ } after an if statement" issue on the other day. If there is anything need to be taken care, please just let me know. Hopefully it will appear in the nightly build soon. :-) Thanks, George Pierre Joye wrote: > Hi George, > > On Thu, Mar 27, 2008 at 8:11 PM, George Wang wrote: > >> 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. >> > > I don't think it is necessary. If you like to bundle the LSAPI > library, it is perfectly fine to keep it under the BSD license. > > Cheers, >