• Like

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Plone Conference 2010 – Where we go from here

  • 1,190 views
Uploaded on

14 guidelines to follow as Plone moves forward.

14 guidelines to follow as Plone moves forward.

More in: Technology , Design
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,190
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
18
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide




  • As a developer community, we need to be better at communicating our architectural goals
    What are our plans and why do we want to do this
  • As a developer community, we need to be better at communicating our architectural goals
    What are our plans and why do we want to do this


  • Written 3 years ago.


  • Your average 14 year old kid is much more likely to pick up PHP
  • Your average 14 year old kid is much more likely to pick up PHP
  • Your average 14 year old kid is much more likely to pick up PHP














  • Our user interface is 10x better than anyone else out there


  • Our user interface is 10x better than anyone else out there


  • Our user interface is 10x better than anyone else out there


  • Our user interface is 10x better than anyone else out there


  • Our user interface is 10x better than anyone else out there


  • I’m pleased to announce that Plone now has an official UI team.


  • I’m pleased to announce that Plone now has an official UI team.


  • Generate UI "style guide" best practices documentation
  • Generate UI "style guide" best practices documentation
  • Generate UI "style guide" best practices documentation
  • Generate UI "style guide" best practices documentation
  • Generate UI "style guide" best practices documentation

  • Hard to describe plone because the answer largely depends on what each user is using it for.

    Admit that Plone isn’t really a good fit for blogs, 3 page sites.
  • Hard to describe plone because the answer largely depends on what each user is using it for.

    Admit that Plone isn’t really a good fit for blogs, 3 page sites.
  • Hard to describe plone because the answer largely depends on what each user is using it for.

    Admit that Plone isn’t really a good fit for blogs, 3 page sites.
  • Hard to describe plone because the answer largely depends on what each user is using it for.

    Admit that Plone isn’t really a good fit for blogs, 3 page sites.

  • Determine the first steps with Plone make those easier

  • Determine the first steps with Plone make those easier

  • Determine the first steps with Plone make those easier

  • Determine the first steps with Plone make those easier

  • Determine the first steps with Plone make those easier

  • Determine the first steps with Plone make those easier

  • Determine the first steps with Plone make those easier

  • Determine the first steps with Plone make those easier






  • And we can already export a lot of things right now thanks to GenericSetup.
  • And we can already export a lot of things right now thanks to GenericSetup.
  • And we can already export a lot of things right now thanks to GenericSetup.
  • And we can already export a lot of things right now thanks to GenericSetup.
  • And we can already export a lot of things right now thanks to GenericSetup.
  • And we can already export a lot of things right now thanks to GenericSetup.
  • So what does that mean?

    And I’ll go out on a limb now and say that we’re going to start seeing that as early as Plone 4.2.
  • So what does that mean?

    And I’ll go out on a limb now and say that we’re going to start seeing that as early as Plone 4.2.
  • So what does that mean?

    And I’ll go out on a limb now and say that we’re going to start seeing that as early as Plone 4.2.

  • KSS didn’t get the adoption we’d hoped for. jQuery has proven to be a better long-term solution.
    We’ll begin to move core Plone features away from using KSS in Plone 4.1. Should give us a 15%-50% speedup.
    Expect it to be gone in Plone 5.
  • KSS didn’t get the adoption we’d hoped for. jQuery has proven to be a better long-term solution.
    We’ll begin to move core Plone features away from using KSS in Plone 4.1. Should give us a 15%-50% speedup.
    Expect it to be gone in Plone 5.
  • KSS didn’t get the adoption we’d hoped for. jQuery has proven to be a better long-term solution.
    We’ll begin to move core Plone features away from using KSS in Plone 4.1. Should give us a 15%-50% speedup.
    Expect it to be gone in Plone 5.
  • KSS didn’t get the adoption we’d hoped for. jQuery has proven to be a better long-term solution.
    We’ll begin to move core Plone features away from using KSS in Plone 4.1. Should give us a 15%-50% speedup.
    Expect it to be gone in Plone 5.

  • We won't see many of the "revolutionary" things talked about during the keynote as part of the plone core until Plone 5.


  • We won't see many of the "revolutionary" things talked about during the keynote as part of the plone core until Plone 5.


  • Practical considerations mean that we can’t do many of these by default in Plone 4 right now.

    But they can be integrated, with varying degrees of effort.
  • Practical considerations mean that we can’t do many of these by default in Plone 4 right now.

    But they can be integrated, with varying degrees of effort.
  • Practical considerations mean that we can’t do many of these by default in Plone 4 right now.

    But they can be integrated, with varying degrees of effort.
  • Alan talked about Chameleon earlier.
    Chameleon can make your templates render substantially faster. It’s a quick way to optimize your site.
    But you need to make sure your templates all validate as xml.
    Enfold has put a lot of work into this over the past month.

  • Alan talked about Chameleon earlier.
    Chameleon can make your templates render substantially faster. It’s a quick way to optimize your site.
    But you need to make sure your templates all validate as xml.
    Enfold has put a lot of work into this over the past month.

  • Alan talked about Chameleon earlier.
    Chameleon can make your templates render substantially faster. It’s a quick way to optimize your site.
    But you need to make sure your templates all validate as xml.
    Enfold has put a lot of work into this over the past month.

  • Alan talked about Chameleon earlier.
    Chameleon can make your templates render substantially faster. It’s a quick way to optimize your site.
    But you need to make sure your templates all validate as xml.
    Enfold has put a lot of work into this over the past month.

  • Works in Plone 4 now.
    But there are a number of issues that prevent it from being fully integrated into the way Plone currently works. Things like relationships don’t work well.

    Plone 4.1 fixes some of those issues and the remainder of the 4.x series will include even more integration tweaks.
  • Works in Plone 4 now.
    But there are a number of issues that prevent it from being fully integrated into the way Plone currently works. Things like relationships don’t work well.

    Plone 4.1 fixes some of those issues and the remainder of the 4.x series will include even more integration tweaks.
  • Works in Plone 4 now.
    But there are a number of issues that prevent it from being fully integrated into the way Plone currently works. Things like relationships don’t work well.

    Plone 4.1 fixes some of those issues and the remainder of the 4.x series will include even more integration tweaks.
  • Works in Plone 4 now.
    But there are a number of issues that prevent it from being fully integrated into the way Plone currently works. Things like relationships don’t work well.

    Plone 4.1 fixes some of those issues and the remainder of the 4.x series will include even more integration tweaks.




  • If you look at the deco brewery buildout that recently came out, you can actually run Deco in Plone 4.

    Deco assumes a lot of changes
  • If you look at the deco brewery buildout that recently came out, you can actually run Deco in Plone 4.

    Deco assumes a lot of changes
  • If you look at the deco brewery buildout that recently came out, you can actually run Deco in Plone 4.

    Deco assumes a lot of changes
  • If you look at the deco brewery buildout that recently came out, you can actually run Deco in Plone 4.

    Deco assumes a lot of changes

  • While the Framework Team thinks it's important to do things like factor custom output transformations out of the editors, we realize that it's things like a new collections UI that are going to prompt people to stay current.

    If we can keep our users following the front-end carrot, the stick needed to handle back-end upgrades won't have to be so big.
  • While the Framework Team thinks it's important to do things like factor custom output transformations out of the editors, we realize that it's things like a new collections UI that are going to prompt people to stay current.

    If we can keep our users following the front-end carrot, the stick needed to handle back-end upgrades won't have to be so big.
  • We need to finish what we started in Plone 3.
  • We need to finish what we started in Plone 3.
  • We need to finish what we started in Plone 3.
  • We need to finish what we started in Plone 3.
  • We need to finish what we started in Plone 3.


  • Plone 4 has already removed a number of unneeded dependencies on CMF and Zope packages. As we move forward, we can remove even more.
  • Plone 4 has already removed a number of unneeded dependencies on CMF and Zope packages. As we move forward, we can remove even more.
  • Plone 4 has already removed a number of unneeded dependencies on CMF and Zope packages. As we move forward, we can remove even more.







  • Drupal, Sharepoint have gotten this horribly wrong.
  • Drupal, Sharepoint have gotten this horribly wrong.
  • Drupal, Sharepoint have gotten this horribly wrong.
  • It’ll work, but you won’t get things like Deco layouts.
  • It’ll work, but you won’t get things like Deco layouts.
  • It’ll work, but you won’t get things like Deco layouts.
  • It’ll work, but you won’t get things like Deco layouts.
  • It’ll work, but you won’t get things like Deco layouts.
  • It’ll work, but you won’t get things like Deco layouts.




  • Relstorage introduced in 4.0 and the WSGI coming in 4.1 mean that within the year, we should be able to run a Plone instance from CPanel
  • Relstorage introduced in 4.0 and the WSGI coming in 4.1 mean that within the year, we should be able to run a Plone instance from CPanel
  • Relstorage introduced in 4.0 and the WSGI coming in 4.1 mean that within the year, we should be able to run a Plone instance from CPanel
  • So that anyone buying a cheap hosting package now has the option of installing and evaluating Plone.
    That puts us on equal footing with other open source CMSs like Joomla and Drupal
    And since we already light years ahead of them in terms of out-of-the-box features, and have a rapidly improving first-run experience thanks to things like Amberjack, we can kick their asses.
  • So that anyone buying a cheap hosting package now has the option of installing and evaluating Plone.
    That puts us on equal footing with other open source CMSs like Joomla and Drupal
    And since we already light years ahead of them in terms of out-of-the-box features, and have a rapidly improving first-run experience thanks to things like Amberjack, we can kick their asses.
  • So that anyone buying a cheap hosting package now has the option of installing and evaluating Plone.
    That puts us on equal footing with other open source CMSs like Joomla and Drupal
    And since we already light years ahead of them in terms of out-of-the-box features, and have a rapidly improving first-run experience thanks to things like Amberjack, we can kick their asses.
  • So that anyone buying a cheap hosting package now has the option of installing and evaluating Plone.
    That puts us on equal footing with other open source CMSs like Joomla and Drupal
    And since we already light years ahead of them in terms of out-of-the-box features, and have a rapidly improving first-run experience thanks to things like Amberjack, we can kick their asses.
  • So that anyone buying a cheap hosting package now has the option of installing and evaluating Plone.
    That puts us on equal footing with other open source CMSs like Joomla and Drupal
    And since we already light years ahead of them in terms of out-of-the-box features, and have a rapidly improving first-run experience thanks to things like Amberjack, we can kick their asses.








  • Plone 4.1 will make it much easier to
  • Plone 4.1 will make it much easier to
  • Plone 4.1 will make it much easier to
  • If you go to see Mike Halm’s talk this afternoon, he’ll be discussing our efforts to create a distribution focused on sites for educational institutions.
  • If you go to see Mike Halm’s talk this afternoon, he’ll be discussing our efforts to create a distribution focused on sites for educational institutions.
  • Plone4Artists is a company making themes for the latest Plone, right?
    Plone4Universities provide training?

    And when Plone 5 comes out, everyone will wonder when you’re going to upgrade.
  • Plone4Artists is a company making themes for the latest Plone, right?
    Plone4Universities provide training?

    And when Plone 5 comes out, everyone will wonder when you’re going to upgrade.
  • Plone4Artists is a company making themes for the latest Plone, right?
    Plone4Universities provide training?

    And when Plone 5 comes out, everyone will wonder when you’re going to upgrade.
  • Plone4Artists is a company making themes for the latest Plone, right?
    Plone4Universities provide training?

    And when Plone 5 comes out, everyone will wonder when you’re going to upgrade.


  • UI Team will assist the framework team in evaluating PLIPs for consistency, usability
    Documentation required up front, gives the Docs Team some lead time on getting our documentation up to date with changes/new features
  • UI Team will assist the framework team in evaluating PLIPs for consistency, usability
    Documentation required up front, gives the Docs Team some lead time on getting our documentation up to date with changes/new features
  • UI Team will assist the framework team in evaluating PLIPs for consistency, usability
    Documentation required up front, gives the Docs Team some lead time on getting our documentation up to date with changes/new features





  • Enfold is providing us with nightly load testing.
  • Enfold is providing us with nightly load testing.
  • Enfold is providing us with nightly load testing.
  • Enfold is providing us with nightly load testing.
  • At last year’s conference, we began the discussion of creating an official QA team. It’s been slow going so far.

  • At last year’s conference, we began the discussion of creating an official QA team. It’s been slow going so far.

  • At last year’s conference, we began the discussion of creating an official QA team. It’s been slow going so far.

  • At last year’s conference, we began the discussion of creating an official QA team. It’s been slow going so far.










