On Sat, Jan 16, 2010 at 4:21 PM, Chris Rossi <ch...@archimedeanco.com>wrote:
> I will add only anecdotally, that I've taken a customer from 3.1 up to > 3.3.2 with repoze and the repoze piece has posed no issues. It's a > little clunky, but it works. I look forward to WSGI integrated into > the core Zope/Plone stack. > *great* to know! any helpful hints about how you got repoze to work with later plone versions? did you just identify the repoze elements (the repoze.org "about" page <http://repoze.org/about.html> names repoze.vhm, repoze.retry, repoze.tm), see how they were connected in the repoze.plone build, and plop them similarly into a plone 3.3.2 buildout, then debug 'til it worked? did you use the virtualenv or buildout packagings? so many questions... :-) -- ken http://myriadicity.net Chris > > > On Sat, Jan 16, 2010 at 3:54 PM, Hanno Schlichting <ha...@hannosch.eu> > wrote: > > Hi. > > > > I'm not a representative of the Repoze project, so I'll just share my > > personal view. > > > > On Sat, Jan 16, 2010 at 9:23 PM, ken manheimer <ken.manhei...@gmail.com> > wrote: > >> these seem to be likely questions if you're interested in adoption of > >> repoze.plone by the wider plone community. please let me know if i'm > >> misunderstanding something basic, or if i've missed somewhere that > covers > >> the issues... > > > > repoze.zope2 and .plone have been written largely by Agendaless for > > the KARL project. That project has gone through another iteration and > > nowadays uses repoze.bfg without any Plone instead. While there are > > some individual users of the repoze.plone approach, there's currently > > no driving party behind it anymore. > > > > Now it's perfectly possible to use most of the software with > > up-to-date versions of Zope2 and Plone, but this setup isn't > > particular well documented or explained anywhere. The entire stack is > > however production proven and there's no doubt about its quality. > > > > At this point I see repoze.zope2 / .plone as a prototype for a full > > WSGI integration into Zope2. It's likely not going to see major > > adoption in its current form. It's more likely that the lessons > > learned from this project will be merged back in some form into Zope2 > > itself, providing it with an OOTB WSGI story. If everything goes well, > > I hope to see Plone have official WSGI support in the future. The > > timeline for that is probably Zope 2.13 or later and Plone 5.0 with a > > final release somewhere in 2011 or 2012. With such a long timeframe > > there's obviously lots of unknowns. > > > > In this situation it's up to every user to decide if the benefits of > > the WSGI approach outweigh the costs of going with a non-standard > > approach. As always you can make a difference by getting involved and > > driving this project forward yourself ;-) > > > > Hanno > > _______________________________________________ > > Repoze-dev mailing list > > Repoze-dev@lists.repoze.org > > http://lists.repoze.org/listinfo/repoze-dev > > >
_______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev