Hi, On Wed, 2008-03-26 at 16:07 -0400, George Wang wrote: > 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.
I think it makes sense, you, as the server's vendor, supports it and whatever the exact usage number are there seem to be users who certainly benefit from it. > > 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? 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. 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. 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... johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
