-- Georgy Turevich <georgy.turev...@gmail.com> wrote (on Friday, 30 October 2009, 11:31 AM +0300): > I have not understood. The component will be developed by other people? Or it > is discontinue for ever?
Discontinued. All development was being done basically by Benjamin himself, and my team is simply too small for me to provide him much additional support without having it affect other projects. We have considered in the past writing an ORM, and the conclusion has always been that we do not have either enough expertise or resources on our team to undertake it. I was willing to let it be a community effort, but it would have taken a dedicated team of volunteers (a) to make it happen in a reasonable time frame, and (b) to provide ongoing support for it. Benjamin got to a point where he realized he'd finished about 50% of functionality, and likely had another 4-6 months before it was releasable. At that point, we'd be gearing up for ZF 2.0, which would mean he'd need to start rewriting to make use of PHP 5.3 features. It was simply a very daunting task, and one he wasn't getting much help with. Additionally, there's the fact that Doctrine is becoming a key part of the greater PHP ecosystem. Agavi and Symfony ship with it. I've seen tutorials for using it with CodeIgniter, Cake (and the new offshoot, Lithium), and of course ZF. Considering that many developers will be using it in other projects, it makes for a natural migration point -- migrate your models from one framework to another in order to make use of a different MVC or components. It simply makes sense *not* to reinvent the wheel here, and instead spend some time doing formal integration with Doctrine in order to leverage its community of developers. -- Matthew Weier O'Phinney Project Lead | matt...@zend.com Zend Framework | http://framework.zend.com/
