RE: [PHP] Question about PHP Licence and it's future!
| From: | Andrés Robinet | Date: | Sun, 24 Feb 2008 08:49:32 +0000 |
| Subject: | RE: [PHP] Question about PHP Licence and it's future! | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-269986@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: Andrés Robinet [mailto:agrobinet@bestplace.biz]
> Sent: Sunday, February 24, 2008 3:41 AM
> To: 'Robert Cummings'; 'Tamer Higazi'
> Cc: php-general@lists.php.net
> Subject: RE: [PHP] Question about PHP Licence and it's future!
>
> > -----Original Message-----
> > From: Robert Cummings [mailto:robert@interjinn.com]
> > Sent: Sunday, February 24, 2008 2:40 AM
> > To: Tamer Higazi
> > Cc: php-general@lists.php.net
> > Subject: Re: [PHP] Question about PHP Licence and it's future!
> >
> >
> > On Sun, 2008-02-24 at 06:50 +0200, Tamer Higazi wrote:
> > > Hi!
> > > I have asked myself a question. After I saw, that SAP will no more
> > > release future Versions of their open source Database MaxDB under the
> > > GPL License, I have asked myself either if this could happen with PHP.
> > >
> > > Who owns PHP? Is it Zend Technologies or the PHP Group itself? "Who" is
> > > the PHP Group and what makes the PHP Group?
> > >
> > > Who guaranties that future Versions of PHP stays open source and are
> > > being released under the Terms of the General Public Licenses?
> > >
> > > Can future Versions from one day to the other no more being released
> > > under the GPL, only under a closed source license? Let us say, PHP
> would
> > > be distributed for several architectures only in binary forms and the
> > > PECL modules stay open source.
> > >
> > > These questions are for me very importand according to an commercial
> > > product which will be planed, designed, written and sold commercially.
> > >
> > > We are pendling between Ruby, Python and PHP5. Only the point "written"
> > > is unclear.
> >
> > It doesn't matter. The PHP code as it is has been released under the PHP
> > License. This means if the future versions were ever released under
> > another license that was exclusionary, then there is still the
> > opportunity to fork code released under the PHP license. Heck you can
> > fork the PHP project now if you felt you could get the ball rolling with
> > enough momentum for acceptance. If beleive the hardened PHP project is
> > considered a fork despite the fact it generally keeps full compatibility
> > while adding security enhancements.
> >
> > Cheers,
> > Rob.
> > --
> > .------------------------------------------------------------.
> > | InterJinn Application Framework - http://www.interjinn.com
> > |
> > :------------------------------------------------------------:
> > | An application and templating framework for PHP. Boasting |
> > | a powerful, scalable system for accessing system services |
> > | such as forms, properties, sessions, and caches. InterJinn |
> > | also provides an extremely flexible architecture for |
> > | creating re-usable components quickly and easily. |
> > `------------------------------------------------------------'
>
> Rob,
>
> Are you sure you can fork the *current* PHP version??? The hardened PHP
> project
> still complains with the PHP license I think. I don't think the current PHP
I meant *complies* not *complains* sorry (lol, I really need that cup of coffee
now)
Regards,
Rob