State Of Zope Linuxtag 2008

1,843 views
1,738 views

Published on

State of Zope talk given by Andreas Jung at the Linuxtag, Berlin, May 2008

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,843
On SlideShare
0
From Embeds
0
Number of Embeds
344
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

State Of Zope Linuxtag 2008

  1. 1. The State of Zope Past - Present - Future Linuxtag, 28. May 2008 Berlin Andreas Jung ZOPYX Ltd. & Co. KG Tübingen, Germany www.zopyx.com
  2. 2. Speaker • Zope core developer since 2001 • Zope 2 release-manager • Contributor to Zope & Plone • Co-funder and 2nd chairman of German Zope User Group (DZUG e.V.) • Author of various Zope and Plone products
  3. 3. Disclaimer This is not a technical talk
  4. 4. Question 1 Who knows Zope?
  5. 5. Question 2 Who uses Zope?
  6. 6. Agenda • Past • Things we have achived with Zope • Present • Where are we standing now • Future • Our goals for the future
  7. 7. The Past - History of Zope • Bobo, Principia • Zope 2 released in 1999 as open-source by Zope Corportation (formerly Digital Creations) • For a long-time the solution for building web-apps on top of Python • Playing in the champions league for a long time competing with J2EE, Coldfusion etc.
  8. 8. Why Zope was/is sexy! • Python • Zope is about object-publishing • integrated fine-grained security model • build-in and pluggable user management • i18n • Unicode-aware • Template languages (ZPT/DTML) • pluggable - reusable • integrated search engine • ZODB • much more......
  9. 9. Other Python frameworks ...are catching up feature-wise
  10. 10. Mistakes made in the past • lots of implicit magic • monolithic in some way • mostly focused on developers • Poor documentation story • zope.org....let‘s skip this topic • steep learning curve
  11. 11. Zope 3 • started in 2001 with the goals: • breaking the Zope core into little pieces (components) • using interfaces and adapters for extending functionality • glueing components together through configuration (ZCML) • ZOPE COMPONENT ARCHITECTURE
  12. 12. Zope 3 (CA) • No more dead-ends • No more magic • Much better documentation • Pluggable architecture • „Explicit is better than implicit“ (GvR)
  13. 13. Zope 3 - the solution? DEATH BY ABSTRACTION (Lennart Regrebo)
  14. 14. The Zope community split-up Plone Zope 2 GROK Zope 3
  15. 15. 2004 Ruby on Rails surfaced
  16. 16. RoR changed a lot • 2004: first release of Ruby on Rails • RoR patterns were adopted by the Python world • „More Python web frameworks than Python keywords“ (Django, Turbogears, Pylons, ...) • Implications for „the old bull“ Zope: • competing with other Python web frameworks • Ouuch.....
  17. 17. The Zope identity crisis • Is Zope 3 the successor of Zope 2? • Will Zope 2 die? • Where are we going? • What is our story for newbies? • How to position ourselves among the other Python web frameworks?
  18. 18. The Zope identity crisis • Jim Fulton: „Two visions“ • Tres Seaver‘s „Whats behind door #3“ talk (2007)
  19. 19. Our vision for the future • We will talk only of the Zope platform • Phase out the term Zope 3 (use Zope Components) • Zope 2 will be the Zope application server • Support Zope 2 for the time being • Zope low-barrier entry point: GROK • Zope components are great
  20. 20. Great stuff for the future • Eggification of Zope • Repeatable buildouts using zc.buildout • Repoze (WSGI integration) • Deliverance • GROK • www.zope.org to be relaunched
  21. 21. GROK • The low-barrier entry point to Zope 3 • Automatic configuration through conventions • Allows you to focus on your app, not on the framework • flat learning curve
  22. 22. Resources • „Two vision“ - Jim Fulton: • http://tinyurl.com/2ehatn • „Behind door #3: Zope futures“ - Tres Seaver • http://tinyurl.com/2egfid • „What Zope did wrong and ...“ - Lennard Regrebro • http://tinyurl.com/2awm58 • www.repoze.org • grok.zope.org
  23. 23. Questions?

×