The Battle for Wesnoth Wiki - User contributions [en]

SummerOfCodeIdeas

2009-04-03T05:40:46Z

Rohita: /* Implement campaign statistics reports on stats.wesnoth.org */

This is a compilation of ideas from ML. Needs to be refined (more detailed description, deliverables, workload estimation?):

== 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 [http://wesnoth.debian.net/?C=M;O=A 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: [[SoC_Information_for_Google#Does_your_organization_have_an_application_template_you_would_like_to_see_students_use.3F_If_so.2C_please_provide_it_now.| 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 [[WesnothSVN|page about svn]] and afterwards [[CompilingWesnoth|compile Wesnoth svn]].

* Once you have everything done here and think your idea is okay, go to [http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants 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!

== 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: [http://dave.wesnoth.org/?p=9] 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 [http://stats.wesnoth.org].

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

=== Write a primitive library for Formula AI ===

Wesnoth has always had a simple C++ based AI. David (our lead developer) has been working on a simple language to write AI in Wesnoth: [[FormulaAI]]

The Wesnoth AI is used as an opponent in most campaigns, and as such is an important piece of code for the Wesnoth project. Unfortunately, because the skills required to understand and modify it are rather arcane, it is also one of the most neglected parts of the Wesnoth code. This is a place where a lot of research and useful work could be done. But keep in mind that [[WhyWritingAWesnothAIIsHard|writing an AI for Wesnoth is difficult]].

Writing a whole AI is so complicated that we believe it can't be done in a single Summer of code. All proposals should keep that in mind and try to identify an interesting subset that would be workable in the limited time of a summer of code

[[SoC Ideas FormulaAI]] - 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:

[[SoC People to bug on IRC]]

== GSoC Student pages ==

Please add a link to your wiki page below

==== AI ====

[[SummerOfCodeProposal_Velory| Velory - SoC Proposal]]

[[SummerOfCodeProposal_AI_Improvement_Crab| Crab - SoC Proposal - AI Improvement]]

[[SummerOfCodeProposal_Sparksteel | Sparksteel - Improving the AI engine design]]

[[FormulaAISoC2009Dragonking | Dragonking - Improving the formula AI ]]

[[GSoC_Proposal_-_Position_Evaluation | henning - Position Evaluation ]]

[[GSoC_Proposal_Evolutionary_AI | heineckm - Evolutionary AI]]

==== Savegame reorganization ====

[[SummerOfCodeProposal_Euschn | Euschn - Savegame reorganization]]

[[SummerOfCodeProposal_lmg| lmg - Savegame reorganization]]

[[SummerOfCodeProposal_grantwu| grantwu - Savegame reorganization]]

==== Extending the Multiplayer server ====

[[SummerOfCodeProposal_rubend | rubend - Extending the Multiplayer server]]

[[MP Server Ilor | Ilor - Extending the Multiplayer server]]

==== Addon server ====

[[SummerOfCodeProposal_Ryochan7| Ryochan7 - Addon server]]

[[SummerOfCodeProposal_iyonius| iyonius - Addon server]]

==== Optimize implementation of WML for memory usage ====

[[SummerOfCodeProposal_res| res - Optimize implementation of WML for memory usage ]]

[[SummerOfCodeProposal_jdmunro| jdmunro - Optimize implementation of WML for memory usage ]]

[[SummerOfCodeProposal_Ryanc| ryanc - Optimize implementation of WML for memory usage ]]

==== Implement campaign statistics reports on stats.wesnoth.org ====

[[SummerOfCodeProposal_Elbin| Elbin - New campaign statistics page]]

[[SummerOfCodeProposal_Munk| Munk - New campaign stats page]]

[[SummerOfCodeProposal_carlestyle| carlestyle - New campaign stats page]]

[[SummerOfCodeProposal_nerwa| NeRwa - New campaign stats page]]

[[SummerOfCodeProposal_mrfinch| mrfinch - New Campaign Statistics Page]]

[[SummerOfCodeProposal_corn| corn - New Campaign Statistics Page]]

[[SummerOfCodeProposal_csaunders | csaunders - SoC Proposal - Stats Server]]

[[SummerOfCodeProposal_rohita | Rohita - New campaign stats page ]]

[[Category:Summer of Code|*]]

SummerOfCodeProposal rohita

2009-04-03T05:37:03Z

Rohita: New page: 1)Basics I am Rohita Hemachandra, a 3rd year undergraduate student from university of Moratuwa, Sri Lanka, studying for a BSc in Information technology. I was interested in part...

1)Basics
I am Rohita Hemachandra, a 3rd year undergraduate student from university of Moratuwa, Sri
Lanka, studying for a BSc in Information technology. I was interested in participating for Google
Summer of Code 2009 because I would be able to contribute to an open source project in my free
time and get an experience on how collaborative software projects are been developed. I was a keen
follower of Google Summer of Code and this is my third time in applying for the program.

Email: rohita85@gmail.com
Freenode nick: Rohita
Wesnoth forum ID: rohita85

2)Experience
I have had an internship at WSO2 Inc [1], an open source SOA middle ware provider for 6months.
I mainly contributed to WSO2 Mashup [2], a javascript web service engine. I worked in a project to
implement gadget a server to WSO2 Mashup. Also I worked in WSO2 ESB [3], an open source Enterprise
Service Bus (ESB). I implemented an Ajax based monitor to monitor and debug SOAP messages gone
through the WSO2 ESB server.

