Just a thought
During the .boom I was interviewed for a position at a company that used Zope. Where I come from, open-source is rare and Zope even more so.
Cheese eating surrender monkey
Zope appears to have been swallowed whole by Plone and then CA, this may or may not be a good thng. Knowing and using Zope is just one of those strange idiosyncrasies I have.
Actually Zope is such an rare beast that I didn't bother to learn it when I had the chance. And the guys the OP was talking about sanked. They were using technology for technology's sake, not to solve problems.
Zope sounds incredibly cool in a way but every time I've convinced myself to learn it, I've ended up chickening out because it just seems way too complicated. Really I think I'd be quicker and better off writing my own Python-based web dev platform than trying to learn that thing well. But while that kind of attitude just leads to lots of reinvented wheels, I feel they could do a lot to simplify the overwhelming amount of crap surrounding Zope.
Zope 3 will be much more like py2ee. But I've moved on.
fool for python
An old saying comes to mind: watch out whose toes you step on, because some day they may be attached to the ass that you have to kiss.
Pretty tangential to the OP's message, but we've moved to zope/plone for website and associated online applications. It was a pretty steep learning curve, but the view is great from up here. After banging my head on JSP's and other assorted J2EE stupidity for a couple of years, zope is a breath of fresh air, and my toes don't curl up painfully when I realize I need to tweak a security config.
Fog Creek Home