Legend:

* [/browser/django/trunk/ Browse source]: See the full code via a Web interface.

18

17

* [/timeline/ Timeline]: Keep track of recent changes.

19

18

20

19

== Getting involved ==

20

Before ''anything'', please read [http://www.djangoproject.com/documentation/contributing/ How to contribute to Django]. You'll find out how the Django community works, and possibly save yourself much grief in the future. `:)`

21

21

22

* [http://www.djangoproject.com/documentation/contributing/ How to contribute to Django]: How our community works.

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.

28

28

29

Currently, a number of branches of development aim to implement new features in Django. Each of these may or may not be stable, but we encourage you to test them out and give feedback to branch maintainers. Each branch has its own page.

29

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!

30

30

31

31

* [wiki:NewformsAdminBranch newforms-admin]: A refactoring of Django's admin site to use the [http://www.djangoproject.com/documentation/newforms/ newforms library] rather than automatic manipulators, allowing for additional customization of admin-site functionality.