Changes between Version 13 and Version 14 of SummerOfCode2010

Timestamp:

Mar 16, 2010, 6:25:59 AM (15 years ago)

Author:

Russell Keith-Magee

Comment:

Cleanup of template compilation proposal

SummerOfCode2010

@@ -22 +22 @@
 
  * You'll need to have a concrete task in mind (some ideas are below) along with a solid idea of what will constitute "success" (you tell us).  
- * If your proposal is a single large feature, you'll need to present a detailed design specification. This proposal should be posted to django-developers, where it can be refined until it sees a level of acceptance from the developer community.
+ * If your proposal is a single large feature, you'll need to present a detailed design specification. This proposal should be posted to [http://groups.google.com/group/django-developers django-developers], where it can be refined until it is accepted by the developer community.
  * We'll want to know a bit about you -- links to previous work are great, if any.  If you're proposing something ambitious, you'll need to convince us that you're up to the task.
  * You'll also need to provide us with a schedule, including a detailed work breakdown and major milestones so your mentor can know if and when to nag you :)
@@ -28 +28 @@
 Note that none of the ideas below are good enough to be submissions in their own right (so don't copy and paste)!  We'll want to know not just ''what'' you want to do but ''how'' you plan to pull it off.
 
-And don't feel limited to the ideas below -- if you've got a cool project you want to work on, we'll probably be able to find you a mentor.  We plan on approving as many projects as we possibly can.
+Don't feel limited to the ideas below -- if you've got a cool project you want to work on, we'll probably be able to find you a mentor.  We plan on approving as many projects as we possibly can.
 
 '''Note: we're looking for projects that add value to Django itself - ''not'' application/CMS projects that use Django.'''
 
+You should also note that as far as proposals go, we don't make a distinction between a GSoC project and any other proposal for a new feature. When you contribute code, you will be expected to adhere to the same contribution guidelines as any other code contributor. This means you will be expected to provide extensive tests and documentation for any feature you add, you will be expected to participate in discussion on [http://groups.google.com/group/django-developers django-developers] when your topic of interest is raised. If you're not already familiar with [http://docs.djangoproject.com/en/1.1/internal/contribution/ Django's contribution guidelines], now would be a good time to read them. 
+
 == Communication ==
 
-The [http://groups.google.com/group/django-gsoc django-gsoc] Google Group has been setup to facilitate communication between students and mentors in the GSoC efforts.
+The [http://groups.google.com/group/django-gsoc django-gsoc] Google Group has been setup to facilitate communication between students and mentors in the GSoC efforts. This list should only be used for GSoC administrative matters. Any discussions on the specifics of a given proposal should be directed to [http://groups.google.com/group/django-developers django-developers].
 
 == Ideas ==
 
-Here are some suggestions for projects students may want to propose (lazyweb: please add to this list!). This isn't by any means the be-all and end-all of ideas; please feel free to submit proposals for things not on this list. 
+Here are some suggestions for projects students may want to propose (lazyweb: please add to this list!). This isn't by any means the be-all and end-all of ideas; please feel free to submit proposals for things not on this list. However, if you're going to propose something that isn't on this list, you might want to check on [http://groups.google.com/group/django-developers django-developers] to see if there is any interest before you start drafting a full proposal.
 
-Try to scope ideas/proposals to the 4-month timeline -- simply proposing to fix a ticket or two will probably result in your proposal being rejected in favor of a more ambitious one.  The SOC '''does not cover activities other than coding''', so certain ideas ("Write a more detailed tutorial" or "Create demonstration screencasts" or "[wiki:AddAPony Add a pony]") are not suitable for inclusion here.
+When developing your proposal, try to scope ideas/proposals to the 4-month timeline -- simply proposing to fix a ticket or two will probably result in your proposal being rejected in favor of a more ambitious one.  The GSoC '''does not cover activities other than coding''', so certain ideas ("Write a more detailed tutorial" or "Create demonstration screencasts" or "[wiki:AddAPony Add a pony]") are not suitable for inclusion here.
 
 On the other side, though, be sure to be concrete in your proposal. We'll want to know what your goals are, and how you plan to accomplish them.
 
 In no particular order:
- * Template compilation
+
+=== Template compilation ===
+ * '''Complexity''': High
+
+A common criticism of Django's template language is that it is too slow. One reason for this is that the rendering process is handled at a very high level, interpreting a tree of tree nodes that have been generated by parsing the template source file. 
+
+Other Python-based template languages gain significant speedups by compiling templates directly to Python bytecode. A Django template compiler would allow for similar templating speedups.
+
+Issues to consider:
+ * How does Django's template variable scoping rules map to a compilation scheme?
+ * Django Template tags are able to modify the context as the template is rendered. How does this affect the compilation process?
+ * How should we handle the upgrade path when compiled templates are added to trunk?
+ 
+See also:
+ * [http://groups.google.com/group/django-developers/browse_thread/thread/9da4fdb455a002b5 One proposal to implement template compilation]
+ * The [source:django/trunk/django/template django.template code module]
+ * Other template languages, like [http://jinja.pocoo.org/2/ Jinja2] and [http://www.cheetahtemplate.org/ Cheetah]
+
+=== Enhanced auth.user ===
  * #3011 (auth User enhancement)
+
+=== 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.
+
+=== Improve annotation and aggregation ===
  * Improvements to annotation/aggregation: string concatentation, date operations, annotation of non-aggregate results, etc
+
+=== 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.
+ 
+=== App loading ===
  * Refactoring of the app loading mechanism (ref. #3591)
+
+=== IPv6 support ===
  * Implement proper IPv6 support in django (ref. #11442, #7735, +++)
+
+=== Testing updates ===
  * Update Django's system tests -- migrate Doctests to UnitTests, and merge the modeltests and regressiontests directories.