Plone Roadmap 2009
- 1. Plone Revised Roadmap Plone 3,4, 5 and beyond
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9. Disclaimer Contents may shiftduring transportation
- 10. Zope 2.11 (or2.12)
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31. Dexterity Through the webschema editing Web-to-filesystem round-trip(!) Pluggable schemas Pluggable behavior Separate packages Faster
- 32. Deliverance xdv Theming done right
- 33. Your theme Plone output Navigation Search Awesome, Inc. Search Navigation Sidebar Sidebar Content Sidebar Content Sidebar Footer Footer
- 34.
- 35. Content type View Form Tile
- 36.
- 37.
- 38. Plone needs tobe faster… …out of the box …for logged in users …in high-end scenarios
- 39. Reduce and simplify the code base
- 40. LINES OF CODE 1200000 1144322 1147545 1122261 1100000 1000000 960456 916360 887059 900000 867263 800000 3.1 ) ) ) 3.0 3.2 ) -26 -17 -14 -09 -02 -03 -01 -05 09 09 09 09 20 20 20 20 k( k( k( k( n n n n Tru Tru Tru Tru Lines of Code/Tempates for Plone including the CMF and Zope stacks
- 41. 1,200,000 1147545 867263 800,000 400,000 0 3.0 nk tru
- 42.
- 43.
- 44.
- 45. 50.0 Anonymous page view 45 37.5 25.0 18 12.5 12 0 Plone 3.3 with ZPT Plone 3.3 with Chameleon Plone trunk
- 46. Logged in view 30.0 24 22.5 15.0 10 7.5 7 0 Plone 3.3 with ZPT Plone 3.3 with Chameleon Plone trunk
- 47. Lacks support forrestricted Python Currently works with views Still some way to go for skin templates Works with Plone 3.3 (some caveats)
- 48. Search Less dependence onCatalog Fewer indexes Queryplan Collective.SOLR
- 49.
- 50.
- 51. Deco A new approach to page editing
- 52.
- 53. Tiles Persistent Stores configuration anddata Form for configuration Live at a unique URL Renders to HTML TILES ARE THE NEW APPS
- 54. Example tiles HTML text Image with caption Lists / stored searches Flash movie/app Form, poll etc. File attachment Fields (AT/Dexterity)
- 55. Deco Full-page editing interface ReplacesKupu DOM manipulation Drag/Drop of Tiles TinyMCE inside text tiles NO GRID MANAGEMENT
- 56.
- 57.
- 58. One content type! A page is also a folder is also a collection
- 59.
- 60. Not the endof content types Custom types still have many uses
- 61. Choice of types Dexterity or Archetypes or NONE
- 62. Plone 3.3 May 2009 Plone 4 End 2009
Editor's Notes
- #2 I’m going to take you through the vision for the next couple of major releases for Plone.
- #3 Goal of 3.x: Stability, predictability, maturity. 3.3 ships Real Soon Now (currently at RC3) Stability comes at the cost of innovation. We cannot do innovate within the scope of Plone 3. That would break the promise of stability. So, happy as we are with Plone 3 — time to get innovating again.
- #4 Plone 4: a cleanup/infrastructure release
- #5 Plone 5: Redefine how content management is done (Until recently known as Plone 4 — confusing, we know ;)
- #6 Then, we invent faster-than-light travel, and… …OK, let’s talk about this one over a beer tonight. ;)
- #7 So, let’s talk about Plone 4 first. This is mostly a cleanup release, with some infrastructural changes.
- #8 We decided to make a Plone 4 release, goal is end of 2009 Not as radical as the work on Plone trunk Will have new features — but stuff that has stabilized through community usage. Features that are too big for a 3.x release. (i,.e require migration, compatibility changes, might break addons)
- #9 With release manager Eric Steele, who should take special care to make sure there are more high-resolution images of him available on the web.
- #10 This is a list of what has been PROPOSED at this point, not what will necessarily land. :) As there is a formal proposal and review process, code to be written on a volunteer basis, and a general lot of uncertainty here — let’s see all of this as speculation, guesswork and hopes.
- #11 BLOB support is the big deal in 2.11 Python 2.6 if we go for Zope 2.12, which I think we should aim for (better unicode memory management in Python, eggified Zope, etc)
- #12 Bug fixes and updates
- #13 Widely used visual editor. The new editing UI for Plone 5 will also be based on TinyMCE. Plone integration already exists. You will still be able to use Kupu with Plone 4, of course. We’ll just switch the default. Also, we won’t change your existing setup when you upgrade — unless you want us to.
- #14 Proper support for BLOBs Store binary objects outside the ZODB, on the filesystem Tested. Jarn has this running in a 7000 employee intranet.
- #15 BTree-based folder implementation, supports ordering Faster Scales better Replaces Folder, ATFolder, Large folder, etc
- #17 Fewer hacks like SecureMailHost.The built-in Zope mailhost is now more advanced than this one. Better for us to have less custom stuff to maintain.
- #18 plone.app.upgrade Upgrade machinery. replaces the suboptimal reinstall button in the current add-on quickinstaller. Makes it simple for product authors to define upgrade steps between versions.
- #19 Newbie (limited/restricted user) — possible to make adjustments to UI and otherwise for certain users. Site admin is a not-fully-fledged admin that can do things like manage users, but not things that can affect the site configuration (ie. install add-ons).
- #20 Stuff like Gloworm
- #21 Commenting is one of the original cool features of the CMF and Plone — but it is way overdue for revision. Currently a Google Summer of Code project.
- #22 Martin has made some interesting improvements here, ability to require a revision note, etc. Simple, non-intrusive, low risk.
- #23 Port over the typography from the new plone.org design Make it color-neutral, so simple customization like adding a company logo always looks good
- #24 OK, time to talk about the exciting release, Plone 5 (I refuse to call this Plone trunk ;)
- #25 Release manager Hanno Schlichting
- #26 Three pillars of Plone 5:
- #30 Approachability means that it should be easy for new developers to pick up
- #31 Replacement for Archetypes.
- #33 Theming fast and simple. Write html, poke holes in it for your Plone content. XDV is deliverance reimplemented as compiled XSLT. Currently has less features than Deliverance, but has much better performance. Laurence’s goal is to have it compile down to a single XSLT transform that can be placed in the pipeline. No special software required to host it. Used on current plone.org.