I have worked with GTS [4], a software solution provider as a mobile application developer. I
contributed mainly to Aba Hatana, a java mobile game developed as the official mobile game of the
popular Sri Lanka film ABA [5]. I also developed a free SMS sending mobile application for Sri
Lanka [6].

This is the third time I am applying for Google Summer of Code. On the previous two occasions
I could not get selected to the program. The competition in the mentoring organizations I applied
was tough but on the process I had many valuable experiences about the program.

I am a big fan of strategy based games since my childhood. The first to get on my attention was
Age of Empires 2 and I found myself playing it many hours a day until I finished it successfully.
Then on I moved onto more strategy games such as Command and Conquer Red Alert, Command and
Conquer Generals, and Rome.

I am new to the game Battle for Wesnoth. What I found interesting in the game is the open
environment where we can also get involved in the development process rather than only on playing.
I am playing Battle for Wesnoth these days in the single player mode.

3) My mother tongue is Sinhala and also I am fluent in speaking and writing in English. In my
internship at WSO2 I got experience on how to work in a collaborative environment. I communicated
often with the community to get their feedbacks and requirements. I take advices as an
encouragement and consider giving clear advices as necessary when the need arises. I believe that
criticism can be either useful or useless, and try to get encouraged by the positive ones while
ignoring what I consider the negative ones.

4) I chose, Implement campaign statistics reports on stats.wesnoth.org as the project to
participate in Summer of Code. I chose Battle of Wesnoth as the possible mentoring organization
because I am very interested in strategy based games and idea of an open source strategy game was
very interesting to me. I chose this specific project as I have many experiences on charting and
reporting projects. I have previous experiences on Eclipse Bert [7], Jasper , Google chart API
and on MySql. I felt like this is the perfect project idea for me to participate in this year’s
Summer of Code program.

I will be using Google chart API and Open Flash Chart [8] as the main charting components.
Both of them are very good charting components that facilitate in creating dynamic and
interactive charts and reports. I will be using php to query the stat database of Wesnoth and
access and call charting components.

Once the project is successfully completed rather than just been a statistics viewer the
project should aid campaign designers in decision making. A campaign decider should b able to
decide whether or not a campaign is successful, what are most successful scenarios in a campaign,
what the scenarios that prevent a player from progressing, what are the scenarios that players
tend to play over and over, what are the most effective units and special units in a given
scenario, whether the popularity of campaign is on the rise or declining, etc.

