The Drupal project has experienced phenomenal growth over its more than 14 years, growing from a small hobby project to over 1 million known installations, over 1 million Drupal.org users, and more than doubling the active contributors and commits in Drupal core between Drupal 7 and Drupal 8, as well as thousands of people who depend on Drupal in some way for a living.
This talk will "de-mystify" some recent developments in the community, from the technical direction of Drupal 8, to various project governance changes, to the increasing role of the Drupal Association on Drupal.org. We'll look at both the historical context that brought those changes about, and talk about how they'll help us scale to the next 1 million sites and users.
2. what's happening?
• Sprints: D8 Cri.cals, Performance, Front-‐End,
Documenta.on, Mutlilingual, Search API, Rules,
Commerce, others?
• Over half (26) of D8 cri.cal issues updated, 5 fixed so far
• 84 total patches commiNed, 134 (known) issues being
worked on
• Issue tag: "drupaldevdays" or (for the cri.cal and
performance sprint) "D8 Accelerate Dev Days"
7. Drupal has…
• 1,127,761 live sites that we know about
• 1,168,980 people in 229 countries speaking 180 languages
• 37,930 of them are developers
• 30,276 modules, 2,128 themes, 930 distribu.ons
• 2,782 contributors to Drupal 8 so far
• Hundreds of Drupal books, 1000s of documenta.on pages
9. Drupal had…
• A couple hundred live sites that we knew about (by word
of mouth, since there was no Update Status)
• Around 20,000 people; a couple hundred were developers
• A couple hundred modules, a couple dozen themes (all of
them ugly), distribu.ons weren't invented yet
• 50 core contributors
• Zero Drupal books; en.re handbook was about 100 pages
20. big drupal 4.7.0 features
• AJAX
• Collapsible fieldsets
• Free tagging
• New XML-‐RPC library
• Form API
• Updated documentaVon for all modules ;)
hNps://www.drupal.org/drupal-‐4.7.0
38. big drupal 6.0 features
• Mul.lingual
• New theme system (.tpl.php files)
• Improved security and performance
• Drag-‐and-‐Drop
hNps://www.drupal.org/drupal-‐6.0
40. just a sampling…
• What takes a Drupal person 30 seconds to *do* might
take a new user 30 minutes to *find*.
• Lots of confusion on front-‐end/back-‐end separa.on:
where am I? Is this what I see, or my users see?
• Confusing terminology
• Page vs. Story? Create content vs. content type
• Collapsible fieldsets = goNa click 'em all!
hNps://www.drupal.org/node/1175694
52. major findings
• Content crea.on/orienta.on problems from D6 fixed!
• Now, the next layer of the onion…
• Content = content, regardless of where it is
• People want edit in place and previews of
everything
• If users end up on Drupal.org, they are hosed. :P
53. state of drupal survey (v2)
hNp://buytaert.net/state-‐of-‐drupal-‐presenta.on-‐august-‐2011
64. challenges
• Lack of clear decision-‐making leads to frustra.on; appears
"cliquish" to "outsiders."
• Greatly favors those with a tremendous amount of free .me on
their hands; terrible for diversity
• Oren "he/she who yells the loudest wins"; can shut down good
ideas by people who don't want to engage
• If no one cares about a thing (or cares enough to fight a baNle), it
doesn't get done.
• "Bus factor" = burnout; key doers feel "trapped" in roles
65. soluVon: augment do-‐ocracy
with formal governance
drupal.org
sorware
working group
drupal.org
infrastructure
working group
drupal.org
content
working group
hNps://www.drupal.org/governance
licensing
working group
branding and
marke.ng
commiNee
community
working group
technical
working group
drupal core
documenta.on
working group
security
working group
67. benefits
• Focus on strategy vs. tac.cs
• More transparent decision-‐making process
• Clear points of escala.on in case of conflict
• Improve "bus factor" by providing support for key
roles
68. example: project applicaVon
review process revamp
hNps://www.drupal.org/node/2453587
• Deploy automated code scanning tools for all projects
• All users create sandboxes first, get full project when
scan passes (non-‐veNed limited to one full project)
• Non-‐veNed users can request veNed status in issue
queue once full module passes scans
• Code review scaled back to licensing, security, or
major API usage problems only.
73. semanVc versioning
• New feature releases of Drupal 8 every 6 months
• Backwards compa.bility preserved!
• Core devs, contrib devs, site builders working on same code base
• Drupal 9? Not un.l there's enough done to warrant breaking BC
74. will we see the killer d8
release in 8.1.0? 8.2.0?
✓
✓
✓
✓
✓
✓
?
?
?
some other awesome thing?
78. what are we funding?
• Performance improvements
• Upgrade path
• Security fixes
• Targeted sprints
• Testbot moderniza.on
• Awesome core contributors!
hNp://webchick.net/d8accelerate-‐deep-‐dive
79. why?
• Most core contribu.on done on volunteer .me
• D8 currently in "bug fix slog"; fun stuff is already done
• Contributors funded through D8 accelerate don't
need to find D7 work
• Targeted sponsorship like this also got D6, D7 out the
door, just less transparently
hNp://webchick.net/d8accelerate-‐deep-‐dive