1. Iterating Plone
Plone Symposium East, 2012
Wednesday, May 30, 12

2. Eric Steele
Plone Release Manager
Wednesday, May 30, 12

3. Release Manager
• Set deadlines
• Try to stick to deadlines
• Keep everyone on task
• Cut releases
• Solve developer disputes
Wednesday, May 30, 12

4. Release Manager
• Solve developer disputes
• Code cop – maintain backwards compatibility
• Say "no"
Wednesday, May 30, 12

5. Framework Team
Wednesday, May 30, 12

6. Framework Team
• Team of experienced developers
• Meet biweekly
• Judge merits of changes to Plone core
Wednesday, May 30, 12

7. PLIPs
• PLone Improvement Proposal
• “What I'd like to change in Plone”
• “Who's going to help me.”
• “Here’s why Plone needs it.”
• “Here’s what's going to break.”
Wednesday, May 30, 12

8. Old Framework Team Process
• Time for the next release!
1) Call for PLIPs.
2) Wait for PLIPs.
3) Review PLIPs.
4) Merge what works.
Wednesday, May 30, 12

9. Old Framework Team Process
• "Here's what's coming in Plone [X]!"
• Except most don't.
Wednesday, May 30, 12

10. New Framework Team Process
• Regular, timed releases, merge deadline
• PLIPs accepted at any time
Wednesday, May 30, 12

11. New Framework Team Process
• Each new PLIP gets a champion
• FWT representative for the PLIP implementer
• Ongoing reviews, direction
• If nobody's willing to champion, PLIP is
declined
Wednesday, May 30, 12

12. New Framework Team Process
• No official review period
• When ready for review, the PLIP gets
reviewed
• Whatever's done/reviewed/accepted at time of
release gets merged into that release
• Version determined by features available at
merge deadline
Wednesday, May 30, 12

13. New Framework Team Process
• Previous
• Membership term based on release
• Closed voting by former/current members
• Now
• Voting by team
• Serve until you hate it
Wednesday, May 30, 12

14. plone-framework-team@lists.plone.org
Wednesday, May 30, 12

15. Plone’s Roadmap
Wednesday, May 30, 12

16. Previously...
Wednesday, May 30, 12

17. Plone
Revised Roadmap
Plone 3, 4, 5 and beyond
Wednesday, May 30, 12

18. Wednesday, May 30, 12

19. Wednesday, May 30, 12

20. Wednesday, May 30, 12

21. Roadmap Team
• Mix of development and industry expertise
• Officially document Plone’s future goals
• Facilitate (not dictate)
• Development
• Marketing
Wednesday, May 30, 12

22. The Working Draft
http://plone.org/roadmap
Wednesday, May 30, 12

23. Roadmap
• High-level vision for Plone's future
• Summary of community goals and activities
Wednesday, May 30, 12

24. Roadmap
• Defines Plone’s
• Purpose
• Competitors
• Key industries
• Differentiators
• Ideal size
Wednesday, May 30, 12

25. Roadmap
• Ideal size
• Complexity
• Duration
• Cost
• “Plone is often used for ‘medium-to-large’
projects”
• Can’t ignore smaller projects
Wednesday, May 30, 12

26. Roadmap Goals
• Low-cost upgrade
• A spoonful of sugar helps the migration go
down
• Introduce new technologies early, before they
become the standard
• More aggressive about moving under-used/
under-maintained features out of core
Wednesday, May 30, 12

27. Roadmap Goals
• More aggressive about moving under-used/
under-maintained features out of core
• These packages will still exist, but will either
• Ship with Plone, but not installed by
default.
• Exist as an add-on product
Wednesday, May 30, 12

28. Plone 4.2
Wednesday, May 30, 12

29. Plone 4.2
• Consistent template code for lists of items
(search results, collection results)
• Improved search results
Wednesday, May 30, 12

30. Wednesday, May 30, 12

31. Plone 4.2
• Consistent template code for lists of items
(search results, collection results)
• Improved search results
• New collections
Wednesday, May 30, 12

