SummerOfCodeIdeas

From The Battle for Wesnoth Wiki

Template:SoC2013

I want to be one of your Google Summer of Code students, what should I do...

Welcome! Here is a quick list of things to do at this time:

  • MOST IMPORTANT Submit your application to Google till May 3rd.
  • MOST IMPORTANT Join the irc channel (#wesnoth-dev on irc.freenode.net) and talk about your project and your appilication. 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.).
  • VERY IMPORTANT Create the wiki page about your idea (Make a copy of the student proposal page template: SoC2013 Template of Student page):
    • Fill the questionnaire.
    • Detail your idea as much as possible, look at other students pages, and please give timeline, milestones and studies you've done
  • If you haven't done so yet, create an account on gna.org (required for committing later on)
  • If you haven't done so yet, create an account on the wesnoth forum, and tell an admin of the forum or leader of the group on the IRC channel to mark it as a GSoC Student account (admins/group leaders are: Boucman, Crab, fendrin/Fabi, Ivanovic, Mordante/SkeletonCrew, Noy, shadowm/shadowmaster, Sirp/Dave, Soliton)
  • 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. This should give you a good idea what the Wesnoth sourcecode is like and will provide a good start to getting used to our coding style, too. You can also start working on your project and submit patches/prototypes related to it

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

List of Ideas for the Project (Suggestions from wesnoth developers)

NOTE: this list of ideas is automatically generated from the 'description' section of pages in Summer of Code 2013 Idea category. DO NOT TRY TO EDIT THIS LIST BY HAND - IT WON'T WORK. INSTEAD, CREATE A NEW PAGE WITH THE 'Soc Ideas2013 Template' template.
NOTE: to add a student page, create a new page based on copy the student proposal page template: SoC2013 Template of Student page):


Addon Server: Create a new and shiny one

Page for the idea: SoC_Ideas_Addon_Server_2013

Wesnoth has an addon server that originally only hosted extra campaigns, but now also hosts Multiplayer Maps, Factions, Eras and more. Also the amount of hosted addon has increased over the years. The server itself is almost unchanged and can use an upgrade. Performance-wise things are not bad, but it would be nice to store additional meta-information on the server and have a better integration for translations.


There are no submitted student proposals for this idea

AI: Implement a 'total defense' strategy

Page for the idea: SoC Ideas AI Defense Strategies 2013

AI in wesnoth's is good at killing things but is bad at defending. Therefore we are forced to make it attack at 2:1 odds. This is the single biggest limiter of the AI skill at the moment. To solve that, we need to teach the AI to defend.

Suggested skills: C++, knowledge of wesnoth's gameplay (can be learned during the project)

There are no student proposals for this idea

AI: Improve configuration and behavior in mainline campaigns

Page for the idea: SoC Ideas AI in Mainline Campaigns Refactoring_2013

We need to ensure our mainline campaigns are using the new capabilities of the AI engine, and improve AI in them by using behavior scripts implemented in lua and C++ code.

Suggested skills: testing and QA skills, C++, lua (can be learned during the project).

There are no student proposals for this idea

AI: Refactor recruitment algorithm

Page for the idea: SoC_Ideas_AI_Recruitment_2013

We need to refactor existing wesnoth's recruitment algorithm to:

  1. support recruiting with multiple leaders.
  2. support per-leader recruit/recall lists.
  3. support easy limiting of recruitable units.
  4. analyze map terrain better
  5. recruit units that are more useful
  6. improve counter-recruiting strategies.
  7. improve recruiting for AI-playable campaigns where AI has to not spend all the gold.

Most likely, a new implementation would be coded from scratch, taking parts of existing C++ code as a guideline.

Suggested skills: mainly C++, a bit of lua (can be learned during the project)

There are no student proposals for this idea

Game Engine: Improve Multiplayer Campaign Support

Page for the idea: SoC Ideas Multiplayer Campaign Support 2013

We need to make coding multiplayer campaigns as easy as coding single player campaigns, making it possible to use different difficulty levels, save/restore progress, and switch/remove/add players easily.

Suggested skills: C++ coding (the project some hard C++ coding tasks in a large codebase)

There are no student proposals for this idea

Other: Your own ideas

Page for the idea: SoC_Ideas_Your_Own_Ideas_2013

Suggested skills: C++ (depends on the project).

There are no student proposals for this idea

New idea template title

Page for the idea: SoC_Ideas2013_Template

Info that will appear on Summer of Code ideas list.

There are no submitted student proposals for this idea

Student proposals not submitted to google

There are 24 student proposals which were not submitted to google
Arkist Arkist
dragos Dragos/GsoC 2013/AI: Implement a 'total defense' strategy
dragos Dragos/GsoC 2013/AI: Refactor recruitment algorithm
elf11, elf_11, elf__11 Elf11
flix Flixx/GSoC 2013/AI: AI: Refactor recruitment algorithm
GrayS Gray
jleldridge Jleldridge
kelpy Kelpy
MaraJade MaraJade
Nephro, nephNephro SoC2013
perennate Perennate
pjte PJ
PL_kolek, PL_kolek_, PL_kolek__, PL_kolek___ PL kolek
redeian Redeian
rsyh93 Rsyh93
Shofixti

Questionnaire

Please see the following page for the questionnaire: User:Shofixti/GSoC13/QuestionnaireShofixti/GSoC13/Proposal
darius42 SoC2013 Darius42
thunderstruck SoC2013 thunderstruck MP Campaign Support
threkk Threkk
Trademark Trademark/GSoC 2013/Addon Server: Create a new and shiny one
varunv Varunv
Vinipsmaker/GSoC13
YoungWolf YoungWolf
Zazweda, ValentinD Zazweda

Student proposals submitted both to wiki and google

(marked by hand, so if your proposal is not there, don't panic, check google's site instead and ping us, if necessary) All the proposals were submitted to google
Arkist
Dragos/GsoC 2013/AI: Implement a 'total defense' strategy
Dragos/GsoC 2013/AI: Refactor recruitment algorithm
Elf11
Flixx/GSoC 2013/AI: AI: Refactor recruitment algorithm
Gray
Jleldridge
Kelpy
MaraJade
Nephro SoC2013
Perennate
PJ
PL kolek
Redeian
Rsyh93
Shofixti/GSoC13/Proposal
SoC2013 Darius42
SoC2013 thunderstruck MP Campaign Support
Threkk
Trademark/GSoC 2013/Addon Server: Create a new and shiny one
Varunv
Vinipsmaker/GSoC13
YoungWolf
Zazweda

Result from Google acceptance

List of proposals accepted by Google would be available on May 27th

This page was last edited on 26 March 2013, at 20:01.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.