Google Summer of Code Tips

From K-3D

Jump to: navigation, search

Here are collected tips and advices for the GSoc students. Specially examples of good finished projects, so that students can have an idea of how to make a succesful project.

Prior Gsoc projects

You can browse already made GSoc projects on the google pages:

K-3D Gsoc 2007 Projects

External Examples

Blender's Modifier Stack Upgrade

This project quite complete. Is a good idea to make a wiki user page with the project idea.

Ogre: Extending, Demo-ing, and Documenting the Shadow Mapping System

This submission is worth viewing.



It is true that you won't have too much time to get in touch with the whole software and specially with its source code. But you should try to do this before you send your application:

  • Download K-3D and install it.
    • Play with the application, know its current state and model behind it.
  • Download the source code.
    • Compile it.
    • Navigate its source code.
    • Try to make a plugin or modify something. (see the Plugin Tutorial)
      • If you are fast coding, you can even try to make a prototype of your idea.

This will help you to put your idea in the context of the K-3D environment. So spend a reasonable time hacking with K-3D and then it will be easier exposing your idea with clarity (which the key point when applying).

Student Selection

Last year, student applications were evaluated mostly on the quality of the application itself. Additional factors should be taken into account:

  • The summer agenda (job, vacations, ...) of the student will be taken into account during student selection.
  • A small code sample will be requested as part of the application process. This allows us to measure both student commitment and technical quality. It also ensures a minimal familiarity with K-3D prior to the start of GSoC
  • Regular chat and email communication before program start, to ensure student availability. Though this was no problem last year, other projects have reported experiences with dissapearing students or very poor communication.
  • Community participation: Extra points for students who are active on the mailing list and wiki before program start!

External Tips