Changes between Version 16 and Version 17 of SummerOfCode2010


Ignore:
Timestamp:
03/16/2010 07:07:15 AM (5 years ago)
Author:
russellm
Comment:

Cleanup of #3011; added stub for remaining projects.

Legend:

Unmodified
Added
Removed
Modified
  • SummerOfCode2010

    v16 v17  
    6969 * '''Complexity''': High
    7070
    71 One of the most class of questions on [http://groups.google.com/group/django-users django-users] surrounds issues of customizing Django's User model:
     71One of the most common class of questions on [http://groups.google.com/group/django-users django-users] surrounds issues of customizing Django's User model. For example:
    7272 * How can I use an email address as a username?
    7373 * I want to use Twitter/OAuth/Facebook to login - why can't I leave the username field empty?
    74  * How can I make the username field X characters longer/shorter?
     74 * How can I make the username field N characters longer/shorter?
    7575 * How can I allow [insert random character] in usernames?
    7676 * How can I have a single "name" field instead of "first_name"/"last_name"?
    7777
    78 At present, there is no easy answer to these questions. Use of Django User model is not mandatory, but it is a dependency for a lot of Django applications. It is possible to do some of these customizations, but it's not trivial to do so.
     78At present, there is no easy answer to these questions. Use of Django User model is not mandatory, but it is a dependency for a lot of Django applications. It is possible to do some of these customizations using some tricks or by manually modifying the contrib.auth source code, but these are not good solutions for novice users.
    7979
    80 Ticket #3011 describes one approach that has been rejected - the idea of a 'pluggable' User model. However, the general problem remains.
     80Ticket #3011 describes one approach that has been rejected - the idea of a 'pluggable' User model.
    8181
    82 '''Note:''' This isn't a problem with a trivial solution, and it isn't a problem where we will take the first proposal we see. A successful proposal on this project will require extensive discussion on [http://groups.google.com/group/django-developers django-developers].
     82'''Note:''' This isn't a problem with an existing worked solution. A successful proposal on this project will require extensive discussion on [http://groups.google.com/group/django-developers django-developers].
    8383
    8484Issues to consider:
     
    8989
    9090See also:
     91 * #3011, and any discussion on [http://groups.google.com/group/django-developers django-developers] that references it.
    9192 * Discussions on [http://groups.google.com/group/django-users django-users] when users have asked the "how do I" questions
    9293 * The [source:django/trunk/django/template django.contrib.auth code module]
    9394
    9495=== Housekeeping ===
    95  * A big housekeeping run. Formalize and document the stable parts of _meta; Cleanup of error messages (BetterErrorMessages and #3349 for ideas); profile the test suite looking for low hanging optimizations.
     96 * '''Complexity:''' Minor
     97
     98A big housekeeping run. Formalize and document the stable parts of _meta; Cleanup of error messages (BetterErrorMessages and #3349 for ideas); profile the test suite looking for low hanging optimizations.
     99
     100Issues to consider:
     101 *
     102
     103See also:
     104 *
    96105
    97106=== Improve annotation and aggregation ===
    98  * Improvements to annotation/aggregation: string concatentation, date operations, annotation of non-aggregate results, etc
     107 * '''Complexity:''' Minor
     108
     109Improvements to annotation/aggregation: string concatentation, date operations, annotation of non-aggregate results, etc
     110
     111Issues to consider:
     112 *
     113
     114See also:
     115 *
    99116
    100117=== Customizable serialization ===
    101  * Customizable Serialization. Define a class-based structure that allows users to define their own serialization format (including different output structure, including non-model fields, etc). Define Django's own serializers in that format.
     118 * '''Complexity:''' Minor
     119
     120Customizable Serialization. Define a class-based structure that allows users to define their own serialization format (including different output structure, including non-model fields, etc). Define Django's own serializers in that format.
     121
     122Issues to consider:
     123 *
     124
     125See also:
     126 *
    102127 
    103128=== App loading ===
    104  * Refactoring of the app loading mechanism (ref. #3591)
     129 * '''Complexity:''' Minor
     130
     131Refactoring of the app loading mechanism (ref. #3591)
     132
     133Issues to consider:
     134 *
     135
     136See also:
     137 *
    105138
    106139=== IPv6 support ===
    107  * Implement proper IPv6 support in django (ref. #11442, #7735, +++)
     140 * '''Complexity:''' Minor
     141
     142Implement proper IPv6 support in django (ref. #11442, #7735, +++)
     143
     144Issues to consider:
     145 *
     146
     147See also:
     148 *
    108149
    109150=== Testing updates ===
    110  * Update Django's system tests -- migrate Doctests to UnitTests, and merge the modeltests and regressiontests directories.
     151 * '''Complexity:''' Minor
     152
     153Update Django's system tests -- migrate Doctests to UnitTests, and merge the modeltests and regressiontests directories.
     154
     155Issues to consider:
     156 *
     157
     158See also:
     159 *
Back to Top