Iterating Plone

19,508 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
19,508
On SlideShare
0
From Embeds
0
Number of Embeds
144
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Iterating Plone

  1. 1. Iterating Plone Plone Symposium East, 2012Wednesday, May 30, 12
  2. 2. Eric Steele Plone Release ManagerWednesday, May 30, 12
  3. 3. Release Manager • Set deadlines • Try to stick to deadlines • Keep everyone on task • Cut releases • Solve developer disputesWednesday, May 30, 12
  4. 4. Release Manager • Solve developer disputes • Code cop – maintain backwards compatibility • Say "no"Wednesday, May 30, 12
  5. 5. Framework TeamWednesday, May 30, 12
  6. 6. Framework Team • Team of experienced developers • Meet biweekly • Judge merits of changes to Plone coreWednesday, May 30, 12
  7. 7. PLIPs • PLone Improvement Proposal • “What Id like to change in Plone” • “Whos going to help me.” • “Here’s why Plone needs it.” • “Here’s whats going to break.”Wednesday, May 30, 12
  8. 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. 9. Old Framework Team Process • "Heres whats coming in Plone [X]!" • Except most dont.Wednesday, May 30, 12
  10. 10. New Framework Team Process • Regular, timed releases, merge deadline • PLIPs accepted at any timeWednesday, May 30, 12
  11. 11. New Framework Team Process • Each new PLIP gets a champion • FWT representative for the PLIP implementer • Ongoing reviews, direction • If nobodys willing to champion, PLIP is declinedWednesday, May 30, 12
  12. 12. New Framework Team Process • No official review period • When ready for review, the PLIP gets reviewed • Whatevers done/reviewed/accepted at time of release gets merged into that release • Version determined by features available at merge deadlineWednesday, May 30, 12
  13. 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 itWednesday, May 30, 12
  14. 14. plone-framework-team@lists.plone.orgWednesday, May 30, 12
  15. 15. Plone’s RoadmapWednesday, May 30, 12
  16. 16. Previously...Wednesday, May 30, 12
  17. 17. Plone Revised Roadmap Plone 3, 4, 5 and beyondWednesday, May 30, 12
  18. 18. Wednesday, May 30, 12
  19. 19. Wednesday, May 30, 12
  20. 20. Wednesday, May 30, 12
  21. 21. Roadmap Team • Mix of development and industry expertise • Officially document Plone’s future goals • Facilitate (not dictate) • Development • MarketingWednesday, May 30, 12
  22. 22. The Working Draft http://plone.org/roadmapWednesday, May 30, 12
  23. 23. Roadmap • High-level vision for Plones future • Summary of community goals and activitiesWednesday, May 30, 12
  24. 24. Roadmap • Defines Plone’s • Purpose • Competitors • Key industries • Differentiators • Ideal sizeWednesday, May 30, 12
  25. 25. Roadmap • Ideal size • Complexity • Duration • Cost • “Plone is often used for ‘medium-to-large’ projects” • Can’t ignore smaller projectsWednesday, May 30, 12
  26. 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 coreWednesday, May 30, 12
  27. 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 productWednesday, May 30, 12
  28. 28. Plone 4.2Wednesday, May 30, 12
  29. 29. Plone 4.2 • Consistent template code for lists of items (search results, collection results) • Improved search resultsWednesday, May 30, 12
  30. 30. Wednesday, May 30, 12
  31. 31. Plone 4.2 • Consistent template code for lists of items (search results, collection results) • Improved search results • New collectionsWednesday, May 30, 12
  32. 32. Wednesday, May 30, 12
  33. 33. Plone 4.2 • Consistent template code for lists of items (search results, collection results) • Improved search results • New collections • HTML 5 compliantWednesday, May 30, 12
  34. 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" buttonWednesday, May 30, 12
  35. 35. Plone 4.2 • plone.app.theming / DiazoWednesday, May 30, 12
  36. 36. Wednesday, May 30, 12
  37. 37. Plone 4.2 • Python 2.7 • Ship lxml with installers • Package jQuery outside of Plone (plone.app.jquery)Wednesday, May 30, 12
  38. 38. Plone 4.3Wednesday, May 30, 12
  39. 39. Plone 4.3 • Unified batch implementation • Remove kupu • DexterityWednesday, May 30, 12
  40. 40. Wednesday, May 30, 12
  41. 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. 42. Wednesday, May 30, 12
  43. 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.3b1Wednesday, May 30, 12
  44. 44. Plone 4.xWednesday, May 30, 12
  45. 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. 46. Plone 5+Wednesday, May 30, 12
  47. 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. 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. 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. 50. SprintsWednesday, May 30, 12
  51. 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, BrazilWednesday, May 30, 12
  52. 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, USWednesday, May 30, 12
  53. 53. Upcoming Sprints • Post-PSE – State College, US • Buschenschanksprint – Grasnitzberg, Austria • Belgian Beer Sprint – Antwerp, Belgium • Plone Conference 2012 – Arnhem, NetherlandsWednesday, May 30, 12
  54. 54. Iterating PloneWednesday, May 30, 12
  55. 55. It’s time...Wednesday, May 30, 12
  56. 56. Plone 5Wednesday, May 30, 12
  57. 57. 3/1/2013Wednesday, May 30, 12
  58. 58. Plone 5 • Dexterity • Plone’s default content type story • Migration plan for Archetypes content • Multilingual content • Diazo • Plone’s recommended theming story • CMSUIWednesday, May 30, 12

×