GSoC 2014 Server Side

(How to prepare?)
 
Line 32: Line 32:
== Hints ==
== Hints ==
The STKAddons code base is getting a bit messy so code restructuring is heavily encouraged. It would also be nice to have regression testing for the newly added features in the form of unit testing. If time allows this could be expanded to full coverage. We realize that this might be a lot for 3 months, so it's up to the student to come up with a promising but realistic timeline prioritizing features he thinks are most important. If unit-testing is considered more important than statistics, so be it. We do prefer few finished features over a lot half-finished features.
The STKAddons code base is getting a bit messy so code restructuring is heavily encouraged. It would also be nice to have regression testing for the newly added features in the form of unit testing. If time allows this could be expanded to full coverage. We realize that this might be a lot for 3 months, so it's up to the student to come up with a promising but realistic timeline prioritizing features he thinks are most important. If unit-testing is considered more important than statistics, so be it. We do prefer few finished features over a lot half-finished features.
 +
 +
Note : If a student proposes to use a different server-side technology, be sure to discuss this with us first!
 +
 +
= Preparation =
 +
 +
You should be able to set up a local instance of stkaddons to test any changes you make. This means you need a fully working Apache-Mysql-PHP stack. More information like where the database structure can be found or what dependencies need to be installed can be found in the readme file in the github repository.

Latest revision as of 16:39, 26 February 2014

Retrieved from "http://supertuxkart.sourceforge.net/GSoC_2014_Server_Side"

User Tools