1. What Zope did wrong(and how it's being fixed) Lennart Regebro http://regebro.wordpress.com/ PyCon 2008, Chicago

2. Zope did most things right 3. Python 4. A hierarchical in memory transactional networkable schemaless object oriented logging database with orthogonal persistency and undo. 5. Security focus 6. Fine-grained access control 7. User management 8. Internationalization 9. Unicode everywhere 10. DTML / ZPT 11. Plugin architecture for code reuse 12. Component Architecture 13. Through The Web Development 14. What Zope 2 did wrong 15. Through The Web Development 16. The ZODB pile of scripts 17. ZClasses 18. Disk-based products 19. Development dead-ends 20. Zope became a ghetto 21. Didn't play with others 22. Big monolith 23. Magic attributes and methods 24. Backwards compatibility forever 25. Badly documented 26. Never ends Starts off easy 27. Development dead-ends Ghetto Magic Loads of old cruft No docs 28. 29. Zope 3! 30. No more dead-ends No magic attributes and methods Managed evolution No ghettos Much better docs 31. Death by abstraction 32. A conspiracy on the hard disk 33. Ugh... Phew... 34. Zope 2+ Zope 3 = Five 35. Never ends Starts off easy 36. Ugh... Phew... 37. 2 + 3 = Five Ugh... Argh! 38.

• Low entry treshold

• and

• all the power of a big framework

• without

• dead ends?

39. 40. Information Manager IT department Site developer Application developer Core developer User Layer Schema driven content types Workflow editors A CMS, ERP or similar Product Layer A Web application server Application Layer API Platform Layer Python Component Architecture Loads of components Framework Layer 41. How is Zope being fixed? 42. Eggyfying 43. Repoze 44. Deliverance 45. Grok 46. Dexterity 47.