Awesome - I'd love to see it!
A good place to start is with our guide to contributing patches:
http://www.djangoproject.com/documentation/contributing/#submitting-patches.
The most important part is correctly generating a patch, but luckily
subversion makes this pretty easy. All you have to do is run "svn diff" and
save the output into a file (if you're on a *nix, "svn diff > mypatch.diff"
will do the trick nicely).
If you run this comment from the top of the Django source tree (i.e. the
directory that contains "AUTHORS", "LICENSE", and "README"), you'll get a
patch that covers everything you've changed in the tree.
Then you can either create a ticket with the patch, or if you'd like feedback
without/before opening a ticket, just post it here.
Hope that helps, and I look forward to checking out your code.
Jacob
I've done that; it's in ticket 3152
(http://code.djangoproject.com/ticket/3152/). I've screwed up the diff
slightly (left a couple of print statements in and some other changes
to templates that weren't strictly necessary), but I hope you can get
the general idea!
Hope you like it :)
Ben