Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Version 18 (modified by simon, 13 years ago) (diff)

Added link to Kid SoC page

Summer of Code 2006

 Summer of Code 2006 site

 Student Signup

 Student FAQ

 Google's Summer of Code 2005: Experience of One Mentor

From our mailing list:

 Fwd: [Web-SIG] [Fwd: Summer of Code preparation]

 Attention Summer of Code prospective participants!

Project ideas

  • Build a schema migration tool for SQLAlchemy, or an SQLObject compatability layer for SQLAlchemy
  •  Work on Kid
  • Build up FastData? into a complete, customizable administration UI
  • Make Widgets autonomous and devise a widget protocol allowing widgets to be used by other frameworks
  • Make TG work on IronPython? and/or Jython
  • Create a flat-file model (perhaps using  MetaTemplate, see  discussion)
  • Add a new Toolbox app for the scheduler
  • ...

Please note, these are just ideas, some as presented here are not enough to keep you occupied throughout the summer.

Ground rules (subject to change)

  1. You must not overbook yourself. Working on your TG project(s) should be your main activity for the entire summer.
  1. You must be willing to provide weekly status reports.
  1. You will be expected to learn how to use SVN and write tests for everything you code.


For any additional inquiry feel free to contact the corresponding mentors:

  • Jonathan LaCour? (jonathan at cleverdevil dot org): SQLAlchemy
  • Simon Belak (simon at hruska dot si): TurboGears

HOWTO: Write a Summer of Code application

Adapted from  Drupal.

Sell your idea. Describe your idea in detail. What is its ultimate goal? What components will it have? What benefits does it have for TurboGears itself and its community? How do you plan to achieve completion of your project? If a specification already exists, what will you do that will go above and beyond expectations?

Sell yourself. Get across your enthusiasm for the project. Tell us what makes you stand out from the rest of the crowd. Talk about your past experiences, what makes you tick. Why are you interested in open source software, and TurboGears in particular? What interests do you have, and how do these interests relate to the project for which you're applying? There is a basic assumption that people applying for Summer of Code will have at least some programming skills already. So rather than spend a lot of time elaborating on these (though by all means, do tell us what you know), spend time talking about you.

Show enthusiasm. Summer of Code is a very exciting opportunity, and TurboGears is an extremely exciting project to work on. We're not just looking for people who want a summer job to pass the time, we're looking for devoted people who have an intrinsic passion for open source.

Get feedback on your idea from the community. Discussing your idea with some established TurboGears folks is vital. If your idea duplicates existing efforts or code (and does not provide a very convincing reason for doing so), it will be rejected. Try to have your application reviewed by someone before you submit it, whether that be the mentor for a particular project itself (in the case of already generated ideas on the following pages), or a person with expertise in a certain area (such as Widgets or Kid). Don't be afraid to ask the community for help; we want you to succeed just as much as you do.

Don't be afraid to go out on a limb. Have a brilliant idea that's not covered by the proposals on the following pages? Great! Don't be scared to try and think "outside the box" and come up with a fantastic idea of your own.