I realized the error I've made with the previous post soon after: please, let's not turn this thread into another debate over physics vs graphics.
Returning on topic: IMHO it would be time better spent to dedicate this thread to planning a possible participation of Trem in future GSoC editions. I've changed the thread title accordingly (took 2009 out).
A starting point would be this:
Google's organization selection criteria.
A first useful step would thus be the above: coming to terms with how you'd use a bunch of students unleashed on the Trem code, given the opportunity.
The second would be be putting together a succint list of selling points for Trem, from a dev perspective, things that would make Google accept it in GSoC.
The third step would be how you'd go about introducing a student (or any person with the required coding skills) to coding for Trem. How can they tell if they got the skills? What are the requirements? What development environment do they need? What previous experience? etc.
All developers, past and present, who would like to throw their 2c in, please do.
This brainstorm would also benefit another topic. I'd like to take some time at some point in the future and give some real loving to the official Trem wiki. The development section will, naturally, need it too. Whether Trem will try to go for GSoC 2010 or not, we can still gather useful guidelines for would-be contributors and populate the wiki. It can't hurt.