SummerOfCodeIdeas
This is a compilation of ideas from ML. Needs to be refined (more detailed description, deliverables, workload estimation?):
Contents
- 1 I want to be one of your Google Summer of Code students, what should I do...
- 2 New (2010) List of Ideas for the Project (Suggestions from the wesnoth developers)
- 3 Old (2009) List of Ideas for the Project (Suggestions from the wesnoth developers)
- 4 Information about our Project
- 5 People to bug on IRC
I want to be one of your Google Summer of Code students, what should I do...
Here is a quick list of things to do to get you started
- Create an account on gna.org
- Create an account on the wesnoth forum, and tell an admin on the IRC channel to mark is as a GSoC Student account (Admins are boucman, Ivanovic, mordante, Shadow_Master, Sirp and Turuk)
- Join the irc channel (#wesnoth-dev on irc.freenode.net) and introduce yourself. We will not give formal interviews, but we will clearly favor people we have learned to know during the selection process (basically communication via IRC is mandatory for our project! it is the main way of "every day communication" for Wesnoth. For the same reason, it's also a good idea to regularly read the IRC logs.).
- Start a wiki page about your idea, add a link on the bottom of this page and add this information on it:
- List your account names (gna, forum, irc nick) so that we can recognize you
- Fill the questionnaire on this page: List of questions to answer
- Detail your idea as much as possible, look at other students pages, and please give milestones and studies you've done
- Add a link to the page at the bottom of this page
- Though not mandatory, it is highly advisable to go to the EasyCoding and NotSoEasyCoding pages and implement one of these ideas (or any idea of similar scope) so we have an idea how you work. Be sure to use your gna account when submitting these patches so we know who it is coming from. You can also implement some features from our feature request database at gna. When you implement something, also list it on your own page with a reference to the patch.
- For working on Wesnoth you have to be able to compile trunk. To do so you should have a look at the page about svn and afterwards compile Wesnoth svn.
- Once you have everything done here and think your idea is okay, go to page at google to submit your application. You have to submit it before April 3rd at 19:00 UTC (12:00 PST) or you have no chance to get in!
New (2010) List of Ideas for the Project (Suggestions from the wesnoth developers)
<<< PLEASE WRITE IDEAS FOR GSOC 2010 HERE >>>
Extend Wesnoth Lua AI support
(proposed by Crab)
Lua AI support was recently added to wesnoth. Expose c++ AI support functions that wesnoth has, to Lua.
Allow to store persistent gameworld information for SP and MP games
(proposed by Crab)
Allow WML authors to store/access persistent data 'in context' of a specific campaign/add-on/group of addons/ group of games. This will allow things like 'achievements' or 'massive multiplayer campaigns' to work.
Old (2009) List of Ideas for the Project (Suggestions from the wesnoth developers)
Here is only a short description of possible Ideas we have, each has a page of its own with a more detailed version on it.
Optimize implementation of WML for memory usage
Based on this idea: [1] optimize WML to minimize its memory usage. High memory usage has been a problem for Wesnoth, and this project will aim to reduce it.
Implement campaign statistics reports on stats.wesnoth.org
Wesnoth has an infrastructure which records details of campaigns that players play into a centralized MySQL database. However, we only have rudimentary reports based on this MySQL database available at this time, at [2].
This project would involve writing a stats reporting web site which would take the data from the MySQL database and produce reports in chart and table form. Campaign designers would be able to use these reports to gather feedback on their campaigns and get ideas for improvements.
A student could largely make their choice of infrastructure for creating the Website -- whether they prefer Python, Perl, Ruby, PHP, etc. This is a great opportunity for someone who doesn't want to dive into hardcore C++ to make a valuable contribution to Wesnoth.
SoC Ideas Stats Server - Full Version of the idea, with detailed information
Extending the Multiplayer server
Our multiplayer community is generally strong and healthy, but we believe its growth is limited by some problems in the interface of the multiplayer lobby.
SoC Ideas Multiplayer server - Full version of the idea, with detailed information
Addon server
Wesnoth has an addon server which offers users to upload user made content (UMC). This allows all other users of Wesnoth to easily download and install this content. The server was originally written for user-made campaigns but contains a lot more types of addons nowadays. Both the server side and the client side need to be improved.
SoC Ideas Addon Server - Full version of the idea, with detailed information
WML validation schemes
Wesnoth uses WML as basic data structure. Over the years this language has evolved and got more complex. At the moment the WML is validated at runtime and in case of a problem the engine stops. With schemes these problems can be validated when loading the WML, making it easier to find problems before running into them.
SoC Ideas Schemes - Full version of the idea, with detailed information
Savegame reorganization
The savegame formats of Wesnoth for single player campaigns and multiplayer differ from each other. And they are processed differently as well. Now there is an additional request coming up: Multiplayer campaigns. The task will be to unify the savegames for all types of scenarios in order to provide a maintainable code again.
SoC Ideas Savegame - Full version of the idea, with detailed information
Other possible ideas to be fleshed out
A MapGenerator rewrite - better scalable for outdoor maps, plus the possibility to define areas (similar to the caverns in the cave generator) etc.
Make your own ideas
If you have your own idea the best thing is to join IRC wesnoth-dev at irc.freenode.net and discuss the idea with the developers there. If the developers think your idea is interesting and like the feature you can start to turn it into a full proposal. Once done discuss it again on IRC so the developers can accept your idea.
Information about our Project
The information we provided google with about our project can be looked up at the site SoC Information for Google.
Also see the DeveloperResources link (from the Project page).
People to bug on IRC
We have prepared a list of people with their "area of competence". This is to give you an idea on which areas those people can be of help for you. Of course you should always just ask in the IRC chan, but those are the most likely ones to answer questions in the respective area. And here is the list: