Re: [Zope-dev] RE: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the sourcecoderepository
Roger Ineichen wrote: ... And please stop telling that there will be a migration path for somthing. Please stop saying that there won't be. > I guess there will never be such a path. I guess differently. > Perhaps custom products can be rewriten based on Zope3 libraries, but a real migration path like known from other software will never be supported. Normaly Zope2 based projects are to highly customized and this will make it impossible for a clear migration path. Perhaps this will be different for standard use of a Plone or Silva. Butdo you really know somebody where is using Plone or Silva out of the box? I'm convinced that there will be a migration path. I don't know if it will be painless or automatic. It may take the form of Zope 2's lower-level infrastructure being replaced by Zope 3's. I think this is entirely possible and would constitute a real migration to Zope 3. It's very possible that there will be a Zope 2 in the future that supports Zope 2 paradigms and Zope 3 paradigms simultaneously. This would look very different from many "pure" Zope 3 applications, but perhaps no more different than a number of sucessful Zope 3 applications such as Schooltool and applications being built by Canonical. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope-dev] RE: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the sourcecoderepository
Hi there, Roger Ineichen wrote: [snip] I really think we should stop draw a vision where we will get a on cklick migration for custom projects. Then this is what people normaly expectt if we speak about a migration path. What vision is this? I don't think anybody has been proposing this vision. I'm not sure how any such visions relate to this discussion anyway. There will be a lot of work to migrate such a application. And I'm not sure if it's the best way to migrate via Five. What'a about the idea to write a new application pure based on Zope3 and then migrate the existing data in the ZODB? I guess this will be much easier for many projects then migrate via existing hooks and reflect every future refactoring over the next years. One question: Who will pay for all this work? Given lots and lots of free programmers that will do all this development, this can happen. I don't see these resources, though. :) So, we usually don't have that luxury. People have real projects in production and we want to start using Zope 3. One main route open to us maintaining existing applications is one of gradual evolution. Of course the other alternative is to forget about evolving towards Zope 3 at all and Zope 2 just going its own way, but I don't think anybody wants that, right? Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
