Legend:

* [wiki:ModelInheritance]: Write-up discussing how inheritance/subclassing of models should work. Currently this is not implemented in the development version of Django, so if you need model subclassing stick to one of the older stable releases or use workarounds like one-to-one relationships.

22

22

* [wiki:SchemaEvolution]: This is a new feature, under development as a project for the 2006 Summer of Code.

23

* [wiki:GenericAuthorization]: Currently Django's permission system only works at the level of an entire model -- e.g., user "Bob" has access to add flatpages and edit users. This Summer of Code project will extend the permission system to be much more fine-grained, so permissions will be able to be assigned per object instead of per model (so, for example, user "Bob" could be given permission to edit only flatpage number 24 and user number 12, instead of all flatpages and all users).

23

* [wiki:RowLevelPermissions]: Currently Django's permission system only works at the level of an entire model -- e.g., user "Bob" has access to add flatpages and edit users. This Summer of Code project will extend the permission system to be much more fine-grained, so permissions will be able to be assigned per object instead of per model (so, for example, user "Bob" could be given permission to edit only flatpage number 24 and user number 12, instead of all flatpages and all users).

24

* [wiki:GenericAuthorization]: A more flexible authorization system for Django. The new system should allow for ACL's, role-based systems, and Django's current model-level permissions.

24

25

* Multiple authentication backends: the [http://code.djangoproject.com/browser/django/branches/multi-auth multi-auth branch] of Django, currently under development, is abstracting the authentication backend to make it easier to use other authentication systems like LDAP. Check out the [http://code.djangoproject.com/browser/django/branches/multi-auth/docs/authentication.txt#L677 documentation] to see how this will work.