[Zope-Coders] Zope 3; getting in on the act?

[Martijn Faassen]

Steve Alexander wrote:
> Martijn Faassen wrote:
> 
> >
> >What do you mean by 'forward-compatibility'? Don't you mean backwards
> >compatibility with Zope 2.x? Or am I missing something here? Anyway,
> >if I understand you right, that is a good approach. Zope 2.x code should be
> >supported as best as we can, but it shouldn't be allowed to 
> >make the new architecture ugly right from the start, by influencing it
> >everywhere with its sometimes bad and implicit assumptions.
> 
> Would it be possible to keep a pure new incompatible Zope3, and have 
> Zope2 compatibility as an add-on product?
> 
> So, I'd be able to get rid of that product, and have a cruft-free Zope.

That'd be nice. But I think the plan *is* to try to separate Zope 2 stuff
out from Zope 3 as much as possible, right? So in theory you could just
throw out the cruftness.. Us contributors could be watchdogs who'll
bark and patch as soon as too much dependency on Zope 2 stuff is introduced. :)

> It sounds like a tall order, but there are applications I'd gladly port 
> to Zope3 which need have no Zope2 dependencies.

And of course new applications we can write. :)

Regards,

Martijn