After the project is completed successfully I hope to provide the following charts and reports
to campaign designers.
1) Users vs Campaigns graphs. For a selected duration, users would be displayed against selected
campaigns in a line graph.
2) Reports on the number of players who played campaigns and the success rates. A bar graph
would be provided with number defeats, victories and total games for each campaign.
3) The user participation in a given campaign over time. A Line graph depicting the how the
player participation is changing over time for a given campaign.
4) Graph showing the number of victories and defeats in a campaign over time.
5) Number of victories and defeats in scenarios in a given campaign.
6) One particular user’s use of units and special units in a scenario and the result and the
time duration.User would be able decide what is the best combination of units and special
units for given scenario.
7) User successfulness of a given campaign.The campaign designer would able to decide the
success rates of users, whether new users are finding it easily to succeed and whether
experienced users succeed more than new users.
8) Campaign rating system. I would be introducing an algorithm to decide the best campaigns.
Statistics on success rates, adaptability of new users, number of users who play again and
again and the number of participants would be used in the algorithm. More ideas on this
would be collected from the Battle of Wesnoth community. The algorithm would be clearly
stated in the reports.
9) An option would be provided to the user to select the associating difficulty level of
statistics. User would be able to select overall, easy, normal or difficult and view graphs
and reports with statistics of the selected difficulty level.

I am hoping to get valuable experience oh how collaborative open source projects work and what
programming techniques are used in strategy games by contributing to this project. I would also
like to keep contributing to the reporting and statistics components in Battle for Wesnoth
project and be a part of the development team.

Project Schedule

Community bonding period – Get ideas from campaign creators and wesnoth community. Studying
wesnoth statistics database. Studying more advanced features of charting and reporting technologies.

The GSOC program spans 12 weeks, so I intend to utilize it as follows (milestone reached at the
end of week):

Week 1: Designing the application. The charts and reports would be designed. The operations allowed
for users would be decided and the navigation of the application would be designed.
Week 2: Designing and creating the UI.
Week 6: Implementing real application. The charts, reports and the navigation of the application
would be implemented.
Week 8: Get feedbacks and modifying the application to be robust and interactive.
Week 10: Testing application and fixing bugs.
Week 11: Documentation of the project to make sure the continuation of the project.

5)Practical Considerations
I have previously worked in subversion based projects so I have very good experience on how
to use subversion. I am not familiar with C++ but I have good experiences on Java and Python as
desktop programming languages. I use Eclipse and jidea as development tools and my favorite build
tool is Maven2. I am mostly online during the day. I would be available on IRC more often through
10.00 AM to 6.00 PM UTC. I would be available through phone in case of emergency; my phone number
is +94715188005.

References:
[1] www.wso2.com
[2] http://wso2.org/projects/mashup
[3] http://wso2.org/projects/esb/java
[4]http://www.gtslk.com/
[5] http://www.abahatana.com/
[6] http://www.dms.lk/
[7] http://www.eclipse.org/birt/phoenix
[8] http://teethgrinder.co.uk/open-flash-chart/gallery-pie.php

User:Rohita

2009-04-03T05:20:04Z

Rohita: Removing all content from page

User:Rohita

2009-04-03T05:14:14Z

Rohita:

1)Basics

I am Rohita Hemachandra, a 3rd year undergraduate student from university of Moratuwa,
Sri Lanka, studying for a BSc in Information technology. I was interested in participating for
Google Summer of Code 2009 because I would be able to contribute to an open source project in my
free time and get an experience on how collaborative software projects are been developed. I was a
keen follower of Google Summer of Code and this is my third time in applying for the program.

Email: rohita85@gmail.com
Freenode nick: Rohita
Wesnoth forum ID: rohita85

2)Experience

I have had an internship at WSO2 Inc [1], an open source SOA middle ware provider for 6months.
I mainly contributed to WSO2 Mashup [2], a javascript web service engine. I worked in a project to
implement gadget a server to WSO2 Mashup. Also I worked in WSO2 ESB [3], an open source Enterprise
Service Bus (ESB). I implemented an Ajax based monitor to monitor and debug SOAP messages gone
through the WSO2 ESB server.

