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
21. Roadmap Team
• Mix of development and industry expertise
• Officially document Plone’s future goals
• Facilitate (not dictate)
• Development
• Marketing
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
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
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
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