32. Wednesday, May 30, 12

33. Plone 4.2
• Consistent template code for lists of items
(search results, collection results)
• Improved search results
• New collections
• HTML 5 compliant
Wednesday, May 30, 12

34. Plone 4.2
• Consistent template code for lists of items
(search results, collection results)
• Improved search results
• New collections
• HTML 5 compliant
• "Test mail server" button
Wednesday, May 30, 12

35. Plone 4.2
• plone.app.theming / Diazo
Wednesday, May 30, 12

36. Wednesday, May 30, 12

37. Plone 4.2
• Python 2.7
• Ship lxml with installers
• Package jQuery outside of Plone
(plone.app.jquery)
Wednesday, May 30, 12

38. Plone 4.3
Wednesday, May 30, 12

39. Plone 4.3
• Unified batch implementation
• Remove kupu
• Dexterity
Wednesday, May 30, 12

40. Wednesday, May 30, 12

41. Plone 4.3
• Plain text searches ignore accents (95%)
• z3c.form support for portlet add/edit forms
(90%)
• In-Plone theme editor (80%)
Wednesday, May 30, 12

42. Wednesday, May 30, 12

43. Plone 4.3
• Update TinyMCE
• TinyMCE version upgrade 3.2.7 (2009) to
3.4.3 (2011)
• IE9 support
• Dexterity support
• Now available as 1.3b1
Wednesday, May 30, 12

44. Plone 4.x
Wednesday, May 30, 12

45. Plone 4.x
• New event type (80%)
• Integrate portions of jQuery UI (15%)
• Allow changing of content ownership (85%)
• Deprecate KSS (90%)
Wednesday, May 30, 12

46. Plone 5+
Wednesday, May 30, 12

47. Plone 5+
• Chameleon (100%)
• WSGI deployment (85%)
• Blocks/Tiles (70%)
• Deco/Deco Lite (40%)
• CMSUI (65%)
• Make ZMI optional (25%)
Wednesday, May 30, 12

48. Plone 5+
• Standardize on z3c.form for forms (25%)
• Standardize on plone.app.registry for settings
(20%)
• Move away from catalog for navigation (10%)
• Move away from Archetypes (70%)
• plone.api (25%)
Wednesday, May 30, 12

49. Plone 5+
• Standardize on z3c.form for forms (25%)
• Standardize on plone.app.registry for settings
(20%)
• Move away from catalog for navigation (10%)
• Move away from Archetypes (70%)
from plone import api
• plone.api (25%) user = api.user.get(username='bob')
Wednesday, May 30, 12

50. Sprints
Wednesday, May 30, 12

51. Sprints
• Rapture Sprint – State College, US
• Sauna Sprint – Tampere, Finland
• Bristol UI Sprint – Bristol, UK
• Living Statues Sprint – Arnhem, Netherlands
• Zidanca Sprint – Lovke, Slovenia
• Plone Symposium South America – São Paulo,
Brazil
Wednesday, May 30, 12

52. Sprints
• Plone Conference 2011 – San Francisco, US
• Art Sprint – Vienna, Austria
• Cioppino Sprint - Bodega Bay, US
• Plone Konferenz – Munich, Germany
• Plone Open Garden – Sorrento, Italy
• Pre-PSE Strategicesque Sprintacular – State
College, US
Wednesday, May 30, 12

53. Upcoming Sprints
• Post-PSE – State College, US
• Buschenschanksprint – Grasnitzberg, Austria
• Belgian Beer Sprint – Antwerp, Belgium
• Plone Conference 2012 – Arnhem, Netherlands
Wednesday, May 30, 12

54. Iterating Plone
Wednesday, May 30, 12

55. It’s time...
Wednesday, May 30, 12

56. Plone 5
Wednesday, May 30, 12

57. 3/1/2013
Wednesday, May 30, 12

58. Plone 5
• Dexterity
• Plone’s default content type story
• Migration plan for Archetypes content
• Multilingual content
• Diazo
• Plone’s recommended theming story
• CMSUI
Wednesday, May 30, 12