Pony, Cat, and Paw: Getting Started with the Open Source Menagerie
summary
Django has about 1,300 open tickets and roughly 500 tickets marked has_patch so find an unassigned ticket or revive a closed PR, click “assign to” with your GitHub username, implement the change, run the relevant tests locally and the Jenkins pipeline will run the rest, include tests and documentation as a minimum, run isort and follow the commit message format from CONTRIBUTING, expect a median two‑week review cycle, use Sprint, IRC or django‑developers mailing list for help, and do ticket triage or PR review while waiting.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:05Getting Started with Django
- 7:40Working on a Ticket
- 13:07Getting Help
- 18:44Review Tickets
- 21:15Friendly Reviews
- 22:39When to Contribute
- 26:18Other Ways to Contribute
- 28:03Outro
related talks
30mMake the most of Open Source
10mYour Web Framework Needs You: An Update
01h 05mDrupal Contributions - A Pragmatic Approach to the Issue Queue
49mDo you wanna be a core dev? (You don't have to be core dev...)
37mContributing to Django or how I learned to stop worrying and just try to fix an ORM Bug
43m'ProTalking' Your Way into Open Source
49m"State of Django" Panel
31mMaintaining a big open source project: lessons learned
