How Drupal.org is built
summary
Drupal.org runs as eight separate Drupal sites plus services like the Composer Endpoint, Drupal CI and GitLab; it already deploys automatic updates in production via a Public Service Announcement API, per-release file checksums and package signing (signatures created on an HSM-protected signing VM using signify) so a client module can atomically replace changed files for non‑Composer installs. Issue crediting uses entity references to aggregate contributions and drives marketplace ranking. Planned work includes semantic versioning for contrib, collaborative GitLab issue forks, and Drupal 8/9 migrations.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 0:36Getting involved with Drupal
- 2:08The Drupal team
- 3:52Drupal jobs
- 6:10Services
- 7:48Automatic Updates
- 16:59Issue Crediting
- 17:42Commit Messages
- 18:09Entity References
- 19:19Field Storage
- 20:34Drupalorg Metrics
- 23:25Drupalorg Marketplace
- 24:21Contributions
- 25:13Contribution Survey
- 25:55Upcoming Projects
- 27:13Semantic Versioning
- 28:54Project
- 30:53Issue Forks
- 33:24Old Sites
- 36:23ThirdParty Services
- 37:08Old Web
- 37:59Membership
- 38:35Supporting Partners
- 39:07Drupal Conference
- 39:59Drupal Contribution Day
- 40:23Questions
- 47:03How can we help
- 49:59SEO
