GSoC 2013: Difference between revisions

From PSwiki
Jump to navigation Jump to search
← Older edit
VisualWikitext
 
(29 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Welcome To Google Summer of Code and Atomic Blue! ==
== Welcome To Google Summer of Code and Atomic Blue! ==
http://www.planeshift.it/graphics/banner-gsoc2013.png     [[File:logoColor_square_small.png|100px]]
== We have NOT been selected !! ==
Google announced the list of organizations on 8th April, and we have not been selected for 2013. '''You can still contribute to our project outside GSoC'''. To do so, jump to the section "Where to begin?"


== What is this program? ==
== What is this program? ==


This is the central page for [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 Google GSoC]. Join the fun!
Google Summer of Code is a global program created by Google that offers students stipends to write code for open source projects. Every year interesting and fun Open Source projects get selected by Google to be part of the program as "Mentoring Organizations". Mentoring organization will accept students and propose ideas for students to work on during the summer.


Atomic Blue will present itself as a mentoring organization for [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 Google GSoC 2013]. The applications for mentoring organizations start on March 18th 2013. So stay tuned for more news from us after this date. A selection will follow.
Atomic Blue will present itself as a mentoring organization for GSoC 2013!


Please note this program '''is not''' a part time activity, but requires time and dedication, in particular it will enroll students '''full time''' in a period of 3 months over the summer to produce Open Source code. The project is funded by Google and all students successfully delivering the results will get paid for the work completed over the summer.
Please note this program '''is not''' a part time activity, but requires time and dedication, in particular it will enroll students '''full time''' in a period of 3 months over the summer to produce Open Source code. The project is funded by Google and all students successfully delivering the results will get paid for the work completed over the summer.


You can learn more about the program at [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 GSoc Google page]


=== Where to begin? ===
== Timeline ==
At high level this is the overall timeline of GSoC:
* '''March''': Organizations apply for the program and gets selected by Google. Selected organizations will be announced on '''8th April'''.
* '''April-May''': Students apply for the program on the selected organizations. Deadline '''3rd May'''.
* '''June-September''': Coding period, this is where the fun is!
* '''October''': Wrap up of the program
 
If you want more details on the overall timeline you can check the [http://www.google-melange.com/gsoc/events/google/gsoc2013 google timeline page].
 
In the meantime you can start to learn our project, read our ideas, discuss and meet with us to present yourself! If you want to be selected, getting involved early is a good start.
 
== Where to begin? ==


First you need to know our project better, here are the next steps you should follow:
First you need to know our project better, here are the next steps you should follow:
1) Read our [http://www.planeshift.it PlaneShift web site] and learn more about the engine and game we are building
2) Review the ideas list below to get a feeling of what we want to implement
3) Review the list of skills needed for each idea and see which one fits you best
4) [http://www.planeshift.it/sources.html Download our sources] and start to familiarize with the code. [https://planeshift.svn.sf.net/svnroot/planeshift/trunk/docs/compiling.html Build our server and client] and have it running on your machine.
5) Contact us if you need more information:
* [http://webchat.freenode.net/?channels=planeshift-prospects CHAT]
* [http://forums.hydlaaplaza.com/smf/ FORUMS]
* [mailto:infoATplaneshiftDOTit EMAIL]


== Main Ideas ==
# Read our [http://www.planeshift.it PlaneShift web site] and learn more about the engine and game we are building
# Review the ideas list below to get a feeling of what we want to implement
# Review the list of skills needed for each idea and see which one fits you best
# [http://www.planeshift.it/sources.html Download our sources] and start to familiarize with the code. [https://planeshift.svn.sf.net/svnroot/planeshift/trunk/docs/compiling.html Build our server and client] and have it running on your machine.
# Contact us if you need more information:
#* [http://webchat.freenode.net/?channels=planeshift-prospects CHAT]
#* [http://forums.hydlaaplaza.com/smf/ FORUMS]
#* [mailto:infoATplaneshiftDOTit EMAIL]
 
= Main Ideas =
This section collects ideas we think are large enough to be developed over the GSoC coding period, which lasts 3-4 months. Please note that we are improving the ideas right now, so check back often for updates.
This section collects ideas we think are large enough to be developed over the GSoC coding period, which lasts 3-4 months. Please note that we are improving the ideas right now, so check back often for updates.


If you think you have a good idea to add to the list, please let us know! We are eager to add one project if it's worth it.
If you think you have a good idea to add to the list, please let us know! We are eager to add one project if it's worth it.


=== Dynamic Economy ===
Each idea has:
* '''Summary''': A short description of the idea
* '''Difficulty''': A mix of complexity, breadth and skills required. Don't get scared by it, all tasks listed are doable!
* '''Skills Needed''': These are the prerequisites to start the project. Please do not assume you can learn those during the GSoC.
* '''Mentor''': a developer of Atomic Blue who will follow you during the summer, helping you
* '''Detailed description page'''. Be sure to check also this page for more information on the task.
 
 
== Mechanisms ==
 
{|  border="0"
{|  border="0"
|-
|-
| [[Image:gsoc1.png|left]]
| [[Image:gsoc4.png|left]]
|'''Summary:''' Our virtual world has a vivid economy, with two main active actors: players and shopkeepers. Players can participate to the economy by finding items and selling those in shops or to other players. Shopkeepers (managed by the server) are producing items, repairing existing items. In addition there are other producers/consumers of income like loot, trainers, crafting and more. With so many variables there is a need of a central Economy Manager, which can monitor and tweak the prices based on offer and demand, and differenciate better the shopkeepers depending on their location, near resources, type of city, etc... The main goal of this project is to build such an Economy Manager based on the existing implementation of shops and loot.
|'''Summary:''' Today in PS you don't have enough interaction with the world. For example you cannot open/close a door physically, or pull a lever. The only way we have doors are the ones where you load into another zone, but that's very limiting. Specifically for doors we need to have the possibility to click on a door object and have it actually swing open in 3d, rotating the model on the pivot. This will allow for example to create mechanisms or other fun stuff where players can interact with objects. Can be doors, but also levers, buttons, shafts, secret passages, puzzles. The engine should generically support the "use" command on an object, and it can rotate or translate.  


'''Difficulty:''' Medium
'''Difficulty:''' Medium
Line 37: Line 66:
'''Skills needed:''' For this project C++ knowledge is needed with some knowledge of mysql.  
'''Skills needed:''' For this project C++ knowledge is needed with some knowledge of mysql.  


'''Details:''' Please read the details in this page [[Dynamic Economy]]
'''Mentor:''' Weltall
 
'''[[Mechanisms | Read here for details]]'''
 
|}
|}


=== Tribes ===
== Scriptable entities ==
[[Image:gsoc2.png|left]]
{|  border="0"
'''Summary:''' The main goal of this project is to provide enhance the current Artificial Intelligence of the entities controlled by the server, allowing the server to simulate their movements, reproduction, harvesting, building villages and more. Even if certain areas are ignored by players, the npc population can still grow and evolve there. The base concept is that NPCs should have a concept of a “tribe” they belong to and contribute to the growth of this group. NPCs should be able to find resources, and then (if an intelligent race) build huts, houses and villages, mate, have children, build defenses, grow in wealth and number, attack other tribes, etc. A central Tribe object will define the next needs for the tribe, and dispatch the members to complete certain tasks which are useful to the evolution of the tribe.
|-
|'''Summary:''' This project consists in the creation of new system to allow a player to attach a scripts to a computer controlled entity (NPC). The NPC can be used as a guard for a building or an henchmen, or as the keeper of a player owned shop. Our engine already has a powerful scripting engine, which can be used to scripts dialogues, quests, and general interaction with the NPCs. As the scripting system is completely server side, we actually allow any kind of action, including the creation of new items, generation of coins, training skills, etc... The first part of this new system will be to to sandbox the current scripting engine by isolating only the commands which can be run by a player controlled entity. The second part is to connect this system to guildhouses, chests or player inventories to allow real exchange of items through the NPC.
 
'''Difficulty:''' Medium
 
'''Skills needed:''' For this project C++ knowledge is needed with some knowledge of mysql.
 
'''Mentor:''' Magodra and Talad
 
'''[[Scriptable Entities| Read here for details]]'''
| [[Image:gsoc6.png|left]]
|}
 
== Tribes ==
{|  border="0"
|-
| [[Image:gsoc2.png|left]]
| '''Summary:''' The main goal of this project is to provide enhance the current Artificial Intelligence of the entities controlled by the server, allowing the server to simulate their movements, reproduction, harvesting, building villages and more. Even if certain areas are ignored by players, the npc population can still grow and evolve there. The base concept is that NPCs should have a concept of a “tribe” they belong to and contribute to the growth of this group. NPCs should be able to find resources, and then (if an intelligent race) build huts, houses and villages, mate, have children, build defenses, grow in wealth and number, attack other tribes, etc. A central Tribe object will define the next needs for the tribe, and dispatch the members to complete certain tasks which are useful to the evolution of the tribe.


'''Difficulty:''' Composed of various tasks from medium to high
'''Difficulty:''' Composed of various tasks from medium to high
Line 48: Line 97:
'''Skills needed:''' For this project C++ knowledge is needed.
'''Skills needed:''' For this project C++ knowledge is needed.


'''Details:''' Artificial intelligence for [[Tribes expansion 2012]]
'''Mentor:''' Magodra
 
'''[[Tribes expansion 2013| Read here for details]]'''
|}


=== Statistics ===
== Autogenerated dungeons ==
{|  border="0"
|-
| '''Summary:''' The dungeon generator aims to generate random dungeons using the idea of a "Superblock" which is a 9x9x9 units box with a grid of connection points. This superblock will be used to generate the actual blocks part of the dungeon. With predefined connection points, a set of standard blocks can be used to create the final area by placing one block next to the other and generate a coherent set of tunnels, rooms, and passages. Additional props can be added to the generated area, like for example special locations, loot, chests, doors, etc... This project aims at creating the algorythms and the actual database tables to store the autogenerated areas.


* [[Analysis package]] of data mining data (Medium) and better server reporting (Easy)
'''Difficulty:''' Composed of various tasks from medium to high


=== GUI ===
'''Skills needed:''' For this project C++ knowledge is needed.


* [[Improved UI 2012]] Includes improvements to the Help system, fixes to the interface, conversion to plugin. Enhancement to the Container System, and Crafting of books.
'''Mentor:''' Talad


=== Mechanisms ===
'''[[Autogenerated Dungeons| Read here for details]]'''
| [[Image:gsoc7.png|left]]
|}


* Adding [[Mechanisms]] and more interaction with the world.
== Special volumetric areas ==
{|  border="0"
|-
| [[Image:GsocSwim.png|right]]
|'''Summary:''' The game engine today knows about moving entities in a 3d environment where the main interaction is through collision detection, which allows for example to players to walk firmly on the ground, or buildings to block the way. This project is about defining special volumetric areas, which are not occupied by any 3d object part of the main area geometry. For example we may decide a certain area is made of water, and specific rules apply while an entity is inside the bounding box of that area. The entity may lose his weight and float, a player may play the swim animation, certain animals may die, others live. Other types can be areas made of cold, lava, magic. The new system should allow to define those areas with associated animations and scripts.


=== Hardcoding removal ===
'''Difficulty:''' Medium


* [[Hardcoding removal]]: Involves moving some of the hardcoded skills/stats/rules/mechanics from the code to the database, making the engine more flexible and more maintainable. (easy to hard)
'''Skills needed:''' For this project C++ knowledge is needed with some knowledge of mysql. In addition some mathematical skills are needed to define movement vectors and bounding boxes.


== Other smaller / fragmented tasks ==
'''Mentor:''' Lucubro


This section contains ideas which have not yet been developed into main ideas. We are not sure if one of these can really cover the 3 months period of GSoC and so those are pending review, discussion and expansion to be moved in the previous section.
'''[[Special volumetric areas| Read here for details]]'''
|}


=== Database ===


* Database reconstruction: Optimise database with innodb triggers, rework of tables, new index, scalability and subdivision of data between different servers...(hard)
== Dynamic Economy ==
{|  border="0"
|-
|'''Summary:''' Our virtual world has a vivid economy, with two main active actors: players and shopkeepers. Players can participate to the economy by finding items and selling those in shops or to other players. Shopkeepers (managed by the server) are producing items, repairing existing items. In addition there are other producers/consumers of income like loot, trainers, crafting and more. With so many variables there is a need of a central Economy Manager, which can monitor and tweak the prices based on offer and demand, and differenciate better the shopkeepers depending on their location, near resources, type of city, etc... The main goal of this project is to build such an Economy Manager based on the existing implementation of shops and loot.


=== Networking ===
'''Difficulty:''' Medium


* TCP layer: add a TCP layer so that clients have the option of connecting with TCP instead. TCP can be preferable for people connecting via wireless or high-bandwidth connections, which is increasingly the case. The relatively high latency to PS servers also means the latency benefits of UDP are not as useful. (hard)
'''Skills needed:''' For this project C++ knowledge is needed with some knowledge of mysql.  


* IPV4 TO IPV6: changing the code so it doesn't rely specifically on IPV4 or IPV6, allow to define various listen interfaces either IPV4 and IPV6. Remove network logic which can be left to system libraries. Conversion to plugin.(easy to medium depending on the parts which are picked up)
'''[[Dynamic Economy| Read here for details]]'''


=== Effect Library ===
'''Mentor:''' Talad


* PSEFFECT: conversion to plugin and performance optimizations. Maybe adding support for 2d objects.(medium)
| [[Image:gsoc1.png|right]]
|}


=== Headless Client ===
== Statistics ==
{|  border="0"
|-
| [[Image:gsoc3.png|right]]
|'''Summary:''' A mmorpg database contains millions data rows, at the present time we have thousands of accounts, entities, items, skills and every second a dozens of transactions are executed growing the database.


* Integration testing: Modify the client to have a headless option to allow for easy integration testing and for combat simulation. This can make it much easier to test balance changes. (medium)
All this data is incredible valuable information to us, because we can extract from it player behaviours, economy trends, rate of item creation and destruction, money that gets consumed. We need to build an easy to use web application which reads and presents the results.


=== Server reliability ===
'''Difficulty:''' Easy to Medium


* Unit Testing: Implement a basic unit testing framework for common server commands and actions. (Medium)
'''Skills needed:''' For this project PHP knowledge is needed with some knowledge of mysql.  


=== Mail System ===
'''Mentor:''' Talad


* A way for player and gm to send in game mails to other players also with items "attached"
'''[[Analysis package| Read here for details]]'''
|}


=== Click to move ===


* From the work in crystal space of 2 years ago during GSOC last year we merged a functionality called NAVMESH in our npcclient. It would be nice if it was possible to show these generated navmesh in clients as a debug features (probably enable-able only from config files or compile time) and also make use of them to allow point and click reliable movement, as right now the algorithm is not able to know if it will hit a wall or a deep hole and will go toward those dangers.
== GUI ==
{|  border="0"
|-
|'''Summary:''' The UI in PlaneShift is managed by a library we created called PAWS (PlaneShift Alternate Windowing System). The library is made of C++ classes to define a widget and an associated XML file which describes the layout and formatting. It keeps a separation between the presentation layer and the logic layer. The core library (/src/common/paws) defines basic items such as windows, labels, checkboxes, button, etc.., then the UI game engine (/src/client/gui) defines a set of windows to be used in the client, built by the core pieces. This GSoC project includes improvements to the quick bar, to the help system, enhancement to the Container System, better skin management, new spellcasting widget, overall improvements to windows resizing.


=== Return to login ===
'''Difficulty:''' Easy to Medium


* Add support to return to the login window instead of closing the client entirely.
'''Skills needed:''' For this project C++ knowledge is needed wand some knowledge of XML.  


=== Make the world less static ===
'''Mentor:''' Weltall


* Add support to define or recognise in some way special area: for example water. Apply effects to the camera when inside the area and  activate things like swimming and diving (with control of breath if applicable).
'''[[Improved UI 2013| Read here for details]]'''
* Add support for flying (not globally but only when allowed from the server) and prevent players to get out of bounds through this.
| http://www.atomicblue.org/ui.png
* Add support for boats and flying mounts (this has the prerequisite of the previous entries)
|}
* Add support for things like night vision or other effects depending on current context and activated from the server.


=== Monsters' sounds perception ===
== Other ideas ==


* Implementation of monsters' sound perception. For example a thief that moves close to a monster without making too much noise will be able to attack it first, while a player with no sneaking skills will be heard by the monster and he will be attacked.
You are welcome to propose ideas which are not in the list above, if you do so, we suggest you discuss it first with us, so we can guide you on the feasibility and complexity of implemeting it. You can also check our [[GSoC other ideas|additional ideas]] without documentation.

Latest revision as of 07:13, 9 April 2013

Welcome To Google Summer of Code and Atomic Blue!

banner-gsoc2013.png    


We have NOT been selected !!

Google announced the list of organizations on 8th April, and we have not been selected for 2013. You can still contribute to our project outside GSoC. To do so, jump to the section "Where to begin?"

What is this program?

Google Summer of Code is a global program created by Google that offers students stipends to write code for open source projects. Every year interesting and fun Open Source projects get selected by Google to be part of the program as "Mentoring Organizations". Mentoring organization will accept students and propose ideas for students to work on during the summer.

Atomic Blue will present itself as a mentoring organization for GSoC 2013!

Please note this program is not a part time activity, but requires time and dedication, in particular it will enroll students full time in a period of 3 months over the summer to produce Open Source code. The project is funded by Google and all students successfully delivering the results will get paid for the work completed over the summer.

You can learn more about the program at GSoc Google page

Timeline

At high level this is the overall timeline of GSoC:

  • March: Organizations apply for the program and gets selected by Google. Selected organizations will be announced on 8th April.
  • April-May: Students apply for the program on the selected organizations. Deadline 3rd May.
  • June-September: Coding period, this is where the fun is!
  • October: Wrap up of the program

If you want more details on the overall timeline you can check the google timeline page.

In the meantime you can start to learn our project, read our ideas, discuss and meet with us to present yourself! If you want to be selected, getting involved early is a good start.

Where to begin?

First you need to know our project better, here are the next steps you should follow:

  1. Read our PlaneShift web site and learn more about the engine and game we are building
  2. Review the ideas list below to get a feeling of what we want to implement
  3. Review the list of skills needed for each idea and see which one fits you best
  4. Download our sources and start to familiarize with the code. Build our server and client and have it running on your machine.
  5. Contact us if you need more information:

Main Ideas

This section collects ideas we think are large enough to be developed over the GSoC coding period, which lasts 3-4 months. Please note that we are improving the ideas right now, so check back often for updates.

If you think you have a good idea to add to the list, please let us know! We are eager to add one project if it's worth it.

Each idea has:

  • Summary: A short description of the idea
  • Difficulty: A mix of complexity, breadth and skills required. Don't get scared by it, all tasks listed are doable!
  • Skills Needed: These are the prerequisites to start the project. Please do not assume you can learn those during the GSoC.
  • Mentor: a developer of Atomic Blue who will follow you during the summer, helping you
  • Detailed description page. Be sure to check also this page for more information on the task.


Mechanisms

 Summary: Today in PS you don't have enough interaction with the world. For example you cannot open/close a door physically, or pull a lever. The only way we have doors are the ones where you load into another zone, but that's very limiting. Specifically for doors we need to have the possibility to click on a door object and have it actually swing open in 3d, rotating the model on the pivot. This will allow for example to create mechanisms or other fun stuff where players can interact with objects. Can be doors, but also levers, buttons, shafts, secret passages, puzzles. The engine should generically support the "use" command on an object, and it can rotate or translate.

Difficulty: Medium

Skills needed: For this project C++ knowledge is needed with some knowledge of mysql.

Mentor: Weltall

Read here for details

Scriptable entities

Summary: This project consists in the creation of new system to allow a player to attach a scripts to a computer controlled entity (NPC). The NPC can be used as a guard for a building or an henchmen, or as the keeper of a player owned shop. Our engine already has a powerful scripting engine, which can be used to scripts dialogues, quests, and general interaction with the NPCs. As the scripting system is completely server side, we actually allow any kind of action, including the creation of new items, generation of coins, training skills, etc... The first part of this new system will be to to sandbox the current scripting engine by isolating only the commands which can be run by a player controlled entity. The second part is to connect this system to guildhouses, chests or player inventories to allow real exchange of items through the NPC.

Difficulty: Medium

Skills needed: For this project C++ knowledge is needed with some knowledge of mysql.

Mentor: Magodra and Talad

Read here for details

Tribes

 Summary: The main goal of this project is to provide enhance the current Artificial Intelligence of the entities controlled by the server, allowing the server to simulate their movements, reproduction, harvesting, building villages and more. Even if certain areas are ignored by players, the npc population can still grow and evolve there. The base concept is that NPCs should have a concept of a “tribe” they belong to and contribute to the growth of this group. NPCs should be able to find resources, and then (if an intelligent race) build huts, houses and villages, mate, have children, build defenses, grow in wealth and number, attack other tribes, etc. A central Tribe object will define the next needs for the tribe, and dispatch the members to complete certain tasks which are useful to the evolution of the tribe.

Difficulty: Composed of various tasks from medium to high

Skills needed: For this project C++ knowledge is needed.

Mentor: Magodra

Read here for details

Autogenerated dungeons

Summary: The dungeon generator aims to generate random dungeons using the idea of a "Superblock" which is a 9x9x9 units box with a grid of connection points. This superblock will be used to generate the actual blocks part of the dungeon. With predefined connection points, a set of standard blocks can be used to create the final area by placing one block next to the other and generate a coherent set of tunnels, rooms, and passages. Additional props can be added to the generated area, like for example special locations, loot, chests, doors, etc... This project aims at creating the algorythms and the actual database tables to store the autogenerated areas.

Difficulty: Composed of various tasks from medium to high

Skills needed: For this project C++ knowledge is needed.

Mentor: Talad

Read here for details

Special volumetric areas

 Summary: The game engine today knows about moving entities in a 3d environment where the main interaction is through collision detection, which allows for example to players to walk firmly on the ground, or buildings to block the way. This project is about defining special volumetric areas, which are not occupied by any 3d object part of the main area geometry. For example we may decide a certain area is made of water, and specific rules apply while an entity is inside the bounding box of that area. The entity may lose his weight and float, a player may play the swim animation, certain animals may die, others live. Other types can be areas made of cold, lava, magic. The new system should allow to define those areas with associated animations and scripts.

Difficulty: Medium

Skills needed: For this project C++ knowledge is needed with some knowledge of mysql. In addition some mathematical skills are needed to define movement vectors and bounding boxes.

Mentor: Lucubro

Read here for details


Dynamic Economy

Summary: Our virtual world has a vivid economy, with two main active actors: players and shopkeepers. Players can participate to the economy by finding items and selling those in shops or to other players. Shopkeepers (managed by the server) are producing items, repairing existing items. In addition there are other producers/consumers of income like loot, trainers, crafting and more. With so many variables there is a need of a central Economy Manager, which can monitor and tweak the prices based on offer and demand, and differenciate better the shopkeepers depending on their location, near resources, type of city, etc... The main goal of this project is to build such an Economy Manager based on the existing implementation of shops and loot.

Difficulty: Medium

Skills needed: For this project C++ knowledge is needed with some knowledge of mysql.

Read here for details

Mentor: Talad

Statistics

 Summary: A mmorpg database contains millions data rows, at the present time we have thousands of accounts, entities, items, skills and every second a dozens of transactions are executed growing the database.

All this data is incredible valuable information to us, because we can extract from it player behaviours, economy trends, rate of item creation and destruction, money that gets consumed. We need to build an easy to use web application which reads and presents the results.

Difficulty: Easy to Medium

Skills needed: For this project PHP knowledge is needed with some knowledge of mysql.

Mentor: Talad

Read here for details


GUI

Summary: The UI in PlaneShift is managed by a library we created called PAWS (PlaneShift Alternate Windowing System). The library is made of C++ classes to define a widget and an associated XML file which describes the layout and formatting. It keeps a separation between the presentation layer and the logic layer. The core library (/src/common/paws) defines basic items such as windows, labels, checkboxes, button, etc.., then the UI game engine (/src/client/gui) defines a set of windows to be used in the client, built by the core pieces. This GSoC project includes improvements to the quick bar, to the help system, enhancement to the Container System, better skin management, new spellcasting widget, overall improvements to windows resizing.

Difficulty: Easy to Medium

Skills needed: For this project C++ knowledge is needed wand some knowledge of XML.

Mentor: Weltall

Read here for details

ui.png

Other ideas

You are welcome to propose ideas which are not in the list above, if you do so, we suggest you discuss it first with us, so we can guide you on the feasibility and complexity of implemeting it. You can also check our additional ideas without documentation.

Retrieved from "https://planeshift.top-ix.org//pswiki/index.php?title=GSoC_2013&oldid=10163"