Changes between Version 16 and Version 17 of SummerOfCode2010

Timestamp:

Mar 16, 2010, 7:07:15 AM (15 years ago)

Author:

Russell Keith-Magee

Comment:

Cleanup of #3011; added stub for remaining projects.

SummerOfCode2010

@@ -69 +69 @@
  * '''Complexity''': High
 
-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:
+One 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:
  * How can I use an email address as a username?
  * I want to use Twitter/OAuth/Facebook to login - why can't I leave the username field empty?
- * How can I make the username field X characters longer/shorter?
+ * How can I make the username field N characters longer/shorter?
  * How can I allow [insert random character] in usernames?
  * How can I have a single "name" field instead of "first_name"/"last_name"?
 
-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.
+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 using some tricks or by manually modifying the contrib.auth source code, but these are not good solutions for novice users.
 
-Ticket #3011 describes one approach that has been rejected - the idea of a 'pluggable' User model. However, the general problem remains.
+Ticket #3011 describes one approach that has been rejected - the idea of a 'pluggable' User model.
 
-'''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].
+'''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].
 
 Issues to consider:
@@ -89 +89 @@
 
 See also:
+ * #3011, and any discussion on [http://groups.google.com/group/django-developers django-developers] that references it.
  * Discussions on [http://groups.google.com/group/django-users django-users] when users have asked the "how do I" questions
  * The [source:django/trunk/django/template django.contrib.auth code module]
 
 === Housekeeping ===
- * 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.
+ * '''Complexity:''' Minor
+
+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.
+
+Issues to consider:
+ *
+
+See also:
+ *
 
 === Improve annotation and aggregation ===
- * Improvements to annotation/aggregation: string concatentation, date operations, annotation of non-aggregate results, etc
+ * '''Complexity:''' Minor
+
+Improvements to annotation/aggregation: string concatentation, date operations, annotation of non-aggregate results, etc
+
+Issues to consider:
+ *
+
+See also:
+ *
 
 === Customizable serialization ===
- * 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.
+ * '''Complexity:''' Minor
+
+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.
+
+Issues to consider:
+ *
+
+See also:
+ *
  
 === App loading ===
- * Refactoring of the app loading mechanism (ref. #3591)
+ * '''Complexity:''' Minor
+
+Refactoring of the app loading mechanism (ref. #3591)
+
+Issues to consider:
+ *
+
+See also:
+ *
 
 === IPv6 support ===
- * Implement proper IPv6 support in django (ref. #11442, #7735, +++)
+ * '''Complexity:''' Minor
+
+Implement proper IPv6 support in django (ref. #11442, #7735, +++)
+
+Issues to consider:
+ *
+
+See also:
+ *
 
 === Testing updates ===
- * Update Django's system tests -- migrate Doctests to UnitTests, and merge the modeltests and regressiontests directories.
+ * '''Complexity:''' Minor
+
+Update Django's system tests -- migrate Doctests to UnitTests, and merge the modeltests and regressiontests directories.
+
+Issues to consider:
+ *
+
+See also:
+ *