Heading to go here heading to go here Impact statement to go here impact statement to go here.
Plone Conference 2010 – Where we go from here
-
Upload
eric-steele -
Category
Technology
-
view
1.203 -
download
1
description
Transcript of Plone Conference 2010 – Where we go from here
Where we go from here.
Plone 4.1 and beyond
Wednesday, October 27, 2010
...or...
Wednesday, October 27, 2010
Things I’ve realized over the past 24 hours.
14 rules for Plone’s future.
Wednesday, October 27, 2010
1.Communicate.
Wednesday, October 27, 2010
1. Communicate.•Where is Plone headed?
•Why?
Wednesday, October 27, 2010
1. Communicate.•Not the Framework Team’s job
•Reactive, not proactive
Wednesday, October 27, 2010
1. Communicate.•“Pete & Andy”
Wednesday, October 27, 2010
1. Communicate.•Welcome to step 1
Wednesday, October 27, 2010
2.Acknowledge our
weaknesses.
Wednesday, October 27, 2010
2. Acknowledge our weaknesses.
•Python will never be as popular as PHP
•Steep learning curve
•Developer experience
Wednesday, October 27, 2010
3. Play to our strengths.
Wednesday, October 27, 2010
3. Play to our strengths.•Workflow & Security
•No revolutionary changes here
•Expect some evolution
•Site admin role
•Workflow manager
Wednesday, October 27, 2010
Wednesday, October 27, 2010
3. Play to our strengths.•Workflow & Security
•No revolutionary changes here
•Expect some evolution
•Site admin role
•Workflow manager
•Local roles viewer
Wednesday, October 27, 2010
Wednesday, October 27, 2010
3. Play to our strengths.
•UI
•We’re 10x better than anyone else
•Should be 100x
•Accessibility, Usability
•Mobile devices
Wednesday, October 27, 2010
3. Play to our strengths.
•UI Team
•Alexander LimiSisi NuttMark CorumNathan Van GheemDenys MishunovGeir Baekholt
Wednesday, October 27, 2010
3. Play to our strengths.
•UI Team
•Evaluate new features for usability, accessibility
•Generate UI "style guide"
•Propose changes to existing features
•Wireframe new ones
Wednesday, October 27, 2010
4. Decide who we want
to be.
Wednesday, October 27, 2010
4. Decide who we want to be.
•Describing Plone is difficult
•Intranets, Complex sites
•Workflow, security, many editors
•Mid-to-Large sized sites
Wednesday, October 27, 2010
5. Answer “What do I
do now?”
Wednesday, October 27, 2010
5. Answer “What do I do now?”
•What are the first-steps with Plone?
•What should I be able to do after 1 day?
•1 week?
•1 month?
Wednesday, October 27, 2010
5. Answer “What do I do now?”
•Day 1
•Amberjack
•Week 1, Month 1
•Deco, Dexterity
Wednesday, October 27, 2010
6. TTW is A-OK.
Wednesday, October 27, 2010
6. TTW is A-OK.•Stop running from it
•Make it both possible and practical
Wednesday, October 27, 2010
6. TTW is A-OK*.•*As long as you can export your
changes.
•Nobody likes the ZMI.
Wednesday, October 27, 2010
6. TTW is A-OK*.•Exports? We can do that.
•Wait... we can do imports too!
•Workflows
•Dexterity types
•Diazo themes
•Templates/Images/CSS/JS
Wednesday, October 27, 2010
6. TTW is A-OK*.•So?
•Download and install themes, types, workflows all without restarting Plone.
•Coming in Plone 4.2
Wednesday, October 27, 2010
7.Don’t invent new technology, if you
can help it.
Wednesday, October 27, 2010
7. Don’t invent new technology, if you can help it.
•Leverage outside technology, where possible
•KSS
•Begin to deprecate in Plone 4.1
•Gone in Plone 5.
Wednesday, October 27, 2010
8. The revolution will be
backported.
Wednesday, October 27, 2010
8. The revolution will be backported.
•Revolution happens in Plone 5.
•Those ideas will mature in Plone 4.x
Wednesday, October 27, 2010
8. The revolution will be backported.
•Practical considerations prevent inclusion in Plone 4
•Work (for some definition of “work”)
•Integration, with varying amounts of effort
Wednesday, October 27, 2010
8. The revolution will be backported.
•Chameleon
•Render your templates faster
•Needs valid templates
•No RestrictedPython support
Wednesday, October 27, 2010
8. The revolution will be backported.
•Dexterity
•Works in Plone 4
•Doesn’t quite integrate
•Will improve with each 4.x release
Wednesday, October 27, 2010
8. The revolution will be backported.
•Diazo
•Works now
•Trivial template cleanup
•Plone 4.2?
Wednesday, October 27, 2010
8. The revolution will be backported.
•Deco
•“Runs” in “Plone 4”
•Doesn’t necessarily make sense in that context.
•Plan: It works, but limits what your Plone site can do.
Wednesday, October 27, 2010
9. Keep moving
forward.
Wednesday, October 27, 2010
9. Keep moving forward.
•Give a compelling reason to upgrade
•Carrots and sticks
Wednesday, October 27, 2010
9. Keep moving forward.
•Continue the move to ZCA
•Tools to Utilities and Views
•Persistent data stored in plone.app registry
•Restricted Python to Views
•Old-style templates to Views
Wednesday, October 27, 2010
9. Keep moving forward.
•Continue the move to ZCA
•CSS/JS/images to browser resources
Wednesday, October 27, 2010
10. Shrink the stack.
Wednesday, October 27, 2010
10. Shrink the stack.•Remove unneeded dependencies
•Zope
•CMF
Wednesday, October 27, 2010
10. Shrink the stack.•Plone 4.1/Zope 2.13
•Welcome to the Zope Toolkit
•Less Five.* integration layers
•zope.app.* removal
Wednesday, October 27, 2010
11.Don’t break sh*t.
Wednesday, October 27, 2010
11. Don’t break sh*t.•Provide smooth upgrade paths for
data
•Provide clear product migration instructions
Wednesday, October 27, 2010
11. Don’t break sh*t.•Deprecate, don’t decimate
•We’re much better at this than others
•Stop saying “will go away”
Wednesday, October 27, 2010
11. Don’t break sh*t.•For example, Archetypes
•Still around in Plone 5
•At a cost
•Gone in Plone 6
•~5-6 Years
•Plan accordingly
Wednesday, October 27, 2010
12. Install everywhere.
Wednesday, October 27, 2010
12. Install everywhere.
•Debian/Ubuntu, Redhat packages in the works
•VMWare images
•EC2
Wednesday, October 27, 2010
12. Install everywhere.
•CPanel
•Relstorage + WSGI
•Within the year
Wednesday, October 27, 2010
12. Install everywhere.
•CPanel
•Welcome to $20 hosting
•Easy-to-get = easy-to-evaluate
•Equal footing with Joomla, Drupal
•Kick ass
Wednesday, October 27, 2010
13. Distributions will be
important.
Wednesday, October 27, 2010
13. Distributions will be important.
•Provide one-click sites for specific use-cases.
•Education
•NGO
•Intranet
•Social
Wednesday, October 27, 2010
13. Distributions will be important.
•Not just add-ons
•Clear set of policies for integration
Wednesday, October 27, 2010
13. Distributions will be important.
•Plone 4.1 makes it easier
•Package to include new defaultadd-ons
•Exclude existing ones
Wednesday, October 27, 2010
13. Distributions will be important.
•Go see my boss
•Education distribution in the works now.
Wednesday, October 27, 2010
Sidebar!
•Stop using “Plone4*” name
•Plone4Artists
•Plone4Universities
•You’ll feel silly when Plone 5 comes out.
Wednesday, October 27, 2010
14.Quality. Quality.
Quality.
Wednesday, October 27, 2010
14. Quality. Quality. Quality
•Improve quality control at all stages of the development process
Wednesday, October 27, 2010
14. Quality. Quality. Quality
•PLIP Process
•UI Team
•Documentation
Wednesday, October 27, 2010
14. Quality. Quality. Quality
•Testing
•Continuous integration testing
•As soon as it’s changed, it’s checked
•Catch regressions as they happen
•Selenium
Wednesday, October 27, 2010
14. Quality. Quality. Quality
•Testing
•Load testing
•Plone 4 is fast
•We want to keep it that way
Wednesday, October 27, 2010
14. Quality. Quality. Quality
•QA Team
•Test releases before they go public
•“soft-release”
•Catch regressions before hurt users
Wednesday, October 27, 2010
14. Quality. Quality. Quality
•QA Team
•Open session on Friday
•QA sprint on Saturday
Wednesday, October 27, 2010
14. Quality. Quality. Quality
•QA Sprint
•QA checklists
•Selenium testing
•Performance testing
•Free food!
Wednesday, October 27, 2010