I have worked with GTS [4], a software solution provider as a mobile application developer.
I contributed mainly to Aba Hatana, a java mobile game developed as the official mobile game of the
popular Sri Lanka film ABA [5]. I also developed a free SMS sending mobile application for
Sri Lanka [6].

This is the third time I am applying for Google Summer of Code. On the previous two occasions I
could not get selected to the program. The competition in the mentoring organizations I applied was
tough but on the process I had many valuable experiences about the program.

I am a big fan of strategy based games since my childhood. The first to get on my attention
was Age of Empires 2 and I found myself playing it many hours a day until I finished it
successfully. Then on I moved onto more strategy games such as Command and Conquer Red Alert,
Command and Conquer Generals, and Rome.

I am new to the game Battle for Wesnoth. What I found interesting in the game is the open
environment where we can also get involved in the development process rather than only on playing.
I am playing Battle for Wesnoth these days in the single player mode.

3) My mother tongue is Sinhala and also I am fluent in speaking and writing in English. In my
internship at WSO2 I got experience on how to work in a collaborative environment. I
communicated often with the community to get their feedbacks and requirements. I take advices as
an encouragement and consider giving clear advices as necessary when the need arises. I believe
that criticism can be either useful or useless, and try to get encouraged by the positive ones
while ignoring what I consider the negative ones.

4) I chose, Implement campaign statistics reports on stats.wesnoth.org as the project to
participate in Summer of Code. I chose Battle of Wesnoth as the possible mentoring organization
because I am very interested in strategy based games and idea of an open source strategy game was
very interesting to me. I chose this specific project as I have many experiences on charting and
reporting projects. I have previous experiences on Eclipse Bert [7], Jasper , Google chart API
and on MySql. I felt like this is the perfect project idea for me to participate in this year’s
Summer of Code program.

I will be using Google chart API and Open Flash Chart [8] as the main charting components.
Both of them are very good charting components that facilitate in creating dynamic and interactive
charts and reports. I will be using php to query the stat database of Wesnoth and access and
call charting components.

Once the project is successfully completed rather than just been a statistics viewer the
project should aid campaign designers in decision making. A campaign decider should b able to
decide whether or not a campaign is successful, what are most successful scenarios in a campaign,
what the scenarios that prevent a player from progressing, what are the scenarios that players
tend to play over and over, what are the most effective units and special units in a given
scenario, whether the popularity of campaign is on the rise or declining, etc.

After the project is completed successfully I hope to provide the following charts and reports
to campaign designers.

1) Users vs Campaigns graphs. For a selected duration, users would be displayed against
selected campaigns in a line graph.
2) Reports on the number of players who played campaigns and the success rates. A bar graph
would be provided with number defeats, victories and total games for each campaign.
3) The user participation in a given campaign over time. A Line graph depicting the how the
player participation is changing over time for a given campaign.
4) Graph showing the number of victories and defeats in a campaign over time.
5) Number of victories and defeats in scenarios in a given campaign.
6) One particular user’s use of units and special units in a scenario and the result and the
time duration.User would be able decide what is the best combination of units and special
units for given scenario.
7) User successfulness of a given campaign.The campaign designer would able to decide the
success rates of users, whether new users are finding it easily to succeed and whether
experienced users succeed more than new users.
8) Campaign rating system. I would be introducing an algorithm to decide the best campaigns.
Statistics on success rates, adaptability of new users, number of users who play again and
again and the number of participants would be used in the algorithm. More ideas on this would
be collected from the Battle of Wesnoth community. The algorithm would be clearly stated in
the reports.
9) An option would be provided to the user to select the associating difficulty level of
statistics. User would be able to select overall, easy, normal or difficult and view graphs
and reports with statistics of the selected difficulty level.

I am hoping to get valuable experience oh how collaborative open source projects work and what
programming techniques are used in strategy games by contributing to this project. I would also like
to keep contributing to the reporting and statistics components in Battle for Wesnoth project and be
a part of the development team.

Project Schedule

