|Version 13 (modified by russellm, 6 years ago) (diff)|
Google's Summer of Code 2010
Django is once again applying to be a sponsoring organization for the 2010 Google Summer of Code. (Read Google's page for more information on how the program works.)
Django's SoC program is being run by Jannis Leidel (jannis /at/ leidel /dot/ info).
If you're interested in mentoring -- supervising a student in work on Django-related activities -- add your name and email here:
- Jannis Leidel (jannis /at/ leidel /dot/ info)
- Russell Keith-Magee (russell@…)
- Ville Säävuori (ville@syneus dot fi)
- Greg Wilson (gvwilson@…)
- Your Name (Your Email)
Student applications open March 29 and end on April 9.
If you'd like to get started on your proposal early, we'll be looking for a few things.
- 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.
- 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 :)
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.
Note: we're looking for projects that add value to Django itself - not application/CMS projects that use Django.
The django-gsoc Google Group has been setup to facilitate communication between students and mentors in the GSoC efforts.
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.
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 "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
- #3011 (auth User enhancement)
- 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.
- Improvements to annotation/aggregation: string concatentation, date operations, annotation of non-aggregate results, etc
- 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.
- Refactoring of the app loading mechanism (ref. #3591)
- Implement proper IPv6 support in django (ref. #11442, #7735, +++)
- Update Django's system tests -- migrate Doctests to UnitTests, and merge the modeltests and regressiontests directories.