GSoC 2011

From PSwiki
Jump to navigation Jump to search

Welcome To Google Summer of Code and Atomic Blue!

This is the central page for Google GSoC. Join the fun!

Registering and signing in

The registration for the students is CLOSED ! The final list of students for this year has been COMPLETED! If you are unhappy about that, you can click here.

What to do if you have not been selected

If you want to have more details on why you were not selected please connect to IRC and speak with us.

Second you can still work with us outside of GSoC! We are always seeking new talented contributors. In case you want to contribute to PlaneShift outside the GSoC contact us in IRC.

Meanwhile: Download our sources and start to familiarize with the code. Build our server and client and have it running on your machine.

Next steps

April 9-April 18: We will run a more detailed set of interviews during this period based on our needs to understand better your capabilities and your profile. This will allow us to know better the students and to make the final selection, which will be announced on the 25th.

April 25: Accepted student proposals announced on the Google Summer of Code 2011 site.

April 26 - August 22: Finally you can start working on the project! August 22 is the last day of work on the code.

For more details on the overall timeline please read this page.

Main Ideas

This section collects ideas we think are large enough to be developed over a period of 3 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.

Dynamic Economy

  • Implementation of an Economy Manager to allow a more Dynamic Economy (medium)

Tribes

  • Artificial intelligence for Tribes expansion (composed of various tasks from medium to high)

Statistics

  • Analysis package of data mining data (Medium) and better server reporting (Easy)

GUI

  • Improved UI 2011 Includes improvements to the Help system, fixes to the interface, conversion to plugin. Enhancement to the Container System, and Crafting of books.

Sound System

  • Sound System . Improve the sound manager, make it more flexible and allow association of sounds to in game events, scripts, monsters actions.

Hardcoding removal

  • 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)

Combat enhancements

  • Combat enhancements: The objective of this idea is to make combat more interactive and smoother, to add special abilities and make it more fun to play.

Other smaller / fragmented tasks

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.


Database

  • Database reconstruction: Optimise database with innodb triggers, rework of tables, new index, scalability and subdivision of data between different servers...(hard)

Networking

  • 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)
  • 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)

Effect Library

  • PSEFFECT: conversion to plugin and performance optimizations. Maybe adding support for 2d objects.(medium)

Headless Client

  • 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)

Server reliability

  • Unit Testing: Implement a basic unit testing framework for common server commands and actions. (Medium)


Weekly progress reports

Here we post the GSoC weekly reports for every student.