Re: Re: PHP Licensed GeoIP PECL module proposal
| From: | Pedram Nimreezi | Date: | Sat, 15 Jul 2006 00:12:41 +0000 |
| Subject: | Re: Re: PHP Licensed GeoIP PECL module proposal | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-3986@lists.php.net to get a copy of this message | ||
Is this accurate?:
http://www.osdir.com/Article9026.phtml
...the next draft of the LGPL will include a change.
Instead of being a separate license, the LGPL will be the GPL with
additional privileges, a kind of template of what additions should be...
On 7/14/06, Greg Beaver <cellog@php.net> wrote:
Olivier Hill wrote: On 7/14/06, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:-- ~ Pedram Nimreezi -- Senior Engineer Major Computing, Inc -- Not by age, but by knowledge is wisdom acquired.site-1 here. I don't see why we should be stuck in the middle of this and risk yet another angry RMS exchange. We have nothing to gain here. They are perfectly free to distribute this extension from their ownThe problem is not hosting this stuff on their website or sourceforge. The problem is with visibility of the module. How many times has geoip been discussed here? I'm sure many PHP users are looking for it on PECL, don't see it, and go somewhere else. This is the biggest flaw PHP has right now in my opinion, that extensions are missing or not centralized and hard to find. I know we don't want the GPL things to be virulant, but in this case, I still don't see how the license exception is different from MySQL. I liked CPAN. I liked PEAR. I just wish PECL could be that easy, or should I say flexible. I've been close to the PHP dev community for a while now, and I find it really hard to contribute stuff. No hard feelings, but I just wanted to let this off my chest. I'm pretty sure some good devs are scared off. Anyway, I'll inform Maxmind that it cannot be included on PECL, even with a license change. Why not just set up a PEAR channel? PECL extensions can be distributed just the same as other packages. I imagine it would not be a problem to mention external PECL channels just as PEAR mentions external PEAR-style channels. This solves the license issue because the extension is distributed externally, but is still easy to find. Greg -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.phpand leave us out of their license mess.