Community bonding period – Get ideas from campaign creators and wesnoth community. Studying wesnoth
statistics database. Studying more advanced features of charting and reporting technologies.

The GSOC program spans 12 weeks, so I intend to utilize it as follows (milestone reached at the end
of week):

Week 1: Designing the application. The charts and reports would be designed. The operations allowed
for users would be decided and the navigation of the application would be designed.

Week 2: Designing and creating the UI.

Week 6: Implementing real application. The charts, reports and the navigation of the application
would be implemented.
Week 8: Get feedbacks and modifying the application to be robust and interactive.

Week 10: Testing application and fixing bugs.

Week 11: Documentation of the project to make sure the continuation of the project.

5)Practical Considerations
I have previously worked in subversion based projects so I have very good experience on how to
use subversion. I am not familiar with C++ but I have good experiences on Java and Python as
desktop programming languages. I use Eclipse and jidea as development tools and my favorite build
tool is Maven2. I am mostly online during the day. I would be available on IRC more often through
10.00 AM to 6.00 PM UTC. I would be available through phone in case of emergency; my phone number
is +94715188005.

References:
[1] www.wso2.com
[2] http://wso2.org/projects/mashup
[3] http://wso2.org/projects/esb/java
[4]http://www.gtslk.com/
[5] http://www.abahatana.com/
[6] http://www.dms.lk/
[7] http://www.eclipse.org/birt/phoenix
[8] http://teethgrinder.co.uk/open-flash-chart/gallery-pie.php

User:Rohita

2009-04-03T05:02:38Z

Rohita: New page: 1)Basics I am Rohita Hemachandra, a 3rd year undergraduate student from university of Moratuwa, Sri Lanka, studying for a BSc in Information technology. I was interested in participat...

1)Basics
I am Rohita Hemachandra, a 3rd year undergraduate student from university of Moratuwa, Sri Lanka, studying for a BSc in Information technology. I was interested in participating for Google Summer of Code 2009 because I would be able to contribute to an open source project in my free time and get an experience on how collaborative software projects are been developed. I was a keen follower of Google Summer of Code and this is my third time in applying for the program.

Email: rohita85@gmail.com
Freenode nick: Rohita
Wesnoth forum ID: rohita85

2)Experience
I have had an internship at WSO2 Inc [1], an open source SOA middle ware provider for 6months. I mainly contributed to WSO2 Mashup [2], a javascript web service engine. I worked in a project to implement gadget a server to WSO2 Mashup. Also I worked in WSO2 ESB [3], an open source Enterprise Service Bus (ESB). I implemented an Ajax based monitor to monitor and debug SOAP messages gone through the WSO2 ESB server.

I have worked with GTS [4], a software solution provider as a mobile application developer. I contributed mainly to Aba Hatana, a java mobile game developed as the official mobile game of the popular Sri Lanka film ABA [5]. I also developed a free SMS sending mobile application for Sri Lanka [6].

This is the third time I am applying for Google Summer of Code. On the previous two occasions I could not get selected to the program. The competition in the mentoring organizations I applied was tough but on the process I had many valuable experiences about the program.

I am a big fan of strategy based games since my childhood. The first to get on my attention was Age of Empires 2 and I found myself playing it many hours a day until I finished it successfully. Then on I moved onto more strategy games such as Command and Conquer Red Alert, Command and Conquer Generals, and Rome.

I am new to the game Battle for Wesnoth. What I found interesting in the game is the open environment where we can also get involved in the development process rather than only on playing. I am playing Battle for Wesnoth these days in the single player mode.

3) My mother tongue is Sinhala and also I am fluent in speaking and writing in English. In my internship at WSO2 I got experience on how to work in a collaborative environment. I communicated often with the community to get their feedbacks and requirements. I take advices as an encouragement and consider giving clear advices as necessary when the need arises. I believe that criticism can be either useful or useless, and try to get encouraged by the positive ones while ignoring what I consider the negative ones.

