GSoC overview

(Code and tickets)
(Code and tickets)
Line 21: Line 21:
=== Code and tickets ===
=== Code and tickets ===
-
The main prerequisite for working on SuperTuxKart is good C++ knowledge. You will also want to get familiar with our [https://sourceforge.net/apps/trac/supertuxkart/ bug tracker]. You do need a sourceforge account in order to submit a ticket. For a successful proposal we expect you to supply at least one patch beforehand so that we can have a look at your coding and commenting style. We have marked certain tickets to be suitable for GSoC, see [[https://sourceforge.net/apps/trac/supertuxkart/report/9|this list]], and added some instructions how to fix the tickets (e.g. design, or which files to look at). Note that some of the tasks are not trivial and need some time to understand the solution, though the actual implementation time should not be too high. Or feel free to create your own ticket. In any case, please discuss the ticket with us first, we can help in identifying tickets appropriate for your skill level. One options is always to improve documentation and fix [[Coding_Style | coding style issues]]. While STK's documentation is rather good and extensive, there are always things that can be improved (e.g. older files might not follow latest changes of our coding style).
+
The main prerequisite for working on SuperTuxKart is good C++ knowledge. You will also want to get familiar with our [https://sourceforge.net/apps/trac/supertuxkart/ bug tracker]. You do need a sourceforge account in order to submit a ticket. For a successful proposal we expect you to supply at least one patch beforehand so that we can have a look at your coding and commenting style. We have marked certain tickets to be suitable for GSoC, see [https://sourceforge.net/apps/trac/supertuxkart/report/9|this list], and added some instructions how to fix the tickets (e.g. design, or which files to look at). Note that some of the tasks are not trivial and need some time to understand the solution, though the actual implementation time should not be too high. Or feel free to create your own ticket. In any case, please discuss the ticket with us first, we can help in identifying tickets appropriate for your skill level. One options is always to improve documentation and fix [[Coding_Style | coding style issues]]. While STK's documentation is rather good and extensive, there are always things that can be improved (e.g. older files might not follow latest changes of our coding style).
Any contributions to SuperTuxKart must be in clean and portable C++. They should also compile without any warnings. We don't expect that a student to be able to check his code on all supported platforms - our community will do this and fix any minor issues that should occur when using a different compiler. But please have a look at some of our [[Portability_concerns | portability advise]].
Any contributions to SuperTuxKart must be in clean and portable C++. They should also compile without any warnings. We don't expect that a student to be able to check his code on all supported platforms - our community will do this and fix any minor issues that should occur when using a different compiler. But please have a look at some of our [[Portability_concerns | portability advise]].

Revision as of 05:51, 21 March 2013

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

User Tools