State of Drupal Barcelona Dries Buytaert

Transcription

1 State of Drupal Barcelona 2007 Dries Buytaert

2 Survey running for 30+ days, collected more than 1000 responses

3 We re really good at

4 We re really good at 1. HTML

5 We re really good at 1. HTML 2. Administering Drupal

6 We re really good at 1. HTML 2. Administering Drupal 3. CSS

7 We re really good at 1. HTML 2. Administering Drupal 3. CSS 4. PHP

8 We re really good at 1. HTML 2. Administering Drupal 3. CSS 4. PHP 5. System administration

9 We re really good at 1. HTML 2. Administering Drupal 3. CSS 4. PHP 5. System administration 6. SQL

10 We re really good at 1. HTML 2. Administering Drupal 3. CSS 4. PHP 5. System administration 6. SQL 7. Module development

11 We re really good at 1. HTML 2. Administering Drupal 3. CSS 4. PHP 5. System administration 6. SQL 7. Module development 8. Theme development

12 We suck at

13 We suck at 1. Flash/Flex

14 We suck at 1. Flash/Flex 2. Module development

15 We suck at 1. Flash/Flex 2. Module development 3. Performance, scalability, HA

16 We suck at 1. Flash/Flex 2. Module development 3. Performance, scalability, HA 4. Marketing/evangelizing

17 We suck at 1. Flash/Flex 2. Module development 3. Performance, scalability, HA 4. Marketing/evangelizing 5. Javascript/JQuery

18 We suck at 1. Flash/Flex 2. Module development 3. Performance, scalability, HA 4. Marketing/evangelizing 5. Javascript/JQuery 6. Theme development

19 We suck at 1. Flash/Flex 2. Module development 3. Performance, scalability, HA 4. Marketing/evangelizing 5. Javascript/JQuery 6. Theme development 7. Graphics design

20 We suck at 1. Flash/Flex 2. Module development 3. Performance, scalability, HA 4. Marketing/evangelizing 5. Javascript/JQuery 6. Theme development 7. Graphics design 8. Documentation writing

21 What we want to get better at

22 Pay attention book authors and trainers

23 What we want to get better at

24 What we want to get better at 1. Module development

25 What we want to get better at 1. Module development 2. Theme development

26 What we want to get better at 1. Module development 2. Theme development 3. Javascript/JQuery

27 What we want to get better at 1. Module development 2. Theme development 3. Javascript/JQuery 4. PHP

28 What we want to get better at 1. Module development 2. Theme development 3. Javascript/JQuery 4. PHP 5. Performance, scalability, HA

29 What we want to get better at 1. Module development 2. Theme development 3. Javascript/JQuery 4. PHP 5. Performance, scalability, HA 6. Administering Drupal

30 What we want to get better at 1. Module development 2. Theme development 3. Javascript/JQuery 4. PHP 5. Performance, scalability, HA 6. Administering Drupal 7. CSS

31 What we want to get better at 1. Module development 2. Theme development 3. Javascript/JQuery 4. PHP 5. Performance, scalability, HA 6. Administering Drupal 7. CSS 8. SQL

32 Expert level Little or no experience Want to learn

33 Expert level Little or no experience Want to learn Marketing/evangelizing Performance, scalability and HA HTML CSS JavaScript/jQuery PHP SQL Flash/Flex Graphic design System administration Drupal module development Drupal theme development Administering Drupal Documentation writing

37 Problem areas

38 Problem areas Determining what modules to use Difficult to add media files Creating a site design Finding good documentation Migrating old content Structuring your site Setting up business processes Usability or user adoption issues Upgrading Drupal Configuring access rights Finding skilled Drupal developers

39 Most wanted end-user features for core

40 Most wanted end-user features for core Better media handling Custom content types (CCK fields) A WYSIWYG editor Better performance Better tools to structure or organize content A basic Views-like module Automatic upgrade functionality Improve event/date/calendar handling Discussion forum improvements Support for workflow management Mass editing and inline editing Better l10n and i18n support

41 Most wanted developer features for core

42 Most wanted developer features for core Better performance for authenticated users Get the Views module's query builder into core Improve node access system Better internal APIs (easier to use, consistency) Better external APIs (import/export, webservices) File API improvements A semantic core theme (like Zen) Smarter cache invalidation Mail subsystem (with queues and accounting) Support for MySQL master-slave configurations Further extend APIs to support internationalization Enhance code quality

43 Survey surprises Test-driven development not popular More database backends not popular

44 There are three kinds of lies: lies, damned lies, and statistics. Mark Twain

45 How many Drupal sites are you involved with? to to

46 Whutt, 85% of the respondents have more than one Drupal site? to to

47

48 How many people gave up on Drupal?

49

50 What we want to get better at is NOT what I want you to get better at!

