| 20 | | == Getting involved == |
| 21 | | Before ''anything'', please read [https://docs.djangoproject.com/en/stable/internals/contributing/ How to contribute to Django]. You'll find out how the Django community works, and possibly save yourself much grief in the future. `:)` |
| 22 | | |
| 23 | | * [https://code.djangoproject.com/wiki/Reports Tickets]: View active tickets, make bug reports and contribute feature requests. |
| 24 | | * [wiki:LittleEasyImprovements Little, easy improvements]: Get your feet wet by taking on one of these small tasks. |
| 25 | | * [https://code.djangoproject.com/query?status=!closed&easy=1 "Easy Pickings" Tickets]: Work on simple tickets to get familiar with Django's code base and the contribution process. |
| 26 | | * [https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-features/#reporting-security-issues How to report security issues]. |
| 27 | | * 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. |
| 28 | | |
| 29 | | == Branches == |
| 30 | | 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. |
| 31 | | |
| 32 | | 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! |
| 33 | | |
| 34 | | See DjangoBranches for more information, including a list of active branches. |
| 35 | | |
| 36 | | == Descriptions of major changes to the codebase == |
| 37 | | |
| 38 | | * [wiki:BackwardsIncompatibleChanges Backwards-incompatible changes]: Comprehensive list of backwards-incompatible changes made since first public release. |
| 39 | | |
| 40 | | == Under discussion == |
| 41 | | |
| 42 | | * [wiki:BetterErrorMessages Better error messages]: Documenting situations where better error messages would improve the experience of using Django |
| 43 | | * [wiki:ReplacingGetAbsoluteUrl Replacing get_absolute_url] and generally improving the concept of url-aware models. |
| 44 | | |
| 45 | | == More Django resources == |
| 46 | | |
| 47 | | See the [wiki:DjangoResources Django resources page] for a cornucopia of unofficial articles, code samples and other information contributed by the community. |
| | 13 | The documentation contains a [https://docs.djangoproject.com/en/stable/internals/contributing/ contributing guide] that should answer your questions. If it doesn't, file a bug! |