Django & Drupal: A tale of two cities.
summary
Comparison shows concrete outcomes and processes: Drupal embeds Symfony and CKEditor to reduce bespoke plumbing, celebrates Drupal 8 release parties worldwide, and raises funds with a targeted Drupal 8 accelerate: $250,000 campaign; Django publishes a public code-of-conduct enforcement manual and runs global outreach like Django Girls events. Both run nonprofits (501c3), rely on conferences for revenue, struggle with burnout and user engagement, and share process-level lessons even when codebases and licenses differ.
AI-written summary · about
chapters (35)
- 0:00Introduction
- 1:10A tale of two cities
- 1:47The age of wisdom
- 2:27Every house has its secret
- 3:40Django vs Ruby
- 5:12Django vs Inkscape
- 5:55Django Code of Conduct
- 7:33Django is a framework with CMS like tendencies
- 7:47What does that mean
- 9:07Its both right
- 10:23Were both open source
- 10:45Djangos culture
- 13:06Drupal events
- 13:36Django in Antarctica
- 14:00Drupal 8 release
- 14:20Drupal bacon
- 15:08Community
- 17:38Community summits
- 18:47Diversity
- 20:07Burnout
- 21:28The Tragedy of the Commons
- 23:39Bug Reports
- 24:08Documentation
- 24:45Emotional Labor
- 25:40Django Software Foundation
- 26:58The Open Web
- 29:11We need to level up
- 30:21Building bridges across technologies
- 31:47Kathy Sierra
- 32:32John O Bacon
- 32:56A revolution in Australia
- 35:25Questions
- 36:23End users
- 39:14Fundraising
- 42:41Lessons from Drupal