Transcript

  • 1. Where we go from here. Plone 4.1 and beyond
  • 2. ...or...
  • 3. Things I’ve realized over the past 24 hours. 14 rules for Plone’s future.
  • 4. 1. Communicate.
  • 5. 1. Communicate.
  • 6. 1. Communicate. •Where is Plone headed?
  • 7. 1. Communicate. •Where is Plone headed? •Why?
  • 8. 1. Communicate.
  • 9. 1. Communicate. •Not the Framework Team’s job
  • 10. 1. Communicate. •Not the Framework Team’s job •Reactive, not proactive
  • 11. 1. Communicate. •“Pete & Andy”
  • 12. 1. Communicate. •Welcome to step 1
  • 13. 2. Acknowledge our weaknesses.
  • 14. 2. Acknowledge our weaknesses.
  • 15. 2. Acknowledge our weaknesses. •Python will never be as popular as PHP
  • 16. 2. Acknowledge our weaknesses. •Python will never be as popular as PHP •Steep learning curve
  • 17. 2. Acknowledge our weaknesses. •Python will never be as popular as PHP •Steep learning curve •Developer experience
  • 18. 3. Play to our strengths.
  • 19. 3. Play to our strengths.
  • 20. 3. Play to our strengths. •Workflow & Security
  • 21. 3. Play to our strengths. •Workflow & Security •No revolutionary changes here
  • 22. 3. Play to our strengths. •Workflow & Security •No revolutionary changes here •Expect some evolution
  • 23. 3. Play to our strengths. •Workflow & Security •No revolutionary changes here •Expect some evolution •Site admin role
  • 24. 3. Play to our strengths. •Workflow & Security •No revolutionary changes here •Expect some evolution •Site admin role •Workflow manager
  • 25. 3. Play to our strengths.
  • 26. 3. Play to our strengths. •Workflow & Security
  • 27. 3. Play to our strengths. •Workflow & Security •No revolutionary changes here
  • 28. 3. Play to our strengths. •Workflow & Security •No revolutionary changes here •Expect some evolution
  • 29. 3. Play to our strengths. •Workflow & Security •No revolutionary changes here •Expect some evolution •Site admin role
  • 30. 3. Play to our strengths. •Workflow & Security •No revolutionary changes here •Expect some evolution •Site admin role •Workflow manager
  • 31. 3. Play to our strengths. •Workflow & Security •No revolutionary changes here •Expect some evolution •Site admin role •Workflow manager •Local roles viewer
  • 32. 3. Play to our strengths.
  • 33. 3. Play to our strengths. •UI
  • 34. 3. Play to our strengths. •UI •We’re 10x better than anyone else
  • 35. 3. Play to our strengths. •UI •We’re 10x better than anyone else •Should be 100x
  • 36. 3. Play to our strengths. •UI •We’re 10x better than anyone else •Should be 100x •Accessibility, Usability
  • 37. 3. Play to our strengths. •UI •We’re 10x better than anyone else •Should be 100x •Accessibility, Usability •Mobile devices
  • 38. 3. Play to our strengths.
  • 39. 3. Play to our strengths. •UI Team
  • 40. 3. Play to our strengths. •UI Team •Alexander Limi Sisi Nutt Mark Corum Nathan Van Gheem Denys Mishunov Geir Baekholt
  • 41. 3. Play to our strengths.
  • 42. 3. Play to our strengths. •UI Team
  • 43. 3. Play to our strengths. •UI Team •Evaluate new features for usability, accessibility
  • 44. 3. Play to our strengths. •UI Team •Evaluate new features for usability, accessibility •Generate UI "style guide"
  • 45. 3. Play to our strengths. •UI Team •Evaluate new features for usability, accessibility •Generate UI "style guide" •Propose changes to existing features
  • 46. 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
  • 47. 4. Decide who we want to be.
  • 48. 4. Decide who we want to be.
  • 49. 4. Decide who we want to be. •Describing Plone is difficult
  • 50. 4. Decide who we want to be. •Describing Plone is difficult •Intranets, Complex sites
  • 51. 4. Decide who we want to be. •Describing Plone is difficult •Intranets, Complex sites •Workflow, security, many editors
  • 52. 4. Decide who we want to be. •Describing Plone is difficult •Intranets, Complex sites •Workflow, security, many editors •Mid-to-Large sized sites
  • 53. 5. Answer “What do I do now?”
  • 54. 5. Answer “What do I do now?”
  • 55. 5. Answer “What do I do now?” •What are the first-steps with Plone?
  • 56. 5. Answer “What do I do now?” •What are the first-steps with Plone? •What should I be able to do after 1 day?
  • 57. 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?
  • 58. 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?
  • 59. 5. Answer “What do I do now?”
  • 60. 5. Answer “What do I do now?” •Day 1
  • 61. 5. Answer “What do I do now?” •Day 1 •Amberjack
  • 62. 5. Answer “What do I do now?” •Day 1 •Amberjack •Week 1, Month 1
  • 63. 5. Answer “What do I do now?” •Day 1 •Amberjack •Week 1, Month 1 •Deco, Dexterity
  • 64. 6. TTW is A-OK.
  • 65. 6. TTW is A-OK.
  • 66. 6. TTW is A-OK. •Stop running from it
  • 67. 6. TTW is A-OK. •Stop running from it •Make it both possible and practical
  • 68. 6. TTW is A-OK*.
  • 69. 6. TTW is A-OK*. •*As long as you can export your changes.
  • 70. 6. TTW is A-OK*. •*As long as you can export your changes. •Nobody likes the ZMI.
  • 71. 6. TTW is A-OK*.
  • 72. 6. TTW is A-OK*. •Exports? We can do that.
  • 73. 6. TTW is A-OK*. •Exports? We can do that. •Wait... we can do imports too!
  • 74. 6. TTW is A-OK*. •Exports? We can do that. •Wait... we can do imports too! •Workflows
  • 75. 6. TTW is A-OK*. •Exports? We can do that. •Wait... we can do imports too! •Workflows •Dexterity types
  • 76. 6. TTW is A-OK*. •Exports? We can do that. •Wait... we can do imports too! •Workflows •Dexterity types •Diazo themes
  • 77. 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
  • 78. 6. TTW is A-OK*.
  • 79. 6. TTW is A-OK*. •So?
  • 80. 6. TTW is A-OK*. •So? •Download and install themes, types, workflows all without restarting Plone.
  • 81. 6. TTW is A-OK*. •So? •Download and install themes, types, workflows all without restarting Plone. •Coming in Plone 4.2
  • 82. 7. Don’t invent new technology, if you can help it.
  • 83. 7. Don’t invent new technology, if you can help it.
  • 84. 7. Don’t invent new technology, if you can help it. •Leverage outside technology, where possible
  • 85. 7. Don’t invent new technology, if you can help it. •Leverage outside technology, where possible •KSS
  • 86. 7. Don’t invent new technology, if you can help it. •Leverage outside technology, where possible •KSS •Begin to deprecate in Plone 4.1
  • 87. 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.
  • 88. 8. The revolution will be backported.
  • 89. 8. The revolution will be backported.
  • 90. 8. The revolution will be backported. •Revolution happens in Plone 5.
  • 91. 8. The revolution will be backported. •Revolution happens in Plone 5. •Those ideas will mature in Plone 4.x
  • 92. 8. The revolution will be backported.
  • 93. 8. The revolution will be backported. •Practical considerations prevent inclusion in Plone 4
  • 94. 8. The revolution will be backported. •Practical considerations prevent inclusion in Plone 4 •Work (for some definition of “work”)
  • 95. 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
  • 96. 8. The revolution will be backported.
  • 97. 8. The revolution will be backported. •Chameleon
  • 98. 8. The revolution will be backported. •Chameleon •Render your templates faster
  • 99. 8. The revolution will be backported. •Chameleon •Render your templates faster •Needs valid templates
  • 100. 8. The revolution will be backported. •Chameleon •Render your templates faster •Needs valid templates •No RestrictedPython support
  • 101. 8. The revolution will be backported.
  • 102. 8. The revolution will be backported. •Dexterity
  • 103. 8. The revolution will be backported. •Dexterity •Works in Plone 4
  • 104. 8. The revolution will be backported. •Dexterity •Works in Plone 4 •Doesn’t quite integrate
  • 105. 8. The revolution will be backported. •Dexterity •Works in Plone 4 •Doesn’t quite integrate •Will improve with each 4.x release
  • 106. 8. The revolution will be backported.
  • 107. 8. The revolution will be backported. •Diazo
  • 108. 8. The revolution will be backported. •Diazo •Works now
  • 109. 8. The revolution will be backported. •Diazo •Works now •Trivial template cleanup
  • 110. 8. The revolution will be backported. •Diazo •Works now •Trivial template cleanup •Plone 4.2?
  • 111. 8. The revolution will be backported.
  • 112. 8. The revolution will be backported. •Deco
  • 113. 8. The revolution will be backported. •Deco •“Runs” in “Plone 4”
  • 114. 8. The revolution will be backported. •Deco •“Runs” in “Plone 4” •Doesn’t necessarily make sense in that context.
  • 115. 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.
  • 116. 9. Keep moving forward.
  • 117. 9. Keep moving forward.
  • 118. 9. Keep moving forward. •Give a compelling reason to upgrade
  • 119. 9. Keep moving forward. •Give a compelling reason to upgrade •Carrots and sticks
  • 120. 9. Keep moving forward.
  • 121. 9. Keep moving forward. •Continue the move to ZCA
  • 122. 9. Keep moving forward. •Continue the move to ZCA •Tools to Utilities and Views
  • 123. 9. Keep moving forward. •Continue the move to ZCA •Tools to Utilities and Views •Persistent data stored in plone.app registry
  • 124. 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
  • 125. 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
  • 126. 9. Keep moving forward.
  • 127. 9. Keep moving forward. •Continue the move to ZCA •CSS/JS/images to browser resources
  • 128. 10. Shrink the stack.
  • 129. 10. Shrink the stack.
  • 130. 10. Shrink the stack. •Remove unneeded dependencies
  • 131. 10. Shrink the stack. •Remove unneeded dependencies •Zope
  • 132. 10. Shrink the stack. •Remove unneeded dependencies •Zope •CMF
  • 133. 10. Shrink the stack.
  • 134. 10. Shrink the stack. •Plone 4.1/Zope 2.13
  • 135. 10. Shrink the stack. •Plone 4.1/Zope 2.13 •Welcome to the Zope Toolkit
  • 136. 10. Shrink the stack. •Plone 4.1/Zope 2.13 •Welcome to the Zope Toolkit •Less Five.* integration layers
  • 137. 10. Shrink the stack. •Plone 4.1/Zope 2.13 •Welcome to the Zope Toolkit •Less Five.* integration layers •zope.app.* removal
  • 138. 11. Don’t break sh*t.
  • 139. 11. Don’t break sh*t.
  • 140. 11. Don’t break sh*t. •Provide smooth upgrade paths for data
  • 141. 11. Don’t break sh*t. •Provide smooth upgrade paths for data •Provide clear product migration instructions
  • 142. 11. Don’t break sh*t.
  • 143. 11. Don’t break sh*t. •Deprecate, don’t decimate
  • 144. 11. Don’t break sh*t. •Deprecate, don’t decimate •We’re much better at this than others
  • 145. 11. Don’t break sh*t. •Deprecate, don’t decimate •We’re much better at this than others •Stop saying “will go away”
  • 146. 11. Don’t break sh*t.
  • 147. 11. Don’t break sh*t. •For example, Archetypes
  • 148. 11. Don’t break sh*t. •For example, Archetypes •Still around in Plone 5
  • 149. 11. Don’t break sh*t. •For example, Archetypes •Still around in Plone 5 •At a cost
  • 150. 11. Don’t break sh*t. •For example, Archetypes •Still around in Plone 5 •At a cost •Gone in Plone 6
  • 151. 11. Don’t break sh*t. •For example, Archetypes •Still around in Plone 5 •At a cost •Gone in Plone 6 •~5-6 Years
  • 152. 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
  • 153. 12. Install everywhere.
  • 154. 12. Install everywhere.
  • 155. 12. Install everywhere. •Debian/Ubuntu, Redhat packages in the works
  • 156. 12. Install everywhere. •Debian/Ubuntu, Redhat packages in the works •VMWare images
  • 157. 12. Install everywhere. •Debian/Ubuntu, Redhat packages in the works •VMWare images •EC2
  • 158. 12. Install everywhere.
  • 159. 12. Install everywhere. •CPanel
  • 160. 12. Install everywhere. •CPanel •Relstorage + WSGI
  • 161. 12. Install everywhere. •CPanel •Relstorage + WSGI •Within the year
  • 162. 12. Install everywhere.
  • 163. 12. Install everywhere. •CPanel
  • 164. 12. Install everywhere. •CPanel •Welcome to $20 hosting
  • 165. 12. Install everywhere. •CPanel •Welcome to $20 hosting •Easy-to-get = easy-to-evaluate
  • 166. 12. Install everywhere. •CPanel •Welcome to $20 hosting •Easy-to-get = easy-to-evaluate •Equal footing with Joomla, Drupal
  • 167. 12. Install everywhere. •CPanel •Welcome to $20 hosting •Easy-to-get = easy-to-evaluate •Equal footing with Joomla, Drupal •Kick ass
  • 168. 13. Distributions will be important.
  • 169. 13. Distributions will be important.
  • 170. 13. Distributions will be important. •Provide one-click sites for specific use- cases.
  • 171. 13. Distributions will be important. •Provide one-click sites for specific use- cases. •Education
  • 172. 13. Distributions will be important. •Provide one-click sites for specific use- cases. •Education •NGO
  • 173. 13. Distributions will be important. •Provide one-click sites for specific use- cases. •Education •NGO •Intranet
  • 174. 13. Distributions will be important. •Provide one-click sites for specific use- cases. •Education •NGO •Intranet •Social
  • 175. 13. Distributions will be important.
  • 176. 13. Distributions will be important. •Not just add-ons
  • 177. 13. Distributions will be important. •Not just add-ons •Clear set of policies for integration
  • 178. 13. Distributions will be important.
  • 179. 13. Distributions will be important. •Plone 4.1 makes it easier
  • 180. 13. Distributions will be important. •Plone 4.1 makes it easier •Package to include new default add-ons
  • 181. 13. Distributions will be important. •Plone 4.1 makes it easier •Package to include new default add-ons •Exclude existing ones
  • 182. 13. Distributions will be important.
  • 183. 13. Distributions will be important. •Go see my boss
  • 184. 13. Distributions will be important. •Go see my boss •Education distribution in the works now.
  • 185. Sidebar!
  • 186. Sidebar! •Stop using “Plone4*” name
  • 187. Sidebar! •Stop using “Plone4*” name •Plone4Artists
  • 188. Sidebar! •Stop using “Plone4*” name •Plone4Artists •Plone4Universities
  • 189. Sidebar! •Stop using “Plone4*” name •Plone4Artists •Plone4Universities •You’ll feel silly when Plone 5 comes out.
  • 190. 14. Quality. Quality. Quality.
  • 191. 14. Quality. Quality. Quality •Improve quality control at all stages of the development process
  • 192. 14. Quality. Quality. Quality
  • 193. 14. Quality. Quality. Quality •PLIP Process
  • 194. 14. Quality. Quality. Quality •PLIP Process •UI Team
  • 195. 14. Quality. Quality. Quality •PLIP Process •UI Team •Documentation
  • 196. 14. Quality. Quality. Quality
  • 197. 14. Quality. Quality. Quality •Testing
  • 198. 14. Quality. Quality. Quality •Testing •Continuous integration testing
  • 199. 14. Quality. Quality. Quality •Testing •Continuous integration testing •As soon as it’s changed, it’s checked
  • 200. 14. Quality. Quality. Quality •Testing •Continuous integration testing •As soon as it’s changed, it’s checked •Catch regressions as they happen
  • 201. 14. Quality. Quality. Quality •Testing •Continuous integration testing •As soon as it’s changed, it’s checked •Catch regressions as they happen •Selenium
  • 202. 14. Quality. Quality. Quality
  • 203. 14. Quality. Quality. Quality •Testing
  • 204. 14. Quality. Quality. Quality •Testing •Load testing
  • 205. 14. Quality. Quality. Quality •Testing •Load testing •Plone 4 is fast
  • 206. 14. Quality. Quality. Quality •Testing •Load testing •Plone 4 is fast •We want to keep it that way
  • 207. 14. Quality. Quality. Quality
  • 208. 14. Quality. Quality. Quality •QA Team
  • 209. 14. Quality. Quality. Quality •QA Team •Test releases before they go public
  • 210. 14. Quality. Quality. Quality •QA Team •Test releases before they go public •“soft-release”
  • 211. 14. Quality. Quality. Quality •QA Team •Test releases before they go public •“soft-release” •Catch regressions before hurt users
  • 212. 14. Quality. Quality. Quality
  • 213. 14. Quality. Quality. Quality •QA Team
  • 214. 14. Quality. Quality. Quality •QA Team •qa-team@lists.plone.org
  • 215. 14. Quality. Quality. Quality •QA Team •qa-team@lists.plone.org •Open session on Friday
  • 216. 14. Quality. Quality. Quality •QA Team •qa-team@lists.plone.org •Open session on Friday •QA sprint on Saturday
  • 217. 14. Quality. Quality. Quality
  • 218. 14. Quality. Quality. Quality •QA Sprint
  • 219. 14. Quality. Quality. Quality •QA Sprint •QA checklists
  • 220. 14. Quality. Quality. Quality •QA Sprint •QA checklists •Selenium testing
  • 221. 14. Quality. Quality. Quality •QA Sprint •QA checklists •Selenium testing •Performance testing
  • 222. 14. Quality. Quality. Quality •QA Sprint •QA checklists •Selenium testing •Performance testing •Free food!