51 During the course of this presentation...

52

53 Drupal.org will serve 20,000 pages

54 Drupal.org will serve 20,000 pages Drupal is downloaded roughly 100 times

55 Drupal.org will serve 20,000 pages Drupal is downloaded roughly 100 times 4 new Drupal sites will launch (estimate)

56 Drupal.org will serve 20,000 pages Drupal is downloaded roughly 100 times 4 new Drupal sites will launch (estimate) 3 of them will be ugly

57 Drupal grew by more than 200% last year

58 Drupal grew by more than 200% last year

59 We hope that during my DrupalCon presentation next year...

60

61 Drupal.org will serve 40,000 pages

62 Drupal.org will serve 40,000 pages Drupal is downloaded 200 times

63 Drupal.org will serve 40,000 pages Drupal is downloaded 200 times 8 new Drupal sites will launch

64 Drupal.org will serve 40,000 pages Drupal is downloaded 200 times 8 new Drupal sites will launch 5 of them will be ugly

65 Not good enough

66 It wouldn t close this gap Source: Google trends

67

68

69

70 So that during my presentation next year...

71 Drupal.org will serve 40,000 pages Drupal is downloaded roughly 200 times

72 Drupal.org will serve 40,000 pages Drupal is downloaded roughly 200 times 40 new Drupal sites will launch

73 Drupal.org will serve 40,000 pages Drupal is downloaded roughly 200 times 40 new Drupal sites will launch 10 of them will be ugly

74 A satisfied user tells 3 people about it. A dissatisfied user tells 11 people about it.

75 Everything should be made as simple as possible, but not simpler. -- Einstein

76 Being simple is not that simple, eh.

77

78 Design is not just what it looks like and feels like. Design is how it works. Steve Jobs

79 Design is not just what it looks like and feels like. Design is how it works. Steve Jobs

80 Translation: Lipstick on a pig doesn t cut it

81 Let s solve the real problems!

82 Executive summary Give users what they want: image handling, WYSIWYG and CCK in core Make Drupal easier to work with See DabbleDb if you need inspiration:

83 If it needs instructions, there is room for improvement.

84 We need to compete on the user experience. That is where the innovation will happen.

85 When technology delivers basic needs, user experience dominates. Don Norman

86 User experience is carefully engineered

87 User experience is carefully engineered We are engineers

88 User experience is carefully engineered We are engineers We can do it

89 Who is taking the lead?

90 Focus for Drupal 7

91 Focus for Drupal 7 32% 24% 44% End users with small or medium Drupal sites Enterprise users with large Drupal sites Web application developers

92 Preferred frequency of major Drupal releases One release every 3 years One release every year One release every 2 years Two releases a year

93 Preferred frequency of major Drupal releases 14% 1% 20% 65% One release every 3 years One release every year One release every 2 years Two releases a year

94 What does this all mean?

95 Easy...

96 Easy... Better media handling Custom content types (CCK fields) A WYSIWYG editor Better performance Better tools to structure or organize content A basic Views-like module Automatic upgrade functionality Improve event/date/calendar handling Discussion forum improvements Support for workflow management Mass editing and inline editing Better l10n and i18n support Framework 32% Better performance for authenticated users Get the Views module's query builder into core Improve node access system Better internal APIs (easier to use, consistency) Better external APIs (import/export, webservices) File API improvements A semantic core theme (like Zen) Smarter cache invalidation Mail subsystem (with queues and accounting) Support for MySQL master-slave configurations Further extend APIs to support internationalization Enhance code quality Product 68%

97 7 end-user features + 3 developer features = killer release

98 Drupal 7 killer release 1. Better media handling 2. Custom content types in core 3. WYSIWYG editor 4. Better performance 5. Better tools to structure/organize content 6. Basic Views like module 7. Automatic upgrade functionality 8. Better performance for authenticated users 9. Views query builder 10. Improve node access system 70 30

99 Drupal 7 killer release 1. Better media handling 2. Custom content types in core 3. WYSIWYG editor 4. Better performance 5. Better tools to structure/organize content 6. Basic Views like module 7. Automatic upgrade functionality 8. Better performance for authenticated users 9. Views query builder 10. Improve node access ystem 70 30

100 Drupal 7 killer release 1. Better media handling 2. Custom content types in core 3. WYSIWYG editor 4. Better performance 5. Better tools to structure/organize content 6. Basic Views like module 7. Automatic upgrade functionality 8. Improve node access system 9. Better internal APIs 10. Better external APIs (import/export, webservices) 70 30

101 There are three kinds of lies: lies, damned lies, and statistics. Mark Twain

102

103 Drupal 7 killer release 1. Better media handling 2. Custom content types in core 3. WYSIWYG editor 4. Better performance 5. Better tools to structure/organize content 6. Basic Views like module 7. Automatic upgrade functionality 8. Improve node access system 9. Better internal APIs 10. Better external APIs (import/export, webservices) Usability

