One of the first applications of the Querki system, once it's up to being at least vaguely real, is going to be a story-management system; at that point, this list should go into there. But there's a long ways to go first, and a lot of stories to be prioritized. So here's the list, in rough priority order.
- I should be able to program in something
- Probably in Java, I think.
- Task: Get Java set up and running on one or more of my machines.
- Task: Install Eclipse, and learn how to use it.
- The Programmers should be able to manage checkpoints and releases -- we need a version-control system.
- Task: I think I'm going to use SourceForge?, so research that.
- Task: Set up the repository, and get my system talking to it for easy checkins.
- The Querki Project should have a sensible open-source license -- need to figure out which license to use, and mark the files up. I don't want to use anything as strict as GPL, nor as open as zlib.
- Task: Research the options.
- Task: Make a decision.
- Task: Mark all the source files up appropriately.
- The Programmers should be able to consistently test their work
- Task: Set up JUnit, and get working with Eclipse
- Task: Set up Selenium-RC, and get working with Eclipse
- The Programmers should have a good programming architecture to work in
- Task: Write a Java version of the Ecosystem pattern
- Task: Get a config system working, suitable for managing a site
- Task: Get a logging system working, mainly focused on debugging and serious errors
- A Querki Admin should be able to easily manage his site
- Task: Write a GUI-based Config editor