4) I chose, Implement campaign statistics reports on stats.wesnoth.org as the project to participate in Summer of Code. I chose Battle of Wesnoth as the possible mentoring organization because I am very interested in strategy based games and idea of an open source strategy game was very interesting to me. I chose this specific project as I have many experiences on charting and reporting projects. I have previous experiences on Eclipse Bert [7], Jasper , Google chart API and on MySql. I felt like this is the perfect project idea for me to participate in this year’s Summer of Code program.

I will be using Google chart API and Open Flash Chart [8] as the main charting components. Both of them are very good charting components that facilitate in creating dynamic and interactive charts and reports. I will be using php to query the stat database of Wesnoth and access and call charting components.

Once the project is successfully completed rather than just been a statistics viewer the project should aid campaign designers in decision making. A campaign decider should b able to decide whether or not a campaign is successful, what are most successful scenarios in a campaign, what the scenarios that prevent a player from progressing, what are the scenarios that players tend to play over and over, what are the most effective units and special units in a given scenario, whether the popularity of campaign is on the rise or declining, etc.

After the project is completed successfully I hope to provide the following charts and reports to campaign designers.
1) Users vs Campaigns graphs. For a selected duration, users would be displayed against selected campaigns in a line graph.
2) Reports on the number of players who played campaigns and the success rates. A bar graph would be provided with number defeats, victories and total games for each campaign.
3) The user participation in a given campaign over time. A Line graph depicting the how the player participation is changing over time for a given campaign.
4) Graph showing the number of victories and defeats in a campaign over time.
5) Number of victories and defeats in scenarios in a given campaign.
6) One particular user’s use of units and special units in a scenario and the result and the time duration.
User would be able decide what is the best combination of units and special units for given scenario.
7) User successfulness of a given campaign.
The campaign designer would able to decide the success rates of users, whether new users are finding it easily to succeed and whether experienced users succeed more than new users.
8) Campaign rating system. I would be introducing an algorithm to decide the best campaigns. Statistics on success rates, adaptability of new users, number of users who play again and again and the number of participants would be used in the algorithm. More ideas on this would be collected from the Battle of Wesnoth community. The algorithm would be clearly stated in the reports.
9) An option would be provided to the user to select the associating difficulty level of statistics. User would be able to select overall, easy, normal or difficult and view graphs and reports with statistics of the selected difficulty level.

I am hoping to get valuable experience oh how collaborative open source projects work and what programming techniques are used in strategy games by contributing to this project. I would also like to keep contributing to the reporting and statistics components in Battle for Wesnoth project and be a part of the development team.

Project Schedule

Community bonding period – Get ideas from campaign creators and wesnoth community. Studying wesnoth statistics database. Studying more advanced features of charting and reporting technologies.

The GSOC program spans 12 weeks, so I intend to utilize it as follows (milestone reached at the end of week):

Week 1: Designing the application. The charts and reports would be designed. The operations allowed for users would be decided and the navigation of the application would be designed.
Week 2: Designing and creating the UI.
Week 6: Implementing real application. The charts, reports and the navigation of the application would be implemented.
Week 8: Get feedbacks and modifying the application to be robust and interactive.
Week 10: Testing application and fixing bugs.
Week 11: Documentation of the project to make sure the continuation of the project.

5) Practical Considerations
I have previously worked in subversion based projects so I have very good experience on how to use subversion. I am not familiar with C++ but I have good experiences on Java and Python as desktop programming languages. I use Eclipse and jidea as development tools and my favorite build tool is Maven2. I am mostly online during the day. I would be available on IRC more often through 10.00 AM to 6.00 PM UTC. I would be available through phone in case of emergency; my phone number is +94715188005.

References:
[1] www.wso2.com
[2] http://wso2.org/projects/mashup
[3] http://wso2.org/projects/esb/java
[4]http://www.gtslk.com/
[5] http://www.abahatana.com/
[6] http://www.dms.lk/
[7] http://www.eclipse.org/birt/phoenix
[8] http://teethgrinder.co.uk/open-flash-chart/gallery-pie.php