Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Plone Conference 2010 – Where we go from here

1,566 views

Published on

14 guidelines to follow as Plone moves forward.

Published in: Technology, Design
  • Be the first to comment

Plone Conference 2010 – Where we go from here

  1. 1. Where we go from here. Plone 4.1 and beyond Wednesday, October 27, 2010
  2. 2. ...or... Wednesday, October 27, 2010
  3. 3. Things I’ve realized over the past 24 hours. 14 rules for Plone’s future. Wednesday, October 27, 2010
  4. 4. 1. Communicate. Wednesday, October 27, 2010
  5. 5. 1. Communicate. •Where is Plone headed? •Why? Wednesday, October 27, 2010
  6. 6. 1. Communicate. •Not the Framework Team’s job •Reactive, not proactive Wednesday, October 27, 2010
  7. 7. 1. Communicate. •“Pete & Andy” Wednesday, October 27, 2010
  8. 8. 1. Communicate. •Welcome to step 1 Wednesday, October 27, 2010
  9. 9. 2. Acknowledge our weaknesses. Wednesday, October 27, 2010
  10. 10. 2. Acknowledge our weaknesses. •Python will never be as popular as PHP •Steep learning curve •Developer experience Wednesday, October 27, 2010
  11. 11. 3. Play to our strengths. Wednesday, October 27, 2010
  12. 12. 3. Play to our strengths. •Workflow & Security •No revolutionary changes here •Expect some evolution •Site admin role •Workflow manager Wednesday, October 27, 2010
  13. 13. Wednesday, October 27, 2010
  14. 14. 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
  15. 15. Wednesday, October 27, 2010
  16. 16. 3. Play to our strengths. •UI •We’re 10x better than anyone else •Should be 100x •Accessibility, Usability •Mobile devices Wednesday, October 27, 2010
  17. 17. 3. Play to our strengths. •UI Team •Alexander Limi Sisi Nutt Mark Corum Nathan Van Gheem Denys Mishunov Geir Baekholt Wednesday, October 27, 2010
  18. 18. 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
  19. 19. 4. Decide who we want to be. Wednesday, October 27, 2010
  20. 20. 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
  21. 21. 5. Answer “What do I do now?” Wednesday, October 27, 2010
  22. 22. 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
  23. 23. 5. Answer “What do I do now?” •Day 1 •Amberjack •Week 1, Month 1 •Deco, Dexterity Wednesday, October 27, 2010
  24. 24. 6. TTW is A-OK. Wednesday, October 27, 2010
  25. 25. 6. TTW is A-OK. •Stop running from it •Make it both possible and practical Wednesday, October 27, 2010
  26. 26. 6. TTW is A-OK*. •*As long as you can export your changes. •Nobody likes the ZMI. Wednesday, October 27, 2010
  27. 27. 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
  28. 28. 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
  29. 29. 7. Don’t invent new technology, if you can help it. Wednesday, October 27, 2010
  30. 30. 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
  31. 31. 8. The revolution will be backported. Wednesday, October 27, 2010
  32. 32. 8. The revolution will be backported. •Revolution happens in Plone 5. •Those ideas will mature in Plone 4.x Wednesday, October 27, 2010
  33. 33. 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
  34. 34. 8. The revolution will be backported. •Chameleon •Render your templates faster •Needs valid templates •No RestrictedPython support Wednesday, October 27, 2010
  35. 35. 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
  36. 36. 8. The revolution will be backported. •Diazo •Works now •Trivial template cleanup •Plone 4.2? Wednesday, October 27, 2010
  37. 37. 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
  38. 38. 9. Keep moving forward. Wednesday, October 27, 2010
  39. 39. 9. Keep moving forward. •Give a compelling reason to upgrade •Carrots and sticks Wednesday, October 27, 2010
  40. 40. 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
  41. 41. 9. Keep moving forward. •Continue the move to ZCA •CSS/JS/images to browser resources Wednesday, October 27, 2010
  42. 42. 10. Shrink the stack. Wednesday, October 27, 2010
  43. 43. 10. Shrink the stack. •Remove unneeded dependencies •Zope •CMF Wednesday, October 27, 2010
  44. 44. 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
  45. 45. 11. Don’t break sh*t. Wednesday, October 27, 2010
  46. 46. 11. Don’t break sh*t. •Provide smooth upgrade paths for data •Provide clear product migration instructions Wednesday, October 27, 2010
  47. 47. 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
  48. 48. 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
  49. 49. 12. Install everywhere. Wednesday, October 27, 2010
  50. 50. 12. Install everywhere. •Debian/Ubuntu, Redhat packages in the works •VMWare images •EC2 Wednesday, October 27, 2010
  51. 51. 12. Install everywhere. •CPanel •Relstorage + WSGI •Within the year Wednesday, October 27, 2010
  52. 52. 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
  53. 53. 13. Distributions will be important. Wednesday, October 27, 2010
  54. 54. 13. Distributions will be important. •Provide one-click sites for specific use- cases. •Education •NGO •Intranet •Social Wednesday, October 27, 2010
  55. 55. 13. Distributions will be important. •Not just add-ons •Clear set of policies for integration Wednesday, October 27, 2010
  56. 56. 13. Distributions will be important. •Plone 4.1 makes it easier •Package to include new default add-ons •Exclude existing ones Wednesday, October 27, 2010
  57. 57. 13. Distributions will be important. •Go see my boss •Education distribution in the works now. Wednesday, October 27, 2010
  58. 58. Sidebar! •Stop using “Plone4*” name •Plone4Artists •Plone4Universities •You’ll feel silly when Plone 5 comes out. Wednesday, October 27, 2010
  59. 59. 14. Quality. Quality. Quality. Wednesday, October 27, 2010
  60. 60. 14. Quality. Quality. Quality •Improve quality control at all stages of the development process Wednesday, October 27, 2010
  61. 61. 14. Quality. Quality. Quality •PLIP Process •UI Team •Documentation Wednesday, October 27, 2010
  62. 62. 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
  63. 63. 14. Quality. Quality. Quality •Testing •Load testing •Plone 4 is fast •We want to keep it that way Wednesday, October 27, 2010
  64. 64. 14. Quality. Quality. Quality •QA Team •Test releases before they go public •“soft-release” •Catch regressions before hurt users Wednesday, October 27, 2010
  65. 65. 14. Quality. Quality. Quality •QA Team •qa-team@lists.plone.org •Open session on Friday •QA sprint on Saturday Wednesday, October 27, 2010
  66. 66. 14. Quality. Quality. Quality •QA Sprint •QA checklists •Selenium testing •Performance testing •Free food! Wednesday, October 27, 2010

×