NSFW: While yea that may be a good way to keep people interested in the project - it would be a step backward. I would be writing code that would never be used in the final project.
malcom2073: yes that was more in line with the plan. While its intended as a legacy feature (not the ideal way to design a plugin) application embedding will be possible with a single function.
Hessian: While our project goals seem to be different we are in need of developers if you are interested.
pRoFiT: I too have had to use it at work so i'm well aware of it. There is a task list in my head but it would probably be of more use if its written down. I wasn't saying scrum didn't apply as much as not in the traditional sense. In larger companies they handle multiple items simultaneously and prioritize each sub task for their item.
In open source we have (hopefully) multiple developers and while feature x may be priority 1 if we don't have someone who can code feature x but they can code feature y which ranks 3 - then feature y comes first. At times we may be able to do items 1,2 and 3 at the same time.
That said heres the roadmap (/priority list) - and it's on the wiki too:
1) Design the openGL rendering engine and create the basic control set (which well be expanded later) - panel, button, label, text box, image
2) Design the basic plugin system for High-Level Plugins
3) Design a hard coded main screen and begin performance testing
4) Build up the rest of the framework - OS Detection, basic tools, networking, database
5) First pass at the Low-Level Plugins
6) Expand control set - Checkbox, option box, Drop Down, List Box, Image List, Progress Bar, Embedded Application
7) Second pass at Low-Level Plugins
8) All Hardcoded modules moved to high level plugins
9) Skin Support
10) Rinse and repeat