Do you wanna be a core dev? (You don't have to be core dev...)
summary
Explains exactly how to move from user to committer: Django now separates a broader core team from a smaller committer team and a technical board of five elected per release; roles are time‑limited so people can step back. Contribution workflow uses IRC, mailing lists, Trac (tickets move unreviewed → accepted → ready for check‑in, flags like easy pickings, patch/needs improvement, docs/tests required) plus GitHub pull requests (GitHub account required). Report security issues privately to security@djangoproject.com. Start small, be rigorous, and build trust.
AI-written summary · about
chapters (14)
- 0:00Introduction to Django
- 2:07The community funnel
- 4:10Core team dynamics
- 7:11Structural changes
- 10:29Governance and the technical board
- 12:48Documenting procedures
- 13:45Mental health and burnout
- 16:47Communication tools
- 20:06Participating in mailing lists
- 23:24Ticket management and tracking
- 30:47Best practices for contribution
- 35:54GitHub and development workflow
- 38:59Release processes
- 44:23Building trust and concluding
related talks
15mYour web framework needs you!
27mFrom junior developer to Django contributor: My open source journey
30mFrom 0 to core contributor
40mOops! I Became an Open Source Maintainer! 😱
26mOops! I Became an Open Source Maintainer!
32mTeam Building in the Django Community: Strategies for Collaboration
18mOpen communication for open development
30mMake the most of Open Source