Re: [Zope-dev] Re: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the source coderepository
Stephan Richter wrote: * We have been constantly trying to make the trunk smaller, and suddenly we blow it up? This does not fit. In fact, I would claim that zwiki and bugtracker should now be moved out of the trunk and placed into top-level dirs themselves. They should be tested using the buildbot. This is a very very good point... * I have a fear that people will be motivated to make Zope 3 changes to make them work better with Zope 2, inserting special code just for Zope 2. Another good point. cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the source coderepository
Lennart Regebro wrote: I think this change can possibly make sense when we have replaced Zope 2 authentication with Zope 3s, and when we have replaces Zope 2 publisher with Zope 3s and when we have replaced the Zope 2 traversal with Zope3s, and maybe a couple of other things. At that point, Zope2 will more or less be Zope3 + App, DateTime, OFS, Products and some other stuff. Then something more of a merge might make sense. This is a really really good point ;-) I think unification is probably a good idea, but not yet... Even so, I'd much prefer to see Z3 stay "light" of Zope 2 and just have Zope 2 become smaller and smaller as it leverages more and more of Zope 3. Put differently, I have no problem with the repositories merging, but I'd like to see the bits of Zope 3 seperately available, without Z2. I know ZPT and testbrowser already work like that, and the more that works like that the better... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] RE: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the source coderepository
Philipp von Weitershausen wrote: Bottom line: I find the risk of your having to dig through horrible Zope 2 code much lower than the chance of joint efforts on Zope 3 technology. Of course, it'd be quite surprising if I didn't believe that as the author of the proposal *wink*. I agree with the points your raise but I worry about the arrival of the pragmatists and making nasty botch jobs to help out some half broken code in Zope or Plone... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the source coderepository
On Thursday 24 November 2005 05:36, Martijn Faassen wrote: > I don't think that threats to leave and portrayals of utter doom are a > fair way to discuss this, Stephan. I must say I find it extremely ironic > to hear from you that stalling Zope 3 for several months is a death blow > to Zope 3 -- where was this sentiment in the past? :) Note that I don't claim that my leaving would stall the development. I just use my case as an example. I always consider myself of someone, who accepts a very high bar for contributing. So, if I think the the bar is too high, my thinking goes, then others will also conceive it as too high and that causes the stalling. Everyone is replaceable, I have learned that in the US. But a certain group might not as easily be. > Like it or not, merging the repository or not, you'd better get used to > the fact that Zope 2 developers are here in your community and that they > will speak up to let their interests be known. It's in your interest to > make us happy, actually, as we're working to make Zope 3 a better > community and a better system. I know that The Zope 2 people are around. And I try to answer Five questions on the lsits and on IRC as good as I can. I also have nothing against hearing the interest of the Zope 2 community. But I am also in a position where I must protect the interests of the Zope-3-only community as well. And in *my* opinion, in this particular case the Zope 2 community has a lot to gain at the expense of the Zope-3-only community. I have outlined my arguments for that statement in the many E-mails before. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the source coderepository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lennart Regebro wrote: > I think this change can possibly make sense when we have replaced Zope > 2 authentication with Zope 3s, and when we have replaces Zope 2 > publisher with Zope 3s and when we have replaced the Zope 2 traversal > with Zope3s, and maybe a couple of other things. Exactly. In this case Zope2 will be a more a 'configuration' of Zope3. Well, I'm repeating my self here ... > > At that point, Zope2 will more or less be Zope3 + App, DateTime, OFS, > Products and some other stuff. Then something more of a merge might > make sense. > yup. This is my impression. This is too early... > Up until then, we have a functioning system now, and I'm guessing the > benefits will not outweigh the work. I can only agree with this on this. J. - -- Julien Anguenot | Nuxeo R&D (Paris, France) CPS Platform : http://www.cps-project.org Zope3 / ECM : http://www.z3lab.org mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDhbZWGhoG8MxZ/pIRAjA5AJ9NdWa0lfhoPrngxVK7CV6ttSPqpACeM9Pk IXBQi5KCZotRxRoO+uJp/j0= =mZRW -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the source coderepository
I think this change can possibly make sense when we have replaced Zope 2 authentication with Zope 3s, and when we have replaces Zope 2 publisher with Zope 3s and when we have replaced the Zope 2 traversal with Zope3s, and maybe a couple of other things. At that point, Zope2 will more or less be Zope3 + App, DateTime, OFS, Products and some other stuff. Then something more of a merge might make sense. Up until then, we have a functioning system now, and I'm guessing the benefits will not outweigh the work. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the source coderepository
Stephan Richter wrote: [snip] So you think it is better to loose the existing Zope 3 developers in anticipation of more community involvement? This would be Zope 3's death blow as we know it, because it would stall Zope 3 for several months. Honestly, I rather have less exposure and keep the code base clean. I don't think that threats to leave and portrayals of utter doom are a fair way to discuss this, Stephan. I must say I find it extremely ironic to hear from you that stalling Zope 3 for several months is a death blow to Zope 3 -- where was this sentiment in the past? :) Like it or not, merging the repository or not, you'd better get used to the fact that Zope 2 developers are here in your community and that they will speak up to let their interests be known. It's in your interest to make us happy, actually, as we're working to make Zope 3 a better community and a better system. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )