On Fri, 2008-03-21 at 15:13 -0500, Ryan Neufeld wrote: > Just wanted to let the devs know I have posted on the Wiki some rough > drafts of documentation for the Risk ruleset I will be proposing for > GSOC as well as a rough draft of my proposal itself. It would be > appreciated if any of you (especially llnz :D) looked it over and left > some feedback. The docs on the Risk ruleset are here: > http://www.thousandparsec.net/wiki/Risk . And my proposal is here: > http://www.thousandparsec.net/wiki/Jphr_proposal I would recommend making the link to your Risk information quite a bit larger, its a little hard to find at first and gave me the impression that your proposal was a lot shorter then it actually is.
As Lee mentioned, Thousand Parsec is based around a 'simultaneous order submission' - 'turn at once' system. Matching this to the standard "take turns" method of a board game is going to be the most challenging tasks and I think you should put more effort into addressing this concern. Some type of example game session would be very useful. I would also recommend that you should take the Project Schedule and turn it into a "Road Map" with estimated dates. Specially important are "functional milestones", these are where you say specific things which will work - for example, "A client will be able to login and view the universe", "A player will be able to place units", etc. They should be testable by your mentor externally, something like "The framework will be done" is not suitable. Of course these dates will change as you get more information - but it should be good for seeing if you have included enough work. We are happy to help you adjust your timeline as we have better knowledge on how long certain things will take. I would recommend taking a look at Lee's "ruleset-book", it's probably quite out of date and it was never completed, but it is still pretty good. http://git.thousandparsec.net/gitweb/gitweb.cgi?p=ruleset-book.git;a=summary Hope this help! Tim 'Mithro' Ansell _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
