iterating plone

Iterating PlonePlone Symposium East, 2012

Wednesday, May 30, 12

Eric SteelePlone Release Manager


Release Manager•Set deadlines

•Try to stick to deadlines

•Keep everyone on task

•Cut releases

•Solve developer disputes


Release Manager•Solve developer disputes

•Code cop – maintain backwards compatibility

•Say "no"


Framework Team


Framework Team•Team of experienced developers

•Meet biweekly

• Judge merits of changes to Plone core


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.”


Old Framework Team Process

•Time for the next release!

1) Call for PLIPs.

2) Wait for PLIPs.

3) Review PLIPs.

4) Merge what works.


Old Framework Team Process

• "Here's what's coming in Plone [X]!"

•Except most don't.


New Framework Team Process

•Regular, timed releases, merge deadline

•PLIPs accepted at any time



•Each new PLIP gets a champion

•FWT representative for the PLIP implementer

•Ongoing reviews, direction

• If nobody's willing to champion, PLIP is declined



•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



•Previous

•Membership term based on release

•Closed voting by former/current members

•Now

•Voting by team

•Serve until you hate it


[email protected]


Plone’s Roadmap


Previously...


PloneRevised RoadmapPlone 3, 4, 5 and beyond


Roadmap Team•Mix of development and industry expertise

•Officially document Plone’s future goals

•Facilitate (not dictate)

•Development

•Marketing


The Working Drafthttp://plone.org/roadmap


http://plone.org/roadmap

http://plone.org/roadmap

Roadmap•High-level vision for Plone's future

•Summary of community goals and activities


Roadmap•Defines Plone’s

•Purpose

•Competitors

•Key industries

•Differentiators

• Ideal size


Roadmap• Ideal size

•Complexity

•Duration

•Cost

•“Plone is often used for ‘medium-to-large’ projects”

•Can’t ignore smaller projectsWednesday, May 30, 12

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


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


Plone 4.2


Plone 4.2•Consistent template code for lists of items

(search results, collection results)

• Improved search results





•New collections





•New collections

•HTML 5 compliant





•New collections

•HTML 5 compliant

• "Test mail server" button


Plone 4.2•plone.app.theming / Diazo


Plone 4.2•Python 2.7

•Ship lxml with installers

•Package jQuery outside of Plone (plone.app.jquery)


Plone 4.3


Plone 4.3•Unified batch implementation

•Remove kupu

•Dexterity


*Wednesday, May 30, 12

Plone 4.3•Plain text searches ignore accents (95%)

•z3c.form support for portlet add/edit forms (90%)

• In-Plone theme editor (80%)


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


Plone 4.x


Plone 4.x•New event type (80%)

• Integrate portions of jQuery UI (15%)

•Allow changing of content ownership (85%)

•Deprecate KSS (90%)


Plone 5+


Plone 5+•Chameleon (100%)

•WSGI deployment (85%)

•Blocks/Tiles (70%)

•Deco/Deco Lite (40%)

•CMSUI (65%)

•Make ZMI optional (25%)


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%)


•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%)

Plone 5+

from plone import apiuser = api.user.get(username='bob')


Sprints


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


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


Upcoming Sprints•Post-PSE – State College, US

•Buschenschanksprint – Grasnitzberg, Austria

•Belgian Beer Sprint – Antwerp, Belgium

•Plone Conference 2012 – Arnhem, Netherlands


Iterating Plone


It’s time...


Plone 5


3/1/2013


Plone 5•Dexterity

•Plone’s default content type story

•Migration plan for Archetypes content

•Multilingual content

•Diazo

•Plone’s recommended theming story

•CMSUI


iterating plone

Technology

plone corewednesday

plone x

plone whos

plone theme editor

collection results

new plip

new technologies

release version