----- Weitergeleitete Message -----
> Von: hakre <hanskren...@yahoo.de>
> An: Zeev Suraski <z...@zend.com>
> CC:
> Gesendet: 17:09 Mittwoch, 30.Januar 2013
> Betreff: Re: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP
> distribution
>
> ----- Ursprüngliche Message -----
>
>> Von: Zeev Suraski <z...@zend.com>
>> An: internals@lists.php.net
>> CC:
>> Gesendet: 9:03 Dienstag, 29.Januar 2013
>> Betreff: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP
> distribution
>>
>> All,
>>
>>
>>
>> Following the discussion at the end of last week, I prepared a draft RFC
>> for the inclusion of Optimizer+ in PHP.
>
> I have some questions:
>
> * In that RFC you write:
>
> "the integration won’t happen before late 2014." [if it's not
> bundled with PHP 5.5]
>
> Can you please outline why? Especially does it mean you stop contributing to
> the
> PECL development if you don't get this bundled with PHP 5.5?
>
> Also can you please outline why you put obviously so much focus in bundling
> this
> to PHP 5.5? Or is my impression wrong?
>
> * With full respect and the best intentions: Are you able and if yes, can you
> share about the motivation why you decided (quite surprisingly) to contribute
> at
> this place in time? As you wrote in the past many PHP core contributors also
> worked on that component while it's well known that PHP is not really
> useable as platform without an opcode cache in an attractive field. You also
> wrote in an earlier email that you got out of sync with your userbase. Under
> these circumstances, the impression could be that it took a little bit too
> long
> until this decision was done and I would like to see this impression
> clarified
> because there are many loose ends.
>
> * Is this surprising and welcomed release related in any way to the Openstack
> Initiative?
>
> * Which benefits does Zend Inc. see in contributing the Opcode cache?
>
> * Last but not least, not related to the opcode cache alone, but related
> because
> you want to bundle it with core: If some day the PHP group decides to choose
> a
> similar software license, but different in the sense that it is more
> compatible
> with existing FLOSS licensing, would you have a problem to re-license as
> well,
> e.g. under MIT or Apache 2.0 for that part?
>
> Thank you for taking your time, I know I ask about a lot, but it would be
> great
> if you give some insights that are not covered by the RFC but could play a
> role
> to make up ones mind about this contribution. Thank you.
>
> -- hakre
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php