Uploaded byDries Buytaert
State of Drupal keynote, DrupalCon Chicago
Dries Buytaert gave a keynote speech about Drupal 7 and the development process for Drupal 8. He discussed highlights of Drupal 7 including fields and overlay, and priorities for Drupal 8 such as fewer critical bugs, improved performance, and accessibility. Buytaert also emphasized strategic directions for Drupal including multi-device publishing, interoperability, and providing a delightful user experience.
![[HKDUG] #20151017 - BarCamp 2015 - Drupal 8 is Coming! Are You Ready?](https://cdn.slidesharecdn.com/ss_thumbnails/hkdug20151017-barcamp2015-drupal8iscomingareyouready-151017054334-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
State of Drupal keynote, DrupalCon Chicago
- 1. Keynote Speech“”What isDrupal?Dries BuytaertDrupal Project Lead
- 2. Agenda Drupal 7highlights Drupal 8 processDrupal 8 priorities
- 4. Actual code freezeFeb2008Jan 2011Drupal 7D7 launchOriginal code freezeOriginal launch dateCriticalbugs
- 5. Drupal 7Actual codefreezeD7 launchCriticalbugsFieldsFeb 2008Jan 2011OverlayDatabaseRegistry
- 6. Drupal 7 communicationsLeadCo-maintainerDrupaldevelopersiiiiiiiiiiiiiiiiiiiiiii
- 7. Drupal 7 communicationsCo-maintainerFeb2008Jan 2011
- 8.
- 9. 30 contributors areresponsible for50% of the Drupal 7 core patchesNumber of patches450400350300250200150100500Number of people1326394311125156187218249280342373404435466497528559590621652683714950
- 10.
- 11. 30 top contributorsNathanHaug“quicksketch”Architect,LullabotKarolyNegyesi“chx”Developer,Examiner.comAlex Bronstein,“effulgentsia”Developer,AcquiaMoshe Weitzman“moshe”Developer,Cyrve,LLCBram Goffings“aspilicious”Developer,StudentYves Chedemois“yched”Developer,FreelanceDaniel Kudwien“sun”Guardian,unleashed mindPeter Wolanin“pwolanin”Developer,AcquiaGáborHojtsy“GáborHojtsy”Developer,AcquiaJeff Burnz“JeffBurnz”Themer,Adaptive themesFrancescoPlacella“plach”Developer,PSENGORoy Scholten“yoroy”UX Design,yoroyNathaniel Catchpole“catch”Developer,Tag1 consultingRob Loach“RobLoach”Developer,AcquiaJennifer Hodgdon“jhodgdon”Developer,Popular ProductivityWare
- 12. 30 top contributorsNathanHaug“quicksketch”Architect,LullabotKarolyNegyesi“chx”Developer,Examiner.comAlex Bronstein,“effulgentsia”Developer,AcquiaMoshe Weitzman“moshe”Developer,Cyrve,LLCBram Goffings“aspilicious”Developer,StudentLarry Garfield“crell”Developer,Palantir.netSaschaGrossenbacher“berdir”Developer,MD SystemIvo Van Geertruyen“mr.baileys”Developer,ONE AgencyDave Reid“DaveReid”Developer, Palantir.netAndreyPostnikov“andypost”Developer,FreelanceYves Chedemois“yched”Developer,FreelanceDaniel Kudwien“sun”Guardian,unleashed mindPeter Wolanin“pwolanin”Developer,AcquiaGáborHojtsy“GáborHojtsy”Developer,AcquiaJeff Burnz“JeffBurnz”Themer,Adaptive themesDerek Wright“dww”Developer,3281d ConsultingJohn AlbinWilkins“JohnAlbin”Themer,Palantir.netChristian Schmidt“c960657”Architect,Berlingske MediaJimmy Berry“boombatower “Developer,BoombatowerStéphaneCorlosquet“scor”developer,MA HospitalAngela Byron“webchick”Cat Herder,LullabotFrancescoPlacella“plach”Developer,PSENGORoy Scholten“yoroy”UX Design,yoroyNathaniel Catchpole“catch”Developer,Tag1 consultingRob Loach“RobLoach”Developer,AcquiaJennifer Hodgdon“jhodgdon”Developer,Popular ProductivityWareDamien TournoudDamZArchitect,CommerceGuysBojhan Somers “bojhan”Designer,FreelanceDavid Rothstein“David_Rothstein“Engineer,AcquiaCasey Notane“casey”Architect,Freelance
- 13.
- 14. Global listening!2010160,000 milestravelled43 trips2 homes
- 15. What did wedo well?Test driven developmentAccessibility teamUpdated dev docDevsnapshotsUsability team
- 16. What can wedo better?Performance firstEmpowermentRelease cycle predictabilityToo many critical bugsHigh bandwidth communicationBetter priorities
- 18. Drupal 8<15 Criticalbugs8th Mar 2011PerformanceAccessibilityInitiative 1UsabilityInitiative 2DocumentationInitiative 3TestingInitiative 4No critical bugs
- 19. Drupal 8?LeadCo-maintainerDrupal developersInitiative1Initiative 2Initiative 3Initiative 4
- 20. What makes agood initiative owner?Good organizerGood communicatorTeam builderGood architect
- 22. The future isbeing anywhere at any time, reaching any information or people needed at any device.“”
- 23. The future isbeing anywhere at any time, reaching any information or people needed at any device.“”
- 24.
- 25. Shipments by formfactor, millions700600Smartphones500400Tablets300Netbooks200NotebooksDevice shipments 1995-2010100Desktops01995199619971998199920012003200420052008200920102006200720002002Source: IDC, Gartner, Morgan Stanley Research
- 26. Device shipments 1995-2010Ifwe were to start Drupal from scratch, we would design for mobile first and desktop experience second700600Smartphones500 Mobile400Tablets300Netbooks200Notebooks100DesktopsFixed020012010Source: IDC, Gartner, Morgan Stanley Research
- 27. The future isbeing anywhere at any time, reaching any information or people needed at any deviceThe future is being anywhere at any time, reaching or people needed at any device“any information”
- 28.
- 29. The future isbeing anywhere at any time, reaching any information or people needed at any deviceThe future is being anywhere at any time, reaching any information or needed at any device“people”
- 30. Individual experienceWeb &socialConsumer appsEnterprise
- 31. So what doesthat mean for Drupal?
- 32. Drupal 8Flash front-endHTMLHTML5Nativeapplication built on web servicesXML
- 33. Strategic Directions OrganizationsIndividuals1.Multi-devicepublishing
- 34. Strategic initiativesOrganizationsThemersEnd-usersIndividualsIT managers/ operationsDevelopers
- 35. Strategic initiativesOrganizationsThemersEnd-usersMark-up freecoreHTML5IndividualsCSS3ContextsWeb servicesIT managers / operationsDevelopers
- 36.
- 37. Strategic Directions OrganizationsIndividuals1. Multi-devicepublishing2. Interoperability
- 38. Strategic initiativesOrganizationsMark-up freecoreContent creatorsThemersHTML5IndividualsCSS3ContextsClean APIsWeb servicesStandards-based connectorsIT managers / operationsDevelopers
- 39. Simplicityand power areincreasing
- 40. Strategic directions OrganizationsIndividuals1. Multi-devicepublishing2. Interoperability3. Delightful experience
- 41. Strategic initiativesMark-up freecoreContent creatorsThemersHTML5IndividualsCSS3AccessibilityUsabilityPerformanceContextsClean APIsWeb servicesStandards-based connectorsIT managers / operationsDevelopers
- 45. Interviewed 20 largeDrupal users
- 46. Interviewed 20 largeDrupal usersConfiguration managementContent staging
- 47. Strategic directions 1. Multi-devicepublishing2. Interoperability3. Delightful experienceConfiguration management4. Configuration managementContent staging5. Content staging
- 48. Strategic initiativesMark-up freecoreContent creatorsContent stagingThemersHTML5CSS3AccessibilityUsabilityContextsPerformanceClean APIsUUIDsWeb servicesExportablesConfiguration managementIT managers / operationsStandards-based connectorsDevelopers
- 49. Strategic directions 1. Multi-devicepublishing2. Interoperability3. Delightful experience4. Configuration management5. Content staging
- 50. But be careful,the future is more than just “features”
- 51. “The battle ofdevices has now become a war of ecosystems. Our competitors aren’t taking our market share with devices; they are taking our market sharewith an entire ecosystem.”Stephen Elop, CEO Nokia
- 52.
- 53.
- 54.
- 55. Drupal 8<15 CriticalbugsWeb servicesUUID’sConfiguration managementHTML 56th Jan 2011PerformanceAccessibilityWeb ServicesUsabilityHTML 5DocumentationUUIDsTestingConfigMgtNo critical bugs
- 56. What can wedo better?Performance firstEmpowermentRelease cycle predictabilityToo many critical bugsHigh bandwidth communicationBetter priorities
- 57.
Editor's Notes
- #2 Nervous
- #8 Signed up for a year or 18 months, and I took us 3 yearsStill remember her first commit – very careful and diligentCould not be happier
- #21 Before we talk about what these initiatives are …Asked on my blog last week ‘What is Drupal?’250 respones, pulled 30 out – share that with you
- #23 Spoken by Dries: it is not hard to see this is the future we’re heading towards. But what does this really mean? Let’s try to break it up and map it back to Drupal .
- #24 Spoken by Dries: it is not hard to see this is the future we’re heading towards. But what does this really mean? Let’s try to break it up and map it back to Drupal .
- #25 Spoken by Dries: in the future will want to access information from any device. This means two things ...
- #28 Spoken by Dries: information lives in different repositories in the cloud ...
- #29 Spoken by Dries: information lives in different repositories in the cloud ...
- #30 Spoken by Dries: this is something that Drupal needs to get better at. Drupal has always been great at social. However, the social features of today (i.e. Twitter, facebook) are no longer the social features of 10 years ago (forums, blogs)
- #31 The individual is at the center. Accessing information from where he/she wants.This is part of a bigger trend commonly referring to at the “consumerization of IT”Web-enabled devices and cloud-based services accelerate this trend
- #33 First thing we need to do, is evolve Drupal needs to be relevant in a device independent world
- #34 The needs of consumers for reliability, security, cost effectiveness, interoperability and multi-device publishing will be similar to the needs that most enterprise have.
- #37 Second, it also means that Drupal needs to be able to integrate many data sourcesThis will map on Drupal 8 initiative #2: Better web services support / interoperability
- #38 The needs of consumers for reliability, security, cost effectiveness, interoperability and multi-device publishing will be similar to the needs that most enterprise have.
- #39 See LSD slides
- #41 The needs of consumers for reliability, security, cost effectiveness, interoperability and multi-device publishing will be similar to the needs that most enterprise have.
- #42 This is the platform of the futureThis is what Drupal has to becomeIt is not about being your your typical developer platform like Rails or phpCake
- #43 Grammy.com on Drupal for second year in rowCommentary Dries: Drupal winning because it has scalability
- #44 House of Representatives standardized on Drupal as a platformCommentary Dries: Drupal winning because it has scalability
- #48 The needs of consumers for reliability, security, cost effectiveness, interoperability and multi-device publishing will be similar to the needs that most enterprise have.
- #49 See LSD slides
- #50 The needs of consumers for reliability, security, cost effectiveness, interoperability and multi-device publishing will be similar to the needs that most enterprise have.
- #53 People pick the most capable tool for the job. However, when there are multiple tools that are equally capable, the value of the ecosystem becomes the key differentiatorWe need to get better at what we doImprove as individuals and our businesses; tell story of Lonely Planet (without disclosing their name)Improve our shared tools; need to continue to make drupal.org better and invest in our tools too
- #54 Need to get better at what we do: - Being more professional; Lonely Planet - Market driven; always surprised how few people know more than 2 things about the competition - Marketing; pull vs push
- #58 Q&A