• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content

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.

Like this presentation? Why not share!

Plone Conference 2010 – Where we go from here

on

  • 1,465 views

14 guidelines to follow as Plone moves forward.

14 guidelines to follow as Plone moves forward.

Statistics

Views

Total Views
1,465
Views on SlideShare
1,465
Embed Views
0

Actions

Likes
1
Downloads
18
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • <br />
  • <br />
  • <br />
  • <br />
  • As a developer community, we need to be better at communicating our architectural goals <br /> What are our plans and why do we want to do this <br />
  • As a developer community, we need to be better at communicating our architectural goals <br /> What are our plans and why do we want to do this <br />
  • <br />
  • <br />
  • Written 3 years ago. <br />
  • <br />
  • <br />
  • Your average 14 year old kid is much more likely to pick up PHP <br />
  • Your average 14 year old kid is much more likely to pick up PHP <br />
  • Your average 14 year old kid is much more likely to pick up PHP <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • Our user interface is 10x better than anyone else out there <br /> <br /> <br />
  • Our user interface is 10x better than anyone else out there <br /> <br /> <br />
  • Our user interface is 10x better than anyone else out there <br /> <br /> <br />
  • Our user interface is 10x better than anyone else out there <br /> <br /> <br />
  • Our user interface is 10x better than anyone else out there <br /> <br /> <br />
  • I&#x2019;m pleased to announce that Plone now has an official UI team. <br /> <br /> <br />
  • I&#x2019;m pleased to announce that Plone now has an official UI team. <br /> <br /> <br />
  • Generate UI "style guide" best practices documentation <br />
  • Generate UI "style guide" best practices documentation <br />
  • Generate UI "style guide" best practices documentation <br />
  • Generate UI "style guide" best practices documentation <br />
  • Generate UI "style guide" best practices documentation <br />
  • <br />
  • Hard to describe plone because the answer largely depends on what each user is using it for. <br /> <br /> Admit that Plone isn&#x2019;t really a good fit for blogs, 3 page sites. <br />
  • Hard to describe plone because the answer largely depends on what each user is using it for. <br /> <br /> Admit that Plone isn&#x2019;t really a good fit for blogs, 3 page sites. <br />
  • Hard to describe plone because the answer largely depends on what each user is using it for. <br /> <br /> Admit that Plone isn&#x2019;t really a good fit for blogs, 3 page sites. <br />
  • Hard to describe plone because the answer largely depends on what each user is using it for. <br /> <br /> Admit that Plone isn&#x2019;t really a good fit for blogs, 3 page sites. <br />
  • <br />
  • Determine the first steps with Plone make those easier <br /> <br />
  • Determine the first steps with Plone make those easier <br /> <br />
  • Determine the first steps with Plone make those easier <br /> <br />
  • Determine the first steps with Plone make those easier <br /> <br />
  • Determine the first steps with Plone make those easier <br /> <br />
  • Determine the first steps with Plone make those easier <br /> <br />
  • Determine the first steps with Plone make those easier <br /> <br />
  • Determine the first steps with Plone make those easier <br /> <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • And we can already export a lot of things right now thanks to GenericSetup. <br />
  • And we can already export a lot of things right now thanks to GenericSetup. <br />
  • And we can already export a lot of things right now thanks to GenericSetup. <br />
  • And we can already export a lot of things right now thanks to GenericSetup. <br />
  • And we can already export a lot of things right now thanks to GenericSetup. <br />
  • And we can already export a lot of things right now thanks to GenericSetup. <br />
  • So what does that mean? <br /> <br /> And I&#x2019;ll go out on a limb now and say that we&#x2019;re going to start seeing that as early as Plone 4.2. <br />
  • So what does that mean? <br /> <br /> And I&#x2019;ll go out on a limb now and say that we&#x2019;re going to start seeing that as early as Plone 4.2. <br />
  • So what does that mean? <br /> <br /> And I&#x2019;ll go out on a limb now and say that we&#x2019;re going to start seeing that as early as Plone 4.2. <br />
  • <br />
  • KSS didn&#x2019;t get the adoption we&#x2019;d hoped for. jQuery has proven to be a better long-term solution. <br /> We&#x2019;ll begin to move core Plone features away from using KSS in Plone 4.1. Should give us a 15%-50% speedup. <br /> Expect it to be gone in Plone 5. <br />
  • KSS didn&#x2019;t get the adoption we&#x2019;d hoped for. jQuery has proven to be a better long-term solution. <br /> We&#x2019;ll begin to move core Plone features away from using KSS in Plone 4.1. Should give us a 15%-50% speedup. <br /> Expect it to be gone in Plone 5. <br />
  • KSS didn&#x2019;t get the adoption we&#x2019;d hoped for. jQuery has proven to be a better long-term solution. <br /> We&#x2019;ll begin to move core Plone features away from using KSS in Plone 4.1. Should give us a 15%-50% speedup. <br /> Expect it to be gone in Plone 5. <br />
  • KSS didn&#x2019;t get the adoption we&#x2019;d hoped for. jQuery has proven to be a better long-term solution. <br /> We&#x2019;ll begin to move core Plone features away from using KSS in Plone 4.1. Should give us a 15%-50% speedup. <br /> Expect it to be gone in Plone 5. <br />
  • <br />
  • We won&apos;t see many of the "revolutionary" things talked about during the keynote as part of the plone core until Plone 5. <br /> <br /> <br />
  • We won&apos;t see many of the "revolutionary" things talked about during the keynote as part of the plone core until Plone 5. <br /> <br /> <br />
  • Practical considerations mean that we can&#x2019;t do many of these by default in Plone 4 right now. <br /> <br /> But they can be integrated, with varying degrees of effort. <br />
  • Practical considerations mean that we can&#x2019;t do many of these by default in Plone 4 right now. <br /> <br /> But they can be integrated, with varying degrees of effort. <br />
  • Practical considerations mean that we can&#x2019;t do many of these by default in Plone 4 right now. <br /> <br /> But they can be integrated, with varying degrees of effort. <br />
  • Alan talked about Chameleon earlier. <br /> Chameleon can make your templates render substantially faster. It&#x2019;s a quick way to optimize your site. <br /> But you need to make sure your templates all validate as xml. <br /> Enfold has put a lot of work into this over the past month. <br /> <br />
  • Alan talked about Chameleon earlier. <br /> Chameleon can make your templates render substantially faster. It&#x2019;s a quick way to optimize your site. <br /> But you need to make sure your templates all validate as xml. <br /> Enfold has put a lot of work into this over the past month. <br /> <br />
  • Alan talked about Chameleon earlier. <br /> Chameleon can make your templates render substantially faster. It&#x2019;s a quick way to optimize your site. <br /> But you need to make sure your templates all validate as xml. <br /> Enfold has put a lot of work into this over the past month. <br /> <br />
  • Alan talked about Chameleon earlier. <br /> Chameleon can make your templates render substantially faster. It&#x2019;s a quick way to optimize your site. <br /> But you need to make sure your templates all validate as xml. <br /> Enfold has put a lot of work into this over the past month. <br /> <br />
  • Works in Plone 4 now. <br /> But there are a number of issues that prevent it from being fully integrated into the way Plone currently works. Things like relationships don&#x2019;t work well. <br /> <br /> Plone 4.1 fixes some of those issues and the remainder of the 4.x series will include even more integration tweaks. <br />
  • Works in Plone 4 now. <br /> But there are a number of issues that prevent it from being fully integrated into the way Plone currently works. Things like relationships don&#x2019;t work well. <br /> <br /> Plone 4.1 fixes some of those issues and the remainder of the 4.x series will include even more integration tweaks. <br />
  • Works in Plone 4 now. <br /> But there are a number of issues that prevent it from being fully integrated into the way Plone currently works. Things like relationships don&#x2019;t work well. <br /> <br /> Plone 4.1 fixes some of those issues and the remainder of the 4.x series will include even more integration tweaks. <br />
  • Works in Plone 4 now. <br /> But there are a number of issues that prevent it from being fully integrated into the way Plone currently works. Things like relationships don&#x2019;t work well. <br /> <br /> Plone 4.1 fixes some of those issues and the remainder of the 4.x series will include even more integration tweaks. <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • If you look at the deco brewery buildout that recently came out, you can actually run Deco in Plone 4. <br /> <br /> Deco assumes a lot of changes <br />
  • If you look at the deco brewery buildout that recently came out, you can actually run Deco in Plone 4. <br /> <br /> Deco assumes a lot of changes <br />
  • If you look at the deco brewery buildout that recently came out, you can actually run Deco in Plone 4. <br /> <br /> Deco assumes a lot of changes <br />
  • If you look at the deco brewery buildout that recently came out, you can actually run Deco in Plone 4. <br /> <br /> Deco assumes a lot of changes <br />
  • <br />
  • While the Framework Team thinks it&apos;s important to&#xA0;do things like factor custom output transformations out of the editors, we realize that it&apos;s things like a new collections UI that are going to prompt people to stay current. <br /> <br /> If we can keep our users following the front-end carrot, the stick needed to handle back-end upgrades won&apos;t have to be so big. <br />
  • While the Framework Team thinks it&apos;s important to&#xA0;do things like factor custom output transformations out of the editors, we realize that it&apos;s things like a new collections UI that are going to prompt people to stay current. <br /> <br /> If we can keep our users following the front-end carrot, the stick needed to handle back-end upgrades won&apos;t have to be so big. <br />
  • We need to finish what we started in Plone 3. <br />
  • We need to finish what we started in Plone 3. <br />
  • We need to finish what we started in Plone 3. <br />
  • We need to finish what we started in Plone 3. <br />
  • We need to finish what we started in Plone 3. <br />
  • <br />
  • <br />
  • Plone 4 has already removed a number of unneeded dependencies on CMF and Zope packages. As we move forward, we can remove even more. <br />
  • Plone 4 has already removed a number of unneeded dependencies on CMF and Zope packages. As we move forward, we can remove even more. <br />
  • Plone 4 has already removed a number of unneeded dependencies on CMF and Zope packages. As we move forward, we can remove even more. <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • Drupal, Sharepoint have gotten this horribly wrong. <br />
  • Drupal, Sharepoint have gotten this horribly wrong. <br />
  • Drupal, Sharepoint have gotten this horribly wrong. <br />
  • It&#x2019;ll work, but you won&#x2019;t get things like Deco layouts. <br />
  • It&#x2019;ll work, but you won&#x2019;t get things like Deco layouts. <br />
  • It&#x2019;ll work, but you won&#x2019;t get things like Deco layouts. <br />
  • It&#x2019;ll work, but you won&#x2019;t get things like Deco layouts. <br />
  • It&#x2019;ll work, but you won&#x2019;t get things like Deco layouts. <br />
  • It&#x2019;ll work, but you won&#x2019;t get things like Deco layouts. <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • 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 <br />
  • 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 <br />
  • 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 <br />
  • So that anyone buying a cheap hosting package now has the option of installing and evaluating Plone. <br /> That puts us on equal footing with other open source CMSs like Joomla and Drupal <br /> 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. <br />
  • So that anyone buying a cheap hosting package now has the option of installing and evaluating Plone. <br /> That puts us on equal footing with other open source CMSs like Joomla and Drupal <br /> 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. <br />
  • So that anyone buying a cheap hosting package now has the option of installing and evaluating Plone. <br /> That puts us on equal footing with other open source CMSs like Joomla and Drupal <br /> 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. <br />
  • So that anyone buying a cheap hosting package now has the option of installing and evaluating Plone. <br /> That puts us on equal footing with other open source CMSs like Joomla and Drupal <br /> 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. <br />
  • So that anyone buying a cheap hosting package now has the option of installing and evaluating Plone. <br /> That puts us on equal footing with other open source CMSs like Joomla and Drupal <br /> 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. <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • Plone 4.1 will make it much easier to <br />
  • Plone 4.1 will make it much easier to <br />
  • Plone 4.1 will make it much easier to <br />
  • If you go to see Mike Halm&#x2019;s talk this afternoon, he&#x2019;ll be discussing our efforts to create a distribution focused on sites for educational institutions. <br />
  • If you go to see Mike Halm&#x2019;s talk this afternoon, he&#x2019;ll be discussing our efforts to create a distribution focused on sites for educational institutions. <br />
  • Plone4Artists is a company making themes for the latest Plone, right? <br /> Plone4Universities provide training? <br /> <br /> And when Plone 5 comes out, everyone will wonder when you&#x2019;re going to upgrade. <br />
  • Plone4Artists is a company making themes for the latest Plone, right? <br /> Plone4Universities provide training? <br /> <br /> And when Plone 5 comes out, everyone will wonder when you&#x2019;re going to upgrade. <br />
  • Plone4Artists is a company making themes for the latest Plone, right? <br /> Plone4Universities provide training? <br /> <br /> And when Plone 5 comes out, everyone will wonder when you&#x2019;re going to upgrade. <br />
  • Plone4Artists is a company making themes for the latest Plone, right? <br /> Plone4Universities provide training? <br /> <br /> And when Plone 5 comes out, everyone will wonder when you&#x2019;re going to upgrade. <br />
  • <br />
  • <br />
  • UI Team will assist the framework team in evaluating PLIPs for consistency, usability <br /> Documentation required up front, gives the Docs Team some lead time on getting our documentation up to date with changes/new features <br />
  • UI Team will assist the framework team in evaluating PLIPs for consistency, usability <br /> Documentation required up front, gives the Docs Team some lead time on getting our documentation up to date with changes/new features <br />
  • UI Team will assist the framework team in evaluating PLIPs for consistency, usability <br /> Documentation required up front, gives the Docs Team some lead time on getting our documentation up to date with changes/new features <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • Enfold is providing us with nightly load testing. <br />
  • Enfold is providing us with nightly load testing. <br />
  • Enfold is providing us with nightly load testing. <br />
  • Enfold is providing us with nightly load testing. <br />
  • At last year&#x2019;s conference, we began the discussion of creating an official QA team. It&#x2019;s been slow going so far. <br /> <br />
  • At last year&#x2019;s conference, we began the discussion of creating an official QA team. It&#x2019;s been slow going so far. <br /> <br />
  • At last year&#x2019;s conference, we began the discussion of creating an official QA team. It&#x2019;s been slow going so far. <br /> <br />
  • At last year&#x2019;s conference, we began the discussion of creating an official QA team. It&#x2019;s been slow going so far. <br /> <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />

Plone Conference 2010 – Where we go from here Plone Conference 2010 – Where we go from here Presentation Transcript

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