Promoting strong community involvement in the project, streamlining development and project management (not just a bug tracker, but also workflow management, tasks, etc.), and I'd like to work towards implementing a very well-documented, and very homogeneous API.
Among other code enhancements, once AI2008 is completed, I'd like to focus directly on the code itself by finding and fixing bottlenecks and performing optimizations without affecting code readability. On the subject of readability, OpenKore needs standardized coding and documentation practices. The lack of this has been a major hindrance to OpenKore's growth, as seen in the numerous "special case" bugs (eg: Swordsman-tree skills with skillsAddAuto).
As for managing the code itself, I plan to enforce some minor education standards. Specifically: version control and using it to its potential. There's nothing wrong with having three or four different branches in the SVN repo at once time, and it will help with developers working to tackle a specific problem, or implement a specific feature, without disrupting the stable branch. This has obviously not been a priority in the past, and I believe proper version control usage will prevent bugs. As we all well know, preventing bugs is a lot easier than fixing them.
cs : ee : realist