Clarification de l'intégration de ZF dans d'autres outils Zend

Salut

Wil Sinclair vient de clarifier la position de Zend concernant Zend Framework et les outils commerciaux de Zend (notamment Zend Studio) :

Citation:

---

Thorsten, most of the Zend Framework integration in Studio are value-adds over PDT, so I wouldn’t be surprised if you don’t find many ZF-specific features in that project. This is a great opportunity to tell everyone what our philosophy is regarding the relationship between Zend Framework and Zend’s commercial products. We believe what is best for our community is also best for Zend. With that in mind, we have no intention to release major functionality that is of use to the general community in ZF that requires a commercial license. Our strategy is to provide value-adds in the commercial products themselves that make them irresistible to all you ZF developers and deployers. J We may ship major performance enhancements that cannot be made in the framework itself. We certainly will provide tools to easily use ZF with our commercial products. We will provide improved interfaces to ZF features. I could even see certain value adds that could be added to our web properties in the future. Please note, these features will be implemented in our products and/or web properties themselves, and are not really ZF features as such.
A perfect example is the Zend_Tool feature. We provide all the functionality in ZF itself. But you can count on an advanced interface available in Zend Studio down the line (provided the community approves of the component and it is promoted to standard library). The current Zend Studio integration, which is very cool BTW- I use it constantly- reflects this strategy.

Not the answer you were looking for, but maybe you’ll find it interesting anyways. J

,Wil

---

En somme, ZF contiendra les fonctionnalités mais les produits commerciaux de Zend contiendront des fonctionnalités (valeur ajoutée) permettant de faciliter l'utilisation de ZF.


Zend n'a donc pas l'intention de "vendre" des fonctionnalités ZF, qui reste un produit gratuit et communautaire.

La license actuelle de ZFFW permet de "forker" le projet en cas de modification de license du FrameWork. Je ne suis donc pas étonné de cette décision. Je pense que cette précision vient plutôt pour rassurer les développeurs échaudés par la "création" de Zend Studio.

PS : Mais je comprends la position de la société Zend. Le tout gratuit, je n'y crois pas tellement. Le tout payant, je n'y crois pas non plus. Et cette solution me semble particulièrement saine et respectueuse !