Hello loveheaven, sorry for the late response. I think hailstone pretty much covered it. Basically, post your ideas and if you implement something, post a patch. You can also use the bug tracker to submit patches (
http://bugs.codemonger.org). If you care to, there are a lot of bugs now that could be addressed if you so choose to. There is a lot in flux right now, both in the 0.2 and 0.3 branch, so in short, please don't submit any networking or GUI patches right now, since that's what's changing so much at the moment.
The 0.2 branch is supposed to be the "stable" branch, but multiplayer has yet to experience a fully working condition in GAE, so I finally decided to chop the whole damn thing up and re-design and re-write it from the ground up (sucking in old sources here and there). None the less, the idea is that 0.2.12 will have working multiplayer functionality and thereafter, few functional changes will go into 0.2 (bug fixes & such) and the primary development focus will be on 0.3.
As far as refactoring, I welcome that, although I would prefer you post an idea before proceeding too deeply. As you can see by examining the GAE vs Glest class structures, quite a bit has already been refactored, but there is a good deal yet to be done. I recently isolated another recurring pattern (with "update()"ing objects and scheduling) that I've implemented into a cute base class (thus simplifying the design and reducing code duplication). I'll still be a bit scarce for another week, after which I'll be on much more often (except for the week that follows
)
