More Related Content
More from Drupalcon Paris
State Of Drupal September 2009
- 1. State of Drupal DrupalCon Paris 2009 Dries Buytaert http://buytaert.net :: http://twitter.com/dries
- 2. Are we freezing the code?
- 4. Code freeze Release “Developer scream” phase - “Drupal was released too early! We’re missing A, B and C still.” “Patch frenzy” phase - “We should maintain backwards compatibility. This is crazy.” - “Crap, my patch isn’t going to make it in!” - “We failed to do enough of X.That is poor leadership.” - “Wait, we can’t freeze the code like this! Production ready Strong momentum - “Drupal is going to be AWESOME.” Start of development cycle “User scream” phase - “I can’t believe you make me relearn this!” - “You shouldn’t release core until contrib is updated.” - “I can’t believe you’re already working on the next version of Drupal core. I haven’t even upgraded yet.” “Slow motion” phase - “We need more core committers to review patches.” - “Gosh, Drupal development is so broken. If only we used Git!” - “We lost momentum.” time
- 5. time
- 6. time
- 7. Nikolai Kondratiev Economist, 1892-1938 Described fifty to sixty-year long waves of economic prosperity and depression
- 8. Joseph Schumpeter Economist, 1883-1950 Radical innovation drives recurring cycles of “creative destruction”
- 9. Paul Saffo • Overestimating short-term benefits, underestimating long-term benefits of innovations • Cycle of expectation and disappointment is an essential part of the innovation process
- 10. We’re normal!
- 11. Gartner Jackie Fenn and Mark Raskin
- 12. Gartner’s hype cycle Plateau of productivity Negative hype Slope of enlightenment Innovation trigger Through of disillusionment time
- 13. Gartner’s hype cycle Peak of inflated expectations Plateau of productivity Positive hype Slope of enlightenment Innovation trigger time
- 14. Gartner’s hype cycle Peak of inflated expectations Plateau of productivity Negative hype Positive hype Slope of enlightenment Innovation trigger Through of disillusionment time
- 15. Gartner’s hype cycle Peak of inflated expectations Plateau of productivity Negative hype Positive hype Slope of enlightenment Innovation trigger Through of disillusionment time
- 16. Gartner’s hype cycle Peak of inflated expectations Plateau of productivity Negative hype Positive hype Slope of enlightenment Innovation trigger Through of disillusionment time
- 17. Gartner’s hype cycle Swamp of diminishing returns Cliff of obsolescence time
- 18. Code freeze Release “Developer scream” phase - “Drupal was released too early! We’re missing A, B and C still.” “Patch frenzy” phase - “We should maintain backwards compatibility. This is crazy.” - “Crap, my patch isn’t going to make it in!” - “We failed to do enough of X.That is poor leadership.” - “Wait, we can’t freeze the code like this! Production ready Strong momentum - “Drupal is going to be AWESOME.” Start of development cycle “User scream” phase - “I can’t believe you make me relearn this!” - “You shouldn’t release core until contrib is updated.” - “I can’t believe you’re already working on the next version of Drupal core. I haven’t even upgraded yet.” “Slow motion” phase - “We need more core committers to review patches.” - “Gosh, Drupal development is so broken. If only we used Git!” - “We lost momentum.” time
- 19. Are we freezing the code?
- 20. When to freeze the code? Next release: peak of inflated expectations Previous release: plateau of productivity time
- 21. Plateau of productivity for Drupal 6?
- 23. !"##"$%&' !" !#$" %" %#$" &" &#$" '" '#$" )*+"&!!," (" -*."&!!," )/+"&!!," 0/1"&!!," 234"&!!," 563"&!!," 768"&!!9" 0:."&!!9" )/+"&!!9" 0/1"&!!9" 234"&!!9" Source: awstats from drupal.org 563"&!!9" 768"&!!;" ()*+,-'$.'/"&"0&' )/+"&!!;" 0/1"&!!;" 234"&!!;" 563"&!!;" 768"&!!<" 0:."&!!<" )/+"&!!<"
- 24. !"##"$%&' !" #" $!" $#" %!" %#" &!" &#" '()"%!!*" +(,"%!!*" '-)"%!!*" .-/"%!!*" 012"%!!*" 341"%!!*" 546"%!!7" .8,"%!!7" '-)"%!!7" .-/"%!!7" ()*+&' 012"%!!7" Source: awstats from drupal.org 341"%!!7" 546"%!!9" '-)"%!!9" .-/"%!!9" 012"%!!9" 341"%!!9" 546"%!!:" .8,"%!!:" '-)"%!!:"
- 26. We continue to win awards
- 28. Peak of inflated expectations for Drupal 7?
- 30. Support for master/slave replication
- 32. Support for multi-insert queries
- 33. Support for delayed inserts
- 34. A much improved support for PostgreSQL
- 35. SQLite support
- 36. MSSQL and Oracle support are now feasible
- 38. Rate limit login attempts
- 39. Better support for WYSIWYG editors
- 41. Added a dummy install profile
- 44. Added a built-in cron feature
- 45. Added a default administrator role
- 46. Redesigned the password strength checker
- 47. Redesigned the add content type screen
- 48. We have a much improved filter system
- 49. Reduced number of SQL queries
- 50. Stopped writing session for anonymous users
- 52. Added support for HTTP proxies (can improve performance up to 2000x)
- 53. Added 10,000 lines of API documentation
- 54. Added a test framework and embraced test driven development
- 55. Wrote thousands of tests
- 56. Improved time zone support
- 57. Cleaned up many APIs
- 58. Made files first class citizens
- 59. Added support for CDNs
- 60. Removed per user themes
- 61. Removed the throttle module
- 62. Added the code registry
- 63. Removed the code registry
- 69. Made various theme system improvements
- 70. Added support for thumbnails
- 71. Added support for image effects
- 72. Modules can declare RDF namespaces
- 73. Added a Field API in core (CCK in core)
- 74. Node bodies are regular fields now
- 75. Made it possible to add fields to users
- 76. Made it possible to add fields to comments
- 77. Made it possible to add fields to anything
- 78. Turned taxonomy term into fields
- 79. Made the help text area a region with blocks
- 80. Made the mission statement a regular block
- 81. Made the footer a regular block
- 83. Added jQuery UI
- 84. Added better module versioning
- 85. Removed the blog API module from core
- 86. Improved the node access control system
- 88. Peak of inflated expectations for Drupal 7?
- 90. Plateau of productivity for Drupal 6 Peak of inflated expectations for Drupal 7
- 91. Where we are today Next release: peak of inflated expectations Previous release: plateau of productivity time
- 92. We are going to freeze the code!
- 94. Field API is not 100% yet
- 95. Profile module not converted yet
- 96. D7UX is still a work in progress
- 97. Test coverage OK but not stellar
- 98. Performance degraded (my biggest concern)
- 99. SQL queries Drupal 6 Drupal 7 /node 103 49 /node/1 43 56 /user/1 Details: APC enabled, XDebug off Credit: catch
- 100. Performance no caching caching /node -20% -12% /node/1 -55% -12% /user/1 -45% -12% Details: APC enabled, XDebug off Credit: catch
- 103. Development Code freeze Drupal 7.0 release
- 104. Development Code freeze 82 weeks Feb 1, 2008 Unknown Phase one: “DrupalCon Paris” • Still allowed: everything • Ends Monday morning • Make a snapshot of everything that is RTBC • Angie and myself will review and commit those as soon we have time to
- 105. Development Code freeze 82 weeks 5 weeks Feb 1, 2008 Sep 7, 2009 Oct 15, 2009 Unknown Phase two: “code slush” • Time boxed at 5 weeks • Not allowed: • New features or functionality • Still allowed: • Up to 10 carefully selected exceptions for new features • Important API changes for existing features • Usability, accessibility, testing, documentation and performance • October 15th = API freeze (including mark-up freeze and schema freeze)
- 106. Current exceptions 1. Imagefield 2. Field translations 3. Convert profile module to field API 4. Convert taxonomy to field API 5. Overlays 6. Edit anywhere 7. Shortcuts 8. Dashboard 9. Plugin manager 10. RDF/RFDa
- 107. Development Code freeze 82 weeks 5 weeks Feb 1, 2008 Sep 7, 2009 Oct 15, 2009 Unknown Phase two: “code slush” • Time boxed at 5 weeks • Not allowed: • New features or functionality • Still allowed: • Up to 10 carefully selected exceptions for new features • Important API changes for existing features • Usability, accessibility, testing, documentation and performance • October 15th = API freeze (including mark-up freeze and schema freeze)
- 108. Development Code freeze 82 weeks 5 weeks 4 weeks ? weeks Feb 1, 2008 Sep 7, 2009 Oct 15, 2009 Nov 15, 2009 Unknown Phase three: “strictly polish” • Time boxed at 4 weeks • Not allowed: • New features, API changes, mark-up changes • Allowed: • Usability, accessibility, testing, documentation and performance • November 15th = string freeze and UI freeze • Releases: first alpha (or potentially beta)
- 109. Development Code freeze 82 weeks 5 weeks 4 weeks ? weeks Feb 1, 2008 Sep 7, 2009 Oct 15, 2009 Nov 15, 2009 Unknown Phase four: “bugs and release blockers only” • Length: until all “release blockers” are fixed • Allowed • Release blockers • Bug fixes • Testing • Releases: betas and RCs
- 110. Development Code freeze 82 weeks 5 6 weeks 4 weeks ? weeks Feb 1, 2008 Sep 7, 2009 Oct 15, 2009 Nov 15, 2009 Unknown Features High-impact exceptions API freeze API changes existing features Upgrade path Performance Usability String freeze Accessibility UI freeze Documentation String changes and UI changes Bug fixes SimpleTests
- 111. Beyond Drupal 7
- 112. Joseph Schumpeter Economist, 1883-1950 Radical innovation drives recurring cycles of “creative destruction”
- 113. Everett Rogers 1931-2004, Diffusion of innovations Showed that innovation adoption does not happen in a straight line, but that it follows a predictable S-curve
- 114. time
- 115. time
- 116. Everett Rogers’ S-curve reach time
- 117. Repeating in many different industries
- 118. William Hyde Wollaston 1828 Innovation Credit: Simon Wardley
- 119. Hippolyte Pixii 1808–1835 Innovation Bespoke Credit: Simon Wardley
- 120. Gramme-dynamo Innovation Bespoke Products Credit: Simon Wardley
- 121. Electricity grid Innovation Bespoke Products Commoditization Credit: Simon Wardley
- 122. Electricity grid Innovation Bespoke Products Service Credit: Simon Wardley
- 123. Electricity has transformed from an innovation to a service Electricity grid William Hyde Wollaston 1828 Innovation Service Credit: Simon Wardley
- 124. Z3, 1941 Innovation Credit: Simon Wardley
- 125. Leo, 1946 Innovation Bespoke Credit: Simon Wardley
- 126. IBM 650 Innovation Bespoke Products Credit: Simon Wardley
- 127. Cloud computing Innovation Bespoke Products Commoditization Credit: Simon Wardley
- 128. Cloud computing Innovation Bespoke Products Service Credit: Simon Wardley
- 129. reach Service Products Bespoke Innovation time Credit: Simon Wardley
- 130. reach Service Products downloadable CRM product Bespoke database Innovation time Credit: Simon Wardley
- 131. reach Acquia Gardens Buzzr Service Open Atrium OpenPublish DrupalEd Acquia Drupal Products PressFlow ... Bespoke Innovation time
- 133. Get break out growth instead of linear growth
- 135. Distributions is one way
- 136. Install profiles as modules + plugin manager
- 137. “Features” is one way
- 138. Richness + reach = success Richness The place to be Drupal Plone Joomla! ExpressionEngine Wordpress Reach
- 139. Richness + reach = success Richness The place to be Frameworks Products Services Reach
- 141. Frameworks create bespoke systems
- 145. reach Service Market or user Products driven development Bespoke Innovation driven Innovation development time
- 146. Denial?
- 147. Drupal 7 usability
- 148. “If you’re not afraid, you’re not doing the right thing.”
- 149. Pain
- 150. Great
- 151. Growing up
- 152. We can’t roll back time. We have no choice to grow up.
- 153. We’ll reach out to new people, and have to learn how to interact with them
- 154. Recap • Learned a pattern on how we innovate -- and we’re normal • Innovation is on track, feel great about Drupal 6 and Drupal 7 • Learned what our evolution might be
- 155. Only good platform is an open platform
- 156. Only good community is a fair and balanced community
- 157. DrupalCon after 4 years ... 25 Drupal developers DrupalCon Belgium Antwerp, 2005
- 158. DrupalCon after 4 years ... 1400 Drupal developers DrupalCon DC Washington, 2009
- 160. Being significant
- 161. How do we go where we aren’t today?
- 162. Richness + reach = success Richness The place to be Drupal Reach
- 163. Richness, we should be less worried about
- 164. Reach is our biggest challenge and opportunity