This Week:

For this post, we will consider “This week” as since the beginning of my acceptance into the Google Summer of Code for Thousand Parsec.  In this time, I have completed the following tasks:

Become familiar with Thousand Parsec framework

I have gone over much of the framework.  Since most of my work will be done on tpserver-cpp, I have studied this the most.  I think that I have a good idea of what is going on throughout the c++ server and I don’t believe that there will be any issues going forward with development on this.

Study various rulesets (especially Minisec)

Studying the already-implemented rulesets has given me an idea of what needs to be implemented to have a working ruleset.

Read Ruleset development with tpserver-cpp vigirously

This document has been of great use for understanding what needs to be implemented to have a running ruleset.  During the GSoC period I hope to have my own contributions to it.  This document helps to further the information gained by going over the Minisec ruleset.

Read entire implementation of MTSec Ruleset

While creating my MTSec Initial Report, I read the entire code base for MTSec.  This has given me a good understanding of what is going on and what I will need to implement in the future.  My report outlines the various methods and hooks that I have at my disposal during devlopment of the MTSec ruleset.

Next Week:

Unfortunately, the next week will be an incredibly tough one for personal reasons.  I will be moving into a new place during the next week and this will require large periods of my time.  Also, I am not 100% sure that my internet connection will be ready for the date that I move in.  During this time I will have internet access at my old home, so I will try to sneak back into there to do as much work as possible.

My goal for this week is to clean up the mtsec.cpp file.  I believe that this file is currently far too long and it implements various ship components with different names from the specification.  Once this has been fixed I also plan to implement the various components of a ship.  This weeks work will build toward my first milestone: the creation of ships that include all of the components outlined in the specification.

I was asked by Aaron Mavrinac to write a report about what exactly MTSec currently does in the code – summary of what the standard hooks are doing, list of orders, list of objects, etc.  For this report I focused mainly on the code itself, sort of the MTSec API as it stands now.  This means that I have read all of the MTSec code already and have a good idea of what is happening within it.  I plan to create a wiki page within the Thousand Parsec Wiki for others to be able to update my work as they see fit.  Feel free to read my report on the MTSec game module source.
(more…)

I have officially started my work today for Thousand Parsec.  My GSoC mentor, Aaron Mavrinac, has outlined these items for me to complete in the next week or so:

1. Make a test commit to tpserver-cpp mtsec branch (add yourself to AUTHORS).

2. Read the TP protocol spec again, make sure you understand what each
thing is.

3. Read Part III of the ruleset development manual.

4. Write me a report about what exactly MTSec currently does in the
code – summary of what the standard hooks are doing, list of orders,
list of objects, etc.

I’ve completed task #1 and I am beginning the rest of the tasks.  My plan is to read the spec over again (I read it many times during the proposal stage) and complete these tasks by the end of the weekend.

I mentioned previously that I would be posting my complete proposal to this blog. Today, I have gone ahead with that and it is viewable in this post.  Throughout the summer as I become more acclimated to Thousand Parsec and the Google Summer of Code process I will be posting regarding possible areas for improvement for this proposal.
(more…)