Version 287 (modified by 13 years ago) ( diff ) | ,
---|
Django source-code repository, wiki and bug-report system ¶
Django is available open-source under the BSD license.
- Getting the code
- Browsing the code online
- Getting involved
- Branches
- Descriptions of major changes to the codebase
- Under discussion
- More Django resources
Getting the code ¶
Django uses Subversion (svn
) for managing its code.
Assuming you have Subversion installed, the following command in a terminal will fetch the most recent code for you:
svn co https://code.djangoproject.com/svn/django/trunk/
Django also offers "official" release tarballs at the download page.
Browsing the code online ¶
- Browse source: See the full code via a Web interface.
- Timeline: Keep track of recent changes.
Getting involved ¶
Before anything, please read How to contribute to Django. You'll find out how the Django community works, and possibly save yourself much grief in the future. :)
- Tickets: View active tickets, make bug reports and contribute feature requests.
- Little, easy improvements: Get your feet wet by taking on one of these small tasks.
- "Easy Pickings" Tickets: Work on simple tickets to get familiar with Django's code base and the contribution process.
- How to report security issues.
- DjangoDesign: Are you a designer rather than a coder? We still want your input. Let us know how we can improve on Django's visual/UX design.
Branches ¶
Development of major new features for Django tends to take place in branches — copies of the main codebase focused on a particular feature. Using branches makes it easier to experiment with such sweeping changes without possibly breaking the trunk — the main line of development.
Branches may not be stable, but they offer a chance to test out bleeding-edge code before it hits the mainline. Give them a try, and remember to send feedback to the branch maintainers!
See DjangoBranches for more information, including a list of active branches.
Descriptions of major changes to the codebase ¶
- Backwards-incompatible changes: Comprehensive list of backwards-incompatible changes made since first public release.
Under discussion ¶
- Better error messages: Documenting situations where better error messages would improve the experience of using Django
- Replacing get_absolute_url and generally improving the concept of url-aware models.
More Django resources ¶
See the Django resources page for a cornucopia of unofficial articles, code samples and other information contributed by the community.