104 Oh...

105 And we have to put out the Drupal 7 killer release one year from now... 14% 1% 20% One release every year 65%

106 Not good enough

107 Drupal.org improvements

108 Drupal.org improvements Quality/popularity ratings for modules Better documentation Faster page loads Better search Better structure/navigation A marketplace for Drupal services User ratings New drupal.org theme notifications for forum topics Documentation in PDF format Better marketing

120 Most important for contributed projects Quality/popularity ratings for modules Move critical contributed modules to core Per project documentation Security reviews for modules and themes Faster upgrade path/releases Per project support forum Test driven development Make it easier to translate modules More Drupal install profiles / distributions Better bug tracking functionality

121

122 What sector are you in? Privately-owned company Full-time consulting Education Other Non-profit Occasional consulting Student

123 What sector are you in? 9% 15% 28% 10% 12% 13% 14% Privately-owned company Full-time consulting Education Other Non-profit Occasional consulting Student

124 Popular with consultants 9% 15% 28% 10% 12% 13% 14% Privately-owned company Full-time consulting Education Other Non-profit Occasional consulting Student

125 Only 3.5% of the respondents work for a public company Only 3.7% of the respondents work for the government

126 Not good enough

127 We must grow the ecosystem

128 Who can afford to do professional work for nothing? -- Bill Gates

129 Open Source zealots might burn your house down...

130 Open Source is not incompatible with business

131 Many Open Source projects have benefited from healthy commercial environments around them...

132

133 We need more of these...

134 The dirty little secret to get noticed as a Drupal company... (or how to be a good bee)

135

136 BECOME PART OF THE COMMUNITY

137 Want me to spell it out in 4 four easy steps?

138 Become part of the community

139 Become part of the community == identify the bottlenecks / critical paths

140 Become part of the community == identify the bottlenecks / critical paths + find a way to give back

141 Become part of the community == identify the bottlenecks / critical paths + find a way to give back + embrace the chaos

142 Become part of the community == identify the bottlenecks / critical paths + find a way to give back + embrace the chaos + learn to collaborate

143 Identify the critical paths

144 Identify the critical paths You ll differentiate yourself

145 Identify the critical paths You ll differentiate yourself We ll be eager to collaborate

146 Identify the critical paths You ll differentiate yourself We ll be eager to collaborate You re fixing real problems

147 Act out of self-interest but try to looking for overlap to solve collective problems

148 Some concrete examples (you don t have an excuse anymore)

149 Some concrete examples (you don t have an excuse anymore) Contribute a top-5 wanted feature

150 Some concrete examples (you don t have an excuse anymore) Contribute a top-5 wanted feature Contribute a DBA

151 Some concrete examples (you don t have an excuse anymore) Contribute a top-5 wanted feature Contribute a DBA Contribute testing person

152 Some concrete examples (you don t have an excuse anymore) Contribute a top-5 wanted feature Contribute a DBA Contribute testing person Contribute a marketeer

153 Some concrete examples (you don t have an excuse anymore) Contribute a top-5 wanted feature Contribute a DBA Contribute testing person Contribute a marketeer Contribute a usability expert

154 Some concrete examples (you don t have an excuse anymore) Contribute a top-5 wanted feature Contribute a DBA Contribute testing person Contribute a marketeer Contribute a usability expert Contribute two usability experts

155 Some concrete examples (you don t have an excuse anymore) Contribute a top-5 wanted feature Contribute a DBA Contribute testing person Contribute a marketeer Contribute a usability expert Contribute two usability experts Contribute a technical writer

156 Some concrete examples (you don t have an excuse anymore) Contribute a top-5 wanted feature Contribute a DBA Contribute testing person Contribute a marketeer Contribute a usability expert Contribute two usability experts Contribute a technical writer Contribute a video cast producer

157 The critical path is your best marketing tool

158 Let s listen to our users and give them a killer Drupal 7 and Drupal.org improvements

159

160

161

162 Let s look ahead... The next years are going to be extremely interesting for Drupal. And so will the rest of today.

163 Thanks!

164 One more thing...

165 Overall happiness 4% 1% 44% 51% Great Totally awesome! Negative Horrible Neutral

166

167 What should the Drupal Association focus on? Work on and fund drupal.org improvements Invest in more hardware to support Drupal's growth Award grants or bounties for compelling ideas Provide visibility for interesting Drupal projects Attract more people to help improve the infrastructure Support the organization of more Drupal events Publish the Drupal newsletter Organize a presence at major conferences Publish press releases and promotional materials Protect the Drupal trademark/brand Distribute Drupal t-shirts, pins, posters, lanyards, etc Go after license violations

168 Complexity kills