193
edits
Difference between revisions of "GSoC Ideas"
link OpenTasks
(Move security audit out of main GSoC ideas list) |
(link OpenTasks) |
||
| Line 103: | Line 103: | ||
Technical contacts: Our IRC channel, our mailing list, or contact [[User:Sev|Eugene Sandulenko]], [[User:DJWillis|John Willis]], [[User:Strangerke|Arnaud Boutonné]] | Technical contacts: Our IRC channel, our mailing list, or contact [[User:Sev|Eugene Sandulenko]], [[User:DJWillis|John Willis]], [[User:Strangerke|Arnaud Boutonné]] | ||
One good place to start if you're looking for new ideas would be our [[TODO]] page (and the other TODO lists linked from there). Again, be sure to talk to us before thinking too much about any idea on | One good place to start if you're looking for new ideas would be our [[TODO]] page (and the other TODO lists linked from there). | ||
Some other ideas (most of which might be incomplete or outdated) can be found on our [[OpenTasks]] page. Again, be sure to talk to us before thinking too much about any idea on these lists, as many things are likely to be outdated or simply wrong. | |||
=== New game engines === | === New game engines === | ||
If you already have reverse engineering experience, you could consider working on one of the external in-development game engines, or even on support for a new game. However, doing this kind of work is very difficult and time-consuming - you would have to convince us that you have the necessary skills to actually be sufficiently productive, probably by demonstrating some actual progress first. | If you already have reverse engineering experience, you could consider working on one of the external in-development game engines, or even on support for a new game. However, doing this kind of work is very difficult and time-consuming - you would have to convince us that you have the necessary skills to actually be sufficiently productive, probably by demonstrating some actual progress first. | ||