-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Aspeli wrote:
> Wichert Akkerman wrote:
>> Previously Martin Aspeli wrote:
>>> If you want to pull in, say, plone.supermodel (a "pure Zope 3" package 
>>> that should be re-usable and may be useful to BFG if it ever wants to 
>>> serialise Zope 3 schema interfaces to/from an XML representation) well, 
>>> it uses zope:* ZCML directives. Are you going to fork plone.supermodel? 
>> I would be very tempted at least. Or decide to not use supermodel.
> 
> Which would mean that the BFG-intersecting parts of the repoze stack 
> would be a fork or re-implementation of all Zope stuff that was 
> interesting to it. I don't think that's a sustainable way forward. Or at 
> least, then repoze should stop billing itself as "the maturity of Zope 
> now with the flexibility of the WSGI future".
> 
> But I don't think that's what Paul or Chris would want. :)

BFG != repoze.

BFG makes no promises that any Zope-derived software will work with it
out of the box.  BFG is a way to build Zope-like appplications without
carrying forward BBB-encrufted legacy.  BBB is "not your father's
Oldsmobile."

Plone will never run on BFG, period.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tsea...@palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJT9tL+gerLs4ltQ4RAkxeAJwKZjpBusQQsFsWplXxtF6lw67jLgCfbWYW
53xdV42yfLnpe+8XMlkTaDE=
=JAWF
-----END PGP SIGNATURE-----
_______________________________________________
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

Reply via email to